DBAsupport.com Forums - Powered by vBulletin
Page 2 of 2 FirstFirst 12
Results 11 to 19 of 19

Thread: Oracle crashes

  1. #11
    Join Date
    Sep 2000
    Posts
    384
    You make it to noarchivelog...
    Radhakrishnan.M

  2. #12
    Join Date
    Jun 2000
    Posts
    417
    As long as you don't want/need archiving you can open in noarchivelog and not worry about the problem. However if you do want it in archivelog mode, set log_archive_start = true instead of false. You have to bounc the database after any changes in the init.ora for them to take effect.

  3. #13
    Join Date
    Sep 2000
    Location
    VA
    Posts
    343

    Thanks everyone.

    I have opened my database in 'NOARCHIVELOG' mode.

    I need to work on it more to see if it crashes or not.
    If it still crashes, I shall again return back to the same forum.

    Thanks again for all your help.
    Shiva.

  4. #14
    Join Date
    Jul 2000
    Posts
    50
    hi!

    It is not a good idea to run your database in no archivelog mode, if it's a production database. You may loose data if the database crashes.

    Keep in archive log mode. Give enough space to archivelog destination. After each backup delete the archives. Make the process in cron script.


    abhijit

  5. #15
    Join Date
    Apr 2000
    Location
    Bangalore
    Posts
    16
    If you don't want to runi in archivelog mode, mount the database and disable archivelog mode by using the following comand.
    svrmgrl> startup mount;
    svrmgrl>alter database noarchivelog;
    svrmgrl>alter database open;

    Thanks,
    Bhaskar

  6. #16
    Join Date
    Aug 2000
    Posts
    236
    If you restart your databse in noarchivelog mode then remember that your backup strategies change entirely.

    I guess that there is not enough space in the archive destination.

    Why dont you move some of your older archive logs elsewhere and free up disk space.

    Also if you are backing up and change to noarchivelog mode then you have to take a full database backup(closed) again.

    Nizar.

  7. #17
    Join Date
    Sep 2000
    Location
    VA
    Posts
    343

    This is not a production database and there is no backup involved. So I guess running the database in noarchive mode is not going to be too dangerous.

    Thanks again for all your responses.
    I have learnt a lot from all you guys.

    Shiva.

  8. #18
    Join Date
    Feb 2000
    Location
    Washington DC
    Posts
    1,843
    If you think, you need this database and you have to recover it when you loose, you need to have some type of backup exp/cold backup/hotbackup with archive logs.

    Justify yourself and have some plan. Sometimes we do neglect and endup having tough time when the situation arise.

    Just a reminder.

  9. #19
    Join Date
    Apr 2000
    Location
    Bangalore
    Posts
    16
    The error message is not saying anything about space problem. It says files to be archived manually which has already been set in control files.
    So comment the above parameter, mount the database and then disable the archivelog as below.
    svrmgrl>startup mount;
    svrmgrl>alter database noarchivelog;
    svrmgrl>alter database open;

    Thanks,
    Bhaskar

    [Edited by Bhaskara on 01-17-2001 at 11:48 AM]

Posting Permissions

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


Click Here to Expand Forum to Full Width