Hi Felipe,
Data Engine Maintenance process debug:
Set the following options in data_engine.cfg via Raw Configure.
loglevel = 6
table_maintenance_loglevel = 6
set the "logsize" key to 200000 so you can also watch/search the log.
On the day before maintenance is scheduled to run, execute this SQL query on the UIM database:
TRUNCATE TABLE TBNLOGGING;
After the scheduled maintenance examine data_engine logs, and query output:
SELECT * FROM TBNLOGGING ORDER BY EVENT DESC;
The TBNLOGGING table will log the actual results of the stored procedures which are used during maintenance at loglevel 6. This will reveal exactly what is going on under the hood when maintenance runs, so we will be able to see if there are timeouts, stored procedures failing, etc.
tbnlogging table should have an entry for spn_de_DataMaint indicating that the data_engine maintenance has completed.To check the table results/activity, you can execute this query but note that table maintenance may take some time to finish and you'll see rows being added in the query output as the maintenance run continues when you run:
select * FROM tbnLogging where Event like '%spn_de_DataMaint%' order by id DESCBelow is an
example from the tbnlogging table during data_engine
partitioning activity:
> spn_de_PartitionAdmin__CreateIndexes(DN_QOS_DATA_0007 DN_QOS_DATA_0007 DN psnDN_QOS_DATA_0007)
- create partition scheme psnDN_QOS_DATA_0007 as partition pfnDN_QOS_DATA_0007 all to ([primary])
- create partition function pfnDN_QOS_DATA_0007(datetime) as range right for values ('20160306','20160307','20160308','20160309','20160310','20160311','20160312','20160313','20160314','20160315','20160316','20160317','20160318','20160319','20160320','20160321','20160322','20160323','20160324','20160325','20160326','20160327','20160328','20160329','20160330','20160331','20160401','20160402','20160403','20160404','20160405','20160406','20160407','20160408','20160409','20160410','20160411','20160412','20160413','20160414','20160415','20160416','20160417','20160418','20160419','20160420')
- Final RetentionTime = 30 Extra partitions = 15
- tbn_de_DataMaintConfig RetentionTime = 30 Extra partitions = 15
> spn_de_PartitionAdmin__PartitionTable(DN_QOS_DATA_0007 DN)
> spn_de_DataMaint_DeleteOldData(DN, 7, Apr 5 2016 12:00AM)
< spn_de_DataMaint_DeleteOldData(HN, 7, Apr 5 2016 12:00AM) ---> OK
< spn_de_PartitionAdmin__ShiftTable(HN_QOS_DATA_0007,HN,2016-04-05 00:00:00) deleted null rows ---> OK
***What you will see in the tbnlogging table is an entry like this: "spn_de_DataMaint <" and "spn_de_DataMaint >".
The "<" and "> indicate the start and end of maintenance. It may have an entry for each qos id, and the ids will be sorted in ascending order, so when the last one completes, it is done.
Note that there is no 'final' log message or entry.
Steve
------------------------------
[Designation]
[City]
------------------------------
Original Message:
Sent: 10-17-2019 03:19 PM
From: Felipe Ribeiro Soares
Subject: data_engine maintanance execution time
Hi guys,
It is possible to check how long the maintenance performed by the data_engine probe lasts?
Our disk goes into 100% utilization from 03:00 am, which is the beginning of the maintenance window, so we are having performance problems in UMP and REST API.
Thanks.