HP Storage Management for Oracle 5.0 Release Notes, HP-UX 11i v3, First Edition, May 2008

• Problem

You can click the Quota tab for the Storage Checkpoint available from the GUI. However,

if the file system and the Storage Checkpoint are on a version earlier than Disk Layout

Version 6, the unknown error code 4646 is displayed.

Workaround

To display Storage Checkpoints Quotas from the GUI for Disk Layout Version 5 and later,

complete the following steps:

1. Using Veritas File System 3.5, create a file system.

2. Upgrade to Veritas File System 5.0. However, you must not upgrade the file system

disk layout version.

3. Create a checkpoint, and click the Quota tab in the GUI.

• Problem

Renaming columns in login.sql can sometimes cause scripts to fail or produce incorrect

results.

Workaround

To prevent this, make the following changes in the user environment to avoid loading the

1. Move the login.sql script to another directory, for example, ~oracle/login.sql.

2. Ensure that this new directory is included in SQLPATH, for example:

export SQLPATH=~oracle/sql:$SQLPATH

3. Do not make SQLPATH read-only. This enables the SMO scripts to be cleared at runtime.

4. Avoid starting the SMO scripts from the directory where login.sql resides, unless

you are sure that login.sql does not contain any settings or commands that change

the default output for queries against the data dictionary or increase the startup time

for SQL*Plus.

You must also avoid using any settings or commands in the glogin.sql file that

change the default output for queries against the data dictionary, or that may increase

the startup time for SQL*Plus.

• Problem

The following error messages are saved in the sys.log file on clusters:

GAB WARNING V-15-1-20115 Port d registration failed, GAB not

configured vxgms: GAB_API_REGISTER error=261

ODM WARNING V-41-6-5 odm_gms_api_start_msgs fails

These messages are displayed in the following scenarios:

— When you restart the machine.

— When ODM is started using /sbin/init.d/odm start and the node is not part of

a cluster.

Workaround

There is no workaround for this problem. You can ignore these messages.

Known Problems And Workarounds 23