| DBLink and 3113 [message #66949] |
Mon, 31 March 2003 04:05 |
Peter Babka
Messages: 2
Registered: March 2003
|
Junior Member |
|
|
Hello,
we have implemented the following solution:
- there is a forever looping plsql script in a local database (DB-01)
- the script executes a SELECT over a database link in an other database
(DB-99) using synonyms
- the SELECT is not issued during the STOP/START interval of DB-99
Whenever DB-99 stopped and restarted, the SELECT over the dblink terminates
the issuing thread with 3113 error code. We suspended the SELECT requests
during the STOP/START - but it did not help, our thead is terminating
regardless of the delay. Other applications (which start after DB-99
restart) are able to directly communicate with DB-99, but our program
aborts.
Our questions:
- is this situation known?
- is there any method which can avoid the 3113?
- is there any status flag which can be checked to ensure that the SELECT
will reach DB-99?
Both databases are on the same level, 8.1.7.4.50
Thanks
Peter
|
|
|
|
] 
Blog
Search
Help
Members
Register
Login
Home
