DB2 offline full backup original path recovery
1. Use db2ckbkp-h to check backup files
[db2inst1@ESB-DB-J5 home] $db2ckbkp-hDMSDEV.0.db2inst.NODE0000.CATN0000.20160513102947.001=MEDIA HEADER REACHED:=Server Database Name-- DMSDEVServer Database Alias-- DMSDEVClient Database Alias-- DMSDEVTimestamp-- 20160513102947Database Partition Number-- 0Instance-- db2instDatabase Configuration Type-- 0 (Non-shared data) Sequence Number- -1Database Member ID-0Release ID-0xD00 (DB2 v9.7) Database Seed-0x7903558CDB Comment's Codepage (Volume)-0DB Comment (Volume)-DB Comment's Codepage (System)-0DB Comment (System)-- Authentication Value-255 (Not specified) Backup Mode-0 (Offline) Includes Logs-0 (No) Compression-0 (Uncompressed) Backup Type-0 (Database-level) Backup Granularity-0 (Non-incremental) Merged Backup Image-0 (No) ) Status Flags-0x1 Consistent onthis memberSystem Catalogs in thisp_w_picpath-1 (Yes) Catalog Partition Number-0DB Codeset-UTF-8DB Territory-LogID-1458720781LogPath-/ db2data/db2inst / NODE0000/SQL00002/SQLOGDIR/Backup Buffer Size-16781312 (4097 4K pages) Number of Sessions-1Platform-0x1E (Linux-x86-64) The properp_w_picpath file name would be:DMSDEV.0.db2inst.DBPART000.20160513102947.001 [1] Buffersprocessed: # # # # Image Verification Complete-successful
two。 Create a new database
The new library is consistent with the check content of the backup file db2ckbkp.
Instance-db2instClient Database Alias-DMSDEVTimestamp-20160513102947DB Codeset-UTF-8LogPath-/ db2data/db2inst/NODE0000/SQL00002/SQLOGDIR/
* strongly required precautions:
(1) if the name of the Instance does not match, create a new instance that is consistent with it
(2) create a new home path that is the same as the original user (above is / db2data)
-- create instance users and fence users
# su-root# useradd-m-gdb2iadm1-d / home/db2inst db2inst# useradd-m-gdb2fadm1-d / home/db2fenc db2fenc# passwd db2inst# passwd dbfenc
-- create a new instance with the same name as the original instance
# su-root# cd/opt/ibm/db2/V10.5/instance#. / db2icrt-p 50100Muru db2fenc db2inst
-- create a new database with the same name as the original database
# su-db2inst# db2start# db2create database dmsdev using codesetutf-8 territory CN
-- change all permissions for backup files
# su-root# chowndb2inst:db2iadm1 / home/DMSDEV.0.db2inst.NODE0000.CATN0000.20160513102947.001
-- create the home path of the original instance
# su-root# mkdir / db2data# chowndb2inst:db2iadm1 / db2data
-- Import full backup files
# su-db2inst# db2restore database dmsdev from / home taken at20160513102947 without rolling forward without prompting
-- assign administrative rights to the library
# db2connect to dmsdev# db2grant dbadm on database to user dms
3. Database configuration work
(1) modify the port number of db2inst under / etc/service
(2) # db2setDB2COMM=tpcip
(3) # reboot