Unsolved

This post is more than 5 years old

2 Intern

 • 

161 Posts

4226

October 6th, 2014 07:00

Backing up DB2 with NetWorker for beginners

Hey guys,

I need to backup a DB2 database with networker. I'm not much of a DBA, so this is kind of challenging.

I run networker 8.0 on server and client side. NMDA 1.2 is also installed on the client. As I can say the DB2 database is running version 10.

I thought I just install networker and NMDA on the client side and the rest is done by the networker client wizard. As I leant that is not the way it is gonna work. The client wizard just gives me the option to backup the filesystem.

I did read the DB2 section in the installation and administration guide of the NMDA module which actually helped not so much.

Do I need to set a link like in an Oracle environment?

What do I need to put in the NMDA config file? Is the db alias enough?

I would really appreciate some help.

Cheers

Jan

2 Intern

 • 

161 Posts

October 8th, 2014 23:00

Thank you!

Registering the wizard manually worked for me although I'm pretty sure I tried it before:

/usr/sbin/nsrdb2ra -i

2 Intern

 • 

161 Posts

October 9th, 2014 06:00

I got "nsrdb2ra -i" to work. I needed to edit the servers-file and restart networker. Although I had done that after the installation of the networker client.


Anyway, I now can use the client wizard to configure the client ressource. I can choose the db2 instance and the specific database within the wizard. I wanna do an offline backup of one of the few databases we got.

Networker throws the message:

Backing up the 'SAMPLE' database.

Unable to backup SAMPLE database due to backup request failure, SQLCODE : -1035, SQL1035N  The operation failed because the specified database cannot be connected to in the mode requested.  SQLSTATE=57019

SQLSTATE 57019: The statement was not successful, because of a problem with a resource.

NMDA backup failed.

64673:nsrdasv: Unable to backup SAMPLE database due to backup request failure, SQLCODE : -1035, SQL1035N  The operation failed because the specified database cannot be connected to in the mode requested.  SQLSTATE=57019

SQLSTATE 57019: The statement was not successful, because of a problem with a resource.

Unfortunately I have no idea what that means

6 Operator

 • 

14.4K Posts

 • 

56.2K Points

October 9th, 2014 07:00

New problem should be - new thread   Here is the hint:

SQL1035N The database is currently in use.

Explanation:

One of the following conditions exists:

o Exclusive use was requested, but the database is already in use as a shared database by another user (in the same process).

o Exclusive use was requested, but the database is already in use as an exclusive database. (Two different processes are trying to access the same database.)

o The maximum number of connections to the database has been reached.

o The database is being used by another user on another system.

o Activate/Deactivate database is in progress. The command cannot be processed.

User Response:

Possible solutions include:

o Resubmit the command later when the database is not in use.

o Change the authorization to match the current user or wait until the database is not in use.

o Wait until the database is not in exclusive use.

o Wait until other users on another system have disconnected from the database.

sqlcode : -1035

sqlstate : 57019

No Events found!

Top