Hello John,
there shouldn't be any issues with MySQL 8.4.4-1.
I've seen a small issue with Mariadb (which is not MySQL) where a newer release failed to create a view (SCI_SME_QUARTER).
Now this view is absolutely irrelevant for normal operation, it just shows how many jobs were processed per quarter.
Hence if there is an issue with the view in the first place, that can be easily fixed after the upgrade.
Naturally it'll make sense to test the upgrade. You'll need a spare machine for that.
A minimal VM will do and it can be thrown away after the test.
I'd suggest the following procedure:
1. Migrate the data to the test machine with MySQL 8.4.4-1
2. Copy the schedulix installation from the production machine to the test machine.
If the OS is compatible and the directory layout is the same, that should work.
But don't forget to create a user (schedulix) as the software owner
3. Adjust the server.conf file; it should point to the new database.
Also check the java.conf file. The JDBCJAR variable should point to the correct JDBC driver
4. Now execute a
sdmsctl test
This does two things. It tests if it understands the server.conf file and it tests if it can connect to the specified database.
It will issue an error message (might be somewhat obscure) if it fails.
5. Now start the server.
Since the test machine is unknown in your network, no jobserver will try to connect.
This is also true for jobservers that run locally, since you didn't start them yet (and if, shut them down first).
Anyway, if the server starts up without issues, the test can be considered successful.
Since this was all done on a separate machine, your production system is not affected.
If there are issues, most of them won't be related to the new MySQL release.
Knowing them before you start the real upgrade will most certainly help to smooth the process.
It goes without saying that if you find compatibility issues, you should report them.
We will fix the issue ASAP (== within a few days, maybe even on the same day).
Best regards,
Ronald