Skip to Content
avatar image
Former Member

problem !!! Oracle redo log archive

I have problem today i couldn't see may archive redo log on production system.

I use ECC6 on Oracle 10.2 and Windows 2003 server.

windows system event -


> The file system structure on the disk is corrupt and unusable. Please run the chkdsk utility on the volume REDO. /RAID1 only for archive and origlog/

I trying to change my archive log destination without stop database instance but archive process cannot write archive redo logs .

Could you help me with this problem

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

3 Answers

  • Best Answer
    avatar image
    Former Member
    Jan 16, 2009 at 11:17 AM

    i change log_archive destination parameter in memory and arch process write first archive log , now i will start online backup

    thank you very much

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member

      Hi Plamen,

      Please make sure that the archive logs getting generated are also backed up frequently to ensure DB restoration in case of any disaster.

      Also, if your question has been answered. Kindly close the thread as solved.

      Regards,

      Deoraj Alok.

  • Jan 16, 2009 at 10:27 AM

    As per http://support.microsoft.com/kb/246026

    You might have to consider fixing the filesystem and restore from backup.

    Regards

    Juan

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Jan 16, 2009 at 10:52 AM

    Hi Plamen,

    This issue should not be taken lightly. It may turn out to be a costly affair.

    My suggestion is to

    1) Stop your DB instance.

    2) Change your archive log backup destination directory by changing the parameter.

    Ensure that orasid user has read,write authorisation to this new destination.

    3) Take backup of the file archSID.log (placed at /oracle/SID/oraarch) and alertSID.log (placed at /oracle/SID/saptrace/background).

    4) Start the DB instance.

    5) Look for any errors reported in the alertSID.log

    6) Start an online backup of the system to ensure that the DB can be recovered in case of a crash.

    Hope this helps.

    Regards,

    Deoraj Alok.

    Add comment
    10|10000 characters needed characters exceeded