Yokohama(+) Upgrade: Increase in the upgrade time for reparenting Appointment Booking Configuration tables [sn_apptmnt_booking_config, sn_apptmnt_booking_service_config, sn_apptmnt_booking_config_rule] to Application file [sys_metadata]The “Appointment Booking” application upgrade to Yokohama may extend the customer upgrade maintenance duration due to the following : An extension of the Appointment Booking Configuration tables (sn_apptmnt_booking_config, sn_apptmnt_booking_service_config, sn_apptmnt_booking_config_rule) to the the Application file (sys_metadata). These tables are part of the Appointment Booking Plugin and starting from Yokohama release any changes made to these tables will be tracked as an update set. This re-parenting process will occur automatically, as scheduled post the Yokohama upgrade.Time taken for reparenting doesn't depend solely on actual table getting reparented but other parent/child, metadata tables as we make copies of them and swap them at the end, thus, it depends on the number of records in the following tables - sys_metadata, sys_dictionary, sys_db_object, sys_documentation, sys_storage_alias along with the tables which are getting reparented. On an instance with almost 29M records in the sys_metadata table, the reparenting process for Appointment Booking Configuration tables took around 36 minutes. As part of our internal testing, the script was executed on a HI instance with 5000 records in the service configuration table, and it took approximately 2.8 minutes to complete. Based on the read audit, the maximum number of records in any customer instance is around 2600. The reparenting for these three tables has been done in the same fix script as they have references to each other.