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:
Sent: 12/19/2024 12:44:00 PM
From: SRINIVASA KILARU
Subject: RE: MAS 9 Upgrade - Updatedb changing ALL DATETIME columns to DATETIME2 type column for ALL tables
Hi Ritesh,
Did you find any resolution/workaround on this issue? We are running into same issue on our instance during upgrade.
------------------------------
SRINIVASA KILARU
------------------------------