temporary space issue
From: dba cjb <chris.brown_at_providentinsurance.co.uk>
Date: Tue, 8 Feb 2011 06:16:32 -0800 (PST)
Message-ID: <3a19d69e-36cd-48d7-a68f-32846f863643_at_k38g2000vbn.googlegroups.com>
Oracle 10.2.0.4 enterprise windows 2003 standard
Mon Feb 07 14:00:53 2011
Errors in file d:\oracle\product\10.2.0\admin\lvyesmi\bdump \lvyesmi_j000_568.trc:
ORA-00600: internal error code, arguments: [kglhdgn_1], [0x7FF84871250], [18446744071639766840], [4], [], [], [], []
Date: Tue, 8 Feb 2011 06:16:32 -0800 (PST)
Message-ID: <3a19d69e-36cd-48d7-a68f-32846f863643_at_k38g2000vbn.googlegroups.com>
Oracle 10.2.0.4 enterprise windows 2003 standard
temp space is 3 * 64gig v$tempfiles in ts LOCALTEMP
Got the following errors yesterday
Mon Feb 07 14:00:26 2011
ORA-1652: unable to extend temp segment by 64 in
tablespace LOCALTEMP
Mon Feb 07 14:00:53 2011
Errors in file d:\oracle\product\10.2.0\admin\lvyesmi\bdump \lvyesmi_j000_568.trc:
ORA-00600: internal error code, arguments: [kglhdgn_1], [0x7FF84871250], [18446744071639766840], [4], [], [], [], []
What I know
temp resource filling up caused database to be unavailable
Known unknowns
Is there a way I can get details of users/query/temp useage at time of crash so that I can say eg Mr x ran a select from tab which used 1.5gig & was trying to grab more space
I am hoping AWR may hold key to who was using temp at time of the crash..thus giving a more meaningful explanation to the customer of the cause and potential solutions
regards
Chris B
Received on Tue Feb 08 2011 - 08:16:32 CST