Just discovered something which caused me some headache. The migrate-export.bat generates DB2 syntax statements by default, regardless if you’re using MS SQL or not for TEPS. Go ahead and try to import the ’saveexport.sql’ into your TEPS SQL db, it will cause some fun corruption. An APAR exists, but it still has not made it into ITM6.2
APAR IZ21307
MIGRATE EXPORT/IMPORT SCRIPTS FAIL FOR MICROSOFT SQL SERVER
Problem Description:
The migrate-export.bat and migrate-import.bat scripts do not work correctly when the TEPS database is Microsoft SQL Server.
The scripts incorrectly detect the database type to be DB2, and insert SQL statements in the saveexport.sql file that are
invalid in SQL Server. Attempting to import the saveexport.sql file into a TEPS using SQLServer will result in several SQL errors and data will be missing from the TEPS database.
Circumvention:
Manually edit the migrate-export.bat script and change the errorlevel checks at line 29 and 35 to 1 from 0.
In the IT field for 17 years. Experience includes consulting, project management, technical support, software development and implementations. Specialized in the area of enterprise implementations and distributed systems management. Provided services to many Fortune 500 companies as well as the government agencies. Provided services as ITM specialist in providing a complete enterprise management solution including rapid deployment, automation, monitoring, and real-time reporting of a Tivoli environment.