NetXMS Support Forum

Hi,

Could you help to identify why table TDATA_ROWS_1178 is growing very fast?

SQL> select count(*) from TDATA_ROWS_1178;

  COUNT(*)
----------
  18189554

Yesterday there was 10 million rows, today it is 18 millions rows.
This table grow by 300MB since yesterday and consumed all available space in tablespace.

SEGMENT_NAME                                                                      SEGMENT_TYPE       size_in_MB
--------------------------------------------------------------------------------- ------------------ ----------
SYS_C0034271                                                                      INDEX                     746
TDATA_ROWS_1178                                                                   TABLE                     624
SNMP_TRAP_LOG                                                                     TABLE                   511.1
SYS_C0034093                                                                      INDEX                     499
TDATA_ROWS_100                                                                    TABLE                     464

Best regards,
Marcin

Hello

This table hold rows for table DCI (with large result set). Check DCI settings – how often it's collected and retention time.
1178 in table name is DCI id, you can either find it in user interface by looking at ID column in last values, or query database directly:

select op.name,d.name from dc_tables d join object_properties op on op.object_id=d.node_id where d.item_id=1178

Hello,

I tried query database directly:
SQL> select op.name,d.name from dc_tables d join object_properties op on op.object_id=d.node_id where d.item_id=1178;

no rows selected

How can I check it in user interface? For which object I should look for DCI id in Data Collection Configuration or Last Values?
I don't have ID's higher than 220.

Best regards,
Marcin

Ok. I found. 1178 is node_id (object_id), not item_id.
And this helped me solving the problem (frequent fetching the list of open files) for node 1178.

Thank you,
Marcin