V9.5 redirected restore problem\question

itsonlyme44 · #1 (**permalink**) 06-29-09, 12:31

DB2 on Windows Veriosn 9.5

I am just sruggling with this database restore!!

When I run it I get the error:
SET TABLESPACE CONTAINERS FOR 5 IGNORE ROLLFORWARD CONTAINER OPERATIONS USING (FILE "I:\DB2_02\NODE0000\SQL00003\SYSTOOLSPACE" 10192 )SQL0298N Bad container path. SQLSTATE=428B2

and I also get:
SQL0902C A system error (reason code = "242

Below are the LIST TABLESPACES DETAIL for the source and my restore script.

I've googled the error but don't really understand what the problem is.. can anyone help

List tablespaces detail (from source)

[CODE]Tablespace ID = 0
Name = SYSCATSPACE
Type = Database managed space
Number of containers = 1

Tablespace ID = 1
Name = TEMPSPACE1
Type = Database managed space
Number of containers = 1

Tablespace ID = 2
Name = USERSPACE1
Type = Database managed space
Number of containers = 1

Tablespace ID = 3
Name = INDSP16K
Number of containers = 1

Tablespace ID = 4
Name = INDSP32K
Type = Database managed space
Number of containers = 1

Tablespace ID = 5
Name = SYSTOOLSPACE
Type = Database managed space
Number of containers = 1

Tablespace ID = 6
Name = INDSP4K
Type = Database managed space
Number of containers = 1

Tablespace ID = 7
Name = TBLSP4K
Number of containers = 1

Tablespace ID = 8
Name = TBLSP16K
Type = Database managed space
Number of containers = 1

Tablespace ID = 9
Name = TBLSP32K
Type = Database managed space
Number of containers = 1

Tablespace ID = 10
Name = SYSTOOLSTMPSPACE
Type = System managed space
Contents = User Temporary data
Number of containers = 1

Tablespace ID = 11
Name = TEMPSPACE2
Type = System managed space
Contents = System Temporary data
Number of containers = 1

----
Restore SCript

Code:

RESTORE DATABASE PRODDM FROM "I:\ProdDMBackup" TO "G:" INTO DUTDM WITH 2 BUFFERS BUFFER 1024 REDIRECT PARALLELISM 1 WITHOUT PROMPTING;
SET TABLESPACE CONTAINERS FOR 0 IGNORE ROLLFORWARD CONTAINER OPERATIONS USING (FILE "G:\DB2_02\NODE0000\DUTDM\CONTAINERS\Catalog_tbsp" 1280000 );
SET TABLESPACE CONTAINERS FOR 1 IGNORE ROLLFORWARD CONTAINER OPERATIONS USING (FILE "G:\DB2_02\NODE0000\DUTDM\system_tbsp" 2560000 );
SET TABLESPACE CONTAINERS FOR 2 IGNORE ROLLFORWARD CONTAINER OPERATIONS USING (FILE "G:\DB2_02\NODE0000\DUTDM\CONTAINERS\USER_TBSP" 5632000 );
SET TABLESPACE CONTAINERS FOR 3 IGNORE ROLLFORWARD CONTAINER OPERATIONS USING (FILE "I:\DB2_02\NODE0000\DUTDM\Containers\INDSP16K_tbsp" 1280000 );
SET TABLESPACE CONTAINERS FOR 4 IGNORE ROLLFORWARD CONTAINER OPERATIONS USING (FILE "I:\DB2_02\NODE0000\DUTDM\Containers\INDSP32K_tbsp" 208000 );
SET TABLESPACE CONTAINERS FOR 5 IGNORE ROLLFORWARD CONTAINER OPERATIONS USING (FILE "I:\DB2_02\NODE0000\SQL00003\SYSTOOLSPACE" 10192 );
SET TABLESPACE CONTAINERS FOR 6 IGNORE ROLLFORWARD CONTAINER OPERATIONS USING (FILE "E:\DB2_02\NODE0000\DUTDM\Containers\INDSP4K_tbsp" 768000 );
SET TABLESPACE CONTAINERS FOR 7 IGNORE ROLLFORWARD CONTAINER OPERATIONS USING (FILE "E:\DB2_02\NODE0000\DUTDM\Containers\TBLSP4K_tbsp" 256000 );
SET TABLESPACE CONTAINERS FOR 8 IGNORE ROLLFORWARD CONTAINER OPERATIONS USING (FILE "I:\DB2_02\NODE0000\DUTDM\Containers\TBLSP16K_tbsp" 6272000 );
SET TABLESPACE CONTAINERS FOR 9 IGNORE ROLLFORWARD CONTAINER OPERATIONS USING (FILE "i:\DB2_02\NODE0000\DUTDM\Containers\TBLSP32K_tbsp" 320000 );
SET TABLESPACE CONTAINERS FOR 10 IGNORE ROLLFORWARD CONTAINER OPERATIONS USING (PATH "G:\DB2_02\NODE0000\DUTDM\Containers\SYSTOOL");
SET TABLESPACE CONTAINERS FOR 11 IGNORE ROLLFORWARD CONTAINER OPERATIONS USING (PATH "G:\DB2_02\NODE0000\DUTDM\Containers\SYSTEMP");
RESTORE DATABASE PRODDM CONTINUE;

Can anyone help me sort this out???

n_i · #2 (**permalink**) 06-29-09, 13:30

- what is in the Windows Event Viewer for SQL0902C?
- is this a local or a network drive (I

?
- does the DB2 service account account have permissions for that path?
- is this the only path that gives you an error?

itsonlyme44 · #3 (**permalink**) 06-29-09, 13:40

no errors in the Windows event viewer.
C: E: F: G: H: and I: are all locally attached Drives
I am logged onto the box as An administrator and using a DBA account to run the restore
I have tried paths G: and I: and I get the same error

ARWinner · #4 (**permalink**) 06-29-09, 14:06

Maybe the text of the error message will give you insight:

Code:

SQL0298N  Bad container path.

Explanation:

The container path violates one of the following requirements:
*  Container paths must be valid fully-qualified absolute paths or valid
   relative paths. The latter are interpreted relative to the database
   directory.
*  For EXTEND, REDUCE, RESIZE and DROP operations, the specified
   container path must exist.
*  The path must be read/write accessible to the instance id (check file
   permissions on UNIX-based systems).
*  Containers must be of the type specified in the command (directory,
   file or device).
*  Containers (directories) in system managed table spaces must be empty
   when designated as containers and must not be nested underneath other
   containers.
*  The containers for one database must not be located underneath the
   directory of another database, and they may not be underneath any
   directory that appears to be for another database. This rules out any
   directory of the form SQLnnnnn, where 'n' is any digit.
*  The container must be within the file size limit for the operating
   system.
*  Containers (files) for dropped database managed table spaces can only
   be reused as containers (directories) for system managed table spaces
   after all agents terminate and vice versa.
*  During a redirected restore, an SMS container was specified for a DMS
   table space or a DMS container was specified for an SMS table space.
*  The specified type of the container for an EXTEND, REDUCE, RESIZE, or
   DROP operation does not match the type of the container (FILE or
   DEVICE) that was specified when the container was created.

This message will also be returned if any other unexpected error
occurred which prevents DB2 from accessing the container.

If you are using a cluster manager, this error can be returned if the
DB2 database manager failed to add the database container path to the
cluster manager configuration. If the cluster manager cannot access this
path, the cluster manager will not be able to successfully manage a
failover involving this path. Error messages from the cluster manager
will be recorded in the db2diag.log file.

User response:

Specify another container location or change the container to make it
acceptable to DB2 (such as changing file permissions) and try again.

If you are using a cluster manager, correct the problem and resubmit the
command:

1. Review the db2diag.log file for error messages from the cluster
   manager.
2. Respond to the cluster manager error messages in the db2diag.log file
   to correct the underlying problem that prevented the DB2 database
   manager from adding the path to the cluster manager configuration.
3. Resubmit the command.

 sqlcode: -298

 sqlstate: 428B2

Andy

n_i · #5 (**permalink**) 06-29-09, 14:59

Quote:

Originally Posted by itsonlyme44

no errors in the Windows event viewer.
I am logged onto the box as An administrator and using a DBA account to run the restore

SQL902 must generate messages in the Windows Event Log and in db2diag.log. It would be best if you find them.

It does not matter how you are logged in; what matters is the account used to run the DB2 service. (Hint: try the Services control panel.)

itsonlyme44 · #6 (**permalink**) 06-29-09, 15:17

I have checked and rechecked the Application and System event logs and find no errors.

I am running all DB2 Service under 'local system' -

I fixed the 'bad container path error but I am still getting the 'SQL0902C A system error (reason code = "242")' error.

Beyond frustrated because this restore has worked every week once a week for quite some time now.. I can't reboot the box because I have about 20 developers working ....

db2girl · #7 (**permalink**) 06-29-09, 16:14

for sql0298n, check that the container path you're specifying is not in use by another tablespace/database (it has to be empty if it's not in use)

for RC=242, check if you have 0x870F00F2 (no resources to create process or thread) logged in the db2diag.log. If you see this error, check the following technote: IBM - Database marked bad with ZRC=0x870F00F2 on Windows

Resolution in this technote is to disable filesystem caching using the alter tablespace command. Example: db2 "alter tablespace userspace1 no file system caching"

If you don't see 0x870F00F2, check what errors are logged in the db2diag.log when restore fails with RC=242