Errors in Trace and Alert Files Concerning Disappearing Processes

From: Dereck L. Dietz <>
Date: Wed, 23 Jan 2008 23:55:49 GMT
Message-ID: <9uQlj.925$>

Windows 2003 Server
8GB Memory
Shared Server

I finally received the trace and alert files from the off-site DBA and went through them to try to figure out the root cause of the processes we've had at my workplace that just disappear.

Here are two segments. Could someone possibly direct me to more details that I can present to my management and the off-site DBA for possible correction?

  • trace file: tiermed_s002_1864.trc ---
    • 2008-01-19 07:28:06.562
    • ACTION NAME:(Elapsed - 4921.63 sec) 2008-01-19 07:28:06.359
    • MODULE NAME:(PROCESS_CLAIMS: Rows - 24,450,000) 2008-01-19 07:28:06.359
    • SERVICE NAME:(SYS$USERS) 2008-01-19 07:28:06.359
    • SESSION ID:(35.9234) 2008-01-19 07:28:06.359
      *********START PLSQL RUNTIME DUMP************
      ***Got internal error Exception caught in pfrrun() while running PLSQL***
      ***Got ORA-3135 while running PLSQL***
      PACKAGE BODY SNDBX.HMP_LOAD: library unit=b02d7608 line=4640 opcode=164 static link=12011f68 scope=1 FP=1200e028 PC=9b64ca84 Page=23 AP=12011f68 ST=1200e568 DL0=11fde048 GF=11fde3e8 DL1=11fde208 DPF=11fde3d0 DS=9b649c90
  • alert log ---

Wed Jan 02 17:16:13 2008
Errors in file d:\oracle\admin\tiermed\bdump\tiermed_s002_1864.trc: ORA-07445: exception encountered: core dump [ACCESS_VIOLATION] [unable_to_trans_pc] [PC:0x0] [ADDR:0x0] [UNABLE_TO_WRITE] [] Wed Jan 02 17:16:58 2008
found dead shared server 'S002', pid = (110, 1) Received on Wed Jan 23 2008 - 17:55:49 CST

Original text of this message