Problems connecting to distributed databases using Oracle10g.

Question Recieved: We have encountered issues connecting to distributed databases using the internal CC&B subsystems (and TNSping) resulting in the following errors:
***********************************************************************
Fatal NI connect error 12557, connecting to:
(DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=CCBTEST)(PORT=1521))(CONNECT_DATA=(SERVICE_NAME=CCBCONVT)(CID=(PROGRAM=C:\spl\CCBCONVT\runtime\CLBDSYNC.exe)(HOST=CCBTEST)(USER=s_cissys))))
VERSION INFORMATION:
TNS for 32-bit Windows: Version 10.2.0.2.0 - Production
Time: 04-SEP-2007 16:26:20
Tracing not turned on.
Tns error struct:
ns main err code: 12557
TNS-12557: TNS:protocol adapter not loadable
ns secondary err code: 12560
nt main err code: 527
TNS-00527: Protocol Adapter not loadable
nt secondary err code: 0
nt OS err code: 0
and
--------------------------------------------------------------------------
--Executing Data Synchronization Process at 09-05-2007 08:50:51
--------------------------------------------------------------------------

--Connecting to the Database
--User Name : CISUSER
--Database Name : CCBCONVT

Couldn't connect to the database Oracle CCBCONVT CISUSER - ORA-12557: TNS:protocol adapter not loadable (DBD ERROR: OCIServerAttach)

Answer: After ensuring that all of the Oracle connections were making use of TNS to perform connections (via the netca oracle command) we investigated the PATH settings and discovered that the original PATH setting
Path=D:\oracle\agent10g\jlib;D:\oracle\agent10g\bin;C:\spl\3rdparty\Perl64\site\bin;C:\spl\3rdparty\Perl64bin;D:\oracle\product\10.2.0\db_1\perl\site\5.8.3\lib\MSWin32-X64-multi-thread\auto\DBD\Oracle;D:\oracle\product\10.2.0\db_1\bin;D:\oracle\product\10.2.0\db_1\NETWORK\ADMIN;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem
caused tnsping to return
TNS-12557: TNS:protocol adapter not loadable
but changing the path by moving the $ORACLE_HOME\bin directory to the beginning (as below)



Path=D:\oracle\product\10.2.0\db_1\bin;D:\oracle\agent10g\jlib;D:\oracle\agent10g\bin;C:\spl\3rdparty\Perl64site\bin;C:\spl\3rdparty\Perl64\bin;D:\oracle\product\10.2.0\db_1\perl\site\5.8.3\lib\MSWin32-X64-multi-thread\auto\DBD\Oracle;D:\oracle\product\10.2.0\db_1\NETWORK\ADMIN;%SystemRoot%\system32;%SystemRoot%;%SystemRoot%\System32\Wbem
corrected this problem.
Further experimentation highlighted the fact that D:\oracle\agent10g\bin was the problematic directory in the PATH. Examining the contents of this directory revealed older versions of tnsping.exe and oranjni10.dll that are present in the D:\oracle\product\10.2.0\db_1\bin directory as shown below.
D:\oracle\agent10g\bin
tnsping.exe 10.2.0.2.0
oranjni10.dll 10.2.0.1.0
D:\oracle\product\10.2.0.db_1\bin

tnsping.exe 10.2.0.3.0
oranjni10.dll 10.2.0.3.0
As a result we have changed our path settings and restarted our CC&B instances to resolve our connection problems.

Comments

Victor Dom said…
At me the same mistake has arisen at creation standby DB by means of Grid Control
DB-10.2.0.3 (32 b)
GC – 10.2
Platform W2003 – 64
Arises after restoration of a DB from backup, before correction init.ora
Yet has not won this problem, it is necessary to do last steps manually. The reason of failure yet has not understood

Popular posts from this blog

Threading...

Tidy Balances.. I don't really hate it

Increasing batch run throughput