I am experiencing a strange connection issue with an agent that connects to a DB2 database on System i. This agent has worked fine for over a year and just started having “ad hoc” problems connecting. If I use a data connection, I can test fine and access tables with no problem. There does not appear to be an issue with the DB2 database. It does not appear to be network issues. There is no maintenance that would take the database offline during this period, etc. The agent runs fine 90% of the time… might run 5 days straight then just not connect. Here is what appears in the log. It seemed to start right after the 8.0.2 upgrade!?! Any thoughts re: troubleshooting this one? Guess I’ll try and add some additional print statements to see if it is really connecting or not. FYI… ODBCConnection is used in the case (really CLI on System i). The error seems clear but am wondering at this stage. Thanks team… anyone else experienced agent connection problems after 8.0.2 upgrade?
note: the dbcollect.nsf is where the agent runs and collects data then distributes to the appropriate sales databases (starts with salesdb1).
09/30/2008 17:00:49 AMgr: Agent (‘Update Docs from DB2)’ in ‘dbcollect.nsf’) message box: Could not connect to T16BV3DD
09/30/2008 17:00:49 AMgr: Agent (‘Update Docs from DB2)’ in ‘dbcollect.nsf’) message box: database salesdb1
09/30/2008 17:00:49 AMgr: Agent (‘Update Docs from DB2)’ in ‘dbcollect.nsf’) message box: LS:DO- The requested operation requires that you first be connected to a data source.
I have this same issue. Replaced the ODBC “lic” file, ran fine for a while…then started failing (sometimes) again. Reinstalled Domino and LEI. Any updates on this problem?
Subject: Re: Intermittent Connection (DB2 Agent on System i)
Thanks for your feedback. We are not using LEI but using ODBCConnection in an agent only. I’ll check out the technote. Would I look for the SQL 523 errors in the system i messages/log or in Domino log (am seeing nothing in Domino log).
Subject: Re: Intermittent Connection (DB2 Agent on System i)
Hi Michael!
Since you’re using an ODBC Connection within an Agent, I would suggest you review the JobLogs of the AMGR Jobs after the Agent completes execution for the SQL errors mentioned by Gil.
However, you may want to consider trying LSX:LC instead of LS:DO (i.e. ODBC) as LS:DO is now considered “legacy”. I have several information resources on using LSX:LC including connectivity with DB2 resources below for your reference:
I really appreciate the assistance. I’ll review the sites and documentation. It is a large agent… a bit ominous for this admin! I can see where the LCConnection would replace the ODBCCOnnection… it is the parts after that that confuse me a bit.
Subject: Error occurred in SQL call level interface
I found the errors (and the successes) in the AMGR job log.
Program: qsqcli
module: sqlcon
procedure: SQLConnect
Statement: 9297
Status: Diagnostic
The confusing part… (I know I’m repeating) why would it work a few days in a row then stop. Also, I can edit the agent and add a space then save… it will work (but not in all cases). Is there a known issue with LS:DO and the DB2 CLI?
These issues started with the upgrade to V8.0.2… worked fine in the previous V8 stream. Any chance this is a regression or was something intentionally removed that would affect LS:DO agents from running? I realize that the LSX route is the way to go but there are tons of customers with legacy agents using LS:DO.
Are there any errors within the AMGR Job Log, other than the Diagnostic message? If not, then I would suggest you contact IBM Lotus Support to continue investigating this issue.