Share the content if you found it is useful (You can share using 300 community websites) click "share" at the end of the post.

You are encouraged to leave a comment.








Monday, March 09, 2009

Oracle error &ERRNO: &REASON has been detected in &ROUTINE.

We will be unable to login using none of the seeded users nor custom users. Applications will not allow any user to be logged in.

For a VISION instance(only), if the Profile option "MO: Operation Unit" (short name for this profile options is ORG_ID) is changed to any other value apart from "Vision Operations", we encounter the above specified error.

Another place where we can check the error is when we run adstrtal.sh or adstpall.sh scripts. The following errors can be found in the log file:

Oracle error -20001: ORA-20001: FND-ORG_ID PROFILE CANNOT READ: N, OPTION, MO: Operating Unit has been detected in FND_GLOBAL.INITIALIZE.
Solution

Following are steps to change the profile option from backend:

1. Get the Profile option ID using the following query:

SQL> Select PROFILE_OPTION_ID,PROFILE_OPTION_NAME from fnd_profile_options
where PROFILE_OPTION_NAME ='ORG_ID';

Example:
SQL> Select PROFILE_OPTION_ID,PROFILE_OPTION_NAME from fnd_profile_options
where PROFILE_OPTION_NAME ='ORG_ID';

2
PROFILE_OPTION_ID
-----------------
PROFILE_OPTION_NAME
--------------------------------------------------------------------------------
1991

ORG_ID


2. Run the following procedure which changes the profile option: Use 1991 as the PROFILE_ID

DECLARE
stat boolean;
BEGIN
dbms_output.disable;
dbms_output.enable(100000);
stat := FND_PROFILE.SAVE('ORG_ID',(enter the Profile ID from above query), 'SITE');
IF stat THEN
dbms_output.put_line( 'Stat = TRUE - profile updated' );
ELSE
dbms_output.put_line( 'Stat = FALSE - profile NOT updated' );
END IF;
commit;
END;

3) Restart the apache server

No comments:

Related Posts Plugin for WordPress, Blogger...

Let us be Friends...

Share |

Popular Posts

Recent Comments