We have ORA-12569 in PL/SQL Dev

[Alexander]

Hello!

I've created database link from 10.2.0.2 to 9.2.0.7:

create database link ETL
  connect to DATA_LOADER
  identified by ************
  using 'etl.inf.sonicduo.com';

for our programmer.

But if he try to expand 'Database links' in PL/SQL Dev on his work machine he receive the error message ORA-12569: TNSacket checksum failure

I can expand 'Database links' on my machine and i can use ETL database link:

SQL> select 555 from dual@etl;

       555
----------
       555

And we are using the same version of PL/SQL Dev 6.0.3.893

Could anybody help me in this case?

 

[Marco Kalter]

To obtain some more diagnostic information, can you modify the shortcut and add the debug parameter? For example:

"C:\Program Files\PLSQL Developer\plsqldev.exe" debug

Reproduce the problem and send me the debug.txt file that is generated in the PL/SQL Developer directory.

 

[dgrieb]

Was anything learned? We are experiencing the same error message when we try to expand the database links for one of our schemas. We are on PL/SQL Developer version 7.0.3.1123 going against an Oracle 10.2.0.2.0 database.

 

[Marco Kalter]

Not really. Can you do a similar test? Modify the shortcut and add the debugsql parameter? For example:

"C:\Program Files\PLSQL Developer\plsqldev.exe" debugsql

Reproduce the problem and send me the debug.txt file that is generated in the PL/SQL Developer directory.

 

[dgrieb]

Sorry, didn't log back in in a while to see that you responded so quickly. I do appreciate it.

We have since isolated that this error is occurring when we create a database link from an Oracle 10.2.0.2.0 database to another an Oracle 10.2.0.2.0 database. It does not occur when we go from a 10.2.0.2.0 to a 9.2.0.7.0 database. In generating the debug file, I did notice that my current Oracle home was a 10g home. On a whim, I changed my Oracle home in preferences from auto-detect to my 10gR2 Oracle Warehouse Builder home. After I restarted PL/SQL Developer, I was able to expand the Database links node in the objects tree in the GUI. That appears to be a viable workaround.

I will be sending you a fail and a succeed debug file for your information.