RAC- DR site is generating huge Alert logs

Hi Folks,
Please help me getting solution for below error coming up in Alert log of stanby server. although the logs are shipping correctly and log sequence number is same on both prod and standby.
But i am worrind because of below error cming continuously from past 3-4 days:
Errors in file /oracle/app/product/10.2.0/db_1/admin/icx/udump/icx1_rfs_9287.trc:
ORA-00314: log 11 of thread 2, expected sequence# 8200 doesn't match 0
ORA-00312: online log 11 thread 2: '+DG1/icxstandby/onlinelog/group_11.1267.698943109'
ORA-00314: log 11 of thread 2, expected sequence# 8200 doesn't match 0
ORA-00312: online log 11 thread 2: '+DG1/icxstandby/onlinelog/group_11.1270.698943107'
Mon Aug 30 12:15:22 2010
Errors in file /oracle/app/product/10.2.0/db_1/admin/icx/udump/icx1_rfs_9287.trc:
ORA-00314: log 6 of thread 1, expected sequence# 10919 doesn't match 10904
ORA-00312: online log 6 thread 1: '+DG1/icxstandby/onlinelog/group_6.265.694205613'
ORA-00314: log 6 of thread 1, expected sequence# 10919 doesn't match 10904
ORA-00312: online log 6 thread 1: '+DG1/icxstandby/onlinelog/group_6.264.694205613'
Mon Aug 30 12:15:22 2010
Errors in file /oracle/app/product/10.2.0/db_1/admin/icx/udump/icx1_rfs_9287.trc:
ORA-00314: log 6 of thread 1, expected sequence# 10919 doesn't match 10904
ORA-00312: online log 6 thread 1: '+DG1/icxstandby/onlinelog/group_6.265.694205613'
ORA-00314: log 6 of thread 1, expected sequence# 10919 doesn't match 10904
ORA-00312: online log 6 thread 1: '+DG1/icxstandby/onlinelog/group_6.264.694205613'
Mon Aug 30 12:15:22 2010
Errors in file /oracle/app/product/10.2.0/db_1/admin/icx/udump/icx1_rfs_9287.trc:
ORA-00314: log 11 of thread 2, expected sequence# 8200 doesn't match 0
ORA-00312: online log 11 thread 2: '+DG1/icxstandby/onlinelog/group_11.1267.698943109'
ORA-00314: log 11 of thread 2, expected sequence# 8200 doesn't match 0
ORA-00312: online log 11 thread 2: '+DG1/icxstandby/onlinelog/group_11.1270.698943107'
Mon Aug 30 12:15:22 2010
Errors in file /oracle/app/product/10.2.0/db_1/admin/icx/udump/icx1_rfs_9287.trc:
ORA-00314: log 11 of thread 2, expected sequence# 8200 doesn't match 0
ORA-00312: online log 11 thread 2: '+DG1/icxstandby/onlinelog/group_11.1267.698943109'
ORA-00314: log 11 of thread 2, expected sequence# 8200 doesn't match 0
ORA-00312: online log 11 thread 2: '+DG1/icxstandby/onlinelog/group_11.1270.698943107'
Please revert asap. i appreciate ur understanding.
regards,
J K J

are you sure DR is in sync .
I see bellow in metalink [ID 18373.1]
Error: ORA-314
Text: log <name> of thread <num>, expected sequence # <num> does not match
<num>
Cause: The online log is out of sequence, probably because it is corrupted or
an old version.
Action: For more information on recovery procedures, see the <Oracle Server
Administrator's Guide>.
*** Important: The notes below are for experienced users - See Note:22080.1
Support Notes:
If the database is from a clean shutdown and no restore has been
performed then it may be just the Online logs have been over-written.
A useful quick check is:
select * from v$recover_file;
If this shows no rows then the following steps may be useful:
a. If you do not know why the current online log is an old copy
take a backup of all existing datafiles (V$datafile),
controlfile (v$controlfile) and the online logs (even though old)
(v$logfile). This ensures you can never get into a worse position
than you are in now.
b. Once you have a safe backup copy:
startup mount
recover database until cancel;
## This should report "Media recovery complete."
alter database open resetlogs;
## The database should open here unless there is some other problem.
c. Now shutdown take a FULL backup of all datafiles / logfiles and
controlfile as you cannot perform recoveries through a resetlogs.

Similar Messages

  • Trace file with different name is alert log file.

    I am strange today
    i found a trace file generated in alert log file with name
    /bdump/stlbas_cjq0_1880.trc:
    but when i am trying to find out in bdump folder i cannot found
    any file with this named. instead i found /bdump/stlbas_cjq0_1853.trc
    is there any possibility of being this scenario ?
    database version:- 10.2.0.4
    Os:- sun solaries spark 64 bits
    Regards
    Halim

    The trace file has been removed/deleted from an OS user. I think you should verify that with OS logs.
    Thanks

  • Job number from alert log file to information

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

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

  • Re-locate Alert log file

    My alert log files seems to be generating somewhere else.
    I am using a PFile to startup. Seems someone played around with the PFile.
    I need to generate the alert logs in a folder as specified by me:
    I have set the following parameters as such, but yet the alert log file doesn't generate in the bdump folder.
    background_dump_dest=C:\oracle\admin\db1\bdump
    core_dump_dest=C:\oracle\admin\db1\cdump
    user_dump_dest=C:\oracle\admin\db1\udump
    Is there any other parameter I need to fidget with?

    I am not using an SPfile. The Pfile is definetely being used for starting the instance.
    background_dump_dest=C:\oracle\admin\db1\bdump
    The other background trace files are being generated here, except for the alert log.
    Alert log is being generated in: C:\oracle\admin\practice\bdump.
    Now just so that i am not makin any human blunders I checked the following to be double sure:
    SQL> select distinct isspecified from V$spparameter;
    ISSPEC
    FALSE
    This means the Pfile is being used.
    SQL> show parameter background_dump
    NAME TYPE VALUE
    background_dump_dest string C:\oracle\admin\db1\bdump
    This verifies the destination folder.
    PLEASE HELP!

  • Database generating a large number of ORA-1403 errors in Alert Log & trace

    Hi,
    Many ORA-1403: no data found messages appear in the alert log, but users are not seeing this error on their screens. The errors are only generated in the alert log along with an associated trace file.
    We have not set the "set events 1403 trace" for either system or session level.
    I confirmed this with the initialization file.
    The database is generating huge trace files..
    Database version: 10.1.0.4.2
    Errors in Trace:
    ksedmp: internal or fatal error
    ORA-01403: no data found
    Regards,
    Chandan

    Hi,
    Check Note:271490.1. Try to issue
    alter system set events '1403 trace name errorstack off'; as recommended in that Note.
    If this not help then check other possible cases of this on Metalink or address this problem to Oracle support directly.
    Best Regards,
    Alex

  • Database Generating Errors in Alert Log

    Hie,
    my db is generating errors in the alert log
    Errors in file /export/home/app/oracle/diag/rdbms/ORACLE_SID/ORACLE_SID/trace/ORACLE_SID_j000_15845.trc (incident=44144):
    ORA-00600: internal error code, arguments: [kdsgrp1], [], [], [], [], [], [], [], [], [], [], []
    ORA-00001: unique constraint (SYSMAN.PK_MGMT_JOB_EXECUTION) violated
    DDE: Problem Key 'ORA 600 [13011]' was completely flood controlled (0x4)
    Further messages for this problem key will be suppressed for up to 10 minutes
    looking forward to your assistance
    Mike

    Tue May 22 12:55:56 2012
    Adjusting the default value of parameter parallel_max_servers
    from 960 to 285 due to the value of parameter processes (300)
    Starting ORACLE instance (normal)
    Tue May 22 13:00:16 2012
    Adjusting the default value of parameter parallel_max_servers
    from 960 to 285 due to the value of parameter processes (300)
    Starting ORACLE instance (normal)
    LICENSE_MAX_SESSION = 0
    LICENSE_SESSIONS_WARNING = 0
    Shared memory segment for instance monitoring created
    Picked latch-free SCN scheme 3
    Using LOG_ARCHIVE_DEST_1 parameter default value as /export/home/app/oracle/product/11.2.0/dbhome_1/dbs/arch
    Autotune of undo retention is turned on.
    IMODE=BR
    ILAT =52
    LICENSE_MAX_USERS = 0
    SYS auditing is disabled
    Starting up:
    Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production
    With the Partitioning, OLAP, Data Mining and Real Application Testing options.
    ORACLE_HOME = /export/home/app/oracle/product/11.2.0/dbhome_1
    System name:     SunOS
    Node name:     server_1
    Release:     5.10
    Version:     Generic_141445-09
    Machine:     i86pc

  • Rac Alert log message '

    Dear All
    My database is running on RAC configuration and the version is 10.1.0.5
    Everyday i come across this error in the alert log of both the instances,
    Unable to restore resource manager plan to '':
    ORA-02097: parameter cannot be modified because specified value is invalid
    ORA-00439: feature not enabled: Database resource manager
    pls help me if u have come across this error

    Check metalink note 735798.1
    HTH...

  • How to check instance alert.log in RAC 10g ASM environment?

    i know to use Grid control or OEM check instance alert.log?
    But since in ASM the alert.log is not recognized, how to check it in OS level just like regular non-RAC checking?
    or the best way to check it ?
    thanks a lot!

    user620464 wrote:
    i know to use Grid control or OEM check instance alert.log?
    But since in ASM the alert.log is not recognized, how to check it in OS level just like regular non-RAC checking?
    or the best way to check it ?
    thanks a lot!Well if you mean that you have put the alert over asm storage than where did it mention to put alert file over ASM? Is not like an o/s where one can go and read the file and surely, neither we need striping or mirroring of it either. I am not sure that there is any way to do so over ASM storage.
    HTH
    Aman....

  • Checkpoint not complete in alert log file Oracle 11gR2 RAC

    Hi,
    I found checkpoint not complete in alert log file, almost every 3 seconds .
    In metalink i saw for this error, archive_lag_target=0, already this value was set to 0 in my database.
    We have 7 redo log groups for each instance, each group is of two redo log files, each file size is 50m.
    To avoid this error what i need to do..........
    please help me..................

    When you "checkpoint not complete" messages in your alert log this normally means your online redo logs are defined too small to handle the load and you have filled and need to switch to a new online redo log before the checkpoint triggered by the previous log switch has been completed.
    Increasing your online redo log size is normally the fix for this.
    HTH -- Mark D Powell --
    PS - The following Oracle support document may also apply:
    Checkpoint Not Complete In Alert.log Due To Setting Of Archive_lag_target [ID 435780.1]
    Edited by: Mark D Powell on Nov 7, 2011 8:29 AM

  • "found dead shared server" in alert.log

    Hi.
    I am getting the following message in the alert log of 10.2.0.2 database.
    Fri Feb 2 11:13:54 2007
    found dead shared server 'S005', pid = (32, 3)
    Fri Feb 2 11:14:24 2007
    found dead shared server 'S005', pid = (32, 4)
    Fri Feb 2 11:59:48 2007
    found dead shared server 'S001', pid = (11, 1)
    found dead shared server 'S005', pid = (32, 5)
    Fri Feb 2 12:00:04 2007
    found dead shared server 'S001', pid = (80, 165)
    found dead shared server 'S001', pid = (80, 166)
    What does it mean actaully...
    will it affect(what impact) my database.
    Thanks
    JD

    Hi,
    Are you using MTS feature? If yes,
    Then as given in the site:
    http://searchoracle.techtarget.com/tip/0,289483,sid41_gci1018471,00.html
    major issue I have seen with MTS is the dispatcher process getting abruptly killed. For some unknown reason the dispatcher process all of a sudden dies, killing the connected sessions. The following is an extract from the alert.log file for one such error:
    Wed Sep 8 09:07:35 2004
    Errors in file /u01/bdump/abc_d050_521.trc:
    ORA-07445: exception encountered: core dump [00000001026BA2D4] [SIGSEGV] [Address
    not mapped to object] [0x000000018] [] []
    Wed Sep 8 09:07:45 2004
    found dead dispatcher 'D050', pid = (667, 207)
    The dead dispatcher process is restarted once pmon cleans the in-doubt sessions. The workaround for this issue is to turn off the DCD (dead connection detection) feature. Set SQLNET.EXPIRE_TIME = 0 in sqlnet.ora file. This issue occurred in v9.2.0.4 and v9.2.0.5 and Oracle is currently working to resolve the same.
    I think you are not using MTS feature, otherwise you would have received errors
    like above & trace file would have been generated & error.ORA-07445
    If you are not using MTS feature,
    set the initialization parameter shared_servers = 0. also make sure that the parameter dispatcher is not set (it has no default) to anything.
    Message was edited by:
    Seema

  • 오라클 10g 장애 관련 alert log 파일좀 올려봅니다.

    Sun Dec 10 03:11:05 2006
    Process J000 died, see its trace file
    Sun Dec 10 03:11:05 2006
    kkjcre1p: unable to spawn jobq slave process
    Sun Dec 10 03:11:05 2006
    Errors in file c:\oracle\product\10.2.0\admin\golf\bdump\golf1_cjq0_4704.trc:
    Process J000 died, see its trace file
    Sun Dec 10 03:11:11 2006
    kkjcre1p: unable to spawn jobq slave process
    Sun Dec 10 03:11:11 2006
    Errors in file c:\oracle\product\10.2.0\admin\golf\bdump\golf1_cjq0_4704.trc:
    Sun Dec 10 03:12:12 2006
    Process J000 died, see its trace file
    Sun Dec 10 03:12:12 2006
    kkjcre1p: unable to spawn jobq slave process
    Sun Dec 10 03:12:12 2006
    Errors in file c:\oracle\product\10.2.0\admin\golf\bdump\golf1_cjq0_4704.trc:
    Sun Dec 10 03:13:18 2006
    Process J000 died, see its trace file
    Sun Dec 10 03:13:18 2006
    kkjcre1p: unable to spawn jobq slave process
    Sun Dec 10 03:13:18 2006
    Errors in file c:\oracle\product\10.2.0\admin\golf\bdump\golf1_cjq0_4704.trc:
    Sun Dec 10 03:20:58 2006
    Process PZ99 died, see its trace file
    Process PZ99 died, see its trace file
    Sun Dec 10 03:31:48 2006
    Process PZ99 died, see its trace file
    Process PZ99 died, see its trace file
    Sun Dec 10 03:42:38 2006
    Process PZ99 died, see its trace file
    Process PZ99 died, see its trace file
    Sun Dec 10 03:48:04 2006
    Process J000 died, see its trace file
    Sun Dec 10 03:48:04 2006
    kkjcre1p: unable to spawn jobq slave process
    Sun Dec 10 03:48:04 2006
    Errors in file c:\oracle\product\10.2.0\admin\golf\bdump\golf1_cjq0_4704.trc:
    Sun Dec 10 03:48:19 2006
    Process J000 died, see its trace file
    Sun Dec 10 03:48:19 2006
    kkjcre1p: unable to spawn jobq slave process
    Sun Dec 10 03:48:19 2006
    Errors in file c:\oracle\product\10.2.0\admin\golf\bdump\golf1_cjq0_4704.trc:
    Sun Dec 10 06:52:34 2006
    Reconfiguration started (old inc 4, new inc 6)
    List of nodes:
    0
    Sun Dec 10 06:52:35 2006
    Process q002 died, see its trace file
    Sun Dec 10 06:52:35 2006
    ksvcreate: Process(q002) creation failed
    Dump file c:\oracle\product\10.2.0/admin/golf/bdump\alert_golf1.log
    Sun Dec 10 06:59:01 2006
    ORACLE V10.2.0.1.0 - Production vsnsta=0
    vsnsql=14 vsnxtr=3
    Windows Server 2003 Version V5.2 Service Pack 1
    CPU : 4 - type 586, 2 Physical Cores
    Process Affinity : 0x00000000
    Memory (Avail/Total): Ph:2877M/3583M, Ph+PgF:4816M/5475M, VA:1937M/2047M
    Sun Dec 10 06:59:01 2006
    Starting ORACLE instance (normal)
    LICENSE_MAX_SESSION = 0
    LICENSE_SESSIONS_WARNING = 0
    Picked latch-free SCN scheme 2
    Autotune of undo retention is turned on.
    LICENSE_MAX_USERS = 0
    SYS auditing is disabled
    ksdpec: called for event 13740 prior to event group initialization
    Starting up ORACLE RDBMS Version: 10.2.0.1.0.
    System parameters with non-default values:
    processes = 150
    __shared_pool_size = 184549376
    __large_pool_size = 4194304
    __java_pool_size = 8388608
    __streams_pool_size = 0
    spfile = +DATA/golf/spfilegolf.ora
    nls_language = KOREAN
    nls_territory = KOREA
    cluster_interconnects = 10.10.10.1:192.168.200.3
    sga_target = 1073741824
    control_files = DATA/golf/controlfile/current.260.573740937, BACKUP/golf/controlfile/current.256.573740937
    db_block_size = 8192
    __db_cache_size = 868220928
    compatible = 10.2.0.1.0
    log_archive_dest_1 = LOCATION=+BACKUP/GOLF/
    log_archive_format = ARC%S_%R.%T
    db_file_multiblock_read_count= 16
    cluster_database = TRUE
    cluster_database_instances= 2
    db_create_file_dest = +DATA
    db_recovery_file_dest = +BACKUP
    db_recovery_file_dest_size= 128849018880
    thread = 1
    instance_number = 1
    undo_management = AUTO
    undo_tablespace = UNDOTBS1
    remote_login_passwordfile= EXCLUSIVE
    db_domain =
    dispatchers = (PROTOCOL=TCP) (SERVICE=GOLFXDB)
    local_listener = GOLF1
    remote_listener =
    job_queue_processes = 10
    audit_file_dest = C:\ORACLE\PRODUCT\10.2.0\ADMIN\GOLF\ADUMP
    background_dump_dest = C:\ORACLE\PRODUCT\10.2.0\ADMIN\GOLF\BDUMP
    user_dump_dest = C:\ORACLE\PRODUCT\10.2.0\ADMIN\GOLF\UDUMP
    core_dump_dest = C:\ORACLE\PRODUCT\10.2.0\ADMIN\GOLF\CDUMP
    db_name = GOLF
    open_cursors = 300
    pga_aggregate_target = 524288000
    Cluster communication is configured to use the following interface(s) for this instance
    10.10.10.1
    Sun Dec 10 06:59:01 2006
    cluster interconnect IPC version:Oracle 9i Winsock2 TCP/IP IPC
    IPC Vendor 0 proto 0
    Version 0.0
    PMON started with pid=2, OS id=4100
    DIAG started with pid=3, OS id=4112
    PSP0 started with pid=4, OS id=4120
    LMON started with pid=5, OS id=4144
    LMD0 started with pid=6, OS id=4184
    LMS0 started with pid=7, OS id=4192
    LMS1 started with pid=8, OS id=4212
    MMAN started with pid=9, OS id=4216
    DBW0 started with pid=10, OS id=4224
    LGWR started with pid=11, OS id=4208
    CKPT started with pid=12, OS id=4236
    SMON started with pid=13, OS id=4244
    RECO started with pid=14, OS id=4252
    CJQ0 started with pid=15, OS id=4264
    MMON started with pid=16, OS id=4280
    MMNL started with pid=17, OS id=4288
    Sun Dec 10 06:59:01 2006
    starting up 1 dispatcher(s) for network address '(ADDRESS=(PARTIAL=YES)(PROTOCOL=TCP))'...
    starting up 1 shared server(s) ...
    Sun Dec 10 06:59:01 2006
    lmon registered with NM - instance id 1 (internal mem no 0)
    Sun Dec 10 06:59:02 2006
    Reconfiguration started (old inc 0, new inc 4)
    List of nodes:
    0 1
    Global Resource Directory frozen
    * allocate domain 0, invalid = TRUE
    Communication channels reestablished
    * domain 0 valid according to instance 1
    * domain 0 valid = 1 according to instance 1
    Sun Dec 10 06:59:03 2006
    Master broadcasted resource hash value bitmaps
    Non-local Process blocks cleaned out
    Sun Dec 10 06:59:03 2006
    LMS 0: 0 GCS shadows cancelled, 0 closed
    Sun Dec 10 06:59:04 2006
    LMS 1: 0 GCS shadows cancelled, 0 closed
    Set master node info
    Submitted all remote-enqueue requests
    Dwn-cvts replayed, VALBLKs dubious
    All grantable enqueues granted
    Sun Dec 10 06:59:05 2006
    LMS 0: 0 GCS shadows traversed, 0 replayed
    Sun Dec 10 06:59:06 2006
    LMS 1: 0 GCS shadows traversed, 0 replayed
    Sun Dec 10 06:59:06 2006
    Submitted all GCS remote-cache requests
    Post SMON to start 1st pass IR
    Fix write in gcs resources
    Reconfiguration complete
    LCK0 started with pid=20, OS id=5164
    Sun Dec 10 06:59:06 2006
    ALTER DATABASE MOUNT
    Sun Dec 10 06:59:07 2006
    Starting background process ASMB
    ASMB started with pid=22, OS id=4920
    Starting background process RBAL
    RBAL started with pid=23, OS id=5172
    Sun Dec 10 06:59:15 2006
    SUCCESS: diskgroup DATA was mounted
    SUCCESS: diskgroup BACKUP was mounted
    Sun Dec 10 06:59:19 2006
    Setting recovery target incarnation to 2
    Sun Dec 10 06:59:19 2006
    Successful mount of redo thread 1, with mount id 2679476622
    Sun Dec 10 06:59:19 2006
    Database mounted in Shared Mode (CLUSTER_DATABASE=TRUE)
    Completed: ALTER DATABASE MOUNT
    Sun Dec 10 06:59:19 2006
    ALTER DATABASE OPEN
    Picked broadcast on commit scheme to generate SCNs
    Sun Dec 10 07:00:21 2006
    LGWR: STARTING ARCH PROCESSES
    ARC0 started with pid=27, OS id=5668
    Sun Dec 10 07:00:21 2006
    ARC0: Archival started
    ARC1 started with pid=28, OS id=5964
    Sun Dec 10 07:00:21 2006
    ARC1: Archival started
    LGWR: STARTING ARCH PROCESSES COMPLETE
    Thread 1 opened at log sequence 1855
    Current log# 2 seq# 1855 mem# 0: +DATA/golf/onlinelog/group_2.262.573740941
    Current log# 2 seq# 1855 mem# 1: +BACKUP/golf/onlinelog/group_2.258.573740941
    Sun Dec 10 07:00:22 2006
    ARC0: STARTING ARCH PROCESSES
    Sun Dec 10 07:00:22 2006
    Successful open of redo thread 1
    Sun Dec 10 07:00:22 2006
    MTTR advisory is disabled because FAST_START_MTTR_TARGET is not set
    Sun Dec 10 07:00:23 2006
    ARC1: Becoming the 'no FAL' ARCH
    Sun Dec 10 07:00:23 2006
    ARC1: Becoming the 'no SRL' ARCH
    Sun Dec 10 07:00:23 2006
    ARC2: Archival started
    ARC2 started with pid=29, OS id=5908
    Sun Dec 10 07:00:23 2006
    ARC0: STARTING ARCH PROCESSES COMPLETE
    ARC0: Becoming the heartbeat ARCH
    Sun Dec 10 07:00:24 2006
    SMON: enabling cache recovery
    Sun Dec 10 07:00:24 2006
    Successfully onlined Undo Tablespace 1.
    Sun Dec 10 07:00:24 2006
    SMON: enabling tx recovery
    Sun Dec 10 07:00:24 2006
    Database Characterset is KO16KSC5601
    replication_dependency_tracking turned off (no async multimaster replication found)
    Starting background process QMNC
    QMNC started with pid=30, OS id=6076
    Sun Dec 10 07:00:28 2006
    Completed: ALTER DATABASE OPEN
    Sun Dec 10 07:06:21 2006
    Shutting down archive processes
    Sun Dec 10 07:06:26 2006
    ARCH shutting down
    ARC2: Archival stopped
    db 접속이(client) "tns 리스너 소켓을 찾을수..." 이런 메세지만 나오며
    db 가 설치되어있는 서버에서 sql-plus 접속이 위와같은 메세지로 접속이 되지 않았습니다.
    status는 모든 인스턴스가 정상적으로 작동중이었구요..
    그래서 서버 그냥 off 시켰다가 on 시키니깐 정상으로 돌아왔는데
    불안하네요...이런문제...
    혹시 보시고 답변좀 부탁합니다.

    ALERT 내용만 보면 아래 두개의 증상과 비슷하네요.
    첫번째는 alter system set undo_retention=1800 sid='*' 명령문을 node1으로 지정해서 실행하면 모든 instance 가 행업이 걸리는 현상이 있네요. 명령문을 없애주거나 아니면 모든 sid 별로 다 실행을 해주라고 나와있네요.
    Symptoms
    3 nodes RAC system on 10.1.0.4. The command "alter system set undo_retention=1800 sid='*';" was issued on node1, immeidately all instances hang. User can not logon to instance 2 and 3. Logon to instance 1 is still OK but query hangs.Alert log on node 2 and 3 report:Timed out trying to start process J000.Timed out trying to start process q000.kkjcre1p: unable to spawn jobq slave processErrors in file /opt/oracle/admin/RAC/bdump/rac3_cjq0_4229.trc
    Cause
    This is caused by unpublished Bug.3023661 RAC INSTANCE HANGS WHEN MODIFYING UNDO_RETENTION PARAMETER(or published Bug 4220405 ALTER SYSTEM SET UNDO_RETENTION=<N> HANGS RAC INSTANCES which has been closed as base bug 3023661)Bug 4220405 ALTER SYSTEM SET UNDO_RETENTION=<N> HANGS RAC INSTANCES which has been closed as base bug 3023661)The problem is caused by deadlock between CKPT and PZ99 slave. The internal algorithm to query thecurrent value of undo_retention of each instance and modify it has problem. It does unnecessary gv$ query andlob$ update when spfile is used. It is coding problem. The bug has been fixed in 10.2 and it is not backportable to 10.1.0.x due to code structure change.
    Solution
    Workaround is to modify one instance at a time, specify the detailed SID name for alter system command, eg:alter system set undo_retention=1800 sid='RAC1';alter system set undo_retention=1800 sid='RAC2';alter system set undo_retention=1800 sid='RAC3';......until all instances are modified.

  • Oracle 10g Enterprise Manager console giving Alert log

    Dear all
    I have One HP server running Oracle 10g on Redhat Enterprise Linux 3.0 and two other systems with Oracle 9i and 8i. I have written sql query in my Oracle10g system which updates the database in 9i.
    The sql statement is
    CREATE MATERIALIZED VIEW ADASNAP REFRESH FAST START WITH SYSDATE NEXT SYSDATE+1 AS
    SELECT * FROM ADA@WCMMISLINK;
    CREATE MATERIALIZED VIEW BGTABSNAP REFRESH FAST START WITH SYSDATE NEXT SYSDATE+1 AS
    SELECT * FROM BGTAB@WCMMISLIN;
    The above query is sheduled to run every day .
    and i get the following Alert log in 10g enterprise manager console
    Generic Alert log ORA-12012: error on auto execute of job 54
    ORA-04052: error occured when looking up remote object WCMM.SYS@WCMMSERVERLINK
    ORA-00604: error occured at recursive SQL level 3
    ORA-12514: tns no listener
    ORA-06512: AT "SYS.DBMS_SNAPSHOT" line 1883
    can you guid me why the above error are occuring
    the ORA-12514: tns no listener
    the above error why it is occuring , then listener is running on oracle 10g server and other 8i and 9i server also and i am able to connect from oracle10g to other oracle 8i and 9i from sql plus and viceversa..
    what could be the problem with tns listener
    Regards
    Niranjan

    Hi Ugonic
    Sorry both are same, it's spelling mistake it's " WCMMISLINK". Acutally, my database is getting updated but this alert log is getting generated in enterprise manager console of 10g.
    The sql statement is
    CREATE MATERIALIZED VIEW ADASNAP REFRESH FAST START WITH SYSDATE NEXT SYSDATE+1 AS
    SELECT * FROM ADA@WCMMISLINK;
    CREATE MATERIALIZED VIEW BGTABSNAP REFRESH FAST START WITH SYSDATE NEXT SYSDATE+1 AS
    SELECT * FROM BGTAB@WCMMISLINK;
    The above query is sheduled to run every day .
    and i get the following Alert log in 10g enterprise manager console
    Generic Alert log ORA-12012: error on auto execute of job 54
    ORA-04052: error occured when looking up remote object WCMM.SYS@WCMMSERVERLINK
    ORA-00604: error occured at recursive SQL level 3
    ORA-12514: tns no listener
    ORA-06512: AT "SYS.DBMS_SNAPSHOT" line 1883
    can you guid me why the above error are occuring
    Regards
    Niranjan

  • ORA-01033 Error cannot be traced in the alert log or v$views

    Hello There,
    I'm hoping you can shed some light on what seems a rather odd occurrence on our Production Oracle Instance.
    Before i elaborate on the nature of the problem, I must confess that i am not an Oracle DBA and have been compelled to post this query since i have no joy from the in house DBA community on the origins of this error.
    We've had an ORA-01033 error being issued by our ETL installation (deployed on a Linux machine) a couple of days ago whence trying to extract some data from the Oracle instance (during overnight DataWarehouse loads) which has consequently aborted the loads necessitating a cleanup.
    This event has already occurred twice before, the first time being a month ago when the event was captured in the v$instance (using the Startup time column where the timestamp corroborates to the first time we experienced this issue and also ackowledged by the DBA team) and also in the V$Dataguard_status.
    Since then, This error has been generated twice although there seems to be no evidence of this in either the Oracle alert log(as confirmed by DBA team) or in any of the v$views (as pointed out by Tom in an earlier post) such as DBA_LOGSTDBY_HISTORY, v$logstdby_state, $logstdby_stats, dba_logstdby_log, dba_logstdby_events,v$dataguard_status, v$dataguard_stats, v$dataguard_config,v$database,v$database_incarnation, v$managed_standby, v$standby_log, v$instance. I searched these views since i suspected a latency issue during a failover which could be the reason for the
    ORA-01033 but found nothing.
    The DBA team have pretty much disowned this issue since they claim to not have any actual evidence of this from the logs and this is the crux of the matter here.
    The Problem i have as the downstream "recepient" of this error is to prove to the DBA team that this is indeed a genuine issue with the Oracle instance affecting it's availability and concomittantly affecting the DW loads.
    FYI, The Oracle instance is in Failover mode, so it's swiftly back online after bombing out for a few seconds.
    Also, I don't have access to the Alert log as it's a Production environment and employs restricted access policy to the server.
    Having said that, Is there anything else besides the obvious ORA errors that should be looked for in the Alert log?
    Where else can ORA-01033 errors be traced/traced in the Dictionary besides the Alert Log?
    Thoughts??
    Regards

    Thank You John for that query, but i'm on V10.2 and this view is relevant for 11g and beyond i believe.
    Perhaps there is an equivalent for V10g?
    I am also a bit bemused by the comment earlier about no trace being left behind if the DBA's performed a manual restart, surely it doesn't matter how the DB is restarted, the event is captured in the dictionary?
    In the meantime, I've got a copy of the Alert log and have found redo log issues (DBWR/LGWR) very close to the time (a min after ORA-01033) of the shutdown event.
    ALTER SYSTEM ARCHIVE LOG
    Thread 1 cannot allocate new log, sequence 117732
    Checkpoint not complete
    I've looked into this a fair bit and this error apparently causes Oracle to suspend all processing on the database until the log switch is made.
    Is this the causal link for my issue?
    Does " suspend all processing on the database " actually translate into an actual ORA-01033 error (or some form of) when the ETL application is trying to connect to and extract data from the Oracle database at that time?
    Edited by: shareeman on 16-Oct-2012 03:50

  • Can I reduce the message in the alert log ?

    Hi All,
    I receive lot of message in my alert log. Can I reduce the message in the alert log ? please help me
    Tue Sep 12 13:53:45 2006
    ARC0: received prod
    Tue Sep 12 13:56:13 2006
    LGWR: prodding the archiver
    Thread 1 advanced to log sequence 2105494
    Tue Sep 12 13:56:13 2006
    Current log# 4 seq# 2105494 mem# 0: E:\ORACLE\MMP\LOG\REDO04.LOG
    Current log# 4 seq# 2105494 mem# 1: C:\ORACLE\MMP\LOG\REDO04.LOG
    Tue Sep 12 13:56:14 2006
    ARC1: received prod
    Tue Sep 12 13:56:14 2006
    ARC1: Beginning to archive log# 3 seq# 2105493
    ARC1: Completed archiving log# 3 seq# 2105493
    ARC1: re-scanning for new log files
    ARC1: prodding the archiver
    Tue Sep 12 13:56:18 2006
    ARC0: received prod
    Tue Sep 12 13:58:26 2006
    LGWR: prodding the archiver
    Thread 1 advanced to log sequence 2105495
    Tue Sep 12 13:58:26 2006
    Current log# 1 seq# 2105495 mem# 0: C:\ORACLE\MMP\LOG\REDO01.LOG
    Current log# 1 seq# 2105495 mem# 1: E:\ORACLE\MMP\LOG\REDO01.LOG
    Tue Sep 12 13:58:27 2006
    ARC1: received prod
    Tue Sep 12 13:58:27 2006
    ARC1: Beginning to archive log# 4 seq# 2105494
    ARC1: Completed archiving log# 4 seq# 2105494
    ARC1: re-scanning for new log files
    ARC1: prodding the archiver
    Tue Sep 12 13:58:31 2006
    ARC0: received prod

    Hi,
    The Oracle database writes an audit trail of the archived redo log files received from the primary database into a trace file. This parameter specifies the level of trace that should be generated when redo logs are archived. The value of the parameter indicates the level of trace to be generated.
    Level      Description
    0      Disabled (default)
    1      Track archival of redo log file
    2      Track status of each archivelog destination
    4      Track archival operational phase
    8      Track archivelog destination activity
    16      Track detailed archivelog destination activity
    32      Track archivelog destination parameter changes
    64      Track ARCn process state activity
    128      Track FAL server related activities
    It can be used in a Primary Database or Standby Database
    for more details see:
    http://docs.nojabrsk.ru/sol10/B12037_01/server.101/b10823/trace.htm
    Cheers

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

Maybe you are looking for