Oracle service terminated unexpectedly -
Good Morning everyone,
I came in this morning and encountered our production database has crashed. We are running Oracle 10G 10.2.0.1 on Windows 2003 R2 Server.
The OS system log just reports the service terminated unexpectedly. With no other information in the lower data box.
Looking in the alert log points to this trace file 3 times and ends.
Tue Feb 03 07:15:53 2009
Errors in file c:\oracle\admin\ptmn\udump\ptmn_ora_2980.trc:
ORA-00600: internal error code, arguments: [kssadpm: null parent], [], [], [], [], [], [], []
ORA-07445: exception encountered: core dump [ACCESS_VIOLATION] [unable_to_trans_pc] [PC:0x7FF773113D4] [ADDR:0x0] [UNABLE_TO_WRITE] []
This is what I have in each trace file.
Dump file c:\oracle\admin\ptmn\udump\ptmn_ora_2980.trc
Tue Feb 03 07:15:52 2009
ORACLE V10.2.0.1.0 - 64bit Production vsnsta=0
vsnsql=14 vsnxtr=3
Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - 64bit Production
With the Partitioning, OLAP and Data Mining options
Windows Server 2003 Version V5.2 Service Pack 2
CPU : 8 - type 8664, 2 Physical Cores
Process Affinity : 0x0000000000000000
Memory (Avail/Total): Ph:20525M/32767M, Ph+PgF:20903M/33873M
Instance name: ptmn
Redo thread mounted by this instance: 1
Oracle process number: 230
Windows thread id: 2980, image: ORACLE.EXE (SHAD)
*** SERVICE NAME:(ptmn.world) 2009-02-03 07:15:52.923
*** SESSION ID:(1329.1631) 2009-02-03 07:15:52.923
*** 2009-02-03 07:15:52.923
ksedmp: internal or fatal error
ORA-07445: exception encountered: core dump [ACCESS_VIOLATION] [unable_to_trans_pc] [PC:0x7FF773113D4] [ADDR:0x0] [UNABLE_TO_WRITE] []
Current SQL statement for this session:
ALTER SESSION SET CURRENT_SCHEMA = PROD
----- Call Stack Trace -----
After calling around a bit I discovered that a developer in an outter office ran a massive select query against the database.
He said it he ran it once it failed, twice it failed, and a 3rd time it failed. According the the alert log, after this 3rd time the
database crashed.
All I'm wanting to know is why did it crash, did the developer use all the os/oracle resources doing this? Any insight would be much appreciated.
To prevent this from happening again he's been restricted to TEST database resources only :)
Thank you all for your time and service :)
Edited by: Steve Baker on Feb 3, 2009 6:37 AM
Edited by: Steve Baker on Feb 3, 2009 6:38 AM