INST-07064 Upgrading Portal to 11g if Schema Name is not 'PORTAL' (Doc ID 1358501.1)

Last updated on JULY 28, 2023

Applies to:

Symptoms

This problem occurs when attempting a 10g-> 11g upgrade on a Portal environment where the Portal schema uses a custom schema name. i.e. the schema name is different from the standard default schema name of 'Portal'.

Oracle® Fusion Middleware Upgrade Guide for Oracle Portal, Forms, Reports, and Discoverer 11g Release 1 (11.1.1) 

Chapter 3 Upgrading Your Oracle Portal, Forms, Reports, and Discoverer Environment, Task 5c.

WLS 10.3.4 is installed.
The FMW binaries have been installed and upgraded to the latest version (11.1.1.4).

Running config.sh from the Fusion Middleware 11.1.1.4 Oracle Home to configure Portal.
At step "3.5.4.2 Specifying the PORTAL Schema Name and Password", entering the correct connection details for the portal schema results in an error:

INST-07064: Unable to connect to the database with the given credentials.

The log file shows this error:

oracle.as.install.engine.modules.validation.oracle.as.install.engine.modules.validation.handler.dbQueries.checkIfAllSchemasArePresent] [tid: <TID>] [ecid: <ECID>] Exception[[
java.sql.SQLSyntaxErrorException: ORA-00942: table or view does not exist
at oracle.jdbc.driver.SQLStateMapping.newSQLException(SQLStateMapping.java:91)

Database tracing shows the ORA-00942 error is related to this statement:

SELECT MR_TYPE FROM schema_version_registry WHERE UPPER(OWNER)=UPPER('<PORTAL_SCHEMA>')
Error encountered: ORA-00942

The same problem does not occur when connecting to a default Portal seeded schema.

Changes

Cause

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