Error: "Ora-43853: Securefile Lobs Cannot Be Used in Non-assm Tablespace 'pmdb_dat1'" When Upgrading P6 (Doc ID 1643719.1)

Last updated on JULY 25, 2017

Applies to:

Primavera P6 Enterprise Project Portfolio Management - Version 8.3.2.0 and later
Information in this document applies to any platform.

Symptoms

When attempting to upgrade P6, the following error occurs.

ERROR
-----------------------
ERROR: ORA-43853: SECUREFILE lobs cannot be used in non-ASSM tablespace "PMDB_DAT1"

Full Error Found In DatabaseSetup log:

OUTPUT>USER [INFO] : Upgrade from schema version 0700.0001.0001.0003 to schema version 0830.0001.0001.0015
OUTPUT>[ERROR] [2014-02-26 08:32:48] ORA-43853: SECUREFILE lobs cannot be used in non-ASSM tablespace "PMDB_DAT1"
OUTPUT>
OUTPUT>[ERROR] [2014-02-26 08:32:48] Database Error: error number=43853
OUTPUT>[ERROR] [2014-02-26 08:32:48] Error Message: ORA-43853: SECUREFILE lobs cannot be used in non-ASSM tablespace "PMDB_DAT1"
OUTPUT>
OUTPUT>USER [WARN] : Could not complete because the job "Run SQL Script ORPM_p70sp3.sql" failed.
OUTPUT>com.primavera.database.tools.DatabaseToolException: ORA-43853: SECUREFILE lobs cannot be used in non-ASSM tablespace "PMDB_DAT1"
OUTPUT>
OUTPUT>    at com.primavera.database.tools.ScriptRunner.ScriptRunner.runSQL(ScriptRunner.java:209)
ERROR>RuntimeException: Could not complete because the job "Perform core upgrade steps" failed. (Could not complete because the job "Perform core upgrade steps" failed.)
OUTPUT>    at com.primavera.database.tools.ScriptRunner.ScriptRunner.run(ScriptRunner.java:145)
OUTPUT>    at com.primavera.database.tools.dbmt.workflow.SqlScriptJob.doJob(SqlScriptJob.java:86)
OUTPUT>    at com.primavera.database.tools.dbmt.AbstractJob.execute(AbstractJob.java:64)
OUTPUT>    at com.primavera.database.tools.dbmt.WorkflowStepJob.doJob(WorkflowStepJob.java:49)
OUTPUT>    at com.primavera.database.tools.dbmt.AbstractJob.execute(AbstractJob.java:64)
OUTPUT>    at com.primavera.database.tools.dbmt.actions.BaseWizardRunner.runJob(BaseWizardRunner.java:195)
OUTPUT>    at com.primavera.database.tools.dbmt.cmd.CmdLineWizardRunnerFactory$1.commit(CmdLineWizardRunnerFactory.java:173)
OUTPUT>    at com.primavera.database.tools.dbmt.actions.JobTreeTypeDef$JobRunner.run(JobTreeTypeDef.java:252)
OUTPUT>    at java.lang.Thread.run(Thread.java:744)
OUTPUT>    at com.primavera.database.tools.dbmt.actions.JobTreeTypeDef$JobRunner.runJobs(JobTreeTypeDef.java:245)
OUTPUT>    at com.primavera.database.tools.dbmt.actions.TransitionMap.initializeCommitPage(TransitionMap.java:339)
OUTPUT>    at com.primavera.database.tools.dbmt.actions.TransitionMap.initialize(TransitionMap.java:131)
OUTPUT>    at com.primavera.database.tools.dbmt.actions.PropertyWizardNavigationAction.tryToLeavePage(PropertyWizardNavigationAction.java:53)
OUTPUT>    at com.primavera.database.tools.dbmt.cmd.CmdLineWizardRunnerFactory$1.performWizardAction(CmdLineWizardRunnerFactory.java:147)
OUTPUT>    at com.primavera.database.tools.dbmt.actions.BaseWizardRunner.runWizard(BaseWizardRunner.java:76)
OUTPUT>    at com.primavera.database.tools.dbmt.actions.WizardActionOperation.perform(WizardActionOperation.java:90)
OUTPUT>    at com.primavera.database.tools.dbmt.cmd.CmdLineApplicationRunner.start(CmdLineApplicationRunner.java:69)
OUTPUT>    at com.primavera.database.tools.dbmt.Main.main(Main.java:91)
OUTPUT>DBError: DBSetup failed to complete! Returned error level: 1

Changes

 

Cause

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