| Oracle® Fusion Middleware Identity Management Provisioning Guide (Oracle Fusion Applications Edition) 11g Release 7 (11.1.7) Part Number E41444-02 |
|
|
PDF · Mobi · ePub |
| Oracle® Fusion Middleware Identity Management Provisioning Guide (Oracle Fusion Applications Edition) 11g Release 7 (11.1.7) Part Number E41444-02 |
|
|
PDF · Mobi · ePub |
This chapter describes common problems that you might encounter when using Identity Management Provisioning 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 provisioning failures. It contains the following topics:
If you are monitoring provisioning using the wizard, from any phase screen, click on 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 on the refresh button besides 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 IDMTOP/config/provisioning/logs/hostname. On Windows, this is IDMTOP\config\provisioning\logs\hostname.
IDMTOP is the Software Installation Location directory you specified on the Installation and Configuration page when you created the provisioning profile. See Section 4.2.7, "Install Location Configuration Page."
Identity Management Provisioning does not have any backup or recovery mechanism, so you must to start from the beginning if case of a failure.
If you perform a workaround that requires you to rerun Identity Management Provisioning, you must clean up the environment before rerunning it. Proceed as follows:
Stop all running services and servers using idmtop\config\scripts\stopall.bat on Windows or idmtop/config/scripts/stopall.sh on UNIX. Then remove the idmtop folder. If you used a Shared Configuration Location, as described in Section 4.2.7, "Install Location Configuration Page," delete that directory.
Remove previously created Identity Management directories from the PATH environment variable, including DIR, APP, and the OHS Oracle home.
Run RCU to drop all schema before the next attempt.
Note:
While dropping schema using RCU, ensure that you explicitly select the ODS schema so that it also gets dropped. It is NOT selected by default, unlike other schema.
Reboot the machine to ensure that all server instances are stopped.
This section describes common problems and solutions. It contains the following topics:
Section 7.2.1, "Missing ODSM Instance Directory on Second Node"
Section 7.2.2, "Null Error Occurs When WebLogic Patches Are Applied"
Section 7.2.4, "Spurious OPatch Error Messages Printed to Log During Install Phase"
Section 7.2.5, "Identity Management Provisioning Wizard Hangs (Linux and UNIX)"
Section 7.2.6, "Provisioning Fails During Install Phase (Linux)"
Section 7.2.8, "Provisioning Fails if Installer Repository Location Is a UNC Path (Windows)"
Section 7.2.9, "Identity Management Provisioning Fails During Preconfigure Phase (Windows)"
Section 7.2.10, "Cannot Log In to the Oracle Identity Federation Server (Windows)"
Section 7.2.11, "Error When Starting Oracle Access Manager Managed Servers (Windows)"
Problem
After you run the Identity Management Provisioning Wizard, only one instance directory for Oracle Directory Services Manager is installed.
Solution
The absence of the ODSM instance directory on the second node does not result in any loss of function.
Problem
During IDM provisioning, patches are applied to all products provisioned, including WebLogic. This entails running the Smart Update bsu command. This command may fail without producing a detailed error message.
Cause
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.
Solution
When planning the IDM deployment, ensure that the IDM_TOP path is 45 characters or fewer in length.
Problem
If you run the Identity Management Patch Manager progress command after Identity Management Provisioning completes, the output shows an active session specific to Identity Management Provisioning, which is listed as ACTIVE, and contains a set of PLANNED steps.
Solution
You can safely ignore this output. The provisioning-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.
Problem
During the install phase of provisioning, you may see a message Starting binary patching for all-binary-patch components ..., followed by a series of OPatch failure messages prefaced with the string prepatch within the provisioning log. These errors contain the string Failed to load the patch object.
Solution
These messages are harmless and can be safely ignored.
Problem
The IdentityManagement Deployment Wizard hangs. Neither the Next nor the Back button is active.
Cause
This problem is due to stale NFS file handles.
Solution
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 provisioning again.
Problem
Provisioning fails during the Install phase.
Cause
Some 32-bit libraries such as crt1.o are missing.
Solution
There are two ways to fix this. Do one of the following:
Copy the 32 -bit libraries gcrt1.o, crtn.o, crti.o, crt1.o, Scrt1.o, and Mcrt1.o from /usr/lib/ on another machine running the same version.
Install the missing package glibc-devel.i686
Problem
The Oracle Internet Directory configuration fails on the Windows 2008 Server R2 +SP1, causing the IdentityManagement Provisioning Wizard to fail.
Solution
After the installation of the Identity Management Provisioning Wizard has finished:
1. Edit the sqlnet.ora file in the Oracle Internet Directory environment folder
%ORACLE_HOME%\network\admin
Set the ADR_BASE parameter to a folder other than the Oracle home, for example,
C:\temp.
2. If it does not exist already, add an sqlnet.ora file to that folder and ensure that it contains the ADR_BASE parameter, set to the same value as in Step 1.
Problem
Provisioning fails at install time on Microsoft Windows with an error message similar to this:
[logStatus] STATE=BUILD_STARTED!TIMESTAMP=2013-03-26 04:56:28 MDT!TARGET=installwls!CATEGORY=Weblogic!DOMAIN=NONE!HOSTNAME=slc02jqf!PRODUCT FAMILY=orchestration!PRODUCT=orchestration!TASK=install!TASKID=orchestration.orchestration.NONE.installwls. NONE!MESSAGE=Starting install for weblogic for C:\idmtop/products/dir!DETAIL=!BUILDFILE=c:\idminstaller\Oracle_IDMLCM1\provisioning\idm-provisioning-build\idm-commonbuild. xml!LINENUMBER=33![2013-03-26T04:56:30.693-06:00] [runIDMProvisioning-install] [NOTIFICATION][] [runIDMProvisioningt-install] [tid: 12] [ecid:0000JqaLtN_B1FH5Ivt1if1HKNuO000003,0] [exec] java.lang.ClassNotFoundException:com.bea.cie.gpr.internal.model.DelegateHomeListHelper
Cause
This error occurs because you are accessing the Software Repository using a UNC path. That is, you are using a path of the form \\server\share.
Solution
To resolve this issue, map the share to a local disk and then specify the repository location using the local disk path.
Problem
When you attempt to perform provisioning, using the provisioning response file, it fails during the Preconfigure phase, with an error similar to this:
TASKID=orchestration.orchestration.BUILD_ERROR.NONE.installNodeManager!MESSAGE =Error exit code 1069 from C:\Windows\system32\sc.exe!DETAIL=Error exit code 1069 from C:\Windows\system32\sc.exe!
Cause
Node Manager fails to start due to a password error.
Solution
Perform the steps described in Section 3.6, "Setting Up Required User (Windows)."
Problem
On a Windows system, after performing Identity Management Provisioning, you cannot log in to the Oracle Identity Federation server even though it is running.
Solution
Make sure that the Oracle Identity Federation server is using IPv4.
To verify this, look in the file setDomainEnv.cmd,
Locate the line EXTRA_JAVA_PROPERTIES and add the following to the entry if it is not already present:
-Djava.net.preferIPv6Addresses -DuseIPv6Address=false -Djava.net.preferIPv6Addresses=false
Save the file and restart the Oracle Identity Federation servers.
Problem
On Windows, after performing Identity Management Provisioning, when you start the OAM managed servers, you see an error similar to this:
Caused by: java.net.SocketException: Address family not supported by protocolfamily: bind
Solution
Edit setDomainEnv.cmd and add the following parameters to the environment variable EXTRA_JAVA_PROPERTIES:
-DuseIPv6Address=false -Djava.net.preferIPv6Addresses=false
Restart the Administration Server and all Managed Servers that are running.
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.
|
 Copyright © 2004, 2013, Oracle and/or its affiliates. All rights reserved. Legal Notices |
|
