Saturday May 30, 2015

Slow startup on MacBook Pro running OS X

I am running the latest OS X Yosemite (10.10.3) on my MacBook Pro and have noticed that the startup duration has increased recently. When I restarted my computer today, I timed the startup delay and was surprised to see that it took more than 10 seconds to even show the Apple logo. A quick search on the Internet solved the problem for me; I reset the PRAM and my MacBook was back to its older self again.

Here is how to do it:

  1. Shutdown your Mac
  2. Locate the following keys on the keyboard: Option, Command (⌘), P, and R. You will need to hold these keys down simultaneously in step 4.
  3. Turn on your Mac.
  4. Immediately press and hold the Option-Command-P-R keys. You must press this key combination before the gray screen appears.
  5. Continue holding the keys down until your Mac restarts, and you hear the startup sound for the second time.
  6. Release the keys. 

Update: If you have Trim Enabler to support a third party SSD, you must disable Trim before attempting to reset PRAM; see

Wednesday May 07, 2014

How to: Run Repository Creation Utility (RCU) on Solaris

Many of the Oracle Fusion Middleware components require the existence of schemas in a database prior to installation. These schemas are created and loaded in the database using the Repository Creation Utility (RCU). Repository Creation Utility is a graphical and CLI-based tool used to create and manage Oracle Fusion Middleware database schemas.

At this time, RCU is available for Windows and Linux platforms only.

If you want to run RCU on Solaris, edit the RCU executable, <RCU_HOME>/bin/rcu, and make the following changes:
  • Look for the “#Platform Checking” section, and comment out the "exit" statement
  • Look for the line which specifies the JRE_DIR and update it to point to a Solaris JRE or JDK
After making these changes, set the SQLPLUS_HOME variable to point to any ORACLE_HOME and export it before running RCU.

Now you will be able to run RCU on Solaris and create the database objects for Oracle Fusion Middleware.

NOTE: Please note that these instructions should be used for development and testing purposes only, as such it is unsupported and should not be used on production environments.

Tuesday May 06, 2014

Timeout error starting OHS with OAM WebGates on Oracle Solaris (SPARC)

Oracle Access Manager provides single sign-on (SSO), authentication, authorization, and other services to registered agents (in any combination) protecting WebCenter resources. A Web server, Application Server, or any third-party application must be protected by a WebGate or mod_osso instance that is registered with Oracle Access Manager as an agent to enforce policies. The agent acts as a filter for HTTP requests.

This document relates to the following versions of the products:

  • Oracle Web Tier Utilities:
  • OAM WebGates for OHS:

When you try to install and configure Oracle Web Tier Utilities with Oracle OAM WebGates for OHS on Oracle SuperCluster (or Solaris SPARC), the installation and initial configuration may go fine in the beginning. However, once you start putting in your directives for OAM protected resources, you may notice that the OHS component does not start up as it used to.

The opmnctl startall and opmnctl stopall commands take longer than usual with the following error messages. You may also notice that the OHS and OPMN log files do not contain much information.

  user1@hostname1:~$ /u01/oracle/ohs_inst/ohs_server02/bin/opmnctl startall

  opmnctl startall: starting opmn and all managed processes...


  opmn id=hostname1:6701

  Response: 0 of 1 processes started.

  ias-instance id=ohs_server02






  --> Process (index=1,uid=118965811,pid=13118)

  time out while waiting for a managed process to start



The culprit is the webgate.conf include in the httpd.conf file and removing it will resolve the issue. However, now you cannot use OAM for SSO.

You may want to try out the steps in MOS Note 1614464.1 to edit the file; but this may not resolve the issue. I was able to start the OHS server after modifying the file, but got a blank (empty) response when I tried to access the application URLs. I would suggest that you read through the rest of the blog and try the solution below.

The fix to this problem is to add the following entry, where IP_Address is the IP address of the local machine, in /etc/hosts on which Oracle HTTP Server is being installed:

IP_ADDRESS stafas12

Yes, you need to put in this value which may be entirely unrelated to you network configuration into the /etc/hosts file to fix the issue.

You can refer to page 57 in the Oracle Fusion Application Release Notes 11.1.7 in MOS Note 1582125.1 for more details. This document also contains the list of other known issues and their resolutions.


Welcome to my blog. I use this site to share my experience as well as tips and tricks on Oracle Fusion Middleware products.



« November 2015