Troubleshoot: Upgrade node profiles for a cluster environment
If we encounter a failure while upgrading the node profiles for a cluster environment, learn how to correct the issue and recover from the failure.
Each potential step in the upgrade node profiles option is included. Since the steps vary, depending on the selections, the steps are not numbered. Find the step that failed to learn more about correcting and recovering from the failure.
Related concepts:
Cluster: Upgrade node profiles
Manual Step: Update the ports for the deployment manager and nodes
Since this is a manual step, any error that occurs is outside the context of the wizard.
Actions Notes Run the step again We can run this step again if it fails. Skip the step If this step was successful, we can skip it if we run the configuration process again. Clean up step None required
Upgrade the ConfigEngine
Actions Notes Run the step again If this step fails, we can run this step again after you clean up the issue. Skip the step If this step was successful, we can skip it if we run the configuration process again. If we re-create the profile for any reason, run this step again.
Clean up step If this step fails, review the parameters and values entered in the Configuration Wizard, specifically the new host name, passwords, port numbers, and the Portal server path. If the parameter and values entered are correct, and the step fails again, use the wp-collector tool to gather the files needed to contact support for help. See Data collection and symptom analysis for information about using the wp-collector tool.
Update database settings
Actions Notes Run the step again Not applicable Skip the step If this step was successful, we can skip it if we run the configuration process again. If we re-create the profile for any reason, run this step again.
Clean up step None required
Validate the database settings
Actions Notes Run the step again If this step fails, we can run this step again after you clean up the issue. Skip the step If this step was successful, we can skip it if we run the configuration process again. If we re-create the profile for any reason, run this step again.
Clean up step Check the properties files to make sure that we have all of the parameters and values set correctly before running the step again.
Connect to new databases
Actions Notes Run the step again If this step fails, we can run the step again. Skip the step If this step was successful, we can skip it if we run the configuration process again. If we re-create the profile for any reason, run this step again.
Clean up step None required
Manual Step: Review database schema changes
Since this is a manual step, any error that occurs is outside the context of the wizard.
Actions Notes Run the step again If this step fails, we can run this step again. Skip the step This step is optional. We can skip this step if we do not want to review the database schema changes. Clean up step None required
Upgrade the base portal database component
Actions Notes Run the step again If this step fails, we can run this step again after you clean up the issue. Skip the step Do not skip this step, if we are running the configuration again. Clean up step If this step fails, delete the database, create a new copy, and run the step again.
Manual Step: Remove check pending statuses from table spaces
Since this is a manual step, any error that occurs is outside the context of the wizard.
Actions Notes Run the step again If this step fails, clean up the issue and start back with the Upgrade the base portal database components step, and then run this step again. Skip the step Do not skip this step, if we are running the configuration again. Clean up step If this step fails, delete the database, create a new copy, and run the Upgrade the portal database component step again before you rerun this step again.
Upgrade the remaining portal databases
Actions Notes Run the step again If this step fails, clean up the issue and start back with the Upgrade the base portal database components. Skip the step Do not skip this step, if we are running the configuration again. Complete the Upgrade the base portal database components and Remove check pending statuses from table spaces steps before running this step again. Clean up step If this step fails, delete the database, create a new copy, and rerun the Upgrade the portal database component and Remove check pending statuses from table spaces steps before running this step again.
Upgrade the portal profile
Actions Notes Run the step again If this step fails, we must contact support. Contact support before starting the Portal server.
Skip the step Do not skip this step, if we are running the configuration again. Clean up step Contact support. When we run this step, the sub task named action-deploy-portlets-applyMIGStatic-wp.oob.full runs and completes successfully. However, the following error messages are shown. We can ignore these error messages:
- EJPXA0161W: The web module ContactList could not be activated. Please see previous messages for reasons and possible corrective actions.
- EJPPH0048W: The synchronization mode of all nodes in the portal cluster is not consistently set. The portlet application PA_ContactList will not be started in the Application Server. Manual synchronization is assumed for all nodes. Manually start the application after all nodes were synchronized.
- EJPXA0067E: The following configuration data is needed to create a content-node resource: content-parentref.
Parent Troubleshooting the Configuration Wizard