locked
DB2 zOS - SBCS Data RRS feed

  • Question

  • When I create a table in DB2 with Varchar, the SSMA sql defintion shows as "VARCHAR(36) FOR SBCS DATA". When we do a migration with the SQLSERVER table datatype as VARCHAR(36), it fails with 

     Errors: The given key was not present in the dictionary.

    When i searched for this error, it sounded like datatype mismatch. But we do not specify "FOR SBCS DATA" in the DB2 table creation query. When I tried to map the datatypes in SSMA, there is no way to specify "VARCHAR(36) FOR SBCS DATA" in the from mapping field. 

    Any suggestions on how to make SSMA ignore "For SBCS DATA" in the source definition? 

    Monday, March 16, 2020 11:36 AM

All replies

  • Also "Create Report" for this table (and for this schema) is empty. Also here is the log enabled at debug level. 

    [Info: Datamigrator] [13628/50] [2020-03-16 17:03:55]: The data migration engine is migrating table '"SENTHIL"."TABLE_NAME"': > [SENTHILDB].[dbo].[TABLE_NAME], 1 rows total
    [Info: Datamigrator] [13628/50] [2020-03-16 17:03:55]: Data Migration Processor is going to wait 500
    [Info: Datamigrator] [13628/50] [2020-03-16 17:03:55]: Data Migration Processor is going to wait 500
    [Info: Gui] [13628/1] [2020-03-16 17:03:56]: The given key was not present in the dictionary.

    [Info: Datamigrator] [13628/50] [2020-03-16 17:03:56]: The given key was not present in the dictionary.
    [Info: Gui] [13628/1] [2020-03-16 17:03:56]:  Errors: The given key was not present in the dictionary.

    Monday, March 16, 2020 11:39 AM
  • Hi senthilnathan_zos,

    Could you please check if the Data Type of the column in DB2 is VARCHAR?

    For Data Type in DB2 z/OS, I suggest you open a thread in the corresponding forum so that people there will help you more effectively.

    Please refer to IBM DB2 to Microsoft SQL Server Migration which might help.

    Best Regards,

    Amelia


    MSDN Community Support
    Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com.

    Tuesday, March 17, 2020 3:10 AM
  • Hi,

    This error usually means that target table is not found. Did you create tables in the SQL Server database manually or synchronized through SSMA? Different casing might be another cause.

    Can you navigate to Tools -> Global settings -> Logging and switch all logs to Debug, then reproduce the error and share the offending call stack with us?

    Thanks,
    Alex.

    Tuesday, March 17, 2020 9:25 PM
  • Hi senthilnathan_zos,

    Was your issue resolved?

    If the replies could help you, please mark the useful reply as answer to help other community members find the helpful reply quickly.

    If you resolve it using your own solution, please share your experience and solution here. It will be very beneficial for other community members who have similar questions.

    If not, please don't hesitate to let us know and tell us the current situation in order to provide further help.

    Best Regards,

    Amelia


    MSDN Community Support
    Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com.

    Friday, March 20, 2020 8:17 AM