After restarting DB2 service, the application server gets ERRORCODE=-4499, SQLSTATE=58009 in database...
We have an application on IBM WebSphere Application Server 7.x and it connects to a remote database on z/os DB2 10.x. For annual operation, DB2 shut down and restarted. After starting the database, we first get
com.ibm.websphere.ce.cm.StaleConnectionException
and then we get
The database manager is not able to accept new requests, has terminated all requests in progress, or has terminated this particular request due to unexpected error conditions detected at the target system. ERRORCODE=-4499, SQLSTATE=58009
The connection between WebSphere and DB2 tested by 'test Connection' in WAS datasource. Both systems are up and running but there is no correct connection between them! There was no change in DB2, WAS, and JDBC driver.
Update: The JDBC driver version is 4.15.134, connection properties is IBM WebSphere default setting and the connection is direct to DB2. Another problem later showed that while the connection still has the problem, executing the query directly on z/OS's DB2 gets the same the error. The query consist of a select with a join on two different tables, selecting on each table is ok, but the final query does not work and gets ERRORCODE=-4499, SQLSTATE=58009.
Update 2
The detail of environment is: IBM WebSphere Application Server 7.0.0.45, DB2 10.1, Java version 1.6 SR16 and z/OS 1.13.
This specific query gets the error in all environments, on all application server, z/os SPUFI, database viewer, such as DBeaver.
Any help is greatly appreciated.
db2 websphere database-connection
asked Nov 23 '18 at 20:09
Ehsan MoradiEhsan Moradi
367
add a comment |
We have an application on IBM WebSphere Application Server 7.x and it connects to a remote database on z/os DB2 10.x. For annual operation, DB2 shut down and restarted. After starting the database, we first get
com.ibm.websphere.ce.cm.StaleConnectionException
and then we get
The database manager is not able to accept new requests, has terminated all requests in progress, or has terminated this particular request due to unexpected error conditions detected at the target system. ERRORCODE=-4499, SQLSTATE=58009
The connection between WebSphere and DB2 tested by 'test Connection' in WAS datasource. Both systems are up and running but there is no correct connection between them! There was no change in DB2, WAS, and JDBC driver.
Update: The JDBC driver version is 4.15.134, connection properties is IBM WebSphere default setting and the connection is direct to DB2. Another problem later showed that while the connection still has the problem, executing the query directly on z/OS's DB2 gets the same the error. The query consist of a select with a join on two different tables, selecting on each table is ok, but the final query does not work and gets ERRORCODE=-4499, SQLSTATE=58009.
Update 2
The detail of environment is: IBM WebSphere Application Server 7.0.0.45, DB2 10.1, Java version 1.6 SR16 and z/OS 1.13.
This specific query gets the error in all environments, on all application server, z/os SPUFI, database viewer, such as DBeaver.
Any help is greatly appreciated.
db2 websphere database-connection
asked Nov 23 '18 at 20:09
Ehsan MoradiEhsan Moradi
367
This question is not about programming. It is better to ask this question on dba.stackexchange.com and most likely you should specify the jdbc-driver version, the connection properties, and whether direct-connection or Db2-connect is involved.
– mao
Nov 24 '18 at 11:28
You should also edit your question to specify the exact WAS version (7.x is not a specification). Since 30/April/2018, WAS 7 is no longer supported by IBM without an extended-support contract . If the versionInfo.sh tool of WAS does not show 7.0.0.45 then you should consider a migration plan. Additionally you should edit your question to state whether the issue happens with all environments or only one or some environments. Additionally specify the JVM version being used. All these basic facts can be relevant.
– mao
Nov 24 '18 at 16:35
Hi, we have a plan for migration to WAS 8.5.5.x, but not for the next few weeks. Environment details have been added to question.
– Ehsan Moradi
Nov 24 '18 at 18:02
add a comment |
We have an application on IBM WebSphere Application Server 7.x and it connects to a remote database on z/os DB2 10.x. For annual operation, DB2 shut down and restarted. After starting the database, we first get
com.ibm.websphere.ce.cm.StaleConnectionException
and then we get
The database manager is not able to accept new requests, has terminated all requests in progress, or has terminated this particular request due to unexpected error conditions detected at the target system. ERRORCODE=-4499, SQLSTATE=58009
The connection between WebSphere and DB2 tested by 'test Connection' in WAS datasource. Both systems are up and running but there is no correct connection between them! There was no change in DB2, WAS, and JDBC driver.
Update: The JDBC driver version is 4.15.134, connection properties is IBM WebSphere default setting and the connection is direct to DB2. Another problem later showed that while the connection still has the problem, executing the query directly on z/OS's DB2 gets the same the error. The query consist of a select with a join on two different tables, selecting on each table is ok, but the final query does not work and gets ERRORCODE=-4499, SQLSTATE=58009.
Update 2
The detail of environment is: IBM WebSphere Application Server 7.0.0.45, DB2 10.1, Java version 1.6 SR16 and z/OS 1.13.
This specific query gets the error in all environments, on all application server, z/os SPUFI, database viewer, such as DBeaver.
Any help is greatly appreciated.
db2 websphere database-connection
asked Nov 23 '18 at 20:09
Ehsan MoradiEhsan Moradi
367
We have an application on IBM WebSphere Application Server 7.x and it connects to a remote database on z/os DB2 10.x. For annual operation, DB2 shut down and restarted. After starting the database, we first get
com.ibm.websphere.ce.cm.StaleConnectionException
and then we get
The database manager is not able to accept new requests, has terminated all requests in progress, or has terminated this particular request due to unexpected error conditions detected at the target system. ERRORCODE=-4499, SQLSTATE=58009
The connection between WebSphere and DB2 tested by 'test Connection' in WAS datasource. Both systems are up and running but there is no correct connection between them! There was no change in DB2, WAS, and JDBC driver.
Update: The JDBC driver version is 4.15.134, connection properties is IBM WebSphere default setting and the connection is direct to DB2. Another problem later showed that while the connection still has the problem, executing the query directly on z/OS's DB2 gets the same the error. The query consist of a select with a join on two different tables, selecting on each table is ok, but the final query does not work and gets ERRORCODE=-4499, SQLSTATE=58009.
Update 2
The detail of environment is: IBM WebSphere Application Server 7.0.0.45, DB2 10.1, Java version 1.6 SR16 and z/OS 1.13.
This specific query gets the error in all environments, on all application server, z/os SPUFI, database viewer, such as DBeaver.
Any help is greatly appreciated.
db2 websphere database-connection
db2 websphere database-connection
asked Nov 23 '18 at 20:09
Ehsan MoradiEhsan Moradi
367
asked Nov 23 '18 at 20:09
Ehsan MoradiEhsan Moradi
367
edited Nov 24 '18 at 18:00
Ehsan Moradi
asked Nov 23 '18 at 20:09
Ehsan MoradiEhsan Moradi
367
asked Nov 23 '18 at 20:09
Ehsan MoradiEhsan Moradi
367
asked Nov 23 '18 at 20:09
Ehsan MoradiEhsan Moradi
367
367
This question is not about programming. It is better to ask this question on dba.stackexchange.com and most likely you should specify the jdbc-driver version, the connection properties, and whether direct-connection or Db2-connect is involved.
– mao
Nov 24 '18 at 11:28
You should also edit your question to specify the exact WAS version (7.x is not a specification). Since 30/April/2018, WAS 7 is no longer supported by IBM without an extended-support contract . If the versionInfo.sh tool of WAS does not show 7.0.0.45 then you should consider a migration plan. Additionally you should edit your question to state whether the issue happens with all environments or only one or some environments. Additionally specify the JVM version being used. All these basic facts can be relevant.
– mao
Nov 24 '18 at 16:35
Hi, we have a plan for migration to WAS 8.5.5.x, but not for the next few weeks. Environment details have been added to question.
– Ehsan Moradi
Nov 24 '18 at 18:02
add a comment |
This question is not about programming. It is better to ask this question on dba.stackexchange.com and most likely you should specify the jdbc-driver version, the connection properties, and whether direct-connection or Db2-connect is involved.
– mao
Nov 24 '18 at 11:28
You should also edit your question to specify the exact WAS version (7.x is not a specification). Since 30/April/2018, WAS 7 is no longer supported by IBM without an extended-support contract . If the versionInfo.sh tool of WAS does not show 7.0.0.45 then you should consider a migration plan. Additionally you should edit your question to state whether the issue happens with all environments or only one or some environments. Additionally specify the JVM version being used. All these basic facts can be relevant.
– mao
Nov 24 '18 at 16:35
Hi, we have a plan for migration to WAS 8.5.5.x, but not for the next few weeks. Environment details have been added to question.
– Ehsan Moradi
Nov 24 '18 at 18:02
This question is not about programming. It is better to ask this question on dba.stackexchange.com and most likely you should specify the jdbc-driver version, the connection properties, and whether direct-connection or Db2-connect is involved.
– mao
Nov 24 '18 at 11:28
This question is not about programming. It is better to ask this question on dba.stackexchange.com and most likely you should specify the jdbc-driver version, the connection properties, and whether direct-connection or Db2-connect is involved.
– mao
Nov 24 '18 at 11:28
You should also edit your question to specify the exact WAS version (7.x is not a specification). Since 30/April/2018, WAS 7 is no longer supported by IBM without an extended-support contract . If the versionInfo.sh tool of WAS does not show 7.0.0.45 then you should consider a migration plan. Additionally you should edit your question to state whether the issue happens with all environments or only one or some environments. Additionally specify the JVM version being used. All these basic facts can be relevant.
– mao
Nov 24 '18 at 16:35
You should also edit your question to specify the exact WAS version (7.x is not a specification). Since 30/April/2018, WAS 7 is no longer supported by IBM without an extended-support contract . If the versionInfo.sh tool of WAS does not show 7.0.0.45 then you should consider a migration plan. Additionally you should edit your question to state whether the issue happens with all environments or only one or some environments. Additionally specify the JVM version being used. All these basic facts can be relevant.
– mao
Nov 24 '18 at 16:35
Hi, we have a plan for migration to WAS 8.5.5.x, but not for the next few weeks. Environment details have been added to question.
– Ehsan Moradi
Nov 24 '18 at 18:02
Hi, we have a plan for migration to WAS 8.5.5.x, but not for the next few weeks. Environment details have been added to question.
– Ehsan Moradi
Nov 24 '18 at 18:02
add a comment |
2 Answers
2
active
oldest
votes
Finally, we found the solution, ran REORG and RUNSTATS on both tables and on all their partitions, and the error vanished both on the application and SPUFI. I guess something went wrong during restart and tables corrupted. Now everything is ok.
answered Nov 25 '18 at 7:18
Ehsan MoradiEhsan Moradi
367
add a comment |
If I got you correctly, you complain on inability of the driver to reestablish the database connections after the DB2 for Z/OS restart.
If yes, then have you tried to set the corresponding connection properties described at the following link?
Configuration of Sysplex workload balancing and automatic client reroute for Java clients
answered Nov 24 '18 at 12:10
Mark BarinsteinMark Barinstein
1,821114
Hi, I've updated the question. The link between the application server and DB2 seems ok but the connection returns the error. Another problem is executing query directly in DB2 get the same error.
– Ehsan Moradi
Nov 24 '18 at 13:54
Very vague description of the problem. “Link seems ok” - does it mean that a test connection is successful? Did the query with join work before the database restart? “Executing query directly” - where do you issue the query from? What exact error codes and messages you get when you run it using some non-jdbc tools?
– Mark Barinstein
Nov 24 '18 at 15:15
Yes, as mentioned in the question, the test connection is successful. Before restarting the DB2, the application works fine, also the query. Other queries functioning well. Our operator executes the query in the database in IBM Spufi and gets exactly the same error code and sqlstate.
– Ehsan Moradi
Nov 24 '18 at 15:24
Then something has changed. If a valid query in SPUFI worked fine before, but returns -4499 (sqlstate 58009) after a subsystem bounce, then your Z/DBA should open a PMR with IBM if she/he cannot see what's different. Sometimes thing are not what they appear to be, and often not what they are claimed to be.
– mao
Nov 24 '18 at 17:12
I did not run the query in recent weeks, but as I remember it workes in SPUFI, application and database viewer apps before. The DBA claims there is no change happened, only restart the system for maintenance. I am out of idea!
– Ehsan Moradi
Nov 24 '18 at 18:08
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53452440%2fafter-restarting-db2-service-the-application-server-gets-errorcode-4499-sqlst%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
Finally, we found the solution, ran REORG and RUNSTATS on both tables and on all their partitions, and the error vanished both on the application and SPUFI. I guess something went wrong during restart and tables corrupted. Now everything is ok.
answered Nov 25 '18 at 7:18
Ehsan MoradiEhsan Moradi
367
add a comment |
Finally, we found the solution, ran REORG and RUNSTATS on both tables and on all their partitions, and the error vanished both on the application and SPUFI. I guess something went wrong during restart and tables corrupted. Now everything is ok.
answered Nov 25 '18 at 7:18
Ehsan MoradiEhsan Moradi
367
add a comment |
Finally, we found the solution, ran REORG and RUNSTATS on both tables and on all their partitions, and the error vanished both on the application and SPUFI. I guess something went wrong during restart and tables corrupted. Now everything is ok.
answered Nov 25 '18 at 7:18
Ehsan MoradiEhsan Moradi
367
Finally, we found the solution, ran REORG and RUNSTATS on both tables and on all their partitions, and the error vanished both on the application and SPUFI. I guess something went wrong during restart and tables corrupted. Now everything is ok.
answered Nov 25 '18 at 7:18
Ehsan MoradiEhsan Moradi
367
edited Nov 25 '18 at 11:02
answered Nov 25 '18 at 7:18
Ehsan MoradiEhsan Moradi
367
answered Nov 25 '18 at 7:18
Ehsan MoradiEhsan Moradi
367
answered Nov 25 '18 at 7:18
Ehsan MoradiEhsan Moradi
367
367
add a comment |
add a comment |
If I got you correctly, you complain on inability of the driver to reestablish the database connections after the DB2 for Z/OS restart.
If yes, then have you tried to set the corresponding connection properties described at the following link?
Configuration of Sysplex workload balancing and automatic client reroute for Java clients
answered Nov 24 '18 at 12:10
Mark BarinsteinMark Barinstein
1,821114
Hi, I've updated the question. The link between the application server and DB2 seems ok but the connection returns the error. Another problem is executing query directly in DB2 get the same error.
– Ehsan Moradi
Nov 24 '18 at 13:54
Very vague description of the problem. “Link seems ok” - does it mean that a test connection is successful? Did the query with join work before the database restart? “Executing query directly” - where do you issue the query from? What exact error codes and messages you get when you run it using some non-jdbc tools?
– Mark Barinstein
Nov 24 '18 at 15:15
Yes, as mentioned in the question, the test connection is successful. Before restarting the DB2, the application works fine, also the query. Other queries functioning well. Our operator executes the query in the database in IBM Spufi and gets exactly the same error code and sqlstate.
– Ehsan Moradi
Nov 24 '18 at 15:24
Then something has changed. If a valid query in SPUFI worked fine before, but returns -4499 (sqlstate 58009) after a subsystem bounce, then your Z/DBA should open a PMR with IBM if she/he cannot see what's different. Sometimes thing are not what they appear to be, and often not what they are claimed to be.
– mao
Nov 24 '18 at 17:12
I did not run the query in recent weeks, but as I remember it workes in SPUFI, application and database viewer apps before. The DBA claims there is no change happened, only restart the system for maintenance. I am out of idea!
– Ehsan Moradi
Nov 24 '18 at 18:08
add a comment |
If I got you correctly, you complain on inability of the driver to reestablish the database connections after the DB2 for Z/OS restart.
If yes, then have you tried to set the corresponding connection properties described at the following link?
Configuration of Sysplex workload balancing and automatic client reroute for Java clients
answered Nov 24 '18 at 12:10
Mark BarinsteinMark Barinstein
1,821114
Hi, I've updated the question. The link between the application server and DB2 seems ok but the connection returns the error. Another problem is executing query directly in DB2 get the same error.
– Ehsan Moradi
Nov 24 '18 at 13:54
Very vague description of the problem. “Link seems ok” - does it mean that a test connection is successful? Did the query with join work before the database restart? “Executing query directly” - where do you issue the query from? What exact error codes and messages you get when you run it using some non-jdbc tools?
– Mark Barinstein
Nov 24 '18 at 15:15
Yes, as mentioned in the question, the test connection is successful. Before restarting the DB2, the application works fine, also the query. Other queries functioning well. Our operator executes the query in the database in IBM Spufi and gets exactly the same error code and sqlstate.
– Ehsan Moradi
Nov 24 '18 at 15:24
Then something has changed. If a valid query in SPUFI worked fine before, but returns -4499 (sqlstate 58009) after a subsystem bounce, then your Z/DBA should open a PMR with IBM if she/he cannot see what's different. Sometimes thing are not what they appear to be, and often not what they are claimed to be.
– mao
Nov 24 '18 at 17:12
I did not run the query in recent weeks, but as I remember it workes in SPUFI, application and database viewer apps before. The DBA claims there is no change happened, only restart the system for maintenance. I am out of idea!
– Ehsan Moradi
Nov 24 '18 at 18:08
add a comment |
If I got you correctly, you complain on inability of the driver to reestablish the database connections after the DB2 for Z/OS restart.
If yes, then have you tried to set the corresponding connection properties described at the following link?
Configuration of Sysplex workload balancing and automatic client reroute for Java clients
answered Nov 24 '18 at 12:10
Mark BarinsteinMark Barinstein
1,821114
If I got you correctly, you complain on inability of the driver to reestablish the database connections after the DB2 for Z/OS restart.
If yes, then have you tried to set the corresponding connection properties described at the following link?
Configuration of Sysplex workload balancing and automatic client reroute for Java clients
answered Nov 24 '18 at 12:10
Mark BarinsteinMark Barinstein
1,821114
answered Nov 24 '18 at 12:10
Mark BarinsteinMark Barinstein
1,821114
answered Nov 24 '18 at 12:10
Mark BarinsteinMark Barinstein
1,821114
answered Nov 24 '18 at 12:10
Mark BarinsteinMark Barinstein
1,821114
1,821114
Hi, I've updated the question. The link between the application server and DB2 seems ok but the connection returns the error. Another problem is executing query directly in DB2 get the same error.
– Ehsan Moradi
Nov 24 '18 at 13:54
Very vague description of the problem. “Link seems ok” - does it mean that a test connection is successful? Did the query with join work before the database restart? “Executing query directly” - where do you issue the query from? What exact error codes and messages you get when you run it using some non-jdbc tools?
– Mark Barinstein
Nov 24 '18 at 15:15
Yes, as mentioned in the question, the test connection is successful. Before restarting the DB2, the application works fine, also the query. Other queries functioning well. Our operator executes the query in the database in IBM Spufi and gets exactly the same error code and sqlstate.
– Ehsan Moradi
Nov 24 '18 at 15:24
Then something has changed. If a valid query in SPUFI worked fine before, but returns -4499 (sqlstate 58009) after a subsystem bounce, then your Z/DBA should open a PMR with IBM if she/he cannot see what's different. Sometimes thing are not what they appear to be, and often not what they are claimed to be.
– mao
Nov 24 '18 at 17:12
I did not run the query in recent weeks, but as I remember it workes in SPUFI, application and database viewer apps before. The DBA claims there is no change happened, only restart the system for maintenance. I am out of idea!
– Ehsan Moradi
Nov 24 '18 at 18:08
add a comment |
Hi, I've updated the question. The link between the application server and DB2 seems ok but the connection returns the error. Another problem is executing query directly in DB2 get the same error.
– Ehsan Moradi
Nov 24 '18 at 13:54
Very vague description of the problem. “Link seems ok” - does it mean that a test connection is successful? Did the query with join work before the database restart? “Executing query directly” - where do you issue the query from? What exact error codes and messages you get when you run it using some non-jdbc tools?
– Mark Barinstein
Nov 24 '18 at 15:15
Yes, as mentioned in the question, the test connection is successful. Before restarting the DB2, the application works fine, also the query. Other queries functioning well. Our operator executes the query in the database in IBM Spufi and gets exactly the same error code and sqlstate.
– Ehsan Moradi
Nov 24 '18 at 15:24
Then something has changed. If a valid query in SPUFI worked fine before, but returns -4499 (sqlstate 58009) after a subsystem bounce, then your Z/DBA should open a PMR with IBM if she/he cannot see what's different. Sometimes thing are not what they appear to be, and often not what they are claimed to be.
– mao
Nov 24 '18 at 17:12
I did not run the query in recent weeks, but as I remember it workes in SPUFI, application and database viewer apps before. The DBA claims there is no change happened, only restart the system for maintenance. I am out of idea!
– Ehsan Moradi
Nov 24 '18 at 18:08
Hi, I've updated the question. The link between the application server and DB2 seems ok but the connection returns the error. Another problem is executing query directly in DB2 get the same error.
– Ehsan Moradi
Nov 24 '18 at 13:54
Hi, I've updated the question. The link between the application server and DB2 seems ok but the connection returns the error. Another problem is executing query directly in DB2 get the same error.
– Ehsan Moradi
Nov 24 '18 at 13:54
Very vague description of the problem. “Link seems ok” - does it mean that a test connection is successful? Did the query with join work before the database restart? “Executing query directly” - where do you issue the query from? What exact error codes and messages you get when you run it using some non-jdbc tools?
– Mark Barinstein
Nov 24 '18 at 15:15
Very vague description of the problem. “Link seems ok” - does it mean that a test connection is successful? Did the query with join work before the database restart? “Executing query directly” - where do you issue the query from? What exact error codes and messages you get when you run it using some non-jdbc tools?
– Mark Barinstein
Nov 24 '18 at 15:15
Yes, as mentioned in the question, the test connection is successful. Before restarting the DB2, the application works fine, also the query. Other queries functioning well. Our operator executes the query in the database in IBM Spufi and gets exactly the same error code and sqlstate.
– Ehsan Moradi
Nov 24 '18 at 15:24
Yes, as mentioned in the question, the test connection is successful. Before restarting the DB2, the application works fine, also the query. Other queries functioning well. Our operator executes the query in the database in IBM Spufi and gets exactly the same error code and sqlstate.
– Ehsan Moradi
Nov 24 '18 at 15:24
Then something has changed. If a valid query in SPUFI worked fine before, but returns -4499 (sqlstate 58009) after a subsystem bounce, then your Z/DBA should open a PMR with IBM if she/he cannot see what's different. Sometimes thing are not what they appear to be, and often not what they are claimed to be.
– mao
Nov 24 '18 at 17:12
Then something has changed. If a valid query in SPUFI worked fine before, but returns -4499 (sqlstate 58009) after a subsystem bounce, then your Z/DBA should open a PMR with IBM if she/he cannot see what's different. Sometimes thing are not what they appear to be, and often not what they are claimed to be.
– mao
Nov 24 '18 at 17:12
I did not run the query in recent weeks, but as I remember it workes in SPUFI, application and database viewer apps before. The DBA claims there is no change happened, only restart the system for maintenance. I am out of idea!
– Ehsan Moradi
Nov 24 '18 at 18:08
I did not run the query in recent weeks, but as I remember it workes in SPUFI, application and database viewer apps before. The DBA claims there is no change happened, only restart the system for maintenance. I am out of idea!
– Ehsan Moradi
Nov 24 '18 at 18:08
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53452440%2fafter-restarting-db2-service-the-application-server-gets-errorcode-4499-sqlst%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
This question is not about programming. It is better to ask this question on dba.stackexchange.com and most likely you should specify the jdbc-driver version, the connection properties, and whether direct-connection or Db2-connect is involved.
– mao
Nov 24 '18 at 11:28
You should also edit your question to specify the exact WAS version (7.x is not a specification). Since 30/April/2018, WAS 7 is no longer supported by IBM without an extended-support contract . If the versionInfo.sh tool of WAS does not show 7.0.0.45 then you should consider a migration plan. Additionally you should edit your question to state whether the issue happens with all environments or only one or some environments. Additionally specify the JVM version being used. All these basic facts can be relevant.
– mao
Nov 24 '18 at 16:35
Hi, we have a plan for migration to WAS 8.5.5.x, but not for the next few weeks. Environment details have been added to question.
– Ehsan Moradi
Nov 24 '18 at 18:02