OPSS Unable to start WL Server XML20108 Fatal Error JPS02592 Failed To Push Ldap Config Data To LibOvd

Issue:

 Jun 21, 2016 7:03:16 PM oracle.security.jps.internal.igf.ovd.OvdIGFServiceProvider pushLdapNamesTolibOvd SEVERE:JPS-02592
<Jun 21, 2016 7:03:16 PM SGT> <Error> <Security> <BEA-090892> <The loading of OPSS java security policy provider failed due to exception, see the exception stack trace or the server log file for root cause. If still see no obvious cause, enable the debug flag -Djava.security.debug=jpspolicy to get more information. Error message: JPS-02592: Failed to push ldap config data to libOvd for service instance "idstore.ldap" in JPS context "default", cause: org.xml.sax.SAXException: Error Parsing at line #1: 1.org.xml.sax.SAXParseException; lineNumber: 1; columnNumber: 1; <Line 1, Column 1>: XML-20108: (Fatal Error) Start of root element expected.>
<Jun 21, 2016 7:03:16 PM SGT> <Critical> <WebLogicServer> <BEA-000386> <Server subsystem failed. Reason: weblogic.security.SecurityInitializationException: The loading of OPSS java security policy provider failed due to exception, see the exception stack trace or the server log file for root cause. If still see no obvious cause, enable the debug flag -Djava.security.debug=jpspolicy to get more information. Error message: JPS-02592: Failed to push ldap config data to libOvd for service instance "idstore.ldap" in JPS context "default", cause: org.xml.sax.SAXException: Error Parsing at line #1: 1.org.xml.sax.SAXParseException; lineNumber: 1; columnNumber: 1; <Line 1, Column 1>: XML-20108: (Fatal Error) Start of root element expected.
weblogic.security.SecurityInitializationException: The loading of OPSS java security policy provider failed due to exception, see the exception stack trace or the server log file for root cause. If still see no obvious cause, enable the debug flag -Djava.security.debug=jpspolicy to get more information. Error message: JPS-02592: Failed to push ldap config data to libOvd for service instance "idstore.ldap" in JPS context "default", cause: org.xml.sax.SAXException: Error Parsing at line #1: 1.
org.xml.sax.SAXParseException; lineNumber: 1; columnNumber: 1; <Line 1, Column 1>: XML-20108: (Fatal Error) Start of root element expected.
        at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.loadOPSSPolicy(CommonSecurityServiceManagerDelegateImpl.java:1402)
        at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(CommonSecurityServiceManagerDelegateImpl.java:1022)
        at weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:873)
        at weblogic.security.SecurityService.start(SecurityService.java:141)
        at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
        Truncated. see log file for complete stacktrace
Caused By: oracle.security.jps.JpsRuntimeException: JPS-02592: Failed to push ldap config data to libOvd for service instance "idstore.ldap" in JPS context "default", cause: org.xml.sax.SAXException: Error Parsing at line #1: 1.
org.xml.sax.SAXParseException; lineNumber: 1; columnNumber: 1; <Line 1, Column 1>: XML-20108: (Fatal Error) Start of root element expected.

Resolution:

1.  Please verify whether your file system having disk space issues ($df -h in case of Linux). One of the causes of XML files corruption is seen when there is a filesystem full condition.

2.  If it is not relates to file system space issues, then it might be because of corrupted adapters.os_xml

3.  As additional symptom $DOMAIN_HOME/config/fmwconfig/ovd/default/server.os_xml was detected as zero (0) bytes.

Corruption of the adapters.os_xml or server.os_xml under this LibOVD location file may lead to Weblogic server startup failure.

Please navigate to the fmwconfig folder and check the adapters.os_xml or server.os_xml file or both
$DOMAIN_HOME/config/fmwconfig/ovd/default/adapters.os_xml

There are chances the any of those xml file could be corrupted due to which the Weblogic server fails to start.


4.  In case the file is corrupted, please perform the following steps:

   a. Take a backup of $DOMAIN_HOME/config/fmwconfig/ovd/default/adapters.os_xml 
      or  server.os_xml
   b. Delete corrupted adapters.os_xml or server.os_xml files under
       $DOMAIN_HOME/config/fmwconfig/ovd/default/adapters.os_xml

   c. Copy adapters.os_xml or server.os_xml from 
         $MW_HOME/oracle_common/modules/oracle.ovd_11.1.1/templates/ to
         $DOMAIN_HOME/config/fmwconfig/ovd/default/. Or restore files from backup.
5. Restart the server. It should works!!

 Hope this post helps you to resolve this issue.

org.eclipse.persistence.exceptions.DatabaseException Internal Exception: java.sql.SQLRecoverableException: IO Error: The Network Adapter could not establish the connection

Source: org.eclipse.persistence.exceptions.DatabaseException Internal Exception: java.sql.SQLRecoverableException: IO Error: The Network Adapter could not establish the connection

org.eclipse.persistence.exceptions.DatabaseException Internal Exception: java.sql.SQLRecoverableException: IO Error: The Network Adapter could not establish the connection

Issue:

****** weblogic startup log ******

INFO: Found persistence provider “org.eclipse.persistence.jpa.PersistenceProvider”. OpenJPA will not be used.
[EL Severe]: 2015-12-06
03:35:08.961–ServerSession(1577131615)–Exception [EclipseLink-4002] (Eclipse Persistence Services – 2.3.1.v20111018-r10243):
org.eclipse.persistence.exceptions.DatabaseException
Internal Exception: java.sql.SQLRecoverableException: IO Error: The Network Adapter
could not establish the connection
Error Code: 17002
Dec 6, 2015 3:35:08 AM
oracle.security.jps.internal.credstore.ldap.LdapCredentialStore init
WARNING: Could not create credential store instance. Reason
oracle.security.jps.service.policystore.PolicyStoreConnectivityException: JPS-10000: There was an internal error in the policy store.
JPS-01055: Could not create credential store instance. Reason oracle.security.jps.service.policystore.PolicyStoreConnectivityException:
JPS-10000: There was an internal error in the policy store.
Error: Diagnostics data was not saved to the credential store.
Error:
Validate operation has failed.
Need to do the security configuration first!

Solution:

1. Verify Database listener is up & running or not

2. Take the backup of jpsconfig.xml file

3. Start the database listener

$$ORACLE_HOME/bin

$lsnrctrl status listener — Verify Listener status

$lsnrctrl start listener — Start the listener,if already not started

4. Start the weblogic from command prompt

$DOMAIN_HOME/bin

$nohup ./startWeblogic.sh > AdminServer.log &

$tail -f AdminServer.log

5. Weblogic Admin Server will start normally.

How to Change Default Font Style to Calibri in Gmail !!

Below are the steps to  change the default font style to Calibri in Gmail.

1. First thing you need to do is to turn on Canned Responses in Gmail. Canned response is a feature which lets you insert same text in different mails. Thus it works like an automated message which saves your time as you need not to write same thing again and again. To turn-on this feature, go to Gmail settings > Labs tab > Canned Response section > Enable it and save changes

2. Now open MS Office Word or any other document editor and choose your desired font, size and color. Now type some sample text like Dear XYZ using preselected font settings. Give some space after the sample text by either having multiple spaces or few lines by pressing Enter key.

3. Select all sample text plus white space (Press Ctrl + a) and then copy it (Press Ctrl + c).

4. Now, go to compose message in Google Email and paste (Press Ctrl + v) the previous copied text. You will notice that your desired font has been inserted into mail body.

5. Save this font style by clicking on canned responses below subject box and selecting Save > New caned response. Give a convenient name to remember like font name.

6. It’s done :). From now on whenever you would like to use different    font in Gmail, just click on canned responses and select the previously stored font.

Your sample text will appear and when you type along with it, the fonts will automatically change.

Hope this will helps you !!

Creating a wlfullclient.jar and Design console configuration

Use the following steps to create a wlfullclient.jar file :

   1. Change directories to the server/lib directory.

         $cd WL_HOME/server/lib

   2. Use the following command to create wlfullclient.jar in the server/lib directory:

         $java -jar wljarbuilder.jar

    3. wlfullclient.jar file will created under $WL_HOME/server/lib

   4.You can now copy and bundle the wlfullclient.jar to $OIM_HOME/designconsole/lib and

       $OIM_HOME/designconsole/ext folders.

   5.  Add the wlfullclient.jar to the client application’s class path.

Note : For both Windows and Linux platforms, wlfullclient.jar file generation procedure is same in OIM.

Hope this will helps you !!

javax.security.auth.login.LoginException in OIM Design Console

Issue :

javax.security.auth.login.LoginException: java.lang.RuntimeException: Failed to instantiate MD5 SecureRandom: Unsupported algorithm

The javax.security.auth.login.LoginException: java.lang.RuntimeException: Failed to instantiate MD5 SecureRandom: Unsupported algorithm exception is thrown after clicking the Login Button in the Oracle Identity Manager Design Console.

Error:

Error Keyword: DAE.LOGON_DENIED
Description: Invalid Login.
Remedy: Contact your system administrator.
Action: E
Severity: H
Help URL:
Detail:
javax.security.auth.login.LoginException: java.lang.RuntimeException: Failed to instantiate MD5 SecureRandom: Unsupported algorithm, MD5Random, selected for FIPS140 mode: FIPS140_SSL
at com.certicom.tls.interfaceimpl.TLSSystem.getRandomNumberGenerator(Unknown Source)
at com.certicom.tls.record.handshake.MessageRandom.initialize(Unknown Source)
at com.certicom.tls.record.handshake.MessageRandom.(Unknown Source)
at com.certicom.tls.record.handshake.HandshakeHandler.startHandshake(Unknown Source)
at com.certicom.tls.interfaceimpl.TLSConnectionImpl.startHandshake(Unknown Source)
at com.certicom.tls.interfaceimpl.TLSConnectionImpl.completeHandshake(Unknown Source)
at com.certicom.tls.record.WriteHandler.write(Unknown Source)
at com.certicom.io.OutputSSLIOStreamWrapper.write(Unknown Source)
at java.io.BufferedOutputStream.flushBuffer(BufferedOutputStream.java:66)
at java.io.BufferedOutputStream.flush(BufferedOutputStream.java:124)
at java.io.DataOutputStream.flush(DataOutputStream.java:107)
at weblogic.rjvm.t3.MuxableSocketT3.connect(MuxableSocketT3.java:406)
at weblogic.rjvm.t3.ConnectionFactoryT3S.createConnection(ConnectionFactoryT3S.java:44)
at weblogic.rjvm.ConnectionManager.createConnection(ConnectionManager.java:1784)
at weblogic.rjvm.ConnectionManager.findOrCreateConnection(ConnectionManager.java:1424)
at weblogic.rjvm.ConnectionManager.bootstrap(ConnectionManager.java:443)
at weblogic.rjvm.ConnectionManager.bootstrap(ConnectionManager.java:322)
at weblogic.rjvm.RJVMManager.findOrCreateRemoteInternal(RJVMManager.java:254)
at weblogic.rjvm.RJVMManager.findOrCreate(RJVMManager.java:197)
at weblogic.rjvm.RJVMFinder.findOrCreateRemoteServer(RJVMFinder.java:238)
at weblogic.rjvm.RJVMFinder.findOrCreateInternal(RJVMFinder.java:200)
at weblogic.rjvm.RJVMFinder.findOrCreate(RJVMFinder.java:170)
at weblogic.rjvm.ServerURL.findOrCreateRJVM(ServerURL.java:153)
at weblogic.rjvm.ServerURL.findOrCreateRJVM(ServerURL.java:96)
at weblogic.security.auth.Authenticate.authenticate(Authenticate.java:80)
at weblogic.security.auth.login.UsernamePasswordLoginModule.login(UsernamePasswordLoginModule.java:184)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at javax.security.auth.login.LoginContext.invoke(LoginContext.java:769)
at javax.security.auth.login.LoginContext.access$000(LoginContext.java:186)
at javax.security.auth.login.LoginContext$4.run(LoginContext.java:684)
at javax.security.auth.login.LoginContext.invokePriv(LoginContext.java:680)
at javax.security.auth.login.LoginContext.login(LoginContext.java:579)
at Thor.API.Security.LoginHandler.weblogicLoginHandler.login(weblogicLoginHandler.java:62)
at oracle.iam.platform.OIMClient.login(OIMClient.java:134)
at oracle.iam.platform.OIMClient.login(OIMClient.java:114)
at com.thortech.xl.client.base.tcAppWindow.internalLogin(tcAppWindow.java:585)
at com.thortech.xl.client.base.tcAppWindow.login(tcAppWindow.java:504)
at com.thortech.xl.client.base.tcAppWindow.(tcAppWindow.java:118)
at com.thortech.xl.client.base.tcAppWindow.main(tcAppWindow.java:174)

Solution 1:

The cryptoj.jar file is missing in the $WLS_HOME/lib directory. Copy the cryptoj.jar file from

$WLS_HOME/lib to $OIM_HOME/designconsole/ext directory.

Solution 2:

If crypto.jar file available, still you are getting an login issue means try the following options :

1. Try to create wlfullclient.jar file and copy it to design console lib and ext directories

2. Verify provided OIM Username and Password is correct

Hope this will helps you!

Enabling the SSL Oracle Identity Manager Design Console

To enable the SSL for Oracle Identity Manager Design Console by following the below steps:

1. Configuring the OIM Design Console

The following task’s needs to be performed to enable the SSL for Oracle Identity Manager Design Console. They are

1.1 Copy Jar Files

1.1.1 Login into the OIM Server.
1.1.2 Copy the webserviceclient+ssl.jar and cryptoj.jar from the $WLS_HOME/lib to $OIM_ORACLE_HOME/designconsole/ext directory

1.2 Configuring classpath.sh

1.2.1 Go to the Go to the $OIM_ORACLE_HOME/designconsole directory and edit the classpath.sh file and add the following content before $CLASSPATH. They are

:./ext/cryptoj.jar:./ext/webserviceclient+ssl.jar

1.2.2 Define the TRUSTSTORE_LOCATION variable in the classpath.sh file.

TRUSTSTORE_LOCATION = “OIM Trust Store.jks”

export TRUSTSTORE_LOCATION

1.3 Configuring xlconfig.xml

1.3.1 Go to the $OIM_ORACLE_HOME/designconsole/config directory and edit the xlconfig.xml file.

1.3.2 Modify the following parameters

https://localhost:/xlWebApp/loginWorkflowRenderer.do

t3s://localhost:/oim

1.4 Configuring xlclient.sh

1.4.1 Go to the Go to the $OIM_ORACLE_HOME/designconsole/ directory and edit the xlclient.sh file and add the following content if your using Self Signed Cert or root certificate is not trusted authority provider.

1.4.1.1 Turn off the SSL Constraints
-Dweblogic.security.SSL.enforceConstraints=off \

1.4.1.2 Turn Off the Host Name Verification
-Dweblogic.security.SSL.ignoreHostnameVerification=true \

1.4.1.3 Turn Off the default Random Number Generator.
The changing default Random Number generator shown in the log as follows

To turn of the off the random generator number in the log add the following flag.

-Dweblogic.security.allowCryptoJDefaultPRNG=true \

1.4.1.4 Debug the SSL Parameters
-Dssl.debug=true \

-Dweblogic.StdoutDebugEnabled=true \

1.5 Sample xlclient.sh file

After configuring the xlclient.sh file and the file content should be following format.

java -DXL.ExtendedErrorOptions=TRUE \
-DXL.HomeDir=. -Djava.security.policy=config/xl.policy \
-Djava.security.manager -Djava.security.auth.login.config=config/authwl.conf \
-Dlog4j.configuration=config/log.properties \
-Dweblogic.security.SSL.trustedCAKeyStore=$TRUSTSTORE_LOCATION \
-Dweblogic.security.SSL.enforceConstraints=off \
-Dweblogic.security.SSL.ignoreHostnameVerification=true \
-Dweblogic.security.allowCryptoJDefaultPRNG=true \
-Dssl.debug=true \
-Dweblogic.StdoutDebugEnabled=true \
-cp $CLASSPATH com.thortech.xl.client.base.tcAppWindow -server server

How To Configure Auto-Approval for End User Self-Registration in OIM 11g?

In the default self-registration template, the Organization field is designated as an approver-only field. This means that an approver must manually supply a value for the Organization field when approving the request.

To configure the self-registration template so that registrations are approved automatically, remove the approver-only flag from the dataset (i.e. SelfCreateUserDataset.xml) for the Organization field.

In OIM 11g, each request work-flow goes through three levels of approvals.

    Template Level

    Request Level

    Operational Level

By default Template Level is auto approved, so here only two levels of approvals need to be configured as auto approval. To achieve this, create two new approval policies, one with the request level approval enabled for self-registration, and the other with the operational level approval enabled.

For 11gR1 versions:

Steps:

    Modify the Self-Register User OOTB request template by restricting the Organization attribute with a mandatory default value.

    Modify the Self-Register user dataset by removing “approver-only” flag or setting it to “false” for Organization AttributeReference. Make sure you import the updated dataset and clear the cache.

    Create two new approval policies, one with the request level approval enabled for self-registration, and the other with the operational level approval enabled with a rule that evaluates to true.

1. Modify the Self-Register User OOTB request template

Modify the Self-Register User OOTB request template by restricting the Organization attribute with a mandatory default value.

2. Modify the Self-Register user dataset

Modify the Self-Register user dataset by setting it to “false” for Organization AttributeReference. Make sure you import the updated dataset (SelfCreateUserDataset.xml) and clear the cache.

See the Example of MDS Utility Usage and Purging Cache.

metadata_files=/metadata/iam-features-requestactions/model-data/SelfCreateUserDataset.xml

3. Create two new approval policies

Create two new approval policies, one with the request level approval enabled for self-registration, and the other with the operational level approval enabled with a rule that evaluates to true.

Now try to submit a request from self-registration, End user will be created into OIM directly without any manual approval.

For 11gR2 versions:

The things you need to do:

–     Create 2 approval policies

o   Request level auto approval for all self-register type requests.

o   Operation level auto approval for all self-register type requests and for all the scopes.

–    Register a pre-process handler which will provide a default home organization for all the self-registered users. This is because home organization is a mandatory user attribute.

RCU 11g fails on Oracle Enterprise Linux 6.5 – RCU-6130 and RCU-6136:Error while trying to execute SQLPlus action

Issue:

While running the Repository Creation Utility 11g (RCU) from Oracle Enterprise Linux 6.5 (OEL6.5) 64bit, it is possible to have errors while creating the schema.

The Oracle Universal Installer will first throw errors in the graphical user interface such as RCU-6130 RCU-6136

Upon inspection of the RCU logs (RCU_HOME/rcu/log/logdir.date_timestamp/rcu.log), the following will be seen.
2015-11-13 11:16:47.199 ERROR rcu: oracle.sysman.assistants.rcu.backend.action.SQLPlusAction::perform: Error initializing SQLPlusEngine:
java.io.IOException: java.io.IOException: java.io.IOException: java.io.IOException: java.io.IOException: java.io.IOException: java.io.IOException: java.io.IOException: java.io.IOException: java.io.IOException: java.io.IOException: java.io.IOException: Error initializing sqlplus.
    at oracle.sysman.assistants.common.dbutil.sqlplus.SQLPlusEngine.setDefaultEngineSettings(SQLPlusEngine.java:2144)
    at oracle.sysman.assistants.common.dbutil.sqlplus.SQLPlusEngine.initialize(SQLPlusEngine.java:352)
    at oracle.sysman.assistants.rcu.backend.action.SQLPlusAction.perform(SQLPlusAction.java:200)
    at oracle.sysman.assistants.rcu.backend.task.AbstractCompTask.execute(AbstractCompTask.java:243)
    at oracle.sysman.assistants.rcu.backend.task.ActualTask.run(TaskRunner.java:306)
    at java.lang.Thread.run(Thread.java:662)

2015-11-13 11:16:47.298 ERROR rcu: oracle.sysman.assistants.rcu.backend.task.ActualTask::run: RCU Operation Failed
oracle.sysman.assistants.common.task.TaskExecutionException: RCU-6136:Error while trying to execute SQLPlus action.
    at oracle.sysman.assistants.rcu.backend.task.AbstractCompTask.execute(AbstractCompTask.java:300)
    at oracle.sysman.assistants.rcu.backend.task.ActualTask.run(TaskRunner.java:306)
    at java.lang.Thread.run(Thread.java:662)
Caused by: oracle.sysman.assistants.common.task.ActionFailedException: RCU-6136:Error while trying to execute SQLPlus action.
    at oracle.sysman.assistants.rcu.backend.action.SQLPlusAction.perform(SQLPlusAction.java:211)
    at oracle.sysman.assistants.rcu.backend.task.AbstractCompTask.execute(AbstractCompTask.java:243)
    … 2 more
Caused by: java.io.IOException: java.io.IOException: java.io.IOException: java.io.IOException: java.io.IOException: java.io.IOException: java.io.IOException: java.io.IOException: java.io.IOException: java.io.IOException: java.io.IOException: java.io.IOException: Error initializing sqlplus.
    at oracle.sysman.assistants.common.dbutil.sqlplus.SQLPlusEngine.setDefaultEngineSettings(SQLPlusEngine.java:2144)
    at oracle.sysman.assistants.common.dbutil.sqlplus.SQLPlusEngine.initialize(SQLPlusEngine.java:352)
    at oracle.sysman.assistants.rcu.backend.action.SQLPlusAction.perform(SQLPlusAction.java:200)
    … 3 more
 These errors are most notably seen on Oracle Identity Management and Oracle Identity and Access Management schemas but can occur on any schema.

Resolution:

1. Please verify that Oracle Fusion Middleware is certified on your Linux Release

2. Please verify you have all of the required packages installed for your Operating System

3. Please give full permissions to RCU and it’s sub folders before executing $./rcu command

     $cd RCU -> $chmod -R 777 * -> cd rcuHome/bin -> ./rcu

4. If the above steps do not solve the issue please try these potential workarounds.
Currently there is no fix for this issue on OEL6.5

a) Try downloading the Windows Version of the RCU and run it from a certified Windows platform.
b) Try using an older versioin of Linux such as OEL5
c) Try running the RCU from a 32-bit platform

Hope this will resolve your issue!

RCU 11g fails on MS Windows – RCU-6136:Error while trying to execute SQLPlus action

Error :

The Repository Creation Utility (RCU), running on MS Windows, fails when attempting to launch SQLPLUS.  The rcu.log shows the following errors:

NOTIFICATION rcu:
oracle.sysman.assistants.common.dbutil.jdbc.JDBCEngine::connect:
Connecting to database: user:jaltaie, role:SYSDBA,
connectString:(description=(address=(host=localhost)(protocol=tcp)(port=1521))(connect_data=(service_name=ORCLDW.MANAARNET.COM)(server=dedicated)))
2011-08-23 22:56:36.284 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.action.SQLPlusAction::perform: paramString =
2015-11-23
22:56:36.452 ERROR rcu:
oracle.sysman.assistants.rcu.backend.action.SQLPlusAction::perform:
Error initializing SQLPlusEngine:
java.io.IOException:
java.io.IOException: java.io.IOException: java.io.IOException:
java.io.IOException: java.io.IOException: java.io.IOException:
java.io.IOException: java.io.IOException: java.io.IOException:
java.io.IOException: java.io.IOException: Error initializing sqlplus.
at oracle.sysman.assistants.common.dbutil.sqlplus.SQLPlusEngine.setDefaultEngineSettings(SQLPlusEngine.java:2113)
at oracle.sysman.assistants.common.dbutil.sqlplus.SQLPlusEngine.initialize(SQLPlusEngine.java:352)
at oracle.sysman.assistants.rcu.backend.action.SQLPlusAction.perform(SQLPlusAction.java:200)
at oracle.sysman.assistants.rcu.backend.task.AbstractCompTask.execute(AbstractCompTask.java:243)
at oracle.sysman.assistants.rcu.backend.task.ActualTask.run(TaskRunner.java:303)
at java.lang.Thread.run(Thread.java:619)

2015-11-23 22:56:36.454 ERROR rcu: oracle.sysman.assistants.rcu.backend.task.ActualTask::run: RCU Operation Failed
oracle.sysman.assistants.common.task.TaskExecutionException: RCU-6136:Error while trying to execute SQLPlus action.
at oracle.sysman.assistants.rcu.backend.task.AbstractCompTask.execute(AbstractCompTask.java:300)
at oracle.sysman.assistants.rcu.backend.task.ActualTask.run(TaskRunner.java:303)
at java.lang.Thread.run(Thread.java:619)
Caused by: oracle.sysman.assistants.common.task.ActionFailedException: RCU-6136:Error while trying to execute SQLPlus action.
at oracle.sysman.assistants.rcu.backend.action.SQLPlusAction.perform(SQLPlusAction.java:211)
at oracle.sysman.assistants.rcu.backend.task.AbstractCompTask.execute(AbstractCompTask.java:243)
… 2 more
Caused
by: java.io.IOException: java.io.IOException: java.io.IOException:
java.io.IOException: java.io.IOException: java.io.IOException:
java.io.IOException: java.io.IOException: java.io.IOException:
java.io.IOException: java.io.IOException: java.io.IOException: Errorinitializing sqlplus.
at oracle.sysman.assistants.common.dbutil.sqlplus.SQLPlusEngine.setDefaultEngineSettings(SQLPlusEngine.java:2113)
at oracle.sysman.assistants.common.dbutil.sqlplus.SQLPlusEngine.initialize(SQLPlusEngine.java:352)
at oracle.sysman.assistants.rcu.backend.action.SQLPlusAction.perform(SQLPlusAction.java:200)
… 3 more

Solution :

The msvcr71.dll is found under \jdk\bin\

1. Copy \jdk\bin\msvcr71.dll to the RCU_HOME bin directory

2. Launch the RCU program from the RCU_HOME bin directory

RCU_HOME/bin/rcu.bat

You may also need to set the ORACLE_HOME environment variable to your RCU home