- On huge infrastructure during execution of mass operation, LaMa may hang
- Solution — Increase the memory for the LaMa JVM (https://help.sap.com/saphelp_nwce10/helpdata/en/43/73949862c16fcbe10000000a1553f6/content.htm)
- During a SAP system cloning operation, the LaMa UI does not allow specifying hostname and IP address for additional physical interfaces as per the selected customization specification. The number of additional physical interfaces for which hostname and IP address can be set is limited to one network adapter. Using the customization specification with three or more network adapters results in an execution error.
-
Figure 1. Virtual Host Names and Networks
-
- Provisioning from virtual host template fails either at the Waiting for host step or at the Adding resources step due to LaMa exception.
- Solution — There is no solution available at this time.
Figure 2. Failure - Provisioning from Virtual Host Template
- Solution — There is no solution available at this time.
- After system cloning operation, validation errors may appear for a cloned SAP system — Error HNMissmatch may be detected for a SAP host during validation.
-
Figure 3. Error - HNMissmatch
-
- Error CloneHnChn may be detected for a SAP sub-system during validation.
-
Figure 4. Error - CloneHnChn
-
- Occasionally the SAP system cloning fails at the Prepare VM clone step. This is seen if the SAP system has several network interfaces and the Auto IP Address option is set for these additional network interfaces in the Host names dialog.
-
Figure 5. Prepare VM Clone Failure
-
- VLVMA adapter cannot be added with the Trusted server option enabled because of File Not Found and Permission denied faults.
- Solution — Make sure that the cacerts file in the directory /usr/sap/<LVM instance ID>/J00/exe/sapjvm_6/jre/lib/security/ has proper access rights (permissions).
- After cloning a SAP JAVA system the status of AS instance of the cloned system is changed to the Error state.
-
Figure 6. SAP JAVA system cloning error state
-
- If a clone or copy operation did not complete successfully, the virtual machine will be deleted from the vCenter Server during the Destroy operation.
- Solution — You need to delete the virtual machine in vCenter Server manually.
- Offline linked copy of SAP HANA on SLES fails on step Stop
-
Figure 7. SAP HANA on SLES failure on Stop Operation
Figure 8. Error - Database is in Use
-