• Embed Doc
  • Readcast
  • Collections
  • CommentGo Back
Download
 
How to use LogMiner to locate Archive Logs Flow
R. Wang
Keywords: logminer, STATSPACK, Archive log filesEnvironment:
Oracle 9iR2 and Solaris 5.9
Circumstance:
Without introduction of new jobs, we monitored rapid diskoccupancy in very short period. The circumstance we encountered is that a newarchive log file (18MB) is created every minute. And, the disk occupancy is rapidlyincreased as shown below.-rw-r----- 1 oracle dba 18873856 Jul 24 20:38 PROD_0001_0000045102.arc-rw-r----- 1 oracle dba 18873856 Jul 24 20:39 PROD_0001_0000045103.arc-rw-r----- 1 oracle dba 18873856 Jul 24 20:40 PROD_0001_0000045104.arc-rw-r----- 1 oracle dba 18873856 Jul 24 20:41 PROD_0001_0000045105.arc-rw-r----- 1 oracle dba 18873856 Jul 24 20:41 PROD_0001_0000045106.arc-rw-r----- 1 oracle dba 18873856 Jul 24 20:43 PROD_0001_0000045107.arc-rw-r----- 1 oracle dba 18873856 Jul 24 20:43 PROD_0001_0000045108.arc-rw-r----- 1 oracle dba 18873856 Jul 24 20:45 PROD_0001_0000045109.arc-rw-r----- 1 oracle dba 18873856 Jul 24 20:45 PROD_0001_0000045110.arc-rw-r----- 1 oracle dba 18873856 Jul 24 20:46 PROD_0001_0000045111.arc-rw-r----- 1 oracle dba 18873856 Jul 24 20:47 PROD_0001_0000045112.arc-rw-r----- 1 oracle dba 18873856 Jul 24 20:49 PROD_0001_0000045113.arc-rw-r----- 1 oracle dba 18873856 Jul 24 20:50 PROD_0001_0000045114.arc-rw-r----- 1 oracle dba 18873856 Jul 24 20:51 PROD_0001_0000045115.arc-rw-r----- 1 oracle dba 18873856 Jul 24 20:52 PROD_0001_0000045116.arc-rw-r----- 1 oracle dba 18873856 Jul 24 20:53 PROD_0001_0000045117.arc-rw-r----- 1 oracle dba 18873856 Jul 24 20:54 PROD_0001_0000045118.arc-rw-r----- 1 oracle dba 18873856 Jul 24 20:56 PROD_0001_0000045119.arc-rw-r----- 1 oracle dba 18873856 Jul 24 20:56 PROD_0001_0000045120.arc-rw-r----- 1 oracle dba 18873856 Jul 24 20:57 PROD_0001_0000045121.arc-rw-r----- 1 oracle dba 18873856 Jul 24 20:58 PROD_0001_0000045122.arc-rw-r----- 1 oracle dba 18873856 Jul 24 20:59 PROD_0001_0000045123.arc-rw-r----- 1 oracle dba 18873856 Jul 24 21:00 PROD_0001_0000045124.arc
Steps of Diagnosis1. Checking on Memory, CPU, I/O
With checking on memory, CPU and I/O, we failed to find any abnormalprocess that excessively consumes resource of database and OS.
 
Note:
For reference on “Monitor Oracle Resouce Consumption in Unix”, pleaserefer to the article in “oracle metalink” with Note: 148466.1.
2. Using Logminer to locate targeted archive log files
Then, we would like to look at what does the database do by examiningarchive log files created with Logminer.Before start using Logminer, please make sure of that you
Log in with sys account with sysdba role
Never escape from the current session because the data viewing of logminer will not be available at other sessions.The steps to use Logminer are depicted as following in details.
1) Check init parameter UTL_FILE_DIR 
SQL>show parameter UTL_FILNAME TYPE VALU------------------------------ ----------- -------------------utl_file_dir string /tmp
2) Creates text based file containing data dictionary contents
execute dbms_logmnr_d.build('shwdict.ora','/tmp');
3) Add targeted archive log files to log list
SQL> executedbms_logmnr.add_logfile('/dbPROD/archive/PROD_0001_0000045087.arc',dbms_logmnr.addfile);PL/SQL procedure successfully completed.SQL> executedbms_logmnr.add_logfile('/dbPROD/archive/PROD_0001_0000045088.arc',dbms_logmnr.addfile);PL/SQL procedure successfully completed.SQL> executedbms_logmnr.add_logfile('/dbPROD/archive/PROD_0001_0000045089.arc',dbms_logmnr.addfile);PL/SQL procedure successfully completed.SQL> executedbms_logmnr.add_logfile('/dbPROD/archive/PROD_0001_0000045288.arc',dbms_logmnr.addfile);PL/SQL procedure successfully completed.
 
SQL> executedbms_logmnr.add_logfile('/dbPROD/archive/PROD_0001_0000045289.arc',dbms_logmnr.addfile);PL/SQL procedure successfully completed.SQL> executedbms_logmnr.add_logfile('/dbPROD/archive/PROD_0001_0000045290.arc',dbms_logmnr.addfile);PL/SQL procedure successfully completed.SQL> executedbms_logmnr.add_logfile('/dbPROD/archive/PROD_0001_0000045291.arc',dbms_logmnr.addfile);PL/SQL procedure successfully completed.SQL> executedbms_logmnr.add_logfile('/dbPROD/archive/PROD_0001_0000045297.arc',dbms_logmnr.addfile);PL/SQL procedure successfully completed.SQL> executedbms_logmnr.add_logfile('/dbPROD/archive/PROD_0001_0000045308.arc',dbms_logmnr.addfile);PL/SQL procedure successfully completed.
Note:
In order to track issues happened, we loaded not onlyexcessive archive log files generated every minutes, butthe normal archive log files created in reasonableinterval.And, then go check the archive log files which have beenloaded and available for analyzing.
SQL> select log_id, filename from v$logmnr_logs;LOG_ID FILENAME----------- -------------------------------------------45087 /dbPROD/archive/PROD_0001_0000045087.arc45088 /dbPROD/archive/PROD_0001_0000045088.arc45089 /dbPROD/archive/PROD_0001_0000045089.arc45288 /dbPROD/archive/PROD_0001_0000045288.arc45289 /dbPROD/archive/PROD_0001_0000045289.arc45290 /dbPROD/archive/PROD_0001_0000045290.arc45291 /dbPROD/archive/PROD_0001_0000045291.arc45297 /dbPROD/archive/PROD_0001_0000045297.arc45308 /dbPROD/archive/PROD_0001_0000045308.arc9 rows selected.
4) Alter date format in current session
of 00

Leave a Comment

You must be to leave a comment.
Submit
Characters: ...
You must be to leave a comment.
Submit
Characters: ...