Tuesday, September 17, 2013

Missing responsibilities in R12.1.3

SYMPTOMS :

When a new responsibility is added, it doesn't show up in the home page. The same problem happens even after clearing cache and removing cookies. Workflow Directory tables don't show corruption.

CAUSE :

LONG_RUNNING_JVM parameter was set to FALSE. TRUE is recommended value for R12.1.3.

This was the value for this parameter.
$ cd $ORA_CONFIG_HOME/10.1.3/j2ee/oacore/config
$ grep -i long_running oc4j.properties
LONG_RUNNING_JVM=false

Since the cache was not refreshed, the responsibilities didn't show up in the home page.

SOLUTION

 To implement the solution, please execute the following steps:

1. Change the LONG_RUNNING_JVM parameter to TRUE in the context file and run the autoconfig

2. Make sure the change is propagated to oc4j.properties
$ cd $ORA_CONFIG_HOME/10.1.3/j2ee/oacore/config
$ grep -i long_running oc4j.properties

Note: verify the changes on both
[oracle@svruatebsal1 ~]$  grep -i long_running $CONTEXT_FILE
                        <jms_cache oa_var="s_long_running_jvm">true</jms_cache>

[oracle@svruatebsal1 ~]$  cd $ORA_CONFIG_HOME/10.1.3/j2ee/oacore/config

[oracle@svruatebsal1 config]$ grep -i long_running oc4j.properties
                                    LONG_RUNNING_JVM=true

3. Bounce oafm

sh $ADMIN_SCRIPTS_HOME/adoafmctl.sh stop
sh $ADMIN_SCRIPTS_HOME/adoafmctl.sh start

4. Retest the issue.

5. Migrate the solution as appropriate to other environments.


+++++++++++(Doc ID 1423432.1) +++++++++++
Troubleshooting Missing Responsibilities For A User (Doc ID 429852.1)

No comments:

Post a Comment