Alert log filtering examples

Hello.
Following the Oracle Note Monitoring 10g Database Alert Log Errors in Enterprise Manager [ID 976982.1], I am trying to include some exceptions in the alert log filtering tool but I was looking for more examples. Does anyone have any?
Oracle Enterprise Manager 10g Release 5 Grid Control 10.2.0.5.0

For example, if I want to filter out any 0600 errors that contain the qctVCO:csform argument, would this be appropriate?
.*ORA-0*(54|1142|1146)\D.*|.*ORA-00600:.*\[qctVCO:csform][^\]]*\].*
Do we need to pipe for each successive ORA error, as above?
Thanks,

Similar Messages

ORA-01403: no data found in alert.log

Dear All,
I am getting ORA-01403: no data found in alert.log.Could you pls help me out what could be reasons behind it..Due to this i m getting loads of alerts.Pls suggest.
Thanks

ORA-01403 No Data Found
Typically, an ORA-01403 error occurs when an apply process tries to update an existing row and the OLD_VALUES in the row LCR do not match the current values at the destination database.
Typically, one of the following conditions causes this error:
Supplemental logging is not specified for columns that require supplemental logging at the source database. In this case, LCRs from the source database might not contain values for key columns. You can use a DML handler to modify the LCR so that it contains the necessary supplemental data. See "Using a DML Handler to Correct Error Transactions". Also, specify the necessary supplemental logging at the source database to prevent future errors.
There is a problem with the primary key in the table for which an LCR is applying a change. In this case, make sure the primary key is enabled by querying the DBA_CONSTRAINTS data dictionary view. If no primary key exists for the table, or if the target table has a different primary key than the source table, then specify substitute key columns using the SET_KEY_COLUMNS procedure in the DBMS_APPLY_ADM package. You also might encounter error ORA-23416 if a table being applied does not have a primary key. After you make these changes, you can reexecute the error transaction.
The transaction being applied depends on another transaction which has not yet executed. For example, if a transaction tries to update an employee with an employee_id of 300, but the row for this employee has not yet been inserted into the employees table, then the update fails. In this case, execute the transaction on which the error transaction depends. Then, reexecute the error transaction.
There is a data mismatch between a row LCR and the table for which the LCR is applying a change. Make sure row data in the table at the destination database matches the row data in the LCR. When you are checking for differences in the data, if there are any DATE columns in the shared table, then make sure your query shows the hours, minutes, and seconds. If there is a mismatch, then you can use a DML handler to modify an LCR so that it matches the table. See "Using a DML Handler to Correct Error Transactions".
Alternatively, you can update the current values in the row so that the row LCR can be applied successfully. If changes to the row are captured by a capture process at the destination database, then you probably do not want to replicate this manual change to destination databases. In this case, complete the following steps:
Set a tag in the session that corrects the row. Make sure you set the tag to a value that prevents the manual change from being replicated. For example, the tag can prevent the change from being captured by a capture process.
EXEC DBMS_STREAMS.SET_TAG(tag => HEXTORAW('17'));
In some environments, you might need to set the tag to a different value.
Update the row in the table so that the data matches the old values in the LCR.
Reexecute the error or reexecute all errors. To reexecute an error, run the EXECUTE_ERROR procedure in the DBMS_APPLY_ADM package, and specify the transaction identifier for the transaction that caused the error. For example:
EXEC DBMS_APPLY_ADM.EXECUTE_ERROR(local_transaction_id => '5.4.312');
Or, execute all errors for the apply process by running the EXECUTE_ALL_ERRORS procedure:
EXEC DBMS_APPLY_ADM.EXECUTE_ALL_ERRORS(apply_name => 'APPLY');
If you are going to make other changes in the current session that you want to replicate destination databases, then reset the tag for the session to an appropriate value, as in the following example:
EXEC DBMS_STREAMS.SET_TAG(tag => NULL);
In some environments, you might need to set the tag to a value other than NULL.

Not clearable : 1 distinct types of ORA- errors have been found in the alert log.

( Correct me if I'm wrong.)
What could be the reason for the fact that the event "1 distinct types of ORA- errors have been found in the alert log." is not clearable?
Even if the problem is solved, the ORA- error will still be in the alert.log.
Therefore the event would eventually only disappear after 7 days.
Doesn't sound very logical to me.

- The event page showing a warning event for "Generic Alert Log Error Status" metric,
- "Generic Alert Log Error Status" event is a statefull metric,
- On each evaluation of the metric defined as 'Statefull', the Cloud Control Agent recalculates the severity,
- This means, EM Agent scans the alert log for ORA errors, "Generic Alert Log Error Status" will return the number of ORA error found,
- Whenever the returned number is grater than the assigned thresholds of "Generic Alert Log Error Status", an alert is raised on EM console,
- On the next scan of alert log file, this alert will be cleared ONLY if the collected value is less than the assigned threshold,
- By checking your system, the warning threshold of "Generic Alert Log Error Status" is 0, so whenever a single ORA error is found in alert log, a warning event will be raised and you will not be able to clear it manually as this is a stateful metric.
There are three cases where this alert can be cleared:
1. The agent found 0 ORA errors in Alert log, then the alert will be cleared automatically
2. Manual clear: By disabling/enabling the metric
3. Manual clear and further not receiving similar alerts frequently: By assigning higher thresholds values
So, I suggest to disable the metric, then, enable it after some time as follows as follows:
- Go to the problematic database home page >> open the 'Oracle Database' drop-down menu >> 'Monitoring' >> 'Metric and Collection Settings',
- Choose 'All metrics' from the 'View' drop-down list >> search for the 'Generic Alert Log Error Status' metric,
- Click the pencil icon under 'Edit' column opposite to the above metric >> remove the Warning Threshold (make it empty) >> 'Continue' >> 'OK'.
- Wait for the next collection schedule in order for the warning events to be cleared, then, enable the metric again with the same steps (setting Warning Threshold=0).
References:
Note 604385.1 Receiving "Clear" Notifications Unexpectedly for 'Generic Alert Log Error Status' Metric
Note 733784.1 What are Statefull and Stateless Metrics in Enterprise Manager - Explanation and Example
HTH
Mani

Alert log monitor help

Hello,
I am very new to shell scripting. Our DB is 10g on AIX. And i wanted to setup something that will monitor my alertlog and send me e-mail out. And i found this online. But have very little knowledge on cronjob. I can set one up. But this script dont tell what goes here. Here is the script that i found online. So if anyone could give me what goes where i would be thankfull. it does says put the check_alert.awk someplace. But is that where the cron comes in place. i mean do i schedule check_alert.awk in my cronjob ??? Just wanted to know what parts goes where and how to set this up the right way so i get e-mail alert for my alert log. a step - step process would be good. Thanks
UNIX shell script to monitor and email errors found in the alert log. Is ran as the oracle OS owner. Make sure you change the "emailaddresshere" entries to the email you want and put the check_alert.awk someplace. I have chosen $HOME for this example, in real life I put it on as mounted directory on the NAS.
if test $# -lt 1
then
echo You must pass a SID
exit
fi
# ensure environment variables set
#set your environment here
export ORACLE_SID=$1
export ORACLE_HOME=/home/oracle/orahome
export MACHINE=`hostname`
export PATH=$ORACLE_HOME/bin:$PATH
# check if the database is running, if not exit
ckdb ${ORACLE_SID} -s
if [ "$?" -ne 0 ]
then
echo " $ORACLE_SID is not running!!!"
echo "${ORACLE_SID is not running!" | mailx -m -s "Oracle sid ${ORACLE_SID} is not running!" "
|emailaddresshere|"
exit 1
fi;
#Search the alert log, and email all of the errors
#move the alert_log to a backup copy
#cat the existing alert_log onto the backup copy
#oracle 8 or higher DB's only.
sqlplus '/ as sysdba' << EOF > /tmp/${ORACLE_SID}_monitor_temp.txt
column xxxx format a10
column value format a80
set lines 132
SELECT 'xxxx' ,value FROM v\$parameter WHERE name = 'background_dump_dest'
exit
EOF
cat /tmp/${ORACLE_SID}_monitor_temp.txt | awk '$1 ~ /xxxx/ {print $2}' > /tmp/${ORACLE_SID}_monitor_location.txt
read ALERT_DIR < /tmp/${ORACLE_SID}_monitor_location.txt
ORIG_ALERT_LOG=${ALERT_DIR}/alert_${ORACLE_SID}.log
NEW_ALERT_LOG=${ORIG_ALERT_LOG}.monitored
TEMP_ALERT_LOG=${ORIG_ALERT_LOG}.temp
cat ${ORIG_ALERT_LOG} | awk -f $HOME/check_alert.awk > /tmp/${ORACLE_SID}_check_monitor_log.log
rm /tmp/${ORACLE_SID}_monitor_temp.txt 2>/dev/null
if [ -s /tmp/${ORACLE_SID}_check_monitor_log.log ]
then
echo "Found errors in sid ${ORACLE_SID}, mailed errors"
echo "The following errors were found in the alert log for ${ORACLE_SID}" > /tmp/${ORACLE_SID}_check_monitor_log.mail
echo "Alert log was copied into ${NEW_ALERT_LOG}" >> /tmp/${ORACLE_SID}_check_monitor_log.mail
echo " "
date >> /tmp/${ORACLE_SID}_check_monitor_log.mail
echo "--------------------------------------------------------------">>/tmp/${ORACLE_SID}_check_monitor_log.mail
echo " "
echo " " >> /tmp/${ORACLE_SID}_check_monitor_log.mail
echo " " >> /tmp/${ORACLE_SID}_check_monitor_log.mail
cat /tmp/${ORACLE_SID}_check_monitor_log.log >> /tmp/${ORACLE_SID}_check_monitor_log.mail
cat /tmp/${ORACLE_SID}_check_monitor_log.mail | mailx -m -s "on ${MACHINE}, MONITOR of Alert Log for ${ORACLE_SID} found errors" "
|emailaddresshere|"
mv ${ORIG_ALERT_LOG} ${TEMP_ALERT_LOG}
cat ${TEMP_ALERT_LOG} >> ${NEW_ALERT_LOG}
touch ${ORIG_ALERT_LOG}
rm /tmp/${ORACLE_SID}_monitor_temp.txt 2> /dev/null
rm /tmp/${ORACLE_SID}_check_monitor_log.log
rm /tmp/${ORACLE_SID}_check_monitor_log.mail
exit
fi;
rm /tmp/${ORACLE_SID}_check_monitor_log.log > /dev/null
rm /tmp/${ORACLE_SID}_monitor_location.txt > /dev/null
The referenced awk script (check_alert.awk). You can modify it as needed to add or remove things you wish to look for. The ERROR_AUDIT is a custom entry that a trigger on DB error writes in our environment.
$0 ~ /Errors in file/ {print $0}
$0 ~ /PMON: terminating instance due to error 600/ {print $0}
$0 ~ /Started recovery/{print $0}
$0 ~ /Archival required/{print $0}
$0 ~ /Instance terminated/ {print $0}
$0 ~ /Checkpoint not complete/ {print $0}
$1 ~ /ORA-/ { print $0; flag=1 }
$0 !~ /ORA-/ {if (flag==1){print $0; flag=0;print " "} }
$0 ~ /ERROR_AUDIT/ {print $0}
I simply put this script into cron to run every 5 minutes passing the SID of the DB I want to monitor.

I have a PERL script that I wrote that does exactly what you want and I'll be glad to share that with you along with the CRON entries.
The script runs opens the current alert_log and searches for key phrases and send e-mail if it finds anything. It then sleeps for 60 sec, wakes up and reads from were it left off to the bottom of the file, searching again and then sleeping. The only down side is it keeps a file handle open on the alert_log, so you have to kill this processes if you want to rename or delete the alert_log.
My email in my profile is not hidden.
Tom

Thread 1 cannot allocate new log, sequence in Alert log

Could someone help, I am getting the below message in my alert log
System: AIX6.1 - Oracle 11r2
GROUP#     THREAD#     MEMBER                                  ARCHIVED     STATUS             MB
1     1     +DATA01/mydb/redolog_group1_member1     NO         INACTIVE             1536
1     1     +DATA01/mydb/redolog_group1_member2     NO         INACTIVE             1536
2     1     +DATA01/mydb/redolog_group2_member2     NO         CURRENT          1536
2     1     +DATA01/mydb/redolog_group2_member1     NO         CURRENT          1536
3     1     +DATA01/mydb/redolog_group3_member2     NO         INACTIVE             1536
3     1     +DATA01/mydb/redolog_group3_member1     NO         INACTIVE             1536
Tue Jul 10 18:37:48 2012
Thread 1 advanced to log sequence 28831 (LGWR switch)
Current log# 1 seq# 28831 mem# 0: +DATA01/mydb/redolog_group1_member1
Current log# 1 seq# 28831 mem# 1: +DATA01/mydb/redolog_group1_member2
Tue Jul 10 19:12:01 2012
Thread 1 advanced to log sequence 28832 (LGWR switch)
Current log# 2 seq# 28832 mem# 0: +DATA01/mydb/redolog_group2_member1
Current log# 2 seq# 28832 mem# 1: +DATA01/mydb/redolog_group2_member2
Tue Jul 10 19:39:00 2012
Thread 1 cannot allocate new log, sequence 28833
Private strand flush not complete
Tue Jul 10 19:39:18 2012
Current log# 2 seq# 28832 mem# 0: +DATA01/mydb/redolog_group2_member1
Current log# 2 seq# 28832 mem# 1: +DATA01/mydb/redolog_group2_member2
Tue Jul 10 19:41:21 2012
Thread 1 advanced to log sequence 28833 (LGWR switch)
Current log# 3 seq# 28833 mem# 0: +DATA01/mydb/redolog_group3_member1
Current log# 3 seq# 28833 mem# 1: +DATA01/mydb/redolog_group3_member2
Tue Jul 10 20:15:28 2012
Thread 1 cannot allocate new log, sequence 28834
Private strand flush not complete
Current log# 3 seq# 28833 mem# 0: +DATA01/mydb/redolog_group3_member1
Current log# 3 seq# 28833 mem# 1: +DATA01/mydb/redolog_group3_member2
Tue Jul 10 20:16:21 2012Could an increase on the redo log file sizes solve this problem? Unfortunately I do not have a test platform, where I could have tested this.

mseberg wrote:
It just a warning. I would read these two notes:
I suspect the OP is more worried about the apparent two minute gap between the "cannot switch" and the "advanced" at     19:39:18 and 19:41:12 respectively. Did the switch really have to wait for that two minutes, or is this a spurious threat caused by an anomaly in the writing of the alert log.
As a cross check, I would examine v$event_histogram (or an AWR/Statspack for the interval) for time spent in the event "log file switch (private strand flush incomplete)". In prinicple I wouldn't expect to see waits longer than a few (less than 10) milliseconds; if the histogram shows long waits consistent with the alert log reports than I'd contact Oracle because something odd is happening.
(Footnote - it's possible that the event times out after a limited interval, log file sync used to time out after 1 second and has recently changed to something shorter and adjustable, so 2 seconds may (for example) appear as 20 x 0.1 seconds.)
Regards
Jonathan Lewis

Thread 1 cannot allocate new log -- from alert log

in my alert log file, I have noticed occasionally that this message was showing out during the business hour (8 am ~ 8 pm). Not often , maybe 3 or 4 times, but there are more during the midnight when system run some administration process such as KGL object name :SELECT /*+rule*/ SYS_XMLGEN(VALUE(KU$), XMLFORMAT.createFormat2('VIEW_T', '7')), KU$.OBJ_NUM ,K
U$.SCHEMA_OBJ.NAME ,KU$.SCHEMA_OBJ.NAME ,'VIEW' ,KU$.SCHEMA_OBJ.OWNER_NAME FROM SYS.KU$_VIEW_VIEW KU$ WHERE KU$
.OBJ_NUM IN (SELECT * FROM TABLE(DBMS_METADATA.FETCH_OBJNUMS(200001)))
. My question is : Do I have to add another redo log file to system? and how much is proper?
I also noticed there where message of "Memory Notification: Library Cache Object loaded into SGA
Heap size 2829K exceeds notification threshold (2048K)" during that hours. Appreciate any advice. my system is 10g r2 on AIX 5.3 L.

The "Thread cannot allocate new log" occurs more often off the regular hours due to system run process. It seems more regular occurring at evry 20 minutes. By OEM, I noticed thate there some system processes run at 2 am, 8 am, 2 pm, 8pm. for examples
1) EMD_MAINTENANCE.EXECUTE_EM_DBMS_JOB_PROCS();
2) MGMT_ADMIN_DATA.EVALUATE_MGMT_METRICS;
3) SELECT /*+ USE_HASH(f a) */ SUM(NVL(F.BYTES - NVL(A.BYTES, 0), 0)/1024/1024), SUM(NVL(F.BYTES, 0)/1024/1024) FROM (SELECT DISTINCT TABLESPACE_NAME FROM USER_TABLES) U, (SELECT TABLESPACE_NAME, SUM(BYTES) BYTES FROM DBA_DATA_FILES GROUP BY TABLESPACE_NAME) F, (SELECT TABLESPACE_NAME, SUM(BYTES) BYTES FROM DBA_FREE_SPACE GROUP BY TABLESPACE_NAME) A WHERE A.TABLESPACE_NAME = U.TABLESPACE_NAME AND F.T...
I wonder why they are necessary? or I have to ad one more redo log.

At what point oracle write "Checkpoint not complete" in alert log ?

DB version: 10.2.0.4/RHEL 5.8
During a batch run, we encountered lots of 'Checkpoint not complete' errors in alert log.
Later we discovered that ORLs were sized only 50mb and this DB had only 3 redo log group. Since this is the potential cause, we are going create at least 10 Redo log groups and increase Redo log size to 500MB.
But , I want to know what exactly causes oracle to write "Checkpoint not complete" in alert log ?
For the purpose of this discussion, I am assuming we have only 1 ORL per redo log group. Is my below assumption correct ?
ORL1
|----------------> ORL1 file got full, so, LGWR starts writing to ORL2 file. Checkpoint occurs at log switch
|                    DBWR writes modified blocks associated with the redo entries in ORL1 to datafiles
|
V
ORL2
|----------------> ORL2 file got full, LGWR wants to start writing to ORL3 file. Checkpoint is initiated at log switch.
|                    But checkpoint can't be finished due to unknowN reasons
|
V
ORL3
|---------------->

Your assumption is only partly right.
I would illustrate it like
ORL1
|
|----------------> ORL1 file got full, so, LGWR starts writing to ORL2 file. Checkpoint occurs at log switch
|                    DBWR starts writing modified blocks associated with the redo entries in ORL1 to datafiles
|
V
ORL2
|----------------> ORL2 file got full, LGWR starts writing to ORL3 file.
|                    Checkpoint for ORL2 is initiated at log switch.
|
V
ORL3
|
|----------------> ORL3 file (the last member) also got full very quickly . LGWR wants to start the 'new cycle' by
                    writing (Reusing) to ORL1. But the checkpoint intiated by the log switch of ORL1 from the previous cycle is
                    not complete yet !! .
Basically you get this error when LGWR attempts to reuse an online redo log file (ORL1 in the above example) and finds that it cannot.
This is because the remaining ORL files (ORL2 and ORL3) got fully written before DB writer finished checkpointing the modified blocks associated with ORL1 yet.
Until the checkpoint of ORL1 is complete, the DB effectively hangs and user sessions have to wait until LGWR can safely reuse ORL1
Yes a larger redo log size of 10 groups can help. But make sure the I/O subsytem where ORLs are stored has no latency issues.

How to check particular error in alert log file

Hi all,
How to check particular error in alert log file,for supose if i get error in batabase yesterday 4 pm & today i want to check alert log file to get basic idea..it might be a big file so how to check that particular error..
Thanks & regards,
Eswar..

What's your oracle version?
If you are in 11g you can use adrci tool
1- set homes diag/rdbms/orawiss/ORAWISS/ : the rdbms home
2- show alert -P "MESSAGE_TEXT LIKE '%ORA-%'" -term : to find all the ORA-% errors in the alert file
3- show alert -P "MESSAGE_TEXT LIKE '%ORA-%' and originating_timestamp > systimestamp-51 " -term : to find all the ORA-% errors in the alert file during the last 51 days,
4- show alert -P "MESSAGE_TEXT LIKE '%ORA-%' and originating_timestamp > systimestamp-1/24 " -term : to find all the ORA-% errors in the alert file during the last hour,
5- show alert -P "MESSAGE_TEXT LIKE '%ORA-12012%' and originating_timestamp > systimestamp-1/24 " -term : to find the particular ORA-12012 error in the alert file during the last hour,
Example:
[oracle@wissem wissem]$ adrci
ADRCI: Release 11.2.0.1.0 - Production on Wed May 4 10:24:54 2011
Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved.
ADR base = "/home/oracle/app/oracle"
adrci> set homes diag/rdbms/orawiss/ORAWISS/
adrci> show alert -P "MESSAGE_TEXT LIKE '%ORA-'" -term
ADR Home = /home/oracle/app/oracle/diag/rdbms/orawiss/ORAWISS:
adrci> show alert -P "MESSAGE_TEXT LIKE '%ORA-%'" -term
ADR Home = /home/oracle/app/oracle/diag/rdbms/orawiss/ORAWISS:
2010-12-11 19:45:41.289000 +01:00
ORA-1109 signalled during: ALTER DATABASE CLOSE NORMAL...
ORA-01547: warning: RECOVER succeeded but OPEN RESETLOGS would get error below
ORA-01152: file 1 was not restored from a sufficiently old backup
ORA-01110: data file 1: '/home/oracle/app/oracle/oradata/ORAWISS/system01.dbf'
ORA-1547 signalled during: ALTER DATABASE RECOVER database until time '2011-01-21:10:48:00' ...
Errors in file /home/oracle/app/oracle/diag/rdbms/orawiss/ORAWISS/trace/ORAWISS_j000_5692.trc:
ORA-12012: error on auto execute of job 29
ORA-01435: user does not exist
2011-03-15 11:39:37.571000 +01:00
opiodr aborting process unknown ospid (31042) as a result of ORA-609
2011-03-15 12:04:15.111000 +01:00
opiodr aborting process unknown ospid (3509) as a result of ORA-609
adrci>
adrci> show alert -P "MESSAGE_TEXT LIKE '%ORA-%' and originating_timestamp > systimestamp-51 " -term
ADR Home = /home/oracle/app/oracle/diag/rdbms/orawiss/ORAWISS:
2011-03-15 10:19:45.316000 +01:00
Errors in file /home/oracle/app/oracle/diag/rdbms/orawiss/ORAWISS/trace/ORAWISS_j006_5536.trc:
ORA-12012: error on auto execute of job 26
ORA-01435: user does not exist
Errors in file /home/oracle/app/oracle/diag/rdbms/orawiss/ORAWISS/trace/ORAWISS_j000_5692.trc:
ORA-12012: error on auto execute of job 29
ORA-01435: user does not exist
2011-03-15 11:39:37.571000 +01:00
opiodr aborting process unknown ospid (31042) as a result of ORA-609
2011-03-15 12:04:15.111000 +01:00
opiodr aborting process unknown ospid (3509) as a result of ORA-609
adrci>

Job number from alert log file to information

Hello!
I have a question about job numbers in alert log file. Today one of our Oracle 10g R2 [10.2.0.4] RAC nodes crashed. After examining alert log file for one of the nodes I saw a lot of messages like:
Tue Jul 26 11:52:43 2011
Errors in file /u01/app/oracle/admin/zeme/bdump/zeme2_j002_28952.trc:
ORA-12012: error on auto execute of job *20627358*
ORA-12705: Cannot access NLS data files or invalid environment specified
Tue Jul 26 11:52:43 2011
Errors in file /u01/app/oracle/admin/zeme/bdump/zeme2_j001_11018.trc:
ORA-12012: error on auto execute of job *20627357*
ORA-12705: Cannot access NLS data files or invalid environment specified
Tue Jul 26 11:52:43 2011
Errors in file /u01/app/oracle/admin/zeme/bdump/zeme2_j000_9684.trc:
ORA-12012: error on auto execute of job *20627342*
ORA-12705: Cannot access NLS data files or invalid environment specified
After examining trc files I have found no further information about error except session ids.
My question is: how to find what job caused these messages to appear in alert log file.
How do I map number in alert log file to some "real" information (owner, statement executed, schedule)?
Marx.

Sorry for the delay
Try this to find the job :
select job, what from dba_jobs ;
How do I find NLS_LANG version?SQL> show parameter NLS_LANG
Do you mean ALTER SESSION inside a job?I meant anywhere, but your question is better.
ORA-12705 - Common Reasons and How to Resolve Them [ID 158654.1]
If OS is Windows lookout for NLS_LANG=NA in the registry
Is it possible you are doing this somewhere ?
ALTER SESSION SET NLS_DATE_FORMAT = 'RRRR-MM-DD\"T\"HH24:MI:SS';NLS database settings are superseded by NLS instance settings
SELECT * from NLS_SESSION_PARAMETERS;
These are the settings used for the current SQL session.
NLS_LANG could be set in a profile for example.
NLS_LANG=_AMERICA.WE8ISO8859P1 ( correct )
NLS_LANG=AMERICA.WE8ISO8859P1 ( Incorrect )
you need to set the "_" as separator.
Windows
set NLS_LANG=AMERICAN_AMERICA.WE8ISO8859P1
Unix
export NLS_LANG=AMERICAN_AMERICA.WE8ISO8859P1
mseberg
Edited by: mseberg on Jul 28, 2011 3:51 PM
Edited by: mseberg on Jul 29, 2011 4:05 AM

Alert Log Content

Hello!!!
I want to see the alert log content for a specific date. But whenever I select a date window (date from.... date until) using the calendar utility there is none to be displayed!!!!
Without search criteria the utility displays the last 10000 lines of the alert log content.
Why this happens????
Simon

Hi ,
When I say 'a window (date from... date to)' I mean a date period for example 01/01/2006 until 03/01/2006.
On Enterprise Manager Console 10g there is the capability to select this date period using the built-in calendar (on right of each text item where I can write down the dates (begin/end date)).
The answer you gave me means that I cannot search the log file content giving specific criteria , as I want?
Thanks for your help !!!
Simon

Settinggs for Generic Alert Log Metric, OEM GC 10204

OS: AIX Grid Control Version: 10204
Agent:10204, Repository DB:10204
This is the setting on a 9208 DB I was testing for Generic Alert Log Error Metric (I had to change [ (square bracket with { curly brackets on the post).
Warning Metric: ORA-*
Critical Metric: ORA-0*(60{0-9}|1157|1562|1628|1650|1653|1654|1655|1656|4031|7445|16014|29740){^0-9}
The Warning metric (ORA-*) is set to a catch all else if not found in the critical metric. Not sure if there's an order the warning vs critical is read, but so far this has worked for our purposes.
In GC 10204, we can add an ORA- error to the 'Alert Log Filter Expresion' and this would prevent a metric from being sent out if matched, so if there's a particular ORA-0600 error we do not want to be sent out as critical, we could add it to to the filter to be ignored. In the Advance Setting GC example , we want to ignore "ORA-00600: internal error code, arguments {qerfxFetch_01}, {}, {}, {}, {}, {}, {}" , so we would added it to the filter as ".*ORA-00600:.*\{qerfxFetch{^\}}*\}.*"
My question - Instead of ignoring the error "ORA-00600: internal error code, arguments {qerfxFetch_01}, {}, {}, {}, {}, {}, {}", I want to move it to be a Warning, can anyone suggest any way of doing this? I've tried adding to the Warning metric {.*ORA-00600:.*\{qerfxFetch{^\}}*\}.*}|ORA-*, but this does not work, as the alert still comes out as a critical.
All suggestions are welcome.

Hi,
You did not mention database version. in 11g, the generic alert log metric will not work. For 10g, you can set this from metrics and policy settings page bu setting warning and critical thresholds for this metric to "ORA-*". And then create a notification rule for this metric.
For 11g, you need to check MOS note 949858.1
Salman

Alert.log showing different time stamps

SR 6582667.992
AIX5L 5.3
The alert,log shows the following:
Thu Oct 18 15:16:55 2007
ALTER DATABASE CLOSE NORMAL
Thu Oct 18 19:16:55 2007 ----------------------------> Time changed
SMON: disabling tx recovery
SMON: disabling cache recovery
Thu Oct 18 19:16:55 2007
Shutting down archive processes
Archiving is disabled
Thu Oct 18 19:17:00 2007
ARCH shutting down
ARC1: Archival stopped
Thu Oct 18 19:17:05 2007
ARC0: Becoming the 'no FAL' ARCH
ARC0: Becoming the 'no SRL' ARCH
ARC0: Archiving disabled
ARCH shutting down
ARC0: Archival stopped
Thu Oct 18 19:17:07 2007
Thread 1 closed at log sequence 100
Successful close of redo thread 1
Thu Oct 18 15:17:07 2007 -------------------------------------------> Time changed back
Completed: ALTER DATABASE CLOSE NORMAL
Thu Oct 18 15:17:07 2007
ALTER DATABASE DISMOUNT
Completed: ALTER DATABASE DISMOUNT
ARCH: Archival disabled due to shutdown: 1089
Shutting down archive processes
Archiving is disabled
Archive process shutdown avoided: 0 active
ARCH: Archival disabled due to shutdown: 1089
Shutting down archive processes
Archiving is disabled
Archive process shutdown avoided: 0 active
Thu Oct 18 15:17:12 2007
Any Idea why this is happening.
I have obtain the OS script that does the shutdown an startup, it is in the SR.
Thank for the help.
Loren

Hi,
Some one or some process is updating date on your server. Following is an example:
I started my database and then modified the date and following is the information recorded in the alert log.
QMNC started with pid=20, OS id=3164
Sat Oct 20 00:44:23 2007
Completed: alter database open
Sat Oct 20 00:07:36 2007
Shutting down archive processes
Sat Oct 20 00:07:41 2007This is how I modified time on my PC.
C:\Documents and Settings\momen>time
The current time is: 0:45:07.36
Enter the new time: 00:05:00Regards

ST04 alert log

Dear Techies
I am running SAP 4.6 B with oracle 10g on solaries
Recently i have upgraded the database from 9.2 to 10g since then iam unable to view Alert log from ST04.
I am getting ORA-1722 error with ABAP dump DBIF_DSQL2_SQL_ERROR
Thanks
Haroon

Hi,
Unfortunately, there is no workaround. 10g changes a lot of things (for example more columns in v$session) and ST04.
Some things were corrected for old versions but not everything.
As I mentioned before, 10g was not supported for releases < 4.6C. From application point of view thre will not be problems, but monitoring tools are expected to have "issues". I have only seen 10g in low versions as a middle step for an upgrade.

Unable to open alert log file

Hi Guys
I am using oracle 10.2.0.4.0 on windows 2003 64 . I am unable to open my alert log file. My alert log file opens in a notepad. I get the following error:
'C:\oracle\admin\efint\bdump\alert_efint.log file is too large for notepad. Use another editor to edit the file.'
I tried opening it with wordpad. It gives back 'Failed to open document error.'
My database is working but it wont let me open my alert file. I was able to open it yesterday but not today.
Any help is appreciated
Thanks in advance....
regards

Hi,
I recommend that you download tail for windows:
http://www.x64bitdownload.com/downloads/t-64-bit-tail4win-download-ljrvpdfr.html
This is the description:
Tail4Win is a real-time log monitor and viewer, is a windows port of the UNIX 'tail -f' command, it can be used to view the end of a growing file. By using Tail4Win system administrator can monitor log files of server applications in real-time, e.g. Apache's error.log and access.log, or IIS, Tomcat, Resin log files. And programmer can monitor application traces easy and quickly. Tail4win can display the last part of a large file quickly without loading the entire file. And it is a file viewer only, it makes no changes to log files. Main fetures: Monitor changes to files and display the changed lines in realtime. Monitor files of any size quickly, no need to load the entire file. Highlighting and filtering let you focus on important informations. Watch multiple files at same time. Real command line support, just like using Unix/Linux "tail" command. Capture and display OutputDebugString (Windows debugging API) output.
Regards,
Mario Alcaide
http://marioalcaide.wordpress.com

Generic Alert Log Expression Syntax

Can anyone explain or point where I can understand the syntax allowed for expressions for monitoring the alert log? For example :
ORA-0*(600?|7445|4[0-9][0-9][0-9])[^0-9]

Are you asking what 'ORA-0*(600?|7445|4[0-9][0-9][0-9])[^0-9]' means?
If so, its just a perl expression. look on google for searching patterns etc in perl and then change it accordingly to what you want (or not) to search for.
Bazza

Alert log filtering examples

Similar Messages

Maybe you are looking for