offline restore without roll forward

[james...@gmail.com]

I am using partitioned DB2 10.1 (AESE), with 15 partitions on 5 machines (each machine hosts 3 partitions).

I have taken an offline backup from my database (after deactivating it) by running following command on catalog node (instance owning node):

db2 backup database myDb on ALL DBPARTITIONNUMS to /home/data/db2/backup

Now I am trying to restore it, by running restore command without roll forward. Starting from catalog node, I run following command on ALL machines, and all of them return success code:

db2 RESTORE DATABASE myDb FROM /home/data/db2/backup TAKEN AT 20140210171717 INTO myDb REPLACE EXISTING WITHOUT ROLLING FORWARD

But when I start my database, and run queries, I keep getting following error:

SQL1471N Cannot connect to database "MYDB" on node "2" because the
database on this node is not synchronized with catalog node. SQLSTATE=08004

Reading IBM pages, I realized it is happening because of roll forwarding issues. I even tried running restore command, and right after that running following command from catalog node:

db2 rollforward db myDb to end of logs ON ALL DBPARTITIONNUMS and complete

But it keeps giving me the same error.

I am just wondering what I am missing, as I just want to restore myDb to its initial state that I had right after loading it, when I took backup.

Any suggestion/idea ?
(Thanks in advance)

James

[Mark A]

I am not sure about 10.1 but on 9.7 I think you need to restore the catalog node only first, then restore
all the other nodes. The first command you issued restores the catalog node only. Then run the same
command again prefixed by db2_all (instead of just db2) to restore to all nodes. At that point you
should be OK to connect to database.

[james...@gmail.com]

When running restore command, I first run it on the node that has catalog partition. So catalog partition gets restored first. Then I run the command on other boxes. db2_all also runs the command separately on each machine (similar to the way I am doing manually on machines). I do not face with any problem in that part, as all the machines return success.
I am just wondering why I keep getting SQL1471N error although I am restoring without Roll Forward.

James

[muke...@gmail.com]

whats the fix for this ?

[Jerry Stuckle]

On 1/13/2017 2:43 AM, muke...@gmail.com wrote:
> whats the fix for this ?
>

Ensure the database is restored from consistent offline backups on all
nodes without rolling forward.

--
==================
Remove the "x" from my email address
Jerry Stuckle
jstu...@attglobal.net
==================

[toun...@gmail.com]

Hi all?
This problem is solved? If Yes, can you share the solution please?
I'm facing To the same issue.

Thanks in advance.