com.google.gwtorm.server.OrmException

Cannot apply SQL CREATE TABLE account_group_by_id_aud ( added_by INT DEFAULT 0 NOT NULL, removed_by INT, removed_on TIMESTAMP NULL DEFAULT NULL, group_id INT DEFAULT 0 NOT NULL, include_uuid VARCHAR(255) BINARY DEFAULT '' NOT NULL, added_on TIMESTAMP NOT NULL ,PRIMARY KEY(group_id,include_uuid,added_on) ) at com.google.gwtorm.jdbc.JdbcExecutor.execute(JdbcExecutor.java:44) at com.google.gwtorm.jdbc.JdbcSchema.createRelations(JdbcSchema.java:119) at com.google.gwtorm.jdbc.JdbcSchema.updateSchema(JdbcSchema.java:89) at com.google.gerrit.server.schema.SchemaCreator.create(SchemaCreator.java:78) at com.google.gerrit.server.schema.SchemaUpdater.update(SchemaUpdater.java:100) at com.google.gerrit.pgm.init.BaseInit$SiteRun.upgradeSchema(BaseInit.java:341)

Samebug tips0

We couldn't find tips for this exception.

Don't give up yet. Paste your full stack trace to get a solution.

Solutions on the web1

  • via Unknown by djph29,
  • Stack trace

    • com.google.gwtorm.server.OrmException: Cannot apply SQL CREATE TABLE account_group_by_id_aud ( added_by INT DEFAULT 0 NOT NULL, removed_by INT, removed_on TIMESTAMP NULL DEFAULT NULL, group_id INT DEFAULT 0 NOT NULL, include_uuid VARCHAR(255) BINARY DEFAULT '' NOT NULL, added_on TIMESTAMP NOT NULL ,PRIMARY KEY(group_id,include_uuid,added_on) ) at com.google.gwtorm.jdbc.JdbcExecutor.execute(JdbcExecutor.java:44) at com.google.gwtorm.jdbc.JdbcSchema.createRelations(JdbcSchema.java:119) at com.google.gwtorm.jdbc.JdbcSchema.updateSchema(JdbcSchema.java:89) at com.google.gerrit.server.schema.SchemaCreator.create(SchemaCreator.java:78) at com.google.gerrit.server.schema.SchemaUpdater.update(SchemaUpdater.java:100) at com.google.gerrit.pgm.init.BaseInit$SiteRun.upgradeSchema(BaseInit.java:341) at com.google.gerrit.pgm.init.BaseInit.run(BaseInit.java:127)

    Write tip

    You have a different solution? A short tip here would help you and many other users who saw this issue last week.

    Users with the same issue

    We couldn't find other users who have seen this exception.