BCC Incremental Deployments And VersionManagerRepository Gather Statistics Change
Last updated on MARCH 28, 2017
Applies to:Oracle Commerce Platform - Version 11.0 and later
Information in this document applies to any platform.
On 18.104.22.168 version, BCC deployment of an empty project is taking 20 minutes. 20 minutes to rollback as well. It is several orders of magnitude slower than ATG 10.2 with older hardware.
DirectSQL deployments are enabled in legacy and new 11.2p2 environments. There are new methods and properties on dyn/admin/nucleus/atg/epub/version/VersionManagerRepository in 11.2, which have been seen taking most of the time in the deployments and rollbacks, namely, calls in these stack frames, which spend a long time in Oracle DB at the start of the deployment process:
The SQL properties for the gathering stats are visible on the VersionManagerRepository component. The gathering stats is normal DB maintenance, usually, but this is getting run on every deployment, and it seems to be causing the majority of the deployment time running the stats in the db. It does not happen in 10.x versions. Is this tunable from the ATG side or requires a DBA to review all the objects its gathering stats for and applying custom indexes? Something that can be disabled optionally?
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms