Vickie pinged me today and told me that after cloning an instance, she was getting this error whenever she tried to login through self service:
"You have encountered an unexpected error. Please contact the System Administrator for assistance."
An examination of Apache and Jserv logs did not show any errors. However $IAS_ORACLE_HOME/Apache/Jserv/logs/jvm/OACoreGroup.0.stderr had these errors:
[Dec 29, 2008 1:48:40 PM EST]:1230576520693:Thread[Thread-29,10,main]:-1:-1:dev.justanexample.com:192.168.10.14:8239:16070UNEXPECTED:[fnd.common.logging.FileHandl
er.publish]:Please check File Permission/Disk Space for: aferror.log, defaulting Logging to STDERR
[Dec 29, 2008 1:51:24 PM EST]:1230576684451:Thread[Thread-101,10,main]:-1:-1:dev.justanexample.com:192.168.10.14:8239:16070UNEXPECTED:[fnd.framework.OAException]:
Application: FND, Message Name: FND_GENERIC_MESSAGE. Tokens: MESSAGE = oracle.apps.fnd.cache.CacheException;
[Dec 29, 2008 1:51:57 PM EST]:1230576717380:Thread[Thread-115,10,main]:-1:-1:dev.justanexample.com:192.168.10.14:8239:16070UNEXPECTED:[fnd.framework.OAException]:
Application: FND, Message Name: FND_GENERIC_MESSAGE. Tokens: MESSAGE = oracle.apps.fnd.cache.CacheException;
[Dec 29, 2008 1:55:39 PM EST]:1230576939360:Thread[Thread-192,10,main]:-1:-1:dev.justanexample.com:192.168.10.14:8239:16070UNEXPECTED:[fnd.framework.OAException]:
Application: FND, Message Name: FND_GENERIC_MESSAGE. Tokens: MESSAGE = oracle.apps.fnd.cache.CacheException;
[Dec 29, 2008 2:00:40 PM EST]:1230577240310:Thread[Thread-295,10,main]:-1:-1:dev.justanexample.com:192.168.10.14:8239:16070UNEXPECTED:[fnd.framework.OAException]:
Application: FND, Message Name: FND_GENERIC_MESSAGE. Tokens: MESSAGE = oracle.apps.fnd.cache.CacheException;
[Dec 29, 2008 2:27:54 PM EST]:1230578874623:Thread[Thread-145,10,main]:-1:-1:dev.justanexample.com:192.168.10.14:8239:16070UNEXPECTED:[fnd.common.logging.DebugEve
ntManager.handlerException]:java.lang.Exception: /aferror.log (Permission denied)
at oracle.apps.fnd.common.logging.FileHandler.(FileHandler.java:103)
at oracle.apps.fnd.common.logging.FileHandler.(FileHandler.java:80)
at oracle.apps.fnd.common.logging.DebugEventManager.registerHandlers(DebugEventManager.java:1241)
at oracle.apps.fnd.common.logging.DebugEventManager.init(DebugEventManager.java:904)
at oracle.apps.fnd.common.logging.DebugEventManager.(DebugEventManager.java:194)
at oracle.apps.fnd.common.AppsLog.(AppsLog.java:519)
at oracle.apps.fnd.common.AppsLog.(AppsLog.java:489)
at oracle.apps.fnd.common.AppsLog.(AppsLog.java:469)
at oracle.apps.fnd.common.AppsContext.makeLog(AppsContext.java:1153)
at oracle.apps.fnd.common.Context.setLog(Context.java:1400)
at oracle.apps.fnd.common.Context.setLog(Context.java:1381)
at oracle.apps.fnd.common.Context.getLog(Context.java:1353)
at oracle.apps.fnd.common.Context.isLoggingEnabled(Context.java:2119)
at oracle.apps.fnd.common.Context.makeConnectionManager(Context.java:655)
at oracle.apps.fnd.common.AppsContext.makeConnectionManager(AppsContext.java:1186)
at oracle.apps.fnd.common.Context.setConnectionManager(Context.java:615)
at oracle.apps.fnd.common.Context.setConnectionManager(Context.java:599)
at oracle.apps.fnd.common.AppsContext.initializeContext(AppsContext.java:880)
at oracle.apps.fnd.common.AppsContext.(AppsContext.java:742)
at oracle.apps.mwa.container.ApplicationsObjectLibrary.AOLInit(ApplicationsObjectLibrary.java:174)
at oracle.apps.mwa.container.ApplicationsObjectLibrary.(ApplicationsObjectLibrary.java:78)
at oracle.apps.mwa.container.MWALib.setObjectLibrary(MWALib.java:339)
at oracle.apps.mwa.wap.engine.WapServlet.init(WapServlet.java:158)
at org.apache.jserv.JServServletManager.load_init(JServServletManager.java:755)
at org.apache.jserv.JServServletManager.loadServlet(JServServletManager.java:659)
at org.apache.jserv.JServServletManager.loadStartupServlets(JServServletManager.java:789)
at org.apache.jserv.JServServletManager.init(JServServletManager.java:447)
at org.apache.jserv.JServ.start(JServ.java:625)
at org.apache.jserv.JServ.main(JServ.java:234)
A search on metalink showed note 418130.1 which gives this cause and solution:
Cause: Un-synchronized data in APPLSYS.WF_LOCAL_USER_ROLES:HZ_PARTY
Solution:
For non-OATM instances:
sql>
begin apps.wf_local_synch.BULKSYNCHRONIZATION(P_ORIG_SYSTEM=>'ALL',
P_PARALLEL_PROCESSES=>2,
P_LOGGING=>'LOGGING', P_RAISEERRORS=>TRUE,
P_TEMPTABLESPACE=>'APPLSYSX'); END; /
For OATM instances:
sql>
begin apps.wf_local_synch.BULKSYNCHRONIZATION(P_ORIG_SYSTEM=>'ALL',
P_PARALLEL_PROCESSES=>2,
P_LOGGING=>'LOGGING', P_RAISEERRORS=>TRUE,
P_TEMPTABLESPACE=>'APPS_TS_TX_DATA');
END;
/
Since we were on an OATM instance, we ran this pl/sql block after logging in as apps:
SQL> begin apps.wf_local_synch.BULKSYNCHRONIZATION(P_ORIG_SYSTEM=>'ALL',
2 P_PARALLEL_PROCESSES=>2,
3 P_LOGGING=>'LOGGING', P_RAISEERRORS=>TRUE,
4 P_TEMPTABLESPACE=>'APPS_TS_TX_DATA'); END;
5 /
PL/SQL procedure successfully completed.
SQL>
There was no need to bounce Apache. After running the above query, we were able to login without issues.
8 comments:
Hi MAN,
I really appreciate your efforts and cant explain how useful this proceudre was.......
very well done!
Thanks
Ahsan
u are goddddd.
how on earth login-screen is showing unknow exception - while problem is un-sync wf data.
God bless oracle...
i have tried your given procedure,but it ddin't work.
Plz help
begin apps.wf_local_synch.BULKSYNCHRONIZATION(P_ORIG_SYSTEM=>'ALL',
P_PARALLEL_PROCESSES=>2,
P_LOGGING=>'LOGGING', P_RAISEERRORS=>TRUE,
P_TEMPTABLESPACE=>'APPS_TS_TX_DATA');
END;
from APPS schema.
waiting for ur reply.
after executing plsql procedure
it gives below errors;
begin apps.wf_local_synch.BULKSYNCHRONIZATION(P_ORIG_SYSTEM=>'ALL',
*
ERROR at line 1:
ORA-12801: error signaled in parallel query server P000
ORA-01452: cannot CREATE UNIQUE INDEX; duplicate keys found
ORA-06512: at "APPS.WF_LOCAL_SYNCH", line 2337
ORA-06512: at line 1
please suggest some solution
You are just superb
hates-off
Regards,
Ajit
I was at a loss with the problem till I found this solution. Hats off to you..!!
Thanks a lot.
Hi 2 All
I face the following error message when i open Receiving function from inventory responsibility (Inventory Responsibility --> Setup --> Receiving -- > Receiving)
You have encountered an unexpected error. Please contact the System Administrator for assistance.
Regards ,
Zulqarnain
Post a Comment