R12 Check Writer XML process failed.

R12 Check Writer XML process failed

Issue:


When attempting to run the Check Writer XML process, the following error occurs.

stat_low = 86
stat_high = 0
emsg:was terminated by signal 6
/test/appltest/apps/apps_st/appl/pay/12.0.0/bin/PYUGEN
Program exited with status -1


Cause:


This issue is generally encountered after cloning. Main reason for this is wrong value of the DBC_FILE parameter in View "PAY_ACTION_PARAMETERS".


Use the following SQL Query to find the Value:

select length(parameter_value), Length(trim(parameter_value)), parameter_value from pay_action_parameters where parameter_name = 'DBC_FILE';



Solution:



1. Run the following query to confirm the extra space(s) in the DBC file parameter value

Query:    

select length(parameter_value), Length(trim(parameter_value)), parameter_value from pay_action_parameters where parameter_name = 'DBC_FILE';



2. Modify the DBC file parameter value in PAY_ACTION_PARAMETERS.

Query:

UPDATE "APPS"."PAY_ACTION_PARAMETERS" SET PARAMETER_VALUE = '<Correct DBC Path>/FileName.dbc';



3. Retest the issue.



4. Confirm the result.

R12 Login Page issue: Java.Lang.OutOfMemoryError: Java Heap Space Error

 R12 Login Page issue: Java.Lang.OutOfMemoryError: Java Heap Space Error

Issue:

We were facing issue in our R12 (12.1.3) E-business suite environment, where all of sudden users were not able to get the login page but existing users were able to use forms/navigate between forms, but not able to use JSP pages. After investigation, we came to know the root cause of the issue.

Log File Location: $INST_TOP/logs/ora/10.1.3/opmn/oacore_default_group_1/oacorestd.err


14/08/12 12:21:51 java.lang.OutOfMemoryError: Java heap space

14/08/12 12:23:05 java.lang.OutOfMemoryError: GC overhead limit exceeded

Solution:

Reset the Java Heap Size in your R12 application server.

Step 1: Identify the maximum Heap Size you can set in your server.

applprod@server:~$ java -mx4096m -version

Invalid maximum heap size: -Xmx4096m

The specified size exceeds the maximum representable size.

Could not create the Java virtual machine.

applprod@server:~$ java -mx3048m -version

java version "1.6.0_10"

Java(TM) SE Runtime Environment (build 1.6.0_10-b33)

Java HotSpot(TM) Server VM (build 11.0-b15, mixed mode)

From this output, we can say maximum 3 GB Java Heap Size can be set in our server.

Step 2: Edit opmn.xml file.

Location : $INST_TOP/ora/10.1.3/opmn/conf/

Edit opmn.xml file for the following parameters (Xms & Xmx)

Search for string Xms or Xmx or module-id=”OC4J”

This search should lead you to below location

‘<‘process-type id=”oacore” module-id=”OC4J” status=”enabled” working-dir=”$ORACLE_HOME/j2ee/home”‘>’
‘<‘category id=”start-parameters”‘>’
‘<‘data id=”java-options” value=”-server -verbose:gc -Xmx512M -Xms128M ……]

The default value for Maximum (-Xmx) and Minimum (-Xms) heap sizes are 512M and 128M respectively.

Again here you have options, you can set both Xms and Xmx has the same value as Xmx if you feel all your sessoins require higher memory or set a lower value for Xms and the maximum value for Xmx. Dont forget to change the values under ‘<‘category id=”stop-parameters”‘>’

opmn.xml also contains jvm configurations for other components – oafm & forms.

Step 3: Edit oc4j.properties file.

Location : ($INST_TOP/ora/10.1.3/j2ee/oacore/config)

This step is optional since we had already made changes in opmn.xml but there is no harm in making the change here. This step will come handy for troubleshooting specific components of Oracle viz., configurator, iSupplier or any other option which heavily utilizes/consumes CPU/memory.

Search for string Xms or Xmx or wrapper.

Option 1: If you find any of the above parameters change the values corresponding to the value you had  mentioned in opmn.xml or even more than that, as long as you dont exceed the maximum heap size limit.

Option 2: If you DO NOT find any of the above parameters, then make an entry like this, under the heading “Java Object Cache Configuration Parameters”

wrapper.bin.parameters=-Xms[Value]M -Xmx[Value]M -XX:NewSize=256M -XX:MaxNewSize=256M

Step 4: Edit Applications Context file

vi $CONTEXT_FILE

Location: $INST_TOP/appl/admin/SID_hostname.xml

search for string s_oacore_jvm_start_options

Change Xms and Xmx value. Repeat the same step for parameter s_oacore_jvm_stop_options.

Create tar file

Create tar file

tar -zvcf file.tar.gz file1 file2 dir1 dir2
eg :-  tar -zcvf CLN_12_1_3_AR.tar.gz CLN_12_1_3_AR


>> Details of tar :-
tar -tvf backup.tar.gz

>> UNTAR in current location
tar -xvf <file>.tar.gz

>> UNTAR in one particular directory
tar -xvf <file>.tar.gz -C /Oracle/test2
eg :-  tar -xvf test_bkp-31Dec13.tar.gz -C /Oracle/test_bkp2

Responsibilities not showing for user

Responsibilities not showing for user

We added one responsibility to a user and wasn't not showing up.

Solution:

Run program 'Workflow Directory Services User/Role Validation' with following parameters.

Note:
Optionally, we can also run 'Synchronize WF LOCAL tables' after this request completes.

11g Background Processes

11g Background Processes


New background processes in 11g. As per Oracle documentation there are 56 new background processes added in 11g release 1

Some Important background Process

MMAN - this process is responsible for ASMM in 10g and AMM in 11g  which manages memory allocation to SGA and PGA

RCBG - this background process is responsible for processing data into server result cache

DIAG - In 11g we have a single location for all the trace files, alert log and other diagnostic files. DIAG is the process which performs  diagnostic dumps and executes oradebug commands

DIA0 – responsible for hang detection and deadlock resoultion

DBRM – Database resource manager is responsible for setting plans to users and all other database resource management activities

EMNC – Event Monitor Coordinator will coordinate with event management and notification activity

FBDA – Flashback Data Archiver process is responsible for all flashback related actions in 11g database

GEN0 - General task execution process which performs required tasks

SMCo – Space management coordinator executes various space management tasks like space reclaiming, allocation etc. It uses slave processes Wnnn whenever required

VKTM – Virtual keeper of time is  responsible for keeping track of the wall-clock time and used as a reference-time counter