TNSping check
Job details
Name: |
TNSping check |
Platform: |
Oracle |
Category: |
Availability |
Description: |
Checks TNSping connectivity on listed targets. Task requires ‘java’ support. Supports Linux/Unix and Windows, will react with an alarm if host is unreachable. |
Long description: |
Task checks TNSping connectivity on listed targets. Task requires ‘java’ support. Supports Linux/Unix and Windows and will react with an alarm if host is unreachable. |
Version: |
2.7 |
Default schedule: |
10 5,17 * * |
Requires engine install: |
Yes |
Compatibility tag: |
.[type=‘instance’ & databasetype=‘oracle’]/.[hasengine=‘YES’ & eleven_and_above = ‘1′ & enable_java = ‘1′] |
Parameters
Name |
Default value |
Description |
Delete statistics older than (days) |
365 |
|
TNSNAMES |
|
TNSNAMES you want to ping. Examples: ORCL10G, SOMEOTHER.DOMAIN.COM |
Job Summary
- Purpose: The purpose of this job is to monitor TNSping connectivity for Oracle database instances to ensure network accessibility.
- Why: This job is vital for maintaining the availability and reliability of database connectivity across networked systems. It supports proactive measures against potential connectivity outages, efficiently managing database operations in Linux/Unix and Windows environments.
- Manual checking: You can manually check TNS connectivity using the following SQL commands:
SELECT * FROM dbw_tnsping_history_#instance~id# ORDER BY execution_counter DESC;
Job Details
- Name: TNSping check
- Description: Monitors TNSping connectivity on listed targets, essential for environments with Oracle database instances. It activates alarms if a target is unreachable.
- Supported Platforms: Linux/Unix and Windows
- Java Required: Yes, the task requires Java support.
- Company: dbwatch.com
- Version: 2.7
- Default Schedule: Twice daily at 05:10 and 17:10.
Dependencies and Implementation
- The monitoring system utilizes internal database procedures and Java code to execute and check TNS ping commands. Dependencies include:
- Self-dependency for checks
- Tables and Java sources for running commands
- Specific procedures to maintain the ping check status
Database Modifications
- Tables Created:
- dbw_tnsping_history_#instance~id#
- Procedures and Java Source:
- Java source named DBW_TNS_#instance~id#
- These components interact to execute TNSping checks directly via the Oracle database environment, logging results, and handling errors adaptively based on the configured command responses.
Reporting and Alerts
- TNSping Status Report:
- Reports the listener’s status with execution history showing response times and command statuses.
- Alerts:
- Configured to alert the administrators when a host becomes unreachable or when the task encounters an issue, ensuring that potential issues are addressed promptly.
Conclusion
This dbWatch job intricately uses scheduled checks for network connectivity related to Oracle databases, employing various database modifications and procedural calls to automate the monitoring and reporting process efficiently. The system ensures that administrators receive timely notifications about connectivity status, significantly aiding in proactive network and database maintenance.