Theresa,
when I run the command I see info like this:
/adsmorc : // al_00ee894v_1_1 (MC: DEFAULT)
Active, Inserted 01/31/03 02:40:32
ObjId: 0.134453795
/adsmorc : // al_01ee894v_1_1 (MC: DEFAULT)
Active, Inserted 01/31/03 02:40:32
ObjId: 0.134453794
/adsmorc : // al_03ee89nc_1_1 (MC: DEFAULT)
Active, Inserted 01/31/03 02:50:22
ObjId: 0.134455581
/adsmorc : // al_04e7u4ci_1_1 (MC: DEFAULT)
Active, Inserted 11/16/02 10:40:20
ObjId: 0.112626200
Does the insertion data jibe with reality? I mean, RMAN/TDPO are set up to
only keep 7 days worth of incrs. So, following that logic, those object
should not be there, correct? Isn't the tdposync utility supposed to get
rid of the stragglers?
When I run tdposync syncdb, it comes back with the message that "The TSM
Server is synchronized with the Oracle Catalog or there are no matching
files in the requested filespace"
If these are stranded objects, how would I delete them from TSM, since
RMANs catalog doesn't know about them?
help!
lisa
Theresa Sarver
<tsarver.IFMC@ To: [EMAIL PROTECTED]
SDPS.ORG> cc:
Sent by: Subject: SHOW commands and TSM 5162
"ADSM: Dist
Stor Manager"
<[EMAIL PROTECTED]
IST.EDU>
02/20/2003
05:13 PM
Please respond
to "ADSM: Dist
Stor Manager"
Does anyone know - do the SHOW commands work with TSM Server 5162? I used
them all the time to view my TDP for Oracle data under TSM415, but after
upgrading the following is returned:
tsm: C2TSMSERV>show version c2f1n11ex_oracle /adsmorc
ANR0852E SHOW: No matching file spaces found for node C2F1N11EX_ORACLE.
Anyone else running 5162 and able to use the SHOW VERSION command?
Thanks;
Theresa
