R12 REP-0069: Internal error REP-50002: Server is shutting down

We are getting R12 application custom concurrent report while running:

REP-0069: Internal error
REP-50002: Server is shutting down








=== Issue Clarification ===

In eBusiness Suite 12.0.6, a custom report based on a concurrent program has failed with the following errors :
REP-0069: Internal error
REP-50002: Server is shutting down

Report Builder: Release 10.1.2.2.0

=== Cause Justification ===

We can only provide specific cause & solution for reports supplied by Oracle, e.g. there is a known issue with a seeded Aged Buckets report in Receivables (Note 1321276.1), or issues relating to Reports Developer, such as Bug 12422704 (neither of which are relevant here).


=== Issue Verification ===

Verified the issue in the log file as noted below:

LOG FILE
-----------------------
Filename = Service_Charges_SoA_060711.txt
See the following error:
Enter Password:
REP-0069: Internal error
REP-50002: Server is shutting down

=== Cause Determination ===

There are a number of possible reasons why a custom report might produce the REP-0069: Internal error. They are usually data related. For example:
1. One or more tables on which report is based contains obsolete data.
2. One or more tables on which report is based contains missing data which the report requires.
3. The processing is too intensive for the CPU and/or JVM used by the Report Engine. For example complex pagination with a large amount of data.
4. Incorrect password not handled correctly by the report.

This list is not exhaustive. Other potential causes may be identified by searching our Knowledge Base in My Oracle Support for "REP-0069: Internal error".

=== Proposed Solutions ===

Ensure that :
- The report has the resources it needs (e.g. memory, CPU, JVM max heap size) in order to process the maximum amount of data it could fetch
- None of the data required by the report is obsolete or missing, and
- The report traps incorrect passwords and returns a controlled error message to the user, if it asks the user to enter a password (as appears to be the case here).

Product Support does not provide specific advice on custom report design. There are 3 options for help with custom report design, which I would try in the following order: (1) Search our Knowledge Base in My Oracle Support for "REP-0069: Internal error". (2) Discuss your report design at https://communities.oracle.com . (3) Engage an on site consultant from Advanced Customer Services.

=== Proposed Solutions Justification ===

1. For example Note 1312609.1 - Payroll Activity Report Error REP-0069.
2. For example Note 731171.1 - R12 Invoice Print - Selected Invoices Error Out With REP-0069: Internal error.
Or Note 1251774.1 - ARZCARPO Automatic Receipts/Remittances Execution Report Completes with "REP-0069: Internal error" and "REP-1401: 'b_12formattrigger'" Errors.
3. We would expect REP-0069 to be accompanied by a Java exception error if the cause is related to Java, e.g. JVM maximum heap size is too low. See Note 859067.1 - Rep-0069: Internal Error java.lang.OutOfMemoryError Running Reports with "Page X of Y" Feature.
4. In the log file, the error is preceded by "Enter Password", so this would seem to be a likely solutoin in this case. See for example Note 1270758.1 - REP-0069 / REP-58101 "Error Stopping Internal Web Server" When Exiting Reports Builder.