| LC Errors/Issues and Resolutions |
Mindwatering Incorporated
Tripp W Black on 09/03/2005 at 02:09 PM |
Category: Notes Developer Tips
LSX (LotusScript Extensions/Connectors)
|
CONNECTION ISSUES
Issue:
[IBM][CLI Driver] SQL1032N No start database manager command was issued. SQLSTATE=57019, Connector 'db2', Method -Connect- (-1032)
Resolutions:
1. Check the DB2 server and the DB2 Manager. Make sure both services are running.
2. Check that DECS is running.
______________________________
Issue:
[IBM][CLI Driver] CLI0124E Invalid argument value. SQLSTATE=S1009, Connector 'db2', Method -Connect- (0xFFFE7961)
Resolution:
Check that the database name is correct -- this is set up at the native client level. If using 'odbc' instead of 'db2', set up a system connection in the "Data Sources (ODBC)" control panel.
______________________________
Issue:
[IBM][CLI Driver] SQL30082N Attempt to establish connection failed with security reason "24" ("USERNAME AND/OR PASSWORD INVALID"). SQLSTATE=08001, Connector 'db2', Method -Connect- (-30082)
Resolution:
The username/id or password entered is not correct.
______________________________
Issue:
LCConnection line fails with message: Cannot load connector library 'odbc'.
In addition, you may see the following error message on the server:
db2nq.exe - unable to locate DLL
The dynamic link library nxmlpar.dll could not be found in the specified path.
Resolutions:
1. Add the Domino executable directory to the environmental Path variable.
2. Check the driver, if using 6.x or 7.x, it's 'odbc2' !
______________________________
Issue:
LCConnection line fails with message: Cannot load connector library 'odbc2'.
Resolutions:
1. Check that the appropriate DLLs exist and that DECS is running.
2. Check how the LCSession & LCConnection is being initialized: For non-LEI, session should be dimmed without parameter and connection should reference source database.
3. Run LCTest or for Domino 7, run DCTEST.EXE (Linux/UNIX) or NDCTEST.EXE (Windows)
4. Check that the connector is spelled correctly.
______________________________
Issue:
Error: [IBM][iSeries Access ODBC Driver][DB2 UDB]SQL5016 - Qualified object name TABLENAME not valid., Connector 'odbc2', Method -Execute-(5106)
Resolution:
Evidently this has to do with the system delimiter between the library and file. Instead of it being the standard SQL ".", the system is expecting a "/".
Either change the "." to "/" or see if you can change the session attributes to switch from *SYS to *SQL.
______________________________
Issue:
Error: Metadata object does not exist, Connector 'odbc2', Method -Execute-
Resolution:
Check the SQL you are executing. The table is misspelled or the library/schema has been out.
(e.g. mytable.tablename instead of just tablename)
______________________________
Issue:
Error: [Microsoft][ODBC Driver Manager] Invalid argument value, Connector 'odbc2', Method -Fetch- (55)
Resolution:
Issue seen a couple times using the generic ODBC or DB2 ODBC rather than the Lotus OEM DataDirect ODBC drivers. Try using the DataDirect ones. Get them via Lotus Passport.
______________________________
Issue:
Error: Field mapping failed due to a missing field, Connector 'odbc2', Method -Update-
Resolution:
Check spelling and capitalization of field names. Fields names can be case sensitive with ODBC.
______________________________
Issue:
ndtest.exe works to connect to db2. However, no connections in DECS Administrator and no DCRs can be created.
The former gives the missing libraries error. The latter gives standard realtime services error. DECS is running.
Resolution:
If Linux, this would normally be a permissions/profile issue where the profile of the domino user (e.g. home/notes/.profile) needs to be updated.
If Windows, the server runs as "Local Service". It doesn't login. However, if the DB2 Client (Configuration Assistant) can see the DB2 database/table and the NDTest can, as well. Check the following:
--> Ensure Domino path and the DB2 Connector are in the environmental PATH variable. (My Computer,--> Performance Settings --> Environmental Variables --> PATH)
--> Verify connector is patched. (Don't let the connector get too far behind the server version level.)
______________________________
DATA/FIELDS ISSUES
Issue:
Invalid field
Resolution:
A source database column does not exist in the source database. Check spelling on the key and data columns in the source table/view.
______________________________
______________________________
previous page
|