• Please add the package "com.addteq" with log level = DEBUG in logging and profiling section in Confluence Administration to monitor the migration logs
  • Following is the list of tables that will be present in the DB after installing 4.2.3
    V0 versionV1 version
    • AO_40ABA8_COLLABORATOR_DB
    • AO_40ABA8_COLLABORATOR_DBV1
    • AO_40ABA8_EDIT_HISTORY_DB
    • AO_40ABA8_EDIT_HISTORY_DBV1
    • AO_40ABA8_ETSHARE
    • AO_40ABA8_ETSHARE_V1
    • AO_40ABA8_ETSHARE_DETAILS
    • AO_40ABA8_ETSHARE_DETAILS_V1
    • AO_40ABA8_EXC_LICENSE_CHECK
    • AO_40ABA8_EXC_LICENSE_CHECK_V1
    • AO_40ABA8_EXCELLENTABLE_DB
    • AO_40ABA8_EXCELLENTABLE_DBV1
    • AO_40ABA8_LIVE_EDIT_CONFIG
    • AO_40ABA8_LIVE_EDIT_CONFIG_V1
    • AO_40ABA8_LIVE_EDIT_REGISTER
    • AO_40ABA8_LIVE_EDIT_REGISTERV1
    • AO_40ABA8_PLUGIN_VERSION
    • AO_40ABA8_PLUGIN_VERSION_V1
    • AO_40ABA8_WHATS_NEW_DB
    • AO_40ABA8_WHATS_NEW_DBV1

    • AO_40ABA8_MIGRATION_AUDIT

    • AO_40ABA8_MIGRATION_STATUS

    • AO_40ABA8_ID_TO_UUID_MAPPING

    • AO_40ABA8_EXC_MAPPING

Version Upgrade Paths

The upgrade path indicates the versions that have been previously installed on the instance before installing 4.2.3. This can be viewed in the AO_40ABA8_PLUGIN_VERSION and AO_40ABA8_PLUGIN_VERSION_V1 tables

For example : Path 4.1.7->4.2.1.6→4.2.3 depicts that the previously installed versions were 4.1.7 and 4.2.1.6


4.1.x -> 4.2.3 or 4.1.x->4.2.1.x->4.2.3
  •  Logs
    1. Phase 1
       


    2. Phase 2

      1. Start of Phase2


      2. End of Phase2



  • AO_40ABA8_MIGRATION_STATUS table :

    PhaseStatus
    Phase 1Not Required
    Phase 2Success



  • Counts of V0 and V1 tables 

    • In Path 4.1.x →4.2.3 :

      No. of records in V0 = No. of records in V1 version.

For example: 
If "AO_40ABA8_EXCELLENTABLE_DB" has 100 records in 4.1.7 then "AO_40ABA8_EXCELLENTABLE_DBV1" should also have 100 records after migration in 4.2.3.
      CODE

    • In Path 4.1.x→4.2.1.x→4.2.3

      No. of records in V1 = No. of records in V0 + No. of records in V1 before installing 4.2.3

For example: 
If in 4.2.1.6 ,"AO_40ABA8_EXCELLENTABLE_DB" has 100 records and "AO_40ABA8_EXCELLENTABLE_DBV1" has 25 records , then after migration in 4.2.3 "AO_40ABA8_EXCELLENTABLE_DBV1" should also have 125 records.
      CODE
  • Check the Statistics column in AO_40ABA8_MIGRATION_STATUS to confirm the number of records migrated for each V0 table in Phase 2. The count in V0 should match the count shown in the statistics column.
  • Each V0 table should have a UUID column with the mapped UUID entries.






4.1.x->4.2.1->4.2.1.x->4.2.3
  •  Logs
    1. Phase 1

      1. Start of Phase 1
         


      2. End of Phase 1
    2. Phase 2 
      1. Start of Phase 2


      2. End of Phase 2

  • AO_40ABA8_MIGRATION_STATUS table :

    PhaseStatus
    Phase 1Success
    Phase 2Not Required

  • Counts of V0 and V1 tables 

    The count of V0 and V1 tables before and after migration should be the same
    CODE
  • Check the Statistics column in AO_40ABA8_MIGRATION_STATUS to confirm the number of records migrated for each V0 table in Phase 1. The count in V0 should match the count shown in the statistics column.
  • Each V0 table should have a UUID column with the mapped UUID entries.











4.2.1.x->4.2.3 or New installation of 4.2.3
  •  Logs
    • Phase 1 & Phase 2
       


  • AO_40ABA8_MIGRATION_STATUS table :

    PhaseStatus
    Phase 1Not Required
    Phase 2Not Required



  • Counts of V0 and V1 tables 

    The V0 tables will be empty
The count of V1 tables before and after installation of 4.2.3 should be the same
    CODE
  • Each V0 table should have an empty UUID column.






Other Scenarios


Failed UUID Migration
  • For mitigating a failed migration, please follow the steps here


  •  Logs
    • Phase 1 & Phase 2 - Failure
       


    • Phase 1 & Phase 2 - After retrying migration 



  • AO_40ABA8_MIGRATION_STATUS table

    • Initial Run - The Statistics column will keep a count of records that have been partially migrated.

      PhaseStatus
      Phase 1Not Required
      Phase 2Failed




    • After retrying migration, a new record for Phase 2 will be added in the table
  • Retrying the migration will resume the migration from where it was interrupted during the initial run. 





Reinstalling 4.2.3/Re-enabling plugin after successful migration
  •  Logs
    • Phase 1 & Phase 2 

       

  • AO_40ABA8_MIGRATION_STATUS table

    • This table will not be updated and still show the status of previous successful migration






Restarting Confluence Instance
  •  Logs

    • Phase 1 & Phase 2 migration will not be triggered. Following will be shown in the logs during restart

      2020-11-04 20:36:32,026 WARN [Catalina-utility-1] [confluence.plugin.descriptor.MacroMetadataParser] parseParameter Unrecognised type 'null' for parameter 'excellentableId' of macro 'excellentable' in plugin 'Addteq.Excellentable'
2020-11-04 20:36:32,026 WARN [Catalina-utility-1] [confluence.plugin.descriptor.MacroMetadataParser] parseParameter Unrecognised type 'null' for parameter 'creation' of macro 'excellentable' in plugin 'Addteq.Excellentable'
2020-11-04 20:36:55,780 DEBUG [ThreadPoolAsyncTaskExecutor::Thread 35] [plugin.excellentable.service.ExecutorServiceManagerImpl] afterPropertiesSet Created Executor Service
2020-11-04 20:36:55,978 DEBUG [ThreadPoolAsyncTaskExecutor::Thread 35] [plugin.excellentable.listener.ExcLicenseListener] afterPropertiesSet ExcLicenseListener After Properties Set
2020-11-04 20:37:03,720 INFO [active-objects-init-system tenant-0] [plugin.excellentable.upgrade.UuidUpgradeTask] upgrade Upgrade tasks can run only on the user authenticated node.
      CODE
  • AO_40ABA8_MIGRATION_STATUS table

    • This table will not be updated and still show the status of previous successful migration