Error in Standby alert log continuously

After I setup the Physical Standby and Logical Standby database, I found lots of errors showing in alert log of Standby database.
LOGMINER: Error 308 encountered, failed to read missing logfile /u01/oradata/arch2/primary/1_1_111111111.dbf
According to the doc, I set the values LOG_ARCHIVE_DEST_3 in case of role transition:
(for primary)
LOCATION=/u01/oradata/arch2/primary/ VALID_FOR=(STANDBY_LOGFILES,STANDBY_ROLE) DB_UNIQUE_NAME=primary(for standby)
LOCATION=/u01/oradata/arch2/standby/ VALID_FOR=(STANDBY_LOGFILES,STANDBY_ROLE) DB_UNIQUE_NAME=standbyWhen I run this command, the error keeps showing in the alert log continuously! Why does it look for the path "primary", but not "standby" ?
ALTER DATABASE START LOGICAL STANDBY APPLY IMMEDIATE;
Help! Does anyone know the problem? All new data can't be found in the logical standby now.
Thank you!

When I enable the LOG_ARCHIVE_DEST_STATE_3, the errors show in alert log again!
LOGMINER: Error 308 encountered, failed to read missing logfile /u01/oradata/arch2/primary/1_1_111111111.dbf
SELECT TYPE,STATUS FROM V$LOGSTDBY;
COORDINATOR
ORA-01291: missing logfile
here are my parameters:
Primary:
LOG_ARCHIVE_DEST_1='LOCATION=/u01/oradata/arch/ MANDATORY VALID_FOR=(ALL_LOGFILES,ALL_ROLES) DB_UNIQUE_NAME=primary'
LOG_ARCHIVE_DEST_2='SERVICE=ORCL_SB LGWR ASYNC VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE) DB_UNIQUE_NAME=standby'
LOG_ARCHIVE_DEST_3='LOCATION=/u01/oradata/arch2/primary/ VALID_FOR=(STANDBY_LOGFILES,STANDBY_ROLE) DB_UNIQUE_NAME=primary'
Standby:
LOG_ARCHIVE_DEST_1='LOCATION=/u01/oradata/arch/ MANDATORY VALID_FOR=(ONLINE_LOGFILES,ALL_ROLES) DB_UNIQUE_NAME=standby'
LOG_ARCHIVE_DEST_2='SERVICE=ORCL_PRI LGWR ASYNC VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE) DB_UNIQUE_NAME=primary'
LOG_ARCHIVE_DEST_3='LOCATION=/u01/oradata/arch2/standby/ VALID_FOR=(STANDBY_LOGFILES,STANDBY_ROLE) DB_UNIQUE_NAME=standby'
Why does the path in primary parameter file show in standby alert log??

Similar Messages

  • Errors in Standby Alert Log

    Dear All,
    We have 10gR2 RAC with Physical Data Guard environment using ASM and both have same disk group names. Lets say the primary database name is prim and stand by database name is stdby. We are getting the following errors in alert log file of standby:
    Clearing online redo logfile 9 +DG_DATAFILES_AND_FB/prim/onlinelog/group9_2a.rdo
    Clearing online log 9 of thread 2 sequence number 0
    Errors in file c:\oracle\product\10.2.0\admin\stdby\bdump\stdby1_mrp0_4288.trc:
    ORA-00313: Message 313 not found; No message file for product=RDBMS, facility=ORA; arguments: [9] [2]
    ORA-00312: Message 312 not found; No message file for product=RDBMS, facility=ORA; arguments: [9] [2] [+DG_DATAFILES_AND_FB/prim/onlinelog/group9_2a.rdo]
    ORA-17503: Message 17503 not found; No message file for product=RDBMS, facility=ORA; arguments: [2] [+DG_DATAFILES_AND_FB/prim/onlinelog/group9_2a.rdo]
    ORA-15173: entry 'prim does not exist in directory '/'
    Errors in file c:\oracle\product\10.2.0\admin\stdby\bdump\stdby1_mrp0_4288.trc:
    ORA-00344: Message 344 not found; No message file for product=RDBMS, facility=ORA; arguments: [+DG_DATAFILES_AND_FB/prim/onlinelog/group9_2a.rdo]
    ORA-17502: Message 17502 not found; No message file for product=RDBMS, facility=ORA; arguments: [4] [+DG_DATAFILES_AND_FB/prim/onlinelog/group9_2a.rdo]
    ORA-15173: entry 'prim' does not exist in directory '/'The errors show that the standby is trying to find files in directory +DG_DATAFILES_AND_FB/prim/onlinelog which apparently doesn’t exist on standby. Below is the result of query for redo logs on standby:
    SQL> SELECT group#, status, member FROM v$logfile where member like '%prim/%'
        GROUP#   STATUS         MEMEBER
             9                            +DG_DATAFILES_AND_FB/prim/onlinelog/group9_2a.rdo
             1                            +DG_DATAFILES_AND_FB/prim/standbylogs/sredo1.rdo
            10                           +DG_DATAFILES_AND_FB/prim/onlinelog/group10_1a.rdo
             2                            +DG_DATAFILES_AND_FB/prim/standbylogs/sredo2.rdo
             3                            +DG_DATAFILES_AND_FB/prim/standbylogs/sredo3.rdo
             4                            +DG_DATAFILES_AND_FB/prim/standbylogs/sredo4.rdo
            11                           +DG_DATAFILES_AND_FB/prim/onlinelog/group11_1a.rdo
            12                           +DG_DATAFILES_AND_FB/prim/onlinelog/group12_2a.rdo
    8 rows selected.  How we can get rid of this error?
    Best regards,

    Generally when we setup standby, are these directories created automatically (i mean '+DG_DATAFILES_AND_FB/prim and '+DG_DATAFILES_AND_FB/stdby) on standby? My understanding is that by default only '+DG_DATAFILES_AND_FB/stdby is created.
    What if i want to put all logs (that are in stdby and prim) in +DG_DATAFILES_AND_FB/stdby?What is the value of DB_CREATE_FILE_DEST and you also set DB_CREATE_ONLINE_LOG_DEST_<> value?
    Also i don't know whether it is relevant or not, but we performed a roll forward for standby using metalink doc id: 836986.1 (Steps to perform for Rolling forward a standby database using RMAN incremental backup when primary and standby are in ASM filesystem). But i am not sure whether the error started coming after that or not.
    But in the beginning for sure, there were no such errors. Just trying to put as much information as i can.Even though you are using same disk groups, But the sub directory names such as "prim","stby" are different,
    After you changed the values of DB_FILE_NAME_CONVERT/LOG_FILE_NAME_CONVERT have you bounced database ? They are static parameters.
    Bounce it and then start MRP, initally errors are expected even it happens during RMAN duplicate.
    logfile member shows in database but not on physical disk, not match
    if you haven't used RMAN duplicate then drop and create redo logs, this can be done at any time.

  • ORA-600 in standby alert log

    We have recently migrated our database from Solaris to Linux (RHEL5) and since this migration we are seeing weird errors related to archive log shipping to the remote standby site and a corresponding ORA-600 in the standby site.
    What's interesting is everything gets resolved by itself, it always seems to happen during the heavy database load when there is frequent log switch happening (~3 min). So initially it tries to archive to the remote site and it fails with the following error in the primary alert log.
    Errors in file /app/oracle/admin/UIIP01/bdump/uiip01_arc1_9772.trc:
    ORA-00272: error writing archive log
    Mon Jul 14 10:57:36 2008
    FAL[server, ARC1]: FAL archive failed, see trace file.
    Mon Jul 14 10:57:36 2008
    Errors in file /app/oracle/admin/UIIP01/bdump/uiip01_arc1_9772.trc:
    ORA-16055: FAL request rejected
    ARCH: FAL archive failed. Archiver continuing
    Mon Jul 14 10:57:36 2008
    ORACLE Instance UIIP01 - Archival Error. Archiver continuing.
    And then we see a ORA-600 on standby database related to this which complains about redo block corruption.
    Mon Jul 14 09:57:32 2008
    Errors in file /app/oracle/admin/UIIP01/udump/uiip01_rfs_12775.trc:
    ORA-00600: internal error code, arguments: [kcrrrfswda.11], [4], [368], [], [], [], [], []
    Mon Jul 14 09:57:36 2008
    And the trace file has this wonderful block corruption error..
    Corrupt redo block 424432 detected: bad checksum
    Flag: 0x1 Format: 0x22 Block: 0x000679f0 Seq: 0x000006ef Beg: 0x150 Cks:0xa2e5
    ----- Dump of Corrupt Redo Buffer -----
    *** 2008-07-14 09:57:32.550
    ksedmp: internal or fatal error
    ORA-00600: internal error code, arguments: [kcrrrfswda.11], [4], [368], [], [], [], [], []
    So ARC tries to resend this redo log again and it succeeds, end of the day all we have is a bunch of these ORA- errors in our alert logs, triggering off our monitors and these errors resolve themselves without any manual intervention, opened a tar with Oracle support as this is not affecting our primary database, they are in no hurry to get this one prioritized and also they are reluctant to accept that it's a bug that resolves itself.
    Just wanted to get it out here to see if anyone experienced a similar problem, let me know if you need any more details.
    As I said earlier this behaviour happens only during peak loads espceially when we have full 500M redo logs that are being archived.
    Thanks in Advance.

    Thanks Madrid!..
    I scoured thru these metalink notes before looking for possible solutions and almost all of them were closed citing a customer problem related to OS, firewall, network, etc or some were closed saying requested data not provided.
    Looks as if they were never successfully closed with a resolution.
    I just want to assure myself that the redo corruption that standby is reporting will not haunt me later, when I am doing a recovery or even a crash recovery using redo logs?..
    I have multiplexed my logs, just in case and have all the block checking parameters enabled on both primary and standby databases.
    Thanks,
    Ramki

  • Error in the alert Log

    Hi There,
    Recently I started seeing these errors in the alert log for one of the databases:
    Tue Aug 04 05:05:00 2009
    Errors in file c:\oracle\product\10.2.0\admin\xxxxxx\bdump\xxxxxx_j000_6104.trc:
    ORA-12012: error on auto execute of job 130961
    ORA-27370: job slave failed to launch a job of type EXECUTABLE
    ORA-27300: OS system dependent operation:accessing execution agent failed with status: 109
    ORA-27301: OS failure message: The pipe has been ended.
    ORA-27302: failure occurred at: sjsec 9
    ORA-27303: additional information: The pipe has been ended.
    So, I tried looking at the trace file associated with the error, and here is what I get:
    $ cat ebcd01_j000_6104.trc
    Dump file c:\oracle\product\10.2.0\admin\xxxxxx\bdump\xxxxxx_j000_6104.trc
    Tue Aug 04 05:05:00 2009
    ORACLE V10.2.0.3.0 - Production vsnsta=0
    vsnsql=14 vsnxtr=3
    Oracle Database 10g Release 10.2.0.3.0 - Production
    Windows Server 2003 Version V5.2 Service Pack 1
    CPU : 4 - type 586, 2 Physical Cores
    Process Affinity : 0x00000000
    Memory (Avail/Total): Ph:1095M/4095M, Ph+PgF:7747M/12110M, VA:1367M/2047M
    Instance name: ebcd01
    Redo thread mounted by this instance: 1
    Oracle process number: 53
    Windows thread id: 6104, image: ORACLE.EXE (J000)
    *** ACTION NAME:(DEL_ARCH_EBCP01) 2009-08-04 05:05:00.191
    *** MODULE NAME:(DBMS_SCHEDULER) 2009-08-04 05:05:00.191
    *** SERVICE NAME:(SYS$USERS) 2009-08-04 05:05:00.191
    *** SESSION ID:(871.15642) 2009-08-04 05:05:00.191
    *** 2009-08-04 05:05:00.191
    ORA-12012: error on auto execute of job 130961
    ORA-27370: job slave failed to launch a job of type EXECUTABLE
    ORA-27300: OS system dependent operation:accessing execution agent failed with status: 109
    ORA-27301: OS failure message: The pipe has been ended.
    ORA-27302: failure occurred at: sjsec 9
    ORA-27303: additional information: The pipe has been ended.
    I'm not sure what job is causing this as there is no reference and also not sure how to resolve this issue!! How can I properly trace back these errors? Any ideas or tips to what should I do?
    I'm running 10.2.0.3 database on windows 2003 server.
    Thanks

    I found the problem.. the executable job was referring to a none existing batch file..
    I have refreshed the database from production some time ago and the jobs I have setup are referring to production scripts and paths (which we didnt have on dev)..
    This is now resolved.
    Thanks

  • "Error in the alert log file " - please help

    Hi ALL,
    I am getting following errors in the alert log frequently.
    My database version is:
    Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - 64bi
    PL/SQL Release 10.2.0.1.0 - Production
    CORE 10.2.0.1.0 Production
    TNS for IBM/AIX RISC System/6000: Version 10.2.0.1.0 - Productio
    NLSRTL Version 10.2.0.1.0 - Production
    Thu Aug 30 16:58:19 2007
    Memory Notification: Library Cache Object loaded into SGA
    Heap size 2172K exceeds notification threshold (2048K)
    KGL object name :select object_name from all_objects where object_name='TOAD_PROFILER' and object_type='PACKAGE'
    Thu Aug 30 17:09:36 2007
    ************************************************************************************

    Additionally you can visit here:
    Alert Error from trc files--Heap size 5236K exceeds notification threshold
    geting error in alert log file
    Adith

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

  • Excluding ORA-00060 errors from Generic Alert Log Error in OEM

    Hi,
    I want to remove the alerts for ORA-00060 errors from OEM Alerts. In "Generic Alert Log Error" the current expression for Warning is ORA-0*(600?|7445|4[0-9][0-9][0-9])[^0-9]. How should I change this expression so that it will not send alerts for ORA-00060. I am not much aware of perl :-). Please help me with the expression.
    Target Type=dbname
    Host=host
    Metric=Generic Alert Log Error
    Metric Value=ORA-00060: Deadlock detected. More info in
    Time/Line Number=Mon Nov 2 10:02:54 2009/134883
    Timestamp=Nov 2, 2009 10:17:14 AM EST
    Severity=Warning
    Message=ORA-error stack (00060) logged in /eb_rdo0_p/oraadmin/pnoltp/bdump/alert_.log.
    Notification Rule Name=Database Alert
    Notification Rule Owner=SYSMAN
    Notification Count=1
    Thanks,
    Varma

    this is default monitored objects.
    To stop monitoring for this object, clear the Critical and Warning threshold values and click Continue.

  • Recovery is repairing media corrupt block x of file x in standby alert log

    Hi,
    oracle version:8.1.7.0.0
    os version :solaris  5.9
    we have oracle 8i primary and standby database. i am getting erorr in alert log file:
    Thu Aug 28 22:48:12 2008
    Media Recovery Log /oratranslog/arch_1_1827391.arc
    Thu Aug 28 22:50:42 2008
    Media Recovery Log /oratranslog/arch_1_1827392.arc
    bash-2.05$ tail -f alert_pindb.log
    Recovery is repairing media corrupt block 991886 of file 179
    Recovery is repairing media corrupt block 70257 of file 184
    Recovery is repairing media corrupt block 70258 of file 184
    Recovery is repairing media corrupt block 70259 of file 184
    Recovery is repairing media corrupt block 70260 of file 184
    Recovery is repairing media corrupt block 70261 of file 184
    Thu Aug 28 22:48:12 2008
    Media Recovery Log /oratranslog/arch_1_1827391.arc
    Thu Aug 28 22:50:42 2008
    Media Recovery Log /oratranslog/arch_1_1827392.arc
    Recovery is repairing media corrupt block 500027 of file 181
    Recovery is repairing media corrupt block 500028 of file 181
    Recovery is repairing media corrupt block 500029 of file 181
    Recovery is repairing media corrupt block 500030 of file 181
    Recovery is repairing media corrupt block 500031 of file 181
    Recovery is repairing media corrupt block 991837 of file 179
    Recovery is repairing media corrupt block 991838 of file 179
    how i can resolve this.
    [pre]
    Thanks
    Prakash
    Edited by: user612485 on Aug 28, 2008 10:53 AM                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       

    Dear satish kandi,
    recently we have created index for one table with nologgign option, i think for that reason i am getting that error.
    if i run dbv utility on the files which are shown in alert log file i am getting the following results.
    bash-2.05$ dbv file=/oracle15/oradata/pindb/pinx055.dbf blocksize=4096
    DBVERIFY: Release 8.1.7.0.0 - Production on Fri Aug 29 12:18:27 2008
    (c) Copyright 2000 Oracle Corporation. All rights reserved.
    DBVERIFY - Verification starting : FILE = /oracle15/oradata/pindb/pinx053.dbf
    Block Checking: DBA = 751593895, Block Type =
    Found block already marked corrupted
    Block Checking: DBA = 751593896, Block Type =
    .DBVERIFY - Verification complete
    Total Pages Examined : 1048576
    Total Pages Processed (Data) : 0
    Total Pages Failing (Data) : 0
    Total Pages Processed (Index): 1036952
    Total Pages Failing (Index): 0
    Total Pages Processed (Other): 7342
    Total Pages Empty : 4282
    Total Pages Marked Corrupt : 0
    Total Pages Influx : 0
    bash-2.05$ dbv file=/oracle15/oradata/pindb/pinx053.dbf blocksize=4096
    DBVERIFY: Release 8.1.7.0.0 - Production on Fri Aug 29 12:23:12 2008
    (c) Copyright 2000 Oracle Corporation. All rights reserved.
    DBVERIFY - Verification starting : FILE = /oracle15/oradata/pindb/pinx054.dbf
    Block Checking: DBA = 759492966, Block Type =
    Found block already marked corrupted
    Block Checking: DBA = 759492967, Block Type =
    Found block already marked corrupted
    Block Checking: DBA = 759492968, Block Type =
    .DBVERIFY - Verification complete
    Total Pages Examined : 1048576
    Total Pages Processed (Data) : 0
    Total Pages Failing (Data) : 0
    Total Pages Processed (Index): 585068
    Total Pages Failing (Index): 0
    Total Pages Processed (Other): 8709
    Total Pages Empty : 454799
    Total Pages Marked Corrupt : 0
    Total Pages Influx : 0
    bash-2.05$ dbv file=/oracle15/oradata/pindb/pinx054.dbf blocksize=4096
    DBVERIFY: Release 8.1.7.0.0 - Production on Fri Aug 29 12:32:28 2008
    (c) Copyright 2000 Oracle Corporation. All rights reserved.
    DBVERIFY - Verification starting : FILE = /oracle15/oradata/pindb/pinx055.dbf
    Block Checking: DBA = 771822208, Block Type =
    Found block already marked corrupted
    Block Checking: DBA = 771822209, Block Type =
    Found block already marked corrupted
    Block Checking: DBA = 771822210, Block Type =
    .DBVERIFY - Verification complete
    Total Pages Examined : 1048576
    Total Pages Processed (Data) : 0
    Total Pages Failing (Data) : 0
    Total Pages Processed (Index): 157125
    Total Pages Failing (Index): 0
    Total Pages Processed (Other): 4203
    Total Pages Empty : 887248
    Total Pages Marked Corrupt : 0
    Total Pages Influx : 0
    My doubts are :
    1.if i drop the index and recreate the index with logging option will this error won't repeat in alert log file
    2.in future if i activate the standby database will database is going to open without any error.
    Thanks
    Prakash
    .

  • Oradism not set up correctly error in the alert log in 9.2.0.4

    Hello,
    I have installed 9.2.0.4 patch on top of 9.2.0.1 database.
    The O/S is Solaris 5.9
    The database is set to work with:
    workarea_size_policy=AUTO.
    The database is not working properly – compared to other machines we have.
    After looking in the alert log I found the following error popping after restart:
    WARNING: -------------------------------
    WARNING: oradism not set up correctly.
    Dynamic ISM can not be locked. Please
    setup oradism, or unset sga_max_size.
    [diagnostic 0, 16, 5001]
    I found the following two notes on the subject, contradicting each other and also contradicting the status of the machine:
    Note:151222.1
    http://metalink.oracle.com/metalink/plsql/ml2_documents.showDocument?p_database_id=NOT&p_id=151222.1
    Telling me not to do the below procedure on 9.2.0.4, though I get the same error and miss the required etc entries specified.
    Note:262886.1
    http://metalink.oracle.com/metalink/plsql/ml2_documents.showDocument?p_database_id=NOT&p_id=262886.1
    Telling me to copy oradism.sav to oradism and I already have those.
    Can you please supply a full and DETAILED procedure regarding what should I do, in case it is not a procedure, please specify how I should solve the ‘oradism not set up correctly’ error.
    Tal Olier
    [email protected]

    Hi Tal,
    Just looked at the notes you referred to. The first doesn't apply to 9.2.0.4. as you state. The other note is for 9.2.0.4e (note the "e", stands for embedded). This "e" release is not what you have, so that note doesn't apply either.
    The AR that I referred to is for 10g, but the 9iR2 info is the same. You need to make sure that $ORACLE_HOME/bin/oradism is owned by root.

  • Ora -3113 error in the alert log

    Hi ,
    We are getting ORA-3113 error in the alertlog and i pasted below alert log entry.
    VERSION INFORMATION:
    TNS for Linux: Version 11.1.0.7.0 - Production
    Unix Domain Socket IPC NT Protocol Adaptor for Linux: Version 11.1.0.7.0 - Production
    Oracle Bequeath NT Protocol Adapter for Linux: Version 11.1.0.7.0 - Production
    TCP/IP NT Protocol Adapter for Linux: Version 11.1.0.7.0 - Production
    Time: 27-JAN-2011 16:11:25
    Tracing not turned on.
    Tns error struct:
    ns main err code: 12535
    TNS-12535: TNSperation timed out
    ns secondary err code: 12560
    nt main err code: 505
    TNS-00505: Operation timed out
    nt secondary err code: 110
    nt OS err code: 0
    Client address: (ADDRESS=(PROTOCOL=tcp)(HOST=10.100.72.127)(PORT=2844))
    Thu Jan 27 16:13:55 2011
    opidcl aborting process unknown ospid (18585_47319544949952) due to error ORA-3113
    Thu Jan 27 16:14:03 2011
    Thread 2 advanced to log sequence 2022 (LGWR switch)
    Current log# 4 seq# 2022 mem# 0: +DATA/systemprod/onlinelog/group_4.269.736019283
    Current log# 4 seq# 2022 mem# 1: +FLASH1/systemprod/onlinelog/group_4.262.736019285
    Thu Jan 27 16:14:13 2011
    opidcl aborting process unknown ospid (14096_47207734746304) due to error ORA-3113
    Thu Jan 27 16:16:34 2011
    Thread 2 advanced to log sequence 2023 (LGWR switch)
    Current log# 8 seq# 2023 mem# 0: +DATA/systemprod/onlinelog/group_8.319.736018999
    Current log# 8 seq# 2023 mem# 1: +FLASH1/systemprod/onlinelog/group_8.3138.736018999
    Thu Jan 27 16:19:33 2011
    Thread 2 advanced to log sequence 2024 (LGWR switch)
    Current log# 3 seq# 2024 mem# 0: +DATA/systemprod/onlinelog/group_3.268.736019049
    Current log# 3 seq# 2024 mem# 1: +FLASH1/systemprod/onlinelog/group_3.261.736019051
    Thu Jan 27 16:22:17 2011
    What could be the workaround to resove this issue
    Regards
    Prem

    ORA-00600/ORA-07445/ORA-03113 = Oracle bug => search on Metalink and/or call Oracle support

  • Error in the alert.log file

    hi,
    my database is down , when chk the alert log i found the below error
    please help me
    Sun Mar 8 20:06:01 2009
    Errors in file /busdata/sp01/eur1/_lgi/oracle/vol1/admin/udump/sp01eur1_ora_3731494.trc:
    ORA-27037: unable to obtain file status
    IBM AIX RISC System/6000 Error: 2: No such file or directory
    Additional information: 4
    Shutting down instance: further logons disabled
    Shutting down instance (immediate)
    License high water mark = 5
    Sun Mar 8 20:06:04 2009
    ALTER DATABASE CLOSE NORMAL
    ORA-1109 signalled during: ALTER DATABASE CLOSE NORMAL...
    Sun Mar 8 20:06:04 2009
    ALTER DATABASE DISMOUNT
    Completed: ALTER DATABASE DISMOUNT
    ARCH: Archiving is disabled

    madhukrishna wrote:
    i am not authorised to start the databse or any servicesThen You have only one choice - please contact Your system administrator and he will investigate what happened, why and how to solve that.
    We can't help or say what was wrong if You have no rights to do anything, even look at trace files.

  • 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

  • Create custom rule: Looking for ORA errors in the alert log

    I would like to create a rule to notify me when ORA errors are generated to the alert log. When I try to create a rule, I seem to only be able to choose from predefined lists. Has anyone configured a rule for this?

    Grrr. This is for 10.2 Grid:
    Go to databases --> select your database
    Under Diagnostic summary, you'll see:
    Alert Log 28-Dec-2006 09:19:48
    The date part is a clickable link, click on it. Scroll to the bootom of the next page and click on:
    "Generic Alert Log Error Monitoring Configuration"
    Now read the page very carefully, its all self explanatory. The reason who haven't had some errors reported is because of that filter. Now set it up the way you want it.
    Good luck
    Bazzza

  • Errors appeared in alert log file should send an email

    Hi,
    I have one requirement to do, as i am new dba, i dont know how to do this,
    sendmail is configured on my unix machine, but dont know how to send the errors appeared in alert logfile should send an email to administrator.
    daily, it has to check the errors in alert log file, if any errors occurs(ORA- errors or WARNING errors) should send an email to administrator.
    please help me how to do it

    Hi,
    There are many methods for interrogating the alert log and sending e-mail. Here are my notes:
    http://www.dba-oracle.com/t_alert_log_monitoring_errors.htm
    - PL/SQL or Java with e-mail alert: http://www.dba-village.com/village/dvp_papers.PaperDetails?PaperIdA=2383
    - Shell script - Database independent and on same level as alert log file and e-mail.
    - OEM - Too inflexible for complex alert log analysis rules
    - SQL against the alert log - You can define the alert log file as an external table and detect messages with SQL and then e-mail.
    Because the alert log is a server side flat file and because e-mail is also at the OS-level, I like to use a server side scell script. It's also far more robust then OEM, especially when combining and evaluating multiple alert log events. Jon Emmons has great notes on this:
    http://www.lifeaftercoffee.com/2007/12/04/when-to-use-shell-scripts/
    If you are on Windows, see here:
    http://www.dba-oracle.com/t_windows_alert_log_script.htm
    For UNIX, Linux, Jon Emmons has a great alert log e-mail script.
    Hope this helps . . . .
    Donald K. Burleson
    Oracle Press author

  • Errors in DB alert log for distributed transactions

    Hi,
    I am receiving the following type of errors regularly in one of our development databases:
    Errors in file e:\oracle\product\diag\rdbms\agdev10g\agdev10g\trace\agdev10g_reco_16356.trc:
    ORA-12514: TNS:listener does not currently know of service requested in connect descriptor
    ORA-02062: distributed recovery received DBID d672931d, expected 2d7b9dec
    ORA-12154: TNS:could not resolve the connect identifier specified
    ORA-12500: TNS:listener failed to start a dedicated server process
    ORA-12154: TNS:could not resolve the connect identifier specified
    From researching on the net it looks like it may have something to do with distributed transactions and database links however I'm not sure how to proceed to diagnose the problem and find out where the issue is. Can anyone help?
    Thanks
    Adam
    Edited by: Adam J. Sawyer on 27/05/2010 16:57

    SQL*Net typically involves two systems so post following details for both systems
    Post Operating System (OS) name & version for DB server system.
    Post results of
    SELECT * from v$version
    or post Oracle version to 4 decimal places
    oerr ora 12514
    12514, 00000, "TNS:listener does not currently know of service requested in connect descriptor"
    // *Cause:  The listener received a request to establish a connection to a
    // database or other service. The connect descriptor received by the listener
    // specified a service name for a service (usually a database service)
    // that either has not yet dynamically registered with the listener or has
    // not been statically configured for the listener.  This may be a temporary
    // condition such as after the listener has started, but before the database
    // instance has registered with the listener.
    // *Action:
    //  - Wait a moment and try to connect a second time.
    //  - Check which services are currently known by the listener by executing:
    //    lsnrctl services <listener name>
    //  - Check that the SERVICE_NAME parameter in the connect descriptor of the
    //    net service name used specifies a service known by the listener.
    //  - If an easy connect naming connect identifier was used, check that
    //    the service name specified is a service known by the listener.
    //  - Check for an event in the listener.log file.
    bcm@bcm-laptop:~$ oerr ora 2062
    02062, 00000, "distributed recovery received DBID %s, expected %s"
    // *Cause: a database link at a coordinator no longer points to the expected
    //         database.  Link may have been redefined, or a different DB mounted.
    // *Action: restore link definition or remote database.
    bcm@bcm-laptop:~$ oerr ora 12154
    12154, 00000, "TNS:could not resolve the connect identifier specified"
    // *Cause:  A connection to a database or other service was requested using
    // a connect identifier, and the connect identifier specified could not
    // be resolved into a connect descriptor using one of the naming methods
    // configured. For example, if the type of connect identifier used was a
    // net service name then the net service name could not be found in a
    // naming method repository, or the repository could not be
    // located or reached.
    // *Action:
    //   - If you are using local naming (TNSNAMES.ORA file):
    //      - Make sure that "TNSNAMES" is listed as one of the values of the
    //        NAMES.DIRECTORY_PATH parameter in the Oracle Net profile
    //        (SQLNET.ORA)
    //      - Verify that a TNSNAMES.ORA file exists and is in the proper
    //        directory and is accessible.
    //      - Check that the net service name used as the connect identifier
    //        exists in the TNSNAMES.ORA file.
    //      - Make sure there are no syntax errors anywhere in the TNSNAMES.ORA
    //        file.  Look for unmatched parentheses or stray characters. Errors
    //        in a TNSNAMES.ORA file may make it unusable.
    //   - If you are using directory naming:
    //      - Verify that "LDAP" is listed as one of the values of the
    //        NAMES.DIRETORY_PATH parameter in the Oracle Net profile
    //        (SQLNET.ORA).
    //      - Verify that the LDAP directory server is up and that it is
    //        accessible.
    //      - Verify that the net service name or database name used as the
    //        connect identifier is configured in the directory.
    //      - Verify that the default context being used is correct by
    //        specifying a fully qualified net service name or a full LDAP DN
    //        as the connect identifier
    //   - If you are using easy connect naming:
    //      - Verify that "EZCONNECT" is listed as one of the values of the
    //        NAMES.DIRETORY_PATH parameter in the Oracle Net profile
    //        (SQLNET.ORA).
    //      - Make sure the host, port and service name specified
    //        are correct.
    //      - Try enclosing the connect identifier in quote marks.
    //   See the Oracle Net Services Administrators Guide or the Oracle
    //   operating system specific guide for more information on naming.
    bcm@bcm-laptop:~$ oerr ora 12500
    12500, 00000, "TNS:listener failed to start a dedicated server process"
    // *Cause:  The process of starting up a dedicated server process failed.
    // The executable could not be found or the environment may be set up
    // incorrectly.
    // *Action: Turn on tracing at the ADMIN level and reexecute the operation.
    // Verify that the ORACLE Server executable is present and has execute
    // permissions enabled. Ensure that the ORACLE environment is specified
    // correctly in LISTENER.ORA. The Oracle Protocol Adapter that is being
    // called may not be installed on the local hard drive.  Please check that
    // the correct Protocol Adapter are successfully linked.
    // If error persists, contact Oracle Customer Support.What explicit SQL or command trigger these errors?

Maybe you are looking for

  • ADOBE Interactive Form in webdynpro not allowing to enter value

    Hi,      I have developed a Adobe interactive  form in SFP and then i developed webdynpro component , then integrated into webdynpro. while running the webdynpro application which is showing the adobeform but the input fields are not allowed to enter

  • Is this a new problem for the zen mic

    I havent found anything about this on the forum but I have to agree that I didnt search a lot , but since a couple of days, I got a new problem on my micro, it started skipping part into some songs then would go back and then skip some parts, it's ve

  • URGENT:: A Concern on output value in the report!!!

    Hi All, I have a concern on the following requirement: Business requirement :            Total Dollar Value = (Actual Quantity – Book Quantity)  x  (Standard Price / Price Unit)                   = (242 – 321) x  (5967.55 / 1000)                   =

  • WLC guest configuration

    I have 4402(50) with 25 nos. 1242 LWAP, I have two guest wlan (guest1 & guest2) with different dynamic interface and vlan. both dhcp scopes assigned in wlc mgmt. guest1 wlan is working properly, guest2 is not authenticating with web authentication. I

  • Compile Error from Forte 6.0 Update 1

    Hi, We have the following situation: // CORBA.h file struct { class Object; typedef Object* Object_ptr; // Our .h file namespace OSP { typedef IDLSEQUENCE_OSP_SetListElement SetList; typedef IDLSEQUENCE_OSP_SetListElement_var SetList_var; // Our .C f