Modifying counter-limits
Each item of data that is recorded is called a counter. By default, the number of counters is limited to eight REAL and four STRING. You might want to increase the number of counters and can do so by modifying a table definition in the database creation script.
To modify counter-limits:
- If your results database connection is valid, IBM® DevOps Test Integrations and APIs (Test Integrations and APIs) silently queries the counter-limits. If the limits are exceeded, invalid rows are shown in red and no rows can be edited until the extra ones are removed.
- You can increase the number of counters
by modifying a table definition in the database creation script.
The example that is shown is from the Oracle create script. (Some lines of SQL are omitted for brevity.)
The
CTR_ID_9andSTRCTR_ID_5entries show the lines that must be added to increase the number ofREALandSTRINGcounters by one.CREATE TABLE "LOGMEASUREMENT_TS"( "IDX" NUMBER(19, 0) NOT NULL, "LOGMEASUREMENT_MRV_ID" NUMBER(19, 0) NOT NULL, "EXECUTION_ID" NUMBER(19, 0), "TIME" NUMBER(20, 0) NOT NULL, ... "CTR_ID_8" NUMBER(19, 0), "CTR_VAL_8" NUMBER(20, 3), "CTR_ID_9" NUMBER(19, 0), "CTR_VAL_9" NUMBER(20, 3), ... "STRCTR_ID_4" NUMBER(19, 0), "STRCTR_VAL_4" VARCHAR2(255), "STRCTR_ID_5" NUMBER(19, 0), "STRCTR_VAL_5" VARCHAR2(255), FOREIGN KEY ("EXECUTION_ID") REFERENCES "EXECUTION"("ID") ON DELETE CASCADE, FOREIGN KEY ("LOGMEASUREMENT_MRV_ID") REFERENCES "LOGMEASUREMENT_MRV"("ID") ON DELETE CASCADE, FOREIGN KEY ("CTR_ID_1") REFERENCES "COUNTER_DETAILS"("ID") ON DELETE CASCADE, ... FOREIGN KEY ("STRCTR_ID_4") REFERENCES "COUNTER_DETAILS"("ID") ON DELETE CASCADE, FOREIGN KEY ("CTR_ID_9") REFERENCES "COUNTER_DETAILS"("ID") ON DELETE CASCADE, FOREIGN KEY ("STRCTR_ID_5") REFERENCES "COUNTER_DETAILS"("ID") ON DELETE CASCADE, ) ;Important:You can increase the table sizes even if the results database contains data. If you need help, consult your local database administrator (DBA).