ADSM-L

Re: ADSM API and DB2 backups

1999-04-14 09:26:58
Subject: Re: ADSM API and DB2 backups
From: John McConnell <jmcconnell AT FIRSTMD DOT COM>
Date: Wed, 14 Apr 1999 09:26:58 -0400
If you installed DB2 UDB you need to have at least fixpacks 6 & 7 installed to 
support ADSM backups.  There is a bug in DB2 V2 and DB2 V5 which prevents the 
DB2<->ADSM interface from working.

John McConnell
allfirst bank


______________________________ Reply Separator _________________________________
Subject: ADSM API and DB2 backups
Author:  MIME:michael.lightfoot AT CENTRELINK.GOV DOT AU at INTERNET
Date:    4/14/99 7:21 AM


I have just installed 3.1.0.6 client and API on a Solaris 2.5.1 system which 
has DB2 version 5.0.  We are testing DB2 backups using ADSM and are having 
problems.

When I run the command:

db2  backup db test_q use adsm

from a user set up with all the appropriate environment, I get the following 
error:

SQL2062N  An error occurred while accessing media 
"/export/home/db21s/sqllib/adsm/libadsm.a".  Reason code: "610".

Our DBAs tell me that the above DB2 error is DB2 reporting an ADSM error and 
that the reason code is the ADSM error code.  I looked up return code 610 in 
the ADSM API documentation (at 
http://www.storage.ibm.com/software/adsm/pubs/v3pubs/aix/html/adsmapi/cp5ec 
a.htm) and it says the following:

0610 E DSM_RC_NLS_CANT_OPEN_TXT

Explanation: The system is unable to open the message txt file (dscameng.txt or 
dsmclientV3.cat for AIX). On the AS/400 platform this
file
is QANSAPI/QAANSAMENG(TXT).

System Action: The system returns to the calling procedure.

User Response: Verify that the dscameng.txt file is in the directory
pointed
to by DSMI_DIR. For AIX, verify that the dsmclientV3.cat file has a symbolic 
link to /usr/lib/nls/msg/<locale>/dsmclientV3.cat .

I found the location of dsmclientV3.cat and symbolically linked it to the 
directory referenced by the DSMI_DIR environment variable.  Unfortunately this 
made absolutely no difference, I get precisely the same error.  I've checked 
permissions, checked that the DSMI_DIR variable is actually being referenced 
correctly, I've completely removed and reinstalled both packages (IBMadsm-c and 
IBMadsm-a), moved the DSMI_DIR directory to a different (more sensible) 
location (and changed the environment variable), and finally sworn foul oaths 
at the whole thing :-) to absolutely no avail.

Anyone have any ideas?



michael

Unix Consultant
Centrelink
Australia
<Prev in Thread] Current Thread [Next in Thread>