can you try just using “database=ORACLE” instead of “dbDriver=oracle.jdbc.driver.OracleDriver” in the connection cfg file? This will make the Designer use its built-in Oracle JDBC driver. Overall, the configuration of the connection could look something like the attached screenshot. This is an example of the connection file content:
I am not using a custom Oracle JDBC driver. After removing the dbDriver property and replacing it with “database=ORACLE”, the error in the Problems window disappears. Thanks for pointing that out!
Out of curiosity, though, shouldn’t I be able use the “dbDriver” property instead of the “database” property? The clover engine understands it since I can run the graph – only the Designer reports that error.
I’m not sure why the dbDriver property doesn’t work for you - the driver should be on classpath of Designer. I just quickly tried it, and it work in my setup. Luckily using database property works for you.