Migrate-import and restoring the TEPS database.
sandrajones 270000NWW2 Visits (9751)
So the previous blog detailed the steps on how to take the export of your TEPS but it is only useful if you know what to do to restore it on your original or another TEPS. This is what this blog will discuss.
There are some requirements before an import can be done if you are moving from one machine to another:
The database type for the TEPS database must be the same. ( so db2 to db2; MSSQL to MSSQL)
The same HUB TEMS needs to be used and the same application support needs to be installed on the TEPS that the import is being done to.
There are a couple of issues that it is worth knowing and will be seen whatever operating type you are importing the TEPS database to:
When you import there is some errors that may be seen like:
SQLExecDirect rc=-1: SQL_ERROR SQLSTATE: 42S02, ERR: -204, MSG: [IBM][CLI Driver][DB2/LINUX] SQL0204N "ITMUSER.TAGGROBJ" is an undefined name. SQLSTATE=42704 RC = -1
These might not just be seen for this name
ITMUSER.TMANOBJS, ITMUSER.TMANTMPL, ITMUSER.TTMPLSIT, ITMU
These errors can be ignored, any other errors would need to be reviewed.
Also if the migrate-import is used on a TEPS, that TEPS database is dropped and overwritten, you cannot add to an existing TEPS with this command.
So the import is straight forward if you are restoring back to your previously saved TEPS, and no updates have taken place in the meantime. The TEPS should be stopped before this is done.
The default file saveexport.sql will be in this directory already, but as mentioned in the last blog, it is wise to take a copy of the export (and maybe date it) as the file is overwritten any time the migrate-export is run.
type in migrate-import.
type ./itmcmd execute cq "runscript.sh migrate-import.sh"
be sure to use double quotes in this command.
The output of the command will look something like:
That is all that is needed unless the release has changed between the save and restore.
Restore import and change release.
If there has been a change of release as well, the following steps also need to be done to add application support:
On Linux or Unix:
This will update the application support.
The file looks like this on windows:
Change the KFW_MIGRATE_FORCE value to Y, and remember that once the import is done to change it back to N.
You can also import a windows TEPS to a Linux machine or a Linux machine to a Windows machine, by following the instructions above for operating system you are importing into and using the KFW_MIGRATE_FORCE=Y setting after the import. This needs to be set to Y regardless of whether the version is the same when changing operating types. Also this can only be done if the databases in both machine types is the same.
Addition to this blog is the following:
There has been an issue with migrate-export at 6.3 FP04 which means there is a problem after the import is done.
Please see this Tech Note:
ITM 6.3.0 Fix Pack 4 on xLinux, zLinux and AIX platforms. Windows users are not affected.
Subscribe and follow us for all the latest information directly on your social feeds: