After upgrade to BPM 8.5.6 when I try to start the nodeagent or Dmgr I see "runConfigActions script execution failed".
I have recently upgrade my BPM Std environment to BPM 8.5.6. When trying to start the deployment manager after the upgrade I see the following exception on the commandline
./startManager.shrunConfigActions script execution failed. Exit code: 1Exception caught while waiting for runConfigActions script to complete:/opt/ibm/BPM/v8.5/profiles/DmgrProfile/bin/runConfigActions.sh
After upgrading to 8.5.6 and starting the servers for the first time some automatic post upgrade steps are executed. The error message indicates that there is an issue running those automatic steps.
The logs to check in that case are
BPMConfig_.log in the profile's log directory and bootstrapProcessServerData.log (only for the deployment manager)
In that specific case here the following exception showed up in the bootstrap log:
ImportFileHel E PreparedStatementCallback; bad SQL grammar [select SNAPSHOT_ID,CREATED_ON,NAME,ACRONYM,DESCRIPTION,SEQ_NUM,ERROR_COUNTER,ORIG_CREATED_ON,ACTIVATED_ON,STATUS,CAPABILITY,ARCHIVED_ON,LAST_MODIFIED,REPOSITORY_BRANCH_ID,CREATED_BY_USER_ID,BRANCH_ID,PROJECT_ID,LAST_MODIFIED_BY_USER_ID,CHANGE_DATA,IS_ACTIVE,IS_BLA_ACTIVE,IS_STARTED,IS_INSTALLED,IS_BLA_INSTALLED,IS_TIP_DEPLOYED,IS_DEFAULT,TIP_DEPLOYMENT_IN_PROGRESS,HAS_SUSPENDED_ALL_INSTANCES,IS_ARCHIVED from LSW_SNAPSHOT where SNAPSHOT_ID = ?]; nested exception is com.ibm.db2.jcc.am.SqlSyntaxErrorException: DB2 SQL Error: SQLCODE=-206, SQLSTATE=42703, SQLERRMC=HAS_SUSPENDED_ALL_INSTANCES, DRIVER=4.18.60org.springframework.jdbc.BadSqlGrammarException: PreparedStatementCallback; bad SQL grammar [select SNAPSHOT_ID,CREATED_ON,NAME,ACRONYM,DESCRIPTION,SEQ_NUM,ERROR_COUNTER,ORIG_CREATED_ON,ACTIVATED_ON,STATUS,CAPABILITY,ARCHIVED_ON,LAST_MODIFIED,REPOSITORY_BRANCH_ID,CREATED_BY_USER_ID,BRANCH_ID,PROJECT_ID,LAST_MODIFIED_BY_USER_ID,CHANGE_DATA,IS_ACTIVE,IS_BLA_ACTIVE,IS_STARTED,IS_INSTALLED,IS_BLA_INSTALLED,IS_TIP_DEPLOYED,IS_DEFAULT,TIP_DEPLOYMENT_IN_PROGRESS,HAS_SUSPENDED_ALL_INSTANCES,IS_ARCHIVED from LSW_SNAPSHOT where SNAPSHOT_ID = ?]; nested exception is com.ibm.db2.jcc.am.SqlSyntaxErrorException: DB2 SQL Error: SQLCODE=-206, SQLSTATE=42703, SQLERRMC=HAS_SUSPENDED_ALL_INSTANCES, DRIVER=4.18.60
This indicates missing post installation steps especially the database upgrade step.
Please follow the DB upgrade steps carefully.
- As we created the IBM Business Process Manager V8.5.x environment without using the BPMConfig command or you do not have a complete configuration properties file, you must complete the following steps to generate the file:
- Upgrade the profile to V8.5.6.
On Microsoft Windows operating systems: install_root\bin\BPMConfig.bat -upgrade -profile deployment_manager_profile_name
On UNIX-based and Linux operating systems: install_root/bin/BPMConfig.sh -upgrade -profile deployment_manager_profile_name - Export the configuration properties file.
On Microsoft Windows operating systems: install_root\bin\BPMConfig.bat -export -profile deployment_manager_profile_name -de deployment_environment_name -outputDir path_to_configuration_files
On UNIX-based and Linux operating systems: install_root/bin/BPMConfig.sh -export -profile deployment_manager_profile_name -de deployment_environment_name -outputDir path_to_configuration_files
The configuration properties file is named deployment_environment_name.propertiesand is in the output directory that you specified. You will refer to this file from the migration properties file in the next step.
Tip: If you do not know the deployment environment name, you can find it by going todeployment_manager_profile/bin and running the following command:
wsadmin -conntype none -lang jython -c "print AdminConfig.list('BPMDeploymentEnvironment')"
The output is either nothing, if no deployment environment is configured, or a statement similar to the following:
WASX7357I: By request, this scripting client is not connected to any server process. Certain configuration and application operations will be available in local mode.
'TestDe(cells/PCCell1|cell-bpm.xml#BPMDeploymentEnvironment_1401230195442)'
The name right before cells/ is the deployment_environment_name, in this case TestDe.
If you are using secure LDAP and you verify the exported properties file with the BPMConfig -validate command, you might see the following error: CWMCB0345E: LDAP protocol ldaps: is not supported. You can safely ignore this error.
- Upgrade the profile to V8.5.6.
- Create a migration properties file using the template. This file will be used in the later upgrade commands. The template properties file to copy is ininstall_root/util/migration/resources/migration.properties. Ensure that the value of each of the following properties in the migration properties file is set correctly:
- bpm.home: IBM Business Process Manager installation path
- profile.name: Name of the deployment manager profile
- target.config.property.file: Full path to the configuration properties file that you used to create your IBM Business Process Manager V8.5.x environment or that you generated in step 12.
Important: Check the bpm.de.sourceInfo.versionInfo property in the configuration properties file and make sure that the source version is correct. If this property does not exist in the file, you do not need to add it. - Run one of the following commands to upgrade your database, wheremigration_properties_file is the migration properties file that you created in step 13.
Notes: If you have multiple deployment environments, complete this step for each deployment environment. Skip this step for AdvancedOnly deployment environments. There is no database schema update for AdvancedOnly environments upgraded from V8.5.x.
On Microsoft Windows operating systems: install_root\bin\DBUpgrade.bat -propertiesFile migration_properties_file
On UNIX-based and Linux operating systems: install_root/bin/DBUpgrade.sh -propertiesFile migration_properties_file
Running the steps outlined should solve the issue.
Thank You.
Regards,
Guru