By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
443,694 Members | 1,846 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 443,694 IT Pros & Developers. It's quick & easy.

Tablespace containers not accessible

P: 2
Hello,
I had created the backup of my Production DB2 database on Dev and It was working fine.
However, we decided to updated the Dev Db with a latest version of the Prod and for that I copied over the folder which has my table spaces e.g. F:/ABCD to the DEV m/c at D:/ABCD.
I am not able to query the DB after that and the error message I get it error:
SQL0290N Table space access is not allowed. SQLSTATE=55039

I checked with list tablespace containers for <tablsespace ID> on the Dev DB.
The location where the table space containers are still pointing to the Prod DB path , e.g. on F:/ and not on D:/ .
I tried to change the table space containers path set tablespace containers for 1 using (path 'd:\ABCD\TEMP_PLGO_TABSPA1'), but it is not getting accessed yet.
I am still getting the error as SQL0290N Table space access is not allowed. SQLSTATE=55039

SOmeone please suggest what I can do . I am stuck as to how the container path can be changed.

Please respond.
Jul 31 '08 #1
Share this Question
Share on Google+
3 Replies


docdiesel
Expert 100+
P: 297
Hi,

maybe this way of db transfer is working sometimes, but I guess the words an IBM expert would use are "it's not recommended". You'd better use the original db2 backup db/tablespace tool.

Check the state of the tablespaces with "list tablespaces show detail". What's the state? Is it quiesced?

Another hack to get the first hack working could be to restore the original path. Do you have a drive F: on your dev system? If not, "add" it with "subst F: D:\". This makes D:\mypath available as F:\mypath, too.

Regards,


Bernd
Aug 1 '08 #2

P: 2
Hi,

maybe this way of db transfer is working sometimes, but I guess the words an IBM expert would use are "it's not recommended". You'd better use the original db2 backup db/tablespace tool.

Check the state of the tablespaces with "list tablespaces show detail". What's the state? Is it quiesced?

Another hack to get the first hack working could be to restore the original path. Do you have a drive F: on your dev system? If not, "add" it with "subst F: D:\". This makes D:\mypath available as F:\mypath, too.

Regards,
Bernd

Hello,
Thanks for your response.
1: Please let me know the proper and recommended way of taking tha backup of a DB from one server and restoring the backup on another server. We want to do it everyday, because we want the DB on the other server to be an exact replica of the Prod DB.
2: On doing list tablespaces show detail, all the Tablespaces are OFFLINE.
except one . I have tried to get the table space to Online as well, but the Table space are not accessible.
3:If there is no easy way for easy backup and restore, then please also suggest in detail the last step you have mentioned.

Regards,
Rachana
Aug 1 '08 #3

docdiesel
Expert 100+
P: 297
Hi,

you should at least one time do a full offline backup of your prod db:

Expand|Select|Wrap|Line Numbers
  1. db2 backup db mydb to x:\mypath\
Move the backup to the test system and restore it:

Expand|Select|Wrap|Line Numbers
  1. db2 restore db mydb from x:\mypath\
You may use "backup/restore db mydb tablespace mytbspc" later on. Use a "db2 ? backup" on the db2 command window to see all options.

Regards,


Bernd
Aug 1 '08 #4

Post your reply

Sign in to post your reply or Sign up for a free account.