Fusion Apps Installation : Database Provisioning Failed during listener start

If you are provisioning database for Fusion Applications and provisioning fails then check logs under $PROVISION_HOME/provisioning/logs/<hostname>/

Depending on phase at which build failed, open corresponding log file

  • Pre Verification – runFusionDB-preverify.log
  • Installation –  runFusionDB-install.log
  • Pre Configuration – runFusionDB-preconfigure.log
  • Configuration – runFusionDB-configure.log

In my case database provisioning failed at Configure phase so I looked at runFusionDB-configure.log where error reported was

______

[2011-10-29T08:40:39.002-04:00] [runFusionDB-configure] [ERROR] [] [runFusionDB-configure] [tid: 10] [ecid: 0000JDFgXQD6ESgvDCoItC1EezGz000000,0]  An error occurred while trying to start the listener process. Please view the log for the Configure step.
______

As error was while starting Database Listener so I checked listener log file at $ORACLE_BASE/diag/tnslsnr/<hostname>/listener_<DB_SID>/trace

/listener_<SID>.log

_______
Started with pid=2095

Listening on: (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=innowave12.com)(PORT=152

3)))Error listening on: (DESCRIPTION=(ADDRESS=(PROTOCOL=IPC)(KEY=EXTPROC1523)))

TNS-12555: TNS:permission denied TNS-12560: TNS:protocol adapter error

  TNS-00525: Insufficient privilege for operation   Linux Error: 1: Operation not permitted

No longer listening on: (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=innowave12.com

)(PORT=1523)))

___________

Root Cause : Old IPC Sockets stored in files  /var/tmp/.oracle (hidden folder) was owned by different user (non root user).

Fix:

1. Stop all listeners running on machine

2. Delete folder /var/tmp/.oracle

3. Create folder /var/tmp/.oracle from root user and change permission to 777

Click on “Retry” button of Fusion Application Database Provisioning Screen

About the Author Masroof Ahmad

Leave a Comment:

4 comments
Add Your Reply