Support Article

Operation completes successfully, but returns no content

SA-12551

Summary



When attempting to access a Pega instance, an error appears instead of the login page. Restarting the instance does not resolve the issue.


Error Messages



In Internet Explorer (IE):

Status: Good
Message: The Operation completed successfully, but returned no content
Operator ID <blank>
requestor ID: HFBD94FE556D99AA9ECD71508620C8C48



In Chrome:

PegaRules Request Status
fail
Caught db exception while looking up pyLable in Data-Admin-Nodes PRRuntimeException



In PegaRULES log:


Problem #1, SQLState 64000, Error code 257: java.sql.SQLException: ORA-00257: archiver error. Connect internal only, until freed.
Caused by: java.sql.SQLException: ORA-00257: archiver error. Connect internal only, until freed.

 

Steps to Reproduce



Direct your browser to main login page of Pega instance.


Root Cause



The root cause of this problem is defect/misconfiguration in the operating environment. There was a lack of archive space for the database.

Resolution



This issue is resolved by making the following change to the operating environment:

Increase the space available to the database and restart the JVMs.

Published August 3, 2015 - Updated October 8, 2020


33% found this useful

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.