Wednesday, February 5, 2020

Forms Socket to Servlet Mode Convert with Oracle E-Business Suite Release 12

Convert Forms Socket to Servlet Mode

grep connectMode $FORMS_WEB_CONFIG_FILE

$ grep connectMode $FORMS_WEB_CONFIG_FILE

connectMode=socket

   1. Pre heealth checks & Source the environment on the application tier.

   2. Stop all the application and db sevices:
  
   3. Take cold/rman backup and start the DB services

   4. Run the following script to disable Forms Socket Mode and re-enable Forms Servlet Mode:


      $FND_TOP/bin/txkrun.pl -script=ChangeFormsMode -contextfile=$INST_TOP/appl/admin/TEST_testserver.xml -mode=servlet -runautoconfig=No -appspass=<apps>
    
      For example, on UNIX:
      $FND_TOP/bin/txkrun.pl -script=ChangeFormsMode \
      -contextfile=$INST_TOP/appl/admin/mycontext.xml \
      -mode=servlet \
      -runautoconfig=No


      The script prompts for the parameters if they are not passed as command line arguments.

   5. If Autoconfig was not automatically executed as part of the preceding step, then run 
      AutoConfig on the application tier in check/test mode and backup required files

      $AD_TOP/bin/adchkcfg.sh -- Test Mode

      Run Autoconfig

      $INST_TOP/admin/scripts/adautocfg.sh

   6. Start all the application tier services:

      $INST_TOP/admin/scripts/adstrtal.sh

   7. Log in to Oracle Applications as applmgr user 
   
      check whether Forms are in Servlet mode

      grep connectMode $FORMS_WEB_CONFIG_FILE

      $ grep connectMode $FORMS_WEB_CONFIG_FILE
        connectMode=servlet

   8. Do Post health checks.

Increase -XX:MaxPermSize and number of JVMs for oacore in R12

Increase -XX:MaxPermSize and number of JVMs for oacore

1. Shutdown Applications

2. Take Database and Application backup before start activity.

3. Take a backup of the $CONTEXT_FILE.

4. Edit the $CONTEXT_FILE and change the -XX:MaxPermSize parameter on the line below

FROM: 

<oacore_jvm_start_options oa_var="s_oacore_jvm_start_options">-server -verbose:gc 
-Xmx512M -Xms512M -XX:MaxPermSize=160M -XX:NewRatio=2  -XX:+PrintGCTimeStamps -XX:+UseTLAB 
-XX:+UseParallelGC  -XX:ParallelGCThreads=2  -Dcom.sun.management.jmxremote 
-Djava.security.policy=/u01/product/1012/j2ee/oacore/config/java2.policy 
-Djava.awt.headless=true -Dhttp.webdir.enable=false 
-Doracle.security.jazn.config=/u01/inst/apps/TEST_testserver/ora/10.1.3/j2ee/oacore/config/ja
zn.xml</oacore_jvm_start_options>

TO:

oacore_jvm_start_options oa_var="s_oacore_jvm_start_options">-server -verbose:gc 
-Xmx512M -Xms512M -XX:MaxPermSize=256M -XX:NewRatio=2  -XX:+PrintGCTimeStamps -XX:+UseTLAB 
-XX:+UseParallelGC  -XX:ParallelGCThreads=2  -Dcom.sun.management.jmxremote 
-Djava.security.policy=/u01/product/1012/j2ee/oacore/config/java2.policy 
-Djava.awt.headless=true -Dhttp.webdir.enable=false 
-Doracle.security.jazn.config=/u01/inst/apps/TEST_testserver/ora/10.1.3/j2ee/oacore/config/ja
zn.xml</oacore_jvm_start_options>

FROM

<oacore_jvm_stop_options oa_var="s_oacore_jvm_stop_options">-server -verbose:gc 
-Xmx512M -Xms512M -XX:MaxPermSize=160M -XX:NewRatio=2  -XX:+PrintGCTimeStamps -XX:+UseTLAB 
-XX:+UseParallelGC  -XX:ParallelGCThreads=2  
-Djava.security.policy=/u01/product/1012/j2ee/oacore/config/java2.policy 
-Djava.awt.headless=true -Dhttp.webdir.enable=false</oacore_jvm_stop_options>

TO:

<oacore_jvm_stop_options oa_var="s_oacore_jvm_stop_options">-server -verbose:gc 
-Xmx512M -Xms512M -XX:MaxPermSize=256M -XX:NewRatio=2  -XX:+PrintGCTimeStamps -XX:+UseTLAB 
-XX:+UseParallelGC  -XX:ParallelGCThreads=2  
-Djava.security.policy=/u01/product/1012/j2ee/oacore/config/java2.policy 
-Djava.awt.headless=true -Dhttp.webdir.enable=false</oacore_jvm_stop_options>

5. Verify that s_oacore_nprocs is set to 2 on the $CONTEXT_FILE

cat $CONTEXT_FILE|grep s_oacore_nprocs

6. Take a backup of the $INST_TOP/ora/10.1.3/opmn/conf/opmn.xml file.

7. Edit the $INST_TOP/ora/10.1.3/opmn/conf/opmn.xml file and search for the process-type 
id="oacore" and update the following lines or settings under it:

FROM:

 <category id="start-parameters">

                     <data id="java-options" value="-server -verbose:gc 
-Xmx1024M -Xms512M -XX:MaxPermSize=160M -XX:NewRatio=2 -XX:+PrintGCTimeStamps -XX:+UseTLAB 
-XX:+UseParallelGC -XX:ParallelGCThreads=2 -Dcom.sun.management.jmxremote 
-Djava.security.policy=$ORACLE_HOME/j2ee/oacore/config/java2.policy -Djava.awt.headless=true 
-Dhttp.webdir.enable=false 
-Doracle.security.jazn.config=/u01/inst/apps/TEST_testserver/ora/10.1.3/j2ee/oacore/config/ja
zn.xml"/>

TO:

 <category id="start-parameters">

                     <data id="java-options" value="-server -verbose:gc -Xmx512M 
-Xms512M -XX:MaxPermSize=256M -XX:NewRatio=2 -XX:+PrintGCTimeStamps -XX:+UseTLAB 
-XX:+UseParallelGC -XX:ParallelGCThreads=2 -Dcom.sun.management.jmxremote 
-Djava.security.policy=$ORACLE_HOME/j2ee/oacore/config/java2.policy -Djava.awt.headless=true 
-Dhttp.webdir.enable=false 
-Doracle.security.jazn.config=/u01/inst/apps/TEST_testserver/ora/10.1.3/j2ee/oacore/config/ja
zn.xml"/>

FROM:

<category id="stop-parameters">

                     <data id="java-options" value="-server -verbose:gc 
-Xmx1024M -Xms512M -XX:MaxPermSize=160M -XX:NewRatio=2 -XX:+PrintGCTimeStamps -XX:+UseTLAB 
-XX:+UseParallelGC -XX:ParallelGCThreads=2 
-Djava.security.policy=$ORACLE_HOME/j2ee/oacore/config/java2.policy -Djava.awt.headless=true 
-Dhttp.webdir.enable=false"/>

TO:

<category id="stop-parameters">

                     <data id="java-options" value="-server -verbose:gc -Xmx512M 
-Xms512M -XX:MaxPermSize=256M -XX:NewRatio=2 -XX:+PrintGCTimeStamps -XX:+UseTLAB 
-XX:+UseParallelGC -XX:ParallelGCThreads=2 
-Djava.security.policy=$ORACLE_HOME/j2ee/oacore/config/java2.policy -Djava.awt.headless=true 
-Dhttp.webdir.enable=false"/>


FROM:

<process-set id="default_group" numprocs="1"/>

TO:

<process-set id="default_group" numprocs="2"/>

8. Start Applications.

9. Verify Opmn status.

   adopmnctl.sh status

Java Heap Space Issue in R12

SQL> select instance_name from v$instance;

INSTANCE_NAME
----------------
TEST

SQL> select DEVELOPER_PARAMETERS from apps.FND_CP_SERVICES where SERVICE_ID = (select MANAGER_TYPE from apps.FND_CONCURRENT_QUEUES where CONCURRENT_QUEUE_NAME = 'FNDCPOPP');

DEVELOPER_PARAMETERS
-----------------------------------------------------
J:oracle.apps.fnd.cp.gsf.GSMServiceController:-mx512m


SQL> update FND_CP_SERVICES
set DEVELOPER_PARAMETERS =

'J:oracle.apps.fnd.cp.gsf.GSMServiceController:-mx1024m'

where SERVICE_ID = (select MANAGER_TYPE from FND_CONCURRENT_QUEUES

where CONCURRENT_QUEUE_NAME = 'FNDCPOPP');

1 row updated.

SQL> commit;

Commit complete.

SQL> select DEVELOPER_PARAMETERS from apps.FND_CP_SERVICES where SERVICE_ID = (select MANAGER_TYPE from apps.FND_CONCURRENT_QUEUES where CONCURRENT_QUEUE_NAME = 'FNDCPOPP');

DEVELOPER_PARAMETERS
------------------------------------------------------
J:oracle.apps.fnd.cp.gsf.GSMServiceController:-mx1024m

Monday, February 3, 2020

FNDCPASS Error in password verification for APPS in R12

Issue:

[applmgr@dev ~]$ FNDCPASS apps/****** 0 Y system/******SYSTEM APPLSYS apps
Log filename : L5179008.log


Report filename : O5179008.out
[applmgr@dev ~]$ cat L5179008.log
+---------------------------------------------------------------------------+
Application Object Library: Version : 12.0.0

Copyright (c) 1979, 1999, Oracle Corporation. All rights reserved.

 module:
+---------------------------------------------------------------------------+

Current system time is 31-JAN-2020 15:00:00

+---------------------------------------------------------------------------+

Arguments

   FNDCPASS system/***** SYSTEM APPLSYS *****
+----------------------------------------------------------------------------+
Working...
Error in password verification for APPS.

+---------------------------------------------------------------------------+
Concurrent request completed
Current system time is 31-JAN-2020 15:00:00

+---------------------------------------------------------------------------+

Cause:

[oracle@dev ~]$ sqlplus '/as sysdba'

SQL> show parameter case

NAME                                 TYPE        VALUE
------------------------------------ ----------- ------------------------------
sec_case_sensitive_logon             boolean     TRUE

Solution:

[oracle@dev ~]$ sqlplus '/as sysdba'

SQL> alter system set sec_case_sensitive_logon=FALSE;

System altered.

SQL> show parameter case

NAME                                 TYPE        VALUE
------------------------------------ ----------- ------------------------------
sec_case_sensitive_logon             boolean     FALSE

[applmgr@dev ~]$ FNDCPASS apps/******0 Y system/***** SYSTEM APPLSYS apps
Log filename : L5179012.log


Report filename : O5179012.out

[applmgr@dev ~]$ cat L5179012.log
+---------------------------------------------------------------------------+
Application Object Library: Version : 12.0.0

Copyright (c) 1979, 1999, Oracle Corporation. All rights reserved.

 module:
+---------------------------------------------------------------------------+

Current system time is 31-JAN-2020 15:04:26

+---------------------------------------------------------------------------+

Arguments

   FNDCPASS system/***** SYSTEM APPLSYS *****
+----------------------------------------------------------------------------+
Working...

FNDCPASS completed successfully.

+---------------------------------------------------------------------------+
Concurrent request completed successfully
Current system time is 31-JAN-2020 15:04:28

+---------------------------------------------------------------------------+


WARNING: failed to start ASMB (connection failed) in Oracle 12c

Issue:

Starting background process ASMB
Tue Feb 04 05:25:00 2020
ASMB started with pid=37, OS id=19368
WARNING: failed to start ASMB (connection failed) state=0x1 sid=''

Cause:

RMAN CATALOG EXTREMELY SLOW WHEN MIGRATING DATABASE FROM ASM TO FILE SYSTEM
RMAN Restore/Duplicate from ASM to Non ASM in 12.1 take a longer time waiting for the ASMB process.  
Any RMAN command at the mount state which involves Non ASM location can take more time.

Solution:

Apply the patch 19503821, if not available for your version/OS then please log a SR with the support to get the patch for your version.

Ref:
WARNING: failed to start ASMB after RAC Database on ASM converted to Single Instance Non-ASM Database (Doc ID 2138520.1)