Ater installation WCC URL gives 404 - Not Found, WCC logs show ORA-12516

Products

• Autosys Workload Automation

Issue/Introduction

After a fresh installation or upgrade to WCC 24.2, the WCC GUI is inaccessible and displays an HTTP 404 - Not Found error. The 'Redirect' button on the page does not resolve the issue.

Review of the WCC log files (e.g., CA-wcc-services.log or jvm logs) reveals the following database connection errors:

ORA-12516: Cannot connect to database. Listener at host [HOSTNAME] port [PORT] does not have a protocol handler for TCP ready or registered for service [SERVICE].ERROR #WccDataSource # Database not available yet. Cannot create the jdbc pool. Will retry after ##### milliseconds

 

The Oracle listener may also show multiple connection attempts from the WCC server using the machine's hostname as the user

Cause

The issue is caused by the Oracle database reaching its maximum limit for PROCESSES or SESSIONS.

When the WCC services attempt to initialize their JDBC connection pool, the Oracle listener refuses the requests because no handlers are available, resulting in the ORA-12516 error. Because the database connection pool cannot be established, the WCC web application fails to start correctly, leading to the 404 error in the browser.

Resolution

To resolve this issue, the Oracle database limits must be increased to accommodate the connection requirements of the WCC services.

• Stop WCC Services - On the WCC server, stop the following services to release any pending connection attempts:

CA-wcc
CA-wcc-services

• Increase Oracle Database Limits - Coordinate with your Database Administrator (DBA) to verify and increase the session limits:
• Check the current session count and limits:
  sql
SELECT COUNT(*) FROM v$session;
SHOW PARAMETER processes;
SHOW PARAMETER sessions;


• Increase the processes and sessions limits (e.g., to 500 or higher based on environment needs):
  sql
ALTER SYSTEM SET processes=500 SCOPE=SPFILE;
ALTER SYSTEM SET sessions=500 SCOPE=SPFILE;


• Restart the Oracle database instance if necessary for the changes to take effect. 
  
  
• Clear Logs and Restart WCC.
• (Optional) Clear or archive the existing WCC log files to ensure a clean troubleshooting view.
  Start the WCC services:
  CA-wcc-services
CA-wcc


• Monitor the logs to ensure the JDBC pool is created successfully and no further ORA-12516 errors appear.
• Once the services have initialized, the WCC GUI should be accessible without the 404 error.

Additional Information

To speak with a customer representative or a Support Engineer, see Contact Support. Scroll to the bottom of the page and click on your respective region.