IBM-AUSTRIA - PC-HW-Support    30 Aug 1999

ORACLE ENTERPRISE MANAGER SHOWS DATABASE as NOT STARTED

    Record number:       H165893
    Device:              D/T8680
    Model:               M
    Hit count:           UHC00000
    Success count:       USC0000
    Publication code:    PC50
    Tip key:
    Date created:        O99/02/10
    Date last altered:   A99/02/11
    Owning B.U.:         USA


Abstract: ORACLE ENTERPRISE MANAGER SHOWS DATABASE as NOT STARTED

TEXT:

Oracle Enterprise Manager shows database instances as not started when it is known that they are started.

SYMPTOMS:

When running the Oracle Enterprise Manager Console, database instances that are known to be started are displayed as not started.

The status displayed about the database instances is not correct.

PROBLEM ISOLATION AIDS:

•  The system is a Netfinity 7000 M-10 server, Type 8680, any supported Model configured with Oracle Parallel Server.

•  The system is configured with the following option:

    IBM Netfinity Cluster Enabler Software

•  NOS affected:

WORKAROUND:

1.  Stop the Oracle Enterprise Manager program.
2.  Re-run the Oracle OPSCONF utility. This produces a file named TNSNAMES.ORA.
    The file is located in the %oraclehome%\OPS directory.
3.  Copy this new TNSNAMES.ORA file to the machine where the Oracle Enterprise Manager Console program is being run.
4.  Restart the Oracle Enterprise Manager program and re-try the operation to display the  status of database instances on the cluster nodes.
    DO NOT re-run the Service Discovery step from the Oracle Enterprise Manager Console.

DETAILS:

The steps described above under "WORKAROUND" are currently the only known workaround for this problem.
This problem has been reported to Oracle for resolution.

This problem appears to originate due to a statement in the Oracle Parallel Server "Getting Started" guide book (page 5-18).
A utility called OPSCONF is used to configure Oracle Parallel Server.
OPSCONF produces a file named TNSNAMES.ORA which is copied to each node in the cluster and to the machine where the Oracle Enterprise Manager Console is to be run.

The Oracle documentation instructs the customer to remove the OPS.world entry from the TNSNAMES.ORA file or else the OracleAgent80 service may crash.
However, if that entry is removed before running the Service Discovery process, then the database instances will not be discovered correctly and their status will not be displayed correctly.

The workaround creates the TNSNAMES.ORA file with the correct entries.
This version of the file can be used on the machine where the Oracle Enterprise Manager Console is running.
The version of TNSNAMES.ORA with the entry removed (according to the "Getting Started" guide) can be used on the individual cluster nodes.

TRADEMARKS:

Microsoft, Windows, Windows NT, and the Windows logo are trademarks of Microsoft Corporation in the United States and/or other countries.

Other company, product and service names may be the trademarks or service marks of others.

Please see the LEGAL  -  Trademark notice.
Feel free - send a   for any BUG on this page found - Thank you.