Job Scheduler

Create Table Command for Table SCHEDULER_CLUSTERS contains unsupported DB2 data types

Details

  • Type: Bug Bug
  • Status: Resolved Resolved
  • Priority: Minor Minor
  • Resolution: Fixed
  • Affects Version/s: 1.3.1
  • Fix Version/s: 1.3.2
  • Component/s: Job Scheduler Binaries
  • Description:
    Hide

    15:02:00.805 scheduler 0 1544.5B4 204.254MB ....[xc.insert 3, "executeQuery"]
    15:02:00.805 scheduler 0 1544.5B4 204.254MB ...{scheduler} [debug3] (Database) select count from SCHEDULER_CLUSTERS where 1=0 (sos::scheduler::database::Database::create_table_when_needed)
    15:02:00.805 scheduler 0 1544.5B4 204.254MB ...{scheduler} [debug3] (Database) [com.ibm.db2.jcc.a.SqlException] ["DB2ADMIN.SCHEDULER_CLUSTERS" is an undefined name.] [executeQuery] []
    15:02:00.805 scheduler 0 1544.5B4 204.254MB ...{scheduler} [WARN] (Database) [com.ibm.db2.jcc.a.SqlException] ["DB2ADMIN.SCHEDULER_CLUSTERS" is an undefined name.] [executeQuery] []
    15:02:00.805 scheduler 0 1544.5B4 204.254MB ...{scheduler} [info] (Database) SCHEDULER-909 Creating database table SCHEDULER_CLUSTERS
    15:02:00.805 scheduler 0 1544.5B4 204.254MB ...{scheduler} sos::scheduler::database::Transaction::execute COMMIT (sos::scheduler::database::Database::create_table_when_needed)
    15:02:00.805 scheduler 0 1544.5B4 204.254MB ...sos::Sos_database_session::execute_direct_single COMMIT
    15:02:00.805 scheduler 0 1544.5B4 204.254MB ...{scheduler} sos::scheduler::database::Transaction::execute CREATE TABLE SCHEDULER_CLUSTERS (`member_id` varchar(100) not null, `scheduler_id` varchar(100) not null, `precedence` integer, `last_heart_beat` integer, `next_heart_beat` integer, `active` boolean, `exclusive` boolean, `dead` boolean, `command` varchar(250), `http_url` varchar(100), `deactivating_member_id` varchar(100), `xml` clob, primary key( `member_id` )) (sos::scheduler::database::Database::create_table_when_needed)
    15:02:00.805 scheduler 0 1544.5B4 204.254MB ...jdbc: executeUpdate CREATE TABLE SCHEDULER_CLUSTERS ("MEMBER_ID" varchar(100) not null, "SCHEDULER_ID" varchar(100) not null, "PRECEDENCE" integer, "LAST_HEART_BEAT" integer, "NEXT_HEART_BEAT" integer, "ACTIVE" boolean, "EXCLUSIVE" boolean, "DEAD" boolean, "COMMAND" varchar(250), "HTTP_URL" varchar(100), "DEACTIVATING_MEMBER_ID" varchar(100), "XML" CLOB, primary key( "MEMBER_ID" ))Vm::static_vm=00D8A0E8 _debug=0
    15:02:00.836 scheduler 31 1544.5B4 204.254MB ...[xc.insert 1, "com.ibm.db2.jcc.a.SqlException"]
    15:02:00.836 scheduler 0 1544.5B4 204.254MB ...[xc.insert 2, "The BOOLEAN data type is currently only supported internally."]
    15:02:00.836 scheduler 0 1544.5B4 204.254MB ...[xc.insert 3, "executeUpdate"]
    15:02:00.852 scheduler 16 1544.5B4 204.254MB ...{scheduler} [none] (Database) CREATE TABLE SCHEDULER_CLUSTERS ("MEMBER_ID" varchar(100) not null, "SCHEDULER_ID" varchar(100) not null, "PRECEDENCE" integer, "LAST_HEART_BEAT" integer, "NEXT_HEART_BEAT" integer, "ACTIVE" boolean, "EXCLUSIVE" boolean, "DEAD" boolean, "COMMAND" varchar(250), "HTTP_URL" varchar(100), "DEACTIVATING_MEMBER_ID" varchar(100), "XML" CLOB, primary key( "MEMBER_ID" )) (sos::scheduler::database::Database::create_table_when_needed)
    15:02:00.852 scheduler 0 1544.5B4 204.254MB ...{scheduler} [none] (Database) [com.ibm.db2.jcc.a.SqlException] [The BOOLEAN data type is currently only supported internally.] [executeUpdate] []
    15:02:00.852 scheduler 0 1544.5B4 204.254MB ...[xc.append "sos::scheduler::database::Database::create_table_when_needed"]
    15:02:00.852 scheduler 0 1544.5B4 204.254MB ...[ERROR SCHEDULER-363 Error when creating SQL table SCHEDULER_CLUSTERS: [com.ibm.db2.jcc.a.SqlException] [The BOOLEAN data type is currently only supported internally.] [executeUpdate] [] / sos::scheduler::database::Database::create_table_when_needed]

    Show
    15:02:00.805 scheduler 0 1544.5B4 204.254MB ....[xc.insert 3, "executeQuery"] 15:02:00.805 scheduler 0 1544.5B4 204.254MB ...{scheduler} [debug3] (Database) select count from SCHEDULER_CLUSTERS where 1=0 (sos::scheduler::database::Database::create_table_when_needed) 15:02:00.805 scheduler 0 1544.5B4 204.254MB ...{scheduler} [debug3] (Database) [com.ibm.db2.jcc.a.SqlException] ["DB2ADMIN.SCHEDULER_CLUSTERS" is an undefined name.] [executeQuery] [] 15:02:00.805 scheduler 0 1544.5B4 204.254MB ...{scheduler} [WARN] (Database) [com.ibm.db2.jcc.a.SqlException] ["DB2ADMIN.SCHEDULER_CLUSTERS" is an undefined name.] [executeQuery] [] 15:02:00.805 scheduler 0 1544.5B4 204.254MB ...{scheduler} [info] (Database) SCHEDULER-909 Creating database table SCHEDULER_CLUSTERS 15:02:00.805 scheduler 0 1544.5B4 204.254MB ...{scheduler} sos::scheduler::database::Transaction::execute COMMIT (sos::scheduler::database::Database::create_table_when_needed) 15:02:00.805 scheduler 0 1544.5B4 204.254MB ...sos::Sos_database_session::execute_direct_single COMMIT 15:02:00.805 scheduler 0 1544.5B4 204.254MB ...{scheduler} sos::scheduler::database::Transaction::execute CREATE TABLE SCHEDULER_CLUSTERS (`member_id` varchar(100) not null, `scheduler_id` varchar(100) not null, `precedence` integer, `last_heart_beat` integer, `next_heart_beat` integer, `active` boolean, `exclusive` boolean, `dead` boolean, `command` varchar(250), `http_url` varchar(100), `deactivating_member_id` varchar(100), `xml` clob, primary key( `member_id` )) (sos::scheduler::database::Database::create_table_when_needed) 15:02:00.805 scheduler 0 1544.5B4 204.254MB ...jdbc: executeUpdate CREATE TABLE SCHEDULER_CLUSTERS ("MEMBER_ID" varchar(100) not null, "SCHEDULER_ID" varchar(100) not null, "PRECEDENCE" integer, "LAST_HEART_BEAT" integer, "NEXT_HEART_BEAT" integer, "ACTIVE" boolean, "EXCLUSIVE" boolean, "DEAD" boolean, "COMMAND" varchar(250), "HTTP_URL" varchar(100), "DEACTIVATING_MEMBER_ID" varchar(100), "XML" CLOB, primary key( "MEMBER_ID" ))Vm::static_vm=00D8A0E8 _debug=0 15:02:00.836 scheduler 31 1544.5B4 204.254MB ...[xc.insert 1, "com.ibm.db2.jcc.a.SqlException"] 15:02:00.836 scheduler 0 1544.5B4 204.254MB ...[xc.insert 2, "The BOOLEAN data type is currently only supported internally."] 15:02:00.836 scheduler 0 1544.5B4 204.254MB ...[xc.insert 3, "executeUpdate"] 15:02:00.852 scheduler 16 1544.5B4 204.254MB ...{scheduler} [none] (Database) CREATE TABLE SCHEDULER_CLUSTERS ("MEMBER_ID" varchar(100) not null, "SCHEDULER_ID" varchar(100) not null, "PRECEDENCE" integer, "LAST_HEART_BEAT" integer, "NEXT_HEART_BEAT" integer, "ACTIVE" boolean, "EXCLUSIVE" boolean, "DEAD" boolean, "COMMAND" varchar(250), "HTTP_URL" varchar(100), "DEACTIVATING_MEMBER_ID" varchar(100), "XML" CLOB, primary key( "MEMBER_ID" )) (sos::scheduler::database::Database::create_table_when_needed) 15:02:00.852 scheduler 0 1544.5B4 204.254MB ...{scheduler} [none] (Database) [com.ibm.db2.jcc.a.SqlException] [The BOOLEAN data type is currently only supported internally.] [executeUpdate] [] 15:02:00.852 scheduler 0 1544.5B4 204.254MB ...[xc.append "sos::scheduler::database::Database::create_table_when_needed"] 15:02:00.852 scheduler 0 1544.5B4 204.254MB ...[ERROR SCHEDULER-363 Error when creating SQL table SCHEDULER_CLUSTERS: [com.ibm.db2.jcc.a.SqlException] [The BOOLEAN data type is currently only supported internally.] [executeUpdate] [] / sos::scheduler::database::Database::create_table_when_needed]
  • Environment:
    DB2

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Joacim Zschimmer added a comment - 23 July 2007 13:41

Wenn DB2 dies meldet: "The BOOLEAN data type is currently only supported internally", welcher Datentyp ist denn der richtige? Bislang verwendet der Scheduler diesen Datentyp. Ich kann's leider nicht testen, weil mir die DB2-Datenbank der SOS den Zugang verweigert ("Connection refused").

Es scheint so, dass DB2 diesen Datentyp einmal kannte. Vielleicht heißt er anders? Oder wir nehmen wir bei einigen anderen Datenbanken numeric(1).

Joacim Zschimmer

Show
Joacim Zschimmer added a comment - 23 July 2007 13:41 Wenn DB2 dies meldet: "The BOOLEAN data type is currently only supported internally", welcher Datentyp ist denn der richtige? Bislang verwendet der Scheduler diesen Datentyp. Ich kann's leider nicht testen, weil mir die DB2-Datenbank der SOS den Zugang verweigert ("Connection refused"). Es scheint so, dass DB2 diesen Datentyp einmal kannte. Vielleicht heißt er anders? Oder wir nehmen wir bei einigen anderen Datenbanken numeric(1). Joacim Zschimmer
Hide
Permalink
Andreas Liebert added a comment - 24 July 2007 10:59

numeric(1) sollte verwendet werden

Show
Andreas Liebert added a comment - 24 July 2007 10:59 numeric(1) sollte verwendet werden
Hide
Permalink
Joacim Zschimmer added a comment - 01 August 2007 06:55

Weil ich keinen Zugang zu db2 habe, muss das noch geprüft werden.

Show
Joacim Zschimmer added a comment - 01 August 2007 06:55 Weil ich keinen Zugang zu db2 habe, muss das noch geprüft werden.

People

Dates

  • Created:
    17 July 2007 17:35
    Updated:
    01 August 2007 06:55
    Resolved:
    01 August 2007 06:55
Atlassian JIRA (v4.1.2#531) | Report a problem | Request a feature | Contact administrators
Powered by a free Atlassian JIRA open source license for Job Scheduler. Try JIRA - bug tracking software for your team.