newguy2489
ADSM.ORG Member
- Joined
- Jun 24, 2009
- Messages
- 16
- Reaction score
- 0
- Points
- 0
We have an older Oracle instance (9.2.08) running on AIX 6.1 that we are backing up to TSM. The B/A client, and it's api have been updated to 7.1.1.4, but the Oracle TDP, matched to the DB version is at 5.4. 1.0 so we are no longer supported by Tivoli.
We have implemented a new TSM infrastructure with replication of our 2 primary TSM servers to 2 remote TSM servers, and now I am starting to see some of these off backup failures related to dsm.sys file options. When we started doing the replication, we noticed lots of errors in the client error logs all relating to a nrtable database... and after some research found that we needed to add in new parms to the dsm.sys files to let each backup (B/A and Oracle TDP in this case) write it's own copy of this database, and it also seems to update the dsm.sys file with replication related info after or during each backup. We fixed these errors, but now we are getting sporadic backup failures
On several occasions in the past few weeks, we have seen backup failures for this node, some right out of the gate, some near the time the backup normally completes, but all have made reference to invalid options in the dsm.sys file. In one case I found several replication related parms, that looked ok, but were in the wrong spot in the stanza, I deleted them, and the next backup completed successfully. In another case I couldn't find anything wrong, but restoring the dsm.sys file to the one from the previous night's backup solved the issue.
Anyone else seeing anything like this? Any thoughts or ideas are greatly appreciated.
Thanks!
We have implemented a new TSM infrastructure with replication of our 2 primary TSM servers to 2 remote TSM servers, and now I am starting to see some of these off backup failures related to dsm.sys file options. When we started doing the replication, we noticed lots of errors in the client error logs all relating to a nrtable database... and after some research found that we needed to add in new parms to the dsm.sys files to let each backup (B/A and Oracle TDP in this case) write it's own copy of this database, and it also seems to update the dsm.sys file with replication related info after or during each backup. We fixed these errors, but now we are getting sporadic backup failures
On several occasions in the past few weeks, we have seen backup failures for this node, some right out of the gate, some near the time the backup normally completes, but all have made reference to invalid options in the dsm.sys file. In one case I found several replication related parms, that looked ok, but were in the wrong spot in the stanza, I deleted them, and the next backup completed successfully. In another case I couldn't find anything wrong, but restoring the dsm.sys file to the one from the previous night's backup solved the issue.
Anyone else seeing anything like this? Any thoughts or ideas are greatly appreciated.
Thanks!