After installing OBM, an error occurs during the DB configuration step

Hello, guys. I'm Jiwook.

After installing OBM, an error occurs during the DB configuration step.

The error content is 'org.postgresql.util.PSQLException: ERROR : relation "id_catalog" does not exist Position: 20'.

Does anyone know why this happens?

I need help.
Thank you.

  • Suggested Answer

    0  

    Hello,

    The error message means

    The error message gives Postgres state 42P01.  The error means the database is trying to access a table named "id_catalogue," but the table does not exist in the schema.  

    Please log into Postgres and check which tables have been created:

    [postgres]$ psql
    psql (13.13)
    Type "help" for help.
     
    postgres=# \l
                                      List of databases
       Name    |  Owner   | Encoding |   Collate   |    Ctype    |   Access privileges
    -----------+----------+----------+-------------+-------------+-----------------------
    event     | postgres | UTF8     | en_US.UTF-8 | en_US.UTF-8 |
    mgmt      | postgres | UTF8     | en_US.UTF-8 | en_US.UTF-8 |
    postgres  | postgres | UTF8     | en_US.UTF-8 | en_US.UTF-8 |
    rtsm      | postgres | UTF8     | en_US.UTF-8 | en_US.UTF-8 |
    template0 | postgres | UTF8     | en_US.UTF-8 | en_US.UTF-8 | =c/postgres          +
              |          |          |             |             | postgres=CTc/postgres
    template1 | postgres | UTF8     | en_US.UTF-8 | en_US.UTF-8 | =c/postgres          +
              |          |          |             |             | postgres=CTc/postgres

    These table names need to match the table names in the configuration wizard and they also need to be created.  When on the database settings pages of the wizard, mane sure you select "create a new database or user schema".

    I hope this helps.

  • Suggested Answer

    0  

    I had the same issue, and at the end in the configserver_all.log it showed that the mgmt schema failed to be created, but the primary error was a different one: 

    2025-01-15 16:45:53,809 [JobExecutor-2] (SqlTask.java:98) INFO - Executing sql task :conf/sql/postgres/postgres-reg-db-extension.sql with DB context :dbType=(Postgresql); hostName=puegcsvm67908.swinfra.net; dbName=mgmt; userName=postgres; server=puegcsvm67908.swinfra.net; port=5432
    2025-01-15 16:45:53,819 [JobExecutor-2] (SqlTask.java:123) ERROR - Executing SQL failed
    org.postgresql.util.PSQLException: ERROR: could not open extension control file "/usr/share/pgsql/extension/uuid-ossp.control": No such file or directory

    Then the installationg moved forward and the secondary error related to id_catalogue also appeared, that is a consequence of this primary error:

    2025-01-15 16:46:04,246 [JobExecutor-2] (DBPropertiesManager.java:112) ERROR - Failed to initialize IDGen
    com.mercury.infra.config.idgen.IDGenPersistencyException: ERROR: relation "id_catalog" does not exist
    Position: 20

    Once I fixed the initial error the id_catalogue one got fixed as well. In order to solve the uuid-ossp.control missing file error I had to install the uuid-ossp extension for postgres in my DB server. Then I dropped the mgmt schema that was not properly created and this time installation run smoothly. 

    This package is mentioned in the installation guide at "https://docs.microfocus.com/doc/Operations_Bridge_Manager/24.2/PsqlGrantAccessPermissions" it says:

    "You must install the PostgreSQL contrib package for registration of the uuid-ossp extension"

  • 0   in reply to   

    Yeah, I just found that too ;-)

    Install by:
    sudo apt-get install postgresql-contrib

    Or:

    sudo yum install postgresql-contrib

    Test with: 

    SELECT uuid_generate_v1();
    SELECT uuid_generate_v4();

    You may need to log into the DB and run: 
    CREATE EXTENSION IF NOT EXISTS "uuid-ossp";