Friday, April 10, 2020

Adding and tuning oacore_server to EBS 12.2

Adding and tuning  oacore_server to EBS 12.2
Reference
Managing Configuration of Oracle HTTP Server and Web Application Services in Oracle E-Business Suite Release 12.2 (Doc ID 1905593.1)
4.4 Customizing the Number of Instances of a Particular Service Type
  • Preparation
From Run Identify the Used port that you will create another one like it for the new service
more $CONTEXT_FILE |grep s_wls_oacoreport
<wls_oacoreport oa_var=”s_wls_oacoreport” oa_type=”PORT” base=”7201″ step=”1″ range=”-1″ label=”WLS OACORE Application Port”>7203</wls_oacoreport>
** Note that PATCH use another Port that you should not use the same
PATCH was 7202,then we will use for patch 7204
For RUN we will use 7205
Or you can identify from Console
.Running Service
Adminsrvctl UP RUN
Backup your Context
cp PRD_asv-prdap11.xml PRD_asv-prdap11.xml_befAdd

  • Adding oacore_server2
perl $AD_TOP/patch/115/bin/adProvisionEBS.pl ebs-create-managedserver -contextfile=/u01/PRD/fs1/inst/apps/PRD_asv-prdap11/appl/admin/PRD_asv-prdap11.xml -managedsrvname=oacore_server2 -servicetype=oacore -managedsrvport=7205 -logfile=/tmp/oacoreadd1.log
Enter the APPS Schema password:
Enter the WebLogic AdminServer password:
Start the new created server
admanagedsrvctl.sh start oacore_server2
Identify your hostnamings
more $CONTEXT_FILE |grep s_oacore_nodes
<oacore_nodes oa_var=”s_oacore_nodes”>asv-prdap11.corp.beone.net:7203</oacore_nodes>
add details of the newly added managed servers into the OHS configuration files on all nodes participate the cluster
perl $FND_TOP/patch/115/bin/txkSetAppsConf.pl -contextfile=/u01/PRD/fs1/inst/apps/PRD_asv-prdap11/appl/admin/PRD_asv-prdap11.xml -configoption=addMS -oacore=asv-prdap11.corp.beone.net:7205
  • Bouncing
adapcctl.sh start
adstpall.sh apps/q3AcPEhG
wait until adRegisterWLSListeners.pl is finished(it is updating the Context file with all WLS Changes)
adadminsrvctl.sh start
Update Context
<oacore_jvm_start_options oa_var=”s_oacore_jvm_start_options”>-d64 -Xms2048m -Xmx2048m -XX:CompileThreshold=8000 -XX:PermSize=128m -XX:MaxPermSize=256m….
<nm_jvm_startup_properties oa_var=”s_nm_jvm_startup_properties” osd=”Solaris”>-d64 -Xms4096m -Xmx4096m -XX:CompileThreshold=8000 -XX:PermSize=128m -XX:MaxPermSize=256m
Run Autoconfig on Apps tier
Stop adminsrv then startall

No comments:

Post a Comment

[ERROR]: The value of s_patch_service_name is not set correctly in atleast one of the context files.

[ERROR]: The value of s_patch_service_name is not set correctly in atleast one of the context files. I got the issue below wh...