Now you can map the hostname with required IP address on client machine to connect to the database:Ĭhanges can be observed again with studio again. Note: This change does not required a DB restart. Instead you can map the hostname to required IP address as required. To change the behaviour you will have to change the parameter to “no” so that system is not forced anymore to use IP address of the Network interface.
The users are possible to be SAPABAP1, SAPHANADB, SAPSR3 or SAPThis behaviour is controlled by parameter “public_hostname_resolution” under global.ini. Your SAP schema user is locked due to too many times failed log on attempt. You can also verify the same by querying M_HOST_INFORMATION. In this case when you try to make connection to a tenant database via webdispatcher or sql clients you will not be able to communicate to tenant DB. If you check the properties of a tenant database from studio you will see the following:Įven though you connect to DB using NAT IP (10.253.80.9) it is internally redirected to original IP (10.249.28.20) to make additional connections. You must log in to the database user SAPHANADB and reset the. Same has been depicted below with an example of SAP HANA Studio. After installing HANA Studio, add a database, pay attention to select Teant Database. The main connection between NAT and the IP is established via DNS or a local entry in local host file.īut internally SAP HANA tries to make a connection to the Tenant DB using physical IP by default. There are scenarios where you do not connect to SAP HANA database instance directly via Host IP address or Physical hostname but via a Virtual IP or NAT address.
0 kommentar(er)
