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
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.
I removed the quotes but kept the *. It still fails at the same point- giving me the Lotus Notes error (which indicateds the ODBC driver fails) It fails ath the same point loading all records up to 16536.
bming wrote: 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.
Your trouble is not in QlikView yet - it's somewhere between Notes and the ODBC driver. You need to find out the limitations of the ODBC transfer - is there any threshold that could be configured.
Try going through various settings within your ODBC Data Source definitions. For example, AS/400 ODBC driver allows configuring the "block size" for the individial "packets" being sent between the database and the client. Depending on the size of the database and the performance of the machine, this parameter needs to be tweaked to achieve optimum performance. When it's set too high, the database issues sporadic messages and failures. There might be something similar for Notes (never had a chance to load Notes data into QlikView...)
One more thought. It sounds like you've identified the documents represented by rows 16536 & 16537. Can you delete these documents (from a copy of the DB) to see if the error goes away or still occurs on that row#?
The ODBC driver version is 3.02.2006.706 from IBM. I am using Domino Vers 6.5.2 and version 8.5 of Qlkview. I have attached the latest log file from the last failure. [View:http://community.qlik.com/cfs-file.ashx/__key/CommunityServer.Discussions.Components.Files/11/4061.nsd.log:550:0]
I believe the NotesSQL trace facility can give you a node count for the statement.
Not sure which release 3.02.2006 corresponds to -- I'm used to seeing an alpha at the end of the release like "3.02g". I'm actually using the Notes 8 driver now.
The latest 3.02 release is 3.2i. If your's is older than that, you might want to try an upgrade to 3.02i.
I limited the Load to just one column of the view instead of the ten or so and actually managed to load slightly FEWER records. That is wierd. I used the ODBC trace - the resultant file was empty. No other log file was created
