Date: Fri, 29 Mar 2024 13:29:57 +0000 (UTC) Message-ID: <1473672521.12971.1711718997425@change.sos-berlin.com> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_12970_704524983.1711718997425" ------=_Part_12970_704524983.1711718997425 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
The Job Scheduler needs InnoDB tables.
For this, a CREATE TABLE statement ends with TYPE=3D InnoDB in = MySQL 4 and with ENGINE=3DInnoDB in MySQL 5.
Until MySQL 5.4 was Type=3DInnoDB as far backward compatible, b= ut since MySQL 5.5 an error is thrown.
We have therefore modified the SQL statements to ENGINE=3DInnoD= B for Job Scheduler releases > 1.3.10.1132.
You have an error in your SQL syntax. Check the manual that corres=
ponds to your MySQL server version for the right syntax to use near 'Engine=
=3DInnoDB'
In this case you must change in all SQL files (./db/mysql/*.sql) the ENGINE=3DInnoDB to TYPEInnoDB and start the ./install/schedu= ler_install_tables.(cmd|sh) script.
You have an error in your SQL syntax. Check the manual that corres=
ponds to your MySQL server version for the right syntax to use near 'Type=
=3DInnoDB'
In this case you must change in all SQL files (./db/mysql/*.sql) the TYPE=3DInnoDB to ENGINEInnoDB.
Furthermore, missing four CREATE TABLE statements.
Insert the following CREATE TABLEs to ./db/mysql/scheduler.sql:
CREATE = TABLE IF NOT EXISTS SCHEDULER_JOBS ( "SPOOLER_ID" varchar(100) CHARACTER SET latin1 NOT NULL, = =20 "CLUSTER_MEMBER_ID" varchar(100) CHARACTER SET latin1 NOT NULL, = =20 "PATH" varchar(255) CHARACTER SET latin1 NOT NULL, = =20 "STOPPED" int(1) NOT NULL DEFAULT 0, = =20 "NEXT_START_TIME" varchar(24) , = =20 PRIMARY KEY ("SPOOLER_ID","CLUSTER_MEMBER_ID","PATH") ) ENGINE=3DInnoDB;=20 =20 =20 CREATE TABLE IF NOT EXISTS SCHEDULER_JOB_CHAINS ( "SPOOLER_ID" varchar(100) CHARACTER SET latin1 NOT NULL, = =20 "CLUSTER_MEMBER_ID" varchar(100) CHARACTER SET latin1 NOT NULL, = =20 "PATH" varchar(255) CHARACTER SET latin1 NOT NULL, = =20 "STOPPED" int(1) NOT NULL DEFAULT 0, = =20 PRIMARY KEY ("SPOOLER_ID","CLUSTER_MEMBER_ID","PATH") ) ENGINE=3DInnoDB; =20 =20 CREATE TABLE IF NOT EXISTS SCHEDULER_JOB_CHAIN_NODES ( "SPOOLER_ID" varchar(100) CHARACTER SET latin1 NOT NULL,=20 "CLUSTER_MEMBER_ID" varchar(100) CHARACTER SET latin1 NOT NULL, = =20 "JOB_CHAIN" varchar(255) CHARACTER SET latin1 NOT NULL, = =20 "ORDER_STATE" varchar(100) CHARACTER SET latin1 NOT NULL, = =20 "ACTION" varchar(100) , = =20 PRIMARY KEY ("SPOOLER_ID","CLUSTER_MEMBER_ID","JOB_CHAIN","ORDER_STATE"= ) ) ENGINE=3DInnoDB; =20 =20 CREATE TABLE IF NOT EXISTS SCHEDULER_CLUSTERS ( "MEMBER_ID" varchar(100) CHARACTER SET latin1 NOT NULL, "SCHEDULER_ID" varchar(100) CHARACTER SET latin1 NOT NULL, "PRECEDENCE" int(11), "LAST_HEART_BEAT" int(11), "NEXT_HEART_BEAT" int(11), "ACTIVE" int(1), "EXCLUSIVE" int(1), "DEAD" int(1), "COMMAND" varchar(250), "HTTP_URL" varchar(100), "DEACTIVATING_MEMBER_ID" varchar(100), "XML" longtext, PRIMARY KEY ("MEMBER_ID") ) ENGINE=3DInnoDB;=20 =20
Start the ./install/scheduler_install_tables.(cmd|sh) script.