Results 1 to 12 of 12
  1. #1
    Join Date
    Aug 2009
    Posts
    55

    Unanswered: rman instance down suddenly without reason

    I use rman to do warmn backup in cron job.
    I find it failure
    Recovery Manager: Release 9.2.0.7.0 - 64bit Production

    Copyright (c) 1995, 2002, Oracle Corporation. All rights reserved.

    connected to target database: RCA (DBID=2453491915)
    RMAN-00571: ================================================== =========
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ================================================== =========
    RMAN-00554: initialization of internal recovery manager package failed
    RMAN-04004: error from recovery catalog database: ORA-01034: ORACLE not available
    ORA-27101: shared memory realm does not exist
    SVR4 Error: 2: No such file or directory
    07/24/09 02:13:51: Tar Backup File to /dev/rmt/0
    a .// 0 tape blocks
    Suppress Backup File to /database/backup_data

    07/24/09 02:18:12: Database SAS
    07/24/09 02:18:12: Tar initSAS.ora on /dev/rmt/0
    a /opt/oracle/product/9ir2/dbs/initSAS.ora 6 tape blocks


    Then I find the rman instance is down without reason.
    I start up rman instance again and the warmbackup is ok again.
    I check the alert.log but there is no data about why the rman instance down suddenly.
    So, any way ot logging that can show why the rman instance down suddenly ??
    Any way to prevent the rman instance down again without reason ?/
    Any monitor way to know the root casue why the rman instance down suddenly

  2. #2
    Join Date
    Feb 2009
    Posts
    62
    What exactly do you mean 'the RMAN instance is down'

    These errors:
    Code:
    RMAN-04004: error from recovery catalog database: ORA-01034: ORACLE not available
    ORA-27101: shared memory realm does not exist
    say that the database you're using to store your recovery catalog in was not up and running at the point you did the RMAN backup.

  3. #3
    Join Date
    Aug 2009
    Posts
    55

    rman instance is down suddenly

    Hi,
    Acutally, the rman instance is up .
    In normal case , the rman backup can be done .
    But it is unknown reason the rman instance suddenly is down , not up .
    Then , the rman backup cannot be done .,
    I need to restart the rman instance by commmand again .
    I want to know why the rman instance down suddenly .
    I check the alert.log but there is no data for this ..
    Any suggestion or advice on how to prevent the rman instance down suddenly again ???

  4. #4
    Join Date
    Dec 2003
    Posts
    1,074
    We don't use a recovery catalog, so this may not be useful advice ... but are you checking the alert log for the recovery catalog, or are you checking the alert log in the instance which is requesting the RMAN backup?

    --=cf

  5. #5
    Join Date
    Aug 2009
    Posts
    55

    rman instance down suddenly

    I check the alert.log already, there is no information about why the rman instance suddenly down ... No related information why the rman instance down suddenly ......
    Any advice ????
    Any way how to open the trace for rman instance to collect more information ,so next time , the rman instance down , there is informaton .
    Any method ????

  6. #6
    Join Date
    Aug 2003
    Location
    Where the Surf Meets the Turf @Del Mar, CA
    Posts
    7,776
    Provided Answers: 1
    How long had the DB been down before it was discovered?
    What do OS logs show between last alert_SID.log prior to restart & DB start?

    You could establish a sanity job to validate instance is up & online;
    which could alarm when DB is down.
    You can lead some folks to knowledge, but you can not make them think.
    The average person thinks he's above average!
    For most folks, they don't know, what they don't know.
    Good judgement comes from experience. Experience comes from bad judgement.

  7. #7
    Join Date
    Aug 2009
    Posts
    55

    rman instance down suddenly

    Hi,
    The rman instance down and warmbackup is failure .
    We find it happen at 23 July....we restart up the rman instance at 11Aug.
    We search alert.log and there is no information about rman instance down
    suddenly ..

    >>You could establish a sanity job to validate instance is up & online;
    >>which could alarm when DB is down
    .
    so, you mean I need to write unix script to monitor the rman instance down .
    but there is no logging or trace to analyse if the rman instance down again??
    Any way to open trace /debug for rman instance ????
    any suggestion ???

  8. #8
    Join Date
    Aug 2003
    Location
    Where the Surf Meets the Turf @Del Mar, CA
    Posts
    7,776
    Provided Answers: 1
    What do OS logs show between last alert_SID.log prior to restart & DB start?
    You can lead some folks to knowledge, but you can not make them think.
    The average person thinks he's above average!
    For most folks, they don't know, what they don't know.
    Good judgement comes from experience. Experience comes from bad judgement.

  9. #9
    Join Date
    Aug 2009
    Posts
    55
    No data in that period of time , in OS log ........

  10. #10
    Join Date
    Aug 2003
    Location
    Where the Surf Meets the Turf @Del Mar, CA
    Posts
    7,776
    Provided Answers: 1
    You report log files look OK.
    Without clues, you are left with a total mystery.

    Good Luck!
    You can lead some folks to knowledge, but you can not make them think.
    The average person thinks he's above average!
    For most folks, they don't know, what they don't know.
    Good judgement comes from experience. Experience comes from bad judgement.

  11. #11
    Join Date
    Feb 2009
    Posts
    62
    Acutally, the rman instance is up .
    I'm afraid, based on the evidence you've posted, at the time you tried to do that warm backup, the Catalog database was definitely down.
    That's what the error ORA-01034: ORACLE not available means - your database is down.

    If there is nothing at all in the Alert.log for that database showing how it was shutdown, then it suggests that someone did a shutdown abort, or killed the Db process, or just unplugged the server.
    There should be something in the OS logs showing if the server was shutdown and restarted.

  12. #12
    Join Date
    Jun 2003
    Location
    West Palm Beach, FL
    Posts
    2,713

    You are fired!

    Quote Originally Posted by chuikingman
    ...
    We find it happen at 23 July....we restart up the rman instance at 11Aug.
    ...
    Does this meen that you did not notice anything for almost 3 WEEKS?

    How often do you take backups?

    Unfortunately you covered it up and may have kept it secret from your Manager, otherwise you would have been FIRED!
    The person who says it can't be done should not interrupt the person doing it. -- Chinese proverb

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •