Bill,

How would you pass this info on the command line????  as it prompts you for it 
when you execute TDPOSYNC.

Catalog user name
Catalog Password
Catalog Connect String

-----Original Message-----
From: Bill Boyer [mailto:bill.boyer AT VERIZON DOT NET]
Sent: Thursday, February 13, 2003 9:52 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: TDP monitoring


Let your DBA create the shell scripts and RMAN scripts for the backups and
TDPOSYNC, then YOU schedule them via TSM. Create a command schedule that
SU's to the Oracle user and runs the shell script(s). The result is then
posted as the completion code for the schedule event. The DBA (or whoever
creates the shell scripts) needs to make sure and return from the script
with an meaningfull code.

Like su - ORACLE "-c /path/to/shell/script.sh"

Bill Boyer
"My problem was caused by a loose screw at the keyboard" - ??

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU]On Behalf Of
Wholey, Joseph (TGA\MLOL)
Sent: Thursday, February 13, 2003 9:45 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: TDP monitoring


Tyring to get a general survey of how TSMers managing large scale
deployments of TDP for Oracle.

Since it's a client driven process (in our environment), the success or
failure is difficult to monitor.
Also, TDPOSYNC requires information only the DBAs would know.
e.g.    Catalog user name
        Catalog Password
        Catalog Connect String


How do most people manage that?  How do you keep a DBA honest and make sure
he runs it?
Any info would be greatly appreciated.

Regards, Joe