IBM Support

IZ21307: MIGRATE EXPORT/IMPORT SCRIPTS FAIL FOR MICROSOFT SQL SERVER

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Environment:
    TEPS, Windows only, when MSSQL used as TEPS database
    
    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.
    
    Detailed Recreation Procedure:
    Set up TEPS with SQL Server as database.  Run
    migrate-export.bat.  Use migrate-clean.bat to clear out the TEPS
    database, then attempt to import the saveexport.sql file using
    migrate-import.bat.  The TEPS log will show several SQL
    insertion errors.
    
    Approver:RP
    
    Related Files and Output: none
    

Local fix

  • Alter migrate-export.bat to force the type of database.
    
    At label :foundDataSource  add
    
    set KFW_DSN_TYPE=MSSQL
    

Problem summary

  • 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.
    

Problem conclusion

  • The migrate-export.bat script incorrectly checks the errorlevel
    of the command used to determine the database type.  The command
    returns the number of rows selected from the database as the
    errorlevel.  If a particular database check fails, it returns 0
    for the errorlevel, but the script incorrectly assumes a 0 means
    the correct database was found.
    
    The errorlevel check was updated in the code to check for 1
    instead of 0.
    
    The fix for this APAR is contained in the following maintenance
    packages:
     | interim fix | 6.1.0.7-TIV-ITM-IF0002
    

Temporary fix

Comments

APAR Information

  • APAR number

    IZ21307

  • Reported component name

    TEPS

  • Reported component ID

    5724C04PS

  • Reported release

    610

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2008-04-29

  • Closed date

    2008-08-27

  • Last modified date

    2008-08-27

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

Fix information

  • Fixed component name

    TEPS

  • Fixed component ID

    5724C04PS

Applicable component levels

  • R610 PSY

       UP

[{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SSCTLMQ","label":"ITM Tivoli Enterprise Portal Server V6"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"610","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
27 August 2008