Re: TDP Oracle best practice

[Chavdar Cholev]

Hello Shawn,
if you have tsm for san this would be good option for multi TB env. For TB
DBs we use from 4-8 session backing up to tape direcly

HTH
Chavdar


On Friday, November 11, 2016, Shawn Drew  wrote:

> I’m looking for best practice advice for TDP for Oracle with regards to #
> of channels.
>
> If you have a classic TSM environment with a disk pool that migrates to
> tape, it would seem that using one-channel for TDPO backups makes the most
> sense to prevent the case where multi-channel files get migrated to the
> same tape.  Our DBAs are quite opposed to using only one channel
> (particularly large multi-TB databases) but I can’t find any official best
> practice statement from IBM that I can use as a response.
> Unfortunately IBM support worded it “you might want to only use
> one-channel” which didn’t sound strong enough for our DBAs.
>
> There is no “reverse-collocation” to ensure the data ends up on different
> tapes, as far as I know, so what is the best practice for backing up Oracle
> data in an environment with data migrations?
>
> -Thanks
> Shawn
>

Re: TDP Oracle issue: thousands of near simultaneous sessions per node

[Grigori Solonovitch]

Hello Rick,
We were using similar RMAN scripts with TSM 5.4/5.5, TDPO 5.5 and TSM Client 
5.x/6.2 for quite long time without any problems.
Each crosscheck creates just a few sessions without any performance problem.
By the way, I never use something like "setlimit channel tdp1 kbytes 1073741824 
maxopenfiles 32 readrate 200;"
I think you need to ask your DBA to tune setlimit statement or try to remove it 
at all.
This is my RMAN script which is working perfectly:

run {
  #
  # Allocate channel to Tivoli Storage Manager for database
  allocate channel t1 type 'sbt_tape' parms 
'ENV=(TDPO_OPTFILE=/oracle/base/admin/tdpo/$1.opt)';
  #
  # Set parameter for tablespace SYSTEM (block corruption is not allowed)
  set maxcorrupt for datafile 1 to 0;
  #
  # Set date and time format
  sql 'alter session set NLS_DATE_FORMAT = "-MM-DD:HH24:MI:SS"';
  #
  # Backup database to TSM
  backup
incremental level $2
filesperset $FILES
tag='Database_$1.Level_$2.Date_$3'
format='/$HOST/$1.$3.$2.%s.%p.%t'
database
include current controlfile
  ;
  #
  # Switch and archive redo log files
  sql 'ALTER SYSTEM SWITCH LOGFILE';
  sql 'ALTER SYSTEM ARCHIVE LOG CURRENT';
  #
  # Backup archive redo logs
  backup
filesperset=128
tag='Archive_$1.Level_$2.Date_$3'
format='/$HOST/Archive_$1.$3.%s.%p.%t'
(archivelog from logseq $START_SEQUENCE)
  ;
  #
  # Backup control file to trace and to disk
  sql 'ALTER DATABASE BACKUP CONTROLFILE TO TRACE NORESETLOGS';
  sql 'ALTER DATABASE BACKUP CONTROLFILE TO TRACE RESETLOGS';
  sql "ALTER DATABASE BACKUP CONTROLFILE TO ''$4''";
  #
  # Release TSM channel
  release channel t1;
}
#
# Allocate channel for maintenance
allocate channel for maintenance type 'sbt_tape' parms 
'ENV=(TDPO_OPTFILE=/oracle/base//admin/tdpo/$1.opt)';
#
# Report unrecoverable data files
report unrecoverable database;
#
# Report data files required backup according to retention policy
report need backup database;
#
# Report number of redundant backups
report need backup redundancy 7 database;
#
# Report number of incremental backups
report need backup incremental=0 database;
#
# Delete obsolete backups
delete noprompt obsolete;
#
# Release TSM channel
release channel;
#
exit
EOF

-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Rick 
Adamson
Sent: 29 05 2013 6:50 PM
To: ADSM-L@VM.MARIST.EDU
Subject: [ADSM-L] TDP Oracle issue: thousands of near simultaneous sessions per 
node

Looking for some direction...

I recently inherited a TSM server along with many TDP for Oracle nodes.
The TSM server is 5.4 (upgrade on the horizon).
The Oracle clients run on mostly AIX, but some Suse Linux, the TDP client is 
ver.5.5.x and the BA clients are primarily 6.2.

All of the database and log backups are initiated by CRON and when they start a 
single Oracle node will start and stop literally thousands of sessions on the 
TSM server within a minute or two.

Oracle and RMAN are new to me and I have talked with our DBA team regarding the 
problem but to no surprise they imply it is a TSM issue.
When this occurs the obvious impact to the TSM server is devastating, 
performance is crushed and the console churn is a blur.

In reading the Oracle and TDP documentation I am suspicious of the RMAN scripts 
as the cause, but before I go testing changes or opening a support case, I 
thought I would ask the group.

The RMAN scripts do perform several "crosschecks" during the process and I 
suspect that each backup piece it queries for starts and stops a client session 
on the TSM server.

Has anyone seen this issue before? Is there any way to get the TDP client to 
perform all operations during a single, or minimal,  sessions?
I have included the RMAN script I suspect below.

All feedback welcome,
~Rick

===

rman target backup/sqbkup3 catalog rman10/sqbkup3@rcat1_catalog.world < 
/opt/oracle/log/rman_full_csp1.log 2>&1 run { allocate channel tdp1 type 
'sbt_tape'
parms 'ENV=(TDPO_OPTFILE=/opt/tivoli/tsm/client/oracle/bin64/tdpo.csp1.opt)';
setlimit channel tdp1 kbytes 1073741824 maxopenfiles 32 readrate 200;

sql 'alter system archive log current';
resync catalog;
change archivelog all validate;
backup database include current controlfile format 'df_%t_%s_%p'; backup 
archivelog all delete input format 'al_%t_%s_%p'; release channel tdp1; } EOF #

rman < /opt/oracle/log/backup_delete_csp1.log 2>&1 connect target 
backup/sqbkup3 connect catalog rman10/sqbkup3@rcat1_catalog.world
allocate channel for delete type 'sbt_tape'
parms 'ENV=(TDPO_OPTFILE=/opt/tivoli/tsm/client/oracle/bin64/tdpo.csp1.opt)';
configure retention policy to recovery window of 14 days; list backup of 
database; list backup of database summary; list backup of archivelog all 
summary; crosscheck backup; delete noprompt obsolete; delete noprompt expired 
backup; crosscheck backup; release channel; allocate channel for delete type 
disk; cro

Re: TDP Oracle issue: thousands of near simultaneous sessions per node

[Richard Cowen]

Rick,

I have seen something similar recently.  More than 1 million client sessions in 
24 hours from a single DP Oracle node.  My 32-bit perl script ran out of 
memory- a 64-bit version handled it...
I haven't investigated any further, just a lot of ANR0406I/ANR0403I pairs. A 
few hundred sessions actually sent data.

Richard


-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Rick 
Adamson
Sent: Wednesday, May 29, 2013 2:44 PM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] TDP Oracle issue: thousands of near simultaneous sessions 
per node

Ricky,
Obviously there are multiple scripts each scheduled at different times, but 
appears that each one allocates one channel.
The TSM server has max sessions set at 300, and there have been no 
modifications to the defaults for resource utilization on the client.

Thanks,
~Rick


-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Plair, 
Ricky
Sent: Wednesday, May 29, 2013 1:03 PM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] TDP Oracle issue: thousands of near simultaneous sessions 
per node

Rick,
How many channels do the DBA have set in RMAN to use for the backups. Also how 
many max sessions are set up on the server node and  resourceutilization in the 
dsm.sys file on the client

-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Rick 
Adamson
Sent: Wednesday, May 29, 2013 11:50 AM
To: ADSM-L@VM.MARIST.EDU
Subject: [ADSM-L] TDP Oracle issue: thousands of near simultaneous sessions per 
node

Looking for some direction...

I recently inherited a TSM server along with many TDP for Oracle nodes.
The TSM server is 5.4 (upgrade on the horizon).
The Oracle clients run on mostly AIX, but some Suse Linux, the TDP client is 
ver.5.5.x and the BA clients are primarily 6.2.

All of the database and log backups are initiated by CRON and when they start a 
single Oracle node will start and stop literally thousands of sessions on the 
TSM server within a minute or two.

Oracle and RMAN are new to me and I have talked with our DBA team regarding the 
problem but to no surprise they imply it is a TSM issue.
When this occurs the obvious impact to the TSM server is devastating, 
performance is crushed and the console churn is a blur.

In reading the Oracle and TDP documentation I am suspicious of the RMAN scripts 
as the cause, but before I go testing changes or opening a support case, I 
thought I would ask the group.

The RMAN scripts do perform several "crosschecks" during the process and I 
suspect that each backup piece it queries for starts and stops a client session 
on the TSM server.

Has anyone seen this issue before? Is there any way to get the TDP client to 
perform all operations during a single, or minimal,  sessions?
I have included the RMAN script I suspect below.

All feedback welcome,
~Rick

===

rman target backup/sqbkup3 catalog rman10/sqbkup3@rcat1_catalog.world < 
/opt/oracle/log/rman_full_csp1.log 2>&1 run { allocate channel tdp1 type 
'sbt_tape'
parms 'ENV=(TDPO_OPTFILE=/opt/tivoli/tsm/client/oracle/bin64/tdpo.csp1.opt)';
setlimit channel tdp1 kbytes 1073741824 maxopenfiles 32 readrate 200;

sql 'alter system archive log current';
resync catalog;
change archivelog all validate;
backup database include current controlfile format 'df_%t_%s_%p'; backup 
archivelog all delete input format 'al_%t_%s_%p'; release channel tdp1; } EOF #

rman < /opt/oracle/log/backup_delete_csp1.log 2>&1 connect target 
backup/sqbkup3 connect catalog rman10/sqbkup3@rcat1_catalog.world
allocate channel for delete type 'sbt_tape'
parms 'ENV=(TDPO_OPTFILE=/opt/tivoli/tsm/client/oracle/bin64/tdpo.csp1.opt)';
configure retention policy to recovery window of 14 days; list backup of 
database; list backup of database summary; list backup of archivelog all 
summary; crosscheck backup; delete noprompt obsolete; delete noprompt expired 
backup; crosscheck backup; release channel; allocate channel for delete type 
disk; crosscheck backup; delete noprompt obsolete; delete noprompt expired 
backup; crosscheck backup; list backup of database; EOF

_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
CONFIDENTIALITY NOTICE: If you have received this email in error, please 
immediately notify the sender by e-mail at the address shown.This email 
transmission may contain confidential information.This information is intended 
only for the use of the individual(s) or entity to whom it is intended even if 
addressed incorrectly. Please delete it from your files if you are not the 
intended recipient. Thank you for your compliance.

Re: TDP Oracle issue: thousands of near simultaneous sessions per node

[Rick Adamson]

Ricky,
Obviously there are multiple scripts each scheduled at different times, but 
appears that each one allocates one channel.
The TSM server has max sessions set at 300, and there have been no 
modifications to the defaults for resource utilization on the client.

Thanks,
~Rick


-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Plair, 
Ricky
Sent: Wednesday, May 29, 2013 1:03 PM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] TDP Oracle issue: thousands of near simultaneous sessions 
per node

Rick,
How many channels do the DBA have set in RMAN to use for the backups. Also how 
many max sessions are set up on the server node and  resourceutilization in the 
dsm.sys file on the client

-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Rick 
Adamson
Sent: Wednesday, May 29, 2013 11:50 AM
To: ADSM-L@VM.MARIST.EDU
Subject: [ADSM-L] TDP Oracle issue: thousands of near simultaneous sessions per 
node

Looking for some direction...

I recently inherited a TSM server along with many TDP for Oracle nodes.
The TSM server is 5.4 (upgrade on the horizon).
The Oracle clients run on mostly AIX, but some Suse Linux, the TDP client is 
ver.5.5.x and the BA clients are primarily 6.2.

All of the database and log backups are initiated by CRON and when they start a 
single Oracle node will start and stop literally thousands of sessions on the 
TSM server within a minute or two.

Oracle and RMAN are new to me and I have talked with our DBA team regarding the 
problem but to no surprise they imply it is a TSM issue.
When this occurs the obvious impact to the TSM server is devastating, 
performance is crushed and the console churn is a blur.

In reading the Oracle and TDP documentation I am suspicious of the RMAN scripts 
as the cause, but before I go testing changes or opening a support case, I 
thought I would ask the group.

The RMAN scripts do perform several "crosschecks" during the process and I 
suspect that each backup piece it queries for starts and stops a client session 
on the TSM server.

Has anyone seen this issue before? Is there any way to get the TDP client to 
perform all operations during a single, or minimal,  sessions?
I have included the RMAN script I suspect below.

All feedback welcome,
~Rick

===

rman target backup/sqbkup3 catalog rman10/sqbkup3@rcat1_catalog.world < 
/opt/oracle/log/rman_full_csp1.log 2>&1 run { allocate channel tdp1 type 
'sbt_tape'
parms 'ENV=(TDPO_OPTFILE=/opt/tivoli/tsm/client/oracle/bin64/tdpo.csp1.opt)';
setlimit channel tdp1 kbytes 1073741824 maxopenfiles 32 readrate 200;

sql 'alter system archive log current';
resync catalog;
change archivelog all validate;
backup database include current controlfile format 'df_%t_%s_%p'; backup 
archivelog all delete input format 'al_%t_%s_%p'; release channel tdp1; } EOF #

rman < /opt/oracle/log/backup_delete_csp1.log 2>&1 connect target 
backup/sqbkup3 connect catalog rman10/sqbkup3@rcat1_catalog.world
allocate channel for delete type 'sbt_tape'
parms 'ENV=(TDPO_OPTFILE=/opt/tivoli/tsm/client/oracle/bin64/tdpo.csp1.opt)';
configure retention policy to recovery window of 14 days; list backup of 
database; list backup of database summary; list backup of archivelog all 
summary; crosscheck backup; delete noprompt obsolete; delete noprompt expired 
backup; crosscheck backup; release channel; allocate channel for delete type 
disk; crosscheck backup; delete noprompt obsolete; delete noprompt expired 
backup; crosscheck backup; list backup of database; EOF

_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
CONFIDENTIALITY NOTICE: If you have received this email in error, please 
immediately notify the sender by e-mail at the address shown.This email 
transmission may contain confidential information.This information is intended 
only for the use of the individual(s) or entity to whom it is intended even if 
addressed incorrectly. Please delete it from your files if you are not the 
intended recipient. Thank you for your compliance.

Re: TDP Oracle issue: thousands of near simultaneous sessions per node

[Plair, Ricky]

Rick, 
How many channels do the DBA have set in RMAN to use for the backups. Also how 
many max sessions are set up on the server node and  resourceutilization in the 
dsm.sys file on the client

-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Rick 
Adamson
Sent: Wednesday, May 29, 2013 11:50 AM
To: ADSM-L@VM.MARIST.EDU
Subject: [ADSM-L] TDP Oracle issue: thousands of near simultaneous sessions per 
node

Looking for some direction...

I recently inherited a TSM server along with many TDP for Oracle nodes.
The TSM server is 5.4 (upgrade on the horizon).
The Oracle clients run on mostly AIX, but some Suse Linux, the TDP client is 
ver.5.5.x and the BA clients are primarily 6.2.

All of the database and log backups are initiated by CRON and when they start a 
single Oracle node will start and stop literally thousands of sessions on the 
TSM server within a minute or two.

Oracle and RMAN are new to me and I have talked with our DBA team regarding the 
problem but to no surprise they imply it is a TSM issue.
When this occurs the obvious impact to the TSM server is devastating, 
performance is crushed and the console churn is a blur.

In reading the Oracle and TDP documentation I am suspicious of the RMAN scripts 
as the cause, but before I go testing changes or opening a support case, I 
thought I would ask the group.

The RMAN scripts do perform several "crosschecks" during the process and I 
suspect that each backup piece it queries for starts and stops a client session 
on the TSM server.

Has anyone seen this issue before? Is there any way to get the TDP client to 
perform all operations during a single, or minimal,  sessions?
I have included the RMAN script I suspect below.

All feedback welcome,
~Rick

===

rman target backup/sqbkup3 catalog rman10/sqbkup3@rcat1_catalog.world < 
/opt/oracle/log/rman_full_csp1.log 2>&1 run { allocate channel tdp1 type 
'sbt_tape'
parms 'ENV=(TDPO_OPTFILE=/opt/tivoli/tsm/client/oracle/bin64/tdpo.csp1.opt)';
setlimit channel tdp1 kbytes 1073741824 maxopenfiles 32 readrate 200;

sql 'alter system archive log current';
resync catalog;
change archivelog all validate;
backup database include current controlfile format 'df_%t_%s_%p'; backup 
archivelog all delete input format 'al_%t_%s_%p'; release channel tdp1; } EOF #

rman < /opt/oracle/log/backup_delete_csp1.log 2>&1 connect target 
backup/sqbkup3 connect catalog rman10/sqbkup3@rcat1_catalog.world
allocate channel for delete type 'sbt_tape'
parms 'ENV=(TDPO_OPTFILE=/opt/tivoli/tsm/client/oracle/bin64/tdpo.csp1.opt)';
configure retention policy to recovery window of 14 days; list backup of 
database; list backup of database summary; list backup of archivelog all 
summary; crosscheck backup; delete noprompt obsolete; delete noprompt expired 
backup; crosscheck backup; release channel; allocate channel for delete type 
disk; crosscheck backup; delete noprompt obsolete; delete noprompt expired 
backup; crosscheck backup; list backup of database; EOF

_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
CONFIDENTIALITY NOTICE: If you have received this email in error, please 
immediately notify the sender by e-mail at the address shown.This email 
transmission may contain confidential information.This information is intended 
only for the use of the individual(s) or entity to whom it is intended even if 
addressed incorrectly. Please delete it from your files if you are not the 
intended recipient. Thank you for your compliance.

Re: Tdp Oracle strangeness

[Remco Post]

That could be it, if a lot of clients were having these problems. AFAIK, this 
is isolated to one or two client systems. It's worth pursuing though, it could 
be that these systems have been misconfigured (no DHCP at this site). Thanks.

On 29 jul 2010, at 21:16, robert.cla...@usbank.com wrote:

> 
> I think I ran into something like this myself last year. 
> 
> Is the client using DNS to find the TSM server? 
> 
> If so, verify that one of the DNS servers in the round robin isn't failing to 
> return the right address. 
> 
> Thanks, 
> [RC] 
> 
> 
> From: Remco Post 
> To:   ADSM-L@VM.MARIST.EDU
> Date: 07/29/2010 07:48 AM
> Subject:  [ADSM-L] Tdp Oracle strangeness
> Sent by:  "ADSM: Dist Stor Manager" 
> 
> 
> 
> 
> Hi All,
> 
> I have a few oracle TDP clients that sometimes fail to backup and report back 
> a rc -50. This would indicate that either the server is down or that the 
> network connection timed out for some other reason, but in the same second, 
> that same client does connect, for what I think is rman making sure that the 
> file is really gone.
> 
> There is no indication in the TSM server act log of anything not being OK.
> 
> TSM server is 5.5.3.0 on AIX, client is 5.5.1.0, also on AIX.
> 
> -- 
> 
> Gr., Remco 
> 

-- 

Met vriendelijke groeten/Kind regards,

Remco Post

Re: TDP Oracle ANS1035S error on Linux

[Richard Sims]

On Jan 31, 2010, at 11:15 AM, Mario Behring wrote:


ANS1035S (RC406)  Options file '*' could not be found.



See that message in  http://people.bu.edu/rbs/ADSM.QuickFacts

Re: TDP Oracle failures

[Buddy Howeth]

I changed my email address over a week ago and I'm still getting messages
to the wrong email.

Monitor:  Please ensure the server is sending emails to the correct
address.  I have a confirmation email from when I setup a different
address but still the lists are going to the wrong address.

Buddy Howeth
Computer Operations Specialist
Information Systems
Pacific Coast Producers
Corporate Offices
631 N. Cluff Ave
Lodi, CA  95240-0756
(209) 367-8800 - Main#
(209) 367-6288 - Computer Room
(209) 366-6240 - Alpha Pager





Eric Lam 
Sent by: "ADSM: Dist Stor Manager" 
06/11/2009 06:59 AM
Please respond to
"ADSM: Dist Stor Manager" 


To
ADSM-L@VM.MARIST.EDU
cc

Subject
Re: [ADSM-L] TDP Oracle failures






ADMINISTRATOR/MONITOR:

Please remove my email address and subscription from this group,
effective immediately

Thank you

Eric Lam

_
Scanned by IBM Email Security Management Services powered by MessageLabs.
For more information please visit http://www.ers.ibm.com
_

Re: TDP Oracle failures

[Eric Lam]

ADMINISTRATOR/MONITOR:

Please remove my email address and subscription from this group,
effective immediately

Thank you

Eric Lam

Re: TDP Oracle failures

[goc]

hi,check permissions on TSM.PWD file
and if oracle user can read the file

i put all of my tdpo nodes password files in /home/oracle

//
goran

On Thu, May 28, 2009 at 3:14 PM, Matthew Large <
mlargedellt...@googlemail.com> wrote:

> Guys, I have some new info, with a slightly different problem, I hope it
> can
> help:
>
> This is the message in the rman output file:
>
> RMAN-03009: failure of backup command on ORA_SBT_TAPE_1 channel at
> 05/28/2009 13:55:26
> ORA-19506: failed to create sequential file, name="688053317_5871_1.arc",
> parms=""
> ORA-27028: skgfqcre: sbtbackup returned error
> ORA-19511: Error received from media manager layer, error text:
>   ANS1025E (RC137)  Session rejected: Authentication failure
>
>
> It says authentication failure, but I'm absolutely sure the tdpoconf
> password process is working as I run the
>
> TSM> upd no bidwp1-zp1-ora 
>
> and the
>
> UNIX> tdpoconf password 
>
> with no errors. I even deleted the password file, and recreated it.
> Running 'tdpoconf showenv ' returns succesfully:
>
>
> IBM Tivoli Storage Manager for Databases:
> Data Protection for Oracle
> Version 5, Release 4, Level 1.0
> (C) Copyright IBM Corporation 1997, 2007. All rights reserved.
>
>
> Data Protection for Oracle Information
>  Version:  5
>  Release:  4
>  Level:1
>  Sublevel: 0
>  Platform: 64bit TDP Oracle SUN
>
> Tivoli Storage Manager Server Information
>  Server Name:  TSM1-LANFREE
>  Server Address:   TSM1
>  Server Type:  Solaris SPARC
>  Server Port:  1500
>  Communication Method: TCP/IP
>
> Session Information
>  Owner Name:
>  Node Name:BIDWP1-ZP1-ORA
>  Node Type:TDP Oracle SUN
>  DSMI_DIR: /opt/tivoli/tsm/client/api/bin64
>  DSMI_ORC_CONFIG:
> /usr/local/unixsup/backup/tsm/dsm.opt-SWISP012-BIDWP1-ZP1
>  TDPO_OPTFILE:
> /usr/local/dba/scripts/backup/rman/tdpo/tdpo.opt-BIDWP1-BIDWP1-ZP1
>  Password Directory:   /opt/tivoli/tsm/client/oracle/bin64
>  Compression:  FALSE
>  License Information:  License file exists and contains valid license data.
>
> Of course, tdpoconf password used the TDPO_OPTFILE mentioned above.
>
> What authentication stage am I missing?
>
> The data should go over the storage agent path, and if that was the problem
> (I do not believe it is) errors associated with the Storage Agent would
> appear instead.
>
> Any ideas? Or elimination processes?
>
> Much appreciated,
>
> Matthew
>
>
>
>
>
> On 5/26/09, Matthew Large  wrote:
> >
> > D'oh!
> >
> > Sorry - both the client and the server are SunOS 5.10.
> >
> > My bad
> >
> >
> >  On Tue, May 26, 2009 at 10:57 AM, Matthew Large <
> > mlargedellt...@googlemail.com> wrote:
> >
> >> Hi Dave,
> >>
> >> Sure - the clients are on Sun 5.10 and the servers are W2003sp2.
> >>
> >> Much appreciated
> >>
> >>
> >>   On Fri, May 22, 2009 at 5:31 PM, Dave Canan 
> wrote:
> >>
> >>> Could you please include the client and server OS platform and level?
> >>> Thanks.
> >>>
> >>> On Fri, May 22, 2009 at 7:37 AM, Matthew Large <
> >>> mlargedellt...@googlemail.com> wrote:
> >>>
> >>> > Hi,
> >>> >
> >>> > I'm unable to ascertain the cause of this backup failure - the Oracle
> >>> > errors
> >>> > point to a disk problem, but then 'inappropriate ioctl for device'
> >>> looks
> >>> > like there is a problem with the destination device, not the source.
> >>> >
> >>> > Starting backup at 22-may-2009 14:44:34
> >>> > current log archived
> >>> > allocated channel: ORA_SBT_TAPE_1
> >>> > channel ORA_SBT_TAPE_1: sid=139 devtype=SBT_TAPE
> >>> > channel ORA_SBT_TAPE_1: Data Protection for Oracle: version 5.4.1.0
> >>> > RMAN-00571:
> ===
> >>> > RMAN-00569: === ERROR MESSAGE STACK FOLLOWS
> ===
> >>> > RMAN-00571:
> ===
> >>> > RMAN-03002: failure of backup command at 05/22/2009 14:45:08
> >>> > ORA-19587: error occurred reading 512 bytes at block number 1
> >>> > ORA-27091: unable to queue I/O
> >>> > ORA-27072: File I/O error
> >>> > SVR4 Error: 25: Inappropriate ioctl for device
> >>> > Additional information: 4
> >>> > Additional information: 1
> >>> >
> >>> > Recovery Manager complete.
> >>> > + STATUS=1
> >>> >
> >>> > STATUS=1
> >>> > Fri May 22 14:45:08 BST 2009: Backup failed
> >>> > Fri May 22 14:45:08 BST 2009: Finished
> >>> > swisp012#
> >>> >
> >>> >
> >>> > Any help wholly appreciated!
> >>> >
> >>> > Cheers,
> >>> > Matthew
> >>> >
> >>>
> >>>
> >>
> >>
> >>
> >
> >
>

Re: TDP Oracle failures

[Mark Yakushev]

It is possible that RMAN backup and tdpoconf use different dsm.opt (and
different dsm.sys server stanzas). One way to check if the same stanza is
used:

1. Add an invalid "option" to dsm.sys stanza that you use. E.g
...
bad_option 1
..

2. Run tdpoconf showenv  - should fail with "ANS0220E (RC400)  An invalid
option was found during option parsing."
3. Run RMAN backup - should also fail with the same error

If you get different behavior in #2 and 3, you are using different server
stanzas in dsm.sys

Is passwordaccess set to generate or prompt?

Regards,

Mark L. Yakushev
Advisory Software Engineer
Tivoli Storage Manager Development
IBM Corporation
Almaden Research Center




From: Matthew Large 
To:   ADSM-L@VM.MARIST.EDU
Date: 05/28/2009 06:17 AM
Subject:Re: [ADSM-L] TDP Oracle failures



Guys, I have some new info, with a slightly different problem, I hope it
can
help:

This is the message in the rman output file:

RMAN-03009: failure of backup command on ORA_SBT_TAPE_1 channel at
05/28/2009 13:55:26
ORA-19506: failed to create sequential file, name="688053317_5871_1.arc",
parms=""
ORA-27028: skgfqcre: sbtbackup returned error
ORA-19511: Error received from media manager layer, error text:
   ANS1025E (RC137)  Session rejected: Authentication failure


It says authentication failure, but I'm absolutely sure the tdpoconf
password process is working as I run the

TSM> upd no bidwp1-zp1-ora 

and the

UNIX> tdpoconf password 

with no errors. I even deleted the password file, and recreated it.
Running 'tdpoconf showenv ' returns succesfully:


IBM Tivoli Storage Manager for Databases:
Data Protection for Oracle
Version 5, Release 4, Level 1.0
(C) Copyright IBM Corporation 1997, 2007. All rights reserved.


Data Protection for Oracle Information
 Version:  5
 Release:  4
 Level:1
 Sublevel: 0
 Platform: 64bit TDP Oracle SUN

Tivoli Storage Manager Server Information
 Server Name:  TSM1-LANFREE
 Server Address:   TSM1
 Server Type:  Solaris SPARC
 Server Port:  1500
 Communication Method: TCP/IP

Session Information
 Owner Name:
 Node Name:BIDWP1-ZP1-ORA
 Node Type:TDP Oracle SUN
 DSMI_DIR: /opt/tivoli/tsm/client/api/bin64
 DSMI_ORC_CONFIG:
/usr/local/unixsup/backup/tsm/dsm.opt-SWISP012-BIDWP1-ZP1
 TDPO_OPTFILE:
/usr/local/dba/scripts/backup/rman/tdpo/tdpo.opt-BIDWP1-BIDWP1-ZP1.
 Password Directory:   /opt/tivoli/tsm/client/oracle/bin64
 Compression:  FALSE
 License Information:  License file exists and contains valid license data.

Of course, tdpoconf password used the TDPO_OPTFILE mentioned above.

What authentication stage am I missing?

The data should go over the storage agent path, and if that was the problem
(I do not believe it is) errors associated with the Storage Agent would
appear instead.

Any ideas? Or elimination processes?

Much appreciated,

Matthew





On 5/26/09, Matthew Large  wrote:
>
> D'oh!
>
> Sorry - both the client and the server are SunOS 5.10.>
>
> My bad
>
>
>  On Tue, May 26, 2009 at 10:57 AM, Matthew Large <.
> mlargedellt...@googlemail.com> wrote:
>
>> Hi Dave,
>>
>> Sure - the clients are on Sun 5.10 and the servers are W2003sp2.
>>
>> Much appreciated
>>
>>
>>   On Fri, May 22, 2009 at 5:31 PM, Dave Canan  wrote:
>>
>>> Could you please include the client and server OS platform and level?
>>> Thanks.
>>>
>>> On Fri, May 22, 2009 at 7:37 AM, Matthew Large <
>>> mlargedellt...@googlemail.com> wrote:
>>>
>>> > Hi,
>>> >
>>> > I'm unable to ascertain the cause of this backup failure - the Oracle
>>> > errors
>>> > point to a disk problem, but then 'inappropriate ioctl for device'
>>> looks
>>> > like there is a problem with the destination device, not the source.
>>> >
>>> > Starting backup at 22-may-2009 14:44:34
>>> > current log archived
>>> > allocated channel: ORA_SBT_TAPE_1:
>>> > channel ORA_SBT_TAPE_1: sid=139 devtype=SBT_TAPE
>>> > channel ORA_SBT_TAPE_1: Data Protection for Oracle: version 5.4.1.0.
>>> > RMAN-00571:
===
>>> > RMAN-00569: === ERROR MESSAGE STACK FOLLOWS
===
>>> > RMAN-00571:
===
>>> > RMAN-03002: failure of backup command at 05/22/2009 14:45:08
>>> > ORA-19587: error occurred reading 512 bytes at block number 1
>>> > ORA-27091: unable to queue I/O
>>> > ORA-27072: File I/O error
>>> > SVR4 Error: 25: Inappropriate ioctl for device
>>> > Additional information: 4
>>> > Additional information: 1
>>> >
>>> > Recovery Manager complete.
>>> > + STATUS=1
>>> >
>>> > STATUS=1
>>> > Fri May 22 14:45:08 BST 2009: Backup failed
>>> > Fri May 22 14:45:08 BST 2009: Finished
>>> > swisp012#
>>> >
>>> >
>>> > Any help wholly appreciated!:
>>> >
>>> > Cheers,
>>> > Matthew
>>> >
>>>
>>>
>>>
>>>
>>>
>>>
>>>

Re: TDP Oracle failures

[Jorge Amil]

 Hi,

Sometimes(i do not why) i have the same problem.

Try put 

passworddir /opt/tivoli/tsm/client/oracle/bin64

 

in the dsm.sys file

 

Kind regards

 

Jorge Garcia
> Date: Thu, 28 May 2009 14:14:43 +0100
> From: mlargedellt...@googlemail.com
> Subject: Re: [ADSM-L] TDP Oracle failures
> To: ADSM-L@VM.MARIST.EDU
> 
> Guys, I have some new info, with a slightly different problem, I hope it can
> help:
> 
> This is the message in the rman output file:
> 
> RMAN-03009: failure of backup command on ORA_SBT_TAPE_1 channel at
> 05/28/2009 13:55:26
> ORA-19506: failed to create sequential file, name="688053317_5871_1.arc",
> parms=""
> ORA-27028: skgfqcre: sbtbackup returned error
> ORA-19511: Error received from media manager layer, error text:
> ANS1025E (RC137) Session rejected: Authentication failure
> 
> 
> It says authentication failure, but I'm absolutely sure the tdpoconf
> password process is working as I run the
> 
> TSM> upd no bidwp1-zp1-ora 
> 
> and the
> 
> UNIX> tdpoconf password 
> 
> with no errors. I even deleted the password file, and recreated it.
> Running 'tdpoconf showenv ' returns succesfully:
> 
> 
> IBM Tivoli Storage Manager for Databases:
> Data Protection for Oracle
> Version 5, Release 4, Level 1.0
> (C) Copyright IBM Corporation 1997, 2007. All rights reserved.
> 
> 
> Data Protection for Oracle Information
> Version: 5
> Release: 4
> Level: 1
> Sublevel: 0
> Platform: 64bit TDP Oracle SUN
> 
> Tivoli Storage Manager Server Information
> Server Name: TSM1-LANFREE
> Server Address: TSM1
> Server Type: Solaris SPARC
> Server Port: 1500
> Communication Method: TCP/IP
> 
> Session Information
> Owner Name:
> Node Name: BIDWP1-ZP1-ORA
> Node Type: TDP Oracle SUN
> DSMI_DIR: /opt/tivoli/tsm/client/api/bin64
> DSMI_ORC_CONFIG:
> /usr/local/unixsup/backup/tsm/dsm.opt-SWISP012-BIDWP1-ZP1
> TDPO_OPTFILE:
> /usr/local/dba/scripts/backup/rman/tdpo/tdpo.opt-BIDWP1-BIDWP1-ZP1
> Password Directory: /opt/tivoli/tsm/client/oracle/bin64
> Compression: FALSE
> License Information: License file exists and contains valid license data.
> 
> Of course, tdpoconf password used the TDPO_OPTFILE mentioned above.
> 
> What authentication stage am I missing?
> 
> The data should go over the storage agent path, and if that was the problem
> (I do not believe it is) errors associated with the Storage Agent would
> appear instead.
> 
> Any ideas? Or elimination processes?
> 
> Much appreciated,
> 
> Matthew
> 
> 
> 
> 
> 
> On 5/26/09, Matthew Large  wrote:
> >
> > D'oh!
> >
> > Sorry - both the client and the server are SunOS 5.10.
> >
> > My bad
> >
> >
> > On Tue, May 26, 2009 at 10:57 AM, Matthew Large <
> > mlargedellt...@googlemail.com> wrote:
> >
> >> Hi Dave,
> >>
> >> Sure - the clients are on Sun 5.10 and the servers are W2003sp2.
> >>
> >> Much appreciated
> >>
> >>
> >> On Fri, May 22, 2009 at 5:31 PM, Dave Canan  wrote:
> >>
> >>> Could you please include the client and server OS platform and level?
> >>> Thanks.
> >>>
> >>> On Fri, May 22, 2009 at 7:37 AM, Matthew Large <
> >>> mlargedellt...@googlemail.com> wrote:
> >>>
> >>> > Hi,
> >>> >
> >>> > I'm unable to ascertain the cause of this backup failure - the Oracle
> >>> > errors
> >>> > point to a disk problem, but then 'inappropriate ioctl for device'
> >>> looks
> >>> > like there is a problem with the destination device, not the source.
> >>> >
> >>> > Starting backup at 22-may-2009 14:44:34
> >>> > current log archived
> >>> > allocated channel: ORA_SBT_TAPE_1
> >>> > channel ORA_SBT_TAPE_1: sid=139 devtype=SBT_TAPE
> >>> > channel ORA_SBT_TAPE_1: Data Protection for Oracle: version 5.4.1.0
> >>> > RMAN-00571: ===
> >>> > RMAN-00569: === ERROR MESSAGE STACK FOLLOWS ===
> >>> > RMAN-00571: ===
> >>> > RMAN-03002: failure of backup command at 05/22/2009 14:45:08
> >>> > ORA-19587: error occurred reading 512 bytes at block number 1
> >>> > ORA-27091: unable to queue I/O
> >>> > ORA-27072: File I/O error
> >>> > SVR4 Error: 25: Inappropriate ioctl for device
> >>> > Additional information: 4
> >>> > Additional information: 1
> >>> >
> >>> > Recovery Manager complete.
> >>> > + STATUS=1
> >>> >
> >>> > STATUS=1
> >>> > Fri May 22 14:45:08 BST 2009: Backup failed
> >>> > Fri May 22 14:45:08 BST 2009: Finished
> >>> > swisp012#
> >>> >
> >>> >
> >>> > Any help wholly appreciated!
> >>> >
> >>> > Cheers,
> >>> > Matthew
> >>> >
> >>>
> >>>
> >>
> >>
> >>
> >
> >

_
¡Quítate unos clics! Ahora, Internet Explorer 8 tiene todo lo que te gusta de 
Windows Live ¡Consíguelo gratis! 
http://ie8.msn.com/microsoft/internet-explorer-8/es-es/ie8.aspx

Re: TDP Oracle failures

[David McClelland]

Hi Matt,

Does the TSM Server activity log reveal anything - any of the associated
nodes attempting to log in by being denied?

Also, do you have any 'special characters' in the password? I understand
this has caused problems in the past.

And, of course - has this TDP client ever worked? Or has some event, known
or unknown, stopped it working from a previously healthy config?

Cheers,

/David Mc
London, UK


http://www.linkedin.com/in/dmcclelland


-Original Message-
From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of
Matthew Large
Sent: 28 May 2009 14:15
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] TDP Oracle failures

Guys, I have some new info, with a slightly different problem, I hope it can
help:

This is the message in the rman output file:

RMAN-03009: failure of backup command on ORA_SBT_TAPE_1 channel at
05/28/2009 13:55:26
ORA-19506: failed to create sequential file, name="688053317_5871_1.arc",
parms=""
ORA-27028: skgfqcre: sbtbackup returned error
ORA-19511: Error received from media manager layer, error text:
   ANS1025E (RC137)  Session rejected: Authentication failure


It says authentication failure, but I'm absolutely sure the tdpoconf
password process is working as I run the

TSM> upd no bidwp1-zp1-ora 

and the

UNIX> tdpoconf password 

with no errors. I even deleted the password file, and recreated it.
Running 'tdpoconf showenv ' returns succesfully:


IBM Tivoli Storage Manager for Databases:
Data Protection for Oracle
Version 5, Release 4, Level 1.0
(C) Copyright IBM Corporation 1997, 2007. All rights reserved.


Data Protection for Oracle Information
 Version:  5
 Release:  4
 Level:1
 Sublevel: 0
 Platform: 64bit TDP Oracle SUN

Tivoli Storage Manager Server Information
 Server Name:  TSM1-LANFREE
 Server Address:   TSM1
 Server Type:  Solaris SPARC
 Server Port:  1500
 Communication Method: TCP/IP

Session Information
 Owner Name:
 Node Name:BIDWP1-ZP1-ORA
 Node Type:TDP Oracle SUN
 DSMI_DIR: /opt/tivoli/tsm/client/api/bin64
 DSMI_ORC_CONFIG:
/usr/local/unixsup/backup/tsm/dsm.opt-SWISP012-BIDWP1-ZP1
 TDPO_OPTFILE:
/usr/local/dba/scripts/backup/rman/tdpo/tdpo.opt-BIDWP1-BIDWP1-ZP1
 Password Directory:   /opt/tivoli/tsm/client/oracle/bin64
 Compression:  FALSE
 License Information:  License file exists and contains valid license data.

Of course, tdpoconf password used the TDPO_OPTFILE mentioned above.

What authentication stage am I missing?

The data should go over the storage agent path, and if that was the problem
(I do not believe it is) errors associated with the Storage Agent would
appear instead.

Any ideas? Or elimination processes?

Much appreciated,

Matthew





On 5/26/09, Matthew Large  wrote:
>
> D'oh!
>
> Sorry - both the client and the server are SunOS 5.10.
>
> My bad
>
>
>  On Tue, May 26, 2009 at 10:57 AM, Matthew Large <
> mlargedellt...@googlemail.com> wrote:
>
>> Hi Dave,
>>
>> Sure - the clients are on Sun 5.10 and the servers are W2003sp2.
>>
>> Much appreciated
>>
>>
>>   On Fri, May 22, 2009 at 5:31 PM, Dave Canan  wrote:
>>
>>> Could you please include the client and server OS platform and level?
>>> Thanks.
>>>
>>> On Fri, May 22, 2009 at 7:37 AM, Matthew Large <
>>> mlargedellt...@googlemail.com> wrote:
>>>
>>> > Hi,
>>> >
>>> > I'm unable to ascertain the cause of this backup failure - the Oracle
>>> > errors
>>> > point to a disk problem, but then 'inappropriate ioctl for device'
>>> looks
>>> > like there is a problem with the destination device, not the source.
>>> >
>>> > Starting backup at 22-may-2009 14:44:34
>>> > current log archived
>>> > allocated channel: ORA_SBT_TAPE_1
>>> > channel ORA_SBT_TAPE_1: sid=139 devtype=SBT_TAPE
>>> > channel ORA_SBT_TAPE_1: Data Protection for Oracle: version 5.4.1.0
>>> > RMAN-00571:
===
>>> > RMAN-00569: === ERROR MESSAGE STACK FOLLOWS
===
>>> > RMAN-00571:
===
>>> > RMAN-03002: failure of backup command at 05/22/2009 14:45:08
>>> > ORA-19587: error occurred reading 512 bytes at block number 1
>>> > ORA-27091: unable to queue I/O
>>> > ORA-27072: File I/O error
>>> > SVR4 Error: 25: Inappropriate ioctl for device
>>> > Additional information: 4
>>> > Additional information: 1
>>> >
>>> > Recovery Manager complete.
>>> > + STATUS=1
>>> >
>>> > STATUS=1
>>> > Fri May 22 14:45:08 BST 2009: Backup failed
>>> > Fri May 22 14:45:08 BST 2009: Finished
>>> > swisp012#
>>> >
>>> >
>>> > Any help wholly appreciated!
>>> >
>>> > Cheers,
>>> > Matthew
>>> >
>>>
>>>
>>
>>
>>
>
>

No virus found in this incoming message.
Checked by AVG - www.avg.com
Version: 8.5.339 / Virus Database: 270.12.39/2134 - Release Date: 05/27/09
18:21:00

Re: TDP Oracle failures

[Matthew Large]

Guys, I have some new info, with a slightly different problem, I hope it can
help:

This is the message in the rman output file:

RMAN-03009: failure of backup command on ORA_SBT_TAPE_1 channel at
05/28/2009 13:55:26
ORA-19506: failed to create sequential file, name="688053317_5871_1.arc",
parms=""
ORA-27028: skgfqcre: sbtbackup returned error
ORA-19511: Error received from media manager layer, error text:
   ANS1025E (RC137)  Session rejected: Authentication failure


It says authentication failure, but I'm absolutely sure the tdpoconf
password process is working as I run the

TSM> upd no bidwp1-zp1-ora 

and the

UNIX> tdpoconf password 

with no errors. I even deleted the password file, and recreated it.
Running 'tdpoconf showenv ' returns succesfully:


IBM Tivoli Storage Manager for Databases:
Data Protection for Oracle
Version 5, Release 4, Level 1.0
(C) Copyright IBM Corporation 1997, 2007. All rights reserved.


Data Protection for Oracle Information
 Version:  5
 Release:  4
 Level:1
 Sublevel: 0
 Platform: 64bit TDP Oracle SUN

Tivoli Storage Manager Server Information
 Server Name:  TSM1-LANFREE
 Server Address:   TSM1
 Server Type:  Solaris SPARC
 Server Port:  1500
 Communication Method: TCP/IP

Session Information
 Owner Name:
 Node Name:BIDWP1-ZP1-ORA
 Node Type:TDP Oracle SUN
 DSMI_DIR: /opt/tivoli/tsm/client/api/bin64
 DSMI_ORC_CONFIG:
/usr/local/unixsup/backup/tsm/dsm.opt-SWISP012-BIDWP1-ZP1
 TDPO_OPTFILE:
/usr/local/dba/scripts/backup/rman/tdpo/tdpo.opt-BIDWP1-BIDWP1-ZP1
 Password Directory:   /opt/tivoli/tsm/client/oracle/bin64
 Compression:  FALSE
 License Information:  License file exists and contains valid license data.

Of course, tdpoconf password used the TDPO_OPTFILE mentioned above.

What authentication stage am I missing?

The data should go over the storage agent path, and if that was the problem
(I do not believe it is) errors associated with the Storage Agent would
appear instead.

Any ideas? Or elimination processes?

Much appreciated,

Matthew





On 5/26/09, Matthew Large  wrote:
>
> D'oh!
>
> Sorry - both the client and the server are SunOS 5.10.
>
> My bad
>
>
>  On Tue, May 26, 2009 at 10:57 AM, Matthew Large <
> mlargedellt...@googlemail.com> wrote:
>
>> Hi Dave,
>>
>> Sure - the clients are on Sun 5.10 and the servers are W2003sp2.
>>
>> Much appreciated
>>
>>
>>   On Fri, May 22, 2009 at 5:31 PM, Dave Canan  wrote:
>>
>>> Could you please include the client and server OS platform and level?
>>> Thanks.
>>>
>>> On Fri, May 22, 2009 at 7:37 AM, Matthew Large <
>>> mlargedellt...@googlemail.com> wrote:
>>>
>>> > Hi,
>>> >
>>> > I'm unable to ascertain the cause of this backup failure - the Oracle
>>> > errors
>>> > point to a disk problem, but then 'inappropriate ioctl for device'
>>> looks
>>> > like there is a problem with the destination device, not the source.
>>> >
>>> > Starting backup at 22-may-2009 14:44:34
>>> > current log archived
>>> > allocated channel: ORA_SBT_TAPE_1
>>> > channel ORA_SBT_TAPE_1: sid=139 devtype=SBT_TAPE
>>> > channel ORA_SBT_TAPE_1: Data Protection for Oracle: version 5.4.1.0
>>> > RMAN-00571: ===
>>> > RMAN-00569: === ERROR MESSAGE STACK FOLLOWS ===
>>> > RMAN-00571: ===
>>> > RMAN-03002: failure of backup command at 05/22/2009 14:45:08
>>> > ORA-19587: error occurred reading 512 bytes at block number 1
>>> > ORA-27091: unable to queue I/O
>>> > ORA-27072: File I/O error
>>> > SVR4 Error: 25: Inappropriate ioctl for device
>>> > Additional information: 4
>>> > Additional information: 1
>>> >
>>> > Recovery Manager complete.
>>> > + STATUS=1
>>> >
>>> > STATUS=1
>>> > Fri May 22 14:45:08 BST 2009: Backup failed
>>> > Fri May 22 14:45:08 BST 2009: Finished
>>> > swisp012#
>>> >
>>> >
>>> > Any help wholly appreciated!
>>> >
>>> > Cheers,
>>> > Matthew
>>> >
>>>
>>>
>>
>>
>>
>
>

Re: TDP Oracle failures

[Matthew Large]

D'oh!

Sorry - both the client and the server are SunOS 5.10.

My bad

On Tue, May 26, 2009 at 10:57 AM, Matthew Large <
mlargedellt...@googlemail.com> wrote:

> Hi Dave,
>
> Sure - the clients are on Sun 5.10 and the servers are W2003sp2.
>
> Much appreciated
>
>   On Fri, May 22, 2009 at 5:31 PM, Dave Canan  wrote:
>
>> Could you please include the client and server OS platform and level?
>> Thanks.
>>
>> On Fri, May 22, 2009 at 7:37 AM, Matthew Large <
>> mlargedellt...@googlemail.com> wrote:
>>
>> > Hi,
>> >
>> > I'm unable to ascertain the cause of this backup failure - the Oracle
>> > errors
>> > point to a disk problem, but then 'inappropriate ioctl for device' looks
>> > like there is a problem with the destination device, not the source.
>> >
>> > Starting backup at 22-may-2009 14:44:34
>> > current log archived
>> > allocated channel: ORA_SBT_TAPE_1
>> > channel ORA_SBT_TAPE_1: sid=139 devtype=SBT_TAPE
>> > channel ORA_SBT_TAPE_1: Data Protection for Oracle: version 5.4.1.0
>> > RMAN-00571: ===
>> > RMAN-00569: === ERROR MESSAGE STACK FOLLOWS ===
>> > RMAN-00571: ===
>> > RMAN-03002: failure of backup command at 05/22/2009 14:45:08
>> > ORA-19587: error occurred reading 512 bytes at block number 1
>> > ORA-27091: unable to queue I/O
>> > ORA-27072: File I/O error
>> > SVR4 Error: 25: Inappropriate ioctl for device
>> > Additional information: 4
>> > Additional information: 1
>> >
>> > Recovery Manager complete.
>> > + STATUS=1
>> >
>> > STATUS=1
>> > Fri May 22 14:45:08 BST 2009: Backup failed
>> > Fri May 22 14:45:08 BST 2009: Finished
>> > swisp012#
>> >
>> >
>> > Any help wholly appreciated!
>> >
>> > Cheers,
>> > Matthew
>> >
>>
>
>

Re: TDP Oracle failures

[Matthew Large]

Hi Dave,

Sure - the clients are on Sun 5.10 and the servers are W2003sp2.

Much appreciated

On Fri, May 22, 2009 at 5:31 PM, Dave Canan  wrote:

> Could you please include the client and server OS platform and level?
> Thanks.
>
> On Fri, May 22, 2009 at 7:37 AM, Matthew Large <
> mlargedellt...@googlemail.com> wrote:
>
> > Hi,
> >
> > I'm unable to ascertain the cause of this backup failure - the Oracle
> > errors
> > point to a disk problem, but then 'inappropriate ioctl for device' looks
> > like there is a problem with the destination device, not the source.
> >
> > Starting backup at 22-may-2009 14:44:34
> > current log archived
> > allocated channel: ORA_SBT_TAPE_1
> > channel ORA_SBT_TAPE_1: sid=139 devtype=SBT_TAPE
> > channel ORA_SBT_TAPE_1: Data Protection for Oracle: version 5.4.1.0
> > RMAN-00571: ===
> > RMAN-00569: === ERROR MESSAGE STACK FOLLOWS ===
> > RMAN-00571: ===
> > RMAN-03002: failure of backup command at 05/22/2009 14:45:08
> > ORA-19587: error occurred reading 512 bytes at block number 1
> > ORA-27091: unable to queue I/O
> > ORA-27072: File I/O error
> > SVR4 Error: 25: Inappropriate ioctl for device
> > Additional information: 4
> > Additional information: 1
> >
> > Recovery Manager complete.
> > + STATUS=1
> >
> > STATUS=1
> > Fri May 22 14:45:08 BST 2009: Backup failed
> > Fri May 22 14:45:08 BST 2009: Finished
> > swisp012#
> >
> >
> > Any help wholly appreciated!
> >
> > Cheers,
> > Matthew
> >
>

Re: TDP Oracle failures

[Dave Canan]

Could you please include the client and server OS platform and level?
Thanks.

On Fri, May 22, 2009 at 7:37 AM, Matthew Large <
mlargedellt...@googlemail.com> wrote:

> Hi,
>
> I'm unable to ascertain the cause of this backup failure - the Oracle
> errors
> point to a disk problem, but then 'inappropriate ioctl for device' looks
> like there is a problem with the destination device, not the source.
>
> Starting backup at 22-may-2009 14:44:34
> current log archived
> allocated channel: ORA_SBT_TAPE_1
> channel ORA_SBT_TAPE_1: sid=139 devtype=SBT_TAPE
> channel ORA_SBT_TAPE_1: Data Protection for Oracle: version 5.4.1.0
> RMAN-00571: ===
> RMAN-00569: === ERROR MESSAGE STACK FOLLOWS ===
> RMAN-00571: ===
> RMAN-03002: failure of backup command at 05/22/2009 14:45:08
> ORA-19587: error occurred reading 512 bytes at block number 1
> ORA-27091: unable to queue I/O
> ORA-27072: File I/O error
> SVR4 Error: 25: Inappropriate ioctl for device
> Additional information: 4
> Additional information: 1
>
> Recovery Manager complete.
> + STATUS=1
>
> STATUS=1
> Fri May 22 14:45:08 BST 2009: Backup failed
> Fri May 22 14:45:08 BST 2009: Finished
> swisp012#
>
>
> Any help wholly appreciated!
>
> Cheers,
> Matthew
>

Re: TDP Oracle Authentication failure

[Jorge Amil]

Hi,
First update the node password. update node node_name password.
Second I recomend in dsm.sys put
passworddir  /opt/tivoli/tsm/client/oracle/bin64/

And as Robben said :Check to see if the user under which the Oracle rman 
process is running
> has read permission to the TDPO.ora_xxx password file.

Hopes it help you.

Jorge Garcia

> Date: Thu, 14 May 2009 16:51:10 -0500
> From: robben.l...@usbank.com
> Subject: Re: [ADSM-L] TDP Oracle Authentication failure
> To: ADSM-L@VM.MARIST.EDU
> 
> Check to see if the user under which the Oracle rman process is running
> has read permission to the TDPO.ora_xxx password file.
> 
> Robben Leaf
> Enterprise Storage Backup and Retention
> 651-962-2698
> robben.l...@usbank.com
> 
> 
> 
> From:
> TSM User 
> To:
> ADSM-L@VM.MARIST.EDU
> Date:
> 05/14/2009 07:51 AM
> Subject:
> [ADSM-L] TDP Oracle Authentication failure
> Sent by:
> "ADSM: Dist Stor Manager" 
> 
> 
> 
> Hi all
> 
> 
> 
> I have a problem witch TDP for Oracle (Version 5, Release 4, Level 2.0) in
> HP_UX B.11.11
> 
> 
> 
> TDP was property configured.
> 
> 
> 
> When exec /opt/tivoli/tsm/client/oracle/bin64/tdpoconf password, TDP Works
> fine, and generate de password file (TDPO.xxx_ora)
> 
> 
> 
> But, when exec /opt/tivoli/tsm/client/oracle/bin64/tdpoconf
> SHOWENVironment,
> TSM server refuse (ANR0424W Session 52044 for node  (TDP Oracle
> HP)  refused
> - invalid password submitted.
> 
> 
> 
> And TDP show ANS1025E (RC137)  Session rejected: Authentication failure
> 
> 
> 
> Any help is appreciated
> 
> 
> 
> U.S. BANCORP made the following annotations
> -
> Electronic Privacy Notice. This e-mail, and any attachments, contains 
> information that is, or may be, covered by electronic communications privacy 
> laws, and is also confidential and proprietary in nature. If you are not the 
> intended recipient, please be advised that you are legally prohibited from 
> retaining, using, copying, distributing, or otherwise disclosing this 
> information in any manner. Instead, please reply to the sender that you have 
> received this communication in error, and then immediately delete it. Thank 
> you in advance for your cooperation.
> 
> 
> 
> -

_
Comparte, crea, disfruta… Descubre todo, en estos vídeos
http://www.windowslive.es 

Re: TDP Oracle Authentication failure

[Robben Leaf]

Check to see if the user under which the Oracle rman process is running
has read permission to the TDPO.ora_xxx password file.

Robben Leaf
Enterprise Storage Backup and Retention
651-962-2698
robben.l...@usbank.com



From:
TSM User 
To:
ADSM-L@VM.MARIST.EDU
Date:
05/14/2009 07:51 AM
Subject:
[ADSM-L] TDP Oracle Authentication failure
Sent by:
"ADSM: Dist Stor Manager" 



Hi all



I have a problem witch TDP for Oracle (Version 5, Release 4, Level 2.0) in
HP_UX B.11.11



TDP was property configured.



When exec /opt/tivoli/tsm/client/oracle/bin64/tdpoconf password, TDP Works
fine, and generate de password file (TDPO.xxx_ora)



But, when exec /opt/tivoli/tsm/client/oracle/bin64/tdpoconf
SHOWENVironment,
TSM server refuse (ANR0424W Session 52044 for node  (TDP Oracle
HP)  refused
- invalid password submitted.



And TDP show ANS1025E (RC137)  Session rejected: Authentication failure



Any help is appreciated



U.S. BANCORP made the following annotations
-
Electronic Privacy Notice. This e-mail, and any attachments, contains 
information that is, or may be, covered by electronic communications privacy 
laws, and is also confidential and proprietary in nature. If you are not the 
intended recipient, please be advised that you are legally prohibited from 
retaining, using, copying, distributing, or otherwise disclosing this 
information in any manner. Instead, please reply to the sender that you have 
received this communication in error, and then immediately delete it. Thank you 
in advance for your cooperation.



-

Re: TDP Oracle Authentication failure

[Howard Coles]

And make sure "passwordaccess" is equal to prompt, not generate in the
dsm.sys stanza for the TDP.

See Ya'
Howard


> -Original Message-
> From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf
> Of David McClelland
> Sent: Thursday, May 14, 2009 8:03 AM
> To: ADSM-L@VM.MARIST.EDU
> Subject: Re: [ADSM-L] TDP Oracle Authentication failure
> 
> Obvious question: is the password you're configuring on the client the
> same
> as that you've defined for that node on the TSM Server? Did you try an
> `UPDATE NODE  ` just to make sure?
> 
> /DMc
> London, UK
> 
> -Original Message-
> From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf
> Of TSM
> User
> Sent: 14 May 2009 13:51
> To: ADSM-L@VM.MARIST.EDU
> Subject: [ADSM-L] TDP Oracle Authentication failure
> 
> Hi all
> 
> 
> 
> I have a problem witch TDP for Oracle (Version 5, Release 4, Level
2.0)
> in
> HP_UX B.11.11
> 
> 
> 
> TDP was property configured.
> 
> 
> 
> When exec /opt/tivoli/tsm/client/oracle/bin64/tdpoconf password, TDP
> Works
> fine, and generate de password file (TDPO.xxx_ora)
> 
> 
> 
> But, when exec /opt/tivoli/tsm/client/oracle/bin64/tdpoconf
> SHOWENVironment,
> TSM server refuse (ANR0424W Session 52044 for node  (TDP Oracle
> HP)  refused
> - invalid password submitted.
> 
> 
> 
> And TDP show ANS1025E (RC137)  Session rejected: Authentication
failure
> 
> 
> 
> Any help is appreciated

Re: TDP Oracle Authentication failure

[David McClelland]

Obvious question: is the password you're configuring on the client the same
as that you've defined for that node on the TSM Server? Did you try an
`UPDATE NODE  ` just to make sure?

/DMc
London, UK

-Original Message-
From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of TSM
User
Sent: 14 May 2009 13:51
To: ADSM-L@VM.MARIST.EDU
Subject: [ADSM-L] TDP Oracle Authentication failure

Hi all



I have a problem witch TDP for Oracle (Version 5, Release 4, Level 2.0) in
HP_UX B.11.11



TDP was property configured.



When exec /opt/tivoli/tsm/client/oracle/bin64/tdpoconf password, TDP Works
fine, and generate de password file (TDPO.xxx_ora)



But, when exec /opt/tivoli/tsm/client/oracle/bin64/tdpoconf SHOWENVironment,
TSM server refuse (ANR0424W Session 52044 for node  (TDP Oracle
HP)  refused
- invalid password submitted.



And TDP show ANS1025E (RC137)  Session rejected: Authentication failure



Any help is appreciated

Re: TDP-Oracle+RMAN

[Neil Rasmussen]

Every Oracle backuppiece starts a new TSM session. Look at the RMAN's User
Guide on how to use the 'filesperset' for starters. There are a few other
parameters that you can use in RMAN to help tune your backups.


Regards,

Neil Rasmussen
Tivoli Storage Manager Client Development
IBM Corporation
Almaden Research Center
650 Harry Road
San Jose, CA 95120-6099
Phone: 408.927.2206 (T/L: 457-2206)
[EMAIL PROTECTED]



[EMAIL PROTECTED]
Sent by: "ADSM: Dist Stor Manager" 
02/21/2008 11:23 AM
Please respond to
"ADSM: Dist Stor Manager" 


To
ADSM-L@VM.MARIST.EDU
cc

Subject
TDP-Oracle+RMAN






Hi,

recently I reviewed backup sessions of some Oracle DB servers (RMAN).
Our DB servers have about 100-400 sessions a day. Can someone explain
in which cases there are new sessions opened by TDPO/RMAN and how to
reduce session usage. I've investigated actlog and there were many many
session open/close operations within one minute. I think that might
stress the backup server unnecessarily.

Thanks
Regards,
..--Egonle

More new features than ever.  Check out the new AIM(R) Mail ! -
http://webmail.aim.com

Re: TDP Oracle client backup schedule and status

[goc]

... and i forgot ... doing LANFree :-)

On 10/16/07, goc <[EMAIL PROTECTED]> wrote:
> actually it can ... quite some magic here but it works here on +80 oracle DB's
>
> http://www.adsm.org/lists/html/ADSM-L/2007-09/msg00322.html
>
> 
> TSM5411 on AIX5.2
> DB's on HPUX IA64
> LTO3 x12 in 2x3584
>
> On 10/16/07, Tim Brown <[EMAIL PROTECTED]> wrote:
> > Can the TDP Oracle client backup be scheduled with the TSM scheduler
> > or does it have to be scheduled with the Oracle Backup Manager.
> >
> > I would like to know the backup status of the TDP Oracle client from the
> > perspective of TSM and not Oracle.
> >
> > Tim Brown
> > Systems Specialist - Project Leader
> > Central Hudson Gas & Electric
> > 284 South Ave
> > Poughkeepsie, NY 12601
> > Email: [EMAIL PROTECTED]
> > Phone: 845-486-5643
> > Fax: 845-486-5921
> > Cell: 845-235-4255
> >
>

Re: TDP Oracle client backup schedule and status

[goc]

actually it can ... quite some magic here but it works here on +80 oracle DB's

http://www.adsm.org/lists/html/ADSM-L/2007-09/msg00322.html


TSM5411 on AIX5.2
DB's on HPUX IA64
LTO3 x12 in 2x3584

On 10/16/07, Tim Brown <[EMAIL PROTECTED]> wrote:
> Can the TDP Oracle client backup be scheduled with the TSM scheduler
> or does it have to be scheduled with the Oracle Backup Manager.
>
> I would like to know the backup status of the TDP Oracle client from the
> perspective of TSM and not Oracle.
>
> Tim Brown
> Systems Specialist - Project Leader
> Central Hudson Gas & Electric
> 284 South Ave
> Poughkeepsie, NY 12601
> Email: [EMAIL PROTECTED]
> Phone: 845-486-5643
> Fax: 845-486-5921
> Cell: 845-235-4255
>

Re: TDP Oracle 5.4.1 ERROR

[Gregory Lynch]

I am new to this, but I ran into a similar problem last week while
upgrading  Oracle TDP. It wound up being a permission issue on some of the
log files and the password file( ./tdpoconf password ) was not properly
created. I would check everything in /opt/tivoli/tsm/client/api/bin64 and
/opt/tivoli/tsm/client/oracle/bin64 and make sure that the proper
permission's are set.


Greg






***
Gregory Lynch
Lead Programmer Analyst
IT Infrastructure/Systems Administration
Stony Brook University Medical Center
HSC Level 3, Room 121  ZIP 8037
Phone: 631-444-9783
[EMAIL PROTECTED]

This e- mail message, including any attachments,
is for the sole use of the intended recipient(s) and may
contain confidential and privileged information.
Any unauthorized review, use, disclosure or distribution is prohibited.
If you are not the intended recipient, please contact the sender
by e-mail and destroy all copies of the original.




TSM User <[EMAIL PROTECTED]>
Sent by: "ADSM: Dist Stor Manager" 
08/29/2007 06:07 PM
Please respond to
"ADSM: Dist Stor Manager" 


To
ADSM-L@VM.MARIST.EDU
cc

Subject
[ADSM-L] TDP Oracle 5.4.1 ERROR






Good afternoon.

Somebody can help me?

Gracias





RMAN> run {

2> allocate channel oem_sbt_backup1 type 'SBT_TAPE' format '%U' parms
'ENV=(TDPO_OPTFILE=/opt/tivoli/tsm/client/oracle/bin64/tdpo.opt)';

backup incremental level 1 cumulative database;

3> 4> backup archivelog all not backed up;

5> delete noprompt obsolete recovery window of 31 days device type
'SBT_TAPE';

}6>

using target database control file instead of recovery catalog

RMAN-00571: ===

RMAN-00569: === ERROR MESSAGE STACK FOLLOWS ===

RMAN-00571: ===

RMAN-03009: failure of allocate command on oem_sbt_backup1 channel at
08/29/2007 18:47:25

ORA-19554: error allocating device, device type: SBT_TAPE, device name:

ORA-27000: skgfqsbi: failed to initialize storage subsystem (SBT) layer

Linux-x86_64 Error: 406: Error desconocido 406

Additional information: 7011

ORA-19511: Error received from media manager layer, error text:

   SBT error = 7011, errno = 406, sbtopen: system error





TSM Server:  5.4 Suse Linux 10 64 (Intel)

TDP Oracle 5.4.1 Suse Linux 10 64 (Intel)



./tdpoconf showenv

Sublevel: 0

 Platform: 64bit TDPO LinuxAMD64

Tivoli Storage Manager Server Information

 Server Name:  DPIPROD_ORACLE

 Server Address:   10.1.2.251

 Server Type:  Linux/x86_64

 Server Port:  1500

 Communication Method: TCP/IP



Session Information

 Owner Name:   oracle

 Node Name:DPIPROD_ORACLE

 Node Type:TDPO LinuxAMD64

 DSMI_DIR: /opt/tivoli/tsm/client/api/bin64

 DSMI_ORC_CONFIG:  /opt/tivoli/tsm/client/api/bin64/dsm.opt

 TDPO_OPTFILE: /opt/tivoli/tsm/client/oracle/bin64/tdpo.opt

 Password Directory:   /opt/tivoli/tsm/client/oracle/bin64

 Compression:  FALSE

 License Information:  License file exists and contains valid license
data.

Re: TDP Oracle

[Allen S. Rout]

>> On Fri, 20 Oct 2006 16:13:54 -0400, Lawrence Clark <[EMAIL PROTECTED]> said:

> the problem you have with them not deleteing automaticly may be in
> the client (node) def. You have to make sure Backup Delete Allowed?:
> Yes is set. do a q node x f=d and verify.  If it is not set,
> even if they product issues a delete it will not occur.


Thanks, but yes, we touched that base.

- Allen S. Rout

Re: TDP Oracle

[Jurjen Oskam]

On Fri, Oct 20, 2006 at 12:10:17PM -0700, Gill, Geoffrey L. wrote:

> 3.If this ignores the retention values set in the management class
> settings, and I believe it still does, do I need a specific management
> class for them?

A TDP for Oracle node *only* has active files on the TSM server, as Oracle
by default guarantees that only unique filenames are sent. This means that
the retention parameters concerning "extra versions" are irrelevant.

In addition to that, when Oracle RMAN deletes a backup, it doesn't only
delete the file on the TSM server, but also the information it has in the
RMAN repository required to restore that file. So, while you can set up
a TDP node such that inactive files will be retained on the TSM server, it
doesn't make sense because the file is useless without the RMAN repository
information, which is already gone.

The retention values in the management class are certainly not ignored. If
you don't set them correctly (as described above), you're almost certainly
storing too much data on the TSM server.

> 1.Can we use a domain we have in place already and if so are there
> any settings we need to look at?
> 4.I am assuming we should use a specific node name for these
> backups and not let them use the node name that is now backing up to the
> server. Still correct right?

You can use an existing domain, but it's much simpler to use a dedicated
TDP for Oracle domain. You only need to set one managementclass containing
one copygroup in that domain. That way, it's guaranteed that the RMAN
backups are bound to the correct management class and you don't have to
fiddle with include statements in the API configuration on the client.

And you should indeed use a specific node for the TDP backups. The TDP node
goes in the TDP domain.

> 2.I believe expiring of objects is done from the RMAN side. If
> this is correct how do I know they are keeping, or maybe better
> described as deleting, what they should?

You need access to the RMAN repository ('recovery catalog') for that.
The RMAN repository can be located in the database itself, or be a
database on its own. Normally RMAN deletes all obsolete objects (as
specified by the DBA) on its own, but there are situations where RMAN
doesn't know that a certain file is stored on the TSM server. That's where
the tdposync tool comes in. It checks the RMAN repository, and then checks
what's available on the TSM server. If there are files in TSM which RMAN
doesn't know about, it can delete those files on the TSM server.

--
Jurjen Oskam

Savage's Law of Expediency:
You want it bad, you'll get it bad.

Re: TDP Oracle

[Lawrence Clark]

the problem you have with them not deleteing automaticly may be in the
client (node) def. You have to make sure
Backup Delete Allowed?: Yes is set. do a q node x f=d and verify.
If it is not set, even if they product issues a delete it will not
occur.

>>> [EMAIL PROTECTED] 10/20/06 3:28 PM >>>
>> On Fri, 20 Oct 2006 12:10:17 -0700, "Gill, Geoffrey L."
<[EMAIL PROTECTED]> said:


> 2.I believe expiring of objects is done from the RMAN side. If
> this is correct how do I know they are keeping, or maybe better
> described as deleting, what they should?

Don't worry about that.  They don't.

as in, they don't delete what they're supposed to, they keep all sorts
of crud they know they aren't supposed to. We've got an issue open
with them since forever ago.

We've taken to periodically switching node names, and then blowing
away the old one.   Eugh.


> 4.I am assuming we should use a specific node name for these
> backups and not let them use the node name that is now backing up to
the
> server. Still correct right?

I think that's the best plan.


- Allen S. Rout


The information contained in this electronic message and any attachments to 
this message are intended for the exclusive use of the addressee(s) and may 
contain information that is confidential, privileged, and/or otherwise exempt 
from disclosure under applicable law.  If this electronic message is from an 
attorney or someone in the Legal Department, it may also contain confidential 
attorney-client communications which may be privileged and protected from 
disclosure.  If you are not the intended recipient, be advised that you have 
received this message in error and that any use, dissemination, forwarding, 
printing, or copying is strictly prohibited.  Please notify the New York State 
Thruway Authority immediately by either responding to this e-mail or calling 
(518) 436-2700, and destroy all copies of this message and any attachments.

Re: TDP Oracle

[Allen S. Rout]

>> On Fri, 20 Oct 2006 12:10:17 -0700, "Gill, Geoffrey L." <[EMAIL PROTECTED]> 
>> said:


> 2.I believe expiring of objects is done from the RMAN side. If
> this is correct how do I know they are keeping, or maybe better
> described as deleting, what they should?

Don't worry about that.  They don't.

as in, they don't delete what they're supposed to, they keep all sorts
of crud they know they aren't supposed to. We've got an issue open
with them since forever ago.

We've taken to periodically switching node names, and then blowing
away the old one.   Eugh.


> 4.I am assuming we should use a specific node name for these
> backups and not let them use the node name that is now backing up to the
> server. Still correct right?

I think that's the best plan.


- Allen S. Rout

Re: TDP Oracle

[Lawrence Clark]

For that part the manual was clear. Better to just create a separte
domain (policy/management class) and set the default mangement class to
veredelte=o reteonly=0

Yes, the manual suggest a separate node name and when you define that
node name you would set it to the separate domain.

>>> [EMAIL PROTECTED] 10/20/06 3:10 PM >>>
Looks like folks here are finally looking into using this function
here and I want to know how things should be set on the TSM server
side
so I have a couple of questions.

1.  Can we use a domain we have in place already and if so are
there
any settings we need to look at?
2.  I believe expiring of objects is done from the RMAN side. If
this is correct how do I know they are keeping, or maybe better
described as deleting, what they should?
3.  If this ignores the retention values set in the management
class
settings, and I believe it still does, do I need a specific management
class for them?
4.  I am assuming we should use a specific node name for these
backups and not let them use the node name that is now backing up to
the
server. Still correct right?
5.  

Thanks,

Geoff Gill
TSM Administrator
PeopleSoft Sr. Systems Administrator
SAIC M/S-G1b
(858)826-4062
Email: [EMAIL PROTECTED]





The information contained in this electronic message and any attachments to 
this message are intended for the exclusive use of the addressee(s) and may 
contain information that is confidential, privileged, and/or otherwise exempt 
from disclosure under applicable law.  If this electronic message is from an 
attorney or someone in the Legal Department, it may also contain confidential 
attorney-client communications which may be privileged and protected from 
disclosure.  If you are not the intended recipient, be advised that you have 
received this message in error and that any use, dissemination, forwarding, 
printing, or copying is strictly prohibited.  Please notify the New York State 
Thruway Authority immediately by either responding to this e-mail or calling 
(518) 436-2700, and destroy all copies of this message and any attachments.

Re: TDP oracle to new domain policy - error deleting old backups from old domain

[Peter Hitchman]

Hi,
I believe what you said about the management classes is true. What rman errors 
are you getting? Did you change the nodename? Doing that upsets the combination 
of rman and tdp in finding backups.

Regards

Pete

-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Behalf Of
Tae Kim
Sent: 30 January 2006 17:27
To: ADSM-L@VM.MARIST.EDU
Subject: [ADSM-L] TDP oracle to new domain policy - error deleting old
backups from old domain


Got a question for you all.

Just move a tdp for oracle node to a different domain policy. this domain
policy does not have management class of the same name that the node was
using for the backup from its old domain policy.  It is my understanding
that once the node gets moved to a new domain, it would look for
management class of the same name that it has bind its backups to and use
that management class. If that management class does not exists, it would
use the default management class.  Is this true?  Also we are having
issues with deleting older DB from RMAN. what can cause these issues? Also
the default management class of the new policy domain has different
retention time. Would it help if I created the same management class with
same backup copy group as the old one in the new policy domain?

TIA,
Tae


Here is the env.
TSM 5.2.4.4 on AIX 5.2 ML5
TDP for Oracle 5.2 on AIX 5.2 ML5

config of the node

  Platform: TDP Oracle AIX
   Client OS Level: 5.2
Client Version: Version 5, Release 2, Level 2.5
Policy Domain Name: FI_FIRST_DOM
 Last Access Date/Time: 01/30/06 12:15:13
Days Since Last Access: <1
Password Set Date/Time: 03/23/04 13:45:27
   Days Since Password Set: 678
 Invalid Sign-on Count: 0
   Locked?: No
   Contact:
   Compression: Client
   Archive Delete Allowed?: Yes
Backup Delete Allowed?: Yes
Registration Date/Time: 03/22/04 11:56:24
 Registering Administrator:
Last Communication Method Used: Tcp/Ip
   Bytes Received Last Session: 4.50 M
   Bytes Sent Last Session: 17,599
  Duration of Last Session: 0.67
   Pct. Idle Wait Last Session: 18.32
  Pct. Comm. Wait Last Session: 60.21
  Pct. Media Wait Last Session: 0.00
 Optionset:
   URL:
 Node Type: Client
Password Expiration Period: 9,999 Day(s)
 Keep Mount Point?: No
  Maximum Mount Points Allowed: 2
Auto Filespace Rename : No
 Validate Protocol: No
   TCP/IP Name:
TCP/IP Address:
Globally Unique ID:
 Transaction Group Max: 0
   Data Write Path: ANY
Data Read Path: ANY
Session Initiation: ClientOrServer
High-level Address:
 Low-level Address:

+=+
This message may contain confidential and/or privileged
information.  If you are not the addressee or authorized to
receive this for the addressee, you must not use, copy,
disclose or take any action based on this message or any
information herein.  If you have received this message in
error, please advise the sender immediately by reply e-mail
and delete this message.  Thank you for your cooperation.
+=+

Re: TDP Oracle

[Neil Rasmussen]

I believe this to be possible.

'SBT_TAPE' tells Oracle/Rman that you want to use a 3rd party media
manager (ie. TDP for Oracle) for your backups. 'SBT_DISK' tells
Oracle/RMAN that you want to use Oracle's internal disk library which
means that you can dump it to local disk. Keep in mind that I have never
attempted this but you should be able to redirect to a tape device rather
than a disk. Again I have never gone directly to tape using this method
but at first glance it seems possible; you may want to refer the
Oracle/Rman User's Guide on this. To be sure, to go to disk your rman
script would look something like the following (remeber this is just an
example):

run
{
   allocate channel t1 type 'SBT_DISK';

   backup controlfile;
   backup database;

}


Regards,

Neil Rasmussen
Software Development
Data Protection for Oracle
[EMAIL PROTECTED]




Kurt Beyers <[EMAIL PROTECTED]>
Sent by: "ADSM: Dist Stor Manager" 
09/22/2005 10:50 PM
Please respond to
"ADSM: Dist Stor Manager"


To
ADSM-L@VM.MARIST.EDU
cc

Subject
TDP Oracle






Good morning,

A rather general question.

Is it possible to take the backup of only 1 instance with the TDP for
Oracle
(an instance that would be used for testing in TSM) and to take the backup
of the other (production) instances to a local tape with an RMAN script?

Both backups (TPD and local RMAN backup) do allocate 'sbt_tape' as
channel.
In other backup solutions, a symbolic link of the Oracle library
$ORACLE_HOME/lib/libobk.sl is created to the library of the backup
solution.
Which means that a backup to a local device using a RMAN script is no
longer
possible.

I did not find out if this is the case too with the TDP for Oracle. Must
all
Oracle instances be restarted after the installation of the TDP or only
the
instance that you want to backup with the TDP or is there no restart at
all.

Thanks,

Kurt Beyers

Re: TDP Oracle Linux Client

[Del Hoobler]

Look here:


http://www-306.ibm.com/software/tivoli/products/storage-mgr-db/platforms.html

Thanks,

Del



"ADSM: Dist Stor Manager"  wrote on 07/06/2005
11:16:12 AM:

> Hello *SM'ers,
> does a Linux Version of TDP For Oracle exist?
>
> Cheers,
> ku
> --
> Darth Vader:
>Impressive. Most impressive. Obi-wan has taught
>you well. You have controlled your fear. Now,
>release your anger! Only your hatred can destroy me!

Re: tdp oracle for AIX 5.3

[Steve S Lafrance]

Hi Youssef !
If you look at the readme of the DP for Oracle 5.2.0 version:
.
Data Protection for Oracle 5.2.0 on AIX 4.3 requires the following MINIMUM
software levels:

  - AIX Version 4.3.3 (32 or 64bit), plus any patches required by Oracle.
.
The 2.2.1 version was also supported on AIX 4.3. The DP for Oracle 5.1.5
is using the same code as 2.2.1 ...so it also support the AIX 4.3 platform.
.
Bonne journée

--
Steve Lafrance
IBM Tivoli Storage Manager
Level II Support -  Tivoli Certified Consultant
International Business Machines


AMHOUCHE Youssef <[EMAIL PROTECTED]>@VM.MARIST.EDU> on 2005-02-15
10:36:42

Please respond to "ADSM: Dist Stor Manager" 

Sent by:"ADSM: Dist Stor Manager" 


To:ADSM-L@VM.MARIST.EDU
cc:
Subject:tdp oracle for AIX 5.3


Hi TSMers

What is the version of tdp oracle that is compatible  with AIX 5.3.

Thank you


===

Ce message et toutes les pieces jointes (ci-apres le "message")
sont confidentiels et etablis a l'intention exclusive de ses destinataires.
Toute utilisation ou diffusion non autorisee est interdite.
Tout message electronique est susceptible d'alteration.
La SOCIETE GENERALE et ses filiales declinent toute responsabilite
au titre de ce message s'il a ete altere, deforme ou falsifie.

===

This message and any attachments (the "message") are confidential
and intended solely for the addressees.
Any unauthorized use or dissemination is prohibited.
E-mails are susceptible to alteration.
Neither SOCIETE GENERALE nor any of its subsidiaries or affiliates
shall be liable for the message if altered, changed or falsified.

===

Re: tdp oracle for AIX 5.3

[Loon, E.J. van - SPLXM]

Hi Youssef!
Checkout the DP for Oracle 5.2.0 readme. It mentions AIX 5.1 as minimum
level, along with Oracle 9.2.0 or later.
http://ftp.rz.uni-karlsruhe.de/pub/tsm/mirror/maintenance/tivoli-data-protec
tion/oracle_aix/v520/aix51/README.TDPO.AIX51
Kindest regards,
Eric van Loon
KLM Royal Dutch Airlines


-Original Message-
From: AMHOUCHE Youssef [mailto:[EMAIL PROTECTED]
Sent: Tuesday, February 15, 2005 16:37
To: ADSM-L@VM.MARIST.EDU
Subject: tdp oracle for AIX 5.3


Hi TSMers

What is the version of tdp oracle that is compatible  with AIX 5.3.

Thank you


===

Ce message et toutes les pieces jointes (ci-apres le "message")
sont confidentiels et etablis a l'intention exclusive de ses destinataires.
Toute utilisation ou diffusion non autorisee est interdite.
Tout message electronique est susceptible d'alteration.
La SOCIETE GENERALE et ses filiales declinent toute responsabilite
au titre de ce message s'il a ete altere, deforme ou falsifie.

===

This message and any attachments (the "message") are confidential
and intended solely for the addressees.
Any unauthorized use or dissemination is prohibited.
E-mails are susceptible to alteration.
Neither SOCIETE GENERALE nor any of its subsidiaries or affiliates
shall be liable for the message if altered, changed or falsified.

===


**
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.
**

Re: TDP ORACLE Backup

[Mike Angel]

Hi,

sorry for the late answer, I hope these informations are still useful for you.

RMAN is able to restore to any Point Of Time on wich you have the backup.

There are many RMAN script options that can be used to set the Point of Time:

- until time 'date_string' wich specifies a time as an upper limit.

- until scn integer wich specifies an SCN as an upper limit.

- until logseq integer wich specifies a redo log sequence number as an upper 
limit.

The until clause can be specified on the Restore and on the Recover commands 
or, more usefull, with a Set command like the below script:

run

{

set until time "to_date('07-DEC-2004 09:00:00','DD-MON- HH24:MI:SS')";

allocate channel TsmCh1 type 'sbt_tape';

allocate channel TsmCh2 type 'sbt_tape';

restore database;

sql "alter database mount";

recover database;

sql "alter database open resetlogs";

}

As shown in the script, after a Point in Time recover the database must be 
opened with the resetlogs option.

For all informations regarding this issue there is the Oracle manual:

Oracle8i Backup and Recovery Guide Release 8.1.5 - a67773.pdf

and the RedBook manual:

Backing Up Oracle Using Tivoli Storage Management - sg246249.pdf

Regards,

Mike Angel

Aix and Oracle System Engineer

-Messaggio originale-

Da: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] conto di

Pawel Wozniczka

Inviato: giovedl 21 ottobre 2004 11.09

A: ADSM-L@VM.MARIST.EDU

Oggetto: Re: TDP Oracle Restore



>Question is :

>when i go about restore, how would i know which backup is being restored..

the

>active backup?? what would i need to do to restore any inactive backup??

Hello

As far as I know "rman" always uses the latest available backupsets, and

there is no official and supported way to restore previous versions of a

database.

But, as usually, there is a trick that makes is possibile, I use it quite

frequently in order to test & verify my oracle-tdp backups.

The trick is based on the fact that if the "rman" finds that the latest

backupsets are marked "unavailable" it will search its database backwards

until available backupsets are found and those backupsets will be used for

restore operations.

To summarize:

a) change status of the rman backupsets that You do NOT want to be used to

unavailable (change backupset xxx unavailable)

b) restore database

c) change status of the rman backupsets that were modified in step "a" back

to available (change backupset xxx available)

To make it easier I created a shell/rman script. (It's strongly hard-coded

to my environment, but with a little effort can be adjusted to be useful in

other environments).

Please let me know whether You are interested, if yes I can send that script

and try to assist in customizing it.

kind regards

Pawel W.

[EMAIL PROTECTED]





Mike Angel

Unix and Tsm Specialist

-
Nuovo Yahoo! Messenger E' molto piy divertente: Audibles, Avatar, Webcam, 
Giochi, Rubrica  Scaricalo ora!

Re: TDP/ORACLE Backup

[Neil Rasmussen]

Yes there is a way to change this. By specifying the option:

TDPO_AVG_SIZE   n  (where 'n' is the size estimate, in MB, you want TDP
Oracle to use with the TSM Server)

Using this option overrides any size that Oracle specifies and can cause
other performance problems on the the TSM Server. However, this option is
very useful if you are using compression and the TSM Server is up against
the wall with regards to availabe storage space for backups.


Regards,

Neil Rasmussen
Software Development
Data Protection for Oracle
[EMAIL PROTECTED]




"Wholey, Joseph (IDS DM&DS)" <[EMAIL PROTECTED]>
Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
12/06/2004 09:24 AM
Please respond to
"ADSM: Dist Stor Manager"


To
[EMAIL PROTECTED]
cc

Subject
Re: TDP/ORACLE Backup






Is it possible to change the estimated size?

-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Behalf Of
Neil Rasmussen
Sent: Monday, December 06, 2004 12:07 PM
To: [EMAIL PROTECTED]
Subject: Re: TDP/ORACLE Backup


Keep in mind that TDP Oracle just passes on what Oracle/Rman asks it to.
So for DB estimation, TDP Oracle uses the value that Oracle passes to it
(which probably is overestimated). If compression is turned on then this
value is grossly overestimated.


Regards,

Neil Rasmussen
Software Development
Data Protection for Oracle
[EMAIL PROTECTED]




"Wholey, Joseph (IDS DM&DS)" <[EMAIL PROTECTED]>
Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
12/06/2004 08:08 AM
Please respond to
"ADSM: Dist Stor Manager"


To
[EMAIL PROTECTED]
cc

Subject
TDP/ORACLE Backup






When running a TDP for Oracle backup, does TDP lock the estimated amount
of the storage pool which it thinks it needs to complete the backup?


If you are not an intended recipient of this e-mail, please notify the
sender, delete it and do not read, act upon, print, disclose, copy, retain
or redistribute it. Click here for important additional terms relating to
this e-mail. http://www.ml.com/email_terms/

Re: TDP/ORACLE Backup

Is it possible to change the estimated size?  

-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Behalf Of
Neil Rasmussen
Sent: Monday, December 06, 2004 12:07 PM
To: [EMAIL PROTECTED]
Subject: Re: TDP/ORACLE Backup


Keep in mind that TDP Oracle just passes on what Oracle/Rman asks it to.
So for DB estimation, TDP Oracle uses the value that Oracle passes to it
(which probably is overestimated). If compression is turned on then this
value is grossly overestimated.


Regards,

Neil Rasmussen
Software Development
Data Protection for Oracle
[EMAIL PROTECTED]




"Wholey, Joseph (IDS DM&DS)" <[EMAIL PROTECTED]>
Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
12/06/2004 08:08 AM
Please respond to
"ADSM: Dist Stor Manager"


To
[EMAIL PROTECTED]
cc

Subject
TDP/ORACLE Backup






When running a TDP for Oracle backup, does TDP lock the estimated amount
of the storage pool which it thinks it needs to complete the backup?


If you are not an intended recipient of this e-mail, please notify the
sender, delete it and do not read, act upon, print, disclose, copy, retain
or redistribute it. Click here for important additional terms relating to
this e-mail. http://www.ml.com/email_terms/

Re: TDP/ORACLE Backup

[Neil Rasmussen]

Keep in mind that TDP Oracle just passes on what Oracle/Rman asks it to.
So for DB estimation, TDP Oracle uses the value that Oracle passes to it
(which probably is overestimated). If compression is turned on then this
value is grossly overestimated.


Regards,

Neil Rasmussen
Software Development
Data Protection for Oracle
[EMAIL PROTECTED]




"Wholey, Joseph (IDS DM&DS)" <[EMAIL PROTECTED]>
Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
12/06/2004 08:08 AM
Please respond to
"ADSM: Dist Stor Manager"


To
[EMAIL PROTECTED]
cc

Subject
TDP/ORACLE Backup






When running a TDP for Oracle backup, does TDP lock the estimated amount
of the storage pool which it thinks it needs to complete the backup?


If you are not an intended recipient of this e-mail, please notify the
sender, delete it and do not read, act upon, print, disclose, copy, retain
or redistribute it. Click here for important additional terms relating to
this e-mail. http://www.ml.com/email_terms/

Re: TDP/ORACLE Backup

[David Longo]

Yes.  And in my experience it tends to slightly overestimate what is
needed.  Maybe 5 or 10 % I have seen, depends a lot on the Oracle
DB size and version  I think.

I guess it's better to overestimate than underestimate.


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
[EMAIL PROTECTED]


>>> [EMAIL PROTECTED] 12/06/2004 11:08:24 AM >>>
When running a TDP for Oracle backup, does TDP lock the estimated
amount of the storage pool which it thinks it needs to complete the
backup?


If you are not an intended recipient of this e-mail, please notify the
sender, delete it and do not read, act upon, print, disclose, copy,
retain or redistribute it. Click here for important additional terms
relating to this e-mail. http://www.ml.com/email_terms/


##
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.
##

Re: TDP Oracle Restore

[Pawel Wozniczka]

>Yes please do send me the script and other procedures that you are using.

Hello

I've modified the script so that it could be used not only in my, but also
in other environments. It can be downloaded from:

http://skowron31.neostrada.pl/rman_scripts/change_rman_backup_status.sh
(in case of any download problems, let me know and I'll send it directly to
your email)

***Important facts to consider:***

- Backup your recovery catalog before using this script
- The script works quite good in my environment, but I can NOT guarantee
that it will also work perfectly everywhere.
- My environment:
* ORACLE 8.1.7.4 target databases
* ORACLE 8.1.7.4 recovery catalog database - separate catalog for
each target database
* AIX 5.1 ML04
* TSM 5.1.9
- Be extremely concentrated and focused when using this script, remember
that you are dealing with your company VITAL data!
- Should you have even a slightest doubt about using this script PLEASE ask
me first, I'll try to answer to your questions.

***How does this script work ?***

1. Connects to the target database and recovery catalog (according to the
supplied parameters)
2. Asks recovery catalog for the list of stored backups (according to the
supplied time range)
3. Parses the output from step 2, and generates rman command files (two
files: one for setting unavailable flag, second for setting back to
available state)
4. Generates shell executable scripts which have to be executed manualy to
perform the actual operation of setting unavailable or available flags.

Before actualy executing, check both *.cmd and *.sh files whether they are
correct !!!


If You execute it without parameters a short usage description will be
displayed, similar to the output below:

change_rman_backup_status.sh v 1.0 - beta
2004 Pawel Wozniczka ([EMAIL PROTECTED])


"This script generates RMAN command files which may be used to set
'unavailable' or 'available' flag to selected backup pieces
Only briefly tested with Oracle 8.1.7.4 on AIX 5.1.4 (both target database
and recovery catalog)

Please use extreme caution with this script !!!
Backup recovery catalog before using commands generated by this script!!!

Wrong parameter count !

USAGE: change_rman_backup_status.sh DBUSER DBPASS DBTNS RCATUSER RCATPASS
RCATTNS START_DATE END_DATE

Execute as oracle, not as root or other user

Required parameters:

DBUSER - target database username (sysdba privileges)
DBPASS - target database user password
DBTNS - target database TNSNAME (alias)
RCATUSER - recovery catalog username
RCATPASS - recovery catalog password
RCATTNS - recovery catalog TNSNAME (alias)
START_DATE - start date (RMAN format, for example '10-OCT-04')
END_DATE - start date (RMAN format, for example '15-OCT-04' or
'sysdate-1'...)

WARNING: exact date format may be different because of various environmental
settings !

Example:

change_rman_backup_status.sh sys secret PRDDB rman secret RCATDB '01-OCT-04'
'05-OCT-04'

Will create commands to set either unavailable or available flags to backup
pieces of the database PRDDB registered in recovery catalog database RCATDB
between 01 October 2004 and 04 October 2004"


As I said earlier I'm quite happy with the script.  But remember that it
doesn't take into consideration all possible configurations and may not
always work as expected, so use it at your own risk.

Feel free to ask in case of any doubts.



kind regards

Pawel Wozniczka

Re: TDP Oracle Restore

[Yiannakis Vakis]

I'm interested too.
Yiannakis


-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Behalf Of
Sandra
Sent: Thursday, October 21, 2004 1:53 PM
To: [EMAIL PROTECTED]
Subject: Re: TDP Oracle Restore


Great !!! Pawel.

Yes please do send me the script and other procedures that you are using.
My scenario is to backup database on live machine and restore it on the
backup
machine on daily basis.

1- How do I know the backupset number, as when i used tdposync, it shows the
dbf
files backedup?

2- Please correct me if i m wrong, tdposync command deactivates the
databases
that we select, and these are then marked for deletion?

Kindest regards
Sandra

Pawel Wozniczka wrote:

> >Question is :
> >when i go about restore, how would i know which backup is being
restored..
> the
> >active backup?? what would i need to do to restore any inactive backup??
>
> Hello
>
> As far as I know "rman" always uses the latest available backupsets, and
> there is no official and supported way to restore previous versions of a
> database.
>
> But, as usually, there is a trick that makes is possibile, I use it quite
> frequently in order to test & verify my oracle-tdp backups.
>
> The trick is based on the fact that if the "rman" finds that the latest
> backupsets are marked "unavailable" it will search its database backwards
> until available backupsets are found and those backupsets will be used for
> restore operations.
>
> To summarize:
>
> a) change status of  the rman backupsets that You do NOT want to be used
to
> unavailable (change backupset xxx unavailable)
> b) restore database
> c) change status of the rman backupsets that were modified in step "a"
back
> to available (change backupset xxx available)
>
> To make it easier I created a shell/rman script. (It's strongly hard-coded
> to my environment, but with a little effort can be adjusted to be useful
in
> other environments).
>
> Please let me know whether You are interested, if yes I can send that
script
> and try to assist in customizing it.
>
> kind regards
>
> Pawel W.
> [EMAIL PROTECTED]

Re: TDP Oracle Restore

[Sandra]

Great !!! Pawel.

Yes please do send me the script and other procedures that you are using.
My scenario is to backup database on live machine and restore it on the backup
machine on daily basis.

1- How do I know the backupset number, as when i used tdposync, it shows the dbf
files backedup?

2- Please correct me if i m wrong, tdposync command deactivates the databases
that we select, and these are then marked for deletion?

Kindest regards
Sandra

Pawel Wozniczka wrote:

> >Question is :
> >when i go about restore, how would i know which backup is being restored..
> the
> >active backup?? what would i need to do to restore any inactive backup??
>
> Hello
>
> As far as I know "rman" always uses the latest available backupsets, and
> there is no official and supported way to restore previous versions of a
> database.
>
> But, as usually, there is a trick that makes is possibile, I use it quite
> frequently in order to test & verify my oracle-tdp backups.
>
> The trick is based on the fact that if the "rman" finds that the latest
> backupsets are marked "unavailable" it will search its database backwards
> until available backupsets are found and those backupsets will be used for
> restore operations.
>
> To summarize:
>
> a) change status of  the rman backupsets that You do NOT want to be used to
> unavailable (change backupset xxx unavailable)
> b) restore database
> c) change status of the rman backupsets that were modified in step "a" back
> to available (change backupset xxx available)
>
> To make it easier I created a shell/rman script. (It's strongly hard-coded
> to my environment, but with a little effort can be adjusted to be useful in
> other environments).
>
> Please let me know whether You are interested, if yes I can send that script
> and try to assist in customizing it.
>
> kind regards
>
> Pawel W.
> [EMAIL PROTECTED]

Re: TDP Oracle Restore

[Sandra]

unfortunately no response yet. Luckily, my DBA's went into something and there
are corrupted data blocks in database which failed the database backup. so
tuntil they are fixing i mtrying to find out the restore procedure.

Regards,
sandra

Yiannakis Vakis wrote:

> Sandra,
> did you get an answer to this question ? I saw your posting and I was
> waiting to see if anyone would reply because I have the same question.
> If you found out the procedure can you please let me know ?
> Thanks
> Yiannakis
>
> -Original Message-
> From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Behalf Of
> Sandra
> Sent: Monday, October 18, 2004 5:01 PM
> To: [EMAIL PROTECTED]
> Subject: TDP Oracle Restore
>
> Dear All,
> Sorry to bother you all again.
> I am going to restore backup of oracle database tomorrow.
>
> The only thing I know about restore is that sample script:
>
> run
> {
> allocate channel t1 type ’sbt_tape’ parms
> ’ENV=(TDPO_OPTFILE=/home/oracle/tdpo.opt)’;
> restore database;
> recover database;
> alter database open;
> }
>
> which is called from the command line while involking MAN.
>
> Question is :
>
> when i go about restore, how would i know which backup is being restored...
> the
> active backup?? what would i need to do to restore any inactive backup??
>
> Cheers
> Sandra

Re: TDP Oracle Restore

[Pawel Wozniczka]

>Question is :
>when i go about restore, how would i know which backup is being restored..
the
>active backup?? what would i need to do to restore any inactive backup??

Hello

As far as I know "rman" always uses the latest available backupsets, and
there is no official and supported way to restore previous versions of a
database.

But, as usually, there is a trick that makes is possibile, I use it quite
frequently in order to test & verify my oracle-tdp backups.

The trick is based on the fact that if the "rman" finds that the latest
backupsets are marked "unavailable" it will search its database backwards
until available backupsets are found and those backupsets will be used for
restore operations.

To summarize:

a) change status of  the rman backupsets that You do NOT want to be used to
unavailable (change backupset xxx unavailable)
b) restore database
c) change status of the rman backupsets that were modified in step "a" back
to available (change backupset xxx available)

To make it easier I created a shell/rman script. (It's strongly hard-coded
to my environment, but with a little effort can be adjusted to be useful in
other environments).

Please let me know whether You are interested, if yes I can send that script
and try to assist in customizing it.

kind regards

Pawel W.
[EMAIL PROTECTED]

Re: TDP Oracle Restore

[Yiannakis Vakis]

Sandra,
did you get an answer to this question ? I saw your posting and I was
waiting to see if anyone would reply because I have the same question.
If you found out the procedure can you please let me know ?
Thanks
Yiannakis


-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Behalf Of
Sandra
Sent: Monday, October 18, 2004 5:01 PM
To: [EMAIL PROTECTED]
Subject: TDP Oracle Restore


Dear All,
Sorry to bother you all again.
I am going to restore backup of oracle database tomorrow.

The only thing I know about restore is that sample script:


run
{
allocate channel t1 type ’sbt_tape’ parms
’ENV=(TDPO_OPTFILE=/home/oracle/tdpo.opt)’;
restore database;
recover database;
alter database open;
}

which is called from the command line while involking MAN.

Question is :

when i go about restore, how would i know which backup is being restored...
the
active backup?? what would i need to do to restore any inactive backup??


Cheers
Sandra

Re: TDP Oracle -- Time of backup and multiple cartridges for one backup

[Sandra]

Please discuss my dear list.
I am newbie to this world and need your support to become the one like you guys.

Sandra

Sandra wrote:

> Dear All,
> As I initiated the backup I saw two weird things:
>
> 1- TSM used 2 cartridges from tape library for backing up single database of
> around 140 GB? Why? I have a single cartridge of 200GB.
>
> 2- From log file created or the tivoli server activity log, I can not tell how
> much time backup took?
>
> Please discuss!
>
> Sandra

Re: TDP Oracle Question

[Prasad, Mahesh (IDS ECCS)]

Bruce,

H..! your default management class is also pointing to the diskpool and I believe 
that the oracle node is registered in C1_ORA_AGENT policy domain. You may want to 
collect "q backup" information
from your oracle node and also collect "tdpoconf showenv" information to confirm that 
the backups are bound to correct management class and tdp environment is set up 
correctly. If that still does not
give any clue, then you have to run a test backup using RMAN/TDP. Check diskpool 
utilization details while backup is running and go through the TSM server activity log 
during the test backup. I hope
you will get a clue there.

Wish you all the best!

Regards,

Mahesh Prasad

-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Behalf Of
Kamp, Bruce
Sent: Thursday, May 27, 2004 10:51 AM
To: [EMAIL PROTECTED]
Subject: Re: TDP Oracle Question


Here you go.

Policy Domain Name C1_ORA_AGENT
Policy Set Name ACTIVE
Mgmt Class Name STANDARD
Copy Group Name STANDARD
Versions Data Exists 1
Versions Data Deleted 0
Retain Extra Versions 1
Retain Only Version 0
Copy Mode MODIFIED
Copy Serialization SHRSTATIC
Copy Frequency 0
Copy Destination C1_ORA_DISK_POOL


DSMI_ORC_CONFIG /usr/tivoli/tsm/client/api/bin/dsm.opt
DSMI_LOG/tmp
TDPO_NODE   xyz_oracle_prod816
TDPO_OWNER  oracle
TDPO_PSWDPATH   /usr/tivoli/tsm/client/oracle/bin
TDPO_NUM_BUFFERS10
TDPO_FS xyz_oracle_prod816
* TDPO_TRACE_FLAGSorclevel0 orclevel1 orclevel2
* TDPO_TRACE_FILE
/usr/tivoli/tsm/client/oracle/bin64/tdpo_trace.out
* TDPO_OWNER  
* TDPO_AVG_SIZE***Not needed for Oracle 8.1.x
* TDPO_MGMT_CLASS_2   
* TDPO_MGMT_CLASS_3   
* TDPO_MGMT_CLASS_4   


Thanks,
-
Bruce Kamp
Senior Midrange Systems Analyst
Memorial Healthcare System
E-Mail: [EMAIL PROTECTED]
Phone: (954) 987-2020 x4597
Pager: (954) 286-9441
Alphapage: [EMAIL PROTECTED]
Fax: (954) 985-1404
-

-Original Message-
From: Prasad, Mahesh (IDS ECCS) [mailto:[EMAIL PROTECTED]
Sent: Thursday, May 27, 2004 9:04 AM
To: [EMAIL PROTECTED]
Subject: Re: TDP Oracle Question

Bruce,

The management class you have shown over here is not the default management
class. Can you please send the backup copy group details of the default
management class and details of the tdpo.opt file?

Regards,

Mahesh Prasad

-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Behalf Of
Kamp, Bruce
Sent: Thursday, May 27, 2004 8:56 AM
To: [EMAIL PROTECTED]
Subject: Re: TDP Oracle Question


I'm still at a loss
Here is my setup:

Mgmt Class:
Policy Domain Name C1_ORA_AGENT
Policy Set Name ACTIVE
Mgmt Class Name C1_ORACLE_MGMT_CLASS
Default Mgmt Class ? No
Description C1 Oracle Agent MGMT Class
Space Management Technique NONE
Auto-Migrate on Non-Use 0
Migration Requires Backup? NO
Migration Destination C1_ORA_DISK_POOL

Backup Copy Group:
Policy Domain Name C1_ORA_AGENT
Policy Set Name ACTIVE
Mgmt Class Name C1_ORACLE_MGMT_CLASS
Copy Group Name STANDARD
Versions Data Exists 1
Versions Data Deleted 0
Retain Extra Versions 1
Retain Only Version 0
Copy Mode MODIFIED
Copy Serialization SHRSTATIC
Copy Frequency 0
Copy Destination C1_ORA_DISK_POOL

Disk Storage Pool:
Storage Pool Name C1_ORA_DISK_POOL
Storage Pool Type PRIMARY
Device Class Name DISK
Estimated Capacity (MB) 200272.0
Pct Util 15.8
Pct Migr 15.8
Pct Logical 100.0
High Mig Pct 90
Low Mig Pct 70
Migration Processes 4
Next Storage Pool C1_ORA_TAPE_POOL
Maximum Size Threshold -
Access READWRITE
Description C1 Oracle Disk Pool

When I look at the disk storage pool it is only 10-15% percent utilized.
Also the only migration I see is the one I do during my normal daily
processing.
Any more ideas?



Thanks,
-
Bruce Kamp
Senior Midrange Systems Analyst
Memorial Healthcare System
E-Mail: [EMAIL PROTECTED]
Phone: (954) 987-2020 x4597
Pager: (954) 286-9441
Alphapage: [EMAIL PROTECTED]
Fax: (954) 985-1404
-

-Original Message-
From: Greg Kemp [mailto:[EMAIL PROTECTED]
Sent: Wednesday, May 26, 2004 12:08 AM
To: [EMAIL PROTECTED]
Subject: Re: TDP Oracle Question

TSM does not lock the total required space for a backup in a storage
pool before the actual backup starts or while in progress. TSM fills
the defined devices for a management class in order of definition until
the storage pool is full or the backup completes. Fill your disks and
TSM moves on to the tape pool or some other defined device.

Bruce

If the MAXSIZE threshold on your disk pool is set to 200GB (which is
excessive) and you have 133GB available there is no reason the backup
isn't ending up on disk. Double check your management class for both
the backup and archive copy pools. T

Re: TDP Oracle Question

[Kamp, Bruce]

Here you go.

Policy Domain Name C1_ORA_AGENT
Policy Set Name ACTIVE
Mgmt Class Name STANDARD
Copy Group Name STANDARD
Versions Data Exists 1
Versions Data Deleted 0
Retain Extra Versions 1
Retain Only Version 0
Copy Mode MODIFIED
Copy Serialization SHRSTATIC
Copy Frequency 0
Copy Destination C1_ORA_DISK_POOL


DSMI_ORC_CONFIG /usr/tivoli/tsm/client/api/bin/dsm.opt
DSMI_LOG/tmp
TDPO_NODE   xyz_oracle_prod816
TDPO_OWNER  oracle
TDPO_PSWDPATH   /usr/tivoli/tsm/client/oracle/bin
TDPO_NUM_BUFFERS10
TDPO_FS xyz_oracle_prod816
* TDPO_TRACE_FLAGSorclevel0 orclevel1 orclevel2
* TDPO_TRACE_FILE
/usr/tivoli/tsm/client/oracle/bin64/tdpo_trace.out
* TDPO_OWNER  
* TDPO_AVG_SIZE***Not needed for Oracle 8.1.x
* TDPO_MGMT_CLASS_2   
* TDPO_MGMT_CLASS_3   
* TDPO_MGMT_CLASS_4   


Thanks,
-
Bruce Kamp
Senior Midrange Systems Analyst
Memorial Healthcare System
E-Mail: [EMAIL PROTECTED]
Phone: (954) 987-2020 x4597
Pager: (954) 286-9441
Alphapage: [EMAIL PROTECTED]
Fax: (954) 985-1404
-

-Original Message-
From: Prasad, Mahesh (IDS ECCS) [mailto:[EMAIL PROTECTED]
Sent: Thursday, May 27, 2004 9:04 AM
To: [EMAIL PROTECTED]
Subject: Re: TDP Oracle Question

Bruce,

The management class you have shown over here is not the default management
class. Can you please send the backup copy group details of the default
management class and details of the tdpo.opt file?

Regards,

Mahesh Prasad

-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Behalf Of
Kamp, Bruce
Sent: Thursday, May 27, 2004 8:56 AM
To: [EMAIL PROTECTED]
Subject: Re: TDP Oracle Question


I'm still at a loss
Here is my setup:

Mgmt Class:
Policy Domain Name C1_ORA_AGENT
Policy Set Name ACTIVE
Mgmt Class Name C1_ORACLE_MGMT_CLASS
Default Mgmt Class ? No
Description C1 Oracle Agent MGMT Class
Space Management Technique NONE
Auto-Migrate on Non-Use 0
Migration Requires Backup? NO
Migration Destination C1_ORA_DISK_POOL

Backup Copy Group:
Policy Domain Name C1_ORA_AGENT
Policy Set Name ACTIVE
Mgmt Class Name C1_ORACLE_MGMT_CLASS
Copy Group Name STANDARD
Versions Data Exists 1
Versions Data Deleted 0
Retain Extra Versions 1
Retain Only Version 0
Copy Mode MODIFIED
Copy Serialization SHRSTATIC
Copy Frequency 0
Copy Destination C1_ORA_DISK_POOL

Disk Storage Pool:
Storage Pool Name C1_ORA_DISK_POOL
Storage Pool Type PRIMARY
Device Class Name DISK
Estimated Capacity (MB) 200272.0
Pct Util 15.8
Pct Migr 15.8
Pct Logical 100.0
High Mig Pct 90
Low Mig Pct 70
Migration Processes 4
Next Storage Pool C1_ORA_TAPE_POOL
Maximum Size Threshold -
Access READWRITE
Description C1 Oracle Disk Pool

When I look at the disk storage pool it is only 10-15% percent utilized.
Also the only migration I see is the one I do during my normal daily
processing.
Any more ideas?



Thanks,
-
Bruce Kamp
Senior Midrange Systems Analyst
Memorial Healthcare System
E-Mail: [EMAIL PROTECTED]
Phone: (954) 987-2020 x4597
Pager: (954) 286-9441
Alphapage: [EMAIL PROTECTED]
Fax: (954) 985-1404
-

-Original Message-
From: Greg Kemp [mailto:[EMAIL PROTECTED]
Sent: Wednesday, May 26, 2004 12:08 AM
To: [EMAIL PROTECTED]
Subject: Re: TDP Oracle Question

TSM does not lock the total required space for a backup in a storage
pool before the actual backup starts or while in progress. TSM fills
the defined devices for a management class in order of definition until
the storage pool is full or the backup completes. Fill your disks and
TSM moves on to the tape pool or some other defined device.

Bruce

If the MAXSIZE threshold on your disk pool is set to 200GB (which is
excessive) and you have 133GB available there is no reason the backup
isn't ending up on disk. Double check your management class for both
the backup and archive copy pools. TDP for Oracle uses the 'BACKUP'
copy group which in your case should point to the disk pool. TDP does
not use the 'ARCHIVE' copy group. I have been bitten by this one in the
past.

Regards,

Greg


On May 24, 2004, at 8:53 AM, Wholey, Joseph (IDS DM&DS) wrote:

> Bruce,
>
> You should make sure that the percentage utilized in your storage pool
> is 0% prior to running your backup.  Also, are any other backups
> running.  Keep in mind that once TSM sees that it's going to need
> 133Gig of disk to backup the Oracle db, it will attempt to lock that
> amount of the stg pool.  If the full amount is not available, it will
> go to the "next" stg pool.
>
> Regards, Joe
>
> -Original Message-
> From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Behalf Of
> Kamp, Bruce
> Sent: Monday, May 24, 2004

Re: TDP Oracle Question

[Prasad, Mahesh (IDS ECCS)]

Bruce,

The management class you have shown over here is not the default management class. Can 
you please send the backup copy group details of the default management class and 
details of the tdpo.opt file?

Regards,

Mahesh Prasad

-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Behalf Of
Kamp, Bruce
Sent: Thursday, May 27, 2004 8:56 AM
To: [EMAIL PROTECTED]
Subject: Re: TDP Oracle Question


I'm still at a loss
Here is my setup:

Mgmt Class:
Policy Domain Name C1_ORA_AGENT
Policy Set Name ACTIVE
Mgmt Class Name C1_ORACLE_MGMT_CLASS
Default Mgmt Class ? No
Description C1 Oracle Agent MGMT Class
Space Management Technique NONE
Auto-Migrate on Non-Use 0
Migration Requires Backup? NO
Migration Destination C1_ORA_DISK_POOL

Backup Copy Group:
Policy Domain Name C1_ORA_AGENT
Policy Set Name ACTIVE
Mgmt Class Name C1_ORACLE_MGMT_CLASS
Copy Group Name STANDARD
Versions Data Exists 1
Versions Data Deleted 0
Retain Extra Versions 1
Retain Only Version 0
Copy Mode MODIFIED
Copy Serialization SHRSTATIC
Copy Frequency 0
Copy Destination C1_ORA_DISK_POOL

Disk Storage Pool:
Storage Pool Name C1_ORA_DISK_POOL
Storage Pool Type PRIMARY
Device Class Name DISK
Estimated Capacity (MB) 200272.0
Pct Util 15.8
Pct Migr 15.8
Pct Logical 100.0
High Mig Pct 90
Low Mig Pct 70
Migration Processes 4
Next Storage Pool C1_ORA_TAPE_POOL
Maximum Size Threshold -
Access READWRITE
Description C1 Oracle Disk Pool

When I look at the disk storage pool it is only 10-15% percent utilized.
Also the only migration I see is the one I do during my normal daily
processing.
Any more ideas?



Thanks,
-
Bruce Kamp
Senior Midrange Systems Analyst
Memorial Healthcare System
E-Mail: [EMAIL PROTECTED]
Phone: (954) 987-2020 x4597
Pager: (954) 286-9441
Alphapage: [EMAIL PROTECTED]
Fax: (954) 985-1404
-

-Original Message-
From: Greg Kemp [mailto:[EMAIL PROTECTED]
Sent: Wednesday, May 26, 2004 12:08 AM
To: [EMAIL PROTECTED]
Subject: Re: TDP Oracle Question

TSM does not lock the total required space for a backup in a storage
pool before the actual backup starts or while in progress. TSM fills
the defined devices for a management class in order of definition until
the storage pool is full or the backup completes. Fill your disks and
TSM moves on to the tape pool or some other defined device.

Bruce

If the MAXSIZE threshold on your disk pool is set to 200GB (which is
excessive) and you have 133GB available there is no reason the backup
isn't ending up on disk. Double check your management class for both
the backup and archive copy pools. TDP for Oracle uses the 'BACKUP'
copy group which in your case should point to the disk pool. TDP does
not use the 'ARCHIVE' copy group. I have been bitten by this one in the
past.

Regards,

Greg


On May 24, 2004, at 8:53 AM, Wholey, Joseph (IDS DM&DS) wrote:

> Bruce,
>
> You should make sure that the percentage utilized in your storage pool
> is 0% prior to running your backup.  Also, are any other backups
> running.  Keep in mind that once TSM sees that it's going to need
> 133Gig of disk to backup the Oracle db, it will attempt to lock that
> amount of the stg pool.  If the full amount is not available, it will
> go to the "next" stg pool.
>
> Regards, Joe
>
> -Original Message-
> From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Behalf Of
> Kamp, Bruce
> Sent: Monday, May 24, 2004 11:34 AM
> To: [EMAIL PROTECTED]
> Subject: Re: TDP Oracle Question
>
>
> That is set to 200G.
>
>
> -
> Bruce Kamp
> Senior Midrange Systems Analyst
> Memorial Healthcare System
> E-Mail: [EMAIL PROTECTED]
> Phone: (954) 987-2020 x4597
> Pager: (954) 286-9441
> Alphapage: [EMAIL PROTECTED]
> Fax: (954) 985-1404
> -
>
> -----Original Message-
> From: Hooft, Jeroen [mailto:[EMAIL PROTECTED]
> Sent: Monday, May 24, 2004 8:30 AM
> To: [EMAIL PROTECTED]
> Subject: Re: TDP Oracle Question
>
> Maybe setting on disk storagepool: "Maximum Size Threshold"?
>
> Jeroen
>
>
> -Original Message-
> From: Kamp, Bruce [mailto:[EMAIL PROTECTED]
> Sent: maandag 24 mei 2004 14:00
> To: [EMAIL PROTECTED]
> Subject: TDP Oracle Question
>
>
> I'm trying to give enough disk to my Oracle backups but have not been
> successful.  My management classes point to disk.  How do I find out
> how
> much disk TSM is looking for to backup straight to disk?  I looked on
> the
> system & saw that the dbf files added up to about 133G I have given it
> 200G.
> Or is there something else that could be pointing to tape instead of
> disk?
>

Re: TDP Oracle Question

[Baughman, Ray A.]

Here's what was causing me some problems

Look at the value of TDPO_AVG_SIZE on the client if it is larger than the size of your 
Disk volumes then TSM will not write to the disk, regardless of the size of the 
storage pool.

Ray Baughman
TSM & Engineering Systems Administrator
National Machinery LLC
Phone 419-443-2257
Fax 419-443-2376
Email [EMAIL PROTECTED]

-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Behalf Of
Kamp, Bruce
Sent: Thursday, May 27, 2004 8:56 AM
To: [EMAIL PROTECTED]
Subject: Re: TDP Oracle Question


I'm still at a loss
Here is my setup:

Mgmt Class:
Policy Domain Name C1_ORA_AGENT
Policy Set Name ACTIVE
Mgmt Class Name C1_ORACLE_MGMT_CLASS
Default Mgmt Class ? No
Description C1 Oracle Agent MGMT Class
Space Management Technique NONE
Auto-Migrate on Non-Use 0
Migration Requires Backup? NO
Migration Destination C1_ORA_DISK_POOL

Backup Copy Group:
Policy Domain Name C1_ORA_AGENT
Policy Set Name ACTIVE
Mgmt Class Name C1_ORACLE_MGMT_CLASS
Copy Group Name STANDARD
Versions Data Exists 1
Versions Data Deleted 0
Retain Extra Versions 1
Retain Only Version 0
Copy Mode MODIFIED
Copy Serialization SHRSTATIC
Copy Frequency 0
Copy Destination C1_ORA_DISK_POOL

Disk Storage Pool:
Storage Pool Name C1_ORA_DISK_POOL
Storage Pool Type PRIMARY
Device Class Name DISK
Estimated Capacity (MB) 200272.0
Pct Util 15.8
Pct Migr 15.8
Pct Logical 100.0
High Mig Pct 90
Low Mig Pct 70
Migration Processes 4
Next Storage Pool C1_ORA_TAPE_POOL
Maximum Size Threshold -
Access READWRITE
Description C1 Oracle Disk Pool

When I look at the disk storage pool it is only 10-15% percent utilized.
Also the only migration I see is the one I do during my normal daily
processing.
Any more ideas?



Thanks,
-
Bruce Kamp
Senior Midrange Systems Analyst
Memorial Healthcare System
E-Mail: [EMAIL PROTECTED]
Phone: (954) 987-2020 x4597
Pager: (954) 286-9441
Alphapage: [EMAIL PROTECTED]
Fax: (954) 985-1404
-

-Original Message-
From: Greg Kemp [mailto:[EMAIL PROTECTED]
Sent: Wednesday, May 26, 2004 12:08 AM
To: [EMAIL PROTECTED]
Subject: Re: TDP Oracle Question

TSM does not lock the total required space for a backup in a storage
pool before the actual backup starts or while in progress. TSM fills
the defined devices for a management class in order of definition until
the storage pool is full or the backup completes. Fill your disks and
TSM moves on to the tape pool or some other defined device.

Bruce

If the MAXSIZE threshold on your disk pool is set to 200GB (which is
excessive) and you have 133GB available there is no reason the backup
isn't ending up on disk. Double check your management class for both
the backup and archive copy pools. TDP for Oracle uses the 'BACKUP'
copy group which in your case should point to the disk pool. TDP does
not use the 'ARCHIVE' copy group. I have been bitten by this one in the
past.

Regards,

Greg


On May 24, 2004, at 8:53 AM, Wholey, Joseph (IDS DM&DS) wrote:

> Bruce,
>
> You should make sure that the percentage utilized in your storage pool
> is 0% prior to running your backup.  Also, are any other backups
> running.  Keep in mind that once TSM sees that it's going to need
> 133Gig of disk to backup the Oracle db, it will attempt to lock that
> amount of the stg pool.  If the full amount is not available, it will
> go to the "next" stg pool.
>
> Regards, Joe
>
> -Original Message-
> From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Behalf Of
> Kamp, Bruce
> Sent: Monday, May 24, 2004 11:34 AM
> To: [EMAIL PROTECTED]
> Subject: Re: TDP Oracle Question
>
>
> That is set to 200G.
>
>
> -
> Bruce Kamp
> Senior Midrange Systems Analyst
> Memorial Healthcare System
> E-Mail: [EMAIL PROTECTED]
> Phone: (954) 987-2020 x4597
> Pager: (954) 286-9441
> Alphapage: [EMAIL PROTECTED]
> Fax: (954) 985-1404
> -----
>
> -Original Message-
> From: Hooft, Jeroen [mailto:[EMAIL PROTECTED]
> Sent: Monday, May 24, 2004 8:30 AM
> To: [EMAIL PROTECTED]
> Subject: Re: TDP Oracle Question
>
> Maybe setting on disk storagepool: "Maximum Size Threshold"?
>
> Jeroen
>
>
> -Original Message-
> From: Kamp, Bruce [mailto:[EMAIL PROTECTED]
> Sent: maandag 24 mei 2004 14:00
> To: [EMAIL PROTECTED]
> Subject: TDP Oracle Question
>
>
> I'm trying to give enough disk to my Oracle backups but have not been
> successful.  My management classes point to disk.  How do I find out
> how
> much disk TSM is looking for to backup straight to disk?  I looked on
> the
> system & saw that the dbf files 

Re: TDP Oracle Question

[Kamp, Bruce]

I'm still at a loss
Here is my setup:

Mgmt Class:
Policy Domain Name C1_ORA_AGENT
Policy Set Name ACTIVE
Mgmt Class Name C1_ORACLE_MGMT_CLASS
Default Mgmt Class ? No
Description C1 Oracle Agent MGMT Class
Space Management Technique NONE
Auto-Migrate on Non-Use 0
Migration Requires Backup? NO
Migration Destination C1_ORA_DISK_POOL

Backup Copy Group:
Policy Domain Name C1_ORA_AGENT
Policy Set Name ACTIVE
Mgmt Class Name C1_ORACLE_MGMT_CLASS
Copy Group Name STANDARD
Versions Data Exists 1
Versions Data Deleted 0
Retain Extra Versions 1
Retain Only Version 0
Copy Mode MODIFIED
Copy Serialization SHRSTATIC
Copy Frequency 0
Copy Destination C1_ORA_DISK_POOL

Disk Storage Pool:
Storage Pool Name C1_ORA_DISK_POOL
Storage Pool Type PRIMARY
Device Class Name DISK
Estimated Capacity (MB) 200272.0
Pct Util 15.8
Pct Migr 15.8
Pct Logical 100.0
High Mig Pct 90
Low Mig Pct 70
Migration Processes 4
Next Storage Pool C1_ORA_TAPE_POOL
Maximum Size Threshold -
Access READWRITE
Description C1 Oracle Disk Pool

When I look at the disk storage pool it is only 10-15% percent utilized.
Also the only migration I see is the one I do during my normal daily
processing.
Any more ideas?



Thanks,
-
Bruce Kamp
Senior Midrange Systems Analyst
Memorial Healthcare System
E-Mail: [EMAIL PROTECTED]
Phone: (954) 987-2020 x4597
Pager: (954) 286-9441
Alphapage: [EMAIL PROTECTED]
Fax: (954) 985-1404
-

-Original Message-
From: Greg Kemp [mailto:[EMAIL PROTECTED]
Sent: Wednesday, May 26, 2004 12:08 AM
To: [EMAIL PROTECTED]
Subject: Re: TDP Oracle Question

TSM does not lock the total required space for a backup in a storage
pool before the actual backup starts or while in progress. TSM fills
the defined devices for a management class in order of definition until
the storage pool is full or the backup completes. Fill your disks and
TSM moves on to the tape pool or some other defined device.

Bruce

If the MAXSIZE threshold on your disk pool is set to 200GB (which is
excessive) and you have 133GB available there is no reason the backup
isn't ending up on disk. Double check your management class for both
the backup and archive copy pools. TDP for Oracle uses the 'BACKUP'
copy group which in your case should point to the disk pool. TDP does
not use the 'ARCHIVE' copy group. I have been bitten by this one in the
past.

Regards,

Greg


On May 24, 2004, at 8:53 AM, Wholey, Joseph (IDS DM&DS) wrote:

> Bruce,
>
> You should make sure that the percentage utilized in your storage pool
> is 0% prior to running your backup.  Also, are any other backups
> running.  Keep in mind that once TSM sees that it's going to need
> 133Gig of disk to backup the Oracle db, it will attempt to lock that
> amount of the stg pool.  If the full amount is not available, it will
> go to the "next" stg pool.
>
> Regards, Joe
>
> -Original Message-
> From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Behalf Of
> Kamp, Bruce
> Sent: Monday, May 24, 2004 11:34 AM
> To: [EMAIL PROTECTED]
> Subject: Re: TDP Oracle Question
>
>
> That is set to 200G.
>
>
> -
> Bruce Kamp
> Senior Midrange Systems Analyst
> Memorial Healthcare System
> E-Mail: [EMAIL PROTECTED]
> Phone: (954) 987-2020 x4597
> Pager: (954) 286-9441
> Alphapage: [EMAIL PROTECTED]
> Fax: (954) 985-1404
> -
>
> -----Original Message-
> From: Hooft, Jeroen [mailto:[EMAIL PROTECTED]
> Sent: Monday, May 24, 2004 8:30 AM
> To: [EMAIL PROTECTED]
> Subject: Re: TDP Oracle Question
>
> Maybe setting on disk storagepool: "Maximum Size Threshold"?
>
> Jeroen
>
>
> -Original Message-
> From: Kamp, Bruce [mailto:[EMAIL PROTECTED]
> Sent: maandag 24 mei 2004 14:00
> To: [EMAIL PROTECTED]
> Subject: TDP Oracle Question
>
>
> I'm trying to give enough disk to my Oracle backups but have not been
> successful.  My management classes point to disk.  How do I find out
> how
> much disk TSM is looking for to backup straight to disk?  I looked on
> the
> system & saw that the dbf files added up to about 133G I have given it
> 200G.
> Or is there something else that could be pointing to tape instead of
> disk?
> I'm running TSM 5.2.1.2 on AIX 5.1.  The client is running TSM
> 5.1.5.11 &
> TDP Oracle ver 2.2.0.1 with Oracle 8.1.7.4.
>
>
> Thanks,
> -
> Bruce Kamp
> Senior Midrange Systems Analyst
> Memorial Healthcare System
> E-Mail: [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>
> Phone: (954) 987-2020 x4597
> Pager: (954) 286-9441
> Alph

Re: TDP Oracle Question

[Greg Kemp]

TSM does not lock the total required space for a backup in a storage
pool before the actual backup starts or while in progress. TSM fills
the defined devices for a management class in order of definition until
the storage pool is full or the backup completes. Fill your disks and
TSM moves on to the tape pool or some other defined device.
Bruce
If the MAXSIZE threshold on your disk pool is set to 200GB (which is
excessive) and you have 133GB available there is no reason the backup
isn't ending up on disk. Double check your management class for both
the backup and archive copy pools. TDP for Oracle uses the 'BACKUP'
copy group which in your case should point to the disk pool. TDP does
not use the 'ARCHIVE' copy group. I have been bitten by this one in the
past.
Regards,
Greg
On May 24, 2004, at 8:53 AM, Wholey, Joseph (IDS DM&DS) wrote:
Bruce,
You should make sure that the percentage utilized in your storage pool
is 0% prior to running your backup.  Also, are any other backups
running.  Keep in mind that once TSM sees that it's going to need
133Gig of disk to backup the Oracle db, it will attempt to lock that
amount of the stg pool.  If the full amount is not available, it will
go to the "next" stg pool.
Regards, Joe
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Behalf Of
Kamp, Bruce
Sent: Monday, May 24, 2004 11:34 AM
To: [EMAIL PROTECTED]
Subject: Re: TDP Oracle Question
That is set to 200G.
-
Bruce Kamp
Senior Midrange Systems Analyst
Memorial Healthcare System
E-Mail: [EMAIL PROTECTED]
Phone: (954) 987-2020 x4597
Pager: (954) 286-9441
Alphapage: [EMAIL PROTECTED]
Fax: (954) 985-1404
-
-Original Message-
From: Hooft, Jeroen [mailto:[EMAIL PROTECTED]
Sent: Monday, May 24, 2004 8:30 AM
To: [EMAIL PROTECTED]
Subject: Re: TDP Oracle Question
Maybe setting on disk storagepool: "Maximum Size Threshold"?
Jeroen
-Original Message-
From: Kamp, Bruce [mailto:[EMAIL PROTECTED]
Sent: maandag 24 mei 2004 14:00
To: [EMAIL PROTECTED]
Subject: TDP Oracle Question
I'm trying to give enough disk to my Oracle backups but have not been
successful.  My management classes point to disk.  How do I find out
how
much disk TSM is looking for to backup straight to disk?  I looked on
the
system & saw that the dbf files added up to about 133G I have given it
200G.
Or is there something else that could be pointing to tape instead of
disk?
I'm running TSM 5.2.1.2 on AIX 5.1.  The client is running TSM
5.1.5.11 &
TDP Oracle ver 2.2.0.1 with Oracle 8.1.7.4.
Thanks,
-
Bruce Kamp
Senior Midrange Systems Analyst
Memorial Healthcare System
E-Mail: [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>
Phone: (954) 987-2020 x4597
Pager: (954) 286-9441
Alphapage: [EMAIL PROTECTED]
Fax: (954) 985-1404
-

If you are not an intended recipient of this e-mail, please notify the
sender, delete it and do not read, act upon, print, disclose, copy,
retain or redistribute it. Click here for important additional terms
relating to this e-mail. http://www.ml.com/email_terms/

Re: TDP Oracle Question

[Greg Kemp]

If the DB is 133GB and the disk pool has 200GB available you are good
regardless. This is given your management class points to the disk
storage pool first. Otherwise you have one or both of the following
issues. (1) The disk pool is 100% utilized at the time of the backup,
and the NEXT pool is set to a tape pool. -OR- (2) The files are larger
than the MAXSIZE threshold set on the disk pool. Do you have a
threshold set on the disk pool? Are the individual DB files larger than
the threshold? TSM doesn't forecast how much disk or tape space the
given backup will require before starting. The backup simply starts and
fills the destination devices that are configured for the management
class in use. If the first device in line is disk the backup will be
sent to disk until either the disk pool fills or the backup completes.
If the disk pool fills to 100% TSM will move onto the next defined
(could be disk or tape or other) storage pool.
Regards,
Greg
On May 24, 2004, at 4:59 AM, Kamp, Bruce wrote:
I'm trying to give enough disk to my Oracle backups but have not been
successful.  My management classes point to disk.  How do I find out
how
much disk TSM is looking for to backup straight to disk?  I looked on
the
system & saw that the dbf files added up to about 133G I have given it
200G.
Or is there something else that could be pointing to tape instead of
disk?
I'm running TSM 5.2.1.2 on AIX 5.1.  The client is running TSM
5.1.5.11 &
TDP Oracle ver 2.2.0.1 with Oracle 8.1.7.4.
Thanks,
-
Bruce Kamp
Senior Midrange Systems Analyst
Memorial Healthcare System
E-Mail: [EMAIL PROTECTED] 
Phone: (954) 987-2020 x4597
Pager: (954) 286-9441
Alphapage: [EMAIL PROTECTED]
Fax: (954) 985-1404
-

Re: TDP Oracle Question

Bruce, 

You should make sure that the percentage utilized in your storage pool is 0% prior to 
running your backup.  Also, are any other backups running.  Keep in mind that once TSM 
sees that it's going to need 133Gig of disk to backup the Oracle db, it will attempt 
to lock that amount of the stg pool.  If the full amount is not available, it will go 
to the "next" stg pool.

Regards, Joe

-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Behalf Of
Kamp, Bruce
Sent: Monday, May 24, 2004 11:34 AM
To: [EMAIL PROTECTED]
Subject: Re: TDP Oracle Question


That is set to 200G.


-
Bruce Kamp
Senior Midrange Systems Analyst
Memorial Healthcare System
E-Mail: [EMAIL PROTECTED]
Phone: (954) 987-2020 x4597
Pager: (954) 286-9441
Alphapage: [EMAIL PROTECTED]
Fax: (954) 985-1404
-

-Original Message-
From: Hooft, Jeroen [mailto:[EMAIL PROTECTED]
Sent: Monday, May 24, 2004 8:30 AM
To: [EMAIL PROTECTED]
Subject: Re: TDP Oracle Question

Maybe setting on disk storagepool: "Maximum Size Threshold"?

Jeroen


-Original Message-
From: Kamp, Bruce [mailto:[EMAIL PROTECTED]
Sent: maandag 24 mei 2004 14:00
To: [EMAIL PROTECTED]
Subject: TDP Oracle Question


I'm trying to give enough disk to my Oracle backups but have not been
successful.  My management classes point to disk.  How do I find out how
much disk TSM is looking for to backup straight to disk?  I looked on the
system & saw that the dbf files added up to about 133G I have given it 200G.
Or is there something else that could be pointing to tape instead of disk?
I'm running TSM 5.2.1.2 on AIX 5.1.  The client is running TSM 5.1.5.11 &
TDP Oracle ver 2.2.0.1 with Oracle 8.1.7.4.


Thanks,
-
Bruce Kamp
Senior Midrange Systems Analyst
Memorial Healthcare System
E-Mail: [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>
Phone: (954) 987-2020 x4597
Pager: (954) 286-9441
Alphapage: [EMAIL PROTECTED]
Fax: (954) 985-1404
- 

 
If you are not an intended recipient of this e-mail, please notify the sender, delete 
it and do not read, act upon, print, disclose, copy, retain or redistribute it. Click 
here for important additional terms relating to this e-mail. 
http://www.ml.com/email_terms/ 

 

Re: TDP Oracle Question

[Kamp, Bruce]

That is set to 200G.


-
Bruce Kamp
Senior Midrange Systems Analyst
Memorial Healthcare System
E-Mail: [EMAIL PROTECTED]
Phone: (954) 987-2020 x4597
Pager: (954) 286-9441
Alphapage: [EMAIL PROTECTED]
Fax: (954) 985-1404
-

-Original Message-
From: Hooft, Jeroen [mailto:[EMAIL PROTECTED]
Sent: Monday, May 24, 2004 8:30 AM
To: [EMAIL PROTECTED]
Subject: Re: TDP Oracle Question

Maybe setting on disk storagepool: "Maximum Size Threshold"?

Jeroen


-Original Message-
From: Kamp, Bruce [mailto:[EMAIL PROTECTED]
Sent: maandag 24 mei 2004 14:00
To: [EMAIL PROTECTED]
Subject: TDP Oracle Question


I'm trying to give enough disk to my Oracle backups but have not been
successful.  My management classes point to disk.  How do I find out how
much disk TSM is looking for to backup straight to disk?  I looked on the
system & saw that the dbf files added up to about 133G I have given it 200G.
Or is there something else that could be pointing to tape instead of disk?
I'm running TSM 5.2.1.2 on AIX 5.1.  The client is running TSM 5.1.5.11 &
TDP Oracle ver 2.2.0.1 with Oracle 8.1.7.4.


Thanks,
-
Bruce Kamp
Senior Midrange Systems Analyst
Memorial Healthcare System
E-Mail: [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>
Phone: (954) 987-2020 x4597
Pager: (954) 286-9441
Alphapage: [EMAIL PROTECTED]
Fax: (954) 985-1404
-

Re: TDP Oracle Question

[Hooft, Jeroen]

Maybe setting on disk storagepool: "Maximum Size Threshold"? 

Jeroen


-Original Message-
From: Kamp, Bruce [mailto:[EMAIL PROTECTED]
Sent: maandag 24 mei 2004 14:00
To: [EMAIL PROTECTED]
Subject: TDP Oracle Question


I'm trying to give enough disk to my Oracle backups but have not been
successful.  My management classes point to disk.  How do I find out how
much disk TSM is looking for to backup straight to disk?  I looked on the
system & saw that the dbf files added up to about 133G I have given it 200G.
Or is there something else that could be pointing to tape instead of disk?
I'm running TSM 5.2.1.2 on AIX 5.1.  The client is running TSM 5.1.5.11 &
TDP Oracle ver 2.2.0.1 with Oracle 8.1.7.4.


Thanks,
-
Bruce Kamp
Senior Midrange Systems Analyst
Memorial Healthcare System
E-Mail: [EMAIL PROTECTED] 
Phone: (954) 987-2020 x4597
Pager: (954) 286-9441
Alphapage: [EMAIL PROTECTED]
Fax: (954) 985-1404
-

Re: TDP Oracle backup/restore question

[David Longo]

Most likely the backed up data is all on one tape, and could therefore
be considered a "single threaded" process (my analogy).

To be able to multiple simultaneous restore sessions, the client
must be sent to a storage pool with collocation, or in the case of
RMAN which is just ONE filespace to TSM server, go directly to
tape - and you must have enough tape drives etc to do this.

Quick answer.



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
[EMAIL PROTECTED]


>>> [EMAIL PROTECTED] 08/21/03 03:55PM >>>
Our environment:
   IBM AIX 4.3.3
   TDP- Oracle 2.2.0
   Oracle Database 8.1.7.4

Question:

We are using Oracle RMAN with Tivoli for our backups. In our RMAN scripts
we defined 5 Channels to use for backups. It takes about one and half hours
to complete the backups.
During the Database recovery process, we are using 5 channels. All the time
only one channel is active restoring files and rest of the channels will be
waiting on the current active channel to complete. It's taking about six to
seven hours for the database restore to complete.

Any one had previous experience with RMAN/Tivoli, waiting for allocating
channels during the restore process?

RMAN backup script:
===
   run {
   sql 'alter system archive log current';
   allocate channel t1 type 'sbt_tape' parms
   'ENV=(TDPO_OPTFILE=/usr/tivoli/tsm/client/oracle/ufom/tdpo.opt)';
   allocate channel t2 type 'sbt_tape' parms
   'ENV=(TDPO_OPTFILE=/usr/tivoli/tsm/client/oracle/ufom/tdpo.opt)';
   allocate channel t3 type 'sbt_tape' parms
   'ENV=(TDPO_OPTFILE=/usr/tivoli/tsm/client/oracle/ufom/tdpo.opt)';
   allocate channel t4 type 'sbt_tape' parms
   'ENV=(TDPO_OPTFILE=/usr/tivoli/tsm/client/oracle/ufom/tdpo.opt)';
   allocate channel t5 type 'sbt_tape' parms
   'ENV=(TDPO_OPTFILE=/usr/tivoli/tsm/client/oracle/ufom/tdpo.opt)';
   backup tag='UFOM_20030731164207' filesperset 3
   format "dbase%d_%u"
   (database);
   backup current controlfile;
   sql 'alter system archive log current';
   backup filesperset 10 archivelog all delete input ;
   backup current controlfile;
   }

RMAN Restor script:
==
   run {
 set until logseq 5029 thread 1;
allocate channel t1 type 'sbt_tape' parms
   'ENV=(TDPO_OPTFILE=/usr/tivoli/tsm/client/oracle/ufom/tdpo.opt)';
allocate channel t2 type 'sbt_tape' parms
   'ENV=(TDPO_OPTFILE=/usr/tivoli/tsm/client/oracle/ufom/tdpo.opt)';
allocate channel t3 type 'sbt_tape' parms
   'ENV=(TDPO_OPTFILE=/usr/tivoli/tsm/client/oracle/ufom/tdpo.opt)';
allocate channel t4 type 'sbt_tape' parms
   'ENV=(TDPO_OPTFILE=/usr/tivoli/tsm/client/oracle/ufom/tdpo.opt)';
allocate channel t5 type 'sbt_tape' parms
   'ENV=(TDPO_OPTFILE=/usr/tivoli/tsm/client/oracle/ufom/tdpo.opt)';
restore controlfile;
alter database mount;
restore database;
recover database;
alter database open resetlogs;
release channel t1;
release channel t2;
release channel t3;
release channel t4;
release channel t5;
   }


   Thanks,
   Samba Chebrolu,
   Senior Oracle DBA,
   Technical Services
   FDC Enterprise Systems
   402-222-5662

##
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.
##

Re: TDP Oracle config question

[David Longo]

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
[EMAIL PROTECTED]


>>> [EMAIL PROTECTED] 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:[EMAIL PROTECTED] 
Sent: Thursday, July 17, 2003 10:10 AM
To: [EMAIL PROTECTED] 
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" <[EMAIL PROTECTED]>
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.
##

Re: TDP Oracle config question

[Conko, Steven]

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:[EMAIL PROTECTED]
Sent: Thursday, July 17, 2003 10:10 AM
To: [EMAIL PROTECTED]
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" <[EMAIL PROTECTED]>
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

Re: TDP Oracle config question

[Conko, Steven]

So is this an expected error message every time we run the TDP? Does that
mean it can be ignored?

-Original Message-
From: Neil Rasmussen [mailto:[EMAIL PROTECTED]
Sent: Thursday, July 17, 2003 10:10 AM
To: [EMAIL PROTECTED]
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" <[EMAIL PROTECTED]>
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

Re: TDP Oracle config question

[Conko, Steven]

So, we should just ignore the error?

-Original Message-
From: Neil Rasmussen [mailto:[EMAIL PROTECTED]
Sent: Thursday, July 17, 2003 10:10 AM
To: [EMAIL PROTECTED]
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" <[EMAIL PROTECTED]>
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

Re: TDP Oracle config question

[Neil Rasmussen]

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" <[EMAIL PROTECTED]>
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

Re: TDP Oracle config question

[David Longo]

We use it here, well sort of.  We have a separate node name for the
RMAN backups on each client, that is one node name for B/A on
this machine and a separate node name for the RMAN/TDPO client.

Therefore we have two stanzas each in dsm.sys and dsm.opt and
have separate backup.excl files.  For the one for TDPO/RMAN, we
have one line:

include * oracleclass

If you had one backup.excl, then I think you would have:

include /adsmorc oracleclass

plus whatever other includes/excludes you use.  Haven't used it
that way as ours was setup with separate files and I continued that
format as it works o.k. for us.

David Longo

>>> [EMAIL PROTECTED] 07/16/03 03:47PM >>>
Thanks again. One more quick question... does the filespace name, such as
/adsmorc need to be "included" in the include/exclude list as the docs
state? I suppose if so it would be on the TDP client?

-Original Message-
From: David Longo [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, July 16, 2003 3:23 PM
To: [EMAIL PROTECTED] 
Subject: Re: TDP Oracle config question


No idea about the missing "-".  I believe the long name is built by
Oracle/RMAN and not TSM.  So need to look there.  I don't know
how that is put together, need to get with your DBA or Oracle on that.

(I just looked at mine and all my RMAN backups use "_" as separators
and have different numbering format, but still a long name.)

We have unique names for each node with TDPO_FS, it's not really
required though, you could use /adsmorc for each one.  I think a good
naming standard for your environment is best.

David Longo

>>> [EMAIL PROTECTED] 07/16/03 03:13PM >>>
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

-Original Message-
From: David Longo [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, July 16, 2003 2:23 PM
To: [EMAIL PROTECTED] 
Subject: Re: TDP Oracle config question


You should NOT create a /adsmorc filesystem or mount point.
The docs are correct, this is just the filespace name used on the server
for this node name.  You could change it to something else if you
want with the TDPO_FS env variable.

The message you are getting tells you that that particular object name
does not exist on the server.  Do a "q filespace blah" for the node
name you are using and you should see /adsmorc.

Is this happening when the RMAN scripts try to delete an object?




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
[EMAIL PROTECTED] 


>>> [EMAIL PROTECTED] 07/15/03 03:42PM >>>
TSM Server: AIX 4.3.3, TSM 5.1.5.4
RMAN Server: AIX4.3.3, TDP 5.2
RMAN Client: AIX 4.3.3, TSM 5.1.5, TDP5.2

The installation guide seems to be a little fuzzy on this topic...

At some point during the backup process we get this error in our
tdpoerror.log file:

23:28:55 ANS4994S TDP Oracle AIX ANU0599 ANU2602E The object
/adsmorc//c-3756527612-20030714-03 was not found on the TSM Server


After doing some of my own research I realize its telling me that the
/adsmorc file space does not exist. My question is where is is supposed
to exist? Am I supposed to create an adsmorc file system or directory on the
TSM server, on the TDP/RMAN server, or the client? Is anything ever going to
get put there? Does it need to be its own mount point?

Any help would be greatly appreciated.

Thanks in advance
Steve

##
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.
##

###

Re: TDP Oracle config question

[Conko, Steven]

Thanks again. One more quick question... does the filespace name, such as
/adsmorc need to be "included" in the include/exclude list as the docs
state? I suppose if so it would be on the TDP client?

-Original Message-
From: David Longo [mailto:[EMAIL PROTECTED]
Sent: Wednesday, July 16, 2003 3:23 PM
To: [EMAIL PROTECTED]
Subject: Re: TDP Oracle config question


No idea about the missing "-".  I believe the long name is built by
Oracle/RMAN and not TSM.  So need to look there.  I don't know
how that is put together, need to get with your DBA or Oracle on that.

(I just looked at mine and all my RMAN backups use "_" as separators
and have different numbering format, but still a long name.)

We have unique names for each node with TDPO_FS, it's not really
required though, you could use /adsmorc for each one.  I think a good
naming standard for your environment is best.

David Longo

>>> [EMAIL PROTECTED] 07/16/03 03:13PM >>>
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

-Original Message-
From: David Longo [mailto:[EMAIL PROTECTED]
Sent: Wednesday, July 16, 2003 2:23 PM
To: [EMAIL PROTECTED]
Subject: Re: TDP Oracle config question


You should NOT create a /adsmorc filesystem or mount point.
The docs are correct, this is just the filespace name used on the server
for this node name.  You could change it to something else if you
want with the TDPO_FS env variable.

The message you are getting tells you that that particular object name
does not exist on the server.  Do a "q filespace blah" for the node
name you are using and you should see /adsmorc.

Is this happening when the RMAN scripts try to delete an object?




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
[EMAIL PROTECTED]


>>> [EMAIL PROTECTED] 07/15/03 03:42PM >>>
TSM Server: AIX 4.3.3, TSM 5.1.5.4
RMAN Server: AIX4.3.3, TDP 5.2
RMAN Client: AIX 4.3.3, TSM 5.1.5, TDP5.2

The installation guide seems to be a little fuzzy on this topic...

At some point during the backup process we get this error in our
tdpoerror.log file:

23:28:55 ANS4994S TDP Oracle AIX ANU0599 ANU2602E The object
/adsmorc//c-3756527612-20030714-03 was not found on the TSM Server


After doing some of my own research I realize its telling me that the
/adsmorc file space does not exist. My question is where is is supposed
to exist? Am I supposed to create an adsmorc file system or directory on the
TSM server, on the TDP/RMAN server, or the client? Is anything ever going to
get put there? Does it need to be its own mount point?

Any help would be greatly appreciated.

Thanks in advance
Steve

##
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.
##

##
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

Re: TDP Oracle config question

[David Longo]

No idea about the missing "-".  I believe the long name is built by
Oracle/RMAN and not TSM.  So need to look there.  I don't know
how that is put together, need to get with your DBA or Oracle on that.

(I just looked at mine and all my RMAN backups use "_" as separators
and have different numbering format, but still a long name.)

We have unique names for each node with TDPO_FS, it's not really
required though, you could use /adsmorc for each one.  I think a good
naming standard for your environment is best.

David Longo

>>> [EMAIL PROTECTED] 07/16/03 03:13PM >>>
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

-Original Message-
From: David Longo [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, July 16, 2003 2:23 PM
To: [EMAIL PROTECTED] 
Subject: Re: TDP Oracle config question


You should NOT create a /adsmorc filesystem or mount point.
The docs are correct, this is just the filespace name used on the server
for this node name.  You could change it to something else if you
want with the TDPO_FS env variable.

The message you are getting tells you that that particular object name
does not exist on the server.  Do a "q filespace blah" for the node
name you are using and you should see /adsmorc.

Is this happening when the RMAN scripts try to delete an object?




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
[EMAIL PROTECTED] 


>>> [EMAIL PROTECTED] 07/15/03 03:42PM >>>
TSM Server: AIX 4.3.3, TSM 5.1.5.4
RMAN Server: AIX4.3.3, TDP 5.2
RMAN Client: AIX 4.3.3, TSM 5.1.5, TDP5.2

The installation guide seems to be a little fuzzy on this topic...

At some point during the backup process we get this error in our
tdpoerror.log file:

23:28:55 ANS4994S TDP Oracle AIX ANU0599 ANU2602E The object
/adsmorc//c-3756527612-20030714-03 was not found on the TSM Server


After doing some of my own research I realize its telling me that the
/adsmorc file space does not exist. My question is where is is supposed
to exist? Am I supposed to create an adsmorc file system or directory on the
TSM server, on the TDP/RMAN server, or the client? Is anything ever going to
get put there? Does it need to be its own mount point?

Any help would be greatly appreciated.

Thanks in advance
Steve

##
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.
##

##
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.
##

Re: TDP Oracle config question

[Conko, Steven]

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

-Original Message-
From: David Longo [mailto:[EMAIL PROTECTED]
Sent: Wednesday, July 16, 2003 2:23 PM
To: [EMAIL PROTECTED]
Subject: Re: TDP Oracle config question


You should NOT create a /adsmorc filesystem or mount point.
The docs are correct, this is just the filespace name used on the server
for this node name.  You could change it to something else if you
want with the TDPO_FS env variable.

The message you are getting tells you that that particular object name
does not exist on the server.  Do a "q filespace blah" for the node
name you are using and you should see /adsmorc.

Is this happening when the RMAN scripts try to delete an object?




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
[EMAIL PROTECTED]


>>> [EMAIL PROTECTED] 07/15/03 03:42PM >>>
TSM Server: AIX 4.3.3, TSM 5.1.5.4
RMAN Server: AIX4.3.3, TDP 5.2
RMAN Client: AIX 4.3.3, TSM 5.1.5, TDP5.2

The installation guide seems to be a little fuzzy on this topic...

At some point during the backup process we get this error in our
tdpoerror.log file:

23:28:55 ANS4994S TDP Oracle AIX ANU0599 ANU2602E The object
/adsmorc//c-3756527612-20030714-03 was not found on the TSM Server


After doing some of my own research I realize its telling me that the
/adsmorc file space does not exist. My question is where is is supposed
to exist? Am I supposed to create an adsmorc file system or directory on the
TSM server, on the TDP/RMAN server, or the client? Is anything ever going to
get put there? Does it need to be its own mount point?

Any help would be greatly appreciated.

Thanks in advance
Steve

##
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.
##

Re: TDP Oracle config question

[David Longo]

You should NOT create a /adsmorc filesystem or mount point.
The docs are correct, this is just the filespace name used on the server
for this node name.  You could change it to something else if you
want with the TDPO_FS env variable.

The message you are getting tells you that that particular object name
does not exist on the server.  Do a "q filespace blah" for the node
name you are using and you should see /adsmorc.

Is this happening when the RMAN scripts try to delete an object?




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
[EMAIL PROTECTED]


>>> [EMAIL PROTECTED] 07/15/03 03:42PM >>>
TSM Server: AIX 4.3.3, TSM 5.1.5.4
RMAN Server: AIX4.3.3, TDP 5.2
RMAN Client: AIX 4.3.3, TSM 5.1.5, TDP5.2

The installation guide seems to be a little fuzzy on this topic...

At some point during the backup process we get this error in our
tdpoerror.log file:

23:28:55 ANS4994S TDP Oracle AIX ANU0599 ANU2602E The object
/adsmorc//c-3756527612-20030714-03 was not found on the TSM Server


After doing some of my own research I realize its telling me that the
/adsmorc file space does not exist. My question is where is is supposed
to exist? Am I supposed to create an adsmorc file system or directory on the
TSM server, on the TDP/RMAN server, or the client? Is anything ever going to
get put there? Does it need to be its own mount point?

Any help would be greatly appreciated.

Thanks in advance
Steve

##
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.
##

Re: TDP Oracle config question

[Conko, Steven]

Neil,

Im still waiting to find out from the DBA running it if he thinks it is
succeeding or failing.

Right now we dont have TDPO_FS defined so it is defaulting to adsmorc. My
question is: is this only a filespace created within TSM Server storage or
does there need to be an actual directory/mount point on a server somewhere?
The documents mention including this filespace in the include/exclude list
which leads me to believe I need to create the directory somewhere. Is that
so?

Thanks
Steve

-Original Message-
From: Neil Rasmussen [mailto:[EMAIL PROTECTED]
Sent: Wednesday, July 16, 2003 11:35 AM
To: [EMAIL PROTECTED]
Subject: Re: TDP Oracle config question


Steve,

Can you answer me this? Does your backup actually fail, or is this just
something that shows up during a successful backup?

The /adsmorc filespace is a TSM Server filespace and is the default for
TDP Oracle and will get created during the backup, if it doesn't already
exist. Unless of course, you are specifying something other than the
default (the option is TDPO_FS).

--

Date:Tue, 15 Jul 2003 13:42:36 -0600
From:"Conko, Steven" <[EMAIL PROTECTED]>
Subject: TDP Oracle config question

TSM Server: AIX 4.3.3, TSM 5.1.5.4
RMAN Server: AIX4.3.3, TDP 5.2
RMAN Client: AIX 4.3.3, TSM 5.1.5, TDP5.2

The installation guide seems to be a little fuzzy on this topic...

At some point during the backup process we get this error in our
tdpoerror.log file:

23:28:55 ANS4994S TDP Oracle AIX ANU0599 ANU2602E The object
/adsmorc//c-3756527612-20030714-03 was not found on the TSM Server


After doing some of my own research I realize its telling me that the
/adsmorc file space does not exist. My question is where is is
supposed
to exist? Am I supposed to create an adsmorc file system or directory on
the
TSM server, on the TDP/RMAN server, or the client? Is anything ever going
to
get put there? Does it need to be its own mount point?

Any help would be greatly appreciated.

Thanks in advance
Steve



Regards,

Neil Rasmussen
Software Development
TDP for Oracle

Re: TDP Oracle config question

[Neil Rasmussen]

Steve,

Can you answer me this? Does your backup actually fail, or is this just
something that shows up during a successful backup?

The /adsmorc filespace is a TSM Server filespace and is the default for
TDP Oracle and will get created during the backup, if it doesn't already
exist. Unless of course, you are specifying something other than the
default (the option is TDPO_FS).

--

Date:Tue, 15 Jul 2003 13:42:36 -0600
From:"Conko, Steven" <[EMAIL PROTECTED]>
Subject: TDP Oracle config question

TSM Server: AIX 4.3.3, TSM 5.1.5.4
RMAN Server: AIX4.3.3, TDP 5.2
RMAN Client: AIX 4.3.3, TSM 5.1.5, TDP5.2

The installation guide seems to be a little fuzzy on this topic...

At some point during the backup process we get this error in our
tdpoerror.log file:

23:28:55 ANS4994S TDP Oracle AIX ANU0599 ANU2602E The object
/adsmorc//c-3756527612-20030714-03 was not found on the TSM Server


After doing some of my own research I realize its telling me that the
/adsmorc file space does not exist. My question is where is is
supposed
to exist? Am I supposed to create an adsmorc file system or directory on
the
TSM server, on the TDP/RMAN server, or the client? Is anything ever going
to
get put there? Does it need to be its own mount point?

Any help would be greatly appreciated.

Thanks in advance
Steve



Regards,

Neil Rasmussen
Software Development
TDP for Oracle

Re: Tdp Oracle 2.2 relink Problem

[Vazquez Vegas, Sergio]

Are you trying to install TDP for Oracle 2.2.x over a 8.0.4.1 Oracle
database?



-Mensaje original-
De: Jose Antonio Atala Olaechea [mailto:[EMAIL PROTECTED]]
Enviado el: viernes, 22 de noviembre de 2002 17:49
Para: [EMAIL PROTECTED]
Asunto: Tdp Oracle 2.2 relink Problem


Hi tsm'rs

I have an AIX TSM Client 4.2.2.1 (AIX 4.3.3.). This server have an oracle
8.0.4.1 database installed. When I try to relink the Tdp for Oracle 2.2
libraries, my forms made on Developer 6i can't be saved on the Oracle
database. This error doesn't happen with my other forms made with Developer
2.1.

What can I do ? any idea?



José Antonio Atala Olaechea
Visiontech del PerúObtenga el máximo provecho del Web. Descarga GRATUITA de
MSN Explorer: http://explorer.msn.es/intl.asp#es

Este mensaje de correo electrónico y sus documentos adjuntos están dirigidos
EXCLUSIVAMENTE a los destinatarios especificados. La información contenida
puede ser CONFIDENCIAL y/o estar LEGALMENTE PROTEGIDA y no necesariamente
refleja la opinión de ENDESA. Si usted recibe este mensaje por ERROR, por
favor comuníqueselo inmediatamente al remitente y  ELIMÍNELO ya que usted
NO ESTA AUTORIZADO al uso, revelación, distribución, impresión o copia de
toda o alguna parte de la información contenida. Gracias. 

This e-mail message and any attached files are intended SOLELY for the
addressee/s identified herein. It may contain CONFIDENTIAL and/or LEGALLY
PRIVILEGED  information and may not necessarily represent the opinion of
ENDESA. If you receive this message in ERROR, please immediately notify the
sender and DELETE it since you ARE NOT AUTHORIZED  to use, disclose,
distribute, print or copy all or part of the contained information. Thank
you.  

Re: TDP Oracle support for Oracle 9i on W2K

[Zlatko Krastev/ACIT]

But IBM's Announcement Letter states that it is already supported since
October 8-th. Quote from EMEA Letter ZP02-494 (find yourself corresponding
US Letter):
"Data Protection for Oracle Version 2.2 on Windows
...
- Oracle8i 8.1.7, or Oracle8i 8.1.7 Parallel Server, or Oracle9i 9.0.1, or
later, or Oracle9i 9.0.1 Parallel Server, or later"

AFAIK Announcement Letters are most authoritative source of information.
When a Letter says "Yes" and the site says "No", the answer ought to be
"Yes" and the site is outdated.

Zlatko Krastev
IT Consultant






David Longo <[EMAIL PROTECTED]>
Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
10.10.2002 01:30
Please respond to "ADSM: Dist Stor Manager"


To: [EMAIL PROTECTED]
cc:
Subject:TDP Oracle support for Oracle 9i on W2K


Tivoli Website seems to indicate that Oracle 9i is not yet supported
for TDP Oracle on W2K clients.  Anybody have any info on this?

Is it where it will "probably work" but is not officially supported
yet?

Thanks,


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
[EMAIL PROTECTED]


"MMS " made the following
 annotations on 10/09/2002 06:31:27 PM
--
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.

==

Re: tdp-oracle 2.2.0.2 with unkown error

[Neil Rasmussen]

The rc = 406 is a return code from the TSM API and Oracle caught the
error. I am not sure why there is no logging from the TSM API to help you
indicate where the error originated. Rc = 406 is telling me that the TSM
API could not find the dsm.opt file. Please make sure that you're TDP for
Oracle options file has an entry similar to the following:

DSMI_ORC_CONFIGc:\tivoli\tsm\agentoba\dsm.opt

With this, TDP for Oracle will pass into the TSM API where to find the
dsm.opt file.


--

Date:Fri, 26 Apr 2002 12:19:03 +0200
From:Norbert Martin NKM-Solutions <[EMAIL PROTECTED]>
Subject: tdp-oracle 2.2.0.2  with unkown error

Hi,
at the moment we have the problem with a tdp for Oracle NT V2.2.0.2 an
Client 4.2.1.20

Please help

Has anybody seen this problem und lose this before?
Error Log / Sched Log:
04/25/2002 11:59:45 ANS1512E Scheduled event 'IC_V1_W1_NT_ORACLE' failed.
Return code = 3.
04/25/2002:09:44:48 PID<158>  ==>  Error: pstdpoCallDsmSetUp failed. rc =
406

What is happend? The Oracle DB is a 8.0.5


RMAN-06005: connected to target database: SVP_BUHA
RMAN-06008: connected to recovery catalog database

RMAN> run {
2> allocate channel t1 type 'SBT_TAPE' parms
3> 'ENV=(TDPO_OPTFILE=c:\apps\tivoli\tsm\AgentOBA\tdpo.opt)';
4>
5> allocate channel t2 type 'SBT_TAPE' parms
6> 'ENV=(TDPO_OPTFILE=c:\apps\tivoli\tsm\AgentOBA\tdpo.opt)';
7>
8> backup incremental level 0
9> format 'df_%t_%s_%p_%u_%c'
10> (database include current controlfile);
11>
12> sql 'alter system archive log current';
13>
14> backup  archivelog all delete input
15> format 'df_%t_%s_%p_%u_%c';
16>
17> release channel t1;
18>
19> release channel t2;
20> }
21>
RMAN-03022: compiling command: allocate
RMAN-03023: executing command: allocate
RMAN-00569: error message stack follows
RMAN-00601: fatal error in recovery manager
RMAN-03004: fatal error during execution of command
RMAN-07001: could not open channel t1
RMAN-10008: could not create channel context
RMAN-10024: error setting up for rpc polling
RMAN-10006: error running sql statement: select distinct my.sid,
sex.serial
from
 v$mystat my, x$ksusex sex where sex.sid = my.sid
RMAN-10002: ORACLE error: ORA-01455: converting column overflows integer
datatyp

with kind regards / mit freundlichen Gruessen

Norbert Martin
High End Storage Consultant
DISK / TAPE / SAN / TSM
Mobile:+49-170-2234111
E-Mail:[EMAIL PROTECTED]


Regards,

Neil Rasmussen
Software Development
TDP for Oracle
[EMAIL PROTECTED]

Re: tdp-oracle

[Jim Healy]

versioning for TDP for oracle should be handled by RMAN according to
recomendations, setting verd and vere allows this to happen.




"Johnson, Reginald (ECCS)" <[EMAIL PROTECTED]>@VM.MARIST.EDU> on
04/23/2002 01:23:26 PM

Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>

Sent by:  "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>


To:   [EMAIL PROTECTED]
cc:

Subject:  tdp-oracle


I see in the guide for tdp for oracle that is recommended that tdp  have
its own separate domain. Within this domain there is copy group with
verdeleted=0 and retonly=0. Can someone explain why it is
recommended to have its own separate domain.

Reggie

Re: TDP Oracle on AIX 5.1

[Luis Tapia]

thanks, i have already got it from support, i installed it yesterday and i4m
not fighting with the tdpoconf... already opened a PMR.

thanks again


>From: Neil Rasmussen <[EMAIL PROTECTED]>
>Reply-To: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
>To: [EMAIL PROTECTED]
>Subject: Re: TDP Oracle on AIX 5.1
>Date: Mon, 22 Apr 2002 13:17:08 -0700
>
>Luis,
>
>Yes, here is the site, it should be accessable from the internet.
>
>ftp://service.boulder.ibm.com/storage/tivoli-storage-management/
>
>
>--
>
>Date:Fri, 19 Apr 2002 19:12:21 +
>From:Luis Tapia <[EMAIL PROTECTED]>
>Subject: Re: TDP Oracle on AIX 5.1
>
>Thanks Neil, yes, it4s AIX 5.1 32bit, which ftp site are you talking
>about?
>the one at service.boulder? it4s accesible from the internet?
>
>thanks again
>
>
>Regards,
>
>Neil Rasmussen
>Software Development
>TDP for Oracle
>[EMAIL PROTECTED]




_
Send and receive Hotmail on your mobile device: http://mobile.msn.com

Re: TDP Oracle on Linux (was AIX 5.1)

[Neil Rasmussen]

Linux support for TDP for Oracle is due out 1Q03 time frame.

--

Date:Tue, 23 Apr 2002 08:48:13 -0400
From:Zoltan Forray/AC/VCU <[EMAIL PROTECTED]>
Subject: TDP Oracle on Linux (was AIX 5.1)

Now then, how about a TDP for Oracle on Linux 

We have been running Oracle on a RH Linux box, for a long time. It is
supported by Oracle !



Regards,

Neil Rasmussen
Software Development
TDP for Oracle

Re: tdp-oracle

[Loon, E.J. van - SPLXM]

Hi Reggie!
This is because you don't want TSM to expire Oracle backup objects.
Oracle does not rely on TSM for backup cataloging. It uses it's own: the
Oracle Recovery Catalog. When you initiate a restore on a Oracle client, it
connects to the Oracle Recovery Catalog and it uses information in that
catalog to retrieve the backup sets and backup pieces names. With that
information the client connects to TSM to retrieve those sets and pieces.
Every now and then you schedule a cleanup script on the client which removes
obsolete sets and pieces. This removes the references from the Oracle
recovery catalog and deletes the actual data from TSM.
Kindest regards,
Eric van Loon
KLM Royal Dutch Airlines


-Original Message-
From: Johnson, Reginald (ECCS) [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, April 23, 2002 19:23
To: [EMAIL PROTECTED]
Subject: tdp-oracle


I see in the guide for tdp for oracle that is recommended that tdp  have its
own separate domain. Within this domain there is copy group with
verdeleted=0 and retonly=0. Can someone explain why it is
recommended to have its own separate domain.

Reggie


**
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.
**

Re: TDP Oracle on AIX 5.1

[Neil Rasmussen]

Luis,

Yes, here is the site, it should be accessable from the internet.

ftp://service.boulder.ibm.com/storage/tivoli-storage-management/


--

Date:Fri, 19 Apr 2002 19:12:21 +
From:Luis Tapia <[EMAIL PROTECTED]>
Subject: Re: TDP Oracle on AIX 5.1

Thanks Neil, yes, it4s AIX 5.1 32bit, which ftp site are you talking
about?
the one at service.boulder? it4s accesible from the internet?

thanks again


Regards,

Neil Rasmussen
Software Development
TDP for Oracle
[EMAIL PROTECTED]

Re: TDP Oracle on AIX 5.1

[Luis Tapia]

Thanks Neil, yes, it4s AIX 5.1 32bit, which ftp site are you talking about?
the one at service.boulder? it4s accesible from the internet?

thanks again


>From: Neil Rasmussen <[EMAIL PROTECTED]>
>Reply-To: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
>To: [EMAIL PROTECTED]
>Subject: TDP Oracle on AIX 5.1
>Date: Thu, 18 Apr 2002 06:58:04 -0700
>
>Luis,
>
>What version of AIX 5 are you after, AIX 5 32bit? Tivoli has GAed TDP for
>Oracle 2.2.1 (aka 5.1.0) that supports AIX 5 32bit and has been available
>on the ftp site for some weeks now. If you do not qualify for FTP TDP for
>Oracle please see your rep. for the GAed version. AIX 5 64bit support will
>come at a later date, I just noticed that Oracle has released its
>developers release for Oracle 9i on AIX 5L (64bit). Hope this helps.
>
>
>--
>
>Date:Wed, 17 Apr 2002 16:53:16 -0400
>From:Luis Tapia <[EMAIL PROTECTED]>
>Subject: TDP Oracle on AIX 5.1
>
>Hi list, I'want to know if some of you have some experiences installing
>TDP
>for Oracle for AIX in an AIX 5.1 box, as you know it is not supported but,
>is there a way? i mean, do i have to wait until tivoli releases 5.1
>support?
>(someday) please help, i have a big warehouse oracle and i have to backup
>it
>to a robot in a TSM environment.
>
>thanks
>
>LT
>
>
>Regards,
>
>Neil Rasmussen
>Software Development
>TDP for Oracle




_
Join the world s largest e-mail service with MSN Hotmail.
http://www.hotmail.com

Re: TDP Oracle 2.1.10 'libobk.so' problems on Oracle 8.1.7 / Solaris 2.7

[Thiha Than]

hi,

Please use TSM 4.1.2.12 API 32 bit not 64 bit.  Your problem should be
fixed by doing so.

regards,
Thiha
To: [EMAIL PROTECTED]
cc:
Subject:TDP Oracle 2.1.10 'libobk.so' problems on Oracle 8.1.7 / Solaris 2.7




We have the following configuration (all on same Sun Ultra server
hardware/OS):

Solaris 7 (64-bit kernel)
Oracle 8.1.7/RMAN (32-bit)
TSM Server  4.1.2
(new)TSM 4.1.2.12 BA Client (64-bit)
(new)TSM 4.1.2.12 API (64-bit)
(new)TDP Oracle 2.1.10 (32-bit)

We're trying to test RMAN with TDP-Oracle, but are having problems getting
Oracle/RMAN to interact with the TDP-Oracle 2.1.10 (32-bit) Media
Management Library 'libobk.so'.  RMAN fails to recognize 'SBT_TAPE'.

Both Oracle and ADSM-L have posted problem reports on this issue which
identified some Solaris OS patches.  However, all of those patches are
installed and we are still having problems.  These Solaris OS patches are
installed:  106300 106327 106980 106541 107544.  One other mentioned patch 109104 has 
been superseded & is not
installed.  There's a chance that 106980-07 is down-rev vs postings.

Our Oracle admin advised me to install the 32-bit 'libobk.so' library for
compatibility.  I might suspect 32-bit/64-bit compatibility issues, but
'aobpswd' runs successfully, opening a TSM Server (v4.1.2) session of type
'TDP Oracle SUN'.   Isn't that sufficient proof that the TDP-Oracle
library and the TSM API configuration are functioning properly together?
 If so, where does the problem (more importantly the resolution) lie?

If you can help me resolve this, rsvp.thanks

Kent Monthei
GlaxoSmithKline

Re: TDP Oracle 2.2 with SAP R/3 on HP-UX

[Robin Sharpe]

Thanks Thiha,

I had stepped away from it for a while, and our Basis administrator got it
working... I'm not exactly sure what he did, but I just looked at the
$ORACLE_HOME/lib directory and there is no libobk.sl there.
/usr/lib/libobk is indeed linked to
/opt/tivoli/tsm/client/oracle/bin/libobk.sl...  I guess that was the trick,
but i really don't remember it being setup that way the other times I
installed it.   Oh well.

Robin



Thiha Than
<[EMAIL PROTECTED]
.COM> To:[EMAIL PROTECTED]
  cc:(bcc: Robin Sharpe/WA/USR/SHG)
12/11/01  Subject:
04:14 PM TDP Oracle 2.2 with SAP R/3 on HP-UX
Please
respond to
"ADSM: Dist
Stor Manager"









I've never tried with R3 and TDPO but we have machines with two different
Oracle level using one libobk.  For Oracle 8.0.6 you will have to
relink(make) and on 8.1.x just creating a soft link from
$ORACLE_HOME/lib/libobk.sl to /usr/lib/libobk.sl is enough.  The
instructions in the manual is correct.  Please make sure to add -lC when
you run 'make' command to relink for 8.0.x.  You mentioned that your
linking was correct and RMAN was looking for /usr/lib/libobk.sl.  What is
/usr/lib/libobk.sl pointing to?  It is supposed to be a soft link to
/opt/tivoli/tsm/client/oracle/bin/libobk.sl.  Can you give me the exact
error that RMAN is reporting?

regards,
Thiha

Re: TDP-Oracle 2.2 Unix

[Michel Engels]

We are setting V2.2 up on a SUN box. Comparing to the previous installation we
did with version V2.10 we had less problems. No relink to be done for Oracle
only creating the link specified in the readme and it worked. The
managementclass we did specify in the dsm.sys in the API directory. We coded
"Include * ORCALE_BU" and all the files were stored in that class. We are still
doing some test therefor I can not say more about second class. Only one thing
we tested and did not work as we would expect is the "tdposync syncdb"-command.
Some tests have still to be done. Specifying another mgmtclass does not change
the policy data information in the TDPOCONF SHOWENV command.

Hope this helps,

Michel Engels
TSM Consultant
Devorteam Belgium






Christoph Pilgram <[EMAIL PROTECTED]> on 07/06/2001
09:22:52 AM

Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>

To:   [EMAIL PROTECTED]
cc:(bcc: Michel Engels/BE/Devoteam)

Subject:  TDP-Oracle 2.2 Unix



Hy all,

we are trying to set up TDP for Oracle 2.2 on a HP-UX box.
We do not manage to assign a separate managment class to the filespace
'/adsmorc'. Although we have an include 'include  /adsmorc/.../* unix_tdp'
in the inclexcl-list the files are always assigned to the
default-management-class. In the error-log the following message is written
:
"Management class 'ORCBACKUP' named on include/exclude line 1 does not
exist."

Can anybody help

Christoph

Re: TDP oracle...and q filespace

[Williams, Tim]

Try q occupancy:
tsm: ADSM>q occupancy *tdp

Node NameType Filespace  StorageNumber
of  Physical   Logical
  Name   Pool Name
Files Space Space

Occupied  Occupied

(MB)  (MB)
  -- --
- - -
PBSXDR00012_TDP  Bkup /oracledb  ORCLDISK
4  0.41  0.41
PBSXDR00012_TDP  Bkup /oracledb  ORCLTAPE
37 10,922.65 10,922.65
PBSXDR00012_TDP  Bkup /oracledb  ORCLTAPE_-
37 10,922.65 10,922.65
  CP





Thiha Than <[EMAIL PROTECTED]>
01/30/2001 11:50 AM
Please respond to "ADSM: Dist Stor Manager"
<[EMAIL PROTECTED]>@SMTP@Exchange
To: [EMAIL PROTECTED]@SMTP@Exchange
cc:

Subject:TDP oracle

hi,

The file space that got created for TDPO backup is only virtual.  So
there
is no way to find out the capacity and pct util.

regards,
Thiha


>When I use TDP for Oracle the backup completes OK.
>But when I issue the command

>query filespace

>TSM tells me the following:
>Node NameFilespace   Platform FilespaceCapacity
Pct
>   Name Type
=
>   (MB)Util
>-- ---   
-
=
>    -
>SVRDBS02_ORC   /WHEPPTDP  API:ORAC-  0.00.0
   Oracle   LE
=

>Question:
>I can also see the files using the command  show versions
 *
>But why is the capacity and the Pct Util  0% ??
>Does it have something to do with the DSMO_AVG_SIZE parameter?