DBConnect 3.x not working with rising columns the way 2.x did...

[timm747747]

I have the following sql statement that is working with other database inputs that were created with dbconnect v2.x. But 3.x fails with an error. This is the first input I've tried to create using the new 3.x version and I'm not having luck with any new ones I'm trying to create. I know timestamp isn't the ideal field, but it is all I have to work with. I've tried extended_timestamp as well as just timestamp and I get an error and cannot get past this. In v2.x I've created over 20 inputs without any problem whatsoever. With 3.x I can't get any created. Any help would be greatly appreciated.

SELECT * FROM "SYS"."DBA_AUDIT_TRAIL"
WHERE TIMESTAMP > ?
ORDER BY TIMESTAMP ASC

java.sql.SQLDataException: ORA-01861: literal does not match format string
No results found.

[timm747747]

Turns out if you have the field EXTENDED_TIMESTAMP in your columns you will hit bug DBX-3610. You need to remove that field and specify each column name manually instead of using a "*".

[resmungo]

This solved a standing issue for me. Thanks!

[somesoni2]

You get this error when you try to setup from DB COnnection UI (Operations dashboard) OR from conf files? Try from UI and also try to provide some field names instead of *.

[timm747747]

I'm adding the input via the UI. I've done this a bunch of other times in the v2.x software and never had a problem.

I tried this just now per your advice

SELECT "ACTION" FROM "SYS"."DBA_AUDIT_TRAIL"
WHERE TIMESTAMP > ?
ORDER BY TIMESTAMP ASC

and now I get the error:

java.sql.SQLException: Missing IN or OUT parameter at index:: 1
No results found.