Rob, Try the following patch for TDP for Oracle:
ftp://service.boulder.ibm.com/storage/tivoli-storage-management/patches/tivo li-data-protection/oracle/win/v2202/ Just recently we had an Oracle machine with similar problems and tried the above patch and all was ok. Cheers Paul -----Original Message----- From: Rob Schroeder [mailto:[EMAIL PROTECTED]] Sent: 12 February 2002 19:30 To: [EMAIL PROTECTED] Subject: tdp for oracle We hare having issues where the TDP for oracle RMAN scripts are termintating. The error happens about the same time that the 2000 server briefly falls off the network. I have no idea why, the outage is about 90 seconds and the TSM services never stop, but obviously the sessions do. Also, when we run the RMAN scripts, the CPU hits 100% on the client with the largest processing being oracle.exe using 90%. Has anyone had performance issues with this and resolved them. TSM server: Win2000 SP2 TSM 4.1.4.1 TSM client: Win2000 SP2 TSM 4.2.1.20 TDP for oracle: v2.2 Here is the error on the TSM server 02/12/2002 10:56:41 ANE4993E (Session: 1501, Node: FFORACLE01_ORACLE) TDP Oracle NT ANS02041 TDP for Oracle: (872): =>() ANS0238E (RC2041) The sequence of calls is invalid. Here is the error on the client: RMAN-03022: compiling command: backup RMAN-03025: performing implicit partial resync of recovery catalog RMAN-03023: executing command: partial resync RMAN-08003: starting partial resync of recovery catalog RMAN-08005: partial resync complete RMAN-03023: executing command: backup RMAN-08009: channel t1: starting archivelog backupset RMAN-08502: set_count=37 set_stamp=453641102 creation_time=12-FEB-02 RMAN-08014: channel t1: specifying archivelog(s) in backup set RMAN-08504: input archivelog thread=1 sequence=1643 recid=1 stamp=453556579 RMAN-08009: channel t2: starting archivelog backupset RMAN-08502: set_count=38 set_stamp=453641102 creation_time=12-FEB-02 RMAN-08014: channel t2: specifying archivelog(s) in backup set RMAN-08504: input archivelog thread=1 sequence=1644 recid=2 stamp=453569684 RMAN-08504: input archivelog thread=1 sequence=1645 recid=3 stamp=453572365 RMAN-08504: input archivelog thread=1 sequence=1646 recid=4 stamp=453573025 RMAN-08504: input archivelog thread=1 sequence=1647 recid=5 stamp=453574226 RMAN-00571: =========================================================== RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS =============== RMAN-00571: =========================================================== RMAN-03007: retryable error occurred during execution of command: backup RMAN-07004: unhandled exception during command execution on channel t1 RMAN-10035: exception raised in RPC: ORA-19502: write error on file "al_37_1_453641102", blockno 1665 (blocksize=512) ORA-27030: skgfwrt: sbtwrite2 returned error ORA-19511: ANS1017E (RC-50) Session rejected: TCP/IP connection failure RMAN-10031: ORA-19624 occurred during call to DBMS_BACKUP_RESTORE.BACKUPPIECECREATE Any help is appreciated. Thanks Rob Schroeder Famous Footwear [EMAIL PROTECTED] http://www.phoenixitgroup.com ******************Internet Email Confidentiality Footer******************* Phoenix IT Group Limited is registered in England and Wales under company number 3476115. Registered Office: Technology House, Hunsbury Hill Avenue, Northampton, NN4 8QS Opinions, conclusions and other information in this message that do not relate to the official business of our firm shall be understood as neither given nor endorsed by it. No contracts may be concluded on behalf of our firm by means of email communications. Confidentiality: Confidential information may be contained in this message. If you are not the recipient indicated (or responsible for delivery of the message to such person), you may not take any action based on it, nor should you copy or show this to anyone; please reply to this email and highlight the error to the sender, then delete the message from your system. Monitoring of Messages: Please note that we reserve the right to monitor and intercept emails sent and received on our network. Warning: Internet email is not 100% secure. We ask you to understand and observe this lack of security when emailing us. We do not accept responsibility for changes made to this message after it was sent Viruses: Although we have taken steps to ensure that this email and any attachments are free from any virus, we advise that in keeping with good computing practice the recipient should ensure they are actually virus free.
