Visit the Below Website to access unlimited exam questions for all IT vendors and Get Oracle Certifications for FREE
http://www.free-online-exams.com
http://www.free-online-exams.com
Problem: oracle.sysman.siebel.management.exceptions.SystemException: Start session failed. Session Id: null. Stderror stream: ODBC error 08001 in SQLConnect:[DataDirect][ODBC Oracle driver][Oracle]ORA-12154: TNS:could not resolve the connect identifier specified
On : 10.2.0.5 version, Managing Siebel Targets
When attempting to check the Siebel repository status in Grid Control,
the following error occurs.
ERROR
-----------------------
ORA-12154
When attempting to check the Siebel repository status in Grid Control,
the following error occurs.
ERROR
-----------------------
ORA-12154
Symptoms:
he issue can be reproduced at will with the following steps:
1. Add SiebelEnterprise
2. Check Siebel repository status in GC console
1. Add Siebel
2. Check Siebel repository status in GC console
Log files:
LOG FILE
-----------------------
Filename = emagent.trc
See the following error:
WARNING: Session id [388770] does not accept commands: Broken pipe (errno:32)
oracle.sysman.siebel.management.exceptions.SystemException: Start session failed. Session Id: null. Stderror stream: ODBC error 08001 in SQLConnect:
[DataDirect][ODBC Oracle driver][Oracle]ORA-12154: TNS:could not resolve the connect identifier specified
(native error 12154).
Unable to login using specified ODBC parameters.
-----------------------
Filename = emagent.trc
See the following error:
WARNING: Session id [388770] does not accept commands: Broken pipe (errno:32)
oracle.sysman.siebel.management.exceptions.SystemException: Start session failed. Session Id: null. Stderror stream: ODBC error 08001 in SQLConnect:
[DataDirect][ODBC Oracle driver][Oracle]ORA-12154: TNS:could not resolve the connect identifier specified
(native error 12154).
Unable to login using specified ODBC parameters.
Solution:
From the Siebel Server that is monitoring this Siebel Repository Database (DBstore), ensure that that Agent has a Network/admin directory with the TNSNAMES.ORA & SQLNET.ORA files in it. If not, create the subdirectory.
Restart the Agent.
At the Siebel Application Server host hosting the dbstore, log in as the Agent user
cd <SIEBEL>/siebsrvr/sys
vi odbc.ini
In this .odbc.ini file, there is a [ODBC Data Sources]
For example:
[ODBC Data Sources]
siebsrvr_SiaLOY_ENT=MERANT 4.2 Oracle 9 Driver
the first part, in the above example “siebsrvr_SiaLOY_ENT” is the ODBC name.
Remember this ODBC name.
There is a Siebel utility name <Siebel>/siebsrvr/bin/odbcsql
cd <SIEBEL>/siebsrvr/bin
./odbcsql /s <ODBC name> /u siebel /p <Siebel password>
To see the options available for the odbcsql utility, issue:
cd <SIEBEL>/siebsrvr/bin
./odbcsql /?
Restart the Agent.
At the Siebel Application Server host hosting the dbstore, log in as the Agent user
cd <SIEBEL>/siebsrvr/sys
vi odbc.ini
In this .odbc.ini file, there is a [ODBC Data Sources]
For example:
[ODBC Data Sources]
siebsrvr_SiaLOY_ENT=MERANT 4.2 Oracle 9 Driver
the first part, in the above example “siebsrvr_SiaLOY_ENT” is the ODBC name.
Remember this ODBC name.
There is a Siebel utility name <Siebel>/siebsrvr/bin/odbcsql
cd <SIEBEL>/siebsrvr/bin
./odbcsql /s <ODBC name> /u siebel /p <Siebel password>
To see the options available for the odbcsql utility, issue:
cd <SIEBEL>/siebsrvr/bin
./odbcsql /?
No comments:
Post a Comment