Solving Remote Monitoring problems

If the configured Oracle instance is remote, use the following information to solve problems of discovering the remote instance, or discovering the remote file system information.

A remote Oracle instance means running the SQL Command Line, or any other Oracle command-line utility, on a computer other than the Oracle database host computer, and then initiating a database connection from the SQL Command Line, or another utility, over the network.

Remote instance not been discovered

If the customer configured remote Oracle instance is not seen in the hierarchy tree, try using either of the following solutions.

SQL*PLUS utility connection failed

Confirm that the SQL*PLUS utility can establish a connection from the Patrol Agent host to the remote host of the Oracle instance.

Through the SQL*PLUS utility, enter the following commands:

export ORACLE_HOME=<local client home>

export PATH=$PATH:$ORACLE_HOME/bin

sqlplus user/password@TNS_STRING_TO_REMOTE_INSTANCE

In this command, the TNS string is used to connect to the remote instance from the local $ORACLE_HOME/network/admin/tnsnames.ora file. In the following tnsnames.ora example, ORCL is the TNS string.

sqlplus user/password@ORCL

“ORCL =

(DESCRIPTION =

(ADDRESS = (PROTOCOL = TCP)(HOST = oraclehost.bmc.com)(PORT = 1521))

(CONNECT_DATA =

(SERVER = DEDICATED)

(SERVICE_NAME = orcl.bmc.com)

)

)”


No Oracle remote service

The Oracle service remote instance is not configured on the local host.

Confirm that the Oracle Database Client is installed on the Patrol Agent host, and that you have added the TNS service entry name from the tnsnames.ora file on the Patrol Agent host.

Remote instance file system information is not available

You configured a remote Oracle instance but there is missing filesystem information.

Try using one of the following solutions to gain access the filesystem information.

The Oracle KM remote package is missing

Confirm the following:

  • The Oracle KM remote package, which includes the alreader and olreader utilities, is installed on the remote host.
  • The Secure Shell (SSH) user has execute privileges on these utilities.

The remote host is not registered

Check the following to confirm support for remote hosting:

  • Remote monitoring is only supported by Linux-to-Linux or Unix-to-Unix systems. There is no Windows support for remote monitoring.
  • Confirm that the remote host has been successfully registered on the system where the remote instance is running.
  • Try using the full host name for the remote host.

The Remote Host is not reachable

Confirm that the SSH connection can be established from the Patrol Agent host to the remote host, and that the the SSH user and password are correctly entered.

Related topic

Configuring instances for remote monitoring

Was this page helpful? Yes No Submitting... Thank you

Comments