Database alert Macro

Hi All,
can you please explain me,why database alerts macro taking long time to run.
Regards,
Naveen.

Venkat
Yes it is a common problem that many companies face. The system has to read data from alert tables such as /sapapo/am_alert and i guess one reason for the long run time is indexing of alert tables especially the /sapapo/am_alert. Please check the OSS notes provide by SAP to improve the performance of alert runtime and display
We applied these notes a while ago and it did make a huge difference. Check notes 907472 ,596332 - and in general all notes that you get when u search with criteria /sapapo/am_alert .
Thanks
Aparna
Edited by: Aparna.Ranganathan on Nov 19, 2010 5:08 PM

Similar Messages

Database Alert Macros issue while executing the macros in Background

Hi All,
I am facing some problems while executing the Database alert macros in Background/Process Chain.
There are two macros for which the problem exists.
1.Excess Projected Inventory above Max
The logic here is, the alert should work for Only Fixed Lot size Procedure.
If the Stock on hand (projected EA) > (Safety Stock (EA) + Full SOQ (EA)) then alert = "Projected inventory is XX% above MAX".
XX is the Percent above Max.
Note: SOQ => fixed lot size.
2.Excess Actual Days of Supply
The Logic here is, the alert should work for all Lot size Procedures except for "Fixed lot size".
Actual Days Supply >=180 days. (current -> future buckets)
- For every receipt cell check the Actual Days Supply - if >= 180 days.
The macros are working perfectly as expected.

Hi Abhi,
Hope you are doing good.
Yes exactly, the macros are working in foreground/Interactively but not in the Background via Process chain. Let me send the details again.
Issue :
I am facing some problems while executing the Database alert macros in Background/Process Chain.
There are two macros for which the problem exists.
1.Excess Projected Inventory above Max
The logic here is, the alert should work for Only Fixed Lot size Procedure. But in Background the alerts are getting created for Lot for Lot and other Planning procedures..
If the Stock on hand (projected EA) > (Safety Stock (EA) + Full SOQ (EA)) then alert = "Projected inventory is XX% above MAX".
XX is the Percent above Max.
Note: SOQ => fixed lot size.
2.Excess Actual Days of Supply
The Logic here is, the alert should work for all Lot size Procedures except for "Fixed lot size". But in Background the alerts are getting created for the Fixed Lot size procedures too..
Actual Days Supply >=180 days. (current -> future buckets)
- For every receipt cell check the Actual Days Supply - if >= 180 days.
The macros are working perfectly as expected in Foreground/Interactively but the samething is not happening while executing the macro in Background/Process Chain.
I have tried running these macros in different sequences(Default/Start/Macro) but couldn't able to resolve the issue.
Thanks in Advance,
Jay.

Errors in Database Alert Log... Please Help

Hi All,
This database is on Oracle 8i but I found errors in the alert Log.
These errors are relating to archiving.
Please take a look at this file to see the details;
http://us.f13.yahoofs.com/bc/47aff3ab_a145/bc/My+Documents/Database+Alert+Log.LOG?bfUw9sHBkd_LbjY0
ARC0: Beginning to archive log# 11 seq# 301
Wed Feb 13 14:57:45 2008
ARC0: Completed archiving log# 11 seq# 301
Wed Feb 13 15:46:26 2008
Errors in file E:\Oracle\admin\MUKREC\udump\ORA03852.TRC:
Wed Feb 13 15:46:26 2008
Errors in file E:\Oracle\admin\MUKREC\udump\ORA03208.TRC:
Wed Feb 13 15:46:30 2008
Errors in file E:\Oracle\admin\MUKREC\udump\ORA03340.TRC:
Wed Feb 13 15:46:30 2008
Errors in file E:\Oracle\admin\MUKREC\udump\ORA00784.TRC:
Wed Feb 13 15:46:31 2008
Errors in file E:\Oracle\admin\MUKREC\udump\ORA03748.TRC:
Wed Feb 13 15:46:32 2008
Errors in file E:\Oracle\admin\MUKREC\udump\ORA01228.TRC:
Wed Feb 13 16:18:57 2008
Thread 1 advanced to log sequence 303
Current log# 13 seq# 303 mem# 0: E:\ORACLE\ORADATA\MUKREC\LOGS\REDO13.LOG
Wed Feb 13 16:18:57 2008
ARC2: Beginning to archive log# 12 seq# 302
Wed Feb 13 16:19:25 2008
ARC2: Completed archiving log# 12 seq# 302
Wed Feb 13 18:40:13 2008
Errors in file E:\Oracle\admin\MUKREC\udump\ORA03872.TRC:
Please help out. What is exactly the cause of this error and how can I avoid it next time from occuring.

>> Please paste the output of E:\Oracle\admin\MUKREC\udump\ORA03872.TRC
Click on the link below to get the output of the ORA03872.TRC trace file
http://us.f13.yahoofs.com/bc/47aff3ab_a145/bc/My+Documents/ORA03872.TRC?bfMq_sHBSRis64KA
>> and last 100 lines of alert log
the last 100 lines of the alert log are here under;
Wed Feb 13 11:50:27 2008
Thread 1 advanced to log sequence 296
Current log# 13 seq# 296 mem# 0: E:\ORACLE\ORADATA\MUKREC\LOGS\REDO13.LOG
Wed Feb 13 11:50:27 2008
ARC0: Beginning to archive log# 12 seq# 295
Wed Feb 13 11:51:02 2008
ARC0: Completed archiving log# 12 seq# 295
Wed Feb 13 12:27:18 2008
Thread 1 advanced to log sequence 297
Current log# 7 seq# 297 mem# 0: E:\ORACLE\ORADATA\MUKREC\LOGS\REDO07.LOG
Wed Feb 13 12:27:18 2008
ARC0: Beginning to archive log# 13 seq# 296
Wed Feb 13 12:27:59 2008
Thread 1 advanced to log sequence 298
Current log# 8 seq# 298 mem# 0: E:\ORACLE\ORADATA\MUKREC\LOGS\REDO08.LOG
Wed Feb 13 12:27:59 2008
ARC1: Beginning to archive log# 13 seq# 296
ARC1: Failed to archive log# 13 seq# 296
ARC1: Beginning to archive log# 7 seq# 297
Wed Feb 13 12:28:33 2008
Thread 1 advanced to log sequence 299
Current log# 9 seq# 299 mem# 0: E:\ORACLE\ORADATA\MUKREC\LOGS\REDO09.LOG
Wed Feb 13 12:29:10 2008
Thread 1 advanced to log sequence 300
Current log# 10 seq# 300 mem# 0: E:\ORACLE\ORADATA\MUKREC\LOGS\REDO10.LOG
Wed Feb 13 12:29:11 2008
ARC0: Completed archiving log# 13 seq# 296
ARC0: STARTING ARCH PROCESSES
ARC2 started with pid=166
Wed Feb 13 12:29:11 2008
ARC0: STARTING ARCH PROCESSES COMPLETE
Wed Feb 13 12:29:11 2008
ARC0: Beginning to archive log# 7 seq# 297
ARC0: Failed to archive log# 7 seq# 297
ARC0: Beginning to archive log# 8 seq# 298
Wed Feb 13 12:29:12 2008
ARC2: Archival started
Wed Feb 13 12:29:32 2008
ARC1: Completed archiving log# 7 seq# 297
ARC1: Beginning to archive log# 8 seq# 298
ARC1: Failed to archive log# 8 seq# 298
ARC1: Beginning to archive log# 9 seq# 299
Wed Feb 13 12:29:48 2008
ARC0: Completed archiving log# 8 seq# 298
Wed Feb 13 12:29:48 2008
ARC2: Beginning to archive log# 9 seq# 299
ARC2: Failed to archive log# 9 seq# 299
Wed Feb 13 12:30:03 2008
ARC1: Completed archiving log# 9 seq# 299
Wed Feb 13 14:46:05 2008
Thread 1 advanced to log sequence 301
Current log# 11 seq# 301 mem# 0: E:\ORACLE\ORADATA\MUKREC\LOGS\REDO11.LOG
Wed Feb 13 14:46:05 2008
ARC1: Beginning to archive log# 10 seq# 300
Wed Feb 13 14:46:41 2008
ARC1: Completed archiving log# 10 seq# 300
Wed Feb 13 14:57:10 2008
Thread 1 advanced to log sequence 302
Current log# 12 seq# 302 mem# 0: E:\ORACLE\ORADATA\MUKREC\LOGS\REDO12.LOG
Wed Feb 13 14:57:10 2008
ARC0: Beginning to archive log# 11 seq# 301
Wed Feb 13 14:57:45 2008
ARC0: Completed archiving log# 11 seq# 301
Wed Feb 13 15:46:26 2008
Errors in file E:\Oracle\admin\MUKREC\udump\ORA03852.TRC:
Wed Feb 13 15:46:26 2008
Errors in file E:\Oracle\admin\MUKREC\udump\ORA03208.TRC:
Wed Feb 13 15:46:30 2008
Errors in file E:\Oracle\admin\MUKREC\udump\ORA03340.TRC:
Wed Feb 13 15:46:30 2008
Errors in file E:\Oracle\admin\MUKREC\udump\ORA00784.TRC:
Wed Feb 13 15:46:31 2008
Errors in file E:\Oracle\admin\MUKREC\udump\ORA03748.TRC:
Wed Feb 13 15:46:32 2008
Errors in file E:\Oracle\admin\MUKREC\udump\ORA01228.TRC:
Wed Feb 13 16:18:57 2008
Thread 1 advanced to log sequence 303
Current log# 13 seq# 303 mem# 0: E:\ORACLE\ORADATA\MUKREC\LOGS\REDO13.LOG
Wed Feb 13 16:18:57 2008
ARC2: Beginning to archive log# 12 seq# 302
Wed Feb 13 16:19:25 2008
ARC2: Completed archiving log# 12 seq# 302
Wed Feb 13 18:40:13 2008
Errors in file E:\Oracle\admin\MUKREC\udump\ORA03872.TRC:
Thu Feb 14 08:03:54 2008
Thread 1 advanced to log sequence 304
Thu Feb 14 08:03:54 2008
Current log# 7 seq# 304 mem# 0: E:\ORACLE\ORADATA\MUKREC\LOGS\REDO07.LOG
Thu Feb 14 08:03:55 2008
ARC1: Beginning to archive log# 13 seq# 303
Thu Feb 14 08:04:45 2008
ARC1: Completed archiving log# 13 seq# 303
Thu Feb 14 08:24:29 2008
Thread 1 advanced to log sequence 305
Current log# 8 seq# 305 mem# 0: E:\ORACLE\ORADATA\MUKREC\LOGS\REDO08.LOG
Thu Feb 14 08:24:29 2008
ARC0: Beginning to archive log# 7 seq# 304
Thu Feb 14 08:25:01 2008
ARC0: Completed archiving log# 7 seq# 304
------------------------------------------------------------------------------------------------------------------------------------

Production database Alert log Message

Hi,
I am using oracle 10gR1 on windows.Recently i have created a physical standby database (sid=smtm) and production database (sid=mtm).My production alter log file dispaly some thing like please suggest my what it shows.
Mon Mar 02 00:18:31 2009
Private_strands 7 at log switch
Thread 1 advanced to log sequence 35722
Current log# 4 seq# 35722 mem# 0: D:\ORACLE\PRODUCT\10.1.0\ORADATA\MTM\REDO04.LOG
Current log# 4 seq# 35722 mem# 1: D:\ORACLE\PRODUCT\10.1.0\ORADATA\MTM\REDO04_A.LOG
Mon Mar 02 00:18:31 2009
ARC1: Evaluating archive   log 2 thread 1 sequence 35721
ARC1: Destination LOG_ARCHIVE_DEST_2 archival not expedited
Committing creation of archivelog 'E:\ORACLE\MTM\ARCHIVES\MTM_945F37AC_1_35721_500044525.ARC'
Invoking non-expedited destination LOG_ARCHIVE_DEST_2 thread 1 sequence 35721 host SMTM
*FAL[server, ARC1]: Begin FAL noexpedite archive (branch 500044525 thread 1 sequence 35721 dest SMTM)*
*FAL[server, ARC1]: Complete FAL noexpedite archive (thread 1 sequence 35721 destination SMTM)*Mon Mar 02 00:29:42 2009
Private_strands 7 at log switch
Thread 1 advanced to log sequence 35723
Current log# 3 seq# 35723 mem# 0: D:\ORACLE\PRODUCT\10.1.0\ORADATA\MTM\REDO03.LOG
Current log# 3 seq# 35723 mem# 1: D:\ORACLE\PRODUCT\10.1.0\ORADATA\MTM\REDO03_A.LOG
Mon Mar 02 00:29:42 2009
ARC1: Evaluating archive   log 4 thread 1 sequence 35722
ARC1: Destination LOG_ARCHIVE_DEST_2 archival not expedited
Committing creation of archivelog 'E:\ORACLE\MTM\ARCHIVES\MTM_945F37AC_1_35722_500044525.ARC'
Invoking non-expedited destination LOG_ARCHIVE_DEST_2 thread 1 sequence 35722 host SMTM
*FAL[server, ARC1]: Begin FAL noexpedite archive (branch 500044525 thread 1 sequence 35722 dest SMTM)*
*FAL[server, ARC1]: Complete FAL noexpedite archive (thread 1 sequence 35722 destination SMTM)*
Thanks

Sorry i have no metalink account.
On production database there is no any ORA error and on standby database Alert log shows.
Mon Mar 02 03:40:38 2009
RFS[1]: No standby redo logfiles created
RFS[1]: Archived Log: 'E:\ORACLE\PRODUCT\10.1.0\ARCHIVES\MTM_945F37AC_1_35728_500044525.ARC'
Committing creation of archivelog 'E:\ORACLE\PRODUCT\10.1.0\ARCHIVES\MTM_945F37AC_1_35728_500044525.ARC'
RFS[1]: No standby redo logfiles created
RFS[1]: Archived Log: 'E:\ORACLE\PRODUCT\10.1.0\ARCHIVES\MTM_945F37AC_1_35729_500044525.ARC'
Committing creation of archivelog 'E:\ORACLE\PRODUCT\10.1.0\ARCHIVES\MTM_945F37AC_1_35729_500044525.ARC'
RFS[1]: No standby redo logfiles created
RFS[1]: Archived Log: 'E:\ORACLE\PRODUCT\10.1.0\ARCHIVES\MTM_945F37AC_1_35730_500044525.ARC'
Committing creation of archivelog 'E:\ORACLE\PRODUCT\10.1.0\ARCHIVES\MTM_945F37AC_1_35730_500044525.ARC'Mon Mar 02 04:29:14 2009
RFS[1]: No standby redo logfiles created
RFS[1]: Archived Log: 'E:\ORACLE\PRODUCT\10.1.0\ARCHIVES\MTM_945F37AC_1_35731_500044525.ARC'
Committing creation of archivelog 'E:\ORACLE\PRODUCT\10.1.0\ARCHIVES\MTM_945F37AC_1_35731_500044525.ARC'
Media Recovery Log
ORA-279 signalled during: ALTER DATABASE RECOVER standby database ...Mon Mar 02 11:01:57 2009
ALTER DATABASE RECOVER CONTINUE DEFAULT
Mon Mar 02 11:01:57 2009
Media Recovery Log E:\ORACLE\PRODUCT\10.1.0\ARCHIVES\MTM_945F37AC_1_35553_500044525.ARC
ORA-279 signalled during: ALTER DATABASE RECOVER    CONTINUE DEFAULT ...Mon Mar 02 11:02:05 2009
ALTER DATABASE RECOVER CONTINUE DEFAULT
Media Recovery Log E:\ORACLE\PRODUCT\10.1.0\ARCHIVES\MTM_945F37AC_1_35554_500044525.ARC
ORA-279 signalled during: ALTER DATABASE RECOVER CONTINUE DEFAULT ...
Mon Mar 02 11:02:14 2009
ALTER DATABASE RECOVER CONTINUE DEFAULT
Media Recovery Log E:\ORACLE\PRODUCT\10.1.0\ARCHIVES\MTM_945F37AC_1_35555_500044525.ARC
ORA-279 signalled during: ALTER DATABASE RECOVER CONTINUE DEFAULT ...
Regards
Thanks for reply.

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.

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.

The database alert log has errors. Please help me

Hi all
I have an Oracle 8i Database that seams to be functioning well but when I
Checked the Database alert Log I realized that something is not fine
Part of the alert log content is here under. What can be problem and how can I
Resolve it. Please I need you assistance...
Thu Feb 07 08:50:37 2008
Thread 1 advanced to log sequence 266
Thu Feb 07 08:50:37 2008
Current log# 11 seq# 266 mem# 0: E:\ORACLE\ORADATA\MUKREC\LOGS\REDO11.LOG
Thu Feb 07 08:50:38 2008
ARC0: Beginning to archive log# 10 seq# 265
Thu Feb 07 08:51:07 2008
ARC0: Completed archiving log# 10 seq# 265
Thu Feb 07 09:23:22 2008
Errors in file E:\Oracle\admin\MUKREC\udump\ORA03976.TRC:
Thu Feb 07 09:23:23 2008
Errors in file E:\Oracle\admin\MUKREC\udump\ORA04092.TRC:
................................................................................................................

I'll just throw a shameless copy-paste from Metalink note : 164839.1 , hope you can use it to get further ? :
Subject: FATAL ERROR IN TWO-TASK SERVER: error = 12571 Found in Alert File
Doc ID: Note:164839.1 Type: PROBLEM
Last Revision Date: 17-DEC-2007 Status: PUBLISHED
fact: Oracle Server - Enterprise Edition
symptom: Errors appear in alert file
symptom: FATAL ERROR IN TWO-TASK SERVER:
symptom: ERROR = 12571
symptom: trace file generated
symptom: Database operations continue successfully
cause: The most common cause for the above error is an ungraceful
disconnection of a session from the oracle db while the db is currently running
a dml statement issued by that session. The error is recorded when oracle
attempts to reply back to the session with the results of the dml and cannot
access the session. Overall database operations are usually not affected.
An ungraceful disconnection could cause by but is not limited to any of the
following:
- the client machine crashed
- the network connection crashed
- the user exited the session improperly (not issuing the 'exit' command)
- the user application allows the user to exit the application without properly
terminating the session.
The above can cause problems with corrupted rollback segments if occurring on a
regular basis and is not addressed. This would require db recovery and
possibly a db rebuild (not a light matter)
PMON will usually rollback most transactions in the rollback segments for a
session if it finds that the session has been ungracefully disconnected, but
there is always a chance that it cannot and this will lead to rollback segment
corruption.
fix:
The dml and the user that issued the dml can be determined from the trace file.
The current dml is in the tracefile header section. The user can be found in
the process state dump of the trace. The process state shows the machine,
o/suser, and user for the session.
The DBA can use this information to determine what the user was doing at the
time and if there was an ungraceful exit from the session the user was
utilizing.
The DBA should then address the cause of the ungraceful exit to reduce the
possibility of recurrence.

Reg-Alert Macro-Day's supply not working

Hi,
    We are using Data base alert macros for day's supply of SNP.But it seems macros are not working.Planning book day's supply key figures value not refelcting in alert monitor(amon1).
our setting is 0-30 days-Information;
                     31-50-Warning;
                     above 51-Error
Thanks&Regards
Venkadesh

Hi Venkadesh,
I think you put your indicator upside down.
0 to 30 should be error and avobe 51 information.
Another comments: to check if the macro is working: after running it, in interactive or background, check table /SAPAPO/AM_ALERT to see if you can see the alert or not.
If you can see the alert in the table but not in the profile, then the issue is your profile; if you can't see your alert in the table neither, then the issue is the alert creation in the macro...
I hope it helps
Julien

APO - SNP Alert Macros running too slow

Hi,
We have created alert macros which run for next 27 weeks for 38000 Product-Location Combinations. They are running too slow.
We are deleting alerts externally using program /sapapo/amon_reorg and then running this macro with "ADD" . This macro slows down once it starts filling up alert table with 100,000 records. What are the best practices for writing the macro so that it runs fast ?.
Thanks.

Is it necessary to write all the alerts? What I mean is, do you filter the results when you view them through the Alert Monitor?
If your alert profile has a minimum threshold set for an alert type, then you can read this threshold in the macro and only write alerts that fall below the threshold.
e.g.
Step: Get Threshold Values : ( 1 Iterations :Initial;Initial )
    Action Box: Get Threshold Value
      LAYOUTVARIABLE_SET( 'Alert_Thresh' ;
      ALERT_PROFILE_THRESH( SDP_ALERT_PROFILE' ; '4100' ; 'I' ) )
Where SDP_ALERT_PROFILE is the profile that contain sthe minimum threshold you want to use and 4100 is the alert type. The I is for information, can use either W for Warning or E for Error as well.
Then use the variable Alert_Thresh to check if your value falls below this, only then write the alert.
Regards
Ian

Database Alerts

Hi,
We want to get database alerts/reports on our production environment for the following
·         Alert when a database goes down.
·         Daily Table and Tablespace growth.
·         Daily database backup reports for success/failure.
Please let us know the steps if it is posible to get these reports through SAP DBA COCKPIT tool or through some other options.
We are using db2 9.7 Fixpack 3.
Appreciate your help on this.

Hi,
There are number of notes on this thing, you can check SAP note 66322.
Thanks
Sunny

Database Alert log.

Hi , I am having release Release 11.2.0.3.0 of oracle. Got database crash tuesday morning, and i am trying to get the reason for the crash. Given below is the alert.log for same. I can see Process RSM0 is getting killed , triggered the crash but could not relate it to the event follwed.
--------------------------------- ALERT.LOG---------------------------
Tue Aug 13 00:20:51 2013
Thread 1 advanced to log sequence 9737 (LGWR switch)
Current log# 3 seq# 9737 mem# 0: +DATA01/sid1004/onlinelog/group_3.379.817601969
Current log# 3 seq# 9737 mem# 1: +DATA02/sid1004/onlinelog/group_3.5858.817601983
Tue Aug 13 00:20:51 2013
LNS: Standby redo logfile selected for thread 1 sequence 9737 for destination LOG_ARCHIVE_DEST_2
Tue Aug 13 00:21:11 2013
Archived Log entry 20595 added for thread 1 sequence 9736 ID 0xe56c03af dest 1:
Tue Aug 13 00:30:48 2013
Thread 1 advanced to log sequence 9738 (LGWR switch)
Current log# 4 seq# 9738 mem# 0: +DATA01/sid1004/onlinelog/group_4.378.817601995
Current log# 4 seq# 9738 mem# 1: +DATA02/sid1004/onlinelog/group_4.7210.817602007
Tue Aug 13 00:30:48 2013
LNS: Standby redo logfile selected for thread 1 sequence 9738 for destination LOG_ARCHIVE_DEST_2
Tue Aug 13 00:30:55 2013
Archived Log entry 20597 added for thread 1 sequence 9737 ID 0xe56c03af dest 1:
Tue Aug 13 00:40:41 2013
Thread 1 advanced to log sequence 9739 (LGWR switch)
Current log# 5 seq# 9739 mem# 0: +DATA01/sid1004/onlinelog/group_5.377.817602019
Current log# 5 seq# 9739 mem# 1: +DATA02/sid1004/onlinelog/group_5.10031.817602031
Tue Aug 13 00:40:42 2013
LNS: Standby redo logfile selected for thread 1 sequence 9739 for destination LOG_ARCHIVE_DEST_2
Tue Aug 13 00:40:47 2013
Archived Log entry 20599 added for thread 1 sequence 9738 ID 0xe56c03af dest 1:
Tue Aug 13 00:50:41 2013
Thread 1 advanced to log sequence 9740 (LGWR switch)
Current log# 6 seq# 9740 mem# 0: +DATA01/sid1004/onlinelog/group_6.376.817602043
Current log# 6 seq# 9740 mem# 1: +DATA02/sid1004/onlinelog/group_6.6026.817602057
Tue Aug 13 00:50:41 2013
LNS: Standby redo logfile selected for thread 1 sequence 9740 for destination LOG_ARCHIVE_DEST_2
Tue Aug 13 00:50:46 2013
Archived Log entry 20601 added for thread 1 sequence 9739 ID 0xe56c03af dest 1:
Tue Aug 13 01:00:40 2013
Thread 1 advanced to log sequence 9741 (LGWR switch)
Current log# 7 seq# 9741 mem# 0: +DATA01/sid1004/onlinelog/group_7.375.817602069
Current log# 7 seq# 9741 mem# 1: +DATA02/sid1004/onlinelog/group_7.10703.817602081
Tue Aug 13 01:00:41 2013
LNS: Standby redo logfile selected for thread 1 sequence 9741 for destination LOG_ARCHIVE_DEST_2
Tue Aug 13 01:00:46 2013
Archived Log entry 20603 added for thread 1 sequence 9740 ID 0xe56c03af dest 1:
Tue Aug 13 01:09:02 2013
minact-scn: useg scan erroring out with error e:12751
Tue Aug 13 01:10:38 2013
Thread 1 advanced to log sequence 9742 (LGWR switch)
Current log# 8 seq# 9742 mem# 0: +DATA01/sid1004/onlinelog/group_8.374.817602093
Current log# 8 seq# 9742 mem# 1: +DATA02/sid1004/onlinelog/group_8.12060.817602105
Tue Aug 13 01:10:39 2013
LNS: Standby redo logfile selected for thread 1 sequence 9742 for destination LOG_ARCHIVE_DEST_2
Tue Aug 13 01:10:51 2013
Archived Log entry 20605 added for thread 1 sequence 9741 ID 0xe56c03af dest 1:
Tue Aug 13 01:15:55 2013
Time drift detected. Please check VKTM trace file for more details.
Tue Aug 13 01:16:27 2013
Thread 1 advanced to log sequence 9743 (LGWR switch)
Current log# 1 seq# 9743 mem# 0: +DATA01/sid1004/onlinelog/group_1.381.817601921
Current log# 1 seq# 9743 mem# 1: +DATA02/sid1004/onlinelog/group_1.5144.817601933
Tue Aug 13 01:17:51 2013
Process RSM0, PID = 8562, will be killed
Tue Aug 13 02:19:38 2013
Starting ORACLE instance (normal)

While you're at MetaLink/MyOracle support, you'd probably want to read the following doc id's as well:
Time Drift Detected. Please Check Vktm Trace File For More Details. (Doc ID 1347586.1)
Alert log shows: "Minact-scn: Useg Scan Erroring Out With Error E:12751" Warning (Doc ID 1478691.1)

Database Alert Rule Engine

Hello ,
I am running Oracle XE . This database collects information about server statistics in my organization ( memory usage, threads running, etc). Now , I need to send alert/ notification emails if the certain thresholds are crossed by server ( ex: if number of threads increase more than 100, send an alert email).
One way to do this is to write stored procedures and schedule them to run every hour and send alert email if conditions are met.
But what I want to do is to use some sort of rule engine where I can specify the rules/conditions which have to be true for alerts to be sent. The reason I want this approach is so that every time there is a new rule, I do not have to write a new stored procedure and I can just specify the condition in the rule engine .
So are there any Rule Engines out there that I can use?

Hi,
Yes.
Oracle has a monitoring tool built-in Entreprise Manager.
I suggest that you get started with:
10g
http://download.oracle.com/docs/cd/E11882_01/server.112/e17120/diag002.htm#ADMIN12292
11g
http://download.oracle.com/docs/cd/E11882_01/server.112/e17120/monitoring001.htm
HTH,
Thierry

Alert Macro Logic

I need a logic to generate an alert, when ever the user executing a macro in monthly buckets. They should always use the Storage bucket profile (Feature available in 5.0). Any help is greatly appreciated.
thx
Jeff

I used the Function: BUCKET_DAYS and was able to resolve this issue.
thx
Jeff

Strange "Database Alert" message when opening Mail

For the last several days, each time I launch Mail, it retrieves mail and then up pops an alert:
"inconsistencies in your sync information for bookmarks were detected and have been repaired."
What is that all about?
It's annoying. How can I fix it?

I receive the same result with contacts

How can I avoid polling for database alerts?

I am implementing a Java package that makes processing alerts from Oracle (the dbms_alert pl/sql package) easier than raw JDBC. This happens inside a servlet. My first problem is that when the servlet container such as tomcat asks the servlet to shutdown, choosing to stop listening for Oracle alerts appears to be impossible without polling Oracle for the alert events.
Specifically, I have a thread that is blocked on a call to dbms_alert.waitany. How can I wake this thread up and have it cleanly shut down? I've tried closing the JDBCConnection in the hopes it would receive a connection-closed exception which my thread could simply ignore if being asked to shut down. But the call to JDBCConnection.close() simply hangs. I've tried a few other tricks to no avail. Documentation I've studied does not discuss the problem at all.
The only "solution" I've found is to pass the dbms_alert.waitany a one-second timeout parameter when waiting for alerts. This makes the thread wake up every second, at which time it will usually just find that the timeout occurred and start waiting again. But this creates an opportunity for it to check an exit flag and terminated itself.
Aside from wasting some CPU cycles this has the serious downside that it results in a remote call to Oracle across the network every second! That will no-doubt aggravate various people in IT as a serious load and I'm not sure how to articulate a good defense.
I'm really hoping that there's some way to wake up my thread without having it wait for a timeout. Otherwise is this not a serious defect?
There are other use cases for my package that are stumped by the same root problem. If I want to register for a new alert, I'd like to wake up my blocked thread, have it make the registration call, then call dbms_alert.waitany again. But this too requires waiting for the thread to wake up based on the timeout and the resulting trade-off between wasting resources and delaying the registration - a trade-off that has no good answer.
Is there any way I can get the call to dbms_alert.waitany to unblock with an error code or exception so this impossible decision becomes irrelevant?
Thanks

>
Specifically, I have a thread that is blocked on a call to dbms_alert.waitany. How can I wake this thread up and have it cleanly shut down?
>
You wake it up the way it is designed to be woken up: signal an alert from another thread.
That thread will 'wake up' when an alert is signaled. So when you want to shutdown set a 'shutdown' variable that the thread checks wheneve it wakes up.
Then use another thread to signal an alert. That alert will wake up your blocked thread, the thread will check the 'shutdown' variable and will take action based on the setting of that variable.
See the examples in the DBMS_ALERT section of the Oracle docs:
http://docs.oracle.com/cd/B28359_01/appdev.111/b28419/d_alert.htm
>
WAITANY Procedure
Call this procedure to wait for an alert to occur for any of the alerts for which the current session is registered.
>
You can register for your own 'JAVA SHUTDOWN' alert in addition to the alert your thread is now registered for. Then use the method I outline above to use the SIGNAL method to generate that 'JAVA SHUTDOWN' alert. That will wake your thread up so it can shut itself down.

Database alert Macro

Similar Messages

Maybe you are looking for