Thank you for the suggestion, schwertner! Unfortunately, when I run the ORACLE_IDM_HOME/bin/root.s
I appreciate your attempt to help.
Main Topics
Browse All TopicsI have a VM, which is being administered by VMware Lab Manager. The VM is running RHEL 5.1, and has an Oracle 11g database installed.
I am in the process of trying to install and configure Oracle Internet Directory 11g. To do this, I ran the Oracle Fusion Middleware 11g Oracle Identity Management Installer. I selected the "Install Software - Do Not Configure" installation type, and chose to "Configure without a Domain" in order to avoid having to install and administer a WebLogic domain. The installation routine ran successfully.
But, I ran into a problem while trying to configure the Oracle Identity Management 11g components. I ran the Oracle Identity Management 11g Release 1 Configuration Wizard [ORACLE_IDM_HOME/bin/confi
- Oracle Instance Location: /data1/u01/config/oracle/a
- Oracle Instance Name: asinst_1
- Select Domain: Configure without a Domain
- Configure Components: Oracle Internet Directory
- Configure Ports: Auto Port Configuration
- Specify Schema Database: Create Schema
After entering my configuration values and hitting the Configure button, the configuration process started running. Shortly thereafter, under Bootstrap Domain Configuration, "Failed" appeared next to the "Create ASInstance" line, with the following error listed:
Error creating ASInstance asinst_1
Cause: An internal operation has failed: Error in starting opmn server
Operation aborted because of a system call failure or internal error
[I have attached the output from the error log for the Oracle Identity Management 11g Configuration Wizard, in case it would be helpful.]
To get more information, I tried to manually start the opmn server [I set ORACLE_INSTANCE to "/data1/u01/config/oracle/
OPMN worker process exited with status 8b. Restarting.
OPMN worker process exited with status 8b. Restarting.
...
OPMN worker process terminated with signal 11 7 times in 10 seconds -- aborting!
Does anyone know what this error means? I am at a loss as to what to do at this point, so any help would be greatly appreciated.
Thank you!
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.

Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
Thank you for the suggestion, schwertner! Unfortunately, when I run the ORACLE_IDM_HOME/bin/root.s
I appreciate your attempt to help.
As a follow-up, I wanted to let everyone know that the problem was relative to my VM. When I installed the software on a regular laptop, things worked without any problems.
In debugging the problem, my VMware Lab Manager administrator found that the error occurred with ESX 3.5.0 123630 running on a Dell PowerEdge R805 with an Athlon processor (the VM was assigned 2GB of memory and 1 CPU). The error did not occur with ESXi 4.0.0 164009 running on a Dell PowerEdge 2950 with a Xeon processor (the VM was assigned 2GB of memory and 1 CPU).
So, at this point, we suspect that the LabManager software with ESX 3.5.0 is the problem. We have a LabManager upgrade with ESX 4.0 waiting in the wings, but it may take a bit for the right people to find time to install it. If, for some reason, the LabManager upgrade does not fix the problem, then it is possible that Oracle is having an issue with the Athlon host processor.
Business Accounts
Answer for Membership
by: schwertnerPosted on 2009-08-19 at 04:56:02ID: 25131566
One asker wrote me: while working with Oracle Support, they suggested we check permissions and ownership on the oidldapd file.
They then also stated that these permissions could be set by running the root.sh script.
We went ahead and ran that script and then when it came to the question,
"Enter the full pathname of the local bin directory: /usr/local/bin", we stopped and thought about it.
Previously, we would just take the default /usr/local/bin but this time we decided to use the $ORACLE_HOME/bin directory.
This was the key that we were looking for. The application server started right up. It is the little things that will stop you cold.