APP-FND-00222 When Attempting To Run Any Request (Doc ID 412987.1)
APPLIES TO:
Oracle Application Object Library - Version 11.5.10.2 to 11.5.10.2 [Release 11.5]
Information in this document applies to any platform.
SYMPTOMS
On 11.5.10.2 in Production:
When attempting to run any request,
the following error occurs:
APP-FND-00222: Encountered an error while getting the ORACLE user account for your concurrent request
The issue can be reproduced at will with the following steps:
1. Submit any request
2. Face the above error
The issue has the following business impact:
Due to this issue, users cannot submit any request.
CHANGES
Recent applying of ATG RUP3 and associated patches
CAUSE
Although there is no customization done but there is some issue in the CUSTOM.pll
This is verified as follows:
1. Log into Apps and Turn OFF "Custom Code" in the Help->Diagnostics menu.
2. After turning off the custom code, it was possible to launch new requests and the
requests went through successfully.
SOLUTION
1. Confirm that there is no CUSTOM.plx exists in $AU_TOP/resource. If any exists then delete it.
2. Take a backup of the current CUSTOM.pll which exists in $AU_TOP/resource.
3. Replace the current CUSTOM.pll with a one from a working instance.
4. Regenerate the CUSTOM.pll and retest the issue.
APPLIES TO:
Oracle Application Object Library - Version 11.5.10.2 to 11.5.10.2 [Release 11.5]
Information in this document applies to any platform.
SYMPTOMS
On 11.5.10.2 in Production:
When attempting to run any request,
the following error occurs:
APP-FND-00222: Encountered an error while getting the ORACLE user account for your concurrent request
The issue can be reproduced at will with the following steps:
1. Submit any request
2. Face the above error
The issue has the following business impact:
Due to this issue, users cannot submit any request.
CHANGES
Recent applying of ATG RUP3 and associated patches
CAUSE
Although there is no customization done but there is some issue in the CUSTOM.pll
This is verified as follows:
1. Log into Apps and Turn OFF "Custom Code" in the Help->Diagnostics menu.
2. After turning off the custom code, it was possible to launch new requests and the
requests went through successfully.
SOLUTION
1. Confirm that there is no CUSTOM.plx exists in $AU_TOP/resource. If any exists then delete it.
2. Take a backup of the current CUSTOM.pll which exists in $AU_TOP/resource.
3. Replace the current CUSTOM.pll with a one from a working instance.
4. Regenerate the CUSTOM.pll and retest the issue.
No comments:
Post a Comment