Errors in archiving in alert log

Hi
I have a Oracle 9i database (9.2.0.7) for which I turned on arhivelog mode a week ago. In this db, inthe alert log there are following errors:
ARC1: Evaluating archive log 1 thread 1 sequence 1221
ARC1: Unable to archive log 1 thread 1 sequence 1221
Log actively being archived by another process
ARC1: Evaluating archive log 2 thread 1 sequence 1222
ARC1: Unable to archive log 2 thread 1 sequence 1222
Log actively being archived by another process
and there are no message like 'Completed archiving' because of another issue - there was an error in specifying the log format. The value of log_archive_format was incorrectly set to "DB001_%s_%t_%r.arc" so there is also another trace file which says that:
*** SESSION ID:(9.1) 2009-03-11 08:42:00.023
ORA-00294: invalid archivelog format specifier 'r'
So there are two things: 1) To change the archive log format
2) To deal with the other issue: Unable to archive log 2 thread 1 sequence 1222
Log actively being archived by another process
What is the process to do this? Will be thankful for help. The database is up now.
Thanks
Nirav
Edited by: orausern on May 1, 2009 1:14 AM

orausern wrote:
Thank you for the suggestion, I tried it but it is giving an error like:
ERROR at line 1:
ORA-02095: specified initialization parameter cannot be modified
also the parameter log_archive_format is not system or session modifiable. My concern is that since this error is more than one week old, will it allow me to shut down the db cleanly (when I get the permission to do so) or will there be some issue if i try to shut the db and then restart. so I am not sure how to proceed..
Thanks
NiravI guess you have taken it wrong, this parameter is indeed changeable but the effect of this would come in the next startup only a its a static parameter.
http://download.oracle.com/docs/cd/B10501_01/server.920/a96536/ch195.htm#REFRN10089
So you need to do some thing like this,
alter system set log_archive_format=<your_desired_format> scope=spfile;Do a reboot and the parameter settings would come into effect. Any dba account should be able to change this parameter but for the bounce of the db, you need to have Sysdba privs. This parameter won't effect your startup or shutdown, they should proceed without issues.
HTH
Aman....

Similar Messages

I am geting errors in my database alert log file ora-12012 and ora 44003

Hi all,
I am using oracle 10g ...10.2.0.1.0 and OS is solaris 10.......
i am geting these errors in my database alert log file last two days..i am not geting why it is coming?
ORA-12012: error on auto execute of job 8887
ORA-44003: invalid SQL name
and trace file is i got i am posting here please help any one is aware about this....
System name: SunOS
Node name: obrmzone1
Release: 5.10
Version: Generic_137111-06
Machine: sun4v
Instance name: ------
Redo thread mounted by this instance: 1
Oracle process number: 144
Unix process pid: 26874, image:--------- (J000)
*** ACTION NAME:(AUTO_SPACE_ADVISOR_JOB) 2011-06-10 22:00:49.372
*** MODULE NAME:(DBMS_SCHEDULER) 2011-06-10 22:00:49.372
*** SERVICE NAME:(SYS$USERS) 2011-06-10 22:00:49.372
*** SESSION ID:(110.7114) 2011-06-10 22:00:49.372
*** 2011-06-10 22:00:49.372
ORA-12012: error on auto execute of job 8887
ORA-44003: invalid SQL name
thank you in advance,
Dav

I just google with "ORA-44003: invalid SQL name" and found below link:
http://www.oracle-base.com/articles/10g/dbms_assert_10gR2.php
SIMPLE_SQL_NAME
The SIMPLE_SQL_NAME function checks the input string conforms to the basic characteristics of a simple SQL name:
The first character of the name is alphabetic.
The name only contains alphanumeric characters or the "_", "$", "#"
Quoted names must be enclosed by double quotes and may contain any characters, including quotes provided they are represented by two quotes in a row ("").
The function ignores leading and trailing white spaces are ignored
The length of the input string is not validated.

Need to find the way to get the actual error message in the alert log.

Hi,
I have configured OEM 11G and monitoring target versions are from 9i to 11g. Now my problem is i have defined the metrics for monitoring the alert log contents and OEM is sending alert if there is any error in the alert log but it is not showing the actual error message just it is showing as below.
============================
Target Name=IDMPRD
Target type=Database Instance
Host=oidmprd01.ho.abc.com
Occurred At=Dec 21, 2011 12:05:21 AM GMT+03:00
Message=1 distinct types of ORA- errors have been found in the alert log.
Metric=Generic Alert Log Error Status
Metric value=1
Severity=Warning
Acknowledged=No
Notification Rule Name=RULE_4_PROD_DATABASES
Notification Rule Owner=SYSMAN
============================
Is there any way to get the complete error details in the OEM alert itself.
Regards
DBA.

You need to look at the Alert Log error messages, not the "status" messages. See doc http://docs.oracle.com/cd/E11857_01/em.111/e16285/oracle_database.htm#autoId2

How to be notified for all ORA- Errors recorded in the alert.log file

based on Note:405396.1, I Changed the Matches Warning from the default value ORA-0*(600?|7445|4[0-9][0-9][0-9])[^0-9] to ORA-* in order to receive an warning alert for all ORA- errors.
but I just recieved the alert like the following:
Metric=Generic Alert Log Error
Time/Line Number=Mon Feb 25 23:52:21 2008/21234
Timestamp=Feb 26, 2008 12:06:03 AM EST
Severity=Warning
Message=ORA-error stack (1654, 1654, 1654) logged in /opt/oracle/admin/PRD/bdump/alert_PRD.log.
Notification Rule Name=Alert Log Error
Notification Rule Owner=SYSMAN
as you can see, the message only indicate the ORA-1654, nothing else.
How to set in 10g grid control to get the details alert that in the alert log like:
"ORA-1654: unable to extend index ADM.RC_BP_STATUS by 1024 in tablespace PSINDEX"
I can't believe Oracle 10g Grid control only provide the ORA- number without details

Go to your database target.
On the home tab, on the left hand side under Diagnostic Summary, you'll see a clickable date link next to where it says 'Alert Log'. Click on that.
next click on Generic Alert Log Error Monitoring Configuration (its at the bottom)
In the alert thresholds put:
ORA-0*(600?|7445|4[0-9][0-9][0-9])[^0-9]
I believe that will pick anything up but experiment, its only perl.
If you want to test this use the DBMS_System.ksdwrt package but I would advise you only do so on a test database. If you've never heard of it, google it. Its a way of writing to your alert log.
Make sure you have your emails sent to long format as well.

"found dead shared server ... " errors occured in oracle alert log

Dear all,
I have found a error message in my oracle alert log which is "found dead shared server 's000, pid=(10,1)'". What's this mean? and this error will casue a core dump in ../cdump directory.
btw. Thanks the answers of antti.koskinen and yingkuan.

one more thing, my server is not configured as shared server mode, it is dedicated server mode. but I don't know why system inform me "found dead shared server..".

Error in primary database alert log

Dear all i am getting the following error in my primary database alert log
oracle 10.2.0.3
Os/ rhel 4
Errors in file /u01/app/oracle/admin/PROSVR1/bdump/prosvr1_arc0_26151.trc:
ORA-00088: command cannot be executed by shared server
Tue Jul 7 23:20:37 2009
PING[ARC0]: Heartbeat failed to connect to standby 'DRSVR1'. Error is 88.
Tue Jul 7 23:25:38 2009
Errors in file /u01/app/oracle/admin/PROSVR1/bdump/prosvr1_arc0_26151.trc:
ORA-00088: command cannot be executed by shared server
Tue Jul 7 23:25:38 2009
PING[ARC0]: Heartbeat failed to connect to standby 'DRSVR1'. Error is 88.
Please let me know what needs to be done.
THanks in advance,
Aj

00088, 00000, "command cannot be executed by shared server "
// *Cause: Debug command issued on shared server.
// *Action: Reissue the command using a dedicated server.

Prodding the archiver in alert log

the following things are repeated in the alert log file can any guru explain me about these and any alternation required in the system level
Mon Sep 04 18:21:48 2006
ARC0: received prod
Mon Sep 04 18:21:48 2006
ARC0: Beginning to archive log# 3 seq# 2102048
ARC0: Completed archiving log# 3 seq# 2102048
ARC0: re-scanning for new log files
ARC0: prodding the archiver
ARC0: received prod
Mon Sep 04 18:23:03 2006
LGWR: prodding the archiver
Thread 1 advanced to log sequence 2102050
Mon Sep 04 18:23:03 2006
Current log# 1 seq# 2102050 mem# 0: C:\ORACLE\MMP\LOG\REDO01.LOG
Current log# 1 seq# 2102050 mem# 1: E:\ORACLE\MMP\LOG\REDO01.LOG
Mon Sep 04 18:23:04 2006
ARC0: received prod
Mon Sep 04 18:23:04 2006
ARC0: Beginning to archive log# 4 seq# 2102049
ARC0: Completed archiving log# 4 seq# 2102049
ARC0: re-scanning for new log files
ARC0: prodding the archiver
ARC0: received prod
Mon Sep 04 18:24:10 2006
LGWR: prodding the archiver
Mon Sep 04 18:24:10 2006
ARC0: received prod
ARC0: Beginning to archive log# 1 seq# 2102050
Thread 1 advanced to log sequence 2102051
Mon Sep 04 18:24:11 2006
Current log# 5 seq# 2102051 mem# 0: E:\ORACLE\MMP\LOG\REDO05.LOG
Current log# 5 seq# 2102051 mem# 1: C:\ORACLE\MMP\LOG\REDO05.LOG
Mon Sep 04 18:24:13 2006
ARC0: Completed archiving log# 1 seq# 2102050
ARC0: re-scanning for new log files
ARC0: prodding the archiver
ARC0: received prod

Hi oradba,
I havent set any parameter in parameter file. so what i should I do reduce the message in alert log. So What is the message prodding,rescanning mean in the arch0,1 etc., Currently I have 5 log files and from the message of alert log i could find that there are 4 archiver process. Is there is compare and contrast for no.log files and no.of archiver process. Please explain...
Thanks in advance
with regards
Prem

ORA-16009 Error in Alert Log

Hi DBAs,
I saw the error ORA-16009 in alert log file. The database version is 10.2.0.3 configured with Physical standby on AIX 6.1 . The error is coming in alert log for a long time , I beleive after a swithover to Standby and switch back to Primary.
But I see the log from Primary to Standby are being applied and MRP is working fine on Standby Site.
I am posting the error message from alert log and trace file.
-------- Message in alert.log --------------
--Connected User is Valid
RFS[61129]: Assigned to RFS process 1511478
RFS[61129]: Database mount ID mismatch [0x8afdb574:0x8afd830b]
RFS[61129]: Client instance is standby database instead of primary
RFS[61129]: Not using real application clusters
Fri May 8 22:32:57 2009
Errors in file /oracle/admin/DBSID/udump/DBSID_rfs_1511478.trc:
ORA-16009: remote archive log destination must be a STANDBY database/oracle/admin/DBSID/bdump
HOST [DBSID]-> May 8 22:33:52 hostname daemon:err|error ltid[933986]: Remote scan failed on host HOST, drive IBMULTRIUM-TD25, Host is not the scan host for this shared drive (304)
----------------- Trace File with complete detail of the Error -----------------------------------
/oracle/admin/DBSID/udump/DBSID_rfs_1511478.trc
Oracle Database 10g Enterprise Edition Release 10.2.0.3.0 - 64bit Production
With the Partitioning and Data Mining options
ORACLE_HOME = /oracle/product/10.2.0/db_1
System name: AIX
Node name: hostname
Release: 3
Version: 5
Machine: XXXXXXX
Instance name: DBSID
Redo thread mounted by this instance: 1
Oracle process number: 19
Unix process pid: 1491066, image: oracleDBSID@hostname*** SERVICE NAME:(DBSID.DOMAIN.COM) 2009-05-08 22:31:57.314
*** SESSION ID:(1094.21412) 2009-05-08 22:31:57.314
Detected dead process 1491030; subsuming V$MANAGED_STANDBY slot
*** 2009-05-08 22:31:57.318 61287 kcrr.c
RFS[61128]: Database mount ID mismatch [0x8afdb574:0x8afd830b]
*** 2009-05-08 22:31:57.318 61287 kcrr.c
RFS[61128]: Client instance is standby database instead of primary
*** 2009-05-08 22:31:57.318 61287 kcrr.c
RFS[61128]: Not using real application clusters
ORA-16009: remote archive log destination must be a STANDBY database
Please advise and suggest,
Thanks
-Samar-

I have the follow setting for log_archive_dest_2 on Primary and standby which seems to be OK but above mention note which is for Oracle 9i server suggesting to disable the remote archiving on the standby database. Also I am using ASYNC option for log transport.
At Primary:
SQL> show parameter log_archive_dest_2
NAME TYPE VALUE
log_archive_dest_2 string SERVICE=STDBY LGWR ASYNC REOPEN=60 DB_UNIQUE_NAME=STDBY
At standby:
SQL> show parameter log_archive_dest_2
NAME TYPE VALUE
log_archive_dest_2 string SERVICE=PRI LGWR ASYNC REOPEN=60 DB_UNIQUE_NAME=PRI
Thanks
-Samar-

Archiver hung al log error

Hi,
i got the alert in OEM grid control for a database.The alert is archiver hung alert log error.what is this errror and how i should over come it.
Thankx in advance....

Hi,
i got the alert in OEM grid control for a
database.The alert is archiver hung alert log
error.what is this errror and how i should over comeOne of the database monitored by Grid Control is reporting that the Archiver is hung. The Archiver hangs when it is unable to write archive logs to the archive log destination directory. You need to either increase the size of the archive log destination directory or back up and purge the archive logs.

Errors in the alert log upon portal 3.0.6 installation

We installed Portal 3.0.6 with with Oracle 8.1.7 on a RedHat 6.2, kernel 2.2.17 machine. We noticed the following error lines in the alert-log, just before opening the DB:
ORA-00604: error occurred at recursive SQL level 1
ORA-04045: errors during recompilation/revalidation of SYS./cd252dcc_RegisterService
ORA-30511: invalid DDL operation in system triggers
ORA-06512: at "SYS.DBMS_JAVA", line 0
ORA-06512: at line 2
Any idea what might be the problem here?
The DB and Portal seem to communicate well so far. The pool_sizes in init.ora are setup high, 50Mb each.
Thanks.
K.
null

Krassi,
Not sure what the error is. Have you tried to look at the object using DBA Studio to see if it can be recompiled?
Rich

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

Strange errors in alert log

Hi, as someone relatively new to Oracle i need some help in identifying some errors in the oracle alert log.
ORA-12012: error on auto execute of job 92712
ORA-29282: invalid file ID
Thu Mar 14 23:17:50 GMT 2013
I know that nothing should be running at 23:17 on the database so i can only assume its a maintanance job - but how can i identify exactly what it relates to and what the error is?
Kind regards

Error: ORA 12012
Text: error on auto execute of job <num>
Cause: Some kind of error was caught while doing an automatic execute of a
job.
Action: Look at the accompanying errors for details on why the execute failed.
SELECT * FROM user_jobslooking for id

Create report to get lat 30days Metric alert & Alert log errors Grid

We would like to create a report to display last 30 day's mertric alert and alert log errros in EM Grid. How we can do it?

DBMS Direct,
But in the post How to be notified for all ORA- Errors recorded in the alert.log file
11iuser complain about that why he/she just get error number without any explain of arrised error.
In my situation I just get "distinct types of ORA- errors" without even any error code.
Perhaps I need to change something in emoms.properties or emd.properties.
By the way I select Message format -- Long Format
Sorry for my poor English

Receiving Alerts on ORA- error in Alert Log File

Hi,
I am using 10.2.0.5 OEM grid control and same versioned agent on my database servers. I have configured the alert email notification if there is any ORA- error message in my alert log file. The metric i selcted for this is "Generic Alert Log Error Status". In notification email, i see only the message that there is generic error message in the alert log file. Is there any way to set this notification so that i receive the exact ORA- error message in my alert notification email if there is any kind of ORA- error found in my alert log file?
Thanks
Salman

Please look into the Metalink Note: 458605.1
Subject: Receiving "Clear" Notifications Unexpectedly for 'Generic Alert Log Error Status' Metric

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

Errors in archiving in alert log

Similar Messages

Maybe you are looking for