cancel
Showing results for 
Search instead for 
Did you mean: 

Issue with debugging of catalog schemas procedure

dmitri_marinin
Explorer
0 Kudos

Hi all,

we’ve encountered an issue with debugging of catalog schemas procedure. We create a sample procedure in Development system:

PROCEDURE "SAPEMP"."D00_DS_GENERAL.TEST::DEBUG_TEST" ( out output INTEGER )

       LANGUAGE SQLSCRIPT

       SQL SECURITY INVOKER

       --DEFAULT SCHEMA <default_schema_name>

       READS SQL DATA AS

BEGIN

/*****************************

       Write your procedure logic

*****************************/

DECLARE v int := 2;

output:= v;

END;

Then we debug it using catalog schemas procedure debugging:

Debugger works fine:

Then we transport procedure to Quality system, and debug it in the same way:

Debugger returns an error message:

  1. eclipse.buildId=unknown
  2. java.version=1.7.0_60
  3. java.vendor=Oracle Corporation

BootLoader constants: OS=win32, ARCH=x86_64, WS=win32, NL=ru_RU

Command-line arguments:  -os win32 -ws win32 -arch x86_64

  1. com.sap.ndb.studio.sqlscript.debugger.core

Error

Command response parse failed

  1. java.lang.NumberFormatException: For input string: "72057594038612108"

            at java.lang.NumberFormatException.forInputString(Unknown Source)

            at java.lang.Integer.parseInt(Unknown Source)

            at java.lang.Integer.parseInt(Unknown Source)

            at com.sap.ndb.studio.sqlscript.debugger.core.model.Parser.parseCompileForDebugRsources(Parser.java:1220)

            at com.sap.ndb.studio.sqlscript.debugger.core.model.Parser.compileForDebug(Parser.java:1168)

            at com.sap.ndb.studio.sqlscript.debugger.core.model.Parser.commandParser(Parser.java:206)

            at com.sap.ndb.studio.sqlscript.debugger.core.model.Parser.handleResponse(Parser.java:127)

            at com.sap.ndb.studio.sqlscript.debugger.core.model.Parser.parseMessage(Parser.java:92)

            at com.sap.ndb.studio.sqlscript.debugger.core.model.SQLScriptDbgSessionManager.handleResponse(SQLScriptDbgSessionManager.java:467)

            at com.sap.ndb.studio.sqlscript.debugger.core.model.SQLScriptDbgSessionManager.compileForDebug(SQLScriptDbgSessionManager.java:1451)

            at com.sap.ndb.studio.sqlscript.debugger.core.model.SQLScriptDbgSessionManager.startDebug(SQLScriptDbgSessionManager.java:263)

            at com.sap.ndb.studio.sqlscript.debugger.core.model.SQLScriptDbgDebugTarget.init(SQLScriptDbgDebugTarget.java:116)

            at com.sap.ndb.studio.sqlscript.debugger.core.launching.SQLScriptDbgLaunchDelegate.launch(SQLScriptDbgLaunchDelegate.java:105)

            at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:883)

            at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:739)

            at org.eclipse.debug.internal.ui.DebugUIPlugin.buildAndLaunch(DebugUIPlugin.java:1039)

            at org.eclipse.debug.internal.ui.DebugUIPlugin$8.run(DebugUIPlugin.java:1256)

            at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)


Quality and Development systems have the same HANA version: 1.00.85.03.400544. SAP HANA studio different versions return the same error (1.00.85.0 and 2.0.13 versions).

Regards,

Dmitry.

Accepted Solutions (1)

Accepted Solutions (1)

dmitri_marinin
Explorer
0 Kudos

Hi all,

this issue is fixed in Revision 100 for SAP HANA STUDIO 2 (Version: 2.1.4).

Regards,

Dmitry.

Answers (0)