Do not input private or sensitive data. View Qlik Privacy & Cookie Policy.
Skip to main content

Announcements
Qlik Connect 2026! Turn data into bold moves, April 13 -15: Learn More!
cancel
Showing results for 
Search instead for 
Did you mean: 
Not applicable

ODBC SQL crash

I am in my very early days of using Qlikview with server based Lotus Notes databases using Notes SQL ODBC drivers. I have had success until now. I am trying to load around 80,000 records form a view. The SQL script runs and the load ceases at record 16536. There does not seem to be anything strange about record 16537.

Restriciting the load via where statements does not work I just get "Column not Found" error.

This is the error data from Qlikview

SQL Error

SQL Scriptline

SQL State 00000

SQL Select * "from Maintenance all by REquest No all" (the view name)

In the nsd log file (which would have bee ngenerated by the Notes SQL driver or such like these are the lines that seem to realte to the crash:

Generated Messages:

INFO (0): Walk mem for process NLNOTES (13d4)
INFO (0): Walk mem for process ntaskldr (10c8)
INFO (0): Walk mem for process nsqle32 (1330)
INFO (0): terminated process [ NLNOTES: 5076]
INFO (0): terminated process [ntaskldr: 4296]
INFO (0): terminated process [ nsqle32: 4912]
INFO (0): Deleting pid.nbf
WARNING (0): Debugger still attached to 3 processes

Please send the following files:

NSD Log : C:\Program Files\lotus\notes\data\IBM_TECHNICAL_SUPPORT\nsd_W32I_T18036662TP5000_2009_04_27@14_18_50.log
Core Dump : C:\Program Files\lotus\notes\data\IBM_TECHNICAL_SUPPORT\core.nsqle32.W32I_T18036662TP5000_2009_04_27@14_18_50

Am I just running out of RAM. I have had no trouble with views with a few thousand records but it is my undersanding that Qlkview can handle very large amounts of data.

Any feedback will help

14 Replies
Not applicable
Author

[View:http://community.qlik.com/cfs-file.ashx/__key/CommunityServer.Discussions.Components.Files/11/0763.latest-nsd.log:550:0]I tried the version 8 SQL driver with same failure. Reverted back because of other problems with the driver. Tried again with a different copy of the database - no improvement. Tried with selecting one column and got a worse result. Latest log file attached.

Not applicable
Author

I think that the SQL is not match SQL 92 standard.

Please try it like

SQL Select * from "from Maintenance all by REquest No all"

or Select * from [from Maintenance all by REquest No all]

Good luck!

Not applicable
Author

The error in the link in your reply would seem to indicate that it would occur when the first document was hit. In my case the Notes client falls over at document 8729. The error only occurs with this database. It does not directly relate to the number of documents (around 65000) as I have used the same procedure with even larger document numbers in different Lotus Notes files. I cannot see anything odd with the documents. They all look the same. It's some unsolvable anomaly.

Latest error log attached

[View:http://community.qlik.com/cfs-file.ashx/__key/CommunityServer.Discussions.Components.Files/11/3301.ndserror.log:550:0]

.

rwunderlich
Partner Ambassador/MVP
Partner Ambassador/MVP

1. Can you copy the database (using Notes)? Sometimes this surfaces structural problems with the nsf.

2. Have you tried deleting document 8729 to see if the error moves?

3. Have you tried running fixup on this DB?

From the nsd file, your error is "LookupHandle: null handle" trying to unlock something. You'll proabably have to take this to IBM support if deleting a document doesn't fix it.

If you google "LookupHandle: null handle" you'll find a number of reported problems (not with NotesSQL, but other apps) where a string field has a null value. Do any of the view fields have null values? If so, can you add column formula to make them empty '' strings?

-Rob

edmondo_tassi
Contributor III
Contributor III

Hello, the star * in sql select is an issue.

Try this in spite of:

SQL SELECT "TABLE NAME".*

FROM "TABLE NAME".

It works 2 me.

Bye

p.s. Keep in mind to modify in 4096 the transfer rate on sql notes configuration, is quite faster.