| Oracle FAQ | Your Portal to the Oracle Knowledge Grid | |
 |
 | |||
| Oracle FAQ | Your Portal to the Oracle Knowledge Grid | |
|
| |||
Home -> Community -> Mailing Lists -> Oracle-L -> RE: How to interpret Alert.Log & Trace files...
Denmark,
I am not an expert but from everything I have read is that when you get
ORA-00600 errors you should probably open a TAR with Oracle. It may not be
much but why take the chance.
I would be interested in that tuning script that you downloaded. Cound you
send it to me directly or let me know where you downloaded it from?
Thanks,
Dave
-----Original Message-----
Sent: Friday, August 24, 2001 1:53 PM
To: Multiple recipients of list ORACLE-L
Hi DBA's
I'm currently monitoring the Oracle SIDALRT.LOG and *.TRC files in $ORACLE_HOME/RDBMS80/TRACE on our production Oracle 805 database. I've observed the following files being used by Oracle in that directory:
SIDP000.TRC 5MB SIDP001.TRC 5MB SIDP002.TRC 5MB SIDP003.TRC 5MB SIDP004.TRC Current Trace file
Other trace files exist in the directory with the following naming convention: Ora99999.trc
One is generated everytime I run the "BACKUP CONTROLFILE TO TRACE" command. However, I notice that each Ora99999.trc generated with the CONTROLFILE TRACE has other trace dumps in it as well from previous events. For example,
the last CONTROLFILE Trace written (Ora00479.trc) (8 Aug 2001 8:03 AM) has this entry at the beginning:
Dump file e:\orant\rdbms80\trace\ORA00479.TRC
Tue Aug 07 16:38:30 2001
ORACLE V8.0.5.0.0 - Production vsnsta=0
vsnsql=c vsnxtr=3
Windows NT V4.0, OS V5.101, CPU type 586
Oracle8 Enterprise Edition Release 8.0.5.0.0 - Production
PL/SQL Release 8.0.5.0.0 - Production
Windows NT V4.0, OS V5.101, CPU type 586
Instance name: prod
Redo thread mounted by this instance: 1
Oracle process number: 38
pid: 1df
Redo thread mounted by this instance: 1
Oracle process number: 11
pid: 1df
Now to get to my questions.
I'm noticing the following entries in the PRODALRT.LOG.
Below is a paste of the entries logged since this morning:
Completed: alter tablespace SYSTEM end backup
Fri Aug 24 08:03:26 2001
Thread 1 advanced to log sequence 3880
Current log# 2 seq# 3880 mem# 0: E:\ORANT\DATABASE\LOGPROD2.ORA
Thread 1 advanced to log sequence 3881
Current log# 1 seq# 3881 mem# 0: E:\ORANT\DATABASE\LOGPROD1.ORA
Fri Aug 24 08:03:31 2001
alter database backup controlfile to 'CTL1PROD.8am'
Fri Aug 24 08:03:32 2001
Completed: alter database backup controlfile to 'CTL1PROD.8am
Fri Aug 24 08:03:32 2001
alter database backup controlfile to trace
Completed: alter database backup controlfile to trace
Fri Aug 24 09:20:16 2001
Errors in file e:\orant\rdbms80\trace\prodP002.TRC:
ORA-00600: internal error code, arguments: [17176], [0], [], [], [], [], [],
[]
Fri Aug 24 09:20:17 2001
Errors in file e:\orant\rdbms80\trace\prodP003.TRC:
ORA-00600: internal error code, arguments: [17176], [0], [], [], [], [], [],
[]
Fri Aug 24 09:33:48 2001
Thread 1 advanced to log sequence 3882
Current log# 2 seq# 3882 mem# 0: E:\ORANT\DATABASE\LOGPROD2.ORA
Fri Aug 24 09:41:23 2001
Errors in file e:\orant\rdbms80\trace\prodP003.TRC:
ORA-00600: internal error code, arguments: [17176], [0], [], [], [], [], [],
[]
Fri Aug 24 09:41:24 2001
Errors in file e:\orant\rdbms80\trace\prodP002.TRC:
ORA-00600: internal error code, arguments: [17176], [0], [], [], [], [], [],
[]
Fri Aug 24 09:42:21 2001
Errors in file e:\orant\rdbms80\trace\prodP003.TRC:
ORA-00600: internal error code, arguments: [17176], [0], [], [], [], [], [],
[]
Fri Aug 24 09:42:22 2001
Errors in file e:\orant\rdbms80\trace\prodP002.TRC:
ORA-00600: internal error code, arguments: [17176], [0], [], [], [], [], [],
[]
Fri Aug 24 09:42:33 2001
Errors in file e:\orant\rdbms80\trace\prodP003.TRC:
ORA-00600: internal error code, arguments: [17176], [0], [], [], [], [], [],
[]
Fri Aug 24 09:42:34 2001
Errors in file e:\orant\rdbms80\trace\prodP002.TRC:
ORA-00600: internal error code, arguments: [17176], [0], [], [], [], [], [],
[]
Fri Aug 24 09:42:48 2001
Errors in file e:\orant\rdbms80\trace\prodP003.TRC:
ORA-00600: internal error code, arguments: [17176], [0], [], [], [], [], [],
[]
Fri Aug 24 09:42:49 2001
Errors in file e:\orant\rdbms80\trace\prodP002.TRC:
ORA-00600: internal error code, arguments: [17176], [0], [], [], [], [], [],
[]
Fri Aug 24 09:43:07 2001
Errors in file e:\orant\rdbms80\trace\prodP003.TRC:
ORA-00600: internal error code, arguments: [17176], [0], [], [], [], [], [],
[]
Fri Aug 24 09:43:08 2001
Errors in file e:\orant\rdbms80\trace\prodP002.TRC:
ORA-00600: internal error code, arguments: [17176], [0], [], [], [], [], [],
[]
Fri Aug 24 09:56:22 2001
Errors in file e:\orant\rdbms80\trace\prodP001.TRC:
ORA-00600: internal error code, arguments: [17176], [0], [], [], [], [], [],
[]
Fri Aug 24 09:56:22 2001
Errors in file e:\orant\rdbms80\trace\prodP000.TRC:
ORA-00600: internal error code, arguments: [17176], [0], [], [], [], [], [],
[]
Fri Aug 24 09:56:24 2001
Errors in file e:\orant\rdbms80\trace\prodP001.TRC:
ORA-00600: internal error code, arguments: [17176], [0], [], [], [], [], [],
[]
Fri Aug 24 09:56:25 2001
Errors in file e:\orant\rdbms80\trace\prodP000.TRC:
ORA-00600: internal error code, arguments: [17176], [0], [], [], [], [], [],
[]
Fri Aug 24 10:03:41 2001
Errors in file e:\orant\rdbms80\trace\prodP001.TRC:
ORA-00600: internal error code, arguments: [17176], [0], [], [], [], [], [],
[]
Fri Aug 24 10:03:42 2001
Errors in file e:\orant\rdbms80\trace\prodP000.TRC:
ORA-00600: internal error code, arguments: [17176], [0], [], [], [], [], [],
[]
Fri Aug 24 10:32:52 2001
Thread 1 advanced to log sequence 3883
Current log# 1 seq# 3883 mem# 0: E:\ORANT\DATABASE\LOGPROD1.ORA
Fri Aug 24 10:48:19 2001
Errors in file e:\orant\rdbms80\trace\prodP001.TRC:
ORA-00600: internal error code, arguments: [17176], [0], [], [], [], [], [],
[]
Fri Aug 24 10:48:19 2001
Errors in file e:\orant\rdbms80\trace\prodP000.TRC:
ORA-00600: internal error code, arguments: [17176], [0], [], [], [], [], [],
[]
Fri Aug 24 10:49:37 2001
Errors in file e:\orant\rdbms80\trace\prodP001.TRC:
ORA-00600: internal error code, arguments: [17176], [0], [], [], [], [], [],
[]
Fri Aug 24 10:49:37 2001
Errors in file e:\orant\rdbms80\trace\prodP000.TRC:
ORA-00600: internal error code, arguments: [17176], [0], [], [], [], [], [],
[]
Fri Aug 24 10:49:53 2001
Errors in file e:\orant\rdbms80\trace\prodP001.TRC:
ORA-00600: internal error code, arguments: [17176], [0], [], [], [], [], [],
[]
Fri Aug 24 10:49:54 2001
Errors in file e:\orant\rdbms80\trace\prodP000.TRC:
ORA-00600: internal error code, arguments: [17176], [0], [], [], [], [], [],
[]
I'm no expert, but I know I should be concerned about the ORA errors. Before I go barking up the wrong tree, I would appreciate advice, suggestions, explanations from othe DBA's who have experience using the Alert logs and trace files to monitor the Oracle database.
Using a tuning script that I downloaded, I got the follwoing tuning recommendations about tuning our production database:
Current Date and Time: 08/23/2001 15:59:11 Database name: orcl
Measurement Goal Value Action ------------------------------ ------ ----------- ------------------------------------------------- Library cache hit percent >=0.99 1.00 OK Dictionary cache hit percent >=0.90 0.99 OK Buffer cache hit percent >=0.90 0.71 Increase theDB_BLOCK_BUFFERS in INIT.ORA
Sort area hit percent >=0.90 1.00 OK Redo Log space requests =0 17 Increase the LOG_BUFFER in INIT.ORA " Examine Redo Log size " Examine number of Redo Log
groups
-- Current value: log_buffer = 32768 -- Current value: redo log size = 1048576 -- Current value: # of redo log groups = 2 Enqueue waits =0 2 Increase theENQUEUE_RESOURCES in INIT.ORA
Checkpoints not completed <=1 0 OK Rollback contention ratio <=0.01 0.00 OK Redo allocation latch miss (W) <=0.01 0.00 OK Redo allocation latch miss (I) <=0.01 0.00 OK Redo copy latch miss (WTW) <=0.01 0.00 OK Redo copy latch miss (Immed) <=0.01 0.00 OK Freelist contention ratio <=0.01 0.00 OK
I would appreciate advice on changing initialization parameters.
Are there some parameters that can be modified on the fly without cycling
the engine?
How can I find out which ones? The DB_BLOCK_BUFFERS parameter needs some
attention urgently, right?
I am being cautious because changing some parameters can impact others.
I know this is a lot to chew on, but feel free to send me to sites that might provide technical resources. Unfortunately, I don't have access to Metalink.
Thanks in advance,
Denmark Weatherburne
"Knowledge is power, but it is only useful if it is shared!"
-- Please see the official ORACLE-L FAQ: http://www.orafaq.com -- Author: Denmark Weatherburne INET: denmark_weatherburne_at_hotmail.com Fat City Network Services -- (858) 538-5051 FAX: (858) 538-5051 San Diego, California -- Public Internet access / Mailing Lists -------------------------------------------------------------------- To REMOVE yourself from this mailing list, send an E-Mail message to: ListGuru_at_fatcity.com (note EXACT spelling of 'ListGuru') and in the message BODY, include a line containing: UNSUB ORACLE-L (or the name of mailing list you want to be removed from). You may also send the HELP command for other information (like subscribing). -- Please see the official ORACLE-L FAQ: http://www.orafaq.com -- Author: Farnsworth, Dave INET: DFarnsworth_at_Ashleyfurniture.com Fat City Network Services -- (858) 538-5051 FAX: (858) 538-5051 San Diego, California -- Public Internet access / Mailing Lists -------------------------------------------------------------------- To REMOVE yourself from this mailing list, send an E-Mail message to: ListGuru_at_fatcity.com (note EXACT spelling of 'ListGuru') and in the message BODY, include a line containing: UNSUB ORACLE-L (or the name of mailing list you want to be removed from). You may also send the HELP command for other information (like subscribing).Received on Fri Aug 24 2001 - 13:02:40 CDT
 |
 |