Unsupported content This version of the documentation is no longer supported. However, the documentation is available for your convenience. You will not be able to leave comments.

Specifying the product environment during the database migration


This topic provides the workaround required when you use a custom environment for the BMC Release Process Management application.

When you change the default environment  for the BMC Release Process Management application in <RLM_HOME>\server\jboss\standalone\deployments\RPM_KNob.yml and that environment configuration is not specified in <RLM_HOME>\releases\<your current product version>\RPM\config\database.yml, then after running the rake task for the database migration, the following error appears:

rake aborted!
database configuration does not specify adapter

To fix this issue, add the necessary configurations for your environment to the to <RLM_HOME>\releases\<your current product version>\RPM\config\database.yml, or use configurations of another environment from <RLM_HOME>\releases\<your current product version>\RPM\config\database.yml by running the following rake task in the command line:

 jruby -S rake db:migrate RAILS_ENV=<environment_name>

For example, if you want to use the database configurations for the production environment, run the following rake task in the command line:

 jruby -S rake db:migrate RAILS_ENV=production

Related topics

Patch-1-version-4-4-00-01

Patch-2-version-4-4-00-02

Patch-3-version-4-4-00-03

Patch-4-version-4-4-00-04

Patch-5-version-4-4-00-05

Patch-6-version-4-4-00-06

Patch-7-version-4-4-00-07

Patch-8-version-4-4-00-08

Patch-9-version-4-4-00-09

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*