How To Fix SCTS_HOT621 - Redeployment of objects with errors started for HDI &1,HANA Repository &2

SAP Error Message - Details

• Message type: E = Error

• Message class: SCTS_HOT - Messages for HANA Object Transport

• Message number: 621

• Message text: Redeployment of objects with errors started for HDI &1,HANA Repository &2

System Response

When starting to deploy SAP HANA objects, the system identified that HDI
objects and/or SAP HANA Repository packages/objects with deployment
errors already existed in the HTA Repository before the deployment, but
these packages/objects were not part of the deployment.
SAP HANA objects are deployed in the following cases:
When transporting HDI objects/SAP HANA Repository packages/objects in
the import step <ZK>SAP HANA Deployment</>
When using Note Assistant (transaction SNOTE) to import corrections to
HDI objects/SAP HANA Repository packages/objects
In manual deployments of HDI objects in the transaction SCTS_HDI_DEPLOY
These HDI objects/SAP HANA packages/objects with errors may have
possibly been deployable after the deployment, which is why the system
attempted to deploy them. As a result, the system scheduled a job named
REDEPLOY_FAILED_HANA_OBJECTS.
The job attempts the following:
It tries to deploy all HDI objects that have status <LS>E - Deployment
to container failed</> or <LS>Z - Deletion in container failed</> in the
HTA Repository in the system to the HDI containers.
It tries to deploy all SAP HANA packages/objects that have the status
<LS>E - Deployment to SAP HANA Repository failed</> or <LS>Deletion in
SAP HANA Repository failed</> in the system HTA Repository to the SAP
HANA Repository.
This means it is possible to only correct and transport the HDI
objects/SAP HANA packages/objects that actually contain errors, because
all dependent HDI objects/SAP HANA packages/objects containing errors
are automatically deployed again after the import and are error-free if
the deployment is successful.
The current status of HDI objects can be viewed in the transaction
SCTS_HDI_DEPLOY.
The current status of SAP HANA packages/objects in the HTA Repository
can be viewed in transaction SCTS_HTA_DEPLOY in the package/object
details.

Procedure for System Administrators

The job is scheduled by default if packages/objects/HDI objects with
deployment errors existed in the HTA Repository before the deployment
but they were not part of the deployment.
The automatic scheduling of the job can be controlled using HTA
parameter RUN_JOB_REDEPLOY_FAILED_HANA_OBJECTS. If the entry does not
exist in table CTS_HOT_PARAMS or has the value X, the job is
automatically scheduled after the deployment. This job is also scheduled
automatically for the following values:
For the value H (but only if HDI objects with errors exist)
For the value R (but only if SAP HANA Repository objects with errors
exist)
For all other values, the job is not automatically scheduled. The job is
only scheduled, however, for the object type (HDI and/or SAP HANA
Repository) for which objects were also deployed.
Alternatively you can schedule the job manually and only have the job
run at specific times, for example. To do this, schedule a job for
report SCTS_HTA_REDEPLOY_FAILED .
It is also possible to start report SCTS_HTA_REDEPLOY_FAILED manually in
transaction SA38.
If the job was scheduled by the import step <ZK>SAP HANA deployment</>
when transporting SAP HANA objects, the log of the redeployment job is
found in the step <ZK>Redeployment of HANA objects with errors</> (this
step is not specific to a transport request).
In all cases, it can also be found in the subdirectory <LS>log</> of the
transport directory. Its name is <LS>5<(><<)>yymmdd>.<(><<)>SID></>.
Example: If the redeployment was started on January 22, 2016, the log is
found under <LS>/usr/sap/trans/log/5160122.QAS</>.
To display the log, start report RSPUTPRT in transaction SA38. For the
field <LS>Full File Name (with Dir.)</>, enter the value of the complete
file name, for example: <LS>/usr/sap/trans/log/5160122.QAS</>.
The number of activation attempts for SAP HANA Repository objects when
redeploying SAP HANA objects with errors can be changed using the HTA
parameter MAX_NO_ACTIVATION_ATTEMPTS_REDEPL_FAILED in the table
CTS_HOT_PARAMS.
For information about the process of activating SAP HANA Repository
objects, see the <DS:NA.SCTS_HOT539>long text of the message for the
individual activation attempts</>.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message SCTS_HOT621 - Redeployment of objects with errors started for HDI &1,HANA Repository &2 ?

  The SAP error message SCTS_HOT621 indicates that there was an issue during the redeployment of objects in the HANA database, specifically related to HDI (HANA Deployment Infrastructure) and the HANA Repository. This error typically arises when there are inconsistencies or errors in the deployment of database objects.
  Causes:
  
  Object Dependencies: There may be dependencies between objects that are not met, leading to errors during redeployment.
  Syntax Errors: There could be syntax errors in the SQL scripts or definitions of the objects being deployed.
  Version Mismatch: The version of the objects in the HDI container may not match the expected version in the HANA repository.
  Resource Conflicts: Conflicts with existing objects in the HANA database can prevent successful redeployment.
  Configuration Issues: Misconfigurations in the HDI container or the HANA environment can lead to deployment failures.
  
  Solutions:
  
  Check Logs: Review the detailed logs for the specific errors that occurred during the redeployment. This can provide insights into what went wrong.
  Validate Objects: Ensure that all objects being deployed are valid and do not have syntax errors. You can use tools like the HANA Studio or Web IDE to validate the objects.
  Resolve Dependencies: Make sure that all dependencies are satisfied before redeploying. This may involve deploying dependent objects first.
  Rebuild HDI Container: If the issue persists, consider rebuilding the HDI container. This can sometimes resolve inconsistencies.
  Check for Conflicts: Look for any existing objects in the HANA database that may conflict with the objects being deployed. You may need to drop or rename conflicting objects.
  Consult Documentation: Refer to SAP documentation for specific guidelines on HDI and HANA repository deployments, as there may be version-specific considerations.
  
  Related Information:
  
  SAP Notes: Check SAP Notes related to HDI and deployment errors for any known issues or patches that may address the problem.
  SAP Community: Engage with the SAP Community forums to see if others have encountered similar issues and what solutions they found effective.
  HANA Studio/Web IDE: Use these tools for better visibility into the deployment process and to troubleshoot issues interactively.
  
  If the problem persists after trying the above solutions, consider reaching out to SAP support for further assistance, providing them with detailed logs and error messages for a more accurate diagnosis.