Online viewing of alert log

I know that there is a switch for online using the less command. does any one know the exact syntax to enable viewing entries of alert log as and when they are written? Some thing like autoscroll of the alert log entries so we can monitor the entries..
RGDS,
BMP

So far the less command displays in a pg like manner contents from any text file, but the controls it provides are for browsing/editting.
~ Madrid

Similar Messages

  • Clusterware 12.1.0.2.0:  Alert Log is empty

    Hello,
    After one week working with a cluster initially of two nodes and after 3, I see that my alertrac1.log is empty on all nodes.
    If we go to the ORACLE_HOME for the GI.
    [grid@rac1 rac1]$ pwd
    /u01/app/12.1.0/grid/log/rac1
    [grid@rac1 rac1]$ ls -ltr
    total 17360
    drwxr-x---. 2 root oinstall     4096 Mar  4 13:43 ctssd
    drwxr-x---. 2 root oinstall     4096 Mar  4 13:43 crsd
    drwxr-x---. 2 grid oinstall     4096 Mar  4 13:43 evmd
    drwxr-x---. 2 grid oinstall     4096 Mar  4 13:43 cssd
    drwxr-x---. 2 grid oinstall     4096 Mar  4 13:43 mdnsd
    drwxr-x---. 2 root oinstall     4096 Mar  4 13:43 gnsd
    drwxr-x---. 2 grid oinstall     4096 Mar  4 13:43 srvm
    drwxr-x---. 2 grid oinstall     4096 Mar  4 13:43 gipcd
    drwxr-x---. 2 grid oinstall     4096 Mar  4 13:43 diskmon
    drwxr-xr-x. 2 grid oinstall     4096 Mar  4 13:43 afd
    drwxrwxr-t. 5 grid oinstall     4096 Mar  4 13:43 racg
    drwxr-x---. 2 grid oinstall     4096 Mar  4 13:43 admin
    drwxr-x---. 2 root oinstall     4096 Mar  4 13:43 crfmond
    drwxr-x---. 2 root oinstall     4096 Mar  4 13:43 crflogd
    drwxrwxr-x. 2 grid oinstall     4096 Mar  4 13:43 xag
    drwxr-xr-x. 6 grid oinstall     4096 Mar  4 13:43 acfs
    -rw-rw-r--. 1 grid oinstall        0 Mar  4 13:43 alertrac1.log
    drwxr-x---. 2 root oinstall     4096 Mar  4 13:47 ohasd
    drwxr-x---. 2 grid oinstall     4096 Mar 15 10:14 gpnpd
    drwxrwxrwt. 2 grid oinstall     4096 Mar 15 10:23 client
    Also other logs , like css, crsd are empty.
    This is a extrange issue, never seem for me.
    The Linux servers are installed in Spanish.
    Red Hat Enterprise Linux Server release 6.5 (Santiago)
    However, if I change the environment variables to English.
    The messages are coming out in Spanish.
    Then If I execute any crsctl command from GRID user:
    [grid@rac1 ~]$ crsctl check cluster -all
    rac1:
    CRS-4537: Cluster Ready Services está en lÃnea
    CRS-4529: Cluster Synchronization Services está en lÃnea
    CRS-4533: El gestor de eventos está en lÃnea
    rac2:
    CRS-4537: Cluster Ready Services está en lÃnea
    CRS-4529: Cluster Synchronization Services está en lÃnea
    CRS-4533: El gestor de eventos está en lÃnea
    rac3:
    CRS-4537: Cluster Ready Services está en lÃnea
    CRS-4529: Cluster Synchronization Services está en lÃnea
    CRS-4533: El gestor de eventos está en lÃnea
    The messages are in Spanish, there seems to me this reading the env variables.
    The .bash_profile for GRID user is:
    export TMP=/tmp
    export TMPDIR=$TMP
    export ORACLE_HOSTNAME=rac1.localdomain
    export ORACLE_BASE=/u01/app/grid
    export ORACLE_HOME=/u01/app/12.1.0/grid
    export ORACLE_SID=+ASM1; export ORACLE_SID
    export ORACLE_TERM=xterm; export ORACLE_TERM
    export BASE_PATH=/usr/sbin:$PATH; export BASE_PATH
    export PATH=$ORACLE_HOME/bin:$PATH; export PATH
    export LD_LIBRARY_PATH=$ORACLE_HOME/lib:/lib:/usr/lib; export LD_LIBRARY_PATH
    export CLASSPATH=$ORACLE_HOME/JRE:$ORACLE_HOME/jlib:$ORACLE_HOME/rdbms/jlib; export CLASSPATH
    ulimit -u 16384 -n 65536
    export NLS_LANG=AMERICAN_AMERICA.AL32UTF8
    export LANG=en_US.UTF-
    You know that it can be happening?
    Many thanks
    Arturo

    Hello,
    Thanks for you answer.
    Yes, If I use adrci from the grid user:
    adrci> show alert
    Choose the home from which to view the alert log:
    1: diag/clients/user_grid/host_203307297_82
    2: diag/clients/user_oracle/host_203307297_82
    3: diag/rdbms/_mgmtdb/-MGMTDB
    4: diag/asm/+asm/+ASM1
    5: diag/tnslsnr/rac1/listener
    6: diag/tnslsnr/rac1/mgmtlsnr
    7: diag/tnslsnr/rac1/asmnet1lsnr_asm
    8: diag/tnslsnr/rac1/listener_scan2
    9: diag/tnslsnr/rac1/listener_scan3
    10: diag/tnslsnr/rac1/listener_scan1
    11: diag/crs/rac1/crs
    Q: to quit
    The 11 option, go to /u01/app/grid/diag/crs/rac1/crs/trace/ alert.log.
    Here in this directory are all the Crs trace files, including css, crsd components etc.
    Well,, I think is a small change of 12c.
    Thanks again.
    Regards
    Arturo

  • Check alert log without loggin into the server ??

    hello all,
    Is there any way i can look at the last 30 - 50 lines in the alert log without going thru vi or any editor on unix system ?? I am on 10203 (hp - ux). and i have dba grant to me. But do not have access to the server to login as oracle to view the alert log...so i was wondering if there are any procedures handy or anyways to look at the alert log without loggin in to unix system??
    THANK YOU..

    Please post all output from your SQL*Plus and paste it between ** tag
    Kamran Agayev A. (10g OCP)
    http://kamranagayev.wordpress.com                                                                                                                                                                                                                                                                                                                                                                               

  • 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

  • How to view alert log?

    I tried clicking on the xml alert log, but it goes into IE and tells me "Cannot view xml input using xsl style sheet...Only one top level element allowed in an xml document". I don't see any adrci, and I can't find any text file alert log? trace directory only has files beginning with cdump. database and dbs directories don't have it. And nothing about it in the docs?
    I hope I'm missing something obvious. The database is running. XP Pro SP3.

    Udo wrote:
    Hello Joel,
    the good old text alert log is still there, it just moved a bit. The default location would be ORACLE_HOME\diag\rdbms\xe\xe\trace, e.g. D:\oracle\product\database_xe_11_2\app\oracle\diag\rdbms\xe\xe\trace for the instance on my machine.Yep, that's the trace directory I was looking in, it only has an xml.
    See this thread for further hints: {thread:id=2281565}(You had an extra ampersand in the thread id). Yeah, 'Diag Trace' says same directory.
    Anyone know how to get the css right? I'm clueless about such things.
    >
    -Udo

  • How do I view IOS system log files on my iPhone?

    I'm getting occasional buzzes on my iPhone when it is in silent mode, but it's not obvious where the buzzes are coming from. How can I view the IOS log files on the phone to figure out which application is generating the alerts?

    Hey Steve,
    You'll want to connect your phone to your computer and sync it in iTunes. You can read more about it here:
    iOS: Syncing your data with iTunes
    http://support.apple.com/kb/HT1386
    Welcome to Apple Support Communities!
    Have a good one,
    Delgadoh

  • Change of date in alert log

    Hi
    Oracle Version 10.2.0.3.0
    Last friday we had a power failure and a server rebooted abruptly. After it came online I restarted the database and the db did a instance recovery and came online without any problems. However when I checked the alert log file I noticed that the date & timestamp has gone back 14 days. This was there for a while and then it started showing the current date & timestamp. Is that normal? If it's not could some one help me to figure out why this has happened?
    Fri Feb 27 21:26:29 2009
    Starting ORACLE instance (normal)
    LICENSE_MAX_SESSION = 0
    LICENSE_SESSIONS_WARNING = 0
    Picked latch-free SCN scheme 2
    Using LOG_ARCHIVE_DEST_1 parameter default value as /opt/oracle/product/10.2/db_1/dbs/arch
    Autotune of undo retention is turned on.
    IMODE=BR
    ILAT =121
    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.3.0.
    System parameters with non-default values:
    processes = 1000
    sessions = 1105
    __shared_pool_size = 184549376
    __large_pool_size = 16777216
    __java_pool_size = 16777216
    __streams_pool_size = 0
    nls_language = ENGLISH
    nls_territory = UNITED KINGDOM
    filesystemio_options = SETALL
    sga_target = 1577058304
    control_files = /opt/oracle/oradata/rep/control.001.dbf, /opt/oracle/oradata/rep/control.002.dbf, /opt/oracle/oradata/rep/control.003.dbf
    db_block_size = 8192
    __db_cache_size = 1342177280
    compatible = 10.2.0
    Fri Feb 27 21:26:31 2009
    ALTER DATABASE MOUNT
    Fri Feb 27 21:26:35 2009
    Setting recovery target incarnation to 1
    Fri Feb 27 21:26:36 2009
    Successful mount of redo thread 1, with mount id 740543687
    Fri Feb 27 21:26:36 2009
    Database mounted in Exclusive Mode
    Completed: ALTER DATABASE MOUNT
    Fri Feb 27 21:26:36 2009
    ALTER DATABASE OPEN
    Fri Feb 27 21:26:36 2009
    Beginning crash recovery of 1 threads
    parallel recovery started with 3 processes
    Fri Feb 27 21:26:37 2009
    Started redo scan
    Fri Feb 27 21:26:41 2009
    Completed redo scan
    481654 redo blocks read, 13176 data blocks need recovery
    Fri Feb 27 21:26:50 2009
    Started redo application at
    Thread 1: logseq 25176, block 781367
    Fri Feb 27 21:26:50 2009
    Recovery of Online Redo Log: Thread 1 Group 6 Seq 25176 Reading mem 0
    Mem# 0: /opt/oracle/oradata/rep/redo_a/redo06.log
    Mem# 1: /opt/oracle/oradata/rep/redo_b/redo06.log
    Fri Feb 27 21:26:53 2009
    Completed redo application
    Fri Feb 27 21:27:00 2009
    Completed crash recovery at
    Thread 1: logseq 25176, block 1263021, scn 77945260488
    13176 data blocks read, 13176 data blocks written, 481654 redo blocks read
    Fri Feb 27 21:27:02 2009
    Expanded controlfile section 9 from 1168 to 2336 records
    Requested to grow by 1168 records; added 4 blocks of records
    Thread 1 advanced to log sequence 25177
    Thread 1 opened at log sequence 25177
    Current log# 7 seq# 25177 mem# 0: /opt/oracle/oradata/rep/redo_a/redo07.log
    Current log# 7 seq# 25177 mem# 1: /opt/oracle/oradata/rep/redo_b/redo07.log
    Successful open of redo thread 1
    Fri Feb 27 21:27:02 2009
    MTTR advisory is disabled because FAST_START_MTTR_TARGET is not set
    Fri Feb 27 21:27:02 2009
    SMON: enabling cache recovery
    Fri Feb 27 21:27:04 2009
    Successfully onlined Undo Tablespace 1.
    Fri Feb 27 21:27:04 2009
    SMON: enabling tx recovery
    Fri Feb 27 21:27:04 2009
    Database Characterset is AL32UTF8
    replication_dependency_tracking turned off (no async multimaster replication found)
    Starting background process QMNC
    QMNC started with pid=17, OS id=4563
    Fri Feb 27 21:27:08 2009
    Completed: ALTER DATABASE OPEN
    Fri Feb 27 22:46:04 2009
    Thread 1 advanced to log sequence 25178
    Current log# 8 seq# 25178 mem# 0: /opt/oracle/oradata/rep/redo_a/redo08.log
    Current log# 8 seq# 25178 mem# 1: /opt/oracle/oradata/rep/redo_b/redo08.log
    Fri Feb 27 23:43:49 2009
    Thread 1 advanced to log sequence 25179
    Current log# 9 seq# 25179 mem# 0: /opt/oracle/oradata/rep/redo_a/redo09.log
    Current log# 9 seq# 25179 mem# 1: /opt/oracle/oradata/rep/redo_b/redo09.log
    Fri Mar 13 20:09:29 2009
    MMNL absent for 1194469 secs; Foregrounds taking over
    Fri Mar 13 20:10:16 2009
    Thread 1 advanced to log sequence 25180
    Current log# 10 seq# 25180 mem# 0: /opt/oracle/oradata/rep/redo_a/redo10.log
    Current log# 10 seq# 25180 mem# 1: /opt/oracle/oradata/rep/redo_b/redo10.log
    Fri Mar 13 20:21:17 2009
    Thread 1 advanced to log sequence 25181
    Current log# 1 seq# 25181 mem# 0: /opt/oracle/oradata/rep/redo_a/redo01.log
    Current log# 1 seq# 25181 mem# 1: /opt/oracle/oradata/rep/redo_b/redo01.log

    yes, you are right. I just found that the server was shutdown for more than 4 hours and server came back online @ 8:08pm and I think within few minutes those old timestamp appeared in the alertlog. We have a table which captures current timestamp from the db and timestamp from application and usually both columns are same. But following are the rows inserted during the time of the issue. Not sure why this has happened. One more thing is that the listener was started and on while database was starting and performing instance recovery.
    DBTimestamp_ ApplicationTimestamp_
    27-02-2009 21:27:45 13-03-2009 20:08:42
    27-02-2009 21:31:47 13-03-2009 20:08:43
    27-02-2009 21:31:54 13-03-2009 20:08:43
    27-02-2009 21:33:39 13-03-2009 20:08:42
    27-02-2009 21:35:47 13-03-2009 20:08:42
    27-02-2009 21:37:45 13-03-2009 20:08:42
    27-02-2009 21:38:24 13-03-2009 20:08:42
    27-02-2009 21:39:42 13-03-2009 20:08:42
    27-02-2009 21:40:01 13-03-2009 20:08:42
    27-02-2009 21:41:13 13-03-2009 20:08:42
    27-02-2009 21:44:07 13-03-2009 20:08:43
    27-02-2009 21:53:54 13-03-2009 20:08:42
    27-02-2009 22:03:45 13-03-2009 20:08:42
    27-02-2009 22:07:02 13-03-2009 20:08:42

  • ORA-01403: no data found in alert.log

    Dear All,
    I am getting ORA-01403: no data found in alert.log.Could you pls help me out what could be reasons behind it..Due to this i m getting loads of alerts.Pls suggest.
    Thanks

    ORA-01403 No Data Found
    Typically, an ORA-01403 error occurs when an apply process tries to update an existing row and the OLD_VALUES in the row LCR do not match the current values at the destination database.
    Typically, one of the following conditions causes this error:
    Supplemental logging is not specified for columns that require supplemental logging at the source database. In this case, LCRs from the source database might not contain values for key columns. You can use a DML handler to modify the LCR so that it contains the necessary supplemental data. See "Using a DML Handler to Correct Error Transactions". Also, specify the necessary supplemental logging at the source database to prevent future errors.
    There is a problem with the primary key in the table for which an LCR is applying a change. In this case, make sure the primary key is enabled by querying the DBA_CONSTRAINTS data dictionary view. If no primary key exists for the table, or if the target table has a different primary key than the source table, then specify substitute key columns using the SET_KEY_COLUMNS procedure in the DBMS_APPLY_ADM package. You also might encounter error ORA-23416 if a table being applied does not have a primary key. After you make these changes, you can reexecute the error transaction.
    The transaction being applied depends on another transaction which has not yet executed. For example, if a transaction tries to update an employee with an employee_id of 300, but the row for this employee has not yet been inserted into the employees table, then the update fails. In this case, execute the transaction on which the error transaction depends. Then, reexecute the error transaction.
    There is a data mismatch between a row LCR and the table for which the LCR is applying a change. Make sure row data in the table at the destination database matches the row data in the LCR. When you are checking for differences in the data, if there are any DATE columns in the shared table, then make sure your query shows the hours, minutes, and seconds. If there is a mismatch, then you can use a DML handler to modify an LCR so that it matches the table. See "Using a DML Handler to Correct Error Transactions".
    Alternatively, you can update the current values in the row so that the row LCR can be applied successfully. If changes to the row are captured by a capture process at the destination database, then you probably do not want to replicate this manual change to destination databases. In this case, complete the following steps:
    Set a tag in the session that corrects the row. Make sure you set the tag to a value that prevents the manual change from being replicated. For example, the tag can prevent the change from being captured by a capture process.
    EXEC DBMS_STREAMS.SET_TAG(tag => HEXTORAW('17'));
    In some environments, you might need to set the tag to a different value.
    Update the row in the table so that the data matches the old values in the LCR.
    Reexecute the error or reexecute all errors. To reexecute an error, run the EXECUTE_ERROR procedure in the DBMS_APPLY_ADM package, and specify the transaction identifier for the transaction that caused the error. For example:
    EXEC DBMS_APPLY_ADM.EXECUTE_ERROR(local_transaction_id => '5.4.312');
    Or, execute all errors for the apply process by running the EXECUTE_ALL_ERRORS procedure:
    EXEC DBMS_APPLY_ADM.EXECUTE_ALL_ERRORS(apply_name => 'APPLY');
    If you are going to make other changes in the current session that you want to replicate destination databases, then reset the tag for the session to an appropriate value, as in the following example:
    EXEC DBMS_STREAMS.SET_TAG(tag => NULL);
    In some environments, you might need to set the tag to a value other than NULL.

  • 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

  • Question about the Initialization Parameters Information in the Alert.log

    Hi, All -
    What is the correct answer for the following question.
    Specifically, what information does Oracle provide you with in the alert.log regarding initialization parameters?
    a. Values of all initialization parameters at startup
    b. Values of initialization parameters modified since last startup
    c. Values of initialization parameters with non-default values
    d. Only values of initialization parameters that cannot be modified dynamically.
    I think the answer should be B, but I would like to confirm.

    The answer is C
    http://download.oracle.com/docs/cd/B19306_01/server.102/b14220/process.htm#sthref1633
    The alert log is a special trace file. The alert log of a database is a chronological log of messages and errors, and includes the following items:
    All internal errors (ORA-600), block corruption errors (ORA-1578), and deadlock errors (ORA-60) that occur
    Administrative operations, such as CREATE, ALTER, and DROP statements and STARTUP, SHUTDOWN, and ARCHIVELOG statements
    Messages and errors relating to the functions of shared server and dispatcher processes
    Errors occurring during the automatic refresh of a materialized view
    The values of all initialization parameters that had nondefault values at the time the database and instance start
    Kamran Agayev A. (10g OCP)
    http://kamranagayev.wordpress.com

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

  • Errors in alert log

    Hi,
    we have Oracle 11.2.0 standard running under Windows Xp 32
    At last time alert log is full of error? like
    Tue Dec 18 11:14:26 2012
    Errors in file c:\oracle\diag\rdbms\ \trace\ratik_j000_4448.trc:
    Errors in file c:\oracle\diag\rdbms\ \trace\ratik_j000_4448.trc:
    and Db is open and in read/write mode
    each trace file is over 4 GB size and new trace files appear and they all are like <sid>j000<>.trc
    all trace files contains following messages
    Trace file c:\oracle\diag\rdbms\ \trace\<sid>j0003300.trc
    Oracle Database 11g Release 11.2.0.1.0 - Production
    Windows XP Version V5.1 Service Pack 3
    CPU : 4 - type 586, 4 Physical Cores
    Process Affinity : 0x0x00000000
    Memory (Avail/Total): Ph:705M/2986M, Ph+PgF:3533M/6914M, VA:978M/2047M
    Instance name: ratik
    Redo thread mounted by this instance: 1
    Oracle process number: 19
    Windows thread id: 3300, image: ORACLE.EXE (J000)
    *** 2013-03-12 09:07:08.906
    *** SESSION ID:(192.5) 2013-03-12 09:07:08.906
    *** CLIENT ID:() 2013-03-12 09:07:08.906
    *** SERVICE NAME:(SYS$USERS) 2013-03-12 09:07:08.906
    *** MODULE NAME:(EM_PING) 2013-03-12 09:07:08.906
    *** ACTION NAME:(AGENT_STATUS_MARKER) 2013-03-12 09:07:08.906
    --------Dumping Sorted Master Trigger List --------
    Trigger Owner : SYSMAN
    Trigger Name : MGMT_JOB_EXEC_UPDATE
    --------Dumping Trigger Sublists --------
    trigger sublist 0 :
    trigger sublist 1 :
    Trigger Owner : SYSMAN
    Trigger Name : MGMT_JOB_EXEC_UPDATE
    trigger sublist 2 :
    trigger sublist 3 :
    trigger sublist 4 :
    what it can be and whow can I fix it?
    Thank's

    There are no ora-00600 errors not in aler not in treace file. And it is not a standby, it is a standalone Db server
    full trace files are over 4GB
    so again the alert log
    Starting ORACLE instance (normal)
    LICENSE_MAX_SESSION = 0
    LICENSE_SESSIONS_WARNING = 0
    Picked latch-free SCN scheme 2
    Using LOG_ARCHIVE_DEST_1 parameter default value as USE_DB_RECOVERY_FILE_DEST
    Autotune of undo retention is turned on.
    IMODE=BR
    ILAT =27
    LICENSE_MAX_USERS = 0
    SYS auditing is disabled
    Starting up:
    Oracle Database 11g Release 11.2.0.1.0 - Production.
    Using parameter settings in server-side spfile C:\ORACLE\PRODUCT\11.2.0\DBHOME_1\DATABASE\SPFILERATIK.ORA
    System parameters with non-default values:
    processes = 150
    nls_language = "AMERICAN"
    nls_territory = "AMERICA"
    memory_target = 1200M
    control_files = "C:\ORACLE\ORADATA\RATIK\CONTROL01.CTL"
    control_files = "C:\ORACLE\FLASH_RECOVERY_AREA\ \CONTROL02.CTL"
    Wed Mar 13 11:32:52 2013
    db_block_size = 8192
    compatible = "11.2.0.0.0"
    db_recovery_file_dest = "C:\oracle\flash_recovery_area"
    db_recovery_file_dest_size= 3852M
    undo_tablespace = "UNDOTBS1"
    max_enabled_roles = 148
    remote_login_passwordfile= "EXCLUSIVE"
    db_domain = ""
    dispatchers = "(PROTOCOL=TCP) (SERVICE=ratikXDB)"
    utl_file_dir = "*"
    job_queue_processes = 100
    audit_file_dest = "C:\ORACLE\ADMIN\ \ADUMP"
    audit_trail = "DB"
    db_name = " SID "
    open_cursors = 300
    optimizer_mode = "ALL_ROWS"
    query_rewrite_enabled = "TRUE"
    query_rewrite_integrity = "TRUSTED"
    aq_tm_processes = 1
    diagnostic_dest = "C:\ORACLE"
    Deprecated system parameters with specified values:
    Wed Mar 13 11:33:02 2013
    max_enabled_roles
    End of deprecated system parameter listing
    Wed Mar 13 11:33:03 2013
    PMON started with pid=2, OS id=2484
    Wed Mar 13 11:33:03 2013
    MMAN started with pid=9, OS id=2176
    Wed Mar 13 11:33:04 2013
    DBW0 started with pid=10, OS id=2896
    Wed Mar 13 11:33:04 2013
    SMON started with pid=13, OS id=2380
    Wed Mar 13 11:33:03 2013
    GEN0 started with pid=4, OS id=1056
    Wed Mar 13 11:33:03 2013
    DBRM started with pid=6, OS id=2188
    Wed Mar 13 11:33:04 2013
    RECO started with pid=14, OS id=3452
    Wed Mar 13 11:33:04 2013
    MMNL started with pid=16, OS id=2588
    Wed Mar 13 11:33:03 2013
    VKTM started with pid=3, OS id=2492 at elevated priority
    starting up 1 dispatcher(s) for network address '(ADDRESS=(PARTIAL=YES)(PROTOCOL=TCP))'...
    Wed Mar 13 11:33:03 2013
    DIA0 started with pid=8, OS id=2180
    starting up 1 shared server(s) ...
    Wed Mar 13 11:33:04 2013
    MMON started with pid=15, OS id=1640
    VKTM running at (10)millisec precision with DBRM quantum (100)ms
    Wed Mar 13 11:33:03 2013
    PSP0 started with pid=7, OS id=2504
    Wed Mar 13 11:33:04 2013
    CKPT started with pid=12, OS id=2544
    Wed Mar 13 11:33:04 2013
    LGWR started with pid=11, OS id=3228
    ORACLE_BASE from environment = C:\oracle
    Wed Mar 13 11:33:03 2013
    DIAG started with pid=5, OS id=2488
    Wed Mar 13 11:33:10 2013
    alter database mount exclusive
    Successful mount of redo thread 1, with mount id 327119926
    Database mounted in Exclusive Mode
    Lost write protection disabled
    Completed: alter database mount exclusive
    alter database open
    Wed Mar 13 11:33:21 2013
    Beginning crash recovery of 1 threads
    Started redo scan
    Completed redo scan
    read 463 KB redo, 146 data blocks need recovery
    Started redo application at
    Thread 1: logseq 517, block 72654
    Recovery of Online Redo Log: Thread 1 Group 1 Seq 517 Reading mem 0
    Mem# 0: C:\ORACLE\ORADATA\RATIK\REDO01.LOG
    Completed redo application of 0.35MB
    Completed crash recovery at
    Thread 1: logseq 517, block 73581, scn 11916940
    146 data blocks read, 146 data blocks written, 463 redo k-bytes read
    Wed Mar 13 11:33:32 2013
    Thread 1 advanced to log sequence 518 (thread open)
    Thread 1 opened at log sequence 518
    Current log# 2 seq# 518 mem# 0: C:\ORACLE\ORADATA\RATIK\REDO02.LOG
    Successful open of redo thread 1
    Wed Mar 13 11:33:35 2013
    SMON: enabling cache recovery
    Wed Mar 13 11:33:36 2013
    Successfully onlined Undo Tablespace 2.
    Verifying file header compatibility for 11g tablespace encryption..
    Verifying 11g file header compatibility for tablespace encryption completed
    SMON: enabling tx recovery
    Database Characterset is CL8MSWIN1251
    No Resource Manager plan active
    replication_dependency_tracking turned off (no async multimaster replication found)
    Starting background process QMNC
    Wed Mar 13 11:33:45 2013
    QMNC started with pid=20, OS id=4012
    Wed Mar 13 11:33:49 2013
    Completed: alter database open
    Wed Mar 13 11:33:56 2013
    Starting background process CJQ0
    Wed Mar 13 11:33:56 2013
    CJQ0 started with pid=22, OS id=2540
    Wed Mar 13 11:33:57 2013
    db_recovery_file_dest_size of 3852 MB is 0.00% used. This is a
    user-specified limit on the amount of space that will be used by this
    database for recovery-related files, and does not reflect the amount of
    space available in the underlying filesystem or ASM diskgroup.
    Wed Mar 13 11:34:23 2013
    Errors in file c:\oracle\diag\rdbms\\trace\_j000_632.trc:
    Wed Mar 13 11:34:29 2013
    Trace dumping is performing id=[cdmp_20130313113429]
    Errors in file c:\oracle\diag\rdbms\\trace\_j000_632.trc:
    Wed Mar 13 11:34:39 2013
    Errors in file c:\oracle\diag\rdbms\\trace\_j000_632.trc:
    Wed Mar 13 11:34:41 2013
    Trace dumping is performing id=[cdmp_20130313113441]
    Errors in file c:\oracle\diag\rdbms\\trace\_j000_632.trc:
    Trace dumping is performing id=[cdmp_20130313113448]
    Wed Mar 13 11:34:53 2013
    Errors in file c:\oracle\diag\rdbms\k\trace\_j000_632.trc:
    Errors in file c:\oracle\diag\rdbms\\trace\_j000_632.trc:
    Wed Mar 13 11:35:01 2013
    Trace dumping is performing id=[cdmp_20130313113501]
    Errors in file c:\oracle\diag\rdbms\\trace\_j000_632.trc:
    Wed Mar 13 11:35:07 2013
    Errors in file c:\oracle\diag\rdbms\\trace\_j000_632.trc:
    Trace dumping is performing id=[cdmp_20130313113509]
    Errors in file c:\oracle\diag\rdbms\ratik\ratik\trace\ratik_j000_632.trc:
    Wed Mar 13 11:35:20 2013
    Errors in file c:\oracle\diag\rdbms\\trace\_j000_632.trc:
    Errors in file c:\oracle\diag\rdbms\\trace\_j000_632.trc:
    Errors in file c:\oracle\diag\rdbms\\trace\_j000_632.trc:
    Wed Mar 13 11:36:20 2013
    Errors in file c:\oracle\diag\rdbms\\trace\_j000_632.trc:
    Errors in file c:\oracle\diag\rdbms\\trace\_j000_632.trc:
    Errors in file c:\oracle\diag\rdbms\\trace\_j000_632.trc:
    Errors in file c:\oracle\diag\rdbms\\trace\_j000_632.trc:
    and this message goes on till server is restarted after server is up that message appear again
    in trace file
    Trace file c:\oracle\diag\rdbms\ \trace\<sid>j0003300.trc
    Oracle Database 11g Release 11.2.0.1.0 - Production
    Windows XP Version V5.1 Service Pack 3
    CPU : 4 - type 586, 4 Physical Cores
    Process Affinity : 0x0x00000000
    Memory (Avail/Total): Ph:705M/2986M, Ph+PgF:3533M/6914M, VA:978M/2047M
    Instance name: ratik
    Redo thread mounted by this instance: 1
    Oracle process number: 19
    Windows thread id: 3300, image: ORACLE.EXE (J000)
    *** 2013-03-12 09:07:08.906
    *** SESSION ID:(192.5) 2013-03-12 09:07:08.906
    *** CLIENT ID:() 2013-03-12 09:07:08.906
    *** SERVICE NAME:(SYS$USERS) 2013-03-12 09:07:08.906
    *** MODULE NAME:(EM_PING) 2013-03-12 09:07:08.906
    *** ACTION NAME:(AGENT_STATUS_MARKER) 2013-03-12 09:07:08.906
    --------Dumping Sorted Master Trigger List --------
    Trigger Owner : SYSMAN
    Trigger Name : MGMT_JOB_EXEC_UPDATE
    --------Dumping Trigger Sublists --------
    trigger sublist 0 :
    trigger sublist 1 :
    Trigger Owner : SYSMAN
    Trigger Name : MGMT_JOB_EXEC_UPDATE
    trigger sublist 2 :
    trigger sublist 3 :
    trigger sublist 4 :
    *** 2013-03-12 09:07:14.046
    oer 8102.3 - obj# 86174, rdba: 0x00810e2c(afn 2, blk# 69164)
    kdk key 8102.3:
    ncol: 8, len: 47
    key: (47):
    01 80 05 41 44 4d 34 36 02 c1 02 0b 78 70 0a 10 08 2c 32 28 f2 c9 c0 02 c1
    04 01 80 01 80 10 c0 89 b8 fe e0 85 45 5a 8d 44 5f 2f 1c b6 ea bb
    mask: (2048):
    05 09 80 54 00 00 00 00 00 4c 00 00 00 88 70 9e 3e 00 00 00 00 00 00 00 00
    40 00 00 00 c8 78 34 0d 94 d1 aa 06 a0 03 8d 0b 00 00 00 00 ed d4 aa 06 9c
    70 9e 3e 00 00 00 00 38 00 00 00 0d 00 00 00 01 00 00 00 03 00 00 00 01 00
    00 00 00 00 00 00 00 00 00 00 00 00 00 00 a0 79 9e 3e 00 00 00 00 ed d4 aa
    06 e8 70 9e 3e 00 00 00 00 38 00 00 00 00 00 00 00 38 00 00 00 00 00 00 00
    4c 00 00 00 00 00 00 00 9c 70 9e 3e 00 00 00 00 00 00 00 00 14 00 00 00 00
    40 00 00 00 00 00 00 a0 79 9e 3e 6c 00 00 00 c8 1c e4 3e 68 b6 3d 0d 7c 79
    34 0d fc f5 c4 62 a0 03 8d 0b a0 79 9e 3e 38 00 00 00 ff ff ff 7f 00 00 00
    00 00 00 00 00 00 40 00 01 00 00 00 00 38 ca f4 62 00 00 00 00 00 00 00 00
    00 00 00 00 02 00 00 00 02 00 00 00 02 00 00 00 00 00 00 00 00 00 00 00 00
    00 00 00 c4 b0 3d 0d 08 76 9e 3e 16 00 00 00 f0 1c e4 3e 00 00 00 00 64 81
    34 0d 00 00 00 00 44 79 34 0d 8c 2c 20 07 17 00 00 00 c4 b0 3d 0d 4c 79 34
    0d 28 23 ea 06 5c 79 34 0d 8c 2c 20 07 17 00 00 00 c4 b0 3d 0d 64 79 34 0d
    28 23 ea 06 b4 79 34 0d a5 d2 ec 62 5c 88 34 0d 80 79 34 0d 8c 2c 20 07 17
    00 00 00 6c 00 00 00 88 79 34 0d 28 23 ea 06 ac 79 34 0d 58 14 cd 62 08 76
    9e 3e a0 03 8d 0b 00 00 00 00 00 00 00 00 02 00 00 00 0c 7e 34 0d c4 b0 3d
    0d 80 ff 8c 0b 6c 00 00 00 d4 79 34 0d 36 a4 c2 62 c8 1c e4 3e 06 00 00 00
    0c 7e 34 0d 02 00 00 00 84 00 00 00 c4 b0 3d 0d 10 7e 34 0d ef 5f 3b 02 c8
    1c e4 3e 06 00 00 00 0c 7e 34 0d 02 00 00 00 84 00 00 00 c4 b0 3d 0d 06 00
    00 00 40 7e 34 0d 02 00 00 00 84 00 00 00 c4 b0 3d 0d 44 7e 34 0d ef 5f 3b
    and those memory blocks till the end of log file
    NO SR is raised.

  • Oracle errors in alert.log

    Hello guys,
    I have the following Oracle Release 10.2.0.1.0 server configuration:
    - Windows 2003 Server SP2
    - 3,25 GB RAM (I think that is a 4 GB but this is a windows 2003 standard edition)
    - 2 Intel Xeon Quad core
    - 3 disk partitions (C -> 40GB, 25 GB free / E -> 100 GB 85 GB free / F 300 GB -> 270 GB free)
    The PRISM instance configuration is:
    Archivelog: TRUE
    SGA Size: 584 MB
    Actual PGA Size: 40 MB
    Services running (OracleDBConsolePRISM, OracleOraDb10g_home1TNSListener, OracleServeicePRISM)
    The problem is that there are just 5 users that use this database, but there are a lot of errors in the alert.log that makes the database not available, the error messages are like this:
    Mon Feb 16 16:31:24 2009
    Errors in file e:\oracle\product\10.2.0\admin\prism\bdump\prism_j001_11416.trc:
    ORA-12012: error on auto execute of job 42567
    ORA-00376: file ORA-00376: file 3 cannot be read at this time
    ORA-01110: data file 3: 'E:\ORACLE\PRODUCT\10.2.0\ORADATA\PRISM\SYSAUX01.DBF'
    ORA-06512: at "EXFSYS.DBMS_RLMGR_DR", line 15
    ORA-06512: at line 1
    cannot be read at this timeThe content of prism_j001_11416.trc is:
    Dump file e:\oracle\product\10.2.0\admin\prism\bdump\prism_mmon_4620.trc
    Mon Feb 16 11:07:33 2009
    ORACLE V10.2.0.1.0 - Production vsnsta=0
    vsnsql=14 vsnxtr=3
    Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Production
    With the Partitioning, OLAP and Data Mining options
    Windows Server 2003 Version V5.2 Service Pack 2
    CPU                 : 8 - type 586, 2 Physical Cores
    Process Affinity    : 0x00000000
    Memory (Avail/Total): Ph:1981M/3325M, Ph+PgF:3612M/5221M, VA:1278M/2047M
    Instance name: prism
    Redo thread mounted by this instance: 1
    Oracle process number: 11
    Windows thread id: 4620, image: ORACLE.EXE (MMON)
    *** SERVICE NAME:(SYS$BACKGROUND) 2009-02-16 11:07:33.480
    *** SESSION ID:(161.1) 2009-02-16 11:07:33.480
    KEWRCTLRD: OCIStmtFetch Error. ctl_dbid= 1515633963, sga_dbid= 1515633963
    KEWRCTLRD: Retcode: -1, Error Message: ORA-00376: file 3 cannot be read at this time
    ORA-01110: data file 3: 'E:\ORACLE\PRODUCT\10.2.0\ORADATA\PRISM\SYSAUX01.DBF'
      *** SQLSTR: total-len=328, dump-len=240,
          STR={select snap_interval, retention,most_recent_snap_time, most_recent_snap_id, status_flag, most_recent_purge_time, most_recent_split_id, most_recent_split_time, mrct_snap_time_num, mrct_purge_time_num, snapint_num, retention_num, swrf_version}
    *** kewrwdbi_1: Error=13509 encountered during run_once
    keaInitAdvCache: failed, err=604
    02/16/09 11:07:33 >ERROR: exception at dbms_ha_alerts_prvt.post_instance_up308: SQLCODE -13917,ORA-13917: Posting system
    alert with reason_id 135 failed with code [5] [post_error]
    02/16/09 11:07:33 >ERROR: exception at dbms_ha_alerts_prvt.check_ha_resources637: SQLCODE -13917,ORA-13917: Posting syst
    em alert with reason_id 136 failed with code [5] [post_error]
    02/16/09 11:07:33 >parameter dump for dbms_ha_alerts_prvt.check_ha_resources
    02/16/09 11:07:33 > - local_db_unique_name (PRISM)
    02/16/09 11:07:33 > - local_db_domain (==N/A==)
    02/16/09 11:07:33 > - rows deleted (0)
    02/16/09 11:07:33 >ERROR: exception at dbms_ha_alerts_prvt.check_ha_resources637: SQLCODE -13917,ORA-13917: Posting syst
    em alert with reason_id 136 failed with code [5] [post_error]
    02/16/09 11:07:33 >parameter dump for dbms_ha_alerts_prvt.check_ha_resources
    02/16/09 11:07:33 > - local_db_unique_name (PRISM)
    02/16/09 11:07:33 > - local_db_domain (==N/A==)
    02/16/09 11:07:33 > - rows deleted (0)
    *** 2009-02-16 11:07:41.293
    ****KELR Apply Log Failed, return code 376
    *** 2009-02-16 11:08:35.294
    ****KELR Apply Log Failed, return code 376
    *** 2009-02-16 11:09:38.294
    ****KELR Apply Log Failed, return code 376
    *** 2009-02-16 11:10:41.295
    ****KELR Apply Log Failed, return code 376
    *** 2009-02-16 11:11:44.296
    ****KELR Apply Log Failed, return code 376
    *** 2009-02-16 11:12:29.328And this is an extract from listener.log file:
    TNSLSNR for 32-bit Windows: Version 10.2.0.1.0 - Production on 16-FEB-2009 11:05:44
    Copyright (c) 1991, 2005, Oracle.  All rights reserved.
    System parameter file is e:\oracle\product\10.2.0\db_1\network\admin\listener.ora
    Log messages written to e:\oracle\product\10.2.0\db_1\network\log\listener.log
    Trace information written to e:\oracle\product\10.2.0\db_1\network\trace\listener.trc
    Trace level is currently 0
    Started with pid=9212
    Listening on: (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=akscl-mfs15.am.enterdir.com)(PORT=1521)))
    Listener completed notification to CRS on start
    TIMESTAMP * CONNECT DATA [* PROTOCOL INFO] * EVENT [* SID] * RETURN CODE
    16-FEB-2009 11:07:25 * service_register * prism * 0
    16-FEB-2009 11:07:31 * service_update * prism * 0
    16-FEB-2009 11:07:34 * service_update * prism * 0
    16-FEB-2009 11:07:37 * service_update * prism * 0
    16-FEB-2009 11:07:57 * (CONNECT_DATA=(SERVER=DEDICATED)(SERVICE_NAME=PRISM)(CID=(PROGRAM=\\akscl-mfs15\PRISMPM\PRISMPM.EXE)(HOST=xx-W20972)(USER=CSC3157))) * (ADDRESS=(PROTOCOL=tcp)(HOST=144.180.225.7)(PORT=1607)) * establish * PRISM * 0
    16-FEB-2009 11:07:58 * service_update * prism * 0
    16-FEB-2009 11:07:58 * (CONNECT_DATA=(SERVER=DEDICATED)(SERVICE_NAME=PRISM)(CID=(PROGRAM=\\akscl-mfs15\PRISMPM\PRISMPM.EXE)(HOST=xx-W20972)(USER=CSC3157))) * (ADDRESS=(PROTOCOL=tcp)(HOST=144.180.225.7)(PORT=1608)) * establish * PRISM * 0
    16-FEB-2009 11:07:58 * (CONNECT_DATA=(SERVER=DEDICATED)(SERVICE_NAME=PRISM)(CID=(PROGRAM=\\akscl-mfs15\PRISMPM\PRISMPM.EXE)(HOST=xx-W20972)(USER=CSC3157))) * (ADDRESS=(PROTOCOL=tcp)(HOST=144.180.225.7)(PORT=1612)) * establish * PRISM * 0
    16-FEB-2009 11:07:59 * (CONNECT_DATA=(SERVER=DEDICATED)(SERVICE_NAME=PRISM)(CID=(PROGRAM=\\akscl-mfs15\PRISMPM\PRISMPM.EXE)(HOST=xx-W20972)(USER=CSC3157))) * (ADDRESS=(PROTOCOL=tcp)(HOST=144.180.225.7)(PORT=1613)) * establish * PRISM * 0
    16-FEB-2009 11:07:59 * (CONNECT_DATA=(SERVER=DEDICATED)(SERVICE_NAME=PRISM)(CID=(PROGRAM=\\akscl-mfs15\PRISMPM\PRISMPM.EXE)(HOST=xx-W20972)(USER=CSC3157))) * (ADDRESS=(PROTOCOL=tcp)(HOST=144.180.225.7)(PORT=1614)) * establish * PRISM * 0
    16-FEB-2009 11:08:01 * service_update * prism * 0
    16-FEB-2009 15:05:26 * (CONNECT_DATA=(SERVICE_NAME=PRISM)(CID=(PROGRAM=C:\Program Files\Microsoft Office\OFFICE11\EXCEL.EXE)(HOST=xx-W21498)(USER=csc2682))) * (ADDRESS=(PROTOCOL=tcp)(HOST=144.180.227.131)(PORT=1999)) * establish * PRISM * 0
    16-FEB-2009 15:05:27 * (CONNECT_DATA=(SERVICE_NAME=PRISM)(CID=(PROGRAM=C:\Program Files\Microsoft Office\OFFICE11\EXCEL.EXE)(HOST=xx-W21498)(USER=csc2682))) * (ADDRESS=(PROTOCOL=tcp)(HOST=144.180.227.131)(PORT=2000)) * establish * PRISM * 0
    16-FEB-2009 17:33:26 * (CONNECT_DATA=(CID=(PROGRAM=)(HOST=__jdbc__)(USER=))(SERVICE_NAME=PRISM)) * (ADDRESS=(PROTOCOL=tcp)(HOST=144.180.227.18)(PORT=2513)) * establish * PRISM * 0
    16-FEB-2009 17:33:26 * (CONNECT_DATA=(CID=(PROGRAM=)(HOST=__jdbc__)(USER=))(SERVICE_NAME=PRISM)) * (ADDRESS=(PROTOCOL=tcp)(HOST=144.180.227.18)(PORT=2514)) * establish * PRISM * 0
    16-FEB-2009 17:33:27 * (CONNECT_DATA=(CID=(PROGRAM=)(HOST=__jdbc__)(USER=))(SERVICE_NAME=PRISM)) * (ADDRESS=(PROTOCOL=tcp)(HOST=144.180.227.18)(PORT=2515)) * establish * PRISM * 0
    16-FEB-2009 17:33:27 * (CONNECT_DATA=(CID=(PROGRAM=)(HOST=__jdbc__)(USER=))(SERVICE_NAME=PRISM)) * (ADDRESS=(PROTOCOL=tcp)(HOST=144.180.227.18)(PORT=2516)) * establish * PRISM * 0
    16-FEB-2009 17:33:27 * (CONNECT_DATA=(CID=(PROGRAM=)(HOST=__jdbc__)(USER=))(SERVICE_NAME=PRISM)) * (ADDRESS=(PROTOCOL=tcp)(HOST=144.180.227.18)(PORT=2517)) * establish * PRISM * 0
    16-FEB-2009 17:33:27 * (CONNECT_DATA=(CID=(PROGRAM=)(HOST=__jdbc__)(USER=))(SERVICE_NAME=PRISM)) * (ADDRESS=(PROTOCOL=tcp)(HOST=144.180.227.18)(PORT=2518)) * establish * PRISM * 0
    16-FEB-2009 17:33:27 * (CONNECT_DATA=(CID=(PROGRAM=)(HOST=__jdbc__)(USER=))(SERVICE_NAME=PRISM)) * (ADDRESS=(PROTOCOL=tcp)(HOST=144.180.227.18)(PORT=2519)) * establish * PRISM * 0
    16-FEB-2009 17:33:27 * (CONNECT_DATA=(CID=(PROGRAM=)(HOST=__jdbc__)(USER=))(SERVICE_NAME=PRISM)) * (ADDRESS=(PROTOCOL=tcp)(HOST=144.180.227.18)(PORT=2520)) * establish * PRISM * 0
    16-FEB-2009 17:33:27 * (CONNECT_DATA=(CID=(PROGRAM=)(HOST=__jdbc__)(USER=))(SERVICE_NAME=PRISM)) * (ADDRESS=(PROTOCOL=tcp)(HOST=144.180.227.18)(PORT=2521)) * establish * PRISM * 0
    16-FEB-2009 17:33:27 * (CONNECT_DATA=(CID=(PROGRAM=)(HOST=__jdbc__)(USER=))(SERVICE_NAME=PRISM)) * (ADDRESS=(PROTOCOL=tcp)(HOST=144.180.227.18)(PORT=2523)) * establish * PRISM * 0
    16-FEB-2009 17:33:27 * (CONNECT_DATA=(CID=(PROGRAM=)(HOST=__jdbc__)(USER=))(SERVICE_NAME=PRISM)) * (ADDRESS=(PROTOCOL=tcp)(HOST=144.180.227.18)(PORT=2524)) * establish * PRISM * 0
    16-FEB-2009 17:33:27 * (CONNECT_DATA=(CID=(PROGRAM=)(HOST=__jdbc__)(USER=))(SERVICE_NAME=PRISM)) * (ADDRESS=(PROTOCOL=tcp)(HOST=144.180.227.18)(PORT=2525)) * establish * PRISM * 0
    16-FEB-2009 17:33:27 * (CONNECT_DATA=(CID=(PROGRAM=)(HOST=__jdbc__)(USER=))(SERVICE_NAME=PRISM)) * (ADDRESS=(PROTOCOL=tcp)(HOST=144.180.227.18)(PORT=2526)) * establish * PRISM * 0
    16-FEB-2009 17:33:27 * (CONNECT_DATA=(CID=(PROGRAM=)(HOST=__jdbc__)(USER=))(SERVICE_NAME=PRISM)) * (ADDRESS=(PROTOCOL=tcp)(HOST=144.180.227.18)(PORT=2527)) * establish * PRISM * 0
    16-FEB-2009 17:33:27 * (CONNECT_DATA=(CID=(PROGRAM=)(HOST=__jdbc__)(USER=))(SERVICE_NAME=PRISM)) * (ADDRESS=(PROTOCOL=tcp)(HOST=144.180.227.18)(PORT=2528)) * establish * PRISM * 0
    16-FEB-2009 17:33:27 * (CONNECT_DATA=(CID=(PROGRAM=)(HOST=__jdbc__)(USER=))(SERVICE_NAME=PRISM)) * (ADDRESS=(PROTOCOL=tcp)(HOST=144.180.227.18)(PORT=2529)) * establish * PRISM * 0
    16-FEB-2009 17:33:27 * (CONNECT_DATA=(CID=(PROGRAM=)(HOST=__jdbc__)(USER=))(SERVICE_NAME=PRISM)) * (ADDRESS=(PROTOCOL=tcp)(HOST=144.180.227.18)(PORT=2530)) * establish * PRISM * 0
    16-FEB-2009 17:33:29 * service_update * prism * 0Please need help to solve this issue, best regards.

    Hello guys,
    Thanks for the tips, after checking the tablespaces the results are:
    SQL> select tablespace_name,status from dba_tablespaces;
    TABLESPACE_NAME                STATUS
    SYSTEM                         ONLINE
    UNDOTBS1                       ONLINE
    SYSAUX                         ONLINE
    TEMP                           ONLINE
    USERS                          ONLINE
    PRISM                          ONLINEThe datafiles:
    SQL> select file#,name,status,enabled from v$datafile;
    FILE#         NAME                                        STATUS  ENABLED
             1     E:\ORACLE\PRODUCT\10.2.0\ORADATA\PRISM\SYSTEM01.DBF          SYSTEM  READ WRITE
             2     E:\ORACLE\PRODUCT\10.2.0\ORADATA\PRISM\UNDOTBS01.DBF          ONLINE  READ WRITE
             3     E:\ORACLE\PRODUCT\10.2.0\ORADATA\PRISM\SYSAUX01.DBF          *RECOVER* READ WRITE
             4     E:\ORACLE\PRODUCT\10.2.0\ORADATA\PRISM\USERS01.DBF          ONLINE  READ WRITE
             5     F:\ORACLE\PRISM\PRISM.ORA                         ONLINE  READ WRITESo, following the metalink guide:
    SQL> recover datafile 'E:\ORACLE\PRODUCT\10.2.0\ORADATA\PRISM\SYSAUX01.DBF';  -->Here the system ask for the log file, I select AUTO
    SQL> alter database datafile 'E:\ORACLE\PRODUCT\10.2.0\ORADATA\PRISM\SYSAUX01.DBF' online; Now the datafiles are all ONLINE, I will wait some time to check the database behavior after this change and back with the results and correct answer, best regards.

  • SMON ABOUT TO RECOVER UNDO SEGMENT s messages in alert log

    Problem
    ======
    There are lots of messages appearing in alert log of the following form:
    SMON: about to recover undo segment %s
    SMON: mark undo segment %s as available
    Reason
    ======
    When the recovery is going on after a abnormal shutdown. Cause These errors do not indicate rollback segment corruption. In oracle8i, this may becoz of problem with the "rollback_segments" parameter in the init.ora. where as in oracle9i, When the instance is shutdown, during the next startup instance recovery needs to take place.
    In AUM we do not have any control over which undo segments will brought online after the instance startup.When SMON finds such offline undo segments with transactions needing recovery ,then it does what is intended to do recovery.
    Solution
    ======
    with oracle8i, we need to cross check rollback_segments" parameter in the init.ora
    with oracle9i,
    first note down segment from SMON: mark undo segment %s as available
    sqlplus "/ as sysdba"
    alter session set "_smu_debug_mode"=4;
    alter rollback segment <offline segment name> online;
    e.g. alter rollback segment "_SYSSMU11$" online;
    Where 11 is the number that is appearing in the messages in the alert log.

    What's the point duplicate metalink doc here,
    SMON: ABOUT TO RECOVER UNDO SEGMENT %s messages in alert log
    Doc ID: Note:266159.1
    besides it's violation of Oracle support service contract.

  • Errors in Alert log file

    Hi,
    I have encountered following errors in alrt log file, its strange to see FAST_START_MTTR_TARGET is out of valid and aksing to use another value and that value is changing every second, it should be in increasing order or it should be consistent. I think i have a serious problem, so anyone could help me out on this. I am getting this "FAST_START_MTTR_TARGET 121 is out of the valid MTTR range, use 24381 instead" error regurarly.
    FAST_START_MTTR_TARGET 121 is out of the valid MTTR range, use 24381 instead.
    Wed Jan 16 23:40:34 2008
    Completed checkpoint up to RBA [0x2aadb.2.10], SCN: 5473742880
    Wed Jan 16 23:45:51 2008
    FAST_START_MTTR_TARGET 121 is out of the valid MTTR range, use 24017 instead.
    Wed Jan 16 23:46:21 2008
    FAST_START_MTTR_TARGET 121 is out of the valid MTTR range, use 23647 instead.
    Wed Jan 16 23:46:52 2008
    FAST_START_MTTR_TARGET 121 is out of the valid MTTR range, use 23298 instead.
    Wed Jan 16 23:47:22 2008
    FAST_START_MTTR_TARGET 121 is out of the valid MTTR range, use 22906 instead.
    Wed Jan 16 23:47:52 2008
    FAST_START_MTTR_TARGET 121 is out of the valid MTTR range, use 22507 instead.
    Wed Jan 16 23:48:22 2008
    FAST_START_MTTR_TARGET 121 is out of the valid MTTR range, use 22133 instead.
    Wed Jan 16 23:48:52 2008
    FAST_START_MTTR_TARGET 121 is out of the valid MTTR range, use 21786 instead.
    Wed Jan 16 23:49:22 2008
    FAST_START_MTTR_TARGET 121 is out of the valid MTTR range, use 21443 instead.
    Wed Jan 16 23:49:52 2008
    FAST_START_MTTR_TARGET 121 is out of the valid MTTR range, use 21062 instead.
    Wed Jan 16 23:50:22 2008
    FAST_START_MTTR_TARGET 121 is out of the valid MTTR range, use 20698 instead.
    Wed Jan 16 23:53:53 2008
    Incremental checkpoint up to RBA [0x2aadb.31b4.0], current log tail at RBA [0x2aadb.3e38.0]
    Thu Jan 17 00:00:54 2008
    FAST_START_MTTR_TARGET 121 is out of the valid MTTR range, use 19582 instead.
    FAST_START_MTTR_TARGET 121 is out of the valid MTTR range, use 16287 instead.
    Thu Jan 17 00:34:01 2008
    FAST_START_MTTR_TARGET 121 is out of the valid MTTR range, use 15902 instead.
    Thu Jan 17 00:34:31 2008
    FAST_START_MTTR_TARGET 121 is out of the valid MTTR range, use 14638 instead.
    Thu Jan 17 00:35:01 2008
    FAST_START_MTTR_TARGET 121 is out of the valid MTTR range, use 13600 instead.
    Thu Jan 17 00:35:31 2008
    FAST_START_MTTR_TARGET 121 is out of the valid MTTR range, use 12773 instead.
    Thu Jan 17 00:36:02 2008
    FAST_START_MTTR_TARGET 121 is out of the valid MTTR range, use 12460 instead.
    Thu Jan 17 00:36:32 2008
    FAST_START_MTTR_TARGET 121 is out of the valid MTTR range, use 12338 instead.
    Thu Jan 17 00:37:01 2008
    Process P187 died, see its trace file
    Thu Jan 17 00:37:02 2008
    FAST_START_MTTR_TARGET 121 is out of the valid MTTR range, use 12248 instead.
    Thu Jan 17 00:37:02 2008
    Process P188 died, see its trace file
    Thu Jan 17 00:37:03 2008
    Process P189 died, see its trace file
    Thu Jan 17 00:37:04 2008
    Process P190 died, see its trace file
    Thu Jan 17 00:37:16 2008
    Process J000 died, see its trace file
    Thu Jan 17 00:37:16 2008
    kkjcre1p: unable to spawn jobq slave process
    Thu Jan 17 00:37:16 2008
    Errors in file /oracle/BP3/saptrace/background/bp3_cjq0_4788.trc:
    Process J000 died, see its trace file
    Thu Jan 17 00:37:22 2008
    kkjcre1p: unable to spawn jobq slave process
    Thu Jan 17 00:37:22 2008
    Errors in file /oracle/BP3/saptrace/background/bp3_cjq0_4788.trc:
    Thanks
    Jafar

    This parameter, FAST_START_MTTR_TARGET ranges from 0 to 3600 seconds. It is important to specify your oracle version, since a similar issue is reported for the 10gR1 release.
    The solution for it would be to increase the value to the suggested one in the alert.log file, but it could be completely out of range from the valid values, so set it to zero and let the oracle instance calculate the value. You can check the output at the V$INSTANCE_RECOVERY view at the columns TARGET_MTTR, and ESTIMATED_MTTR prior to proceeding with modificaiton.
    On the other hand, I suggest you to read this metalink note
    Kkjcre1p: Unable To Spawn Jobq Slave Process, Error 1089
         Doc ID:      Note:344275.1
    for the Kkjcre1p error message.
    ~ Madrid

Maybe you are looking for