Weird problems in Oracle Applications environment
- From: amit poddar <amit.poddar@xxxxxxxx>
- To: oracle-l@xxxxxxxxxxxxx
- Date: Wed, 05 Jan 2005 15:56:43 -0500
Hi,
Database: 9.2.0.5
Middle tier: 9iAS (1.0.2.2.2)
Sometimes our Oracle applications database background processes start
dying, leaving behind trace files in udump directory.
This happens almost every minute till we bounce the middle tier.
The alert log says something like this:
Errors in file /u01/home/oracle/admin/BAN1/udump/ban1_ora_104222.trc:
Mon Jun 21 11:37:12 2004
Errors in file /u01/home/oracle/admin/BAN1/udump/ban1_ora_72416.trc:
Mon Jun 21 11:38:17 2004
Errors in file /u01/home/oracle/admin/BAN1/udump/ban1_ora_140886.trc:
And the udump trace file says:
*** SESSION ID:(365.6297) 2005-01-04 20:08:51.176
FATAL ERROR IN TWO-TASK SERVER: error = 12592
*** 2005-01-04 20:08:51.191
ksedmp: internal or fatal error
Current SQL statement for this session:
begin dbms_session.reset_package; end;
----- Call Stack Trace -----
calling call entry argument values in hex
location type point (? means dubious value)
-------------------- -------- --------------------
----------------------------
ksedmp+0148 bl ksedst 1027C5204 ?
opitsk+0970 bl ksedmp 2029D1C04 ?
opiino+0790 bl opitsk 000000000 ? 000000000 ?
opiodr+08e8 bl _ptrgl
opidrv+032c bl opiodr 3C104630B0 ? 400000000 ?
FFFFFFFFFFFFEE0 ?
0027B8718 ?
sou2o+0028 bl opidrv 3C00212E38 ? 4A004BBD0 ?
FFFFFFFFFFFFEE0 ?
main+0138 bl 01FD5D8C
Has anybody faced a similar problem. If yes how did you overcome it.
I have opened a tar with Oracle on this 4 times in last year.
Since this problem has happened 4 times last year and everytime we
bounce the middle tier the problem goes away.
Currently tar is open with Oracle on this.
thanks
amit
--
//www.freelists.org/webpage/oracle-l
Other related posts:
