Troubleshooting error WWC-0000 When Try to Access to Portal 11g

Troubleshooting error WWC-0000 When Try to Access to Portal 11g

Troubleshooting error WWC-0000 When Try to Access to Portal 11g

Titleimage

Posted by Patrick Hamou on 2017:09:22 18:12:49

APPLIES TO: Portal - Version 11.1.1.3.0 and later

Portal - Version 11.1.1.3.0 and later
Information in this document applies to any platform.
Checked for currency on 26-MAR-2015

PURPOSE: troubleshooting, WWC-000

This is a guide to troubleshooting error WWC-0000 when trying to access to Portal 11g

TROUBLESHOOTING STEPS

Possible cause of this issue: Database Upgrade from 10g to 11g

Description: After Database upgrade unable to access to Portal due to error WWC-00000

Document referring the solution: This was caused by invalid objects and missing database grant to the Portal Schema.
Apply solution of note: Note 1368226.1

-----------------------------------------------------

Possible cause of this issue: There were missing ACLs after the install.

Description: Missing ACL after fresh install this was reported as Bug  8801803

Document referring the solution: Workaround recreate the ACL manually. Steps to do this in the following note.
Note 875212.1

-----------------------------------------------------

Possible cause of this issue: Proxy Server was not routing properly the traffic to SSO

Description: 

a.- A proxy was set up on the DB server which was blocking traffic from DB to SSO 
b.- Portal Proxy was not routing to SSO server.

Document referring the solution: This issue was caused by a network misconfiguration Portal Midtier and Portal Database should be able to reach SSO server.. Related Notes :
Note 1284400.1
Note 1068777.1
Note 976788.1
Note 1264916.1

-----------------------------------------------------

Possible cause of this issue: SSL was enable but all the steps were not completed

Description: Portal was not wired properly to work with SSL

Document referring the solution: Completed the SSL setup.
Reference:
Note 1275276.1

-----------------------------------------------------

Possible cause of this issue: OID userid has special characters such as trailing spaces

Description: This was caused by special character (Trailing spaces) in the userid attribute in OID

Document referring the solution: Delete and recreate the user without trailing spaces in LDAP repository

-----------------------------------------------------

Possible cause of this issue: Upgrading Portal 10g SSL to Portal 11g SSL

Description: Certificate issue

Document referring the solution: Upgrade steps in this note
Note 1185414.1: Upgrading Portal 10g SSL to Portal 11g SSL

-----------------------------------------------------

Possible cause of this issue: SSL wallet file deleted in one RAC node.

Description: 

DB directory /home/oracle/ssldeleted.

Under that ssl directory, there was a ssl wallet file used between the fusion middleware server and database server. OAM needs that ssl wallet. That is why the error is not consistent as the database servers are two-node RAC. 

So, when traffic hits the first Rac node where the ssl wallet was removed, get the error, and when traffic hit the second Rac node, it is fine as the ssl wallet on the second Rac node is there.

If check:
Portal builder
   ->Administer tab

       ->Global settings
           ->SSO/OID tab
              ->Under SSO sever settings. 

There are two settings:
1. Query URL PreFix: <URL for F5 OAM VIP> 
2.  Wallet Path: file:/home/oracle/ssl/wallet (this file folder is being deleted)

Document referring the solution: Workaround:

Option 1:
Restore DB directory that was deleted from backup.

Option 2:
Recreate the deleted directory then create a new wallet and import the root certificate.
Reference:
Create an Empty Wallet (HTTPS)

 

 

Posted by Patrick Hamou on 2017:09:22 18:12:49

Return to Blog