Database MySQL - PcVue is not archiving

6 Posts
5 Users
0 Likes
53 Views
(@c-pinasanzarcinfo-com)
Posts: 42
Trusted Member
Topic starter
 

Hi,

I'm trying to archive in MySQL database, installed in the same machine than PcVue. I have configured all by default, and I can reach the
database from PcVue, and create the tables, but PcVue is not archiving. My configuration:
- VM W10.
- PcVue 16.0.0-rc018.
- MySQL Server 8.0.32 x64-bit.
- Connector/ODBC ANSI 8.0.32 x32-bit.
- I have created a new database in MySQL, all by default, empty, without tables.
- I have configured the ODBC connector to link this database, and the user has all rights.
- In PcVue, I have configured the ODBC database, and changed the "Delimiter for identifiers" to the one for MySQL.
Then I have added the ODBC Archive Unit, LogList and Trends, all by default.

When I launch PcVue, the tables has been created, and there is no message in the Event Viewer about the database.

Maybe I have installed a wrong version of MySQL,or there are some special settings to apply...

Thanks for the support!
Claudia

 
Posted : 20/02/2023 5:06 pm
(@k-lemairearcinfo-com)
Posts: 14
Active Member
 

Hello Claudia,

I don't see anything strange about your configuration.
The quickest way to understand to issue is to activate the ODBC traces :

https://docs.oracle.com/cd/E17952_01/connector-odbc-en/connector-odbc-configuration-trace-windows.html

Stop the tracing after PcVue startup and check the log file for errors. You can also send it here.

Best regards,
Kévin

 
Posted : 20/02/2023 5:19 pm
n.kunzer
(@n-kunzerarcinfo-com)
Posts: 1236
Member Moderator
 

Hi Claudia,

If I am not mistaken, ODBC is recording some logs (Tab Tracing). Maybe you could check that first.

Nico

 
Posted : 20/02/2023 5:28 pm
(@admin_doc72)
Posts: 493
Member Admin
 

Hello,

One of our cutomer face the same problem while using a recent ODBC Driver for MySQL (8.0.32).
But while using an oldest one (8.0.15) the access to the MySQL database is ok.

This problem was sent to support service which open the SPR 72258 for this.

 
Posted : 20/02/2023 10:22 pm
AD
 AD
(@a-degrearcinfo-com)
Posts: 34
Trusted Member
 

The problem comes from the new MySQL ODBC driver which asks for a date precision of 21 characters instead of 19 and this in spite of the fact that a datetime() is expressed on 19 characters when it is requested.

We will make the necessary evolution in a next version to overcome this bug of MySQL ODBC driver.

 
Posted : 24/02/2023 5:04 pm
(@c-pinasanzarcinfo-com)
Posts: 42
Trusted Member
Topic starter
 

Hi all,

Thank you so much for your answers !!
I will try with an older version of the ODBC driver.

BR,
Claudia

 
Posted : 24/02/2023 5:38 pm