Considerations for 3.0 to 3.1 SP1 upgrade

Discussion created by Scott_Owens Employee on Aug 28, 2013
CA Process Automation Technical Tip by Scott Owens, Sr Support Engineer, August 28th, 2013.

All versions of PAM compare the current schema of the databases they use to what the version expects during startup. Where there are differences PAM will modify the database tables and indices to match what it expects. This check is quick, and normally detects no changes, but after an upgrade, there may be substantial changes, and in the case of pre-3.0 SP1 PAM to a newer version the changes are very substantial. For small databases this is no problem, but with a large database, PAM may take hours to be complete the modifications, and there could be danger that the modifications will fail due to exhausting free space in the database, or transaction log space.

Please see the attached document which has specific recommendations. As a general rule: get rid of as much unneeded data as possible prior to an upgrade. Archives will need to be manually purged, since purge policies were not available back in 3.0, and if reporting is not required consideration should be given to turning reporting off, and dropping the reporting tables.