ADSM-L

Re: TDP Oracle config question

2003-07-25 20:24:28
Subject: Re: TDP Oracle config question
From: David Longo <David.Longo AT HEALTH-FIRST DOT ORG>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Fri, 25 Jul 2003 20:23:44 -0400
I don't think anyone answered today, you can sefely ignore.  It's
not a "TSM" issue, it's how RMAN works.



David B. Longo
System Administrator
Health First, Inc.
3300 Fiske Blvd.
Rockledge, FL 32955-4305
PH      321.434.5536
Pager  321.634.8230
Fax:    321.434.5509
david.longo AT health-first DOT org


>>> sconko AT ADT DOT COM 07/25/03 09:32AM >>>
Does this mean the error is going to be produced every time we run the
backup? Is this a known issue with TSM? Can we safely ignore it, then?

-----Original Message-----
From: Neil Rasmussen [mailto:rasmussn AT US.IBM DOT COM] 
Sent: Thursday, July 17, 2003 10:10 AM
To: ADSM-L AT VM.MARIST DOT EDU 
Subject: Re: TDP Oracle config question


Steve,

The reason that you are seeing this error is that Oracle/Rman first tries
to delete the backuppiece that it is about to create on the TSM Server. In
this way Oracle/Rman ensures that only one copy of the backuppiece exists
on the Backup Media so Rman tries to delete the backuppiece in case it
already exists. The Rman specifications state that only one copy of a
backuppiece will exist at one time on Media Manager (DP for Oracle).

Unfortunately, Oracle/Rman also specifies that the delete routine act as
single and seperate operation, so when Oracle tries to delete a
backuppiece that does not exist, that is an error and DP for Oracle
returns that error. There is no way for DP for Oracle to determine if the
deletion is a true delete of a backuppiece or if Oracle is checking for
backuppiece existence prior to backup.

Hope this helps clear things up.

------------------------------

Date:    Wed, 16 Jul 2003 13:13:39 -0600
From:    "Conko, Steven" <sconko AT ADT DOT COM>
Subject: Re: TDP Oracle config question

Thanks for that bit of information... it definitely clears some things up.
According to the docs, we should be using unique TDPO_FS names for each
node
we are backing up using TDP, correct?

After doing the query and some further investigation into the BACKUPS
table,
it appears we are getting this message because of a missing "-"....

When I do a select in the BACKUPS table, the LL_NAME shows up as:
c-3756527612-2003-0714-02

However, in the error we are getting, the name of the object is:
c-3756527612-20030714-02

Any idea why this is??

Steve



Regards,

Neil Rasmussen
Software Development
TDP for Oracle

##############################################################
This message is for the named person's use only.  It may 
contain confidential, proprietary, or legally privileged 
information.  No confidentiality or privilege is waived or 
lost by any mistransmission.  If you receive this message 
in error, please immediately delete it and all copies of it 
from your system, destroy any hard copies of it, and notify 
the sender.  You must not, directly or indirectly, use, 
disclose, distribute, print, or copy any part of this message
if you are not the intended recipient.  Health First reserves
the right to monitor all e-mail communications through its
networks.  Any views or opinions expressed in this message
are solely those of the individual sender, except (1) where
the message states such views or opinions are on behalf of 
a particular entity;  and (2) the sender is authorized by 
the entity to give such views or opinions.
##############################################################

<Prev in Thread] Current Thread [Next in Thread>