Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Can't run IBM iSeries (AS400) Stored Procedure calls in DBeaver 22.1.0 but can run them in 6.2.0 #17391

Closed
EricWagnerJr opened this issue Aug 18, 2022 · 7 comments · Fixed by #17540

Comments

@EricWagnerJr
Copy link

EricWagnerJr commented Aug 18, 2022

Description

Doing a proof of concept for DBeaver Lite - I can run stored procedures in 6.2.0 using the jtopen (jt400.jar) driver. I can also run select statements against it using 22.1.0, but I can't run stored procedures.

Example Call: "CALL SOMESCHEMA.SOMEPROCEDURE('EA', ?, ?);"

Configs:
image
image
image
image

Logs:

!ENTRY org.jkiss.dbeaver.model 4 0 2022-08-18 14:27:22.000
!MESSAGE Error executing query
!SUBENTRY 1 org.jkiss.dbeaver.model 4 0 2022-08-18 14:27:22.000
!MESSAGE 
!SUBENTRY 2 org.jkiss.dbeaver.model 4 0 2022-08-18 14:27:22.000
!MESSAGE DBException
!STACK 0
org.jkiss.dbeaver.DBException
	at org.jkiss.dbeaver.model.exec.DBExecUtils.tryExecuteRecover(DBExecUtils.java:231)
	at org.jkiss.dbeaver.ui.editors.sql.execute.SQLQueryJob.executeSingleQuery(SQLQueryJob.java:491)
	at org.jkiss.dbeaver.ui.editors.sql.execute.SQLQueryJob.extractData(SQLQueryJob.java:878)
	at org.jkiss.dbeaver.ui.editors.sql.SQLEditor$QueryResultsContainer.readData(SQLEditor.java:3526)
	at org.jkiss.dbeaver.ui.controls.resultset.ResultSetJobDataRead.lambda$0(ResultSetJobDataRead.java:118)
	at org.jkiss.dbeaver.model.exec.DBExecUtils.tryExecuteRecover(DBExecUtils.java:172)
	at org.jkiss.dbeaver.ui.controls.resultset.ResultSetJobDataRead.run(ResultSetJobDataRead.java:116)
	at org.jkiss.dbeaver.ui.controls.resultset.ResultSetViewer$ResultSetDataPumpJob.run(ResultSetViewer.java:4868)
	at org.jkiss.dbeaver.model.runtime.AbstractJob.run(AbstractJob.java:105)
	at org.eclipse.core.internal.jobs.Worker.run(Worker.java:63)
Caused by: java.lang.NullPointerException
	at org.jkiss.dbeaver.model.impl.jdbc.exec.JDBCCallableStatementImpl.getOutputParametersFromMeta(JDBCCallableStatementImpl.java:288)
	at org.jkiss.dbeaver.model.impl.jdbc.exec.JDBCCallableStatementImpl.<init>(JDBCCallableStatementImpl.java:114)
	at org.jkiss.dbeaver.model.impl.jdbc.exec.JDBCFactoryDefault.createCallableStatement(JDBCFactoryDefault.java:48)
	at org.jkiss.dbeaver.model.impl.jdbc.exec.JDBCConnectionImpl.createCallableStatementImpl(JDBCConnectionImpl.java:730)
	at org.jkiss.dbeaver.model.impl.jdbc.exec.JDBCConnectionImpl.prepareCall(JDBCConnectionImpl.java:415)
	at org.jkiss.dbeaver.model.impl.jdbc.exec.JDBCConnectionImpl.prepareStatement(JDBCConnectionImpl.java:102)
	at org.jkiss.dbeaver.model.impl.jdbc.exec.JDBCConnectionImpl.prepareStatement(JDBCConnectionImpl.java:1)
	at org.jkiss.dbeaver.model.DBUtils.createStatement(DBUtils.java:1330)
	at org.jkiss.dbeaver.model.DBUtils.makeStatement(DBUtils.java:1298)
	at org.jkiss.dbeaver.ui.editors.sql.execute.SQLQueryJob.executeStatement(SQLQueryJob.java:551)
	at org.jkiss.dbeaver.ui.editors.sql.execute.SQLQueryJob.lambda$1(SQLQueryJob.java:484)
	at org.jkiss.dbeaver.model.exec.DBExecUtils.tryExecuteRecover(DBExecUtils.java:172)
	... 9 more
!SUBENTRY 3 org.jkiss.dbeaver.model 4 0 2022-08-18 14:27:22.000
!MESSAGE NullPointerException
!STACK 0
java.lang.NullPointerException
	at org.jkiss.dbeaver.model.impl.jdbc.exec.JDBCCallableStatementImpl.getOutputParametersFromMeta(JDBCCallableStatementImpl.java:288)
	at org.jkiss.dbeaver.model.impl.jdbc.exec.JDBCCallableStatementImpl.<init>(JDBCCallableStatementImpl.java:114)
	at org.jkiss.dbeaver.model.impl.jdbc.exec.JDBCFactoryDefault.createCallableStatement(JDBCFactoryDefault.java:48)
	at org.jkiss.dbeaver.model.impl.jdbc.exec.JDBCConnectionImpl.createCallableStatementImpl(JDBCConnectionImpl.java:730)
	at org.jkiss.dbeaver.model.impl.jdbc.exec.JDBCConnectionImpl.prepareCall(JDBCConnectionImpl.java:415)
	at org.jkiss.dbeaver.model.impl.jdbc.exec.JDBCConnectionImpl.prepareStatement(JDBCConnectionImpl.java:102)
	at org.jkiss.dbeaver.model.impl.jdbc.exec.JDBCConnectionImpl.prepareStatement(JDBCConnectionImpl.java:1)
	at org.jkiss.dbeaver.model.DBUtils.createStatement(DBUtils.java:1330)
	at org.jkiss.dbeaver.model.DBUtils.makeStatement(DBUtils.java:1298)
	at org.jkiss.dbeaver.ui.editors.sql.execute.SQLQueryJob.executeStatement(SQLQueryJob.java:551)
	at org.jkiss.dbeaver.ui.editors.sql.execute.SQLQueryJob.lambda$1(SQLQueryJob.java:484)
	at org.jkiss.dbeaver.model.exec.DBExecUtils.tryExecuteRecover(DBExecUtils.java:172)
	at org.jkiss.dbeaver.ui.editors.sql.execute.SQLQueryJob.executeSingleQuery(SQLQueryJob.java:491)
	at org.jkiss.dbeaver.ui.editors.sql.execute.SQLQueryJob.extractData(SQLQueryJob.java:878)
	at org.jkiss.dbeaver.ui.editors.sql.SQLEditor$QueryResultsContainer.readData(SQLEditor.java:3526)
	at org.jkiss.dbeaver.ui.controls.resultset.ResultSetJobDataRead.lambda$0(ResultSetJobDataRead.java:118)
	at org.jkiss.dbeaver.model.exec.DBExecUtils.tryExecuteRecover(DBExecUtils.java:172)
	at org.jkiss.dbeaver.ui.controls.resultset.ResultSetJobDataRead.run(ResultSetJobDataRead.java:116)
	at org.jkiss.dbeaver.ui.controls.resultset.ResultSetViewer$ResultSetDataPumpJob.run(ResultSetViewer.java:4868)
	at org.jkiss.dbeaver.model.runtime.AbstractJob.run(AbstractJob.java:105)
	at org.eclipse.core.internal.jobs.Worker.run(Worker.java:63)

DBeaver Version

DBeaver Lite (Trial) 22.1.0

Operating System

Windows 10

Database and driver

IBM iSeries (AS400) - using jt400.jar driver.

Steps to reproduce

No response

Additional context

No response

@LonwoLonwo
Copy link
Member

Hello @EricWagnerJr

Can you provide a procedure example DDL, please?

@EricWagnerJr
Copy link
Author

EricWagnerJr commented Sep 1, 2022

I'm not sure I am able to share that in this forum. I'm realizing you have a different portal on your site for submitting tech support requests. I think I may need to pivot to there.

Update: I did submit a ticket separately there so we could possibly schedule a call.

@LonwoLonwo
Copy link
Member

So it means that only one stored procedure doesn't work? Not all? Or maybe you can find a sample procedure?

n5a5 added a commit that referenced this issue Sep 2, 2022
n5a5 added a commit that referenced this issue Sep 2, 2022
@n5a5 n5a5 linked a pull request Sep 2, 2022 that will close this issue
@n5a5 n5a5 added this to the 22.2.0 milestone Sep 2, 2022
serge-rider pushed a commit that referenced this issue Sep 2, 2022
Co-authored-by: Nikita Akilov <26031301+akilovich@users.noreply.github.com>
@EricWagnerJr
Copy link
Author

EricWagnerJr commented Sep 2, 2022

No, it is all stored procedures failing. I can't share my companies SPs in a public forum I'm realizing so we will have to take this private over the internal ticketing system.

@n5a5
Copy link
Member

n5a5 commented Sep 2, 2022

@EricWagnerJr Please check out my message on our ticket system, thanks

@EricWagnerJr
Copy link
Author

This fixed the issue @n5a5, thank you.

@n5a5
Copy link
Member

n5a5 commented Sep 2, 2022

@EricWagnerJr My pleasure!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants