By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
437,557 Members | 1,067 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 437,557 IT Pros & Developers. It's quick & easy.

Back Terminated to TSM - Media controller -- problem writing to vendor device. rc = -2025

P: n/a
Hi Group,

I'm running DB2 UDB Enterprise Edition V7.1 in AIX 4.3.3.0. And
database backups goes to the TSM server. We have the following TSM
Client API installed in the server:

tivoli.tsm.client.api.aix43.32bit 5.1.6.0 C TSM Client -
Application Programming Interface

Now my backup getting terminated with the following message in the
db2diag.log:

2007-01-08-22.19.33.800923 Instance:****** Node:000
PID:148604(db2med.84282.0) Appid:none
database_utilities sqluMapVend2MediaRCWithLog Probe:1

Error in Vendor Support Code at line: 983. rc: -50

2007-01-08-22.19.33.812355 Instance:****** Node:000
PID:148604(db2med.84282.0) Appid:none
database_utilities sqluMCWriteToDevice Probe:50

Media controller -- problem writing to vendor device. rc = -2025

2007-01-08-22.19.33.832505 Instance:****** Node:000
PID:84282(db2agent (******)) Appid:*******.070108192217
database_utilities sqlubMWResponse Probe:5 Database:******

DiagData
ffff f817 2d35 30ff 5453 4d00 ....-50.TSM.
What is the cause for the above return codes: Which return code to
consider for troubleshooting as there are two entries RC:- 50 and RC:-
-2025....

Kindly throw some light on what is the issue and how to resolve this?

Thanks in advance,
vj_dba

Feb 15 '07 #1
Share this Question
Share on Google+
5 Replies


P: n/a
On Feb 15, 4:04 am, vijay...@gmail.com wrote:
Hi Group,

I'm running DB2 UDB Enterprise Edition V7.1 in AIX 4.3.3.0. And
database backups goes to the TSM server. We have the following TSM
Client API installed in the server:

tivoli.tsm.client.api.aix43.32bit 5.1.6.0 C TSM Client -
Application Programming Interface

Now my backup getting terminated with the following message in the
db2diag.log:

2007-01-08-22.19.33.800923 Instance:****** Node:000
PID:148604(db2med.84282.0) Appid:none
database_utilities sqluMapVend2MediaRCWithLog Probe:1

Error in Vendor Support Code at line: 983. rc: -50

2007-01-08-22.19.33.812355 Instance:****** Node:000
PID:148604(db2med.84282.0) Appid:none
database_utilities sqluMCWriteToDevice Probe:50

Media controller -- problem writing to vendor device. rc = -2025

2007-01-08-22.19.33.832505 Instance:****** Node:000
PID:84282(db2agent (******)) Appid:*******.070108192217
database_utilities sqlubMWResponse Probe:5 Database:******

DiagData
ffff f817 2d35 30ff 5453 4d00 ....-50.TSM.

What is the cause for the above return codes: Which return code to
consider for troubleshooting as there are two entries RC:- 50 and RC:-
-2025....

Kindly throw some light on what is the issue and how to resolve this?

Thanks in advance,
vj_dba

how about back and restore files througth TSM? such kind of errors
always caused by reasons outside of DB2. check tsm configure again?

Feb 15 '07 #2

P: n/a
vi******@gmail.com wrote:
Hi Group,

I'm running DB2 UDB Enterprise Edition V7.1 in AIX 4.3.3.0. And
database backups goes to the TSM server. We have the following TSM
Client API installed in the server:

tivoli.tsm.client.api.aix43.32bit 5.1.6.0 C TSM Client -
Application Programming Interface

Now my backup getting terminated with the following message in the
db2diag.log:

2007-01-08-22.19.33.800923 Instance:****** Node:000
PID:148604(db2med.84282.0) Appid:none
database_utilities sqluMapVend2MediaRCWithLog Probe:1

Error in Vendor Support Code at line: 983. rc: -50

2007-01-08-22.19.33.812355 Instance:****** Node:000
PID:148604(db2med.84282.0) Appid:none
database_utilities sqluMCWriteToDevice Probe:50

Media controller -- problem writing to vendor device. rc = -2025

2007-01-08-22.19.33.832505 Instance:****** Node:000
PID:84282(db2agent (******)) Appid:*******.070108192217
database_utilities sqlubMWResponse Probe:5 Database:******

DiagData
ffff f817 2d35 30ff 5453 4d00 ....-50.TSM.
What is the cause for the above return codes: Which return code to
consider for troubleshooting as there are two entries RC:- 50 and RC:-
-2025....

Kindly throw some light on what is the issue and how to resolve this?

Thanks in advance,
vj_dba
The -2025 is an SQL-code, that you should be able to find in your DB2
Messages manual (probably as SQL2025x, where x is unknown to me).
The -50 is a TSM API-code, that can be found in the TSM Messages manual, in
the appendix containing API Return Codes.

I can recall getting the -50 about a year ago, can't recall the SQL-code
though.
In our case it was caused by the fact that our DB2-server was unable to
connect to the TSM-server, either because it was down or because it was busy
servicing other (non-DB2)-servers or something alike.

Being at home right now, I have no system or docs at hand, except for ....
the TSM Messages manual I apparently downloaded at home when we were having
our problems with TSM.

Here's wat is says about the -50 return code:

-----------------------------------------------------
-050 E DSM_RC_TCPIP_FAILURE
Explanation: An attempt to connect to the server
using TCP/IP communications failed. This error can
occur if the LAN connection went down or if your
system administrator canceled a backup operation.
System Action: Session rejected. Processing stopped.
User Response: Retry the operation, or wait until the
server comes back up and retry the operation. If the
problem continues, see your system administrator for
further help.
-----------------------------------------------------

HTH.

--
Jeroen
Feb 15 '07 #3

P: n/a
vi******@gmail.com wrote:
Hi Group,

I'm running DB2 UDB Enterprise Edition V7.1 in AIX 4.3.3.0. And
database backups goes to the TSM server. We have the following TSM
Client API installed in the server:

tivoli.tsm.client.api.aix43.32bit 5.1.6.0 C TSM Client -
Application Programming Interface

Now my backup getting terminated with the following message in the
db2diag.log:

2007-01-08-22.19.33.800923 Instance:****** Node:000
PID:148604(db2med.84282.0) Appid:none
database_utilities sqluMapVend2MediaRCWithLog Probe:1

Error in Vendor Support Code at line: 983. rc: -50

2007-01-08-22.19.33.812355 Instance:****** Node:000
PID:148604(db2med.84282.0) Appid:none
database_utilities sqluMCWriteToDevice Probe:50

Media controller -- problem writing to vendor device. rc = -2025

2007-01-08-22.19.33.832505 Instance:****** Node:000
PID:84282(db2agent (******)) Appid:*******.070108192217
database_utilities sqlubMWResponse Probe:5 Database:******

DiagData
ffff f817 2d35 30ff 5453 4d00 ....-50.TSM.
What is the cause for the above return codes: Which return code to
consider for troubleshooting as there are two entries RC:- 50 and RC:-
-2025....

Kindly throw some light on what is the issue and how to resolve this?

Thanks in advance,
vj_dba
Actually I think you may find the -2025 is also a TSM error code :-

The only way I can find to get the meaning of these is the dsmrc.h file
within the TSM client install.

#define DSM_RC_INVALID_MCNAME -2025 /* Mgmt class name not found */

So I would suggest that the dsm.sys and dsm.opt files you have (or the
definition in DBM CFG if you have them) are not pointing at a known
management class on the TSM server ?

Phil
Feb 17 '07 #4

P: n/a
On 17 Feb., 21:49, Philip Nelson <team...@scotdb.comwrote:
vijay...@gmail.com wrote:
Hi Group,
I'm running DB2 UDB Enterprise Edition V7.1 in AIX 4.3.3.0. And
database backups goes to the TSM server. We have the following TSM
Client API installed in the server:
tivoli.tsm.client.api.aix43.32bit 5.1.6.0 C TSM Client -
Application Programming Interface
Now my backup getting terminated with the following message in the
db2diag.log:
2007-01-08-22.19.33.800923 Instance:****** Node:000
PID:148604(db2med.84282.0) Appid:none
database_utilities sqluMapVend2MediaRCWithLog Probe:1
Error in Vendor Support Code at line: 983. rc: -50
2007-01-08-22.19.33.812355 Instance:****** Node:000
PID:148604(db2med.84282.0) Appid:none
database_utilities sqluMCWriteToDevice Probe:50
Media controller -- problem writing to vendor device. rc = -2025
2007-01-08-22.19.33.832505 Instance:****** Node:000
PID:84282(db2agent (******)) Appid:*******.070108192217
database_utilities sqlubMWResponse Probe:5 Database:******
DiagData
ffff f817 2d35 30ff 5453 4d00 ....-50.TSM.
What is the cause for the above return codes: Which return code to
consider for troubleshooting as there are two entries RC:- 50 and RC:-
-2025....
Kindly throw some light on what is the issue and how to resolve this?
Thanks in advance,
vj_dba

Actually I think you may find the -2025 is also a TSM error code :-

The only way I can find to get the meaning of these is the dsmrc.h file
within the TSM client install.

#define DSM_RC_INVALID_MCNAME -2025 /* Mgmt class name not found */

So I would suggest that the dsm.sys and dsm.opt files you have (or the
definition in DBM CFG if you have them) are not pointing at a known
management class on the TSM server ?

Phil
TSM rc -2025 also comes up when a TSM storage pool is full. Have a
look at the TSM ativity log when this error happens. TSM will tell you
there if it is a space problem.

HTH
Joachim

Feb 19 '07 #5

P: n/a
On Feb 15, 10:38 pm, "The Boss" <use...@No.Spam.Please.invalidwrote:
vijay...@gmail.com wrote:
Hi Group,
I'm running DB2 UDB Enterprise Edition V7.1 in AIX 4.3.3.0. And
database backups goes to the TSM server. We have the following TSM
Client API installed in the server:
tivoli.tsm.client.api.aix43.32bit 5.1.6.0 C TSM Client -
Application Programming Interface
Now my backup getting terminated with the following message in the
db2diag.log:
2007-01-08-22.19.33.800923 Instance:****** Node:000
PID:148604(db2med.84282.0) Appid:none
database_utilities sqluMapVend2MediaRCWithLog Probe:1
Error in Vendor Support Code at line: 983. rc: -50
2007-01-08-22.19.33.812355 Instance:****** Node:000
PID:148604(db2med.84282.0) Appid:none
database_utilities sqluMCWriteToDevice Probe:50
Media controller -- problem writing to vendor device. rc = -2025
2007-01-08-22.19.33.832505 Instance:****** Node:000
PID:84282(db2agent (******)) Appid:*******.070108192217
database_utilities sqlubMWResponse Probe:5 Database:******
DiagData
ffff f817 2d35 30ff 5453 4d00 ....-50.TSM.
What is the cause for the above return codes: Which return code to
consider for troubleshooting as there are two entries RC:- 50 and RC:-
-2025....
Kindly throw some light on what is the issue and how to resolve this?
Thanks in advance,
vj_dba

The -2025 is an SQL-code, that you should be able to find in your DB2
Messages manual (probably as SQL2025x, where x is unknown to me).
The -50 is a TSM API-code, that can be found in the TSM Messages manual, in
the appendix containing API Return Codes.

I can recall getting the -50 about a year ago, can't recall the SQL-code
though.
In our case it was caused by the fact that our DB2-server was unable to
connect to the TSM-server, either because it was down or because it was busy
servicing other (non-DB2)-servers or something alike.

Being at home right now, I have no system or docs at hand, except for ....
the TSM Messages manual I apparently downloaded at home when we were having
our problems with TSM.

Here's wat is says about the -50 return code:

-----------------------------------------------------
-050 E DSM_RC_TCPIP_FAILURE
Explanation: An attempt to connect to the server
using TCP/IP communications failed. This error can
occur if the LAN connection went down or if your
system administrator canceled a backup operation.
System Action: Session rejected. Processing stopped.
User Response: Retry the operation, or wait until the
server comes back up and retry the operation. If the
problem continues, see your system administrator for
further help.
-----------------------------------------------------

HTH.

--
Jeroen- Hide quoted text -

- Show quoted text -
Hi..

Thanks for the reply, it's very informative..have a query again..my
TSM admin said it's a TIMEOUT Error..is it so? or it's a TCP/IP
communication error..

Thanks
vj_dba

Feb 20 '07 #6

This discussion thread is closed

Replies have been disabled for this discussion.