[Bug] The version upgrade of [Module Name] caused the workflow to not be offline normally

[lctlover]

Search before asking

• [X] I had searched in the issues and found no similar issues.

What happened

1.3.5升级到2.0.6版本 其中包含有计划任务的工作流可以正常上线，但无法正常下线，会报错。 删除该工作流的计划任务，可以正常下线上线。

What you expected to happen

none

How to reproduce

升级中包含计划任务的工作流，即可重现错误。

Anything else

No response

Version

2.0.6

Are you willing to submit PR?

• [X] Yes I am willing to submit a PR!

Code of Conduct

• [X] I agree to follow this project's Code of Conduct

[github-actions[bot]]

Search before asking

• [X] I had searched in the issues and found no similar issues.

What happened

1.3.5 upgrade to 2.0.6 version The workflow that contains scheduled tasks can go online normally, but cannot go offline normally, and an error will be reported. Delete the scheduled tasks of the workflow, and you can go online and offline normally.

What you expected to happen

none

How to reproduce

The error can be reproduced by upgrading the workflow to include scheduled tasks.

Anything else

No response

Version

2.0.6

Are you willing to submit PR?

• [X] Yes I am willing to submit a PR!

Code of Conduct

• [X] I agree to follow this project's Code of Conduct

[github-actions[bot]]

Thank you for your feedback, we have received your issue, Please wait patiently for a reply.

• In order for us to understand your request as soon as possible, please provide detailed information、version or pictures.
• If you haven't received a reply for a long time, you can join our slack and send your question to channel #troubleshooting

[brave-lee]

@lctlover Has PR been submitted for this issue ?

[lctlover]

I have solved this problem. There are three tables missing

three tables from 2.0.6 dolphinscheduler_mysql.sql, and not drop sql,it will fix this problem. .

CREATE TABLE QRTZ_BLOB_TRIGGERS ( SCHED_NAME varchar(120) NOT NULL, TRIGGER_NAME varchar(200) NOT NULL, TRIGGER_GROUP varchar(200) NOT NULL, BLOB_DATA blob, PRIMARY KEY (SCHED_NAME,TRIGGER_NAME,TRIGGER_GROUP), KEY SCHED_NAME (SCHED_NAME,TRIGGER_NAME,TRIGGER_GROUP), CONSTRAINT QRTZ_BLOB_TRIGGERS_ibfk_1 FOREIGN KEY (SCHED_NAME, TRIGGER_NAME, TRIGGER_GROUP) REFERENCES QRTZ_TRIGGERS (SCHED_NAME, TRIGGER_NAME, TRIGGER_GROUP) ) ENGINE=InnoDB DEFAULT CHARSET=utf8;

CREATE TABLE QRTZ_JOB_DETAILS ( SCHED_NAME varchar(120) NOT NULL, JOB_NAME varchar(200) NOT NULL, JOB_GROUP varchar(200) NOT NULL, DESCRIPTION varchar(250) DEFAULT NULL, JOB_CLASS_NAME varchar(250) NOT NULL, IS_DURABLE varchar(1) NOT NULL, IS_NONCONCURRENT varchar(1) NOT NULL, IS_UPDATE_DATA varchar(1) NOT NULL, REQUESTS_RECOVERY varchar(1) NOT NULL, JOB_DATA blob, PRIMARY KEY (SCHED_NAME,JOB_NAME,JOB_GROUP), KEY IDX_QRTZ_J_REQ_RECOVERY (SCHED_NAME,REQUESTS_RECOVERY), KEY IDX_QRTZ_J_GRP (SCHED_NAME,JOB_GROUP) ) ENGINE=InnoDB DEFAULT CHARSET=utf8;

CREATE TABLE QRTZ_CRON_TRIGGERS ( SCHED_NAME varchar(120) NOT NULL, TRIGGER_NAME varchar(200) NOT NULL, TRIGGER_GROUP varchar(200) NOT NULL, CRON_EXPRESSION varchar(120) NOT NULL, TIME_ZONE_ID varchar(80) DEFAULT NULL, PRIMARY KEY (SCHED_NAME,TRIGGER_NAME,TRIGGER_GROUP), CONSTRAINT QRTZ_CRON_TRIGGERS_ibfk_1 FOREIGN KEY (SCHED_NAME, TRIGGER_NAME, TRIGGER_GROUP) REFERENCES QRTZ_TRIGGERS (SCHED_NAME, TRIGGER_NAME, TRIGGER_GROUP) ) ENGINE=InnoDB DEFAULT CHARSET=utf8;