DB2 Module Savesets

Question

I'm having trouble getting a working DB2 saveset entry. The client I'm at was unable to find the partition number for their node/instance so we can't finish the string. The db is local so as I understand it we use the db instance in place of the node, so the saveset string looks like -
DB2:/DBNAME/DBINSTANCExxxx
where xxxx is the partition

If that is correct (and the manuals seem to say it is), then how can I find the partition so I can complete the string?

If it isn't correct how can I find the correct info to build the string?

Thanks,

ble1 · Answer

Here is the reference:http://publib.boulder.ibm.com/infocenter/db2luw/v8/index.jsp?topic=/com.ibm.db2.udb.doc/core/r0001965.htmLIST ACTIVE DATABASES is also good.

ble1 · Answer

Try 'db2 list node directory'. DB2 admin should be able to help if it is around.

ble1 · Answer

Can you try first client initiated backup? More details can be obtained from log if you increase log level - see module documentation (you will need to set log file and level for both library and binary execution in CFG file). Error itself could be few thing from wrong node (but it seems to be ok according to what you have posted) to password of db2 user.

ct2msb · Answer

Ok, I ran the commands you suggested and I think was able to parse out the right info to put in the saveset string: db2:/dbname/node0000
Because the database lives in a directory that looks like /home/dbuser/dbname/node0000 ...

Now we're getting messages in /nsr/applogs/nsrdb2sv.log:

05/10/07 17:07:20 nsrdb2sv: *** NetWorker Module for DB2 backup session started (426236) ***
05/10/07 17:07:20 nsrdb2sv: Function libdb2api:ClientConnectionAttrisSet - Node Change returned error -1390.
05/10/07 17:07:20 nsrdb2sv: NMDB2_ERROR: Could not set communication to connect to node 0000

Is there anywhere to look for more detailed errors? or are we even using the right node?

ct2msb · Answer

We've tried a client side backup and now we're getting the following error:

SQL2062N An error occurred while accessing media "VENDOR". Reason code: -1

and over on the networker server we're getting:

Cannot write to /disk/xx/xx/xxxxxx-xxxxxx-xxxxxx-xxxxxx - errno=27

However the directory structure is owned by root and root has no trouble writing to it. I also checked the SQL messages in the admin guide, but reason code -1 isn't one of the reason codes listed in the guide.

Any ideas why we're seeing this?

ble1 · Answer

What OS is on storage node where disk device is? I believe you got SQL2062N due to errno=27 on storage node. If you check a bit you will find that error message indicates file system full or file bigger than 2GB (and some systems need to have option for support of file bigger than 2GB turned on manually). Most probably you (well, system admin) needs to turn on that option. (of course, I could be wrong).

NetWorker

DB2 Module Savesets

Was this post helpful?