Database Migration Option: Target Database SAP HANA

Troubleshooting

This part of the document contains additional information about how to proceed when you want to correct known problems that have occurred during the update.

Known problems and issues

Symptom

Solution

You run a dialogue instance installation after a DMO, and the database SID is shown incorrectly in the dialogue.

Set the parameter j2ee/dbname = <YOUR_HDB_SID> in the default profile and start the installation again.

RFC connection errors occur during the Postprocessing roadmap step.

If RFC connection errors occur, check the connection information for DBACOCKPIT to the target database after the downtime processing of SUM and during Postprocessing roadmap step. If the user is locked, choose Activate user now and Reset connect attempts.

The system does not accept the password of user SYSTEM in phase DBQUERY_PRE.

Move the 720 database administration tools to the subdirectory /abap/exe of your SUM directory.

Error in the Postprocessing roadmap step in phase RUN_PSA_VERSION_CREATE.

Check with transaction SECSTORE your system for any inconsistent entries. Repair the connection to the SAP BW client following SAP Note 816861 Information published on SAP site after you have applied the new license.

Some secondary indexes, which are to be created on selected databases only, can be inconsistent after the migration. These inconsistencies are found in phase RUN_RSDB02CK_END and reported in the log file.

To fix the inconsistencies, use transaction SE14 or SE11 and repeat the phase after the correction.

The creation of a logical index for the master data terminates after the migration to the SAP HANA database. The error messages issued during the execution of the query are for example:

table config error; column store error: fail to create scenario/Index does not exist

See SAP Note 1695112 Information published on SAP site for further information and for a solution.