Rdb-OEM 9i Error Guide 7/16/03 2:06 PM

Oracle Rdb Extension for OEM 9i Error Guide Release V7.1.0.0

Oracle Rdb Extension for OEM 9i

Error Guide

Release 7.1.0.0

for Oracle9i Enterprise Managers on Windows NT, Windows 2000, Solaris for Oracle9i Intelligent Agents on OpenVMS for Alpha

June 2003

This document provides information on the potential errors generated by and potential solutions for the Oracle Rdb integration in the Oracle9i Enterprise Manager. Error Messages

Installation

Activity Error listed in the installation error log file in folder C:\Program Files\Oracle\Inventory\log\ Displayed None Error Logged exception VdbSQLException{wstring reason="ORA-01017: invalid username/password; Error logon denied\n";long oracleError=1017;long errorCode=1;wstring sqlStmt="";} On the installation, an invalid username and/or password was specified for the Oracle Management Server Repository.

To update this repository manually, execute the following command from a MS-DOS command window: Possible /bin/oemctl.bat import registry Problems/ OMSRegistryForRdb.registry /@ Solutions where , , and are replaced with the appropriate values. The above example assumes the OMSRegistryForRdb.registry file is in the current directory. This registry file is located in the \classes\oracle\sysman\rdb\registry\ folder.

After the OMS registry is updated, the OMS must be restarted.

Page 1 of 5 Rdb-OEM 9i Error Guide 7/16/03 2:06 PM

Activity Error during installation on Solaris Displayed Error in CreateOUIProcess(): 14 :Bad address Error Logged Error in CreateOUIProcess(): 14 Error :Bad address As per articles in Metalink, unsetting the LD_LIBRARY_PATH environment variable fixes Possible this issue. Problems/ Solutions Ksh/sh: $ unset LD_LIBRARY_PATH csh: % unsetenv LD_LIBRARY_PATH

Navigational Console

Activity Displaying information from a database in the navigational console Displayed "This operation could not be completed because a jdbc connection could not be established Error with the target" SQLException: java..SQLException: Io exception: The Network Adapter could not establish the connection Logged Message: Io exception: The Network Adapter could not establish Error the connection SQLState: null ErrorCode: 17002 Possible On OpenVMS system, oci dispatcher is not running or is in an invalid state. If the oci Problems/ dispatcher is "inactive", start it. If the oci dispatcher is "running", stop it and restart it. Solutions

Activity Displaying information from a database in the navigational console Displayed "This operation could not be completed because a jdbc connection could not be established Error with the target" SQLException: java.sql.SQLException: Io exception: End of TNS data channel Logged Message: Io exception: End of TNS data channel Error SQLState: null ErrorCode: 17002 Possible Database is not open for access. From the OpenVMS system, try opening the database using Problems/ RMU/OPEN. Solutions

Page 2 of 5 Rdb-OEM 9i Error Guide 7/16/03 2:06 PM

Activity Displaying information from a database in the navigational console Displayed "This operation could not be completed because a jdbc connection could not be established Error with the target" SQLException: java.sql.SQLException: ORA-01017: invalid Logged username/password; logon denied Message: ORA-01017: invalid username/password; logon denied Error SQLState: 72000 ErrorCode: 1017 Possible Username or password in the OEM preferred credentials does not match those on the OpenVMS system on which the Rdb database resides. After changing username or password, Problems/ Solutions the user might need to log out and log back into the OEM console since there have been known to be caching issues.

Activity Navigating a database in the OEM Console Displayed Oracle Management Server is out of sync with the Agent Error

Logged Error Possible The OMS somehow got out of sync with the Intelligent Agent. On the node running the Problems/ Agent, delete the .q files in the ora_agent directory tree. In the OEM console, drop the node Solutions on which the database resided and rediscover the node.

Events

Activity Creating an event Displayed Registration Failed Error VNI-4002 : Unknown gateway exception java.lang.String

Logged Error Possible Event definition is not registered in OMS registery. See installation guide on how to update Problems/ OMS registry. Solutions

Activity Creating an event Registration Failed Displayed Registration of event test failed. Error Event Test Name: "" Reason : Event file does not exist

Logged Error Possible Problems/ On OpenVMS system, TCL file associated with the event is not found. Solutions

Page 3 of 5 Rdb-OEM 9i Error Guide 7/16/03 2:06 PM

Activity Creating an event Displayed Oracle Management Server is out of sync with the Agent Error VI-4040: Oracle Management Server out of sync with Agent

Logged Error Possible The OMS somehow got out of sync with the Intelligent Agent. On the node running the Problems/ Agent, delete the .q files in the ora_agent directory tree. In the OEM console, drop the node Solutions on which the database resided and rediscover the node.

Jobs

Activity Output from any job Displayed Failed Error Show Output "This job did not write any output."

Logged Error Possible The user account specified for the NODE in the preferred credentials does not have enough Problems/ privileges to run the job specified. Solutions

Activity Output from any job Displayed Failed Error Show Output "VNI-2015: Authentication Error"

Logged Error Possible The username and/or password specified for the NODE in the preferred credentials are Problems/ incorrect. Solutions

Page 4 of 5 Rdb-OEM 9i Error Guide 7/16/03 2:06 PM

Activity Output from RunDCL job Displayed Failed Error

Logged Error The job appears to run to completion, but the error

!%DCL-W-SKPDAT, image data (records not beginning with "$") ignored Possible Problems/ Solutions occurs towards the end of the job output. To fix, make sure there are no blank lines in (including at the end) of your DCL script. Also, add the line

!$ exit

Activity Creating a job Displayed Oracle Management Server is out of sync with the Agent Error VI-4040: Oracle Management Server out of sync with Agent

Logged Error Possible The OMS somehow got out of sync with the Intelligent Agent. On the node running the Problems/ Agent, delete the .q files in the ora_agent directory tree. In the OEM console, drop the node Solutions on which the database resided and rediscover the node.

Copyright © 2003 . All Rights Reserved.

Page 5 of 5