ORA-12518 and async I/O limit

From: Patrice sur GMail <patrice.boivin@xxxxxxxxx>
To: ORACLE-L <oracle-l@xxxxxxxxxxxxx>
Date: Wed, 13 Mar 2013 11:34:14 -0300
We are seeing two errors, not sure what is causing them.
We think it may be due to a network timeout, the session being dropped at
the other end, the database not knowing and still running the job, but it
never closes or gets rolled back.  When the job is re-run it connects again
to the remote db, tries to run but finds its objects are already locked by
the previous run, and then the database service (yes, windows) stops,
cutting off the Oracle instance on the windows server.

We did notice with ping tests that one of our network segments is so
congested that packets get dropped.

The two errors are:
EM Alert: Critical:SID_goes_here - Failed to connect to database instance:
ORA-12518: TNS:listener could not hand off client connection (DBD ERROR:
OCIServerAttach).

and

*** 2013-03-13 03:30:20.386

*** ACTION NAME:(UserLocks) 2013-03-13 03:30:20.386

*** MODULE NAME:(emagent_SQL_oracle_database) 2013-03-13 03:30:20.386

WARNING:Could not lower the asynch I/O limit to 320 for SQL direct I/O. It
is set to -1

WARNING:Could not lower the asynch I/O limit to 256 for SQL direct I/O. It
is set to -1

*** ACTION NAME:(instance_throughput) 2013-03-13 03:30:20.386

*** MODULE NAME:(emagent_SQL_oracle_database) 2013-03-13 03:30:20.386

WARNING:Could not lower the asynch I/O limit to 288 for SQL direct I/O. It
is set to -1

WARNING:Could not lower the asynch I/O limit to 288 for SQL direct I/O. It
is set to -1

WARNING:Could not lower the asynch I/O limit to 288 for SQL direct I/O. It
is set to -1

WARNING:Could not lower the asynch I/O limit to 256 for SQL direct I/O. It
is set to -1

*** ACTION NAME:(instance_efficiency) 2013-03-13 03:30:20.402

*** MODULE NAME:(emagent_SQL_oracle_database) 2013-03-13 03:30:20.402

WARNING:Could not lower the asynch I/O limit to 288 for SQL direct I/O. It
is set to -1

WARNING:Could not lower the asynch I/O limit to 288 for SQL direct I/O. It
is set to -1

WARNING:Could not lower the asynch I/O limit to 288 for SQL direct I/O. It
is set to -1

WARNING:Could not lower the asynch I/O limit to 256 for SQL direct I/O. It
is set to -1

[...]


 The last time I restarted the database I set it to synchronous I/O, to see
if that will make a difference.


We also noticed that when we restart the instance we have to go in EM and
kill a job session which is locking what looks like the job queue.  Maybe
we are not patient enough?  [?]


This is an old version, 10.2.0.4 on windows x64 but I see in Metalink that
the error re-occurred on other OSes (AIX, possibly linux)  and in later
versions (11.1 "and later" ).


-- Patrice
My profiles: [image:
Facebook]<http://www.facebook.com/home.php?#!/profile.php?id=100000206805521>[image:
LinkedIn] <http://ca.linkedin.com/pub/patrice-boivin/a/933/5a9>[image:
Twitter] <http://www.twitter.com/PatriceBoivin>
 <http://www.twitter.com/PatriceBoivin>
Signature powered by WiseStamp <http://www.wisestamp.com/email-install>



--
//www.freelists.org/webpage/oracle-l
ORA-12518 and async I/O limit

Other related posts:
