Hi!
I am having a problem when I restore a database to a location that is a symbolic link. It appears DB2 is translating the symbolic link, and storing the container names using the "real" path. This is a problem because the plan is to mount this area in the location of the symbolic link in case of a disaster at the primary location.
For example:
The data location is /law/prod/db2_data/db2inst1. The symbolic link is /db2_data/db2inst1 points to /law/prod/db2_data/db2inst1.
Code:
ll /db2_data
lrwxr-xr-x 1 db2inst1 db2inst1 32 Mar 18 15:24 db2inst1 -> /law/prod/db2_data/db2inst1
In case of a disaster, the /law/prod/db2_data/db2inst1 will be mounted as /db2_data/db2inst1.
So my restore command is:
Code:
db2 "restore db db2inst1 to /db2_data/db2inst1 into db2inst1"
But when I query the containers, the whole path is listed:
Code:
TBSPC_NAME CONT_NAME CONTAINER_TYPE USABLE_PAGES
------------ ---------------------------------------------------------------------------- -------------- ------------
SYSCATSPACE /law/prod/db2_data/db2inst1/db2inst1/NODE0000/SQL00001/SQLT0000.0 SMS Directory 0
TEMPSPACE1 /law/prod/db2_data/db2inst1/db2inst1/NODE0000/SQL00001/SQLT0001.0 SMS Directory 0
USERSPACE1 /law/prod/db2_data/db2inst1/db2inst1/NODE0000/SQL00001/SQLT0002.0 SMS Directory 0
SYSTOOLSPACE /law/prod/db2_data/db2inst1/db2inst1/NODE0000/SQL00001/SYSTOOLSPACE DMS File 8188
SYSTOOLSTMPS /law/prod/db2_data/db2inst1/db2inst1/NODE0000/SQL00001/SYSTOOLSTMPSPACE SMS Directory 0
Is there anyway to force it to not translate the links?
Thanks!
Jodie