WLP 10.3 COMMIT Task Fails When Trying to Propagate Newly Added DataSync's UserSegment

(Doc ID 1279021.1)

Last updated on JULY 17, 2017

Applies to:

Oracle WebLogic Portal - Version and later
Information in this document applies to any platform.


The below error occurs when trying to propagate newly added UserSegment to an existing portal
application's Datasync project:

<tool:election accepted="true" decision-state="RESOLUTION_DONE" processing-state="PROCESSING_TODO" explanation="A dependent requires this node to exist, however it was not included in the export of the source system. It is possible that the associated adapter is not enabled." impossible-explanation="" manual-explanation="This resource is required by [Application:PersonalizationService:UserSegments:UserSeg001] and needs to be added, however it was not found in the inventory file. This is typically because the resource was excluded by scoping. Either add the resource to the destination system manually or ensure that the resource is in scope." dependency-taxonomy="Application:PersonalizationService:UserSegments:UserSeg001" election-identifier="0" first-pass="0" has-manual-step="true" has-resolver-step="false" needs-processing="true" implied="true" impossible="false" impossible-reason-code="" manual-reason-code="BaseNodeRules:scope" name="DefaultRequestPropertySet" needs-caution="true" type="UNKNOWN_TYPE" operation="OPERATION_ADD" policy-approved="true" reason-code="BaseNodeRules:ensureAdd0" taxonomy="Application:PersonalizationService:UserProfiles:DefaultRequestPropertySet" taxonomy-depth="4" out-of-scope="true"/>


Sign In with your My Oracle Support account

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

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms