Data Loss MySQL Ignition History

Hi,

Today I discovered that when I try to access the data from some tags in July the data is missing. The configuration has been kept the same all along but all the sabed data using ignition native history mode is missing. I can access the data from August but everything since the 16 July is missing. I’m guessing there is a corruption in the database given that in MySQL there is a database named image just where the problem starts.

How can i see which data /lines are causing the problem ?

I think the problem started when i clicked retry on a Quarantined file in Store and Forward, but i’m not sure and I don’ have the quarantined file.

Go to Config - Tags - History and click on your tag history data provider and check what the settings are for Data Pruning, it may have been purged by this.

It double checked that. Data pruning is not activated and I have data from before the 16th July. It is really from july 16th tup unto August 1st that I can’t recover/see the data.

Is there any chance your database is simply full and couldn’t store that data?

Not really. I could see the data just before. It was really after that retry in Store And Forward that now I cant’ see it. It seems really weird to me.

I changed recently from month to weekd in the ways to store data. I don’t know if that store and forward changed the structure somewhere and it tinks it is by week instead of mont (or viseversa ?)

You probably want to look at both your gateway logs and your DB logs to see what is being rejected.

Ignition returns zero as values. I think it doesnt reject anything it justs returns zero given that it doesnt find the history of the data, although I’m confident it is in the database somewhere. I checked the logs but no error message is shown anywhere

You might want to have support look over your shoulder.

1 Like

Thanks. I’m guessing the next line is the one causing the issue, but I’m not sure.

SELECT @@datadir datadir,sd.path FROM information_schema.INNODB_TABLES st JOIN information_schema.innodb_datafiles sd USING(space) WHERE st.name = ‘cnc/sqlt_data_1_20200716’;

Nevermind. Thought i had some more new information but that is not the case. All the information from july is missing, so I think somewhere the change from month to week changed an ID or a key and now it is unable to see the table. Just grasping at straws here.

I however, have no idea how I can solve it…

Didn’t wait for support to look over your shoulder, huh? You really should have IA help you unscramble this.

I wanted to make sure the system is stable and we continue to function as before. I’m defnitely not going to modfiy anything but jus tryng to learn more about the situation ^^’