Tuesday, August 9, 2016

New Feature - Oracle EBS 12.2.5 Application Tier Cloning With Dualfs Option

In Oracle EBS 12.2.2, 12.2.3 & 12.2.4, application tier cloning has to be done for each RUN & PATCH file systems separately.

But now in Oracle EBS 12.2.5, application tier cloning for both RUN & PATCH file systems can be done at once by using the new feature option dualfs as follows. This is very useful in reducing the time required for cloning.

Let's assume source instance RUN file system is fs2.
Then copy the source instance fs2 RUN file system EBSapps directory to target instance fs2 directory. After the cloning, fs2 will become the RUN file system of the instance and fs1 will become PATCH file system  automatically.

$ perl adcfgclone.pl appsTier dualfs

Saturday, July 16, 2016

Patch Timeout in Jsp Compilation During the TXK delta 7 Upgrade

Error

During the TXK delta 7 upgrade while applying following patches below error occurs in jsp compilation.
adop phase=apply patches=20784380,22363475,22495069 merge=yes
   
[root@test Desktop]# tail -f /u01/TEST/fs2/inst/apps/TEST_ebis/logs/appl/rgf/ojsp/ojspc_error.log
[14052] compiling: 7s elapsed, 50 successful 0 failed
[14052] compiling: 7s elapsed, 50 successful 0 failed
[14052] compiling: 6s elapsed, 50 successful 0 failed
[14052] compiling: 7s elapsed, 50 successful 0 failed
[14052] compiling: 7s elapsed, 50 successful 0 failed
[14052] compiling: 6s elapsed, 50 successful 0 failed
[14052] compiling: 7s elapsed, 50 successful 0 failed
[14052] compiling: 6s elapsed, 50 successful 0 failed
[14052] compiling: 7s elapsed, 50 successful 0 failed
[14052] compiling: 6s elapsed, 50 successful 0 failed
[14052] compiling: 7s elapsed, 50 successful 0 failed
[14052] compiling: 7s elapsed, 50 successful 0 failed
[14052] compiling: 6s elapsed, 50 successful 0 failed
[14052] !!SEVERE WARNING!! TIMEOUT[600 seconds] EXPIRED DURING COMPILATION

Solution
Set ojspCompile.conf files in fs1 and fs2 java_home to respective values as below.

/u01/TEST/fs1/inst/apps/TEST_ebis/appl/admin/ojspCompile.conf
/u01/TEST/fs2/inst/apps/TEST_ebis/appl/admin/ojspCompile.conf

java_home = /u01/TEST/fs1/EBSapps/comn/util/jdk64
java_home = /u01/TEST/fs2/EBSapps/comn/util/jdk64

Then execute below to proceed with jsp compilation;

[oratest@test TEST]$ strace -t -o jspcompile.txt perl -x $FND_TOP/patch/115/bin/ojspCompile.pl --compile -p 6 -log /tmp/ojspCompile.log
logfile set: /tmp/ojspCompile.log
starting...(compiling delta)
using 10i internal ojsp ver: 10.3.6.0
synchronizing dependency file:
  loading deplist...7829
  enumerating jsps...7829
  updating dependency...0
initializing compilation:
  eliminating children...5954 (-1875)
  searching uncompiled...4529
translating and compiling:
  searching untranslated...0  
  compiling jsps...4529/4529 in 11m55s                
Finished!

Then execute the adop phase=apply patches=20784380,22363475,22495069 merge=yes restart=yes

Sunday, July 10, 2016

Upgrade Oracle FMW WebTier of Oracle EBS 12.2 to 11gR1 PatchSet 6 (11.1.1.7)

Upgrading the Oracle Fusion Middleware WebTier of Oracle E-Business Suite Release 12.2 to 11gR1 PatchSet 6 (11.1.1.7) (Doc ID 2002603.1)

Friday, July 8, 2016

Exception in thread "main" java.lang.OutOfMemoryError: Java heap space in Weblogic Patch application


$ sh bsu.sh -prod_dir=/u01/TEST/fs2/FMW_Home/wlserver_10.3 -patchlist=EJUW -verbose -install
Checking for conflicts....
Conflict(s) detected - resolve conflict condition and execute patch installation again
Conflict condition details follow:
Patch EJUW is mutually exclusive and cannot coexist with patch(es): Y5AP,BLTG,FCX7,1LRI,VKXF,2GYW,CW9T
Exception in thread "main" java.lang.OutOfMemoryError: Java heap space
    at java.util.AbstractCollection.toArray(AbstractCollection.java:136)
    at java.util.ArrayList.addAll(ArrayList.java:530)
    at org.apache.xmlbeans.impl.schema.SchemaTypeImpl.getProperties(SchemaTypeImpl.java:705)
    at com.bea.cie.common.dao.xbean.XBeanDataHandler.loadPropertyMap(XBeanDataHandler.java:775)
    at com.bea.cie.common.dao.xbean.XBeanDataHandler.<init>(XBeanDataHandler.java:99)
    at com.bea.cie.common.dao.xbean.XBeanDataHandler.createDataHandler(XBeanDataHandler.java:559)
    at com.bea.cie.common.dao.xbean.XBeanDataHandler.getComplexValue(XBeanDataHandler.java:455)
    at com.bea.plateng.patch.dao.cat.PatchCatalogHelper.getPatchDependencies(PatchCatalogHelper.java:442)
    at com.bea.plateng.patch.dao.cat.PatchCatalogHelper.getPatchDependencies(PatchCatalogHelper.java:464)
    at com.bea.plateng.patch.dao.cat.PatchCatalog.getPatchDependencies(PatchCatalog.java:56)
    at com.bea.plateng.patch.dao.cat.PatchCatalogHelper.getInvalidatedPatchMap(PatchCatalogHelper.java:1621)
    at com.bea.plateng.patch.PatchSystem.updatePatchCatalog(PatchSystem.java:436)
    at com.bea.plateng.patch.PatchSystem.refresh(PatchSystem.java:130)
    at com.bea.plateng.patch.PatchSystem.setCacheDir(PatchSystem.java:201)
    at com.bea.plateng.patch.Patch.main(Patch.java:306)

Solution:
1.  Go to /%FMW_Home%/utils/bsu/
2.  Edit the bsu.sh
3.  Here you will find the following: MEM_ARGS="-Xms256m -Xmx512m"
4.  Increase these values to "-Xms1024m -Xmx1024m"

Reference:
Java.lang.OutOfMemoryError" Error When Applying Oracle Weblogic Server Patch (Doc ID 2007492.1)

Wednesday, May 11, 2016

Migrating Oracle E-Business Suite R12 from Linux 32-bit to Linux 64-bit - Docs

Migrating Oracle E-Business Suite R12 from Linux 32-bit to Linux 64-bit (Doc ID 471566.1)
Cloning Oracle Applications Release 12 with Rapid Clone (Doc ID 406982.1)
Using Oracle EBS R12 with a Database Tier Only Platform on Oracle 11gR1 (Doc ID 762669.1)
Migrating OLAP From 32 Bits to 64 Bits or Across Platforms (Doc ID 352306.1)

Wednesday, May 4, 2016

Oracle EBS 12.2.5 Reference Docs

Oracle E-Business Suite Release Notes, Release 12.2 (Doc ID 1320300.1)
Oracle E-Business Suite Release 12.2.5 Readme (Doc ID 1983050.1)
Oracle E-Business Suite Installation and Upgrade Notes Release 12 (12.2) for Linux x86-64 (Doc ID 1330701.1)
Applying the Latest AD and TXK Release Update Packs to Oracle E-Business Suite Release 12.2 (Doc ID 1617461.1)
Oracle E-Business Suite Release 12.2: Consolidated List of Patches and Technology Bug Fixes (Doc ID 1594274.1)

Oracle EBS Workflow Notification Mailer with Cloud E-Mail Servers

Configuring an Oracle Workflow Notification Mailer with Cloud E-Mail Servers (Doc ID 2077434.1)

Query to get the workflow notification mailer logfile to troubleshoot issues.

select fl.meaning,fcp.process_status_code,
decode(fcq.concurrent_queue_name,'WFMLRSVC','mailer container','WFALSNRSVC','listener container',fcq.concurrent_queue_name) "CONTAINER",
fcp.concurrent_process_id,os_process_id, fcp.logfile_name
from fnd_concurrent_queues fcq, fnd_concurrent_processes fcp , fnd_lookups fl
where fcq.concurrent_queue_id=fcp.concurrent_queue_id and fcp.process_status_code='A'
and fl.lookup_type='CP_PROCESS_STATUS_CODE' and
fl.lookup_code=fcp.process_status_code
and concurrent_queue_name in('WFMLRSVC','WFALSNRSVC')
order by fcp.logfile_name;

Saturday, March 5, 2016

How to find Oracle EBS Weblogic Server Admin Port Number and URL

Web Logic Server Admin Port 

 Method 1:

Open the EBS domain config file in following location.
$EBS_DOMAIN_HOME/config/config.xml

Then check for Admin Server Port.

Method 2:

Open the application tier context file
$CONTEXT_FILE

Then check the value of variable "s_wls_adminport" in the for the correct Web Logic Server Admin port number

Web Logic Server Console URL

http://<server name>. <domain name> : < WLS Admin Port>/console
For example. http://oracle.test.com:7003/console

Steps to Change Oracle Weblogic Server Node Manager & Administration User Password



The option to set the Oracle WebLogic Server Administration User password to a
non-default value is available during Oracle E-Business Suite installation. This section
describes the procedure to use (on the run file system) if you need to change the
password at a later time.


The EBS WebLogic Domain uses Node Manager to control the Administration Server
and the managed servers. For the EBS WebLogic Domain, the Node Manager and
WebLogic Server Administration User passwords must be same, otherwise the AD
control scripts will not work properly.


Important: 

If you need to change the Administration User password, you must change the Node Manager password first, If you do not do this, the WebLogic Server configuration change will not be detected and the next online patching cycle may fail.

The instructions that follow should be performed on the run file system. The password

change will be automatically propagated to the patch file system during the next adop

prepare phase or fs_clone operation.


1.Shut down all application tier services except the Admin Server.

On the primary node, run the command:
$ <ADMIN_SCRIPTS_HOME>/adstpall.sh -skipNM -skipAdmin

2. Change the Oracle WebLogic Server Node Manager and Administration User passwords by performing the following steps on weblogic console

Changing the Oracle WebLogic Server Node Manager Password

-Login to weblogic to server console: 


 

- Login using the current weblogic admin username and  password.

- Click on the lock and edit button



- Click on Domain link
- Click on Security TAB
   


- Click on "Advanced" Tab
- Provide the new node manager  password which you want to configure for weblogic admin user



- Click on "save"

 

- Verify settings updated successfully and then click on "Activate changes"

- Verify all changes has been activated successfully.

Changing the Oracle WebLogic Server Administration User Password

- Click on "Security Realms"
- Click on "myrealm"



-  select "users and groups" and select weblogic User: