diff --git a/en/docs/install-and-setup/setup/setting-up-databases/changing-default-databases/changing-to-mssql.md b/en/docs/install-and-setup/setup/setting-up-databases/changing-default-databases/changing-to-mssql.md index 4a0ea5e44d..b90046394e 100644 --- a/en/docs/install-and-setup/setup/setting-up-databases/changing-default-databases/changing-to-mssql.md +++ b/en/docs/install-and-setup/setup/setting-up-databases/changing-default-databases/changing-to-mssql.md @@ -75,8 +75,14 @@ $ pip install mssql-cli $ mssql-cli -U sharedadmin -P sharedadmin -d apim_db -i /dbscripts/apimgt/mssql.sql; ``` -!!! note - As the `WSO2_MB_STORE` DB is not shared and does not contain data that needs to be migrated, it is recommended to use the default H2 for `WSO2_MB_STORE_DB` even in production. +!!! warning + Due to a known limitation in H2 databases that can cause frequent database crashes in production environments, it is recommended to configure an external database for `WSO2_MB_STORE_DB` instead of using the default H2 database. For more information on this H2 limitation, see [H2 Database Issue #4052](https://github.com/h2database/h2database/issues/4052). + + To create tables in the MB store database (`WSO2_MB_STORE_DB`), execute the relevant script as shown below: + + ```sh + $ mssql-cli -U mbstoreuser -P mbstoreuser -d mb_store_db -i /dbscripts/mb-store/mssql-mb.sql; + ``` !!! warning "Troubleshooting" If you encounter the following error while using the default H2 database as the MB store database, follow the instructions in this section. Note that this error will only occur if the MB store database is corrupted. diff --git a/en/docs/install-and-setup/setup/setting-up-databases/changing-default-databases/changing-to-mysql.md b/en/docs/install-and-setup/setup/setting-up-databases/changing-default-databases/changing-to-mysql.md index 4952d31bb2..1b3c1be59d 100644 --- a/en/docs/install-and-setup/setup/setting-up-databases/changing-default-databases/changing-to-mysql.md +++ b/en/docs/install-and-setup/setup/setting-up-databases/changing-default-databases/changing-to-mysql.md @@ -142,8 +142,14 @@ Follow the instructions below to set up a MySQL database: $ mysql -u apimadmin -p -Dapim_db < '/dbscripts/apimgt/mysql.sql'; ``` -!!! note - As the `WSO2_MB_STORE` DB is not shared and does not contain data that needs to be migrated, it is recommended to use the default H2 for `WSO2_MB_STORE_DB` even in production. +!!! warning + Due to a known limitation in H2 databases that can cause frequent database crashes in production environments, it is recommended to configure an external database for `WSO2_MB_STORE_DB` instead of using the default H2 database. For more information on this H2 limitation, see [H2 Database Issue #4052](https://github.com/h2database/h2database/issues/4052). + + To create tables in the MB store database (`WSO2_MB_STORE_DB`), execute the relevant script as shown below: + + ```sh + $ mysql -u mbstoreuser -p -Dmb_store_db < '/dbscripts/mb-store/mysql-mb.sql'; + ``` !!! warning "Troubleshooting" If you encounter the following error while using the default H2 database as the MB store database, follow the instructions in this section. Note that this error will only occur if the MB store database is corrupted. diff --git a/en/docs/install-and-setup/setup/setting-up-databases/changing-default-databases/changing-to-oracle-rac.md b/en/docs/install-and-setup/setup/setting-up-databases/changing-default-databases/changing-to-oracle-rac.md index c1ba2758a5..dc111b92ec 100644 --- a/en/docs/install-and-setup/setup/setting-up-databases/changing-default-databases/changing-to-oracle-rac.md +++ b/en/docs/install-and-setup/setup/setting-up-databases/changing-default-databases/changing-to-oracle-rac.md @@ -57,8 +57,16 @@ Copy the Oracle JDBC libraries (for example, the `/jdbc/lib/ojdbc14 SQL> @/dbscripts/apimgt/oracle_rac.sql ``` -!!! note - As the `WSO2_MB_STORE` DB is not shared and does not contain data that needs to be migrated, it is recommended to use the default H2 for `WSO2_MB_STORE_DB` even in production. +!!! warning + Due to a known limitation in H2 databases that can cause frequent database crashes in production environments, it is recommended to configure an external database for `WSO2_MB_STORE_DB` instead of using the default H2 database. For more information on this H2 limitation, see [H2 Database Issue #4052](https://github.com/h2database/h2database/issues/4052). + + To create tables in the MB store database (`WSO2_MB_STORE_DB`), login to the database via client and execute the relevant SQL file: + + For example, let's consider `mb_store_db` as the database. + + ```sh + SQL> @/dbscripts/mb-store/oracle-rac-mb.sql + ``` !!! warning "Troubleshooting" If you encounter the following error while using the default H2 database as the MB store database, follow the instructions in this section. Note that this error will only occur if the MB store database is corrupted. diff --git a/en/docs/install-and-setup/setup/setting-up-databases/changing-default-databases/changing-to-oracle.md b/en/docs/install-and-setup/setup/setting-up-databases/changing-default-databases/changing-to-oracle.md index f82f4b85c6..147a8ed769 100644 --- a/en/docs/install-and-setup/setup/setting-up-databases/changing-default-databases/changing-to-oracle.md +++ b/en/docs/install-and-setup/setup/setting-up-databases/changing-default-databases/changing-to-oracle.md @@ -59,8 +59,16 @@ Follow the instructions below to set up an Oracle database. SQL> @/dbscripts/apimgt/oracle.sql ``` -!!! note - As the `WSO2_MB_STORE` DB is not shared and does not contain data that needs to be migrated, it is recommended to use the default H2 for `WSO2_MB_STORE_DB` even in production. +!!! warning + Due to a known limitation in H2 databases that can cause frequent database crashes in production environments, it is recommended to configure an external database for `WSO2_MB_STORE_DB` instead of using the default H2 database. For more information on this H2 limitation, see [H2 Database Issue #4052](https://github.com/h2database/h2database/issues/4052). + + To create tables in the MB store database (`WSO2_MB_STORE_DB`), login to the database via client and execute the relevant SQL file: + + For example, let's consider `mb_store_db` as the database. + + ```sh + SQL> @/dbscripts/mb-store/oracle-mb.sql + ``` !!! warning "Troubleshooting" If you encounter the following error while using the default H2 database as the MB store database, follow the instructions in this section. Note that this error will only occur if the MB store database is corrupted. diff --git a/en/docs/install-and-setup/setup/setting-up-databases/changing-default-databases/changing-to-postgresql.md b/en/docs/install-and-setup/setup/setting-up-databases/changing-default-databases/changing-to-postgresql.md index 9cc00066c2..fc9f37aa83 100644 --- a/en/docs/install-and-setup/setup/setting-up-databases/changing-default-databases/changing-to-postgresql.md +++ b/en/docs/install-and-setup/setup/setting-up-databases/changing-default-databases/changing-to-postgresql.md @@ -68,8 +68,16 @@ Follow the instructions below to set up the PostgreSQL database and users. $ psql -U -d apim_db -f /dbscripts/apimgt/postgresql.sql -W ``` -!!! note - As the `WSO2_MB_STORE` DB is not shared and does not contain data that needs to be migrated, it is recommended to use the default H2 for `WSO2_MB_STORE_DB` even in production. +!!! warning + Due to a known limitation in H2 databases that can cause frequent database crashes in production environments, it is recommended to configure an external database for `WSO2_MB_STORE_DB` instead of using the default H2 database. For more information on this H2 limitation, see [H2 Database Issue #4052](https://github.com/h2database/h2database/issues/4052). + + To create tables in the MB store database (`WSO2_MB_STORE_DB`), execute the relevant script as shown below: + + For example, take `mb_store_db` as the database + + ```sh + $ psql -U -d mb_store_db -f /dbscripts/mb-store/postgresql-mb.sql -W + ``` !!! warning "Troubleshooting" If you encounter the following error while using the default H2 database as the MB store database, follow the instructions in this section. Note that this error will only occur if the MB store database is corrupted.