Since upgrading to PRTG version 8 I have a sensor that is a bat file that does a tnsping to an oralce database that now fails with the following message

Response not wellformed: " C:\Windows\system32>tnsping raceall.ult-db4 TNS Ping Utility for 32-bit Windows: Version 10.2.0.1.0 - Production on 11-NOV-2010 07:34:50 Copyright (c) 1997, 2005, Oracle. All rights reserved. Used parameter files: c:\oracle\ora10\network\admin\sqlnet.ora Used TNSNAMES adapter to resolve the alias Attempting to contact (DESCRIPTION = (ADDRESS_LIST = (ADDRESS = (PROTOCOL = TCP)(HOST = 10.16.1.21)(PORT = 1721))) (CONNECT_DATA = (SERVER = DEDICATED) (SID = raceall))) OK (20 msec) "

The bat file worked fine on the previous version. As can be seen the tnsping actually completes OK. I have made no changes and I am at loss as to why this sensor test now fails.


Article Comments

Dear John,

the reason is that PRTG 8 is more strict (and in fact more correct) with the Responses of Exe/Script Sensors. No line breaks or any “:” are allowed. The response has to have the format of Value: Message. The message should not be more than a few words.

Best Regards.


Nov, 2010 - Permalink

OK so how can I measure the response time from a tnsping?


Nov, 2010 - Permalink

Not strictly an answer - but a suggestion. I monitor our Oracle db by running a query against it using "SELECT 1 FROM DUAL". As the query has to be routed over TNS it serves the double purpose of testing that the database is accessible and that it is running without any dependency on a particular schema. It's been a reliable test for us for some time and perhaps simpler than using TNSPING in a batch.

HTH


Nov, 2010 - Permalink

@john, you would have to try parsing the output in your script (most likely a VBscript would then be the better tool), so that all the "unnecessary" stuff is suppressed


Nov, 2010 - Permalink