404 NOT FOUND Error After Login For Certain Users Which Are Not Based on PORTAL_PUBLIC (Doc ID 1466869.1)

Last updated on MARCH 08, 2017

Applies to:

Portal - Version 11.1.1.4.0 and later
Information in this document applies to any platform.

Symptoms

A custom database schema was created in Portal 10g and Portal users were based on that database schema.
From User profile --> preferences TAB --> Database Schema , instead of having PORTAL_PUBLIC, they have a different schema.
 
In Portal 10g everything was working fine, but after upgrading to Portal 11g, users start getting the following error  when trying to login:

Error: The listener returned the following Message: 404 Not Found
 

And the following error is seen in the WLS_PORTAL.log

Mar 13, 2014 3:24:19 PM GMT> <Error> <oracle.portal> <BEA-000000> <ERROR: Repository Gateway error: Database Error: ORA=6550 ORA-06550: line 32, column 3:
PLS-00201: identifier 'PORTAL30.WPG_SESSION' must be declared
ORA-06550: line 32, column 3:
PL/SQL: Statement ignored
ORA-06550: line 33, column 3:
PLS-00201: identifier 'PORTAL30.WWPOB_PAGE' must be declared
ORA-06550: line 33, column 3:
PL/SQL: Statement ignored
ORA-06550: line 37, column 4:
PLS-00201: identifier 'PORTAL30.WPG_SESSION' must be declared
ORA-06550: line 37, column 4:
PL/SQL: Statement ignored
ORA-06550: line 43, column 4:
PLS-00201: identifier 'PORTAL30.WPG_SESSION' must be declared
ORA-06550: line 43, column 4:
PL/SQL: Statement ignored>

The problem users are able to login to oiddas.
If the database schema in the User Profile is set back to *PORTAL_PUBLIC (the default) all users are able to login and work as expected.
 

 

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