What is wrong with this Redirected restore command - UDBv8.2 fp14 on Linux

[p***@hotmail.com]

Hi all,
This is a very urgent issue for my team. We are trying a Redirected restore the most current online DB2 UDBv8.2 backup copy from prod disk to another/test instance disk on . Our environment is RedHat Linux. We have tried the following with failure:

(1)[***@aaanpudb1 /]$ db2 restore db AANPDM01 from "/stuff/ftp/bkp" taken at 20070525164103 to "/dmd/data" into AANNDM01
NEWLOGPATH "/dmt/log" redirect without rolling forward;

SQL1052N The database path "/dmd/data" does not exist.

Note: "/dmd/data" does not exist in the source DB2 Linux Production environment but categorically exist in the target DB2 Linux

Test environment. What I need is to restore restore from production to test.
[***@fsfnpudb1 /]$ <== prod_instance_DB
[***@target_server <== systest_instance_DB

(2) We then tried to sFTP the backup image copy to the test environment but not having much luck either. We got repeated failure

with this message:

sftp> put FSNPDM01.0.db2prd1.NODE0000.CATN0000.20070925044506.001
Uploading AANPDM01.0.db2prd1.NODE0000.CATN0000.20070925044506.001 to

/db2home/db2inst1/AANPDM01.0.db2prd1.NODE0000.CATN0000.20070925044506.001
AANPDM01.0.db2prd1.NODE0000.CATN0000.20070925044506.001 12% 3972MB 4.2MB/s 1:54:37 ETA. Couldn't write to

remote file
"/db2home/db2inst1/FSNPDM01.0.db2prd1.NODE0000.CATN0000.20070925044506.001": Failure ID mismatch (127219 != 3)


Could any of our redirected restore gurus please step in and shed some light on this technical matter! This will be highly

appreciated!!

Sincerely

okonita

[Kelly Schlamb]

Hello,

I have no experience with sftp so I cannot comment on problem #2. As for the SQL1052N issue, if you truly have that path there and DB2 is not recognizing it then I suggest opening a PMR with support.

Now, you say that /dmd/data does actually exist on the target box. Can you check and make sure that it's actually a directory, and not a file or something (this wouldn't be done on purpose, but maybe it was done accidentally). Or maybe it's a link that points to an invalid location? Both of these things will result in an SQL1052N.

Regards,
Kelly

[p***@hotmail.com]

So, I take it you find no syntax, missing required option, etc.

Now, I will tripple-check to make sure it is a folder and not a file, etc.

Big question: Redirected restore CAN be done between to seperate DB2 instances. Also, that DB2 data file and logs files( can be pointed to the same path as the original/existing path for the redirect restore requirement.

Your thoughts?

Okonita

[Kelly Schlamb]

Nothing in your command looks wrong to me from a syntax or missing options point of view. If there was something wrong with that then I'd expect a different type of error.

Yes, a redirected restore can be done to a different instance. I'm not really sure what you are asking with respect to the data file and log files. By specifying the "TO" option, you are telling DB2 to change the database path (where the metadata resides, and potentially other things like the 3 default tablespaces). By specifying "REDIRECT", you are saying that you want to change the containers associated with one or more tablespaces in the database (and you'll use the SET TABLESPACE CONTAINERS command to do that).

Regards,
Kelly

[p***@hotmail.com]

Kelly,
Thank you very much for your giving me another set of eyes and for your explanation.