Oracle: 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 your Oracle 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.
The type of failure that you encounter determines whether you can run the step again. You can repeat the instructions again if the issue for the failure does not affect the values that you entered in the wizard. For example, if you forgot to copy the JDBC JAR files from your database to the portal server, you can copy the files to the portal server. Then, repeat the step without harm. If you need to update wizard values to correct the issue, you must create new scripts in the wizard. Upload your saved selections, update your values, and create scripts. Examples of issues that result in you updating your values include entering the wrong port number or entering an incorrect host name into the wizard. |
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 |
Manual Step: Create the data directory, data, and the index directory, index, on your database server
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 you already created these directories, 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 |
Set up your 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 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, you must create new scripts in the wizard. Upload your saved selections, change the affected values, and create new scripts to run. For example, if you entered the wrong path to your database library, you must upload your saved selections, correct the path, and then configure your system with new scripts. |
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 |
Manual Step: Download the script and run it on the database server to set up your database
During this step, you set permissions on your 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.
In this
step, you download a script to run. The type of failure you encounter determines whether you 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. You can run the downloaded script again if the issue for the failure does not affect any values that you entered in the wizard. If you need to update values, you must create new scripts in the wizard. Upload your saved selections, change the affected values, and create new scripts to run. For example, if you entered the wrong path to your database library, you must upload your saved selections, correct the path, and then configure your system with new scripts. |
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 |
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. For example, if your data and index directories are not created in the correct location, this step might fail. (Automatic Storage Management Users only): After you run the setup database script, you must manually create JCR table spaces to prevent a database transfer failure . Go to Oracle: Creating JCR table spaces (Automatic Storage Management) to perform additional manual instructions. After you perform these instructions, run the transfer database step again. (Automatic Storage Management Users only): If you manually downloaded a script to set up your database, you must edit the script for your Automatic Storage Management environment to prevent a database transfer failure. After you run the edited script, you can run the transfer database step again. 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 |
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 |
Manual Step: Download the script and run it to grant the database runtime user the appropriate privileges to work with database tables
Actions | Notes |
---|---|
Run the step again | You cannot rerun a manual step, but you 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 you can run
the script again. You can run the downloaded script again if the issue for the failure does not affect any values that you entered in the wizard. For example, if you created runtime users and groups incorrectly on your database server, you can correct the issue and run the script again. 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 |
Manual Step: Improve database response time for your database that contains the JCR domain
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 | Not applicable. |
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 |