Maximo

Maximo

Come for answers, stay for best practices. All we're missing is you.

 View Only
Back to discussions
Expand all | Collapse all

MAS 9 Upgrade - Updatedb changing ALL DATETIME columns to DATETIME2 type column for ALL tables

  • 1.  MAS 9 Upgrade - Updatedb changing ALL DATETIME columns to DATETIME2 type column for ALL tables

    Posted Sat December 14, 2024 12:51 AM

    Hi All,

    Need suggestions on below.

    Upgrading 7613 to MAS 9. Running updatedb.sh. (Managed SQL Instance DB on Azure) 

    Updatedb started altering DATETIME columns to DATETIME2 columns for all tables. It is running from last 20 hours and keep going.

    Since it is gonna change all DATETIME columns to DATETIME2 columns and this is gonna take couple of weeks on large size of DB.

    Please advise on how to prevent this or speed this up. 



    ------------------------------
    Ritesh Ranjan
    ------------------------------


  • 2.  RE: MAS 9 Upgrade - Updatedb changing ALL DATETIME columns to DATETIME2 type column for ALL tables

    Posted Sat December 14, 2024 12:52 AM
    Edited by Ritesh Ranjan Sat December 14, 2024 12:52 AM

    are there any options/configurations on SQL DB, where we can set datetime column type globally?



    ------------------------------
    Ritesh Ranjan
    ------------------------------

    Original Message


  • 3.  RE: MAS 9 Upgrade - Updatedb changing ALL DATETIME columns to DATETIME2 type column for ALL tables

    Posted Fri December 20, 2024 10:43 AM

    Hi Ritesh,

    Did you find any resolution/workaround on this issue? We are running into same issue on our instance during upgrade.



    ------------------------------
    SRINIVASA KILARU
    ------------------------------

    Original Message


  • 4.  RE: MAS 9 Upgrade - Updatedb changing ALL DATETIME columns to DATETIME2 type column for ALL tables

    Posted Sat December 21, 2024 08:46 AM
    Edited by Ritesh Ranjan Mon December 23, 2024 02:18 AM
    Hi,
    You can't escape that. But you can change the approach. Instead of doing that conversion via updatedb.sh, do it manually directly on DB level.
    Find all the persistent attribute of maxtype DATE and DATETIME, then run alter commands directly on DB level. that will be faster and then run updatedb.sh in maxinst pod.
    Another thing you will encounter index dependencies on those date type attributes. You will have to take note of them and drop them.
    post updatedb.sh you will have to recreate them.
    Hope this helps you and if yes, please mark this as accepted answer.
    Let me know what else you encountered.
    'The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this message and any attachments. WARNING: Computer viruses can be transmitted via email. The recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email. www.wipro.com'

    Internal - General Use




    Original Message