Metabase errors can arise from various issues such as database connection problems, configuration issues. Common causes include incorrect database credentials, network connectivity issues, or misconfigured settings.
When you create, upgrade, or delete a metabase and problems occur that block the action from successfully completing, a Metabase Errors window opens showing all available SQL messages generated from the server system, including error messages. Use the error message details to help troubleshoot the problems before attempting the action again.
Note:
- If any error(s) occur while creating a metabase, any partially completed actions will be rolled back.
- Scroll down to see any details too long to fit the Details field or drag the corner of the window to resize it.
- Click Copy To Clipboard to save the text of the error message. You can paste the text into another application to share or archive.
- Click Close to the window. If you are creating a metabase, the New Metabase window remains open.
Types of Errors
When performing replication, you might get an error message in these circumstances:
- You failed to stop the associated project prior to upgrading or deleting a metabase. The message will indicate that the kernel on the runtime server is running and must be stopped before you can proceed.
- You have data in the replication backlogs and you will lose transactions that have not yet been replicated.
- You upgraded and deleted a metabase, and the port number for the connection associated with the metabase changed.
- You added a metabase and a metabase already exists for the data connection.
- You entered an invalid username or password when adding a metabase.