[
https://issues.apache.org/jira/browse/IGNITE-1993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15055849#comment-15055849
]
Nigel Westbury commented on IGNITE-1993:
----------------------------------------
Sorry, I must have missed that change when moving the changes across to the
forked repository. The 'if not exists' should of course have been removed, as
that was the whole point of the fix. Our test team here have tested the
product on Oracle and they did not create the table, so I am confident the code
works. However the code they tested was not built from the github fork hence
the error you found due to the missed change was not picked up by our testing.
> JDBC discovery uses non-standard SQL when creating table (not compatible with
> Oracle)
> -------------------------------------------------------------------------------------
>
> Key: IGNITE-1993
> URL: https://issues.apache.org/jira/browse/IGNITE-1993
> Project: Ignite
> Issue Type: Bug
> Components: SQL
> Affects Versions: ignite-1.4
> Environment: Oracle database
> Reporter: Nigel Westbury
> Labels: easyfix, patch
> Fix For: 1.4
>
> Attachments: IGNITE1993.patch
>
>
> The SQL used by TcpDiscoveryJdbcIpFinder to create the table (defined by
> CREATE_ADDRS_TABLE_QRY) uses 'if not exists' clause. However this clause is
> not supported by Oracle and causes SQLSyntaxErrorException: "ORA-00922:
> missing or invalid option" to be thrown. This prevents JDBC discovery from
> being used with an Oracle database.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
