There are various reasons for this error, but the one I hit was that the table name is case sensitive, and returned from Oracle by the JDBC driver in uppercase. If you specify the tablename in your connecter config in lowercase, it won’t be matched, and this error is thrown. You can validate this by setting debug logging (edit etc/kafka/connect-log4j.properties to set log4j.rootLogger=DEBUG, stdout), and observe: (I’ve truncated some of the output for legibility)

Continue Reading

OBIEE supports JDBC as a connection protocol, using the driver available on all installations of OBIEE, bijdbc.jar. This makes connecting to OBIEE from custom or third-party applications very easy. Once connected, you issue “Logical SQL” against the “tables” of the Presentation Layer. An example of logical SQL is: SELECT "Time"."T05 Per Name Year" saw_0 FROM "A - Sample Sales" To find more Logical SQL simply inspect your nqquery.log (obis-query.log in 12c), or Usage Tracking.

Continue Reading

In setting the scheduler in Publisher I discovered a useful difference in jdbc drivers. Our repository is on Oracle 11g. According to the manual oracle.jdbc.driver.OracleDriver should be used, but previous installations have used oracle.bi.jdbc.AnaJdbcDriver so I tried this too. In experimenting with both I found you get more useful feedback from the second one. Here’s the same problem reported by both drivers: · Exception [TOPLINK-4002] (Oracle TopLink - 11g Release 1 (11.

Continue Reading