|
Oracle Client installation
Users should check that the Oracle Client is installed properly on the Netprobe machine. Please review the separate article: How to solve database client installation issues in SQL-Toolkit plugin
|
|
ORA-01034: ORACLE not available ORA-27101: shared memory realm does not exist
- On the Netprobe machine, please use Oracle's sqlplus command to connect the database, to check that the database is started.
- Please check that the ORACLE_HOME environment variable is set correctly in the Netprobe startup script. Certain users reported that having extra / character at the end would trigger this error.
|
|
ORA-02391: exceeded simultaneous SESSIONS_PER_USER limit
- The SQL-Toolkit plugin was unable to connect the database due to the SESSION_PER_USER limit being breached. This is an Oracle database setting, and please consult the DBA if the session limit needs to be increased.
|
|
ORA-12154: TNS:could not resolve the connect identifier specified
This error means that value inputted in the Database Name parameter cannot be resolved.
- If you are using the tnsnames.ora file to resolve the database name, check the said file if the correct database name is used.
- If you are not using the tnsnames.ora file, input the following value/format in the Database Name parameter:
(DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=<database server host/IP>)(PORT=<database server port>))(CONNECT_DATA=(SERVICE_NAME=database name/database global name))) |
e.g.
(DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=192.168.100.180)(PORT=1521))(CONNECT_DATA=(SERVICE_NAME=geneos_db))) |
|
|
ORA-12170: TNS:Connect timeout occurred
-
Please check that the host parameter in tnsnames.ora is correct. For example, the error would occur if it points to a non-existing IP address.
|
|
ORA-12514: TNS:listener does not currently know of service requested in connect descriptor
- Please check that the Oracle database and listener service are running
- Please check that the service name parameter in tnsnames.ora is correct.
|
|
ORA-12541: TNS:no listener
- Please check that the Oracle listener service is running
- Please check that the port parameter in tnsnames.ora is correct.
|
|
ORA-12545: Connect failed because target host or object does not exist
The plug-in neither cannot connect nor cannot resolve the hostname of the database server.
To troubleshoot this:
- Extract the database server's hostname being used by the SQL-Toolkit plug-in
-
- It can be extracted either via tnsnames.ora or listener.ora depending on which file is being used.
- It can be in the connection string defined in the SQL-Toolkit sampler itself.
- Execute a ping command that targets the said server's hostname from the Netprobe server.
-
- If ping is unsuccessful, report the results to the database and network/firewall administrators.
- If ping is successful, check the dataview if the error persists. If the error persists, validate the correct Oracle network file then extract the hostname being referred to.
|
|
ORA-06413: Connection not open
- This error may occur for older versions of Oracle database client on Windows, when it is called from a client installation path that contains bracket symbols. This could more commonly happen when Netprobe is installed under the 32-bit default path C:\Program Files (x86).
- Users are advised to install the 64-bit Windows Netprobe, which had been available since version GA4.2.
- Users who are still using 32-bit Netprobe versions should check the installation path and avoid the bracket symbol if appropriate.
|
|
Further Reading
Please kindly check the following guides:
|
Comments
0 comments
Please sign in to leave a comment.