Skip to content

External PostgreSQL

Run the MetaMiner Database (MMDB) on a PostgreSQL server that your DBA manages, instead of the embedded database.

Before you begin

  • A PostgreSQL server reachable from the MetaMiner Server on its port (5432 by default).
  • An empty database for MetaMiner, UTF-8 encoded.
  • A login role for MetaMiner that owns the database and can create schemas and objects in it.
  • The login role can create roles: at every start the MetaMiner Server (MMS) creates or updates the read-only role readonly and the MetaQuery roles mq_reader and mq_reader_all.
  • Optional: SSL enabled on the PostgreSQL server.

TODO: state the minimum supported PostgreSQL version for external MMDB

PostgreSQL 16 is shipped for the embedded database. Confirm the oldest external version supported for BusinessObjects-only installations.

TODO: confirm the exact privileges needed

Source: the read-only role is created at every start, which needs CREATEROLE. Confirm whether CREATEROLE alone is sufficient or whether the login must be a superuser for the MetaMiner role settings (statement and temp-file limits).

Steps

  1. Ask your DBA to create the database and login role, for example:

    Run as a PostgreSQL administrator
    CREATE ROLE metaminer_owner LOGIN PASSWORD '<password>' CREATEROLE;
CREATE DATABASE metaminer OWNER metaminer_owner ENCODING 'UTF8' TEMPLATE template0;

  2. In MMA, stop the server if it is running.

  3. Click Configure MMDB.
  4. Set Active DB Type: to Postgres.
  5. Enter DBMS Host:, Port:, DB Name:, Username: and Password:. Check SSL if the server requires encrypted connections.
  6. Click Validate and Close.
  7. Start the server. MMS creates all schemas on the first start; this takes a few minutes.

Image of the Configure MMDB dialog with Postgres selected and the connection fields filled

../../images/admin/configure-mmdb-external.png

Switching does not move data

Changing Active DB Type points MetaMiner at a different database; it does not copy metadata. MetaMiner then pulls all environments again from the start. To keep history, copy the existing MMDB first; see Back Up and Restore MMDB.

Verify

  • server\logs\server.log shows the schema updates completing and no database errors.
  • The MMA health indicator shows no red state.
  • After the first pull, environments appear in the MetaMiner Client.

Troubleshooting

Validation fails in Configure MMDB

Check host, port, database name, login and password, pg_hba.conf on the PostgreSQL server (the MetaMiner Server address must be allowed), and SSL settings.

The server fails to start after switching

Look for permission errors in server.log. The login must be able to create schemas, objects and roles. Database updates are designed not to depend on specific role names, so they also work when the database owner is not mmuser.

Database updates fail on start

A failed update is logged with its number and is retried at the next start. Updates for the BusinessObjects schema do not block startup; MMS logs which required database objects are missing. Contact Infolytik Support with the log.

Next steps