MOVE_CAST_ERROR dump when using UJBR to restore an environment
Hello SAP Experts,
While using UJBR to store Metadata tables the following ST22 dump is generated:
- Runtime Error: MOVE_CAST_ERROR
- Exception: CX_SY_MOVE_CAST_ERROR.
The error can be re-generated by following steps:
- Go to t-code UJBR in the SAP command field
- Select the following options: Restore Meta Data tables and Restore File Service.
- Execute the process and then check the job in t-code SM37
Solution
The MOVE_CAST_ERROR error occurs when a data type mismatch or an inconsistent environment is restored. To fix this error, try these actions:
1) Check SAP Notes:
To resolve the issue please check and implement the following SAP note:
- 2311421 - Removes the cache tables from Backup process in UJBR
- 2415328 - Remove log tables from Backup process in UJBR
2) Check Source and Target Systems:
Ensure that the file service structures and metadata in the environment you're restoring are compatible. This error can be caused by any discrepancy between the source and target computers, including version mismatches or insufficient backups.
3) Execute Data Consistency Checks:
Perform environment consistency checks before executing UJBR:
- To look for validation issues in the environment, run the UJ_VALIDATION application.
- To check the coherence of the metadata table, execute UJ0_GET_GEN_TAB_SUM.
4) Apply Recent Support Packs:
Make sure the most recent patches and support packs are installed on your system. Runtime issues during restoration could be caused by outdated or incompatible support packs.
5) Increase Memory Allocations (Optional):
If the error is due to memory limitations then Y=you might need to modify system parameters for memory allocation, such as ztta/max_memreq_MB or abap/heap_area_total.
6) Debug the UJBR Process:
Get specific information about the location of the cast fault, and enable debugging during the UJBR process if the above-mentioned solution doesn't work. Check ABAP dump in t-code ST22 for more hints about the dump.
7) Contact SAP Support:
After completing these checks, if the problem still exists, you might need to open a ticket with SAP Support and give them the specifics of the ST22 dump and the actions that caused the mistake.