2169341 - Error: Java Class not found in classpath.1557665 - Database connection in Desktop Intellige.1868289 - Unable to start the BusinessObjects Ente.2211262 - Oracle Listener cannot be started.1626443 - PCM10: Failed to connect to Oracle datab.1822696 - Poor performance when reporting off an O.1670876 - Client Versions needed for Oracle 10.2 i.1206647 - Does Crystal Reports support Oracle TIME.
1738989 - Upgrade/Support Package import hang due.1980814 - No Oracle stored procedures listed in Cr.global . This is necessary for the initial installation and must be adjusted as described above. To check these settings, use the following SQL statements:įor distributed (multihost) systems, the default value is. SELECT * FROM "PUBLIC"."M_HOST_INFORMATION" WHERE KEY = 'net_publicname' To list the IP address marked as public, use the following SQL statement: With which the SAP HANA system is accessed from outside. The IP address xx.xx.xx.* must never be identical to the IP address In the example, the pattern xx.xx.xx.* represents the IP address of the internal network. The key is an IP address andįigure 1: Example settings for section - see attachment Otherwise, communication between hosts will not If the parameter listeninterface in section is set to The parameter listeninterface in section must be set to. local and must not be changed.Ī multihost SAP HANA production system must have a separate network for internal communication. SELECT * FROM "PUBLIC"."M_INIFILE_CONTENTS" WHERE SECTION = 'communication' AND KEY = 'listeninterface' įor single-host installations, the default value is . To check this setting, use the following SQL statement: In single-host systems, the listeninterface parameter in section must be set to. Them as described in the documents named below. Recommend checking these parameters and, if necessary, reconfiguring The following parameters in global.ini are important for a secure configuration:ĭepending on the setup of the SAP HANA system, we strongly If root privileges or SSH are notĪvailable, you can still perform network configuration as of revision 82īut you will need to use a host-by-host approach, also known asĭecentralized execution. In the Lifecycle Management chapter ("Configuring SAP HANA Do not change the parameters manually but follow one of the procedures described in the SAP HANA Administration Guide, Necessary to configure the settings for internal service communication To avoid opening an attack vector in an SAP HANA system, it is Secure Network Settings for Internal SAP HANA Services
0 kommentar(er)
