SAP Knowledge Base Article - Preview

2393464 - FAQ: SAP HANA Live Content Installation

Symptom

Whilst importing delivery units into your SAP HANA System you can sometimes run into some common errors which can easily be fixed without the means of opening an SAP Incident.

Lets look at an example when importing SAP HANA Analytics into a system. During the import you may see an error similiar to this:

Wiki.png

To get a more in depth look a what actually went wrong here, we would need to look into the installation log (this is printed after the import fails) or the indexserver.trc file:

[37654]{228998}[123/-1] 2014-04-07 23:24:06.604933 e REPOSITORY  activator.cpp(01179) : Repository: Activation failed for at least one object;At least one runtime reported an error during revalidation. Please see CheckResults for details.

 

The problem in such cases is the person who was responsible for the prerequisites for the import did not check SAP note 1781992 before starting the import.

It is very important to have the necessary tables in the SAP_ECC Schema or else the import will fail. Best thing to do if this fails is to compare the existing tables with the tables listed in the note by executing this SQL:

 

select table_name from m_cs_tables where schema_name = 'SAP_ECC' order by table_name asc;

 

What if you have already imported the tables and the installation log is saying that it cannot find some particular tables. Here is an example of something you may see in the logs:

 

2016-05-30 15:14:55:381|-02:00|8|SYSTEM|Object: sap.hba.ecc.TCURM_BWKEY_BUKRS_WERKS.calculationview ==> Error Code: 40117
2016-05-30 15:14:55:382|-02:00|8|SYSTEM|Repository: Encountered an error in repository runtime extension;Model inconsistency. 
Create Scenario failed: ColumnTable SAPERP:TCURM not found (cannot get catalog object)(calculationNode (BW_1$$$$TCURM$$))The following errors occurred: Inconsistent calculation model (34011)
2016-05-30 15:14:55:409|-02:00|8|SYSTEM|Object: sap.hba.ecc.T156C_BSTAUS.calculationview ==> Error Code: 40117
2016-05-30 15:14:55:410|-02:00|8|SYSTEM|Repository: Encountered an error in repository runtime extension;Model inconsistency.
Create Scenario failed: ColumnTable SAPERP:T156C not found (cannot get catalog object)(calculationNode (T156C))The following errors occurred: Inconsistent calculation model (34011)
2016-05-30 15:14:55:442|-02:00|8|SYSTEM|Object: sap.hba.ecc.SpecialGLCode.calculationview ==> Error Code: 40117
2016-05-30 15:14:55:443|-02:00|8|SYSTEM|Repository: Encountered an error in repository runtime extension;Model inconsistency.
Create Scenario failed: ColumnTable SAPERP:T074T not found (cannot get catalog object)(calculationNode (T074T))The following errors occurred: Inconsistent calculation model (34011)
2016-05-30 15:14:55:474|-02:00|8|SYSTEM|Object: sap.hba.ecc.SpecialGLCodeValueHelp.calculationview ==> Error Code: 40117

 

As you can see, I have highlighted the tables which are failing to be found.

Checking the transaction SE11 you can see that these tables are existing in the system, so what is the problem? The next step is to check if the tables are in "TERMINATED" state, or "POOLED" state. These tables should be changed to "TRANSPARENT" state.

se14 --> <table name (ENTER)> --> Press "Continue adjustment".


Read more...

Keywords

KBA , HAN-LM-APP , SAP HANA Application Lifecycle Management , How To

About this page

This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP ONE Support launchpad (Login required).

Search for additional results

Visit SAP Support Portal's SAP Notes and KBA Search.