TDP ERP DB2 restore fails SQL2062N RC:18

AjM

ADSM.ORG Member
Joined
Jan 19, 2009
Messages
135
Reaction score
2
Points
0
Location
Mexico
Hello,

Im setting up new backups on sap servers with tdp erp db2 6.3 on linux, after succesfull backup with tdp erp backom tool, tried a restore but it fails with this code. DB2 starts creating db structure but after that it fails.

Command run with db2sid user
Code:
backom -c r_db -a PRD -b 1024 -B 2 -S 1 -P 2 -e /opt/tivoli/tsm/tdp_r3/initPRD.utl
[B]SQL2062N  An error occurred while accessing media "VENDOR".  Reason code:"18".[/B]
[B]SQL2008N  The utility command could not be processed because the callerac
parameter is not within valid range or the requested action is out ofsequence.[/B]
BKI8548I: Elapsed time: 9 min 26 sec
BKI8618E: Restore command failed due to an error.
BKI8512I: Return code is: 300


backom.log
Code:
BKI8806I: Data Protection for SAP(R) - BackOM 6.3.0.0 (475X) Sep 22 2011
BKI2027I: Using TSM-API version 6.3.0.0 (compiled with 5.5.0.0).
BKI8652I: DB2 version 'SQL09076' with 64 bits detected.
BKI8511I: The command is: -c r_db -a PRD -b 1024 -B 2 -S 1 -P 2 -e /opt/tivoli/tsm/tdp_r3/initPRD.utl
BKI8541I: Using profile '/opt/tivoli/tsm/tdp_r3/initPRD.utl'.
BKI8540I: Using ProLE at sapprd:tdpr3db264
BKI8543I: Querying TSM for file(s) '?*-PRD-NODE????-??????????????.tdi'.
BKI8543I: Querying TSM for file(s) '?*.PRD.?.NODE????.??????????????.?*'.
BKI8610I: Restoring database backup ...
BKI8643I: Using vendor library at '/opt/tivoli/tsm/tdp_r3/db264/libtdpdb264.so' ...
BKI8640I: Using 2 buffers with a size of 1024 ...
BKI8641I: Using 1 session(s) ...
BKI8642I: Using a degree of parallelism of 2 ...
SQL2062N  An error occurred while accessing media "VENDOR".  Reason code:
"18".
SQL2008N  The utility command could not be processed because the callerac
parameter is not within valid range or the requested action is out of
sequence.
BKI8548I: Elapsed time: 9 min 26 sec
BKI8618E: Restore command failed due to an error.
BKI8512I: Return code is: 300


tdpdb2.PRD.NODE0000.log
Code:
BKI8806I: Data Protection for SAP(R) 6.3.0.0 (475X) Sep 22 2011
BKI2027I: Using TSM-API version 6.3.0.0 (compiled with 5.5.0.0).
BKI8816I: DB2 version 'SQL09076' detected.
BKI8800I: The command is: RESTORE
BKI8801I: Time: 2013-01-19-10.37.47.0994 --- PID: 29096
BKI8822I: Configuration parameter(s):
            TDP_DIR=/opt/tivoli/tsm/tdp_r3/tdplog
            XINT_PROFILE=/opt/tivoli/tsm/tdp_r3/initPRD.utl
            CALLER=BACKOM
BKI8814I: Inquired TSM with mask '*.PRD.*.NODE0000.20130117174641.*'.
BKI8802I: Found 1 database image(s) on TSM server.
BKI7049I: The default for environment variable PROLE_PORT will be used.
BKI5016I: Time: 01/19/2013 10:38:02 AM New TSM session created: MGMNT-CLASS: , TSM-Server: TSMxxxx, type: SIMPLE
BKI5010E: Tivoli Storage Manager Error:
ANS1017E (RC-50)  Session rejected: TCP/IP connection failure
(rc=-50).
BKI8810I: Cleaning up resources of process 29096'.

Please advise
Regards
 
Last edited:
It looks like the client lost connection to the TSM server. I've seen the "Vendor: Reason Code 18" when running backups are killed either manually or a higher priority process prempts it.

Assuming that network is ok, TSM is up and basic connectivity is ok, I would search the TSM activity log at the time the restore process stopped. You may find more info there.
 
Hi, AjM,

Recenly I have deployed the TSM ERP(DB2) for my customer.

#1, For this file '/opt/tivoli/tsm/tdp_r3/initPRD.utl', please confirm the server_a stanza's nodename and other configration is right.

#2, /opt/tivoli/tsm/api/bin64/dsm.sys, please confirm this file's ip and nodename is right.

#3, /opt/tivoli/tsm/tdp_r3/db264/backom -c password, have you confirm the password setting is OK?
 
It looks like the client lost connection to the TSM server. I've seen the "Vendor: Reason Code 18" when running backups are killed either manually or a higher priority process prempts it.

Assuming that network is ok, TSM is up and basic connectivity is ok, I would search the TSM activity log at the time the restore process stopped. You may find more info there.

I can restore logs using backom and db2 cmd loading tdp library,
I have a PMR with IBM, they asked for actlog and q opt.
 
Hi, AjM,

Recenly I have deployed the TSM ERP(DB2) for my customer.

#1, For this file '/opt/tivoli/tsm/tdp_r3/initPRD.utl', please confirm the server_a stanza's nodename and other configration is right.

#2, /opt/tivoli/tsm/api/bin64/dsm.sys, please confirm this file's ip and nodename is right.

#3, /opt/tivoli/tsm/tdp_r3/db264/backom -c password, have you confirm the password setting is OK?

All config files are fine, logs restore works fine with backom and db2 cmds loading shared library

DB full database restore fails with that code, I guess after database is prepared by db2 on filesystems, you can see them grow
 
Return code 18 from TSM API stands for:

DSM_RS_ABORT_NO_MEMORY 18
Verify if there is enough memory available on server where are you performing the restore and/or settings of ulimit (ulimit -a to see actual settings). Try monitoring memory usage after you start the restore.
 
Back
Top