Reason code: "406". Otherwise you run it as the db2 user as shown in the second example below - your DBA will supply you with the correct username. If neither of these cases is met, you receive this error message. Client definitions The dsm.opt file You will already have a dsm.opt file for your standard backups, so you need to create another one called something like dsm_db2.opt which contains the following. More about the author
These are DSMI_DIR, DSMI_CONFIG and DSMI_LOG. DB2 must also be able to read its dsm.opt file and the dsm.sys file. Define your QPRD10_DB2 client to the TSM1 server with the DB2 policy set. To segregate the two, you need to define two TSM clients, one for backups, and one for archives. https://adsm.org/forum/index.php?threads/db2-tsm-backup-error-reason-code-406.12468/
For snapshots, use the db2acsutil utility located in sqllib/bin. One way to check the variables is to use the command env |grep DSMI Another way is to use the 'set' command. export DSMI_DIR=/usr/tivoli/tsm/client/opt/bin64 export DSMI_LOG=/path to your log files export DSMI_CONFIG=/usr/tivoli/tsm/client/ba/bin64/dsm_db2.opt File permissions The TSM1_QPRD10_DB2 stanza in the example above has two log files, /path/tsm.db2.dsmerror.log and /path/tsm.b2.dsmsched.log where /path is the path
Assuming the script is in /usr/local/scripts/db2backup.ksh, the command is something like /usr/local/scripts/db2backup.ksh or su - db2user -c "/usr/local/scripts/db2backup.ksh" In the second example, the '-' means run the command as db2user Solution - get the filespace mount changed. LAN-free will speed up backups of DB2 databases, but is not suitable for smaller files like archive logs. DEFINE COPYGROUP domain_name policyset_name mgmtclass_name TYPE=ARCHIVE DESTINATION=archive_stgpool_name RETVER=NOLIMIT IBM recommends that you make archive logs go to a different storage pool that the DB2 database backups.
If the variables are missing you need to set them with the export command, and add them to the .profile dataset for that userid. Tsm Reason Code 106 Alternatively, you can just check the archive dates. You also need to know if your DBA has included "su db2user" commands inside the script, in which case you run the command as root. https://www.ibm.com/support/knowledgecenter/SSEPGG_9.8.0/com.ibm.db2.luw.messages.sql.doc/doc/msql02033n.html From the "Tivoli Storage Manager Messages Manual": 0406 DSM_RC_NO_OPT_FILE S Explanation: The options file specified by file-name cannot be found.
DB2 Archving DB2 copies its archive logs off to TSM using the API, and as this is not controlled by TSM it is quite difficult to work out what is happening. For this to happen successfully you need to set archivedelete=yes on the client definition at the TSM server. To check to see if these variables are set, you need to log onto the AIX server with the db2 userid, lets call it db2user, or sudo to it from the Register Help Remember Me?
Configuring the Backups For the sake of simplifying the text, this section assumes that you are going to define a DB2 backup on an AIX server called QPRD10, running on a http://www.lascon.co.uk/tsm-and-db2.php Substitute your own paths and filenames echo "/usr/tivoli/tsm/client/ba/bin64/dsmcad_db2 -optfile=/usr/tivoli/tsm/client/ba/bin64/dsm_db2.opt" |at now You will also need symbolic links in the API directory, usually /usr/tivoli/tsm/client/api/bin64 to point to the dsm.sys and dsm.opt files Environment Setup Failed: (406) No Default User Configuration File. The problem was that the filespace that was mounted with the nosuid parameter set, which meant that password worked for root only. Lascon Storage Contact us Home Backup and DR Hardware Mainframe Open Systems Databases Strategy FDRABR TSM Snapshot Backups Instant Backup Remote Mirroring Backing up DB2 on AIX with TSM Unlike the
If you define unique log names for the DB2 stanza then that separates out the DB2 messages from the standard client and again it makes debugging easier. We logged on as root and tried running the command arssycscr -d (as stated in documentation) and received this error DB Error: STARTUP -- SQLSTATE=HENV=0, SQLCODE=-1 The Database was up and Corresponding TSM include statements are include /*/NODE????/FULL_BACKUP.* LANFREE_MC include /*/NODE????/DB_INCR_BACKUP.* LANFREE_MC include /*/NODE????/DB_DELTA_BACKUP.* LANFREE_MC include /*/NODE????/TSP_BACKUP.* LANFREE_MC include /*/NODE????/TSP_INCR_BACKUP.* LANFREE_MC include /*/NODE????/TSP_DELTA_BACKUP.* LANFREE_MC If you use TSM to store your DB2 However, sometimes we seem to get this error when everything is set up correctly.
Some common problems DB2 Script Make sure your DB2 backup script is set as executable (chmod 755 is usually considered appropriate). You also need to tell DB2 to use the TSM interface, and while this would normally be done by your DBA, for completeness. You will need a DB2 policy set and management class, with a backup copy group with the parms set to 1,0,0,0. http://odenews.net/tsm-error/ans1314e-rc14-file-data-currently-unavailable-on-server.html There are at least three possible solutions you have not allocated the dsm.opt file There is no symbolic link from the api directory to the ba directory LoginRequest LoginToggle navigation
If you use the default management class for your archive copy group, then the ': mgmtclass_name' parameter is not required. You can't use that for DB2, simply because you have to schedule a command or script for DB2, so you need a different client. DB2 environment variables The API uses three environment variables to point DB2 to the right locations for the TSM parameters.
System Action: The TSM client ends. Recent releases of DB2, certainly from DB2 9.7 onwards, have several types of object, and the backups of eacjh object must be directed to a LAN free management class. TSM will create these using the root userid so you must change the access to the files so DB2 can update them. In general you do not want just anyone to be able to update these files, so owner write and everyone else read; or chmod 644 is considered appropriate.
Reason code: "406". You need to define an archive copygroup in the DB2 management class, otherwise archiving will fail. Bill Gallagher Re: DB2 UDB 7.2 & TSM Error Message March 13, 2002 04:35 PM (in response to Paul Dobbratz) Paul, This is an error message that I have come to You need to know the path and name of the DB2 backup script that has hopefully been defined by your DBA.
You will also need an archive copy group defined for the DB2 log archiving, which is scheduled and managed by DB2. If you miss this out you will see the environment variables for root. This lets DB2 manage backup retention. This is an IBM product for use in conjunction with OnDemand product.
The webports must be unique and are used for communication with the dsmcad. Use a command something like this ln -s /usr/tivoli/tsm/client/ba/bin64/dsmcad dsmcad_db2 Now you need to start your dsmcad up, so you use a command like this. su - db2user Note the '-' in the middle. As far as I know, the path below is not site specific but is the DB2 installation default.
Mark Maziarczyk Error Message April 3, 2002 12:37 PM (in response to Bill Gallagher) Don't know if anyone can help me solve this one but we were trying to install (PDD) DB2 errors RC 406 If the backup is not working but there is nothing in the tsm logs then you need to look at the DB2 logs. These are very wordy and difficult to decipher, an example is If you can find a DB2 API guide and look up RC=11 it just tells you that DB2 has had So what you need to do is create a TSM client which we'll call QPRD10_DB2.
thanks in advance mark International DB2 Users Group 330 North Wabash, Suite 2000 | Chicago, IL 60611-4267 Phone: (312) 321-6881 | Fax: (312) 673-6688 Copyright © 2016 IDUG. If it is not set, then TSM looks for the file dsm.opt in the current directory. Within this file, add an extra stanza below the one that manages your standard backups, so your dsm.sys file looks something like The two node names must match the nodes defined Note that you specify RETVER=NOLIMIT, as the deletion of expired archives is controlled by DB2.
If it is not executable you will get a error message like "Scheduled Event 'xxxxx' failed return code 126." TSM server password not set If you don't set the TSM password The process will differ on other platforms. If the number of archived objects is changing then that indicates that archiving is happening.