Details
-
Fix
-
Status: Released (View Workflow)
-
Major
-
Resolution: Fixed
-
None
-
None
Description
Current Situation
- The SQL script /db/db2/scheduler_instances_insert.sql includes a syntax error that causes that the processing to be aborted.
- This SQL script doesn't affect the JobScheduler.
It is only used by JID. - Consequently the JobScheduler cannot be started automatically by the installer at the end of the setup.
You have to start the JobScheduler manually.
Desired Behavior
/db/db2/scheduler_instances_insert.sql should work.
Workaround
Edit the /db/db2/scheduler_instances_insert.sql in line 3. Delete the closing round bracket after "HOSTNAME"='...' and put it after "TCP_PORT"='...'
CREATE PROCEDURE TMP() LANGUAGE SQL BEGIN IF EXISTS (SELECT * FROM SCHEDULER_INSTANCES WHERE "SCHEDULER_ID"='scheduler.1.10' AND "HOSTNAME"='OH' AND "TCP_PORT"='4410') THEN UPDATE SCHEDULER_INSTANCES SET "JETTY_HTTP_PORT"=40410,"JETTY_HTTPS_PORT"=48410,"RELEASE_NUMBER"='1.10.4' WHERE "SCHEDULER_ID"='scheduler.1.10' AND "HOSTNAME"='OH' AND "TCP_PORT"='4410'; ELSE INSERT INTO SCHEDULER_INSTANCES ("SCHEDULER_ID","HOSTNAME","TCP_PORT","JETTY_HTTP_PORT","JETTY_HTTPS_PORT","RELEASE_NUMBER") VALUES ('scheduler.1.10','OH',4410,40410,48410,'1.10.4'); END IF; END @ CALL TMP @ DROP PROCEDURE TMP @ COMMIT
Then call .\install\scheduler_install_tables.cmd from the command prompt
> .\install\scheduler_install_tables.cmd scheduler_instances_insert.sql
