Explanation: This can occur when Foxhound connects to a High Availability secondary (mirror) database and/or a read-only scale out (copy) database, but not the updatable primary or root node database.

In this case Foxhound cannot create the three properties procedures (rroad_engine_properties, rroad_database_properties and rroad_connection_properties) in the target database because it is read-only.

25 2016-06-19 15:37:21.784 Full Build 4679a 1000010086 701.a3(701eh2) CREATE PROCEDURE rroad_engine_properties failed. SQLSTATE = WO005, ERRORMSG() = Server 'p001': [SAP][ODBC Driver][SQL Anywhere] Modifications not permitted for read-only database [120-HA_Demo_16_Copy4] 26 2016-06-19 15:37:21.795 Full Build 4679a 1000010086 702.a3(702eh2) CREATE PROCEDURE rroad_database_properties failed. SQLSTATE = WO005, ERRORMSG() = Server 'p001': [SAP][ODBC Driver][SQL Anywhere] Modifications not permitted for read-only database [120-HA_Demo_16_Copy4] 27 2016-06-19 15:37:21.815 Full Build 4679a 1000010086 700.a3(700eh2) CREATE PROCEDURE rroad_connection_properties failed. SQLSTATE = WO005, ERRORMSG() = Server 'p001': [SAP][ODBC Driver][SQL Anywhere] Modifications not permitted for read-only database [120-HA_Demo_16_Copy4] 28 2016-06-19 15:38:07.056 Full Build 4679a 1000010161 701.a3(701eh2) CREATE PROCEDURE rroad_engine_properties failed. SQLSTATE = WO005, ERRORMSG() = Server 'p002': [SAP][ODBC Driver][SQL Anywhere] Modifications not permitted for read-only database [122-HA_Demo_16_Secondary] 29 2016-06-19 15:38:07.066 Full Build 4679a 1000010161 702.a3(702eh2) CREATE PROCEDURE rroad_database_properties failed. SQLSTATE = WO005, ERRORMSG() = Server 'p002': [SAP][ODBC Driver][SQL Anywhere] Modifications not permitted for read-only database [122-HA_Demo_16_Secondary] 30 2016-06-19 15:38:07.079 Full Build 4679a 1000010161 700.a3(700eh2) CREATE PROCEDURE rroad_connection_properties failed. SQLSTATE = WO005, ERRORMSG() = Server 'p002': [SAP][ODBC Driver][SQL Anywhere ]Modifications not permitted for read-only database [122-HA_Demo_16_Secondary]

One solution is to

• start another Foxhound sampling session connected to the primary or root node database, then

• wait a moment for the three properties procedures to be created on the primary or root node database and then sent to the secondary (mirror) database and/or read-only scale out (copy) database, then

• stop and start sampling on the secondary (mirror) database and/or read-only scale out (copy) database, to force Foxhound to begin using the three properties procedures.

See also...
How do I see Foxhound diagnostics, errors and exceptions?