Skip to Content

Sometimes you may get a connection error when converting a table to
extended storage:

 

ALTER TABLE “DT_SCHEMA”.”TABLE_A” USING EXTENDED STORAGE;

[4863] {207439} [95/10731633] 2016-05-06 17:50:26.455132 e FedTrace

odbcaccess.cpp(03672) : ODBC error: connected:  1 state: HY000 cide: -65 [SAP]

[ODBC Driver] Unable to connect to server ‘HANA’: [SAP AG] [LIBODBCHDB SO] [ HDBODBC]

General error;1033 error while parsing protocol

This error happens on multi-host systems if the time on the dynamic tiering host is not synchronized with that of the HANA hosts.  The error means that that the dynamic tiering host couldn’t communicate with SAP HANA to fetch the contents of the table required for the conversion.

 

Check for Different Certificate Sizes

 

Certificate sizes on the dynamic tiering and SAP HANA hosts should match. Certificate mutual authentication and the SSL protocol secure internal communications between the hosts. Different certificate sizes cause an initial connection failure from SAP HANA to dynamiic tiering with the error [SAP][ODBC Driver]TLS handshake failure SQLSTATE:HY000.

 

Log in as SIDadm on the dynamic tiering host and enter these commands to compare certificate sizes:

  1. cd $SECUDIR
  2. ls -al sap_system_pki_instance.*

Note the file sizes. The file sizes should match those on the HANA host.

 

Log in as SIDadm on the SAP HANA host and enter these commands:

  1. cd $SECUDIR
  2. ls -al sap_system_pki_instance.*

Do the file sizes match those on the dynamic tiering host?

 

For these certificates to work correctly, you need to synchronize the clocks on the SAP HANA and dynamic tiering hosts. Run the date command on each host.

To report this post you need to login first.

Be the first to leave a comment

You must be Logged on to comment or reply to a post.

Leave a Reply