-
ORA-02068: following severe error from dblink
Dear friends,
My database (oracle 9.2.0.8.0) will call another database's (oracle 9i cluster) view through DB Link to get some data.
If we are to access the data for the first time in a particular session, it gives the output within a second.
But if we access the data after 45mins in the same session(already connection is open), the query is running for 9 mins it throws an oracle error.
There is no network issue also(solaris 5.8 server).
select * from where =;
synonym is created in my database for remote database view (schema_name.view_name@dblink_name)
please find the Oracle error below:
ORA-02068: following severe error from RAMBOMAX
ORA-03113: end-of-file on communication channel
SID EVENT STATE WAIT_TIME SECONDS_IN_WAIT P1 P2 P3 SQL_HASH_VALUE
---
--------------------------------------------------------------------------------
-----
--------------------------------------------------------------------------------
--------------- -- -- --
--------------------------------------------------------------------------------
547 SQL*Net message to client WAITED KNOWN TIME -1 0 1413697536 1 0 951575186
283 SQL*Net message from dbli WAITING 0 441 675562835 1 0 3503340408
298 SQL*Net message from dbli WAITING 0 199 675562835 1 0 3503340408
572 SQL*Net message from dbli WAITING 0 485 675562835 1 0 3503340408
632 SQL*Net message from dbli WAITING 0 358 675562835 1 0 3503340408
634 SQL*Net message from dbli WAITING 0 250 675562835 1 0 3503340408
581 SQL*Net message from dbli WAITING 0 208 675562835 1 0 3503340408
561 SQL*Net message from dbli WAITING 0 376 675562835 1 0 3503340408
520 SQL*Net message from dbli WAITING 0 413 675562835 1 0 3503340408
What could be the reason for this? could some one please help me on this?
Its very urgent this error is happening in live servers :(
Thanks,
Prathap
-
if the resource limits are enabled then check the value for idle_time resource and increase the value.
Also look into adding SQLNET.EXPIRE_TIME = to the sqlnet.ora file.
Thanks,
Vijay Tummala
Try hard to get what you like OR you will be forced to like what you get.
-
Originally Posted by vnktummala
if the resource limits are enabled then check the value for idle_time resource and increase the value.
Also look into adding SQLNET.EXPIRE_TIME = to the sqlnet.ora file.
Thanks,
Hi,
The resource limits are UNLIMITED only.
SQLNET.EXPIRE_TIME =3
Kindly do the needful,
thanks,
prathap
-
increase the expire_time value. please test it in dev or test environment before moving to production.
Thanks,
Vijay Tummala
Try hard to get what you like OR you will be forced to like what you get.
-
Most probably remote database is timing out your connection.
Close dblink before attempting to use it again.
Pablo (Paul) Berzukov
Author of Understanding Database Administration available at amazon and other bookstores.
Disclaimer: Advice is provided to the best of my knowledge but no implicit or explicit warranties are provided. Since the advisor explicitly encourages testing any and all suggestions on a test non-production environment advisor should not held liable or responsible for any actions taken based on the given advice.
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
Click Here to Expand Forum to Full Width
|