I have the latest build of PB on windows 10. I'm using MySQL db and have the aggravating issue of not being able to generate or use the system catalog tables. I've tried DBA, DBO, Admin, Sys, and blank in the table owner field on the DB profile with no success. I can access my tables and connect easily - just not the PB tables.
This question has probably been asked 100 times but I can't find it anywhere in the history.
J
Hi James;
I worked through the MySQL stuff last night on my Laptop by installing and configuring MySQL 8.0.13 from scratch. Here is what I found and how to make it work with PB2017R3 and PS2017R3 ...
1) The MySQL Installer only allows you to install one ODBC client type - either 32 or 64 bit. It shows you both but, when you pick one - you cannot pick the other. So make sure that you download the alternate ODBC bitness driver MSI as you will need to run this manually.
2) The ODBC drivers and some other MySQL components (ie: WorkBench) may not install and give a C++ 2010 Redistribution files missing message. The actual problem could be a bad C++ 2017 Redistribution installation that corrupted the 2010 registry entries. To correct this, perform a "repair" on the "C++ 2017 Redistribution" package. Make sure that you repair both the 32bit and 64bit packages!
3) Using the 32bit ODBC Administrator, create a MySQL System DSN for your PB IDE connection.
For example:
4) Using the 64bit ODBC Administrator, create a MySQL System DSN for your PowerServer connection.
5) Create a PB IDE DB Profile to connect to MySQL DB using the 32bit DSN. To make sure that the PBCAT tables are created ... make sure that you use the "Schema" name as the DB Owner - as follows:
6) Connect to your MySQL database. You should not get any errors. Then use PB IDE Painter to verify that the PBCat tables were indeed created.
7) You can even use MySQL's "Work Bench" product (DB Console) to re-verify ...
8) In PowerServer, you can try and connect to the newer MySQL DB releases - but the current native driver only supports the older 5.x MySQL releases. If you create a Data Source in AEM and try & connect ... it will fail.
9) Instead, create a 64 bit ODBC System DSN Using the 64 bit MySQL driver
10) Now create an ODBC Data Source connection to MySQL in PowerServer, as follows:
From this point on-wards .. both the PB IDE, its Apps and PowerServer are working well with the latest MySQL (for me).
HTH
Regards ... Chris
Hi Peter;
Yes, I found that reconnecting to the MySQL DB a 2nd time also came up with the same message that the PBCATxxx tables were not there or useable!
Here is what I did to fix this problem (not a PB issue .. its MySQL), as follows:
MySQLWorkBench: use RHMB on "root" under Table Privileges and select "Create Schema" from pop-up menu!
Part 2: Create a new Schema called "root" within your new DB.
My PBCATxxx Table access issue then went away and the PB IDE was able to connect and use the PBCATxxx tables without error.
HTH
Regards ... Chris
