Topic
  • 3 replies
  • Latest Post - ‏2011-10-25T11:32:07Z by SystemAdmin
ShariqHanif
ShariqHanif
2 Posts

Pinned topic Column names are replaced by schema name in views during migration

‏2011-10-19T11:14:40Z |
Hello ,

I am migrating from Oracle 10g to DB2 v9.7 using IBMDMT v(2.00-b2114). I notice that column names are replaced by schema name in all the views due to which views can not be migrated/deployed . This is happening in previous versins of IBMDMT as well . Can you please see attached snap and look into the issue .

Thanks

Shariq
Updated on 2011-10-25T11:32:07Z at 2011-10-25T11:32:07Z by SystemAdmin
  • SystemAdmin
    SystemAdmin
    708 Posts

    Re: Column names are replaced by schema name in views during migration

    ‏2011-10-20T17:11:38Z  
    Hi shariq,
    Can you please attach your IBMExtract.properties file?

    Best regards,
    Raul
  • ShariqHanif
    ShariqHanif
    2 Posts

    Re: Column names are replaced by schema name in views during migration

    ‏2011-10-23T11:44:53Z  
    Hi shariq,
    Can you please attach your IBMExtract.properties file?

    Best regards,
    Raul
    Thanks for your reply Raul .

    For some reason there is no IBMExtract.properties for v2114 so I am attaching v2.00-b1758 file .

    Regards

    Shariq
  • SystemAdmin
    SystemAdmin
    708 Posts

    Re: Column names are replaced by schema name in views during migration

    ‏2011-10-25T11:32:07Z  
    Thanks for your reply Raul .

    For some reason there is no IBMExtract.properties for v2114 so I am attaching v2.00-b1758 file .

    Regards

    Shariq
    Hi Shariq, I have compared your file to mine but have found minor differences.

    Yours has:

    retainConstraintsName=false
    oracleNumberMapping=false
    mapTimeToTimestamp=null

    mine has:

    retainConstraintsName=true
    oracleNumberMapping=true
    mapTimeToTimestamp=false

    and mine also has (and yours doesn't have)

    loadException=true
    exceptSchemaSuffix=_EXP
    exceptTableSuffix=

    but I don't think this might be the difference. We haven't experienced this issue.
    Our last build version was 2.00-b1799.