How To Prevent the Profile Option MO: Operating Unit Being Set to NULL at Site Level?
(Doc ID 393560.1)
Last updated on DECEMBER 06, 2017
Applies to:
Oracle Application Object Library - Version 11.5.10.2 to 12.2 [Release 11.5 to 12.2]Information in this document applies to any platform.
FORM:FNDPOMPV.FMB - Update System Profile Values
Goal
The profile option MO: Operating Unit is crucial in a Multi-Org environment. It is a requirement to have a profile option value at Site level at all times because the application will be inaccessible without it. Not a single application user will be able to login to system using their application User Name. Not even the System Administrator (SYSADMIN) will be able to login to restore the profile option value in case someone accidentally removed it.
Exception encountered at login (AppsLogin):
You have encountered an unexpected error. Please contact the System Administrator for assistance. Click here for exception details.
The exception details are the following:
oracle.apps.fnd.framework.OAException: Application: FND, Message Name: SQL_PLSQL_ERROR. Tokens: ROUTINE = AppsConnectionManager.appsInitialize(int,int,int,int,Connection):-1,-1,-1,0,oracle.jdbc.driver.OracleConnection@1106021; REASON = java.sql.SQLException: ORA-20001: Oracle error -20001: ORA-20001: FND-ORG_ID PROFILE CANNOT READ: N, OPTION, MO: Operating Unit has been detected in FND_GLOBAL.INITIALIZE. ORA-06512: at "APPS.APP_EXCEPTION", line 72 ORA-06512: at "APPS.FND_GLOBAL", line 101 ORA-06512: at "APPS.FND_GLOBAL", line 1147 ORA-06512: at "APPS.FND_GLOBAL", line 620 ORA-06512: at line 1 ; ERRNO = 20001; at oracle.apps.fnd.framework.server.OAExceptionUtils.processAOLJErrorStack(OAExceptionUtils.java:988) at oracle.apps.fnd.framework.OACommonUtils.processAOLJErrorStack(OACommonUtils.java:866) at oracle.apps.fnd.framework.webui.OAPageBean.validateUser(OAPageBean.java:4656) at oracle.apps.fnd.framework.webui.OAPageBean.preparePage(OAPageBean.java:697) ... at org.apache.jserv.JServConnection.processRequest(JServConnection.java:456) at org.apache.jserv.JServConnection.run(JServConnection.java:294) at java.lang.Thread.run(Thread.java:595) ## Detail 0 ## oracle.apps.fnd.framework.OAException: Application: FND, Message Name: FND_GENERIC_MESSAGE. Tokens: MESSAGE = java.sql.SQLException: ORA-20001: Oracle error -20001: ORA-20001: FND-ORG_ID PROFILE CANNOT READ: N, OPTION, MO: Operating Unit has been detected in FND_GLOBAL.INITIALIZE. ORA-06512: at "APPS.APP_EXCEPTION", line 72 ORA-06512: at "APPS.FND_GLOBAL", line 101 ORA-06512: at "APPS.FND_GLOBAL", line 1147 ORA-06512: at "APPS.FND_GLOBAL", line 620 ORA-06512: at line 1 ; at oracle.apps.fnd.framework.OAException.wrapperException(OAException.java:905) at oracle.apps.fnd.framework.OAException.wrapperException(OAException.java:879) at oracle.apps.fnd.framework.server.OAExceptionUtils.processAOLJErrorStack(OAExceptionUtils.java:980) at oracle.apps.fnd.framework.OACommonUtils.processAOLJErrorStack(OACommonUtils.java:866) ... at org.apache.jserv.JServConnection.processRequest(JServConnection.java:456) at org.apache.jserv.JServConnection.run(JServConnection.java:294) at java.lang.Thread.run(Thread.java:595) ## Detail 0 ## java.sql.SQLException: ORA-20001: Oracle error -20001: ORA-20001: FND-ORG_ID PROFILE CANNOT READ: N, OPTION, MO: Operating Unit has been detected in FND_GLOBAL.INITIALIZE. ORA-06512: at "APPS.APP_EXCEPTION", line 72 ORA-06512: at "APPS.FND_GLOBAL", line 101 ORA-06512: at "APPS.FND_GLOBAL", line 1147 ORA-06512: at "APPS.FND_GLOBAL", line 620 ORA-06512: at line 1 at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:134) at oracle.jdbc.ttc7.TTIoer.processError(TTIoer.java:289) at oracle.jdbc.ttc7.Oall7.receive(Oall7.java:589) ... at org.apache.jserv.JServConnection.run(JServConnection.java:294) at java.lang.Thread.run(Thread.java:595) oracle.apps.fnd.framework.OAException: Application: FND, Message Name: FND_GENERIC_MESSAGE. Tokens: MESSAGE = java.sql.SQLException: ORA-20001: Oracle error -20001: ORA-20001: FND-ORG_ID PROFILE CANNOT READ: N, OPTION, MO: Operating Unit has been detected in FND_GLOBAL.INITIALIZE. ORA-06512: at "APPS.APP_EXCEPTION", line 72 ORA-06512: at "APPS.FND_GLOBAL", line 101 ORA-06512: at "APPS.FND_GLOBAL", line 1147 ORA-06512: at "APPS.FND_GLOBAL", line 620 ORA-06512: at line 1 ; at oracle.apps.fnd.framework.OAException.wrapperException(OAException.java:905) at oracle.apps.fnd.framework.OAException.wrapperException(OAException.java:879) at oracle.apps.fnd.framework.server.OAExceptionUtils.processAOLJErrorStack(OAExceptionUtils.java:980) ... at org.apache.jserv.JServConnection.run(JServConnection.java:294) at java.lang.Thread.run(Thread.java:595) ## Detail 0 ## java.sql.SQLException: ORA-20001: Oracle error -20001: ORA-20001: FND-ORG_ID PROFILE CANNOT READ: N, OPTION, MO: Operating Unit has been detected in FND_GLOBAL.INITIALIZE. ORA-06512: at "APPS.APP_EXCEPTION", line 72 ORA-06512: at "APPS.FND_GLOBAL", line 101 ORA-06512: at "APPS.FND_GLOBAL", line 1147 ORA-06512: at "APPS.FND_GLOBAL", line 620 ORA-06512: at line 1 at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:134) at oracle.jdbc.ttc7.TTIoer.processError(TTIoer.java:289) at oracle.jdbc.ttc7.Oall7.receive(Oall7.java:589) at oracle.jdbc.ttc7.TTC7Protocol.doOall7(TTC7Protocol.java:1972) at oracle.jdbc.ttc7.TTC7Protocol.parseExecuteFetch(TTC7Protocol.java:1119) ...
Error encountered within the forms application while trying to open any form:
Oracle error -20001: ORA-20001: FND-ORG_ID PROFILE CANNOT READ: N, OPTION, MO Operating Unit has been detected in FND_GLOBAL.INITIALIZE.
Note: The above listed exceptions and errors were gathered from an Oracle E-Business Suite 11i (11.5.10) environment. Quite likely, there will be some slight variations in terms of line numbers etc. on other releases such as Release 12.
Solution
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Goal |
| Solution |
| Prerequisites |
| Setup steps |
| Result |
| References |