1. Forum
  2. Usenet
  3. COMP.DATABASES.IBM-DB2

  • db2look generated on V10.5 failing on V9.7

    From Jerry Stuckle@21:1/5 to Shashi Shekhar on Thu Oct 20 22:38:16 2016
    On 10/20/2016 8:55 PM, Shashi Shekhar wrote:
    Hi All,

    Need your help/suggestion.

    DB2 Version - 10.5 , 9.7
    OS - AIX


    Recently , on our Dev environment DB2 got migrated from 9.7 to V10.5. QA is still 9.7.

    I was in process of building a new Database on Dev. I have created the database on QA as well, but due to multiple changes App. Team wants to recreate each objects again in QA from Dev. Since I have all objects ( tables and Procedures) in one schema. I
    thought to drop the schema in QA and generate db2look in dev only for that specific schema and run that in QA.

    But I came across few keywords used in V10.5 like "octets", "Organize by rows" and some more which are not allowed in 9.7 and giving error.

    any idea ? should I manually remove those ?


    Thanks in advance for reply.


    Regards
    Shashi


    In general, tools are upward compatible but not downward, as you found.

    The safest way would be to recreate the objects using the original DDL
    you used on Dev. Failing that, you can't just blindly remove the
    keywords. You need to look at each statement and ensure the changes
    result in an equivalent object in 9.7.

    --
    ==================
    Remove the "x" from my email address
    Jerry Stuckle
    [email protected]
    ==================

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Shashi Shekhar@21:1/5 to All on Thu Oct 20 17:55:59 2016
    Hi All,

    Need your help/suggestion.

    DB2 Version - 10.5 , 9.7
    OS - AIX


    Recently , on our Dev environment DB2 got migrated from 9.7 to V10.5. QA is still 9.7.

    I was in process of building a new Database on Dev. I have created the database on QA as well, but due to multiple changes App. Team wants to recreate each objects again in QA from Dev. Since I have all objects ( tables and Procedures) in one schema. I
    thought to drop the schema in QA and generate db2look in dev only for that specific schema and run that in QA.

    But I came across few keywords used in V10.5 like "octets", "Organize by rows" and some more which are not allowed in 9.7 and giving error.

    any idea ? should I manually remove those ?


    Thanks in advance for reply.


    Regards
    Shashi

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Jerry Stuckle@21:1/5 to Shashi Shekhar on Fri Oct 21 09:07:47 2016
    On 10/21/2016 6:18 AM, Shashi Shekhar wrote:
    On Friday, October 21, 2016 at 8:08:23 AM UTC+5:30, Jerry Stuckle wrote:
    On 10/20/2016 8:55 PM, Shashi Shekhar wrote:
    Hi All,

    Need your help/suggestion.

    DB2 Version - 10.5 , 9.7
    OS - AIX


    Recently , on our Dev environment DB2 got migrated from 9.7 to V10.5. QA is still 9.7.

    I was in process of building a new Database on Dev. I have created the database on QA as well, but due to multiple changes App. Team wants to recreate each objects again in QA from Dev. Since I have all objects ( tables and Procedures) in one schema.
    I thought to drop the schema in QA and generate db2look in dev only for that specific schema and run that in QA.

    But I came across few keywords used in V10.5 like "octets", "Organize by rows" and some more which are not allowed in 9.7 and giving error.

    any idea ? should I manually remove those ?


    Thanks in advance for reply.


    Regards
    Shashi


    In general, tools are upward compatible but not downward, as you found.

    The safest way would be to recreate the objects using the original DDL
    you used on Dev. Failing that, you can't just blindly remove the
    keywords. You need to look at each statement and ensure the changes
    result in an equivalent object in 9.7.


    Thanks Jerry.

    meanwhile, I googled and found below page of developerworks. he also faced similar issue.

    https://www.ibm.com/developerworks/community/blogs/norbertogf/entry/db2look-105-to-97?lang=en

    I also replaced those keywords with null/space. and ran the db2look file on my QA. It worked .

    Any idea, This way I would have missed something which may cause potential issue later time?

    Thanks again in advance for your time.


    Regards
    Shashi



    Without examining all of your DDL (like I suggested above), it's
    impossible to say whether you will have a potential issue or not later.
    There are way too many variables.

    The question here is - if there is a problem, will it be easier to
    correct now, or after you've added a bunch of data to the database?

    --
    ==================
    Remove the "x" from my email address
    Jerry Stuckle
    [email protected]
    ==================

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)