Uploaded image for project: 'Solution Center'
  1. Solution Center
  2. SOL-146

Clients and fail safety

    XMLWordPrintable

    Details

    • Type: Explanation
    • Status: Published
    • Affects Version/s: EXASolution 4.2.0, EXASolution 5.0
    • Fix Version/s: None
    • Component/s: ADO.NET, Client SDK, EXAplus, JDBC, ODBC
    • Labels:
      None
    • Explanation:
      Hide

      Automatic reconnect

      In case the database is not available or temporarily shut down, client connections to this database are terminated. The interfaces have the ability to automatically reconnect to the system.

      • JDBC driver, ADO.NET driver, ODBC driver, Client SDK:
        The driver tries to get a new connection to the same session. If a transaction was open they get an error like "Successfully reconnected, transaction was rolled back"
      • EXAplus
        EXAplus connects to EXASolution via JDBC and uses therefore all the provided functionality.

      Connection IP

      All the active EXASolution nodes can accept client connections. You can provide the most EXASolution drivers and EXAplus with a connection string, which contains all possible hosts including the stand by one.

      • EXAplus:
        Connection string will be provided via "-c" parameter in the console version and via the field "Connection string" in the graphical version
      • JDBC driver
        In the connection string, you can replace "Host:Port" with the list of all possible hosts and ports.
      • ODBC driver
        The driver accept the host list instead of the host parameter in the DSN configuration.
      • EXA-CLI
        The function EXAServerConnect accepts now a extended connection string, containing hosts and ports
      • ADO.NET driver
        The parameter "host" or "server" can contain a connection string similar to other interfaces (a node list or range and a port).

      The connection string contains for a 4 +1 -node cluster for example following data:

      192.168.0.2..6:8563
      

      Note that the connect time will increase if the host specified does not have an EXA node running on them.

      If the reconnect was not successful you can get one of the SQL states 40004, 40009, 40018, 40020. If it was successful and the transaction was rolled back you can get one of the SQL states: 40001, 40002, 40003, 40005, 40007, 40008, 40010, 40011, 40017, 40019. If the connection was completely lost you get the SQL state 08001.

      Show
      Automatic reconnect In case the database is not available or temporarily shut down, client connections to this database are terminated. The interfaces have the ability to automatically reconnect to the system. JDBC driver, ADO.NET driver, ODBC driver, Client SDK: The driver tries to get a new connection to the same session. If a transaction was open they get an error like "Successfully reconnected, transaction was rolled back" EXAplus EXAplus connects to EXASolution via JDBC and uses therefore all the provided functionality. Connection IP All the active EXASolution nodes can accept client connections. You can provide the most EXASolution drivers and EXAplus with a connection string, which contains all possible hosts including the stand by one. EXAplus: Connection string will be provided via "-c" parameter in the console version and via the field "Connection string" in the graphical version JDBC driver In the connection string, you can replace "Host:Port" with the list of all possible hosts and ports. ODBC driver The driver accept the host list instead of the host parameter in the DSN configuration. EXA-CLI The function EXAServerConnect accepts now a extended connection string, containing hosts and ports ADO.NET driver The parameter "host" or "server" can contain a connection string similar to other interfaces (a node list or range and a port). The connection string contains for a 4 +1 -node cluster for example following data: 192.168.0.2..6:8563 Note that the connect time will increase if the host specified does not have an EXA node running on them. If the reconnect was not successful you can get one of the SQL states 40004, 40009, 40018, 40020. If it was successful and the transaction was rolled back you can get one of the SQL states: 40001, 40002, 40003, 40005, 40007, 40008, 40010, 40011, 40017, 40019. If the connection was completely lost you get the SQL state 08001.
    • Category 1:
      Clients, Interfaces & Drivers

      Attachments

        Activity

          People

          • Assignee:
            CaptainEXA Captain EXASOL
            Reporter:
            CaptainEXA Captain EXASOL
          • Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

            • Created:
              Updated: