DB2 for z/OS: Troubleshooting Database Transfer
If you encounter a failure during the configuration process, determine whether you can run the step again, skip the step, or if you must clean up the step. For some failed steps, learn how to correct the issue and recover from the failure.
Each potential step in the configuration is included. Because the steps vary depending on your selections, the steps are not numbered. Find the step that failed to learn more about correcting and recovering from the failure. If you need to change a value that you entered in the wizard, then you must run the configuration again.
Back up the properties files that the wizard uses during the configuration
Actions | Notes |
---|---|
Run the step again | You can run the step again without causing any harm. Alternatively, you can manually back up the properties files instead of running the step again. |
Skip the step | If
you already backed up your properties files before you started this configuration, you can skip this
step. If this step is successful, you can skip it if you encounter a failure in a later step and need to run the configuration again. |
Clean up step | None required |
Manual Step: Create the database configuration users on DB2® for z/OS®
Actions | Notes |
---|---|
Run the step again | You cannot rerun a manual step, but you can perform the instructions for the step again without harm. |
Skip the step | If this step is
successful, you can skip it if you encounter a failure in a later step and need to run the
configuration
again. If you have database IDs that are already defined, review the RACF commands before you skip this step. You might need to edit the RACF commands. For example, the RACF administrator might need to remove the ADDUSER commands if you already have database user IDs that are defined in your RACF. |
Clean up step | None required |
Manual Step: Download the script and view instructions to delete existing databases
Actions | Notes |
---|---|
Run the step again | You can run this step only under certain conditions.
|
Skip the step | If you have never run the transfer database step, you can skip this step. |
Clean up step | None required |
Manual Step: Download the script and view instructions to create your databases
Actions | Notes |
---|---|
Run the step again | You cannot rerun a manual step, but you can perform the
instructions for the step again without harm. Use the SQLSTATE associated with the error message to determine the source of the problem. |
Skip the step | If this step is successful, you can skip it if you encounter a failure in a later step and need to run the configuration again. |
Clean up step | If you need to update wizard values to correct the issue, do not run the
commands in this step again. You must create new scripts in the wizard. Upload your saved
selections, update your values, and create scripts. In the next configuration attempt, you must delete existing databases before you create databases. Do not skip the following step: Manual Step: Download the script and view instructions to delete existing databases |
Validate the database connection and environment
During this step, you are validating that the database is still available and that you can successfully connect to the database.
Actions | Notes |
---|---|
Run the step again | You cannot rerun a manual step, but you can perform the instructions for the step again without harm. |
Skip the step | If this step is successful, you can skip it if you encounter a failure in a later step and need to run the configuration again. |
Clean up step | None required |
Stop the portal server
Actions | Notes |
---|---|
Run the step again | You can run the step again without causing any harm. |
Skip the step | If you already stopped the portal server, you can skip this step. |
Clean up step | None required |
Transfer the database
Actions | Notes |
---|---|
Run the step again | The type of failure that you encounter determines whether you can run the
step again. Use the ERRORCODE and SQLSTATE associated with the error message in the ConfigTrace.log to determine the reason for the failure. You might have a portal failure that does not have a SQLSTATE error code that is associated with the error message. You can run the step again if the issue for the failure does not affect any values that you entered in the wizard. If you need to update values in the wizard, you must create new scripts in the wizard. Upload your saved selections, change the affected values, and create new scripts to run. You do not need to run previous successful steps. |
Skip the step | If this step is successful, you can skip it if you encounter a failure in a later step and need to run the configuration again. |
Clean up step | If you need to update wizard values to correct the
issue, do not run the commands in this step again. You must create new scripts in the wizard. Upload
your saved selections, update your values, and create scripts. In the next configuration attempt, you must delete existing databases before you create databases. Do not skip the following step: Manual Step: Download the script and view instructions to delete existing databases. |
Grant privileges to the database runtime users
Actions | Notes |
---|---|
Run the step again | The type of failure that you encounter determines whether you can run the
step again. You can run the step again if the issue for the failure does not affect any values that you entered in the wizard. If you need to update values in the wizard, you must create new scripts in the wizard. Upload your saved selections, change the affected values, and create new scripts to run. You do not need to run previous successful steps. |
Skip the step | If this step is successful, you can skip it if you encounter a failure in a later step and need to run the configuration again. |
Clean up step | None required |
Connect to your databases
Actions | Notes |
---|---|
Run the step again | The type of failure that you encounter determines whether you can run the
step again. Use the ERRORCODE and SQLSTATE associated with the error message in the ConfigTrace.log to determine the reason for the failure. You can run the step again if the issue for the failure does not affect any values that you entered in the wizard. If you need to update values in the wizard, you must create new scripts in the wizard. Upload your saved selections, change the affected values, and create new scripts to run. You do not need to run previous successful steps. |
Skip the step | If you need to run the configuration again, you must repeat this step if you
need to run the transfer database step again. If this step is
successful, you can skip it if you encounter a failure in a later step and need to run the
configuration
again. If this step is successful, you can skip it if you encounter a failure in a later step. |
Clean up step | None required |
Manual Step: Download the script and view instructions to reset the check pending status on portal table spaces
Actions | Notes |
---|---|
Run the step again | You cannot rerun a manual step, but you can perform the instructions for the step again without harm. |
Skip the step | If this step is successful, you can skip it if you encounter a failure in a later step and need to run the configuration again. |
Clean up step | None required |
Reset the web content manager event log
Actions | Notes |
---|---|
Run the step again | You can run this step repeatedly without causing harm. |
Skip the step | If this step is successful, you can skip it if you encounter a failure in a later step and need to run the configuration again. |
Clean up step | None required |
Start the portal server
Actions | Notes |
---|---|
Run the step again | You can run the step again without causing any harm |
Skip the step | If you already started the portal server, you can skip this step. |
Clean up step | None required |