App-Fnd-00222 Whe attempting to run any request [ID 412987.1] | |||||
Modified 05-OCT-2008 Type PROBLEM Status MODERATED |
This document is being delivered to you via Oracle Support's Rapid Visibility (RaV) process, and therefore has not been subject to an independent technical review. |
Applies to:
Oracle Application Object Library - Version: 11.5.10.2This problem can occur on 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
STEPS
The issue can be reproduced at will with the following steps:
1. Submit any request
2. Face the above error
BUSINESS IMPACT
The issue has the following business impact:
Due to this issue, users cannot submit any request.
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
STEPS
The issue can be reproduced at will with the following steps:
1. Submit any request
2. Face the above error
BUSINESS IMPACT
The issue has the following business impact:
Due to this issue, users cannot submit any request.
Changes
Recent applying of ATG RUP3 and associated patchesCause
Although there is no customization done but there is some issue in the CUSTOM.pll
This is verified as follows
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.
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
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
![]() Products
|
This comment has been removed by a blog administrator.
ReplyDelete