Can ORA-01013 error cause by Temp TS contention?
- From: Karth Panchan <keyantech@xxxxxxxxx>
- To: ORACLE-L <oracle-l@xxxxxxxxxxxxx>
- Date: Sun, 9 Nov 2014 23:26:22 -0500
All
We are running Production Oracle 11.2.0.2 with 6 node RAC.
Our OLTP and Reports sharing same schema with single Temp table space.
Our OLTP App servers(.net) getting 40 occurrence of ORA-01013 error per hour.
Application have time out set for 30secs with Oracle connections.
Some occurrence generate Trace file with entry in alert.log, but some NO entry
in alert.log.
From trace file took sql and ran in production it came out instantly. SQL
wasn't cancelled by any end user or by time out due to no response from Oracle.
Talking to Production DBA they inform me this error is caused by TS enq
contention in TEMP table space caused by Reports running with large volume of
data.
My question was, then why my SQL plus comes with quick response all the time. I
was informed my session may be ran when there was no contention.
I am not convinced because my session was ran when our App Servers receiving
error and reports sessions were running.
Anyone agree with this TEMP TS contention cause ORA-01013 (agree I may be
missing something here) or any other scenarios?
Appreciate your input.
Thanks
Karth--
//www.freelists.org/webpage/oracle-l
Other related posts:
