• Please help support our sponsors by considering their products and services.
    Our sponsors enable us to serve you with this high-speed Internet connection and fast webservers you are currently using at ADSM.ORG.
    They support this free flow of information and knowledge exchange service at no cost to you.

    Please welcome our latest sponsor Tectrade . We can show our appreciation by learning more about Tectrade Solutions
  • Community Tip: Please Give Thanks to Those Sharing Their Knowledge.

    If you receive helpful answer on this forum, please show thanks to the poster by clicking "LIKE" link for the answer that you found helpful.

  • Community Tip: Forum Rules (PLEASE CLICK HERE TO READ BEFORE POSTING)

    Click the link above to access ADSM.ORG Acceptable Use Policy and forum rules which should be observed when using this website. Violators may be banned from this website. This notice will disappear after you have made at least 3 posts.

DB2 Backup Issue - SQL2033N return code 406

c.j.hund

ADSM.ORG Member
#1
Hello all,

I'm having an issue backing up a database after a full system recovery. The TSM client version I'm using after the rebuild is 6.4.2.1. I'm actually not sure which TSM client was in use before the full recovery. Different client versions could end up being part of the problem I'm having here. Not sure.

When I run my backup I get the following:

db2 backup db FOO online use tsm
SQL2033N An error occurred while accessing TSM during the processing of a

database utility. TSM reason code: "406".

In my dsmerror.log file, I find the following:
'/usr/tivoli/tsm/client/api/bin/ww00adm.opt' could not be found, or it cannot be read.

Neither that directory not that ww00adm.opt file exist on this new rebuilt server (it's a 64bit installation), and the settings in my db2 user's .profile are set correctly:

export DSMI_DIR=/usr/tivoli/tsm/client/api/bin64
export DSMI_CONFIG=/usr/tivoli/tsm/client/api/bin64/dsm.opt

SERVER:/ww00util/ww00adm >echo $DSMI_CONFIG
/usr/tivoli/tsm/client/api/bin64/dsm.opt

Even though those variables are set correctly, the backup is still trying to find a .opt file that doesn't exist. I do not know where it is pulling this setting from. I suspect this ww00adm.opt file was in use prior to the server being rebuilt. To perhaps complicate the issue, the server was renamed when it was rebuilt ... although the TSM node names are the same.

A "db2adult query full" works, however. I'm able to pull up the existing full backups for the FOO database, but I'm not able to start a new backup.

Sincere thanks for any pointers,
C.J.
 

marclant

ADSM.ORG Moderator
#5
That's a different issue than the original poster, I see you opened another thread for this, so let's leave this one alone.
 

Advertise at ADSM.ORG

If you are reading this, so are your potential customer. Advertise at ADSM.ORG right now.

UpCloud high performance VPS at $5/month

Get started with $25 in credits on Cloud Servers. You must use link below to receive the credit. Use the promo to get upto 5 month of FREE Linux VPS.

The Spectrum Protect TLA (Three-Letter Acronym): ISP or something else?

  • Every product needs a TLA, Let's call it ISP (IBM Spectrum Protect).

    Votes: 18 18.4%
  • Keep using TSM for Spectrum Protect.

    Votes: 60 61.2%
  • Let's be formal and just say Spectrum Protect

    Votes: 12 12.2%
  • Other (please comement)

    Votes: 8 8.2%

Forum statistics

Threads
31,685
Messages
135,065
Members
21,703
Latest member
agent0810
Top