Re: Oracle TDP and RMAN
Hi Ingrid! Have you checked the SBTIO.LOG file? In most cases it contains more clear messages. Kindest regards, Eric van Loon KLM Royal Dutch Airlines -Original Message- From: Kowieski.Ingrid [mailto:[EMAIL PROTECTED] Sent: Tuesday, November 23, 2004 15:51 To: [EMAIL PROTECTED] Subject: Oracle TDP and RMAN We are getting the following error message when running an RMAN backup with the Oracle TDP (5.2.2.0): RMAN-00571: === RMAN-00569: === ERROR MESSAGE STACK FOLLOWS === RMAN-00571: === RMAN-03009: failure of backup command on ORA_SBT_TAPE_1 channel at 11/23/2004 06 :59:02 ORA-19502: write error on file "DB_5tg5pt17_1_1", blockno 98817 (blocksize=512) ORA-27030: skgfwrt: sbtwrite2 returned error ORA-19511: Error received from media manager layer, error text: ANS0266I (RC2302) The dsmEndTxn vote is ABORT, so check the reason field. I've searched online for both the 19502 and ANS02661 messages, but really found no responses that are helpful. Also, if I look the reason code up in the manual (which looks to be RC2302 to me), it says the following: 2302 I DSM_RC_CHECK_REASON_CODE Explanation: After a dsmEndTxn call, the transaction is aborted by either the server or client with a DSM_VOTE_ABORT and the reason is returned. System Action: The system returns to the calling procedure. User Response: Check the reason field for the code which explains why the transaction has been aborted. Is anyone familiar with this error message and how it can be resolved? Thanks for your time. Ingrid ** For information, services and offers, please visit our web site: http://www.klm.com. This e-mail and any attachment may contain confidential and privileged material intended for the addressee only. If you are not the addressee, you are notified that no part of the e-mail or any attachment may be disclosed, copied or distributed, and that any other action related to this e-mail or attachment is strictly prohibited, and may be unlawful. If you have received this e-mail by error, please notify the sender immediately by return e-mail, and delete this message. Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries and/or its employees shall not be liable for the incorrect or incomplete transmission of this e-mail or any attachments, nor responsible for any delay in receipt. **
Oracle TDP and RMAN
We are getting the following error message when running an RMAN backup with the Oracle TDP (5.2.2.0): RMAN-00571: === RMAN-00569: === ERROR MESSAGE STACK FOLLOWS === RMAN-00571: === RMAN-03009: failure of backup command on ORA_SBT_TAPE_1 channel at 11/23/2004 06 :59:02 ORA-19502: write error on file "DB_5tg5pt17_1_1", blockno 98817 (blocksize=512) ORA-27030: skgfwrt: sbtwrite2 returned error ORA-19511: Error received from media manager layer, error text: ANS0266I (RC2302) The dsmEndTxn vote is ABORT, so check the reason field. I've searched online for both the 19502 and ANS02661 messages, but really found no responses that are helpful. Also, if I look the reason code up in the manual (which looks to be RC2302 to me), it says the following: 2302 I DSM_RC_CHECK_REASON_CODE Explanation: After a dsmEndTxn call, the transaction is aborted by either the server or client with a DSM_VOTE_ABORT and the reason is returned. System Action: The system returns to the calling procedure. User Response: Check the reason field for the code which explains why the transaction has been aborted. Is anyone familiar with this error message and how it can be resolved? Thanks for your time. Ingrid
Re: Oracle TDP and RMAN
Charles, In addition to all the other good answers to this post, you can add this to your argument with the dba's. TSM is NOT a tape management system in the classic sense of that type of product. Classic tape management systems returns a tape to scratch after some policy driven number of days. TSM only returns a tape to scratch when it is logically empty. The rman page 85 note simply doesn't apply to TSM. Hope this helps, Bill Colwell At 05:02 PM 11/19/2004, you wrote: >In working with our Oracle DBA's they feel TSM< should manage the RMAN Oracle >Retentions etc... Is there a "Preferred method?" If so why? > > >Here's one of our DBA's response when I told them my understanding is that >RMAN usually manages the Backup Retentions etc > >"Note on page 85 of the RMAN Backup and Recovery Handbook it says: > >"If you are using a tape management system, it may have its own retention >policy. If the tape management system's retention policy is in conflict with >the backup retention policy you have defined in RMAN, the tape management >system's retention policy will take precedence and your ability to recovery a >backup will be in jeopardy." > >That is why I was leaving it up to the Tivoli retention policy to be used >instead of RMAN retention policies. This seems to be in conflict with the >comment about TSM having a "dumb repository". > > >Thanks for you thoughts... > >Regards, > >Charles -- Bill Colwell C. S. Draper Lab Cambridge Ma.
Re: Oracle TDP and RMAN
Thanks again, for your input... This is the BEST Support list out there. Regards, Charles -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Behalf Of Andreas Almroth [ MTNCameroon O&M - DMSC ] Sent: Saturday, November 20, 2004 3:12 AM To: [EMAIL PROTECTED] Subject: Re: Oracle TDP and RMAN > In working with our Oracle DBA's they feel TSM< should manage the RMAN > Oracle Retentions etc... Is there a "Preferred method?" If so why? > RMAN should normally take care of the retention "cleaning". The node should be set up to be allowed to delete backups. In the manual for TDP Oracle it says one should set up verdeleted=0 and retonly=0. That is, when RMAN has deleted the object in the recovery catalog and in TSM, the object should be removed in TSM upon next inventory run. > Here's one of our DBA's response when I told them my understanding is > that RMAN usually manages the Backup Retentions etc > > "Note on page 85 of the RMAN Backup and Recovery Handbook it says: > > "If you are using a tape management system, it may have its own retention > policy. If the tape management system's retention policy is in conflict > with the backup retention policy you have defined in RMAN, the tape > management system's retention policy will take precedence and your ability > to recovery a backup will be in jeopardy." > Yes, this is true for some backup systems. That is why one should never set up a retention policy in the backup system for RMAN backups. > That is why I was leaving it up to the Tivoli retention policy to be used > instead of RMAN retention policies. This seems to be in conflict with the > comment about TSM having a "dumb repository". I would use RMAN retention, in Oracle 9i it is even easier. The DBA's should have a script that is run regularly to expire backups. This way there will be a minimal risk of ending up with an inconsistency between the recovery catalog and what is stored in TSM. If an inconsistency occurs, you can run tdposync to synchronise recovery catalog and TSM. Regards, Andreas
Re: Oracle TDP and RMAN
> In working with our Oracle DBA's they feel TSM< should manage the RMAN > Oracle Retentions etc... Is there a "Preferred method?" If so why? > RMAN should normally take care of the retention "cleaning". The node should be set up to be allowed to delete backups. In the manual for TDP Oracle it says one should set up verdeleted=0 and retonly=0. That is, when RMAN has deleted the object in the recovery catalog and in TSM, the object should be removed in TSM upon next inventory run. > Here's one of our DBA's response when I told them my understanding is > that RMAN usually manages the Backup Retentions etc > > "Note on page 85 of the RMAN Backup and Recovery Handbook it says: > > "If you are using a tape management system, it may have its own retention > policy. If the tape management system's retention policy is in conflict > with the backup retention policy you have defined in RMAN, the tape > management system's retention policy will take precedence and your ability > to recovery a backup will be in jeopardy." > Yes, this is true for some backup systems. That is why one should never set up a retention policy in the backup system for RMAN backups. > That is why I was leaving it up to the Tivoli retention policy to be used > instead of RMAN retention policies. This seems to be in conflict with the > comment about TSM having a "dumb repository". I would use RMAN retention, in Oracle 9i it is even easier. The DBA's should have a script that is run regularly to expire backups. This way there will be a minimal risk of ending up with an inconsistency between the recovery catalog and what is stored in TSM. If an inconsistency occurs, you can run tdposync to synchronise recovery catalog and TSM. Regards, Andreas
Re: Oracle TDP and RMAN
On Fri, Nov 19, 2004 at 04:02:11PM -0600, Hart, Charles wrote: > In working with our Oracle DBA's they feel TSM< should manage the RMAN Oracle > Retentions etc... Is there a "Preferred method?" If so why? The preferred method is letting RMAN manage the retention policies of the backups. Especially so since Oracle 9i: RMAN works absolutely great for this. It was explicitly designed to be able to implement database retention policies. It keeps track of stored backups, and if you'd let TSM expire backups you'd lose some RMAN functionality like e.g. "CHANGE BACKUPSET foobar KEEP FOREVER". > "Note on page 85 of the RMAN Backup and Recovery Handbook it says: > > "If you are using a tape management system, it may have its own retention > policy. Note the "may". > If the tape management system's retention policy is in conflict with the > backup Note the "if". This "if" is quite important. The TDP for Oracle-documentation quite clearly explains how to configure the TSM retention policy so that it does not conflict with RMAN. > That is why I was leaving it up to the Tivoli retention policy to be used > instead of RMAN retention policies. If he keeps insisting on doing so, he'll be creating a dangerous situation for himself. For example, the "CHANGE ... KEEP FOREVER" will *not* work as expected: your backup *will* be gone when TSM expires it. In addition, he'll have to perform regular CROSSCHECK commands on the recovery catalog, and delete objects with the UNAVAILABLE status. RMAN still thinks it has the backups, while TSM expired them. So: configure TSM to not ever expire any backups made with RMAN. This is quite easy, and is explained in the installation documentation of the TDP for Oracle. Let RMAN take care of the database retention policy. That's what it's designed to do. -- Jurjen Oskam
Re: Oracle TDP and RMAN
Please read the TDP for Oracle manual. It indicates that that you should have your TSM retention set at 1,0,0,0. Set your Oracle management class with those retentions, and Oracle will handle deletion of unneeded backups. -- Mark Stapleton ([EMAIL PROTECTED]) Berbee Information Networks Office 262.521.5627 >-Original Message- >From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On >Behalf Of Hart, Charles >Sent: Friday, November 19, 2004 4:02 PM >To: [EMAIL PROTECTED] >Subject: Oracle TDP and RMAN > >In working with our Oracle DBA's they feel TSM< should manage >the RMAN Oracle Retentions etc... Is there a "Preferred >method?" If so why? > > >Here's one of our DBA's response when I told them my >understanding is that RMAN usually manages the Backup >Retentions etc > >"Note on page 85 of the RMAN Backup and Recovery Handbook it says: > >"If you are using a tape management system, it may have its >own retention policy. If the tape management system's >retention policy is in conflict with the backup retention >policy you have defined in RMAN, the tape management system's >retention policy will take precedence and your ability to >recovery a backup will be in jeopardy." > >That is why I was leaving it up to the Tivoli retention policy >to be used instead of RMAN retention policies. This seems to >be in conflict with the comment about TSM having a "dumb repository". > > >Thanks for you thoughts... > >Regards, > >Charles >
Oracle TDP and RMAN
In working with our Oracle DBA's they feel TSM< should manage the RMAN Oracle Retentions etc... Is there a "Preferred method?" If so why? Here's one of our DBA's response when I told them my understanding is that RMAN usually manages the Backup Retentions etc "Note on page 85 of the RMAN Backup and Recovery Handbook it says: "If you are using a tape management system, it may have its own retention policy. If the tape management system's retention policy is in conflict with the backup retention policy you have defined in RMAN, the tape management system's retention policy will take precedence and your ability to recovery a backup will be in jeopardy." That is why I was leaving it up to the Tivoli retention policy to be used instead of RMAN retention policies. This seems to be in conflict with the comment about TSM having a "dumb repository". Thanks for you thoughts... Regards, Charles
