Oracle: Troubleshooting Database Transfer
If we encounter a failure during the configuration process, determine whether we can run the step again, skip the step, or if we 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. 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. To change a value entered in the wizard, then run the configuration again.
If we must go through the wizard again, download the wizard selections that you made to save time. Then, cancel the configuration. Start the process over and upload the saved selections. Correct or enter values for the parameters that caused the failure.
Back up the properties files the wizard uses during the configuration
During this step, the wizard attempts to back up the wkplc.properties, wkplc_dbdomain.properties, and wkplc_dbtype.properties files.
Actions Notes Run the step again We can run the step again without causing any harm. Alternatively, we can manually back up the properties files instead of running the step again. Skip the step If we already backed up the properties files before startinged this configuration, we can skip this step. If this step is successful, we 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 Oracle database
step: Manual
Actions Notes Run the step again We cannot rerun a manual step, but we can perform the instructions for the step again without harm. The type of failure that you encounter determines whether we can run the step again.
We can repeat the instructions again if the issue for the failure does not affect the values entered in the wizard. For example, if you forgot to copy the JDBC JAR files from the database to the portal server, we can copy the files to the portal server. Then, repeat the step without harm.
To update wizard values to correct the issue, create new scripts in the wizard. Upload your saved selections, update the values, and create scripts. Examples of issues that result in you updating the values include entering the wrong port number or entering an incorrect host name into the wizard.
Skip the step If this step is successful, we 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 data directory, data, and the index directory, index, on the database server
step: Manual Step: Create the data directory, data, and the index directory, index,
Actions Notes Run the step again We cannot rerun a manual step, but we can perform the instructions for the step again without harm. Skip the step If we already created these directories, skip this step. If this step is successful, we can skip it if you encounter a failure in a later step and need to run the configuration again.
Clean up step None required
Set up the database
Use the ERRORCODE and SQLSTATE associated with the error message in the ConfigTrace.log to determine the source of the problem.
Actions Notes Run the step again The type of failure that you encounter determines whether we can run the step again. We can run the step again if the issue for the failure does not affect any values entered in the wizard. To update values, create new scripts in the wizard. Upload the saved selections, change the affected values, and create new scripts to run. For example, if we entered the wrong path to the database library, we must upload the saved selections, correct the path, and then configure the system with new scripts.
Skip the step If this step is successful, we 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: Download the script and run it on the database server to set up the database
During this step, we set permissions on the database.
Actions Notes Run the step again We cannot rerun a manual step, but we can perform the instructions for the step again without harm. In this step, you download a script to run. The type of failure you encounter determines whether we can run the script again. Use the ERRORCODE and SQLSTATE associated with the error message in the ConfigTrace.log to determine the reason for the failure.
We can run the downloaded script again if the issue for the failure does not affect any values entered in the wizard.
To update values, create new scripts in the wizard. Upload the saved selections, change the affected values, and create new scripts to run. For example, if we entered the wrong path to the database library, we must upload the saved selections, correct the path, and then configure the system with new scripts.
Skip the step If this step is successful, we can skip it if you encounter a failure in a later step and need to run the configuration again. Clean up step None required
Validate the database connection and environment
During this step, we are validating the database is still available and we can successfully connect to the database.
Actions Notes Run the step again We cannot rerun a manual step, but we can perform the instructions for the step again without harm. Skip the step If this step is successful, we 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 We can run the step again without causing any harm. Skip the step If we already stopped the portal server, we 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 we 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.
We might have a portal failure that does not have a SQLSTATE error code associated with the error message.
We can run the step again if the issue for the failure does not affect any values entered in the wizard. For example, if the data and index directories are not created in the correct location, this step might fail.
To update values in the wizard, create new scripts in the wizard. Upload your saved selections, change the affected values, and create new scripts to run. We do not need to run previous successful steps.
Skip the step If this step is successful, we can skip it if you encounter a failure in a later step and need to run the configuration again. Clean up step None required
Grant privileges to the database runtime users.
step: Grant privileges
Actions Notes Run the step again The type of failure that you encounter determines whether we can run the step again. We can run the step again if the issue for the failure does not affect any values entered in the wizard.
To update values in the wizard, create new scripts in the wizard. Upload your saved selections, change the affected values, and create new scripts to run. We do not need to run previous successful steps.
Skip the step If this step is successful, we 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: Download the script and run it to grant the database runtime user the appropriate privileges to work with database tables
step: Manual Step: Download the script and run it to grant the database runtime
Actions Notes Run the step again We cannot rerun a manual step, but we can perform the instructions for the step again without harm. In this step, you download a script to run. The type of failure you encounter determines whether we can run the script again. We can run the downloaded script again if the issue for the failure does not affect any values entered in the wizard. For example, if created runtime users and groups incorrectly on the database server, we can correct the issue and run the script again.
To update values in the wizard, create new scripts in the wizard. Upload the saved selections, change the affected values, and create new scripts to run. We do not need to run previous successful steps.
Skip the step If this step is successful, we 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: Improve database response time for the database containing the JCR domain
step: Manual Step: Improve database response time for the database containing
Actions Notes Run the step again We cannot rerun a manual step, but we can perform the instructions for the step again without harm. Skip the step Not applicable. Clean up step None required
Start the portal server
Actions Notes Run the step again We can run the step again without causing any harm Skip the step If we already started the portal server, we can skip this step. Clean up step None required