Errors After A Redirected Restore!

ADM1814E The current log path
"/ PATH/NODE0000/" is invalid.

ADM1811E DB2 will now switch to the default log path
"/PATH/NODE0000/SQL00004/SQLOGDIR/".

Whether you are restoring to a different machine or on the same machine never forget to change the NEWLOGPATH Database Parameter. If you don’t DB2 will switch to default log path. This will not be an issue if you are using default log path.

DB2 was unable to confirm logs were archived.
Return code 118489304, FirstArchNum 31953, HeadExtentID 31958

An error was received from the user exit program.
0x2FF21508 : 0x0000001C ....

Userexit program maintains a log which is more informative than the above and it will be in the files named USEREXIT.ERR & ARCHIVE.LOG, you should be able to find that in the LOGPATH.

You have to act based on that.

In my case I have to create a directory for the new database so that it can archive the logs.

This message keeps coming up sometimes after a redirected restore and not sure what it means… Help me!

SQL procedure executables recovery has been initiated. DBNAME
0x2FF1E330 : 0x4341535342202020

SQL procedure executables recovery ended. RC:
0x2FF1E310 : 0x00000000

Migrating from AIX to Windows

There are the steps that i followed to migrate...

Haven't done the move on Prod DB. Will update with changes if any.

STEPS:

DB2 doesn’t support cross platform back-up and restore between AIX & Windows. Thus redirect restore cannot be used.

But DB2 UDB has tools to achieve this task.

• db2move - Used for moving User tables (DATA)
• db2look - Creates DDL to create the database objects in the new environment.
• db2cfexp – Exports connectivity configuration to an export profile
• db2cfimp – Import connectivity configuration information.

Steps for Moving from AIX to Windows

On AIX:

1. Use db2move to export all table data to PC/IXF files
2. Use db2look to generate DDL for all the database objects.
3. Use db2cfexp to export the configuration information to a file.
4. Transfer PC/IXF files & Configuration profile in Binary Mode.
5. Transfer db2look.sql & db2move.lst in ASCII Mode.

On Windows:

1. Make sure the version of DB2 is same with the appropriate Fixpack.
2. Create an instance with the same name as it was in AIX. (optional)
3. Create all the databases that you are moving.
4. Set current schema name.
5. Create required Buffer pools and Table Spaces for the DB.
6. Run the script generated by db2look
7. Import the configuration information using db2cfimp tool.
8. Run db2move in load mode. (Takes a while for large DB’s)
9. Update DB CFG to reflect the source DB.
10. Do a Full DB/Table space Backup to take the table space out of backup pending state and check for the integrity of the Backup.
11. Detect the tables that are in check pending state and bring it to normal state. (set integrity)
12. Check other db objects to make sure they are in Normal State.
13. All the configuration parameters need to be tuned according to the current hardware.

NOTE:

Don’t forget that default values for some parameters are different for windows & AIX

comments, suggestions, questions are welcome..

Welcome

Hi all

DB2 DBA's out there

Come Share your thought's findings...