Shulou(Shulou.com)05/31 Report--

This article mainly shows you the "RHEL 7 installation oracle rac 11.2.0.4 implementation of root.sh error ohasd failed to start how to do", the content is easy to understand, clear, hope to help you solve doubts, the following let the editor lead you to study and learn "RHEL 7 installation oracle rac 11.2.0.4 implementation of root.sh error ohasd failed to start how to do" this article.

Error message:

[root@rac1 ~] # / u01/app/oraInventory/orainstRoot.sh

Changing permissions of / u01/app/oraInventory.

Adding read,write permissions for group.

Removing read,write,execute permissions for world.

Changing groupname of / u01/app/oraInventory to oinstall.

The execution of the script is complete.

[root@zjdb1 ~] # / u01/app/11.2.0/grid/root.sh

Performing root user operation for Oracle 11g

The following environment variables are set as:

ORACLE_OWNER= grid

ORACLE_HOME= / u01/app/11.2.0/grid

Enter the full pathname of the local bin directory: [/ usr/local/bin]:

Copying dbhome to / usr/local/bin...

Copying oraenv to / usr/local/bin...

Copying coraenv to / usr/local/bin...

Creating / etc/oratab file...

Entries will be added to the / etc/oratab file as needed by

Database Configuration Assistant when a database is created

Finished running generic part of root script.

Now product-specific root actions will be performed.

Using configuration parameter file: / u01/app/11.2.0/grid/crs/install/crsconfig_params

Creating trace directory

User ignored Prerequisites during installation

Installing Trace File Analyzer

OLR initialization-successful

Root wallet

Root wallet cert

Root cert export

Peer wallet

Profile reader wallet

Pa wallet

Peer wallet keys

Pa wallet keys

Peer cert request

Pa cert request

Peer cert

Pa cert

Peer root cert TP

Profile reader root cert TP

Pa root cert TP

Peer pa cert TP

Pa peer cert TP

Profile reader pa cert TP

Profile reader peer cert TP

Peer user cert

Pa user cert

Adding Clusterware entries to inittab

Ohasd failed to start

Failed to start the Clusterware. Last 20 lines of the alert log follow:

2015-05-23 23 3715 45.460:

[client (13782)] CRS-2101:The OLR was formatted using version 3.

Reason for reporting an error:

Because RHEL 7 runs and restarts processes using systemd instead of initd, root.sh runs ohasd processes through traditional initd.

Solution:

In RHEL 7, ohasd needs to be set up as a service before running the script root.sh.

The steps are as follows:

1. Create a service file as a root user

# touch / usr/lib/systemd/system/ohas.service

# chmod 777 / usr/lib/systemd/system/ohas.service

two。 Add the following to the newly created ohas.service file

[root@rac1 init.d] # cat / usr/lib/systemd/system/ohas.service

[Unit]

Description=Oracle High Availability Services

After=syslog.target

[Service]

ExecStart=/etc/init.d/init.ohasd run > / dev/null 2 > & 1 Type=simple

Restart=always

[Install]

WantedBy=multi-user.target

3. Run the following command as the root user

Systemctl daemon-reload

Systemctl enable ohas.service

Systemctl start ohas.service

4. View running status

[root@rac1 init.d] # systemctl status ohas.service

Ohas.service-Oracle High Availability Services

Loaded: loaded (/ usr/lib/systemd/system/ohas.service; enabled)

Active: failed (Result: start-limit) since Fri 2015-09-11 16:07:32 CST; 1s ago

Process: 5734 ExecStart=/etc/init.d/init.ohasd run > / dev/null 2 > & 1 Type=simple (code=exited, status=203/EXEC)

Main PID: 5734 (code=exited, status=203/EXEC)

Sep 11 16:07:32 rac1 systemd [1]: Starting Oracle High Availability Services...

Sep 11 16:07:32 rac1 systemd [1]: Started Oracle High Availability Services.

Sep 11 16:07:32 rac1 systemd [1]: ohas.service: main process exited, code=exited, status=203/EXEC

Sep 11 16:07:32 rac1 systemd [1]: Unit ohas.service entered failed state.

Sep 11 16:07:32 rac1 systemd [1]: ohas.service holdoff time over, scheduling restart.

Sep 11 16:07:32 rac1 systemd [1]: Stopping Oracle High Availability Services...

Sep 11 16:07:32 rac1 systemd [1]: Starting Oracle High Availability Services...

Sep 11 16:07:32 rac1 systemd [1]: ohas.service start request repeated too quickly, refusing to start.

Sep 11 16:07:32 rac1 systemd [1]: Failed to start Oracle High Availability Services.

Sep 11 16:07:32 rac1 systemd [1]: Unit ohas.service entered failed state.

The status is failed at this time because there is no / etc/init.d/init.ohasd file yet.

Now you can run the script root.sh without reporting any more ohasd failed to start errors.

If the ohasd failed to start error is still reported, it may be that ohas.service did not start immediately after the root.sh script created the init.ohasd. For more information on the solution, please see the following:

When running root.sh, refresh / etc/init.d until the init.ohasd file appears, and immediately manually start the ohas.service service command: systemctl start ohas.service

[root@rac1 init.d] # systemctl status ohas.service

Ohas.service-Oracle High Availability Services

Loaded: loaded (/ usr/lib/systemd/system/ohas.service; enabled)

Active: active (running) since Fri 2015-09-11 16:09:05 CST; 3s ago

Main PID: 6000 (init.ohasd)

CGroup: / system.slice/ohas.service

6000 / bin/sh / etc/init.d/init.ohasd run > / dev/null 2 > & 1 Type=simple

6026 / bin/sleep 10

Sep 11 16:09:05 rac1 systemd [1]: Starting Oracle High Availability Services...

Sep 11 16:09:05 rac1 systemd [1]: Started Oracle High Availability Services.

Sep 11 16:09:05 rac1 su [6020]: (to grid) root on none

The above is all the contents of the article "what to do when RHEL 7 installs oracle rac 11.2.0.4 and executes root.sh error ohasd failed to start". Thank you for reading! I believe we all have a certain understanding, hope to share the content to help you, if you want to learn more knowledge, welcome to follow the industry information channel!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.