My Oracle Support Banner

OBIA 11g: Facing Issues At Sync Phase Of Applying A Patch As Part Of Bundle Patches On BIAPPS (Doc ID 2113401.1)

Last updated on OCTOBER 08, 2018

Applies to:

Business Intelligence Applications Consumer - Version 11.1.1.8.1 to 11.1.1.8.1 [Release 11g]
Information in this document applies to any platform.

Symptoms


Errors during sync phase of applying patches as part of a bundle patch (for example applying the patch 20062795 as part of PB6 bundle patch on BIAPPS 11.1.1.8.1).

When applying a patch (like in the example with patch 20062795 as part of PB6 patch bundle), this is completing successfully but the sync phase fails with message:

Encountered the following exception: Conflicts found in the list: {delete-safe=0, modification-conflicts=0, modification-safe=0, addition-conflicts=64, addition-safe=0, delete-conflicts=0}
.
Root Cause Exception was : Conflicts found in the list: {delete-safe=0, modification-conflicts=0, modification-safe=0, addition-conflicts=64, addition-safe=0, delete-conflicts=0}
.
Encountered the following exception: Patch apply is unsuccessful for the the patch 20062795
.
Root Cause Exception was : Patch apply is unsuccessful for the the patch 20062795
.
FAILED to complete all orchestration-synchpatch tasks successfully
.
.
biapps_patch_storage/orchestration-synchpatch/02142016_012055/biapps_policystore_delta

INFO : If no conflicts were found then please check the
log file for more information about why the patch failed to apply.
 WARNING : patchPolicyStore for Patch: 20062795 at path:
/u01/app/OBI_Patches/20246197/p20062795_111181_Generic.zip
oracle.as.biapps.patch.orchestrate.exp.ConflictDetectedException: Conflicts found in the list: {delete-safe=0, modification-conflicts=0, modification-safe=0, addition-conflicts=64, addition-safe=0, delete-conflicts=0}
at oracle.as.biapps.patch.orchestrate.participants.PatchPolicyStore.analyze(PatchPolicyStore.java:337)
at oracle.as.biapps.patch.orchestrate.participants.PatchPolicyStore.applyPatch(PatchPolicyStore.java:180)
at oracle.as.biapps.patch.orchestrate.conductors.PolicyStoreInstanceConductor.patchPolicyStore(PolicyStoreInstanceConductor.java:246)
at oracle.as.biapps.patch.orchestrate.conductors.PolicyStoreInstanceConductor.postApplyPhase(PolicyStoreInstanceConductor.java:202)
at oracle.as.biapps.patch.orchestrate.conductors.PolicyStoreInstanceConductor.doPostApplyPhaseForApply(PolicyStoreInstanceConductor.java:171)
at oracle.as.biapps.patch.orchestrate.synchpatch.SynchPolicyStorePatchTask.applyPolicyStorePatch(SynchPolicyStorePatchTask.java:60)
at oracle.as.biapps.patch.orch...
 

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.