Tablespace is not avaiable in the HADR Server
If a takeover operation occurs, the new table space that you created is not available on the new primary database. To recover from this situation, restore the table space on the new primary database from a backup image.
In the following example, table space TABLESPACE_1 is restored on database SAMPLE before it is used as the new primary database:
db2 connect to sample
db2 list tablespaces show detail
Note: Run the db2 list tablespaces show detail command to show the status of all table spaces and to obtain the table space ID number.
db2 stop hadr on database sample
db2 "restore database my_database tablespace (tablespace_1) online redirect"
db2 "set tablespace containers for tablespace_1_ID_# ignore rollforward container operations using \
(path ’/my_new_container_path/’)"
db2 "restore database sample continue"
db2 rollforward database my_database to end of logs and stop tablespace "(my_tablespace)"
db2 start hadr on database sample as primary
The primary and standby databases do not require the same database path. If relative container paths are used, the same relative path might map to different absolute container paths on the primary and standby databases.