Symptom
The import/update of SAP HANA Transport Container objects fails in
the subsequent processing phase (method execution). The method execution
log contains information that tells you the following:
- Errors occurred during post-handling SNHI_DELIVERY_UNIT_IMPORT for NHDU L.
The errors affect the following components:
BC-DWB-AIE-AHI (Tools for ABAP and HANA Integration)
Other Terms
SAP HANA Transport Container (HTC), NHDU, delivery unit (DU), ABAP
for SAP HANA, transport (CTS), Software Update Manager (SUM), SUM with
database migration option (DMO), software provisioning manager (SWPM),
Support Package Manager (SPAM), after-import method (AIM), XPRA phase
Reason and Prerequisites
You try to implement SAP HANA repository content in an ABAP on SAP
HANA system using the ABAP Transport Management System (TMS) or other
software logistics tools (such as the Support Package Manager (SPAM),
Software Update Manager (SUM), or software provisioning manager (SWPM)).
The import into the SAP HANA repository ends with return code 8 and the
method execution log provides information like that described in
"Symptom".
Solution
Caution: This SAP Note is updated on a regular
basis. Check this SAP Note to see if it has been updated before creating
a customer message with the component BC-DWB-AIE-AHI or BC-CTS-HTC.
Perform the following steps to identify possible solutions to known problems or to determine the correct component for a customer message:
Known error messages and SAP Notes with suggestions for further analysis
Note that, unless otherwise specified, you must restart the implementation of the SAP HANA repository content using the appropriate software logistics tool after implementing one of the SAP Notes specified below. In the case of an update, you usually need to repeat one phase only. You might have skipped the phase as instructed by an SAP Note; in this case, you do not need to repeat the update.
If you carry out an SP update in EHP 7 for ERP 6.0 or an upgrade to EHP 7 for ERP 6.0, see also the information in SAP Notes 1990263 and 2048896.
Perform the following steps to identify possible solutions to known problems or to determine the correct component for a customer message:
- In the method execution log, search for the transport object R3TR NHDU after the start of logging for the after-import method. The log starts with "Post-import method SNHI_DELIVERY_UNIT_IMPORT started for NHDU L".
- Expand the NHDU log as far as possible and find the first error in this log. The HTC/NHDU log ends with "Post-import method SNHI_DELIVERY_UNIT_IMPORT completed for NHDU L".
- Look for information about this error in this SAP Note.
- If you do not find any information in this SAP Note, carry out a general SAP Note search using the error from the log.
Known error messages and SAP Notes with suggestions for further analysis
Note that, unless otherwise specified, you must restart the implementation of the SAP HANA repository content using the appropriate software logistics tool after implementing one of the SAP Notes specified below. In the case of an update, you usually need to repeat one phase only. You might have skipped the phase as instructed by an SAP Note; in this case, you do not need to repeat the update.
| Error message | SAP tips/further information |
|
Expand the log up to level 4 and search for 'SAP_ECC'. If you find
'SAP_ECC', observe the SAP Note specified in the right-hand column of
this table. Examples for this error are:
|
Have all preconditions for an SAP HANA transport been met? If you use ERP on SAP HANA, you must check "Check 2" in SAP Note 2048896 in particular. |
| "message not found;PackageStoreAccessor::createPackages: SQLpreparation or execution failed. Details can be found in the indexserver trace file." | 1996489 |
| "insufficient privilege: Not authorized" or "Repository: User is not authorized to execute specified operation;User 'SAP<SID>' has no authorization, privilege: 'REPO.IMPORT''' | If you use ERP on SAP HANA, you must check "Check 3" in SAP Note 2048896 in particular. |
| "Repository: import failed;Import::importMultipleFiles(): package sap.erp.sappl.ps.st of DU HCO_ERP_SAPPL_PS_ST is also contained in one of the other DUs" | 1973964 |
| "Repository: import version does not match system version;ArchiveUtil::readFileHeader(): version read from file (13) is higher than current system version (12). Please update your system or import will not work" | 1984354 |
| "CX_SY_RANGE_OUT_OF_BOUNDS" or "CX_SY_CONVERSION_CODEPAGE" | 1903295 |
| "message not found;Write inactive objects: SQL preparation or execution failed. Details can be found in the indexserver trace file" |
Check whether you can implement SAP Note 1990263. If not, create a customer message with the component HAN-AS-RPO, state the precise version of the SAP HANA database, and attach the SAP HANA index server trace file to the message. You can view and download this file by choosing "SAP HANA Studio -> Diagnosis Files" or calling transaction DBACOCKPIT and then choosing "Diagnostics -> Diagnosis Files". |
| "Repository: Encountered an internal error in the repository code, this is most likely a bug in the implementation;failed to write attached content to file" |
For more information about the error, see the SAP HANA index server
trace file. You can view and download this file by choosing "SAP HANA
Studio -> Diagnosis Files" or calling transaction DBACOCKPIT and then
choosing "Diagnostics -> Diagnosis Files". At present, the following error situations are known:
If none of the aforementioned points apply, open an incident with the component HAN-AS-RPO. Specify the exact version of the SAP HANA database and attach the SAP HANA index server trace file to the incident. |
|
The system issues "ColumnTable SAP_EWM:/SCWM/WRKL not found", "Could
not get physical name for schema 'SAP_EWM'", or other errors for objects
in the package "sap.ewm.scmewm". |
The errors occur during the installation or update of SAP EWM. Solutions are described in SAP Note 1892669 in section 6, "Known errors". |
|
"Column store table <table name> does not exist in schema <schema>" |
If the schema is SAP_ECC, go to the first row in this table. If the schema is the correct SAP<SID> schema, use transaction SE11 to check that the specified table is a pooled table. If this is the case, execute the report specified in SAP Note 1849890. |
|
'invalid name of function or procedure: sap.erp.sappl.pph.v02.read.pers/READ_MAT_BERID_CTRL_PARAMS' |
2233213 |
|
"Repository: objects are already locked by another
change;Repository::import(): some of the imported objects are already
locked due to following changes_entries: {changeID: (srcSystem:
<SystemID>, changeNumber: <Nummer>, container: ), objectID:
{tenant: , package: <HANA Repository Paketname>, name: <HANA
Respository Objektname>, suffix: <HANA Repository
Objekttyp> }}' |
Release the change list mentioned under 'changeID' in HALM (SAP HANA
Application Lifecycle Management) of the system ('SystemID') mentioned
under 'srcSystem' or deactivate the change recording in this system.
Then repeat the import/update. General recommendation from SAP Note 2233470: Do not use the change recording in SAP-HANA systems that are also used for ABAP on SAP HANA systems for which the transport mechanism SAP HANA Transport for ABAP (HTA) or the transport mechanism SAP HANA-Transport-Container (HTC) is used. Otherwise, import errors may occur. |
If you carry out an SP update in EHP 7 for ERP 6.0 or an upgrade to EHP 7 for ERP 6.0, see also the information in SAP Notes 1990263 and 2048896.
Header Data
| Released On | 07.01.2016 14:48:56 | ||
| Release Status | Released for Customer | ||
| Component | BC-CTS-HTC Hana Transport Container (ABAP) | ||
| Other Components |
| ||
| Priority | Correction with medium priority | ||
| Category | Help for error analysis |
No comments:
Post a Comment