Below is the text of info APAR II10103, which provides a series of hints and
tips for configuring DB2/6000 to work with ADSM. I hope you find it helpful.
Andy Raibeck
ADSM Level 2 Support
-------------------
ERROR DESCRIPTION:
ERROR DESCRIPTION:
This INFO APAR was created to document some hints and tips for
configuring the ADSM API for use with DB2/6000.
1) Verify that the ADSM API environment variables are configured
correctly. Here is an example of how to set them up in the
instance name's .profile file:
export DSMI_DIR=/usr/lpp/adsm/bin
export DSMI_CONFIG=/usr/lpp/adsm/bin/dsm.opt
export DSMI_LOG=$HOME/sqllib/adsm
Note that DSMI_CONFIG must point to the options file itself,
not just the directory.
DSMI_LOG is where dsierror.log will be written.
'$HOME/sqllib/adsm' is just a suggestion... use whatever
directory you want, as long as the instance name has write
permission to the directory.
2) Install the 2.1.0.5 client if you already haven't done so.
(Note that 2.1.0.5 was the latest client level at the time
of this writing, and should be considered the *minimal*
level.)
3) DB2 used to install a copy of the API. It is an old copy and
must be removed.
a) In $HOME/sqllib/adsm look for 'dsmtca' and
'libApiDS.a'. These are older versions of the API and
should be removed (or renamed to *.old).
NOTE: The API no longer uses the 'dsmtca' file. Rather,
it uses 'dsmapitca', which is located in
/usr/lpp/adsm/bin (or wherever the DSMI_DIR
environment variable points to).
b) There should be ONE and ONLY ONE symbolic link in the
configuration, and that is for 'libApiDS.a'. If it is
not already in there, cd to '/usr/lib' and create the
link:
ln -s /usr/lpp/adsm/api/bin/libApiDS.a
Scan the $HOME/sqllib directory and subdirectories for
any other instances of 'libApiDS.a' and 'dsmtca' and
make sure they are gone. Also check any other DB2
installation directories for these files or symbolic
links. Another directory worth checking is
/usr/lpp/db2_02_01, as well as its subdirectories. If
in doubt, you can scan the /usr filesystem for all
occurrences of 'libApiDS.a' and 'dsmtca' with the Unix
"find" command:
find /usr -name libApiDS.a -print
find /usr -name dsmtca -print
A more thorough, though longer-running approach is to
scan *all* file systems for these files:
find / -name libApiDS.a -print
find / -name dsmtca -print
IMPORTANT: The main points here are that there must be
only TWO references to 'libApiDS.a' in the
DB2 instance name's search path:
/usr/lib/libApiDS.a
/usr/lpp/adsm/api/bin/libApiDS.a
The one in /usr/lib must be a symbolic link
to the actual file in /usr/lpp/adsm/api/bin.
4) PASSWORDACCESS GENERATE must be set. If your other ADSM
clients do not use this option, create another SERVERNAME
stanza in dsm.sys and code PASSWORDACCESS GENERATE. Then
create a special dsm.opt file (pointed to by DSMI_CONFIG)
that has:
SERVERNAME whatever <== the servername in the new
dsm.sys stanza
Please note that PASSWORDACCESS GENERATE will not work if
NODENAME is specified in dsm.opt. Either use the machine's
hostname as the node name, or code NODENAME in dsm.sys.
5) Make sure you can run the 'dsmapipw' and 'adsmqry' programs.
If they are working, then everything should be all set.
Note that you must be the root user to run 'dsmapipw'.
6) If you still can not run 'db2 backup', then check:
a) Have you restarted the DB2 database engine since
updating the DSMI_DIR, DSMI_CONFIG, and DSMI_LOG
environment variables in .profile?
b) How are you actually starting DB2? Do you issue
'db2start' from the AIX command line? If you are
running 'db2start' from a script, then most likely the
environment variables are being lost. To test this,
shut down DB2, and start it from the command line in
the background. Then try 'db2 backup'. Does it work?
7) Make sure that everyone has 'read' access to the dsm.sys and
dsm.opt files.
8) Make sure that the /usr/lpp/adsm/bin/dsmapitca has the 's'
bit set. Use the command 'chmod u+s dsmapitca' to set it, if
necessary. Permissions should be '-rwsr-xr-x'. 'root' must be
the owner.
9) Make sure that dsm.opt has TAPEPROMPT NO.
---------------------- Forwarded by Andrew Raibeck/San Jose/IBM on 05-23-97
05:20 AM ---------------------------
05:20 AM ---------------------------
ADSM-L @ VM.MARIST.EDU
05-22-97 10:46 PM
Please respond to ADSM-L AT VM.MARIST DOT EDU @ internet
To: ADSM-L @ VM.MARIST.EDU @ internet
cc:
Subject: DB2 Backup to ADSM
I have been getting SQL2025N error message with a return code "9" (bad file
descriptor) when backing up DB2 database to ADSM using DB2 Backup. We're
running DB2 v2.1 and ADSM Client 2.1.02. I'm not sure how to configure so that
DB2 talks to ADSM. The latest instructions I have on configuration is for ADSM
Client 2.1.00 where the file dscameng.txt file exists but with Level 2.1.02,
that file doesn't exist but a new directory en_US is located in
/usr/lpp/adsm/bin. Can anyone show me how to configure DB2 with ADSM.
Role: Unix System Administrator
Style: The Thinking Man's Clown
Name: wayneg AT au1.ibm DOT com
Life: "Imagination is more important than knowledge" Albert Einstein
|
