Category: GI and RAC

19c gridSetup.sh throws errors: PRVG-11095 : The TCP system call “connect” failed with error “113” while executing exectask on node “racnode2”

The following errors occur when running Oracle 19c gridSetup.sh:

Summary of node specific errors racnode2  
- PRVG-11067 : TCP connectivity from node "racnode2": "10.2.2.2" to node "racnode1": "10.2.2.1" failed.
PRVG-11095 : The TCP system call "connect" failed with error "113" while executing exectask on node "racnode2"
No route to host  - Cause:  Errors occurred while attempting to establish Transmission Control Protocol (TCP) connectivity between the identified two interfaces.  
- Action:  Ensure that there are no firewalls blocking TCP operations and no process monitors running that can interfere with programs'' network operations. racnode1  - PRVG-11067 : TCP connectivity from node "racnode1": "10.2.2.1" to node "racnode2": "10.2.2.2" failed.

PRVG-11095 : The TCP system call "connect" failed with error "113" while executing exectask on node "racnode1"
No route to host  - Cause:  Errors occurred while attempting to establish Transmission Control Protocol (TCP) connectivity between the identified two interfaces.  
- Action:  Ensure that there are no firewalls blocking TCP operations and no process monitors running that can interfere with programs'' network operations.

SOLUTION

Stop and disable firewalld.

# systemctl status firewalld

# systemctl stop firewalld

# systemctl disable firewalld

What is SYSRAC ?

The SYSRAC administrative privilege is used only by the Oracle agent of Oracle Clusterware to connect to the database using operating system authentication.

Unlike SYSDBA, SYSDG, SYSBACKUP and SYSKM , the SYSRAC privilege only allows OS authentication by the Oracle agent of Oracle Clusterware. Password files and strong authentication cannot be used with the SYSRAC privilege.

SQL> grant sysrac to testuser container=all;

grant sysrac to testuser container=all

*

ERROR at line 1:

ORA-28190: SYSRAC administrative privilege cannot be granted to other users

The administrative privilege SYSRAC is not supported in the password file.

When you create an Oracle database, the following users are automatically created to facilitate separation of duties for database administrators: SYSBACKUP, SYSDG, SYSKM, and SYSRAC.

  • SYSBACKUP facilitates Oracle Recovery Manager (RMAN) backup and recovery operations either from RMAN or SQL*Plus.
  • SYSDG facilitates Data Guard operations. The user can perform operations either with Data Guard Broker or with the DGMGRL command-line interface.
  • SYSKM facilitates Transparent Data Encryption keystore operations.
  • SYSRAC facilitates Oracle Real Application Clusters (Oracle RAC) operations by connecting to the database by the Clusterware agent on behalf of Oracle RAC utilities such as SRVCTL.
  • The SYSRAC administrative privilege cannot be granted to database users and is not supported in a password file. The SYSRAC administrative privilege is used only by the Oracle agent of Oracle Clusterware to connect to the database using operating system authentication.

SYSBACKUP, SYSDG, SYSKM, and SYSRAC user accounts cannot be dropped.

PRVG-11138 PRVG-11352 When Running cluvfy or runcluvfy.sh

When running runcluvfy.sh or cluvfy, the following messages appear:

Multicast or broadcast check - This task checks that network interfaces in subnet are able to communicate over multicast group or broadcast IP address Details: 

 - 

PRVG-11138 : Interface "ens8" on node "racnode1" is not able to communicate with interface "ens8" on node "racnode1" over multicast group "224.0.0.251"  - Cause:  The specified interfaces were not able to communicate using a multicast address.  - Action:  Ensure that multicast is enabled on the specified interfaces and that a network path exists between the interfaces. 

 - 

PRVG-11138 : Interface "ens8" on node "racnode1" is not able to communicate with interface "ens8" on node "racnode1" over multicast group "230.0.1.0"  - Cause:  The specified interfaces were not able to communicate using a multicast address.  - Action:  Ensure that multicast is enabled on the specified interfaces and that a network path exists between the interfaces. 

 - 

PRVG-11352 : Interface "192.168.112.11" on node "racnode1" is not able to communicate with interface "192.168.112.11" on node "racnode1" with broadcast address "255.255.255.255"  - Cause:  The specified interfaces were not able to communicate using the broadcast address.  - Action:  Ensure that broadcast is enabled on the specified interfaces and that the network path allows broadcast.

SOLUTION

Stop and disable firewalld.

# systemctl status firewalld

# systemctl stop firewalld


# systemctl disable firewalld

# systemctl status firewalld

gridSetup.sh ERROR: Unable to verify the graphical display setup. This application requires X display. Make sure that xdpyinfo exist under PATH variable.

When setting up 19c GI by running “gridSetup.sh”, the following errors occur:

 $ ./gridSetup.sh

ERROR: Unable to verify the graphical display setup. This application requires X display. Make sure that xdpyinfo exist under PATH variable.



No X11 DISPLAY variable was set, but this program performed an operation which requires it.

SOLUTION

Enable X11forwarding in /etc/ssh/sshd_config.

# ls -ltr /etc/ssh/sshd_config
-rw——-. 1 root root 4131 Apr 4 2023 /etc/ssh/sshd_config

# vi /etc/ssh/sshd_config

X11Forwarding yes

# systemctl restart sshd

OPatch Error: This Java instance does not support a 64-bit JVM.opatch

When trying to run opatch, the following error occurs:

$ opatch

Error: This Java instance does not support a 64-bit JVM.

Please install the desired version.



OPatch failed with error code 1

SOLUTION

Download the right opatch.

For 19c opatch on Linux x86-64 download “p6880880_190000_Linux-x86-64.zip” instead of “p6880880_190000_Linux.zip”.