Hi
I don't know if anyone else has replied, but we've seen this.
For us it was caused by a down-level TSM backup-archive client (the TDP
uses the API from this). When there was a tape I/O error, TDP tried to
re-try the write, but the API couldn't handle it. We were at BA client
3.7.x.x - after upgrading to BA client level 4.2.x.x we haven't seen the
problem.
BTW, we're also on TDP 3.2.0.8, but I don't think that that was the
problem. I seem to remember that the BKI9001E msg disappeared when going to
4.2.x.x even with 3.2.0.4
Regards
Richard Foster
d.mueller@LVR
.DE To: [EMAIL PROTECTED]
Sent by: cc:
[EMAIL PROTECTED] Subject: ANS1017E (RC-50) Session
rejected: TCP/IP connection failure
IST.EDU
2002-08-16
09:01
Please
respond to
ADSM-L
Hello,
I have TDP 3.2.04 on AIX 4.3.3.
Last night I got the following error:
ANS1017E (RC-50) Session rejected: TCP/IP connection failure
.
.
.
BKI9001E: Internal error: new Message_Block failed.
BKI9001E: Internal error: new Message_Block failed.
BKI1208E: The object '/oracle/P02/sapdata10/btabi_6/btabi.data6' will be
retried [2].
BKI1208E: The object '/oracle/P02/sapdata16/btabd_21/btabd.data21' will be
retried [2].
BKI1208E: The object '/oracle/P02/sapdata4/clud_5/clud.data5' will be
retried [2].
BKI0027I: Time: 08/15/2002 21:59:53 Object: 55 of 122 in process:
/oracle/P02/sapdata10/btabi_6/btabi.data6 Size: 2039.008 MB, MGMNT-CLASS:
SAP_PRODP_D_DY_D30, TSM-Server: ADSM .
BKI0027I: Time: 08/15/2002 21:59:53 Object: 56 of 122 in process:
/oracle/P02/sapdata16/btabd_21/btabd.data21 Size: 2000.008 MB, MGMNT-CLASS:
SAP_PRODP_D_DY_D30, TSM-Server: ADSM .
BKI0027I: Time: 08/15/2002 21:59:53 Object: 57 of 122 in process:
/oracle/P02/sapdata4/clud_5/clud.data5 Size: 360.008 MB, MGMNT-CLASS:
SAP_PRODP_D_DY_D30, TSM-Server: ADSM .
BR233E Backup utility has reported an error while saving file
/oracle/P02/sapdata10/btabi_6/btabi.data6
BR233E Backup utility has reported an error while saving file
/oracle/P02/sapdata12/btabd_40/btabd.data40
.
.
.
I know that we had some problems with our network in the last two weeks.
I think that this error is a consequence of a new network-error, but I
don�t want to be hasty.
Is there anyone who know if this error can be a other cause???
Or have you had the same problem and it was really a network-error???
TIA
Dirk
