Dedicated Nodes for Concurrent Managers - Automatic Setting During Cloning Process (Doc ID 2137598.1)

Last updated on MARCH 08, 2017

Applies to:

Oracle Applications Manager - Version 12.1.3 and later
Oracle Concurrent Processing - Version 12.1.3 and later
Information in this document applies to any platform.

Goal

When doing an EBS Multi-Node clone it is not possible to automate the assignment of a primary processing node for a concurrent manager. Neither can one map source nodes to target nodes nor can one by calling api or so automatically assign a concurrent manager to a specific node.

Especially when doing regular clones (weekly) it is needed to have a possibility to automatically assign concurrent managers to concurrent processing nodes.

---
Description of a current situation:

Doing a clone from a two-node apps env to another two-node apps env:
Source: PROD12APPS (primary node) and PROD12BIP (secondary node)
Target: CRP12APPS (primary node) and CRP12BIP (secondary node)
EBS release 12.1.3, DB version 12.1.0.2
non-shared appl top
Cloning process was successful, all services (including ICM- internal concurrent manager) could be successfully started on CRP12APPS - this being primary node. Also all services could be successfully started on CRP12BIP - secondary node.
But: on the source system, a part of the concurrent managers were pinned (primary node entered as) to PROD12BIP. After clone all this primary-node-setting is gone (since the original nodes no longer exist). And now it is needed an option to pin those CM accordingly to CRP12BIP and make sure they are only started on that Node and not on CRP12APPS (the main-node that it is started always first). This currently cannot be achieved automatically (without having to set manually the node for each concurrent manager in System Administrator responsibility).
The expected behavior was to have the Concurrent Managers associated to secondary node in the Source instance, be automatically associated/mapped to the secondary node in the Target instance during/after cloning process.

Solution

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