OIM T2P Leads to SOA importMetadata Errors MDS-90034 and MDS-91009 during pasteConfig.sh run

(Doc ID 2387024.1)

Last updated on APRIL 16, 2018

Applies to:

Identity Manager - Version 11.1.2.2.9 and later
Information in this document applies to any platform.

Symptoms

On : 11.1.2.2.9 version, Infrastructure

PUMA - T2P for OIM leads to SOA Errors

Running T2P for an OIM setup does not complete for the SOA side


ERROR
-----------------------
#### <SOA Node1> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <> <>
#### <SOA Node1> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <> <>
#### <SOA Node1> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <> <>
#### <SOA Node1> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <> <>
#### <SOA Node1> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <> <>
and

INFO : Mar 16, 2018 17:24:49 - CLONE-23357 <SOA Node2> is already running on port <SOA Port number>
INFO : [PLUGIN][SOA] Mar 16, 2018 17:24:49 - CLONE-51027 Executing "Paste Configuration" operation of the SOA plugin.
INFO : [PLUGIN][SOA] Mar 16, 2018 17:24:49 - CLONE-51028 Extracting soat2p folder from archive.
INFO : [PLUGIN][SOA] Mar 16, 2018 17:24:50 - CLONE-51063 Importing SOA configuration from MDS.
...

Connecting to t3://<AdminServer host>:7001 with userid <WLS Admin User> ...
Successfully connected to Admin Server '<AdminServer Name>' that belongs to domain '<domain name>'.

Warning: An insecure protocol was used to connect to the
server. To ensure on-the-wire security, the SSL port or
Admin port should be used instead.

Location changed to domainRuntime tree. This is a read-only tree with DomainMBean as the root.
For more help, use help(domainRuntime)


Problem invoking WLST - Traceback (innermost last):
 File "/tmp/CLONINGCLIENT-5680753998564914919/tmp1521235490000.py", line 27, in ?
 File "/opt/was/oracle/oim/middleware/oracle_common/common/wlst/mdsWLSTCommands.py", line 295, in importMetadata
 File "/opt/was/oracle/oim/middleware/oracle_common/common/wlst/mdsWLSTCommands.py", line 816, in executeAppRuntimeMBeanOperation
 File "/opt/was/oracle/oim/middleware/oracle_common/common/wlst/mdsWLSTCommands.py", line 1097, in saveStackAndRaiseException
WLSTException: MDS-90034: The source directory or archive "/tmp/CLONINGCLIENT-5680753998564914919/soat2p/MDS/soa_shared_docs" for importing metadata is invalid. MDS-91009: Operation "importMetadata" failure. Use dumpStack() to view the full stacktrace.

and

SEVERE : [PLUGIN][SOA] - ERROR - Mar 16, 2018 17:24:58 - CLONE-53027 Error in importing MDS data.
SEVERE : [PLUGIN][SOA] - CAUSE - Mar 16, 2018 17:24:58 - CLONE-53027 MDS import for "soa-infra" application failed.
SEVERE : [PLUGIN][SOA] - ACTION - Mar 16, 2018 17:24:58 - CLONE-53027 Check SOA server logs for details.


STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Have OIM + SOA in a multi-node cluster prep'd for T2P
2. Move binaries fine
3. Update the moveplan per the existing T2P documentation
4. Run pasteConfig and see errors as it seems to be starting <SOA Node2> on the wrong host and then the MDS imports fail

Changes

 

Cause

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