- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: backup script failed to stop db instance
Operating System - HP-UX
1748019
Members
4639
Online
108757
Solutions
Forums
Categories
Company
Local Language
юдл
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
юдл
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-04-2006 11:15 AM
тАО12-04-2006 11:15 AM
Re: backup script failed to stop db instance
Hi,
Just curious, why do you need to shutdown the database to perform backup?
Regards,
William
Just curious, why do you need to shutdown the database to perform backup?
Regards,
William
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-13-2006 11:57 AM
тАО12-13-2006 11:57 AM
Re: backup script failed to stop db instance
Hello,
just a word on configuration:
- your 3 copies of your controlfile are at the very same location
/u01/oracle/oradata/prod/control01.ctl
/u01/oracle/oradata/prod/control02.ctl
/u01/oracle/oradata/prod/control03.ctl
you should locate them on diffrent physical disks
- your oracle onlineredolog software mirror is at the very same location:
mem#0: /u01/oracle/oradata/prod/redo_1_02_01.log
mem#1: /u01/oracle/oradata/prod/redo_1_02_02.log
you should locate them on diffrent physical disks
Volker
just a word on configuration:
- your 3 copies of your controlfile are at the very same location
/u01/oracle/oradata/prod/control01.ctl
/u01/oracle/oradata/prod/control02.ctl
/u01/oracle/oradata/prod/control03.ctl
you should locate them on diffrent physical disks
- your oracle onlineredolog software mirror is at the very same location:
mem#0: /u01/oracle/oradata/prod/redo_1_02_01.log
mem#1: /u01/oracle/oradata/prod/redo_1_02_02.log
you should locate them on diffrent physical disks
Volker
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-07-2007 03:14 PM
тАО01-07-2007 03:14 PM
Re: backup script failed to stop db instance
Volker,
any reason for that?
Thanks
Fauziah
any reason for that?
Thanks
Fauziah
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-07-2007 05:22 PM
тАО01-07-2007 05:22 PM
Re: backup script failed to stop db instance
hi Fauziah,
All the control files should not be kept in the same location. It is for obvious reasons that they are always multiplexed - corruption of the files or disk crash.
If a control file has been lost or damaged
to a point that Oracle cannot recognize it anymore, when trying to start up the
database will result in an ORA-00205 ("error in identifying control file '%s'")
and an operating system level Oracle error such as ORA-27037 (unable to obtain file status).
In case of a disk crash and loss of all the controlfile, it would be harder to restore.
See metalink note 1014504.6 - Recovering From A Lost Control File.
Below part of the Backup and Recovery basics:
- Running in Archivelog mode
- multiplexing the controlfile
- Taking regular backups
- Periodically doing a complete restore to test your procedures.
hope this helps!
kind regards
yogeeraj
All the control files should not be kept in the same location. It is for obvious reasons that they are always multiplexed - corruption of the files or disk crash.
If a control file has been lost or damaged
to a point that Oracle cannot recognize it anymore, when trying to start up the
database will result in an ORA-00205 ("error in identifying control file '%s'")
and an operating system level Oracle error such as ORA-27037 (unable to obtain file status).
In case of a disk crash and loss of all the controlfile, it would be harder to restore.
See metalink note 1014504.6 - Recovering From A Lost Control File.
Below part of the Backup and Recovery basics:
- Running in Archivelog mode
- multiplexing the controlfile
- Taking regular backups
- Periodically doing a complete restore to test your procedures.
hope this helps!
kind regards
yogeeraj
No person was ever honoured for what he received. Honour has been the reward for what he gave (clavin coolidge)
- « Previous
-
- 1
- 2
- Next »
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP