This discussion is archived
3 Replies Latest reply: May 15, 2013 9:32 AM by KevinHonde RSS

Alert log not displaying timestamp correctly

970114 Newbie
Currently Being Moderated
I am using Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - 64bit Production installed in IBM AIX 6.1.0.0

I find this peculiar situation that the alert log is not getting update with proper timestamp for example i see an update now under my alert log of this fashion


Tue Oct 23 08:38:46 2012
ARC2 started with pid=37, OS id=50
Tue Oct 23 08:38:46 2012
ARC3 started with pid=38, OS id=178
Tue Oct 23 08:38:46 2012
ARC4 started with pid=39, OS id=708
Tue Oct 23 08:38:46 2012
ARC6 started with pid=40, OS id=836
Tue Oct 23 08:38:46 2012
ARC7 started with pid=42, OS id=212
Tue Oct 23 08:38:46 2012
ARC8 started with pid=43, OS id=6
Tue Oct 23 08:38:47 2012
ARC9 started with pid=44, OS id=34
Tue Oct 23 08:38:47 2012
ARCa started with pid=45, OS id=13828238
ARC0: Archival started
Tue Oct 23 08:38:47 2012
ARCb started with pid=46, OS id=28049506
ARC1: Archival started
ARC2: Archival started
ARC3: Archival started
ARC4: Archival started
ARC6: Archival started
ARC7: Archival started
ARC8: Archival started
ARC9: Archival started
ARCa: Archival started
ARC3: Becoming the heartbeat ARCH
Reclaiming FAL entry from dead process [pid 41943210]
Reclaiming FAL entry from dead process [pid 49741894]
Reclaiming FAL entry from dead process [pid 51970174]
Reclaiming FAL entry from dead process [pid 13828234]
Reclaiming FAL entry from dead process [pid 52428974]
Reclaiming FAL entry from dead process [pid 24510706]
Reclaiming FAL entry from dead process [pid 28704950]
Reclaiming FAL entry from dead process [pid 28049504]
Reclaiming FAL entry from dead process [pid 43253966]
ARCb: Archival started
ARC5: STARTING ARCH PROCESSES COMPLETE
Reclaiming FAL entry from dead process [pid 33554536]
Reclaiming FAL entry from dead process [pid 26542116]

But the current system time is
Tue Oct 23 18:40:20 GMT+05:30 2012

My memory_target parameter value is 2GB

SQL> SELECT TZ_OFFSET(SESSIONTIMEZONE), TZ_OFFSET(DBTIMEZONE) FROM DUAL;

TZ_OFFS TZ_OFFS
------- -------
+05:30 -05:30


I am clueless. Experts please help me in fixing this issue. :(

Thanks

Edited by: 967111 on Oct 23, 2012 6:20 AM

Edited by: 967111 on Oct 23, 2012 6:21 AM

Edited by: 967111 on Oct 24, 2012 9:08 PM
  • 1. Re: Alert log not displaying timestamp correctly
    970114 Newbie
    Currently Being Moderated
    I myself solved the issues :)

    Below are the steps needed to be done

    My existing format

    [node01:/u01/app/11.2.0/grid/crs/install]$ date
    Thu Oct 25 12:07:16 GMT+05:30 2012
    [node01:/u01/app/11.2.0/grid/crs/install]$ cat s_crsconfig_hostname_env.txt
    ### This file can be used to modify the NLS_LANG environment variable, which determines the charset to be used for messages.
    ### For example, a new charset can be configured by setting NLS_LANG=JAPANESE_JAPAN.UTF8
    ### Do not modify this file except to change NLS_LANG, or under the direction of Oracle Support Services

    TZ=IST+5:30CDT
    NLS_LANG=AMERICAN_AMERICA.WE8ISO8859P1
    RT_GRQ=ON
    TNS_ADMIN=
    ORACLE_BASE=



    change it to below format

    [node01:/u01/app/11.2.0/grid/crs/install]$ cat s_crsconfig_hostname_env.txt
    ### This file can be used to modify the NLS_LANG environment variable, which determines the charset to be used for messages.
    ### For example, a new charset can be configured by setting NLS_LANG=JAPANESE_JAPAN.UTF8
    ### Do not modify this file except to change NLS_LANG, or under the direction of Oracle Support Services

    TZ=GMT+05:30
    NLS_LANG=AMERICAN_AMERICA.WE8ISO8859P1
    RT_GRQ=ON
    TNS_ADMIN=
    ORACLE_BASE=


    Likewise change on all the nodes


    Restart all the databases and ASM nodes. If any changes made in system date recently then do a complete restart of the whole unix server as well.
  • 2. Re: Alert log not displaying timestamp correctly
    970114 Newbie
    Currently Being Moderated
    I myself fixed the issue :)
  • 3. Re: Alert log not displaying timestamp correctly
    KevinHonde Newbie
    Currently Being Moderated
    Thanks for sharing, had a similar experience... saved my day!!!!!

    OS time was ok.
    SQL*Plus time was ok
    But Alert log, OEM and SQL & PL/SQL developer had wrong time.

    Thanks for posting the solution.

Legend

  • Correct Answers - 10 points
  • Helpful Answers - 5 points