How To
Summary
Cloud Pak for Business Automation (CP4BA) Starter (Demo) deployments are limited to two Automation Document Processing project databases. Creating a project and deploying to runtime both use a project database. So you are limited to creating and deploying one project, or creating two projects and not deploying either to runtime. Deleting a project does not make the databases available again. This document explains how to reset the databases for use with a new project.
Note: This procedure is specific for a Starter deployment. Use the procedure only if there are no existing projects. Resetting the database for a successfully deployed project causes the project to fail.
Environment
Steps
- Log in to the Red Hat OpenShift Console.
- If you are running 22.0.1 or newer, get the password for the user 'basedb' by navigating to Workloads, Secrets, aca-basedb, selecting Reveal Values, and noting the password in BASE_DB_CONFIG.
- Navigate to Workloads, Pods, and select the database pod for your version.
- 21.0.1 - db2u-release-db2u-0
- 21.0.2 - db2ucluster-cp4ba-db2u-0
- 22.0.x and newer - postgres-cp4ba-1
- Select the Terminal tab.
- Connect to the base database.
- 21.0.2 and older
su db2inst1 db2 connect to CP4ADB set schema = BASEDB
- 22.0.1 and newer
psql -h localhost -p 5432 -d cp4adb -U basedb <enter basedb password when prompted>
- 21.0.2 and older
- Reset the project databases.
- To reset both databases
update tenantinfo set DBSTATUS=0;
- To reset the database from just a deleted project
update tenantinfo set DBSTATUS=0 where DBSTATUS=2;
- To reset both databases
- Close the terminal connection.
quit exit
Document Location
Worldwide
Was this topic helpful?
Document Information
Modified date:
26 October 2023
UID
ibm16552484