We noticed that while applying cumulative 6.7.0b398(6.7.3) the NAC startup sequence takes longer. Can you please suggest if it's something unexpected or expected behavior as part of this cumulative.
This is only specific to NAC running with Oracle DB
Migration Script Details:
There is a migration script in the patch 6.7.0b398 i.e. 126.96.36.1998 patch which is V188.8.131.52.202006051400000__
It may take more than usual time to run these actions on the big DB and NAC being available for an end user.
Estimation: A DB size of +300GB it took ~40 minutes for completion of above script execution. Please note the time taken for completion is determined not only by DB size but also the hardware specification of DB server, ongoing activities on DB along with any performance parameters configured by DBA on DB instance.
Release : 6.7.0b398(6.7.3)
Component : CA RELEASE AUTOMATION ADMINISTRATION
DB: Oracle (Only)
DB status Validation: To validate if the RA is able to complete the DB migration successfully. To check what is going on in the DB after the Nolio server is started with running the following script:
select v.sid, v.serial#, v.username, v.status, v.server, v.schemaname, v.osuser, v.process, v.machine, v.program, v.module, v.logon_time, v.event, v.wait_class, v.state, s.* from v$session v left outer join v$sql s on s.sql_id = v.sql_id where v.username = '[!!!USER_NAME!!!]';
Note:: The above script must be executed with the user that has access privileges to the v$session and v$sql views. A System or sysdba user have these privileges. by default. This script allows us to check/monitor sessions running in the DB and will allow us to understand what is being executed with the flyway migration script.