First start of a Content Manager OnDemand instance or the Archive Storage Management (ASM) process takes longer

The first start of a Content Manager OnDemand instance or the Archive Storage Management (ASM) process after an upgrade to Content Manager OnDemand for i 7.2 might take longer because of a number of database changes. The most significant delay occurs if you are upgrading from a release before 7.1 due to the movement of instance-specific data and objects from the QUSRRDARS library into the instance libraries.

Do not end the server job or the ASM job because you are concerned that it is not progressing.
Status messages are signaled during the database changes and the data movement from QUSRRDARS to the instance library. You can check these messages to confirm that the job is progressing.