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.

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.

  • 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
    ------------------------------------------------------------------------------------------------------------------------------------

  • 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.

  • 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.

  • 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.

  • 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....

  • 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)

  • "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..".

  • Ossnet messages alert log

    Hello Experts,
    i am seeing following error messages in database alert log. based on error message OS process was not able to connect one of the cell server. is there any way to find why it is failing to connect cell server?
    OSPID: 27669: connect: ossnet: connection failed to server 192.168.10.11, result=5 (login: sosstcpreadtry failed) (difftime=1953)
    Mon Nov 05 17:35:16 2012
    OSPID: 27665: connect: ossnet: connection failed to server 192.168.10.11, result=5 (login: sosstcpreadtry failed) (difftime=1953)
    Mon Nov 05 17:35:17 2012
    OSPID: 18681: connect: ossnet: connection failed to server 192.168.10.11, result=5 (login: sosstcpreadtry failed) (difftime=1953)
    Mon Nov 05 17:42:22 2012
    OSPID: 12134: connect: ossnet: connection failed to server 192.168.10.11, result=5 (login: sosstcpreadtry failed) (difftime=1953)
    Mon Nov 05 17:42:24 2012
    OSPID: 20097: connect: ossnet: connection failed to server 192.168.10.11, result=5 (login: sosstcpreadtry failed) (difftime=1954)
    OSPID: 12134: connect: ossnet: connection failed to server 192.168.10.11, result=5 (login: sosstcpreadtry failed) (difftime=1953)
    OSPID: 20097: connect: ossnet: connection failed to server 192.168.10.11, result=5 (login: sosstcpreadtry failed) (difftime=1954)
    OSPID: 12134: connect: ossnet: connection failed to server 192.168.10.11, result=5 (login: sosstcpreadtry failed) (difftime=1954)
    please advice

    Hi 892564,
    i was wonder, how do you determine this is Cell server #7 ?The private network of your first exadata has a default range starting from 192.168.10.1 from the lowest compute node (db01).
    A halfrack contains 11 components in the private network (4 nodes and 7 cells).
    Hence 192.168.10.11 would be cell 7.
    For a full rack this IP would match to cell 3.
    Regards,
    Tycho

  • 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-

  • 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.xml or alert.log errors do not appear in EM

    Little puzzled here. Using 11.1.0.6 to test if alert errors will appear on 11.1.0.1 EM Grid pages. Simple ORA-1653 triggered via sql insert and then waited and waited. Nothing. I can use EM to open log file and to display the errors but no alerts are flagged on any of the pages.
    Is this a another bug?
    Roman

    You can read all about how the 11g alert log is monitored in: Monitoring 11g Database Alert Log Errors in Enterprise Manager [ID 949858.1]
    Yes, it describes some bugs (and workarounds) too.
    Eric

  • 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

Maybe you are looking for

  • Financial Reporting Batch Scheduler Failed To Send Email To Users. Version 11.1.2.1

    Created a batch and scheduled the report from Workspace to run. Scheduled batch ran successful but the Email is not generated for the user though we have provided the valid email address. Is this is known issue?

  • IBook G4 won't start up from DVD

    Greetings everyone, Thanks in advance for any help that you are able to provide. My problem is as follows: Last week I was working on my iBook when out of nowhere the screen started flashing between black and the screen. At this point the computer fr

  • Windows Update not working

    I have a couple of servers on Standard 2012R2 (a Domain Controller & File Server) virtualized on VMWare ESXi 5.1.  Server Manager tells me that they have never checked or updated (although they show 40 updates applied).  Set to download updates and n

  • Is the 2.0GHz worth it?

    Hey, I'm about to buy the imac 17inch intel model, and I was just wondering if it would be worth it to clunk down the additional cash for the 1 GHz or 2 GHz models. I plan on using the machine primarily for garage band, music composition/producing, a

  • Not connected to the Internet?

    Various applications give the error message that I am not connected to the internet.  Seems rather odd since I am typing this question on these forums using this same computer.  Overall problem is that the Weather app is no longer functioning for me.