000028138 - KB-1379 - ORACLE_HOME_LISTENER is not SET error

Document created by RSA Customer Support Employee on Jun 14, 2016Last modified by RSA Customer Support Employee on Apr 21, 2017
Version 2Show Document
  • View in full screen mode

Article Content

Article Number000028138
Applies ToAffected Versions: 4.X; 3.6.X
IssueIf you receive one of the following messages when starting or stopping Oracle, using ACM dbora service:
Stopping oracle: ORACLE_HOME_LISTENER is not SET, unable to auto-stop Oracle Net Listener
Or
Starting oracle: ORACLE_HOME_LISTENER is not SET, unable to auto-start Oracle Net Listener
Causethese are not fatal errors.
The listener is getting started or stopped correctly by the script. The issue is the /etc/init.d/dbora script used to start and stop Oracle and the listener is out of date.It uses an Oracle 9 format in place of the Oracle 10/11 format to start and stop the database.
The problem occurs because the start/stop database line attempts to start/stop the listener but the version 10 oracle home directory ($ORACLE_HOME) is not specified on the start line so the listener cannot be started by the database startup or shutdown script. However the very next line in this default script starts or stops the listener so no damage is done.
You can manually modify the script to resolve this or replace it with the attached script.
However upgrades may overwrite the changes.
ResolutionTo modify the script:
1. Become root
2. Change directories to /etc/init.d
3. Using your favorite editor edit the "dbora" script
4. To Change the startup portion:
a. On line 25 (version 3) or line 127 (version 4) change the database start line:
from: su - $ORA_OWNER -c "$ORA_HOME/bin/dbstart"
to: su - $ORA_OWNER -c "$ORA_HOME/bin/dbstart $ORA_HOME" (version 3)
su - $ORA_OWNER -c "$ORA_HOME/bin/dbstart $ORACLE_HOME" (version 4)
b. Comment out line 26 (version3) / 128 (version 4) by placing a "#" character in column 1
6. Change the database stop portion of the script
a. On line 47 (Version3) or 149 (version 4) change the database stop line:
from: su - $ORA_OWNER -c "$ORA_HOME/bin/dbshut"
to: su - $ORA_OWNER -c "$ORA_HOME/bin/dbshut $ORA_HOME" (version 3)
su - $ORA_OWNER -c "$ORA_HOME/bin/dbshut $ORACLE_HOME" (version 4)
b. Comment out line 48 (version3) 150 (version 4) by placing a "#" character in column 1
7. Save and quit the file
8. Test the database stop by running the commands
a. ./dbora stop
b. There should be no errors on the console
b. Cnsure the database and listener have stopped
9. Test the database start by running the commands
a. ./dbora start
b. There should be no errors on the console
b. Cnsure the database and listener now be running
10. Restart the Aveksa Server / Agent
11. Validate you can correctly connect to the UI.

To upload the modified script:
1. Download the attached dbora.3 or doboa.4 script to your local machine
2. Upload the script to the target appliance (in /tmp)
3. Log into the appliance as root
4. Run the following commands
a. mv /etc/init.d/dbora /etc/init.d/dbora.ORIG
b. cd /tmp (or wherever you uploaded the dbora script)
c.mv dbora.3|4 dbora
d. dos2unix /tmp/dbora
e. chmod 766 /tmp/dbora
f. cp -f /tmp/dbora /etc/init.d
5. Test the shutdown / start-up using steps 8-11 listed above.  

Attachments

    Outcomes