Re: Standby errors
Rather than doing an ALTER SYSTEM SWITCH LOGFILE only, issue an ALTER SYSTEM ARCHIVE LOG NEXT I actually do an ARCHIVE LOG NEXT, SWITCH LOGFILE and also have a sleep in the backup-script, which then proceeds to copy all but the *last* archivelog out to tape ! Hematn At 06:19 AM 14-03-03 -0800, you wrote: Oracle 8.1.6 on Solaris 5.8. We have a read-only standby database for one of our production databases. Each night, the standby is shutdown and the previous days archive logs from production are applied. Then the database is brought backup in read-only mode. To get the archive logs, a hot backup is done on the production database. As the last step is the hot backup, a log switch is done and then the archive logs are ftp'd to the server where the standby is. After the hot backup completed yesterday, the log switch occurred, and the logs sent, but when an attempt was made to apply the archive logs we got an error: ORA-00332: archived log is too small - may be incompletely archived ORA-00334: archived log: '/orabackup/archive/TBSPRD/arch1352.arc' ORA-332 signalled during: ALTER DATABASE RECOVER In looking at the archive log, both on the production and standby servers, they are the same size - 16k (the block size for the db is 8k). The next log is 8k in size and then there is another that is 16k before we see any that are normal sized. These would have been the first logs _after_ the hot backup the night before. In the alert log for the production db, it appears the log 1353 was archived _before_ 1352. Has anyone seen this behavior before? Does anybody have any idea why it happened in the first place? Is there something we can do to make sure it never happens again? P.S. We are upgrading to 9.2 this weekend, if that makes any difference. Terry Ball, DBA Birch Telecom Work: 816-300-1335 FAX: 816-300-1800 -- Please see the official ORACLE-L FAQ: http://www.orafaq.net -- Author: Ball, Terry INET: [EMAIL PROTECTED] Fat City Network Services-- 858-538-5051 http://www.fatcity.com San Diego, California-- Mailing list and web hosting services - To REMOVE yourself from this mailing list, send an E-Mail message to: [EMAIL PROTECTED] (note EXACT spelling of 'ListGuru') and in the message BODY, include a line containing: UNSUB ORACLE-L (or the name of mailing list you want to be removed from). You may also send the HELP command for other information (like subscribing). Hemant K Chitale My personal web site is : http://hkchital.tripod.com -- Please see the official ORACLE-L FAQ: http://www.orafaq.net -- Author: Hemant K Chitale INET: [EMAIL PROTECTED] Fat City Network Services-- 858-538-5051 http://www.fatcity.com San Diego, California-- Mailing list and web hosting services - To REMOVE yourself from this mailing list, send an E-Mail message to: [EMAIL PROTECTED] (note EXACT spelling of 'ListGuru') and in the message BODY, include a line containing: UNSUB ORACLE-L (or the name of mailing list you want to be removed from). You may also send the HELP command for other information (like subscribing).
Re: Standby errors
Hi I would recommend that to use the 'alter system archive log current;' since this command don't return until the database has finished to archive the redo logfile. Hemant K Chitale wrote: Rather than doing an ALTER SYSTEM SWITCH LOGFILE only, issue an ALTER SYSTEM ARCHIVE LOG NEXT I actually do an ARCHIVE LOG NEXT, SWITCH LOGFILE and also have a sleep in the backup-script, which then proceeds to copy all but the *last* archivelog out to tape ! Hematn At 06:19 AM 14-03-03 -0800, you wrote: Oracle 8.1.6 on Solaris 5.8. We have a read-only standby database for one of our production databases. Each night, the standby is shutdown and the previous days archive logs from production are applied. Then the database is brought backup in read-only mode. To get the archive logs, a hot backup is done on the production database. As the last step is the hot backup, a log switch is done and then the archive logs are ftp'd to the server where the standby is. After the hot backup completed yesterday, the log switch occurred, and the logs sent, but when an attempt was made to apply the archive logs we got an error: ORA-00332: archived log is too small - may be incompletely archived ORA-00334: archived log: '/orabackup/archive/TBSPRD/arch1352.arc' ORA-332 signalled during: ALTER DATABASE RECOVER In looking at the archive log, both on the production and standby servers, they are the same size - 16k (the block size for the db is 8k). The next log is 8k in size and then there is another that is 16k before we see any that are normal sized. These would have been the first logs _after_ the hot backup the night before. In the alert log for the production db, it appears the log 1353 was archived _before_ 1352. Has anyone seen this behavior before? Does anybody have any idea why it happened in the first place? Is there something we can do to make sure it never happens again? P.S. We are upgrading to 9.2 this weekend, if that makes any difference. Terry Ball, DBA Birch Telecom Work: 816-300-1335 FAX: 816-300-1800 -- Please see the official ORACLE-L FAQ: http://www.orafaq.net -- Author: Ball, Terry INET: [EMAIL PROTECTED] Fat City Network Services -- 858-538-5051 http://www.fatcity.com San Diego, California -- Mailing list and web hosting services - To REMOVE yourself from this mailing list, send an E-Mail message to: [EMAIL PROTECTED] (note EXACT spelling of 'ListGuru') and in the message BODY, include a line containing: UNSUB ORACLE-L (or the name of mailing list you want to be removed from). You may also send the HELP command for other information (like subscribing). Hemant K Chitale My personal web site is : http://hkchital.tripod.com -- Peter Gram, Miracle A/S Phone : +45 2527 7107, Fax : +45 4466 8856 mailto:[EMAIL PROTECTED] - http://MiracleAS.dk -- Please see the official ORACLE-L FAQ: http://www.orafaq.net -- Author: Peter Gram INET: [EMAIL PROTECTED] Fat City Network Services-- 858-538-5051 http://www.fatcity.com San Diego, California-- Mailing list and web hosting services - To REMOVE yourself from this mailing list, send an E-Mail message to: [EMAIL PROTECTED] (note EXACT spelling of 'ListGuru') and in the message BODY, include a line containing: UNSUB ORACLE-L (or the name of mailing list you want to be removed from). You may also send the HELP command for other information (like subscribing).
RE: Standby errors
Actually, the command to force the switch is: alter system switch logfile; alter system archive log all; I did not set the script up, I just inherited it. THe thinking is, since a hot backup and log switch is going to be done anyway, why not ftp the archive logs after the switch, but as part of the same process. Unfortunately, we did not get the upgrade completed this weekend. The log files were the same size on the production database as on the standby (i.e. too small). We did another hot backup as soon as it was discovered, so that we would not be without a recoverable backup, but wanted to know what had caused the archive log process to create logs that it couldn't read. -Original Message- Sent: Friday, March 14, 2003 3:05 PM To: Multiple recipients of list ORACLE-L Why does the copying of archive logs to the standby have anything to do with a hot backup on the primary? They seem like unrelated events. The reason you are getting an incomplete log is that you are using 'alter system switch logfile'. This command returns before archival, so your copy can commence and finish before archival is complete. The correct command to use is 'alter system archive log current'. This command will not return until the current log is fully archived. Than your copy can proceed safely. -- Jeremiah Wilton http://www.speakeasy.net/~jwilton On Fri, 14 Mar 2003, Ball, Terry wrote: Oracle 8.1.6 on Solaris 5.8. We have a read-only standby database for one of our production databases. Each night, the standby is shutdown and the previous days archive logs from production are applied. Then the database is brought backup in read-only mode. To get the archive logs, a hot backup is done on the production database. As the last step is the hot backup, a log switch is done and then the archive logs are ftp'd to the server where the standby is. After the hot backup completed yesterday, the log switch occurred, and the logs sent, but when an attempt was made to apply the archive logs we got an error: ORA-00332: archived log is too small - may be incompletely archived ORA-00334: archived log: '/orabackup/archive/TBSPRD/arch1352.arc' ORA-332 signalled during: ALTER DATABASE RECOVER In looking at the archive log, both on the production and standby servers, they are the same size - 16k (the block size for the db is 8k). The next log is 8k in size and then there is another that is 16k before we see any that are normal sized. These would have been the first logs _after_ the hot backup the night before. In the alert log for the production db, it appears the log 1353 was archived _before_ 1352. Has anyone seen this behavior before? Does anybody have any idea why it happened in the first place? Is there something we can do to make sure it never happens again? P.S. We are upgrading to 9.2 this weekend, if that makes any difference. -- Please see the official ORACLE-L FAQ: http://www.orafaq.net -- Author: Jeremiah Wilton INET: [EMAIL PROTECTED] Fat City Network Services-- 858-538-5051 http://www.fatcity.com San Diego, California-- Mailing list and web hosting services - To REMOVE yourself from this mailing list, send an E-Mail message to: [EMAIL PROTECTED] (note EXACT spelling of 'ListGuru') and in the message BODY, include a line containing: UNSUB ORACLE-L (or the name of mailing list you want to be removed from). You may also send the HELP command for other information (like subscribing). -- Please see the official ORACLE-L FAQ: http://www.orafaq.net -- Author: Ball, Terry INET: [EMAIL PROTECTED] Fat City Network Services-- 858-538-5051 http://www.fatcity.com San Diego, California-- Mailing list and web hosting services - To REMOVE yourself from this mailing list, send an E-Mail message to: [EMAIL PROTECTED] (note EXACT spelling of 'ListGuru') and in the message BODY, include a line containing: UNSUB ORACLE-L (or the name of mailing list you want to be removed from). You may also send the HELP command for other information (like subscribing).
Re: Standby errors
Terry, what's chances the your scrit copy the archive logs the main database to standby database on a same moment when de database is saving the archive log file? Adriano - Original Message - To: Multiple recipients of list ORACLE-L [EMAIL PROTECTED] Sent: Friday, March 14, 2003 11:19 AM Oracle 8.1.6 on Solaris 5.8. We have a read-only standby database for one of our production databases. Each night, the standby is shutdown and the previous days archive logs from production are applied. Then the database is brought backup in read-only mode. To get the archive logs, a hot backup is done on the production database. As the last step is the hot backup, a log switch is done and then the archive logs are ftp'd to the server where the standby is. After the hot backup completed yesterday, the log switch occurred, and the logs sent, but when an attempt was made to apply the archive logs we got an error: ORA-00332: archived log is too small - may be incompletely archived ORA-00334: archived log: '/orabackup/archive/TBSPRD/arch1352.arc' ORA-332 signalled during: ALTER DATABASE RECOVER In looking at the archive log, both on the production and standby servers, they are the same size - 16k (the block size for the db is 8k). The next log is 8k in size and then there is another that is 16k before we see any that are normal sized. These would have been the first logs _after_ the hot backup the night before. In the alert log for the production db, it appears the log 1353 was archived _before_ 1352. Has anyone seen this behavior before? Does anybody have any idea why it happened in the first place? Is there something we can do to make sure it never happens again? P.S. We are upgrading to 9.2 this weekend, if that makes any difference. Terry Ball, DBA Birch Telecom Work: 816-300-1335 FAX: 816-300-1800 -- Please see the official ORACLE-L FAQ: http://www.orafaq.net -- Author: Ball, Terry INET: [EMAIL PROTECTED] Fat City Network Services-- 858-538-5051 http://www.fatcity.com San Diego, California-- Mailing list and web hosting services - To REMOVE yourself from this mailing list, send an E-Mail message to: [EMAIL PROTECTED] (note EXACT spelling of 'ListGuru') and in the message BODY, include a line containing: UNSUB ORACLE-L (or the name of mailing list you want to be removed from). You may also send the HELP command for other information (like subscribing). -- Please see the official ORACLE-L FAQ: http://www.orafaq.net -- Author: Adriano Freire INET: [EMAIL PROTECTED] Fat City Network Services-- 858-538-5051 http://www.fatcity.com San Diego, California-- Mailing list and web hosting services - To REMOVE yourself from this mailing list, send an E-Mail message to: [EMAIL PROTECTED] (note EXACT spelling of 'ListGuru') and in the message BODY, include a line containing: UNSUB ORACLE-L (or the name of mailing list you want to be removed from). You may also send the HELP command for other information (like subscribing).
RE: Standby errors
I have seen lower sequence logs complete archival after higher sequence logs. Usually coinciding with some sort of I/O bottleneck where multiple archiver processes are competing for limited bandwidth. I have not seen any sort of log corruption as a result of that process though. If the logs are identical on both the primary and standby, (use diff to verify) I would suggest doing another backup. Because if that archived log is corrupt it will put a keebosh on your restore. If you used rman for your backup, I am pretty sure you can verify that your archive logs will restore properly. Of course if you can't recover your standby it will have to be resynched as well. Steve -- Please see the official ORACLE-L FAQ: http://www.orafaq.net -- Author: Steve McClure INET: [EMAIL PROTECTED] Fat City Network Services-- 858-538-5051 http://www.fatcity.com San Diego, California-- Mailing list and web hosting services - To REMOVE yourself from this mailing list, send an E-Mail message to: [EMAIL PROTECTED] (note EXACT spelling of 'ListGuru') and in the message BODY, include a line containing: UNSUB ORACLE-L (or the name of mailing list you want to be removed from). You may also send the HELP command for other information (like subscribing).
Re: Standby errors
Why does the copying of archive logs to the standby have anything to do with a hot backup on the primary? They seem like unrelated events. The reason you are getting an incomplete log is that you are using 'alter system switch logfile'. This command returns before archival, so your copy can commence and finish before archival is complete. The correct command to use is 'alter system archive log current'. This command will not return until the current log is fully archived. Than your copy can proceed safely. -- Jeremiah Wilton http://www.speakeasy.net/~jwilton On Fri, 14 Mar 2003, Ball, Terry wrote: Oracle 8.1.6 on Solaris 5.8. We have a read-only standby database for one of our production databases. Each night, the standby is shutdown and the previous days archive logs from production are applied. Then the database is brought backup in read-only mode. To get the archive logs, a hot backup is done on the production database. As the last step is the hot backup, a log switch is done and then the archive logs are ftp'd to the server where the standby is. After the hot backup completed yesterday, the log switch occurred, and the logs sent, but when an attempt was made to apply the archive logs we got an error: ORA-00332: archived log is too small - may be incompletely archived ORA-00334: archived log: '/orabackup/archive/TBSPRD/arch1352.arc' ORA-332 signalled during: ALTER DATABASE RECOVER In looking at the archive log, both on the production and standby servers, they are the same size - 16k (the block size for the db is 8k). The next log is 8k in size and then there is another that is 16k before we see any that are normal sized. These would have been the first logs _after_ the hot backup the night before. In the alert log for the production db, it appears the log 1353 was archived _before_ 1352. Has anyone seen this behavior before? Does anybody have any idea why it happened in the first place? Is there something we can do to make sure it never happens again? P.S. We are upgrading to 9.2 this weekend, if that makes any difference. -- Please see the official ORACLE-L FAQ: http://www.orafaq.net -- Author: Jeremiah Wilton INET: [EMAIL PROTECTED] Fat City Network Services-- 858-538-5051 http://www.fatcity.com San Diego, California-- Mailing list and web hosting services - To REMOVE yourself from this mailing list, send an E-Mail message to: [EMAIL PROTECTED] (note EXACT spelling of 'ListGuru') and in the message BODY, include a line containing: UNSUB ORACLE-L (or the name of mailing list you want to be removed from). You may also send the HELP command for other information (like subscribing).
