EPPM to PPM Migration Utility Fails When Tablespaces Are Not Default

(Doc ID 2225942.1)

Last updated on FEBRUARY 21, 2017

Applies to:

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


When using MIGRATE.BAT to move from EPPM to PPM, using Oracle as the back end database, if non-default existing tablespaces are chosen (as they are identified from the migrate.bat tool), the tool still tries to use the original tablespace names instead of the existing names causing the following errors:


[INFO] [2016-09-23 09:43:30] CREATE USER P6MFGS_ADMUSER
[ERROR] [2016-09-23 09:43:30] ORA-00959: tablespace 'PMDB_DAT1' does not exist

[ERROR] [2016-09-23 09:43:30] Database Error: error number=959
[ERROR] [2016-09-23 09:43:30] Error Message: ORA-00959: tablespace 'PMDB_DAT1' does not exist

[WARN] [2016-09-23 09:43:30] [USER] Could not complete because the job "Run SQL Script orpm_create_users.sql" failed.
com.primavera.database.tools.DatabaseToolException: ORA-00959: tablespace 'PMDB_DAT1' does not exist

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:205)
at com.primavera.database.tools.dbmt.actions.BaseWizardRunner.commit(BaseWizardRunner.java:214)
at com.primavera.database.tools.dbmt.actions.JobTreeTypeDef$JobRunner.run(JobTreeTypeDef.java:253)
at java.lang.Thread.run(Unknown Source)


The issue can be reproduced at will with the following steps:
1. Set up an EPPM database on Oracle. On the target database (can be the same database with new schemas), use non-standard tablespace names like TEST_DAT1, TEST_NDX1, etc..
2. Start migrate.bat and choose the existing tablespaces you just created.
3. migrate.bat will fail with the above errors.


The issue has the following business impact:
Due to this issue, non-default tablespaces cannot be used.


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