Oracle probe not working properly and throwing Oracle errors
search cancel

Oracle probe not working properly and throwing Oracle errors

book

Article ID: 260571

calendar_today

Updated On:

Products

DX Unified Infrastructure Management (Nimsoft / UIM) CA Unified Infrastructure Management On-Premise (Nimsoft / UIM) CA Unified Infrastructure Management SaaS (Nimsoft / UIM)

Issue/Introduction

The oracle probe on a few robots is not working and unable to troubleshoot what is the issue.

When testing the connection, the error is "Please check the connection details, also make sure your database servers are up & running"

The database services is working well and I am able to login to the database with the user with whom we are performing the test.

oracle: Profile: xxxxxx, Oracle error! Status: -1, - ORA-01034: ORACLE not available
ORA-27101: shared memory realm does not exist
Linux-x86_64 Error: 2: No such file or directory

Environment

DX UIM 20.4.x / 23.4.x

oracle probe v5.45

Resolution

Please follow the oracle probe documentation at:

Oracle Database monitoring release notes

oracle client (correct version and bit) matching the server, MUST be installed.

Oracle Supported Versions and Clients

Ask the DBA to try to connect via sqlplus from the robot where the oracle probe is running.

Oracle database issues here that an Oracle DBA should examine - this has nothing to do with the oracle probe itself.

ORA-01034: ORACLE not available

In this case, check if the oracle instance is up and running...for example,

bash-3.00$ sqlplus / as sysdbaSQL*Plus: Release 11.2.0.4.0 Production on Tue Sep 6 08:37:00 2016Copyright (c) 1982, 2013, Oracle.  All rights reserved.Connected to:Oracle Database 11g Enterprise Edition Release 11.2.0.4.0 - 64bit ProductionWith the Partitioning, Data Mining and Real Application Testing options

ORA-27101: shared memory realm does not exist

and

oracle: Profile: <server_name>/tablespace_temp_free, RunQuery - connect failed with: ORA-12154: TNS:could not resolve the connect identifier specified

Try restarting the server where the oracle probe is deployed. This is required after the oracle instant client is installed. Sometimes this is overlooked.