[
https://issues.apache.org/jira/browse/IGNITE-3035?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15250309#comment-15250309
]
Peter Griffiths commented on IGNITE-3035:
-----------------------------------------
The errors were happening as the dbm.getTables() call failed to determine the
table's existence due to the Oracle required upper case query. The system then
tried to create the IP table twice, but failed both times since it already
existed.
> Recent JDBC discovery changes cause errors for Postgres and Microsoft SQL
> Server databases
> ------------------------------------------------------------------------------------------
>
> Key: IGNITE-3035
> URL: https://issues.apache.org/jira/browse/IGNITE-3035
> Project: Ignite
> Issue Type: Bug
> Components: SQL
> Affects Versions: 1.6
> Reporter: Peter Griffiths
>
> The changes introduced by IGNITE-1993 to the TcpDiscoveryJdbcIpFinder class
> to introduce Oracle compatibility cause errors when Postgres or Microsoft SQL
> Server are used as the database. No such issues were encountered using
> either database before.
> The first node to join a grid succeeds and creates the IP table in the
> database, but any further node attempting to join the grid throws the
> following error (for Postgres):
> {code}
> Failed to register local node address in IP finder on start (retrying every
> 2000 ms).: class org.apache.ignite.spi.IgniteSpiException: Failed to
> initialize DB schema.
> ...
> Caused by: org.postgresql.util.PSQLException: ERROR: current transaction is
> aborted, commands ignored until end of transaction block
> {code}
> The same behaviour occurs when using Microsoft SQL Server, but it throws a
> different error.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
