My Oracle Support Banner

Error: "ORA-04098: trigger 'ADMUSER.RT_SETTINGS' is invalid and failed re-validation" When Running Dbsetup Tool To Create A P6 EPPM Database Or When Running Migrate to Move A Database To A New Schema (Doc ID 1609058.1)

Last updated on MARCH 23, 2018

Applies to:

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

Symptoms

When attempting to create a P6 database in Oracle using dbsetup, the following error occurs:

ERROR
-----------------------
Database error.Error number=4098.Error message:ORA-04098:Trigger ADMUSER.TABLE is invalid and failed re-validation

DatabaseToolException (ORA-04098: trigger "ADMUSER.RT_SETTINGS' is invalid and failed re-validation ORA-06512: at line 2

Example Error:
DatabaseToolException (ORA-04098: trigger 'ADMUSER.PRMAUD_PREFER' is invalid and failed re-validation)

 

When attempting to migrate a P6 database to Oracle 12.2 in Oracle using migrate, the following error occurs:

 

ERROR
-----------------------
TIMESTAMP [ERROR] [TIMESTAMP] ORA-04098: trigger 'ADMUSER.RT_SETTINGS' is invalid and failed re-validation
ORA-06512: at line 2

TIMESTAMP [ERROR] [TIMESTAMP] Database Error: error number=4098
TIMESTAMP [ERROR] [TIMESTAMP Error Message: ORA-04098: trigger 'ADMUSER.RT_SETTINGS' is invalid and failed re-validation
ORA-06512: at line 2

TIMESTAMP[WARN] [2018-02-22 15:46:50] [USER] Could not complete because the job "Run SQL Script orpm_settings.sql" failed.
com.primavera.database.tools.DatabaseToolException: ORA-04098: trigger 'ADMUSER.RT_SETTINGS' is invalid and failed re-validation
ORA-06512: at line 2

        at com.primavera.database.tools.ScriptRunner.ScriptRunner.runSQL(ScriptRunner.java:209)
        at com.primavera.database.tools.ScriptRunner.ScriptRunner.run(ScriptRunner.java:145)
        at com.primavera.database.tools.dbmt.workflow.SqlScriptJob.doJob(SqlScriptJob.java:86)
        at com.primavera.database.tools.dbmt.AbstractJob.execute(AbstractJob.java:64)
        at com.primavera.database.tools.dbmt.WorkflowStepJob.doJob(WorkflowStepJob.java:49)
        at com.primavera.database.tools.dbmt.AbstractJob.execute(AbstractJob.java:64)
        at com.primavera.database.tools.dbmt.actions.BaseWizardRunner.runJob(BaseWizardRunner.java:195)
        at com.primavera.database.tools.dbmt.actions.BaseWizardRunner.commit(BaseWizardRunner.java:203)
        at com.primavera.database.tools.dbmt.actions.JobTreeTypeDef$JobRunner.run(JobTreeTypeDef.java:252)
        at java.lang.Thread.run(Thread.java:745)

 


STEPS TO REPRODUCE
-----------------------
The issue can be reproduced at will with the following steps:

  1. Run DBsetup.bat file, and provide db details and click on 'Next'
  2. Additional table spaces get created successfully, click 'Next'
  3. Provide passwords for all P6 related DB users(admuser,privuser,pubuser etc) and click next.
  4. The issue will occur during the creation of the additional objects



Changes

 

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Changes
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.