FMW 11.1.1.7.0 - Applying Patch 18182516: UTF-8 CHARACTERS E3 E80 E81 NOT RECOGNIZED PROPERLY BY B2B

FMW 11.1.1.7.0 - Applying Patch 18182516: UTF-8 CHARACTERS E3 E80 E81 NOT RECOGNIZED PROPERLY BY B2B

- Download the patch zip file p18182516_111170_Linux-x86-64.zip and copy it onto the staging area of the server say PATCH_TOP with appropriate permissions

- Set ORACLE_HOME to SOA Home  

export ORACLE_HOME=$MW_HOME/Oracle_SOA1

- Stop Mid Tier services


Applying Patch


- Unzip the patch zip file into the PATCH_TOP and set current directory to PATCH_TOP/18182516

   $unzip -d PATCH_TOP p18182516_111170_Linux-x86-64.zip

   $cd PATCH_TOP/18182516

- Execute 'setenv OPATCH_PLATFORM_ID 226'

- Run OPatch to apply the patch

   $opatch apply


Post patching

- Backup existing $ORACLE_HOME/soa/thirdparty/edifecs

- unzip and untar XEngine_7_0_5_21.tar.gz to $ORACLE_HOME/soa/thirdparty/edifecs

- Restart all servers (AdminServer and all Managed servers).


Rollback Patch

If any issues post patching and a rollback is required, follow below steps:

- Stop Mid Tier services and set current directory to PATCH_TOP/18182516

   $cd PATCH_TOP/18182516

- Run OPatch rollback

   $opatch rollback -id 18182516

- Restore backup of $ORACLE_HOME/soa/thirdparty/edifecs

- Restart all servers (AdminServer and all Managed servers)


Related Posts:

FMW 11.1.1.7.0 - Applying Oracle Jdeveloper Patch 20265562: MERGE REQUEST ON TOP OF 11.1.1.7.0 FOR BUGS 19890682 14047857 16632043

Applying Patch 20900797: SOA Bundle Patch 11.1.1.7.8

Applying Patch 20423535: SOA Bundle Patch 11.1.1.7.7

Applying Patch 19953598: SOA Bundle Patch 11.1.1.7.6

Applying Patch 19190139 SOA BUNDLE PATCH 11.1.1.7.5

Applying Patch 18609527 SOA BUNDLE PATCH 11.1.1.7.4

Applying Patch 18072286 SOA BUNDLE PATCH 11.1.1.7.3

Applying Patch 17584181 SOA BUNDLE PATCH 11.1.1.7.2

Applying Patch 20900599: SOA Bundle Patch 12.1.3.0.3

Applying Patch 19190139 SOA BUNDLE PATCH 11.1.1.7.5

Applying Patch 19190139 SOA BUNDLE PATCH 11.1.1.7.5


Pre-Patch Instructions

- Review and download the latest version of OPatch 11.1.x via Bug 6880880

- Ensure access to valid OUI Inventory by running opatch lsinventory

- Validate the executables in system PATH like 'which opatch', 'which unzip'

- You MUST apply this patch to both SOA Home $MW_HOME/Oracle_SOA1 and Oracle Common Home $MW_HOME/oracle_common without fail.
  

Applying Patch 19190139

1. Unzip the patch zip file into the PATCH_TOP.

   $ unzip -d PATCH_TOP p19190139_111170_Generic.zip

    
2. $ cd PATCH_TOP/19190139/

3. Run OPatch apply

       $ opatch apply

(Ensure MT services are already stopped, cold backup is recommended before patch)

4. Restart MT services and verify the patch by running 

$opatch lsinventory | grep 19190139

5. If patch fails for some reason, rollback the patch and restart MT services.

Additionally you may also apply the SOA and BPM JDev extensions directly from JDeveloper via the “check for updates” feature.



Related posts:

Applying Patch 20900797: SOA Bundle Patch 11.1.1.7.8

Applying Patch 20423535: SOA Bundle Patch 11.1.1.7.7

Applying Patch 19953598: SOA Bundle Patch 11.1.1.7.6

Applying Patch 18609527 SOA BUNDLE PATCH 11.1.1.7.4

Applying Patch 18072286 SOA BUNDLE PATCH 11.1.1.7.3

Applying Patch 17584181 SOA BUNDLE PATCH 11.1.1.7.2

FMW 11.1.1.6.0 - Applying Patch 16702086: SOA BUNDLE PATCH 11.1.1.6.7

Enabling proxy for SOA servers

Below steps explain proxy parameters to set to enable proxy for SOA server

- Navigate to $SOA_HOME/bin

- Backup setDomainEnv.sh

- Edit setDomainEnv.sh

Set values for below highlighted in bold.

if [ "${SERVER_NAME}" != "AdminServer" ] ; then

EXTRA_JAVA_PROPERTIES="${EXTRA_JAVA_PROPERTIES} -DproxySet=true 
-Dhttps.proxyHost=  
-Dhttp.proxyHost= -Dhttp.proxyPort= -Dhttps.proxyPort= 
-Dhttp.nonProxyHosts=

export EXTRA_JAVA_PROPERTIES
fi

- Restart Mid-tier services

- grep java and make sure the proxy flags are seen in soa server

AIAReadJMSNotificationProcess [1.0] in unknown state in SOA 11g EM Fusion Middleware Console

AIAReadJMSNotificationProcess [1.0] in unknown state in SOA 11g EM Fusion Middleware Console


Are you seeing AIAReadJMSNotificationProcess [1.0] composites in unknown states in your SOA enterprise manager console?


Errors as below:

<Error> <oracle.integration.platform> <SOA-20020> <Deployment of composite "AIAReadJMSNotificationProcess" failed: Error in getting XML input stream: http://soa.localhost.com:port/soa-infra/services/default/AIAErrorTaskAdministrationProcess/AIAErrorTaskAdministrationProcess.wsdl: Connection reset.>
====> CubeEngine load AIAErrorTaskAdministrationProcess/AIAErrorTaskAdministrationProcess took 476 ms

AIAReadJMSNotificationProcess appears in unknown state on SOA cluster nodes

Composite is in Failed state because it may not have got deployed when soa_server has been started. This may be because you have dependencies between your SOA Composites and AIAReadJMSNotificationProcess that has been deployed before AIAErrorTaskAdministrationProcess it depends on. 

For quick fix:

- restart soa_servers but it may happen again because deployment order of SOA Composites cannot be configured

or 

- redeploy AIAReadJMSNotificationProcess composite


For long term fix, follow:

Doc ID 1151973.1 Boot Order Of The Composites Upon Soa Suite Restart


Doc ID 1369101.1 SOA Server With AIA Unable to Look Up WSDL's At Startup

associated with bug: 12979076 - SOA11G MANAGED SERVER WITH AIA FAILS LOOKING UP WSDL AT STARTUP