Tsm Error 406
Reason code: "406". System Action: The TSM client ends. If you are using the C shell then the commands are setenv, not export. Defining client nodes at the TSM server You will already have a TSM client defined on TSM1 to do the file level backups for QPRD10 and that will be scheduled as
Register Help Remember Me? The process will differ on other platforms. 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 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 https://adsm.org/forum/index.php?threads/db2-tsm-backup-error-reason-code-406.12468/
Environment Setup Failed: (406) No Default User Configuration File.
If you don't know what your DB2 instance is called, take a look in db2home and pick the one that was updated most recently. Solution - get the filespace mount changed. The archive log can be found in - /db2home/instance_name/sqllib/db2dump/db2diag.log DB2 LAN free backup considerations See the LAN free section for a general description of LAN free backups. 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
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 The backup data must be sent to a management class that is LAN free capable and this must be defined for every type of backup object. A DB2 restart will be needed to pick the changes up. User Response: See if you have the environment variable DSM_CONFIG (or DSMI_CONFIG for the API) set, which explicitly identifies the TSM options file. ( You can do this by entering the
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 Tsm Reason Code 106 Otherwise, try ps -ef |fgrep -i db2sysc to see what instances are active. TSM will create these using the root userid so you must change the access to the files so DB2 can update them. 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.
All Rights Reserved. Define your QPRD10_DB2 client to the TSM1 server with the DB2 policy set. 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. Reason code: "406".
Tsm Reason Code 106
However, sometimes we seem to get this error when everything is set up correctly. Scheduling First, you need to define a different dsmcad for DB2 to allow you to pick up the DB2 option file. Environment Setup Failed: (406) No Default User Configuration File. You would do this using a TSM command like the one below, with suitable names that fit your site's conventions. This lets DB2 manage backup retention.
As far as I know, the path below is not site specific but is the DB2 installation default. 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 There is usually nothing on either the TSM server or the TSM client logs to indicate that archiving is working, and usually no error messages if it fails. 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.
If neither of these cases is met, you receive this error message. You will need a DB2 policy set and management class, with a backup copy group with the parms set to 1,0,0,0. If you use the default management class for your archive copy group, then the ': mgmtclass_name' parameter is not required. DB2 must also be able to read its dsm.opt file and the dsm.sys file.
Some common problems DB2 Script Make sure your DB2 backup script is set as executable (chmod 755 is usually considered appropriate). There will be an archive log for every DB2 instance on each server. These are DSMI_DIR, DSMI_CONFIG and DSMI_LOG.
This is an IBM product for use in conjunction with OnDemand product.
This page discusses DB2 backups on AIX clients. You need to know the path and name of the DB2 backup script that has hopefully been defined by your DBA. Hope this helps, Bill Gallagher, DBA Phoenix Life Insurance Enfield, CT 06083 IBM Certified Solutions Expert - DB2 UDB v7.1 Database Administration for OS/390 IBM Certified Solutions Expert - DB2 UDB select class_name,count(class_name) from archives where node_name='your_db2_nodename' group by class_name or select class_name,archive_date from archives where node_name='your_db2_nodename' A more direct way is to look at the DB2 archive log, if you
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 The "-c" means switch back to the root userid when the command completes. 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.
It's considered good practice to make all your TSM log files read/write to everyone with chmod 666. 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 The most common cause in my experience is that the environmental variables DSM_CONFIG, DSMI_CONFIG, and/or DSMI_DIR are not set correctly, or there is a file permissions problem in getting to the I am new to DB2 and to the admin portion of databases so any help on the above error message would be appreciated.
You will also need an archive copy group defined for the DB2 log archiving, which is scheduled and managed by DB2. The DB2 object names and paths are Object DB2 object name Full database recovery object /dbname/NODEnnnn/FULL_BACKUP.timestamp.seq_no Incremental database recovery object /dbname/NODEnnnn/DB_INCR_BACKUP.timestamp.seq_no Incremental delta database recovery object /dbname/NODEnnnn/DB_DELTA_BACKUP.timestamp.seq_no Full table space recovery 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) This makes DB2 backups a bit easier to configure and also means you don't need to buy a TDP licence.
db2 backup database portal1d use tsm SQL2062N An error occurred while accessing media "/database/dilmnc1p/sqllib/adsm/libtadsm.a". 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. You could let them default, but that makes debugging harder. 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.
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. For this to happen successfully you need to set archivedelete=yes on the client definition at the TSM server. 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.