High Availability Monitors Version A.03.10 Release Notes

Chapter 1 15

Known Problems and Workarounds

You will then see error messages similar to the following during the

execution phase:

Summary of Analysis Phase:

ERROR Skipped (in analysis)

EMS-Config.EMS-GUI, r=A.03.10

ERROR Skipped (in analysis)

EMS-Core.EMS-ORE, r=A.03.10

ERROR 2 of 5 filesets had Errors.

3 of 5 filesets had no Errors or Warnings:

ERROR The Execution Phase had errors. See

the above output for details.

NOTE Do not use the -x enforce_dependencies=false option under normal

circumstances. Since the option applies to all ﬁlesets with this analysis

error, it would potentially prevent other required ﬁlesets from being

installed.

For more information about installation procedures and related issues,

refer to the following manuals:

• Managing HP-UX Software with SD-UX (B2355-90154)

• swinstall (1M) in the HP-UX Reference (B2355-90166)

When a database is not available, an error message

indicates that its resource instance is not available

• What is the problem? If a database is unavailable or its server is

down, you may see this error message: Resource “/rdbms/...”

is not available. The message will pop up in the EMS graphical

user interface window when you try to access the following resources:

server_started, allowed_max_connects, peak_connects,

usage (for both server and database), commits,

commits_per_sec, database_used, and database_allocated.

• What is the workaround? Before you try to monitor these particular