Joe - I have seen the same thing and reported it to IBM,
but so far they have just given me a list of things to check.
I encourage you to call it in too, if they see another account having
the same problem, it might prompt them to work harder on it.
Everything on the server and client checks out fine, and since
we run ~30 instances of oracle on the same machine, and the same
tdpo backs up 29 just fine, well it is a mystery.
The one odd thing about the one instance that gets these errors is
that it only happens on a level 2 backup; level 0 backups (full) run
fine.
Hope this helps,
Bill Colwell
At 12:23 PM 1/10/2004, you wrote:
>Need help...
>
>I'm getting this message prior to the TDP for Oracle backup failure. It
>transmits appx 6G over 3 channels, but then generates the following errors in
>the tdpoerror.log. I'm not that concerned with
>the ANU2602E or the ANS4994S, but I am concerned with the ANU2508E. Also,
>there is very little documentation on the error.
>We (tsm admins) did not change any configuration on our side, and the DBA's
>state they made no changes on their side. There is nothing in the actlog to
>indicate there is a problem. My initial
>question is, "what is in the "Wrong write state""? And my next question is,
>how do I resolve? Before I call support, does anyone have any insight?
>
>OS platform SunOS 5.8
>Oracle 8.1.7
>TDPv2.2.1
>TSM Server V5,2,0.0 running on zOS
>
>01/10/04 09:26:59 ANU2508E Wrong write state
>01/10/04 09:28:30 ANU2602E The object /adsmorc//arch.BFRMDM.9720.515063712
>was not found on the TSM Server
>01/10/04 09:28:30 ANS4994S TDP Oracle SUN ANU0599 ANU2602E The object
>/adsmorc//arch.BFRMDM.9720.515063712 was not fou
>nd on the TSM Server
>01/10/04 09:28:31 ANU2602E The object /adsmorc//arch.BFRMDM.9719.515063712
>was not found on the TSM Server
>01/10/04 09:28:31 ANS4994S TDP Oracle SUN ANU0599 ANU2602E The object
>/adsmorc//arch.BFRMDM.9719.515063712 was not fou
>nd on the TSM Server
>
>Regards, Joe
----------
Bill Colwell
C. S. Draper Lab
Cambridge Ma.
|
