Oracle Agent Login Failure

Logon Failure messages in the *col.ou* logs

How to verify connectivity to the Oracle database

1. Connect to system with the user id that ITM Oracle Agent installed e.g. if user uses 'root' for ITM 6.X Oracle Agent, connect system as 'root'.
2. Set environment for sqlplus connection.

On UNIX, Linux, set following env variables.

export ORACLE_HOME="<full path of oracle home>"
export ORACLE_SID="<instance>"
export PATH=$ORACLE_HOME/bin:$PATH

On Windows, use following commands to set variables.

SET ORACLE_HOME="<full path of oracle home>"
SET ORACLE_SID="<instance>"
SET PATH=%ORACLE_HOME%\bin;%PATH%

3. Connect Oracle instances by following command

$ sqlplus <connection id>/<password>

SQL*Plus: Release 9.2.0.1.0 - Production on Tue Nov 26 12:02:59 2002

Copyright (c) 1982, 2002, Oracle Corporation. All rights reserved.

Connected to:

Oracle9i Enterprise Edition Release 9.2.0.1.0 - Production

With the OLAP and Oracle Data Mining options

JServer Release 9.2.0.1.0 - Production

SQL>

**** Does this connect? If it does, the listener is well configured. If this does not connect, there is a problem with the listener configuration.

If there is issues with connecting the oracle server, the following errors may appear in *col.ou* logs, check the logs for the following 6 errors and provide the respective solution:

Error #1

RCD0100E (150904) Unable to connect to ORACLE at collector

RCD0105E (150904) Connect sql code = -12547

RCD0105E (150904) Connect sql code msg detail = ORA-12547: TNS:lost contact

SOLUTION:

- LIBPATH or LD_LIBRARY_PATH is set properly.

- The $ITMHOME/config/or.ini file has the following statement in it:

export LD_LIBRARY_PATH=$CANDLEHOME$/$BINARCH$/$PRODUCTCODE$/lib:$CANDLEHOME$/ARCHITECTURE$/lib:/usr/lib

- Oracle agent should be able to access the libraries in the database home.

Error #2

ORA-12541: TNS: no listener

SOLUTION:

- Make sure of listener.ora file in the correct path in TNS_ADMIN. Default TNS_ADMIN is $ORACLE_HOME/network/admin/

Error #3

CML1530I (095109) Start collecting. -------------------------------

RCD0100E (095115) Unable to connect to ORACLE at collector

RCD0105E (095115) Connect sql code = -1034

RCD0105E (095115) Connect sql code msg detail = ORA-01034: ORACLE not available

ORA-27123: unable to attach to shared memory segment

SOLUTION:

- The root/non-rootid has required permissions recursively on oracle_home path(Refer DCF DOC Id : 1247118 )

- Make sure that you can logon to,

sqlplus <dbuserid used to configure the ITM agent>/passwd

Error #4

OIN0105T (101031) Connecting to Oracle, user:xxxxxx
RCD0100E (101031) Unable to connect to ORACLE at collector
RCD0105E (101031) Connect sql code = -12546 ;
RCD0105E (101031) Connect sql code msg detail = ORA-12546:TNS:permission denied

SOLUTION:

Oracle Support has the Doc ID: 443698.1 for this.

Change directory to :
$ cd $ORACLE_HOME/install

./changePerm.sh

Run changePerm.sh and specify the patched server Oracle home location, before accessing client-side utilities or libraries in the database

Note: Error #4 can happen on any platform if customer uses Oracle Enterprise Edition Version 10.2.0.1 to 10.2.0.3.

When it happens, they'll also get the same error when running the following as root at local host. $ORACLE_HOME/sqlplus userid/pw

ORA-12546: TNS:permission denied
But following command works fine. $ORACLE_HOME/sqlplus userid/pw@SID_NAME

Error #5

RCD0100E (161459) Unable to connect to ORACLE at collector

RCD0105E (161459) Connect sql code = -1034

RCD0105E (161459) Connect sql code msg detail = ORA-01034: ORACLE not available

ORA-27101: shared memory realm does not exist

Note: Error #5 happens when the instance is running but database is down.

When database is down,
C:\>sqlplus /nolog

SQL*Plus: Release 10.1.0.2.0 - Production on Tue Aug 5 16:14:18 2008

Copyright (c) 1982, 2004, Oracle. All rights reserved.

SQL> connect / as sysdba

Connected to an idle instance.


When database is up,
C:\IBM\ITM\TMAITM6>sqlplus /nolog

SQL*Plus: Release 10.1.0.2.0 - Production on Tue Aug 5 16:25:10 2008

Copyright (c) 1982, 2004, Oracle. All rights reserved.

SQL> connect / as sysdba

Connected.


When database is down even though the server instance is up, they'll get 1034,27101 error in collector logs like Error #5.

SOLUTION:

Startup the database.

C:\> sqlplus /nolog

SQL*Plus: Release 10.1.0.2.0 - Production on Tue Aug 5 16:14:18 2008

Copyright (c) 1982, 2004, Oracle. All rights reserved.

SQL> connect / as sysdba

Connected to an idle instance.

SQL> startup

ORACLE instance started.

Total System Global Area 171966464 bytes

Fixed Size 787988 bytes

Variable Size 145750508 bytes

Database Buffers 25165824 bytes

Redo Buffers 262144 bytes

Database mounted.

Database opened.

SQL> exit

Error #6

ORA-01017: invalid username/password

Solution:

This error usually happens when the password was not set correctly during the configuration. Refer Technote#1256445
Also, when the korgrant.sql was not executed properly, this error could happen. Refer Technote#1253597

Even though the solution for the error types are appropriate, some instances they need to be combined together to get it worked perfectly. By that time, L2 may seek L3's response to figure out the exact issue.