dcmqridx - DB ALERT when adding files to database

[micha_wagner]

Hi,

I'm using dcmqridx to add DICOM files to a database.
Starting with an empty (non-existent) database.
After ca. 30 studies containing some 200 images each, I get lots of "*** DB ALERT: attempt to seek beyond 33554432 bytes" messages.
I'm trying to understand whether I've hit some internal limit of dcmqridx/dcmqrscp and whether there's a way to get around it.

Additional information:
Windows 10 64bit OS
index.dat file at that time is 44.093.440 bytes large

Thanks for your help,

Michael

[J. Riesmeier]

This one was easy to find (in the source code of "dcmqrdb/libsrc/dcmqrdbi.cc"):

Code: Select all

    /*
    ** print an alert if we are seeking to far
    ** what is the limit? We don't expect the index file to be
    ** larger than 32Mb
    */
    const long maxFileSize = 33554432;
    if (pos > maxFileSize) {
        DCMQRDB_ERROR("*** DB ALERT: attempt to seek beyond " << maxFileSize << " bytes");
    }

[micha_wagner]

Thanks.

Next time I will know how to find it myself.

Michael

This one was easy to find (in the source code of "dcmqrdb/libsrc/dcmqrdbi.cc"):

Code: Select all

    /*
    ** print an alert if we are seeking to far
    ** what is the limit? We don't expect the index file to be
    ** larger than 32Mb
    */
    const long maxFileSize = 33554432;
    if (pos > maxFileSize) {
        DCMQRDB_ERROR("*** DB ALERT: attempt to seek beyond " << maxFileSize << " bytes");
    }

[J. Riesmeier]

Regarding the "internal limits": yes, there are hard-coded limits, e.g. the following:

Code: Select all

/// upper limit for the number of studies per storage area
#define DB_UpperMaxStudies              500
/// upper limit for the number bytes per study
#define DB_UpperMaxBytesPerStudy        0x40000000L
[...]
#define MAX_MAX_STUDIES         DB_UpperMaxStudies
#define MAX_NUMBER_OF_IMAGES    10000

The "DB Alert" on the size of the "index.dat" file should probably rather be a warning than an error message.