org.netezza.error.NzSQLException

ERROR: 'set schema 'sor'' error ^ found "'" (at char 16) expecting `TO' or `'=''

Samebug tips0

There are no available Samebug tips for this exception. If you know how to solve this issue, help other users by writing a short tip.

Don't give up yet. Paste your full stack trace to get a solution.

Solutions on the web4

  • via Google Groups by Gagneet Singh, 6 months ago
    ERROR: 'set schema 'sor'' error ^ found "'" (at char 16) expecting `TO' or `'=''
  • via Google Groups by Pratibha Sharma, 1 year ago
    ERROR: 'select * as x from CTG_DWH..AGG_MOD_TY11 limit 0' error ^ found "AS" (at char 10) expecting a keyword
  • Stack trace

    • org.netezza.error.NzSQLException: ERROR: 'set schema 'sor'' error ^ found "'" (at char 16) expecting `TO' or `'='' at org.netezza.internal.QueryExecutor.getNextResult(QueryExecutor.java:276) at org.netezza.internal.QueryExecutor.execute(QueryExecutor.java:73) at org.netezza.sql.NzConnection.execute(NzConnection.java:2673) at org.netezza.sql.NzStatement._execute(NzStatement.java:849) at org.netezza.sql.NzPreparedStatament.execute(NzPreparedStatament.java:152) at dbfit.fixture.StatementExecution.run(StatementExecution.java:24) at dbfit.fixture.Execute.doRows(Execute.java:27) at fit.Fixture.doTable(Fixture.java:156) at fitlibrary.traverse.AlienTraverseHandler.doTable(AlienTraverseHandler.java:21) at fitlibrary.traverse.workflow.DoTraverseInterpreter.interpretWholeTable(DoTraverseInterpreter.java:104) at fitlibrary.traverse.workflow.DoTraverseInterpreter.interpretWholeTable(DoTraverseInterpreter.java:89) at fitlibrary.DoFixture.interpretWholeTable(DoFixture.java:73) at fitlibrary.suite.InFlowPageRunner.run(InFlowPageRunner.java:27) at fitlibrary.DoFixture.interpretTables(DoFixture.java:42) at dbfit.DatabaseTest.interpretTables(DatabaseTest.java:26) at fit.Fixture.doTables(Fixture.java:81) at fit.FitServer.process(FitServer.java:81) at fit.FitServer.run(FitServer.java:56) at fit.FitServer.main(FitServer.java:41)

    Write tip

    You have a different solution? A short tip here would help you and many other users who saw this issue last week.

    Users with the same issue

    You’re the first here who have seen this exception.