PPM Migrate.bat Does Not Use Non-Default TEMP Tablespace Or Generates Error "ORA-00959: tablespace 'TEMP' does not exist" If TEMP Does Not Exist When Migrating A PPM Database To Oracle

(Doc ID 2225967.1)

Last updated on JANUARY 30, 2017

Applies to:

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


When attempting to run the PPM version of the migrate.bat application to migrate a database to Oracle, and selecting a non-standard/named TEMP tablespace, the following error is generated:

[ERROR] [TIMESTAMP] ORA-00959: tablespace 'TEMP' does not exist

[ERROR] [TIMESTAMP] Database Error: error number=959
[ERROR] [TIMESTAMP] Error Message: ORA-00959: tablespace 'TEMP' does not exist

[WARN] [TIMESTAMP] [USER] Could not complete because the job "Run SQL Script orppm_create_users.sql" failed.
com.primavera.database.tools.DatabaseToolException: ORA-00959: tablespace 'TEMP' does not exist

Note, a secondary symptom is that if a temp tablespace exists, it will use TEMP instead of the non-default tablespace selected.

Steps to reproduce:
1. Have an Oracle target database where the temporary tablespace is named anything other than the default of "TEMP"
2. Perform a migration to that Oracle database.
3. In the tablespace selection screen of migrate.bat, observe that the correct temporary tablespace is listed in the dropdown, and selected as expected.
4. When the migration begins to run, observe that the ADMUSER fails to create and that the SQL and output log file both reference that the user was attempted to be created with temporary tablespace of TEMP, not the correct non-default name.

The issue has the following business impact:
Due to this issue, users cannot migrate using a non-standard/default TEMP tablespace.


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