Skip to content

BluAge - L3 Workshop - org.hsqldb.HsqlException: type not found or user lacks privilege: BIGSERIAL

0

Hi,

Currently working on the BluAge workshop execution/backend (https://catalog.us-east-1.prod.workshops.aws/workshops/bf71c0bc-6d8a-4d04-9c10-ab479f7f0e37/en-US/execution/backend), i'm facing an unknown error during Tomcat server startup: Bluesam consoleAdmin: 2025-01-07T16:26:34.962Z WARN 5240 --- [ main] o.h.t.s.i.ExceptionHandlerLoggedImpl : GenerationTarget encountered exception accepting command : Error executing DDL "create table mask (id bigserial... ... org.hibernate.tool.schema.spi.CommandAcceptanceException: Error executing DDL "create table mask (id bigserial not null, version integer default 0 ... Caused by: java.sql.SQLSyntaxErrorException: type not found or user lacks privilege: BIGSERIAL ... Caused by: org.hsqldb.HsqlException: type not found or user lacks privilege: BIGSERIAL

Then, a general error occurs.

Any idea why this is happenning ?

asked 10 months ago128 views
2 Answers
0
Accepted Answer

Could you please check that the BAC datasource is correctly configured in Tomcat configuration files (context.xml and server.xml files) ?

https://catalog.us-east-1.prod.workshops.aws/workshops/bf71c0bc-6d8a-4d04-9c10-ab479f7f0e37/en-US/data-migration/datasets/vsam-ksds https://catalog.us-east-1.prod.workshops.aws/workshops/bf71c0bc-6d8a-4d04-9c10-ab479f7f0e37/en-US/tools/eclipse/tomcat/datasource

Also, run the Publish action on Tomcat server to make everything synchronize (Eclipse WST working folder and Tomcat configuration folder).

AWS
answered 10 months ago
AWS
EXPERT
reviewed 8 months ago
  • Yes, my server.xml got erased at some point in the Eclipse workspace.

0

The error you're encountering during the Tomcat server startup in the BluAge L3 Workshop is related to a database schema creation issue. Specifically, the error message indicates that the database doesn't recognize the "BIGSERIAL" data type.

This problem is likely occurring because the workshop environment is using HSQLDB (Hyper SQL Database), which doesn't support the BIGSERIAL data type. BIGSERIAL is typically used in PostgreSQL, but HSQLDB has different data type conventions.

To resolve this issue, you should check the database configuration in your project. It's possible that the database dialect or configuration is set for PostgreSQL, while the actual database being used is HSQLDB. You may need to adjust the database configuration to match the HSQLDB syntax.

Here are a few steps you can try:

  1. Review your database configuration files (like application.properties or application.yml) and ensure they are set up correctly for HSQLDB.

  2. If you have control over the schema creation scripts, consider replacing BIGSERIAL with a compatible HSQLDB data type. For example, you might use "BIGINT GENERATED BY DEFAULT AS IDENTITY" instead of BIGSERIAL.

  3. Check if there's an option to use a different database that supports BIGSERIAL, such as PostgreSQL, if that's what the workshop intends.

  4. Verify that all required datasources (jics, bluesam, bac, primary) are correctly configured and that the database server is running properly.

If the issue persists after trying these steps, you may need to consult the workshop documentation for any specific instructions related to database setup, or reach out to the workshop support for further assistance.
Sources
AWS Blu Age L3 workshop - Automation step error | AWS re:Post
AWS BluAge L3 Workshop : bac.war causing issues in loading KSDS files to postgres | AWS re:Post

answered 10 months ago
EXPERT
reviewed 10 months ago
  • my server.xml got erased at some point. Thanks !

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.