We are encountering below errors on our IS logs -
Server logs - 1778 [ISS.0137.36] 2016-12-29 14:29:20 CST FATAL: Check of internal database failed: the current version 55 should be at least 57
1777 [ISS.0137.0] 2016-12-29 14:29:20 CST INFO: [SCHED] IS 9.9, scheduler version: 220.127.116.11
Error logs - java.lang.RuntimeException: java.sql.SQLSyntaxErrorException: [SoftwareAG][SQLServer JDBC Driver][SQLServer]Invalid column name ‘START_AT’.
Caused by: java.lang.RuntimeException: java.sql.SQLSyntaxErrorException: [SoftwareAG][SQLServer JDBC Driver][SQLServer]Invalid column name ‘START_AT’.
Caused by: java.sql.SQLSyntaxErrorException: [SoftwareAG][SQLServer JDBC Driver][SQLServer]Invalid column name ‘START_AT’.
Can someone please help ?
Can you please share the IS version and DB version you are having issue with.
Did you apply any fixes recently on your IS? This issue looks like you installed some fixes and forgot to perform some post-migration steps.
Use Database Component Configuration, Select “Migrate”, choose your product (Integration Server in this case) and Run the scripts.
The column START_AT was not present in version 55 it was introduced in version 57.
So, as suggested by @Prasad run migration scripts to resolve the below issue.
Syed Faraz Ahmed
please apply DC_9.9_DBS_Fix3 (or newer) before trying to migrate the database.
After transitioning to or from daylight savings time,
scheduled tasks run twice or not at all.
Integration Server runs scheduled tasks based on the time
relative to the time zone.
This caused issues when entering and exiting daylight savings
specifically tasks ran twice or not at all.
Now, Integration Server runs scheduled tasks based on coordinated
universal time (UTC).
Because Integration Server runs the tasks without regard to the
relative time zone,
the start and end of daylight savings time does not affect the
execution of scheduled tasks.
Important! If you are using an external database for the
ISInternal functional alias in Integration Server,
after installing a fix that includes PIE-36477 and before
starting Integration Server,
make sure that the latest scripts for ISInternal have been
applied to the database used by
the JDBC pool alias associated with the ISInternal functional
The issue was introduced with with IS_9.9_Core_Fix2 and occurs when the update for the database scripts has been missed (see above).
Thank You Everyone. The issue is resolved once we updated to 57 using DB configurator.