SQLException in IS server logs due to OUTPUT parameter issue

, ,
1

Hi Team,

Whenever the BPM IS tries to start there is a 10 minutes delay at regular intervals not sure what is causing this error.
[i]
2020-03-03 22:36:23 UTC [CommonLib.MWS.0002W] Found inactive subscription 175. Check time: 1583267783767
2020-03-03 22:46:09 UTC [BPM.0101.0002E] Exception: java.sql.SQLException
2020-03-03 22:46:09 UTC [BPM.0101.0512E] Storage exception: [SoftwareAG][SQLServer JDBC Driver][SQLServer]The formal parameter “@p_failedNotEscalated” was not declared as an OUTPUT parameter, but the actual parameter passed in requested output.

Continuous logs after start of IS

2020-03-03 00:22:39 UTC [BPM.0101.0002E] Exception: java.sql.SQLException
2020-03-03 00:22:39 UTC [BPM.0101.0512E] Storage exception: [SoftwareAG][SQLServer JDBC Driver][SQLServer]The formal parameter “@p_failedNotEscalated” was not declared as an OUTPUT parameter, but the actual parameter passed in requested output.
2020-03-03 00:32:39 UTC [BPM.0101.0002E] Exception: java.sql.SQLException
2020-03-03 00:32:39 UTC [BPM.0101.0512E] Storage exception: [SoftwareAG][SQLServer JDBC Driver][SQLServer]The formal parameter “@p_failedNotEscalated” was not declared as an OUTPUT parameter, but the actual parameter passed in requested output.
2020-03-03 00:42:39 UTC [BPM.0101.0002E] Exception: java.sql.SQLEx[/i]

[code]

Before throwing this error it waits for 10 minutes, might be retrying something.

let me know what is causing this issue. So that this delay can be avoided.

Thanks in advance.

2

I think you are missing some PRT and DCC fixes.

What is your IS version and fix levels?

1 Like
3

Hi Mahesh,

Below are the details of fixes available -

Database Configuration
DC_9.12_DBS_Fix20 9.12.0.0020-0078
DC_9.12_EmbeddedDBS_Fix20 9.12.0.0020-0078

For WmPRT, there is no fix installed at the moment. Might be installing latest fix will solve this issue.

Appreciate your response. Just let me know if we continue this way as-is with that error in server log, will that cause any problem.

Application went live last week till now no issues reported so far… it is just that during deployment it is taking time and I want to avoid that.

4

Hi Firoz,

You can continue as-is if it is not impacting the live business processes but as a best practice it is recommended to install the latest fixes on the lower environments, test it (regression) and then promote the fix levels. Please review the fix readme if you really need those fix levels.

Did you upgrade this IS which is hosting the BPM?

5

Mahesh,

Yes IS is upgraded.

I observed today in the lower enviornments I don’t see that alert.

Fixes are same in lower environments and Production for DCC and PRT.

Any other thing which might be causing the issue in Production/DR alone.

6

Have you checked all your schema versions by launching database configurator ? There might be a chance that you have updated the fix level in Update Manager, but neglected upgrading the database by execute action “migrate” in dbcc. Most of the time people tend to forgot to do so.

1 Like