ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.
PMO upgrade fails with ORA-00060: deadlock detected while waiting for resource
book
Article ID: 132230
calendar_today
Updated On:
Products
Clarity PPM SaaSClarity PPM On Premise
Issue/Introduction
When running PMO upgrade, it fails and error message is thrown:
Loading registered objects for building blocks bootstrap... Content Pack Installation - ODF Bootstrap failed: [CA Clarity][Oracle JDBC Driver][Oracle]ORA-20000: Error: ORA-00060: deadlock detected while waiting for resource ORA-06512: at "CLARITY.CMN_ENABLE_DISABLE_SP", line 67 ORA-06512: at line 1 Content Pack Installation - ODF Bootstrap failed: [CA Clarity][Oracle JDBC Driver][Oracle]ORA-20000: Error: ORA-00060: deadlock detected while waiting for resource ORA-06512: at "CLARITY.CMN_ENABLE_DISABLE_SP", line 67 ORA-06512: at line 1 Failed to install content pack: Content Pack Installation - ODF Bootstrap failed [CA Clarity][Oracle JDBC Driver][Oracle]ORA-20000: Error: ORA-00060: deadlock detected while waiting for resource ORA-06512: at "CLARITY.CMN_ENABLE_DISABLE_SP", line 67 ORA-06512: at line 1 Error occurred: com.niku.nsa.service.ExecutableException: Content Pack Installation - ODF Bootstrap failed [CA Clarity][Oracle JDBC Driver][Oracle]ORA-20000: Error: ORA-00060: deadlock detected while waiting for resource ORA-06512: at "CLARITY.CMN_ENABLE_DISABLE_SP", line 67 ORA-06512: at line 1 Check admin.log or use -verbose for more information. Failed to install content pack. ID: csk: exec returned: 1 Failed to install content pack. ID: csk: exec returned: 1 Error occurred: /apps/clarity/META-INF/content/xog/csk/install.xml:242: exec returned: 1 Check admin.log or use -verbose for more information.
Environment
Release: CODCVU9900-15.5.1-PPM SAAS-View Only Userpack for-Canadian Government Entities Component:
Resolution
Ensure Clarity services are stopped prior to the PMO upgrade and that jobs are not running on the database.
Nothing should be accessing the database whilst the PMO upgrade is in progress.