To whom this may concern
When issuing the runstats command the other day, DB2 Express-C returned the ubiquitous SQL22212 error message. Online help wasn't useful at all! Since the last successful runstats was issued on the 16th of November 2012, I decided to play back a system image, created on the 14th of November 2012, and try again. Surprise, surprise: SQL22212 came up again!
'If DB2 fails, then SQL Server may fail too' (IBM DB2 error info refers to TCP/IP addresses) I thought and checked SQL Server – absolutely no problems there, so TCP/IP can't be the culprit!
Looking further into DB2 Express-C behavior I found out that DB2 became more or less defunct - commands being rejected.
I have uninstalled DB2 Express-C until a viable solution is available and use Microsoft SQL Server instead. It came in very handy that I duplicated all DB2 databases on Microsoft SQL Server!
DB2 Express-C 9.n was installed on Windows 7 Ultimate 64 Bit SP1.
Has anybody come across this strange SQL22212 behavior and is there a solution one could share?
Any answer would be appreciated.
NOTICE: developerWorks Community will be offline May 29-30, 2015 while we upgrade to the latest version of IBM Connections. For more information, read our upgrade FAQ.
This topic has been locked.
1 reply Latest Post - 2012-12-14T13:37:17Z by SystemAdmin
Pinned topic SQL22212 Error
Answered question This question has been answered.
Unanswered question This question has not been answered yet.
Updated on 2012-12-14T13:37:17Z at 2012-12-14T13:37:17Z by SystemAdmin
SystemAdmin 110000D4XK5837 PostsACCEPTED ANSWER
Re: SQL22212 Error2012-12-14T13:37:17Z in response to Leo_52Hello,
Can you be more specific about what you attempt when SQL22212N is returned ??
- which client application are you using ?
- which action do you perform within this application ?
Also check that the administration server service is started.