|
5.165 bytes |
Service Hints & Tips |
Document ID: MCGN-458DXQ |
|
This document is provided to IBM and our Business Partners to help sell and/or service IBM products. It is not to be distributed beyond that audience or used for any other purpose. |
Netfinity 7000 M10 - Oracle Enterprise Manager shows database as not started
Applicable to: World-Wide
Source: Retain tip H165893
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.
Note: Supported configurations are listed at the following URL: http://www.pc.ibm.com/us/compat/clustering/matrix.shtml
look for "Oracle Parallel Server".
The system is configured with the following option:
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.
SAS KEYWORDS:
PSY2, D/T8680, NETFINITY, SERVICER ONLY, 7000-M10, ORACLE, PARALLEL, 108197, ENTERPRISE, MANAGER, CONSOLE, DATABASE, ENABLER, OPSCONF, TNSNAMES.ORA
|
Search Keywords |
PSY2, D/T8680, NETFINITY, SERVICER ONLY, 7000-M10, ORACLE, PARALLEL, 108197, ENTERPRISE, MANAGER, CONSOLE, DATABASE, ENABLER, OPSCONF, TNSNAMES.ORA | |
|
Document Category |
Oracle Parallel Server, Retain | |
|
Date Created |
18-02-99 | |
|
Last Updated |
18-02-99 | |
|
Revision Date |
| |
|
Brand |
IBM PC Server | |
|
Product Family |
Clustering, Netfinity 7000 M10 | |
|
Machine Type |
Various, 8680 | |
|
Model |
| |
|
TypeModel |
| |
|
Retain Tip (if applicable) |
H165893 | |
|
Reverse Doclinks |
Date last altered: A99/02/11 |