Pentaho

Hi

We have recently found an issue where having installed a repository into PDI-CE 9.4 with a MySQL 9 back End Repository Database that every time we save an existing job - it wipes it completely and PDI tells you that you need to contact an administrator.

Obviously that won't help - as we are the administrators!

Downgrading MySQL to 8.0.39 works fine but with MySQL 9, PDI-CE wipes the job completely.

When you re-open it, it's just blank. Fortunately with backups we can restore but it has completely messed up and Job Development with the latest MySQL Server version.

I've tried to capture logs but seemingly nothing is being output for this error.

It's quite a critical error but not sure what support we will get for CE. We also use Enterprise Edition if that helps us get noticed..... but I'm quite worried about the development environment on CE given that it seems completely broken when using MySQL 9 now.

Transformations save fine - just Jobs get wiped. Reproduced on multiple machines now.

.......help =-)

Hello,

It sounds like you're encountering a significant issue with PDI-CE 9.4 and MySQL 9. Here are a few steps and considerations that might help resolve this problem:

Potential Solutions
Compatibility Check:
Ensure that PDI-CE 9.4 is officially compatible with MySQL 9. Sometimes, newer versions of databases introduce changes that are not yet supported by the application. hpinstantink
JDBC Driver:
Verify that you are using the correct JDBC driver for MySQL 9. An incompatible driver might cause issues with saving jobs.
Database Configuration:
Check your MySQL 9 configuration settings. Ensure that the database is configured to handle the operations PDI-CE performs. Look for any settings related to transaction handling, storage engines, or character sets that might differ from MySQL 8.
Logs and Debugging:
Increase the logging level in PDI-CE to capture more detailed logs. This might help identify the root cause of the issue. You can adjust the logging level in the log4j.properties file.
Community and Support:
Engage with the Pentaho community forums. Other users might have encountered similar issues and could offer solutions or workarounds.
Enterprise Edition:
Since you also use the Enterprise Edition, consider reaching out to Pentaho support. They might provide more direct assistance and potentially a patch or workaround for this issue.
Best Practices
Backups: Continue to maintain regular backups of your jobs and transformations to prevent data loss.
Testing Environment: Use a separate testing environment to validate changes and updates before applying them to your production environment.

Hope this will help you.
Best regards,
Florence G.

------------------------------
Florence Gayhart
XYZ
------------------------------

Hello Bill:

We had the same problem, and in our case, we found that it was due a problem with security rules in our network sistem operation, microsoft firewall, that detected the job extension (.kjb) as a bad file.

Our system people had to create and exception in secutities rules to avoid the problem.

I hope this can help you.