ORA-1873 accessing the SQL_RESPONSE_COLLECT metric

So you upgraded your databases to 10.2.0.4 and also recreated hc...dat file not
to hang Grid Control agent, enabled health check, started agent -
everything to fix consequences of bug https://metalink.oracle.com/metalink/plsql/showdoc?db=Bug&id=5872000 (see post http://dbadailytelegraph.blogspot.com/2008/08/killing-health-check.html)
and executed tail -f emagent.trc to see if some errors coming - 1, 2, 3 minutes,
everything looks to be alright.

Don't hurry up! :(

The errors are coming! And they are from anonymous PL/SQL block that runs
to measure "SQL Response Time (%)" metric and it scheduled to gather
information every 5 minutes by default:

ORA-06512: at line 7
2008-09-15 22:12:17,815 Thread-4064263072 ERROR engine: [oracle_database,test,sql_response_collect] : nmeegd_GetMetricData failed : ORA-01873: the leading precision of the interval is too small
ORA-06512: at "DBSNMP.MGMT_RESPONSE", line 1013
ORA-06512: at "DBSNMP.MGMT_RESPONSE", line 923
ORA-06512: at line 7

2008-09-15 22:12:17,816 Thread-4064263072 WARN collector: Error exit. Error message: ORA-01873: the leading precision of the interval is too small
ORA-06512: at "DBSNMP.MGMT_RESPONSE", line 1013
ORA-06512: at "DBSNMP.MGMT_RESPONSE", line 923
ORA-06512: at line 7


The search on Metalink leads to https://metalink.oracle.com/metalink/plsql/ml2_documents.showDocument?p_database_id=NOT&p_id=6737060.8
and affected (confirmed) versions of databases are 10.2.0.3 and 10.2.0.4
and it will be fixed in 11.1.0.7 and 11.2

Disabling the metric will help to avoid errors but it can be important metric at some stage.


Have a good day!