1. You have encountered an unexpected error. Please contact the System Administrator for assistance
Cause: Un-synchronized data in APPLSYS.WF_LOCAL_USER_ROLES:HZ_PARTY .A search on metalink showed note 418130.1 which gives this cause and solution:
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.
2. FRM-40735: WHEN-BUTTON-PRESSED trigger raised unhandled exception ORA-29516
A conflict between some java operations when using the Repository Assistant and JIT java compiler.
Turning off the JIT java compiler allows the Workspace to be created without error:
1. Log onto SQLPlus as a DBA account.
2. alter system set java_jit_enabled=false;
3. Retest the issue.
JAVA_JIT_ENABLED
enables or disables the Just-in-Time (JIT) compiler for the Oracle Java Virtual Machine (OracleJVM) environment.
For platforms that support the JIT compiler, the default value of this parameter is true
; otherwise the default value is false
. Attempting to set this parameter to true
on unsupported platforms will result in an error.
The JIT is a compiler that has been introduced in 11g for faster compilation of java code. Prior to 11g, NCOMP (aka JAccelerator) was being used.
With JIT disabled, you may encounter some slowness when compiling and running your java stored procedures if you have any.
3.Login Fails Intermittently With: Application: Fnd, Message Name: oracle.apps.fnd.framework.OAException: Application: FND, Message Name: FND_NO_DATABASE_CONNECTION [ID 1298103.1]
12.1.3 Customers
Apply and test patch 11832737
Be sure to stop and start application tier services after the patch is applied
4. SR 3-2988921361: Workflow Monitor Status Diagram Failure to Display in R12 instance
Setting the value of "ICX:Forms Launcher" profile to one of the forms URL (instead of load balancer URL) for Workflow Admin responsibility is only a temporary solution.