IBM Support

SQL2542N No match for a database image file was found based on the source database alias

Troubleshooting


Problem

db_restore may fail with SQL2542N error and put database in restore pending state when specified multipath.

Cause

Not specified fully qualified paths in db_restore command.

Diagnosing The Problem

Step 1:

db_backup -path /scratch/test1 /scratch/test2 /scratch/test3 -type onl
Checking if Backup or Restore is in progress.
Performing System Health Check...
System is ready to Run Backup(s) and/or Restore(s).
Validating path(s) /scratch/test1
WARN: /scratch may run out of space. Please use NFS or SAN for backups.
Checking for available space for path: /scratch/test1/backup_onl_1
Validating path(s) /scratch/test2
WARN: /scratch may run out of space. Please use NFS or SAN for backups.
Checking for available space for path: /scratch/test2/backup_onl_1
Validating path(s) /scratch/test3
WARN: /scratch may run out of space. Please use NFS or SAN for backups.
Checking for available space for path: /scratch/test3/backup_onl_1
Sufficient space available.

Backup process started....
100%======================================================================================>
Part  Result
----  ------------------------------------------------------------------------
0000  DB20000I  The BACKUP DATABASE command completed successfully.
0001  DB20000I  The BACKUP DATABASE command completed successfully.
0002  DB20000I  The BACKUP DATABASE command completed successfully.
0003  DB20000I  The BACKUP DATABASE command completed successfully.
0004  DB20000I  The BACKUP DATABASE command completed successfully.
0005  DB20000I  The BACKUP DATABASE command completed successfully.
0006  DB20000I  The BACKUP DATABASE command completed successfully.
0007  DB20000I  The BACKUP DATABASE command completed successfully.
0008  DB20000I  The BACKUP DATABASE command completed successfully.
0009  DB20000I  The BACKUP DATABASE command completed successfully.
0010  DB20000I  The BACKUP DATABASE command completed successfully.

Backup successful. The timestamp for this backup image is : 20181126091905

Backup path(s): /scratch/test1/backup_onl_1,/scratch/test2/backup_onl_1,/scratch/test3/backup_onl_1

For more info see /scratch/bluadmin_BNR/logs/backup20181126091854.log

Step 2:

db_restore -path /scratch/test1 /scratch/test2 /scratch/test3 -type frh -timestamp 20181126091905
Checking if Backup or Restore is in progress.
Performing System Health Check...
System is ready to Run Backup(s) and/or Restore(s).
Successfully disabled HA.
Successfully disabled DSM.
Successfully blocked remote connections.
Successfully stopped database.
Successfully started database in admin restricted mode.

Restore in progress on the Head Node...

SQL2542N  No match for a database image file was found based on the source
database alias "BLUDB" and timestamp "20181126002122" provided.
node0101-fab: db2 restore database ... completed rc=4


ERROR: Failed to run restore on head node, please check the diagnostic files and try again.
Successfully unblocked remote connections.
Successfully stopped database.
Successfully started database.
Successfully enabled API Server.
Successfully enabled DS Server.
Successfully enabled HA.

For more info see /scratch/bluadmin_BNR/logs/restore20181126003532.log

Resolving The Problem

db_backup tool creates a directory on top of user specified path (/scratch/test1 /scratch/test2 and /scratch/test3), something like backup_onl_1 if it is online backup.  And  restore db_restore tool expects to give the full path something like , -path "/scratch/test1/backup_onl_1" "/scratch/test2/backup_onl_1" and "/scratch/test3/backup_onl_1" in this case.

Eg: [bluadmin@node0101-fab - Db2wh ~]$ ls /scratch/test1

backup_onl_1

[bluadmin@node0101-fab - Db2wh ~]$ ls /scratch/test1/backup_onl_1

BLUDB.0.db2inst1.DBPART000.20181126091905.001  BLUDB.0.db2inst1.DBPART005.20181126091905.001
BLUDB.0.db2inst1.DBPART000.20181126091905.004  BLUDB.0.db2inst1.DBPART006.20181126091905.001
BLUDB.0.db2inst1.DBPART001.20181126091905.001  BLUDB.0.db2inst1.DBPART007.20181126091905.001
BLUDB.0.db2inst1.DBPART002.20181126091905.001  BLUDB.0.db2inst1.DBPART008.20181126091905.001
BLUDB.0.db2inst1.DBPART002.20181126091905.004  BLUDB.0.db2inst1.DBPART009.20181126091905.001
BLUDB.0.db2inst1.DBPART003.20181126091905.001  BLUDB.0.db2inst1.DBPART010.20181126091905.001
BLUDB.0.db2inst1.DBPART004.20181126091905.001

So the correct db_restore command in this case should be:

db_restore -path /scratch/test1/backup_onl_1 /scratch/test2/backup_onl_1 /scratch/test3/backup_onl_1 -type frh -timestamp 20181126091905

 

Related Information

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSHRBY","label":"IBM Integrated Analytics System"},"Component":"Backup and restore","Platform":[{"code":"PF004","label":"Appliance"}],"Version":"All Versions","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
03 January 2019

UID

ibm10743273