This chapter describes common problems that you might encounter when using Oracle Identity and Access Management Deployment tools, and explains how to solve them.
In addition to this chapter, review the Oracle Fusion Middleware Error Messages Reference for information about the error messages you may encounter.
This chapter contains the following sections:
This section describes how to use the log files and how to recover from deployment failures. It contains the following topics:
If you are performing deployment using the wizard, from any phase screen, click the icon under the Log field to see the logs for the current phase. A new window opens showing the logs. The logs are searchable using the search box at the top of this new window. The log window does not refresh on its own, so click the refresh button next to the search box at the top of this window to refresh the logs.
To check why a phase failed when the wizard is not running, check the corresponding logs files present under the logs directory. On Linux, this is LCM_HOME/provisioning/logs/hostname.
LCM_HOME is the Lifecycle Management Store Location directory that you specified on the Installation and Configuration screen when you created the deployment profile. See Section 4.4.1.8, "Select Installation and Configuration Locations."
Oracle Identity and Access Management Deployment does not have any backup or recovery mechanism, so you must start from the beginning if case of a failure.
In addition, if you perform a workaround that requires you to rerun Oracle Identity and Access Management Deployment, you must clean up the environment before rerunning it. For more information about cleaning up an environment, see Appendix A, "Cleaning Up an Environment Before Rerunning IAM Deployment".
This section describes common problems and solutions. It contains the following topics:
Section 8.2.1, "Null Error Occurs When WebLogic Patches Are Applied"
Section 8.2.3, "Oracle Identity and Access Management Deployment Wizard Hangs (Linux and UNIX)"
Section 8.2.4, "Error Occurs When Running RCU on 64-bit Linux"
Section 8.2.5, "Other Identity and Access Management Deployment Issues"
During Oracle Identity and Access Management deployment, patches are applied to all products deployed, including WebLogic. This entails running the Smart Update bsu command. This command may fail without producing a detailed error message.
In this case, the failure is likely caused by directory paths that are longer than what the bsu command supports. You can verify this by running the bsu command manually, passing it the -log option, and looking for a stack trace containing a message such as the following:
java.lang.IllegalArgumentException: Node name?a?very?long?path?which?may?cause?problems?leading?to?an?IDMTOP?products?dir?utils?bsu?cache_dir too long
For more information, see the chapter "Using the Command Line Interface" in Oracle Smart Update Applying Patches to OracleWebLogic Server.
When planning the IDM deployment, ensure that the IDM_TOP path is 45 characters or fewer in length.
If you run the Identity Management Patch Manager progress command after Oracle Identity and Access Management Deployment completes, the output shows an active session specific to Identity Management Deployment, which is listed as ACTIVE, and contains a set of PLANNED steps.
You can safely ignore this output. The deployment-driven patch session is complete, and all steps which needed to run have run. Creating a new patch session will silently replace this special session without error.
The Oracle Identity and Access Management Deployment Wizard hangs. Neither the Next nor the Back button is active.
This problem is due to stale NFS file handles.
On Linux or UNIX, issue the following command:
df –k
Record the output of the df command, even if it is successful, in case further analysis is necessary. For example, take a screenshot.
If the df command hangs or is unsuccessful, work with your system administrator fix the NFS problem.
After the NFS problem has been resolved and the df command finishes successfully, run deployment again.
Repository Creation Utility (RCU) creates the required database schemas for Identity and Access Management components.
On 64-bit Linux, when you try to run RCU by executing the ./rcu command from the RCU_HOME/bin directory, the following error message is displayed:
Failed to initialize logger with location :/home/oracle/rcuHome/rcu/log/logdir.2013-02-25_15-42/rcu.log Initializing logger using the following location :/tmp/logdir.2013-02-25_15-42/rcu.log Exception in thread "main" java.lang.UnsatisfiedLinkError: /home/oracle/rcuHome/jdk/jre/lib/i386/xawt/libmawt.so: libXext.so.6: cannot open shared object file: No such file or directory at java.lang.ClassLoader$NativeLibrary.load(Native Method) at java.lang.ClassLoader.loadLibrary0(ClassLoader.java:1807) at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1703) at java.lang.Runtime.load0(Runtime.java:770) at java.lang.System.load(System.java:1003) at java.lang.ClassLoader$NativeLibrary.load(Native Method) at java.lang.ClassLoader.loadLibrary0(ClassLoader.java:1807) at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1724) at java.lang.Runtime.loadLibrary0(Runtime.java:823) at java.lang.System.loadLibrary(System.java:1028) at sun.security.action.LoadLibraryAction.run(LoadLibraryAction.java:50) at java.security.AccessController.doPrivileged(Native Method) at java.awt.Toolkit.loadLibraries(Toolkit.java:1605) at java.awt.Toolkit.<clinit>(Toolkit.java:1627) at com.jgoodies.looks.LookUtils.isLowResolution(LookUtils.java:484) at com.jgoodies.looks.LookUtils.<clinit>(LookUtils.java:249) at com.jgoodies.looks.plastic.PlasticLookAndFeel.<clinit>(PlasticLookAndFeel.java:135) at oracle.sysman.assistants.rcu.ui.InteractiveRCUModel.<init>(InteractiveRCUModel.java:117) at oracle.sysman.assistants.rcu.Rcu.execute(Rcu.java:307) at oracle.sysman.assistants.rcu.Rcu.main(Rcu.java:363)
This error message is displayed because RCU is supported only on 32-bit Linux.
To run RCU on 64-bit Linux, use the following workaround:
Go to the RCU_HOME directory, and create a backup of the jdk directory.
cd RCU_HOME
mv jdk jdk.bak
Create a link to the 64-bit JDK folder using the ln command.
ln -s /home/oracle/jdk1.6.0_35 jdk
Execute the ./rcu command from the RCU_HOME/bin directory.
If you are facing any other deployment issues, see the section "Troubleshooting Identity and Access Management Deployment" in the Oracle Fusion Middleware Enterprise Deployment Guide for Oracle Identity and Access Management. This section provides information about some of the other common problems related to deployment.
You can use My Oracle Support (formerly MetaLink) to help resolve Oracle Fusion Middleware problems. My Oracle Support contains several useful troubleshooting resources, such as:
Knowledge base articles
Community forums and discussions
Patches and upgrades
Certification information
Note:
You can also use My Oracle Support to log a service request.You can access My Oracle Support at https://support.oracle.com.