Symptom
While you are running the Solution Manager Configuration, step
managed system setup, you are requested for a Hana Log path for an Abap
system which is running on top of Hana Database. This same path is
requested in the configuration of the system type Hana which corresponds
to this Database.
Hana Log path should not be requested for abap stack but only for system type Hana.
A further result of this correction is that for ABAP managed systems running on Hana the ConfigStores attached to the database (examples HDB_LEVEL and HDB_PARAMETER) will not show up anymore for both technical system types ABAP and HANADB but only for the Hana technical system itself. This may also affect the result of the configuration validation in case such a ConfigStore is used in a validation target system against a technical system of type ABAP.
Hana Log path should not be requested for abap stack but only for system type Hana.
A further result of this correction is that for ABAP managed systems running on Hana the ConfigStores attached to the database (examples HDB_LEVEL and HDB_PARAMETER) will not show up anymore for both technical system types ABAP and HANADB but only for the Hana technical system itself. This may also affect the result of the configuration validation in case such a ConfigStore is used in a validation target system against a technical system of type ABAP.
Other Terms
Hana, solution manager setup, Instance Log Path
Reason and Prerequisites
Hana Database is considered as a separate system type and related
configuration steps have to be clearly separated from the Abap system
one.
Solution
Please implement this note.
Header Data
| Released On | 05.02.2016 20:54:27 |
| Release Status | Released for Customer |
| Component | SV-SMG-DIA-APP-CA Change Analysis + Reporting, Configuration Validation, CCDB |
| Priority | Correction with medium priority |
| Category | Program error |
No comments:
Post a Comment