My Oracle Support Banner

Failure to re-associate a standalone midtier instance with another OID for the second time (Doc ID 400628.1)

Last updated on JULY 01, 2021

Applies to:

Oracle Fusion Middleware - Version 10.1.2.0.0 and later
Enterprise Manager for Fusion Middleware - Version 10.1.2.0.0 and later
Information in this document applies to any platform.
Enterprise Manager for iAS - Version: 10.1.2.0.0
This problem can occur on any platform.

Symptoms

Whilst using the infrastructure link within iasconsole to associate a midtier instance to OID, the screen declares the actions as successful but the OID host and port values remain blank.

One example of  when this might happen is when a standalone midtier instance is used.  If this instance is associated with OID using iasconsole, then disassociated from OID and re-associated to a second OID using iasconsole again.  Whilst the first association will work, the second (and subsequent) associations will fail to completed properly.

Whilst there is no documented procedure for disassociating a standalone midtier from OID, the section in the document - Distributed Configuration Management Administrator's Guide 10g Release 2 (10.1.2), Section 2.2.14.1 - J2EE and Web Cache Instance Using Identity Management (Oracle Internet Directory) does cover the necessary actions.

According to this document, only two configuration files on the midtier need to be changed:


After this change, the midtier should be in a state of "standalone" and using the iasconsole, the midtier can  be asssociated with a new OID.

However, if the midtier is put back into a standalone state, following the document for a second time, any further use of iasconsole to associated to a new OID will fail to complete properly.

N.B. Although iasconsole allows the association command to run and reports it as successful, the necessary updates to the midtier and to the new OID do not take place and iasconsole shows the instance associated but with the OID host and Port are blank.

-- Steps To Reproduce:
1.  Install a standalone J2EE and Webcache instance.
2. Use iasconsole to associate this midtier with a new OID but not to a farm repository.
3. Follow the Distributed Configuration Management Administrator's Guide 10g Release 2 (10.1.2), Section 2.2.14.1 - J2EE
and Web Cache Instance Using Identity Management (Oracle Internet Directory) to convert the midtier back to a "standalone" status .
4. Use iasconsole to attempt a new association to a different OID.
5.  Although iasconsole declares the command successful it has not updated the midtier and OID successfully.
6.  Check the status of the association in iasconsole.  The OID host and port show as blank.


Changes

 

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
Changes
Cause
Solution


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