Thursday, July 14, 2016

Tips: Set OVD 11g Debug Logs to Trace level

Step 1

1. Open ODSM
2. Click Advanced tab
3. Click/Expand Global Plugin
4. Click on the button to Create Plug-in 
5. For Name put for ex. myDumpTr
6. For Class choose DumpTransactions
7. Click on the button Create Parameter
8. For Name write loglevel 
9. For Value write FINEST
10.Cick Ok

Step 2:

1. Open Oracle Enterprise Manager, access http://<host>:<port>/em login with user name Weblogic (or whatever other user that you choose for admin)
2. Expand -> Farm_<name>Domain -> Identity and Access right click ovd1 ->choose Logs -> Log Configuration
3. Click Log Levels tab
 For Logger Name -- com.octetstring.accesslog choose TRACE:32 (FINEST)
 For Logger Name -- com.octetstring.vde choose TRACE:32 (FINEST)
4. Click Apply
5. Click Close in Confirmation dialog box

Stop OVD:

$ORACLE_INSTANCE/bin/opmnctl stopproc ias-component=ovd1

Start OVD:

$ORACLE_INSTANCE/bin/opmnctl startproc ias-component=ovd1


Check logs in $ORACLE_INSTANCE/diagnostics/logs/OVD/ovd1/ location

Tuesday, July 12, 2016

Fix: OAAM 11g R2 PS3 issue to generate OMA offline secret key

Issue:

Unable to generate OMA offline secret key when using OUD as OAM user store(there is no issue when tested with weblogic embedded LDAP).

Error from log file:

<Jul 12, 2016 11:30:49 AM EDT> <Warning> <oracle.ods.virtualization.engine.backend.jndi.OUD> <LIBOVD-40066> <Remote Server Failure:pokuri.demo.com:1389.
javax.naming.NamingException: [LDAP: error code 123 - You do not have sufficient privileges to use the proxied authorization control]; remaining name 'cn=users,dc=demo,dc=com'
at com.sun.jndi.ldap.LdapCtx.mapErrorCode(LdapCtx.java:3169)
at com.sun.jndi.ldap.LdapCtx.processReturnCode(LdapCtx.java:3013)
at com.sun.jndi.ldap.LdapCtx.processReturnCode(LdapCtx.java:2820)

at com.sun.jndi.ldap.LdapCtx.searchAux(LdapCtx.java:1829)

Solution:

Uncheck "Proxy Authentication" option in "OAuth User Profile Service Configuration"(Proxy Authentication is enabled by default) then click on Apply.




Thursday, July 7, 2016

How to Upgrade Oracle Coherence


Upgrade instructions to install Coherence 3.7.1.x on Oracle Access Manager 11gr2 (OAM 11.1.2.0.0) to Oracle Access Manager 11gr2PS2 (OAM 11.1.2.2.0)

1. Download desired coherence patch from Note:1405110.1

2. Shutdown all the servers.

3. On the each Server including the admin server, do the following.

     a. Unzip the contents of the patch to tmp folder.

     b. Backup the jar that exists at the location      MW_HOME/oracle_common/modules/oracle.coherence/coherence.jar

     c. copy the jar tmp/coherence/lib/coherence.jar to the folder MW_HOME/oracle_common/modules/oracle.coherence

     d. Backup the folder $Domain/config and all its nested contents.

4. Start the Admin Server

5. Log into weblogic console

6. Lock configuration

7. Select Deployments and locate the coherence library

8. Select the library and press the Delete button.

9. Release Configuration and apply changes.

10. Lock configuration

11. Select Deployments and press the Install button.

12. Select the coherence jar in the file path. Ensure that the library name is "coherence". Hit the next button till you finish deployments.

13. Save and release the configuration.

14. Stop And Start the Admin Server. Verify the the oam_admin deployment is started.