Error saving to SQL message.

  • Hi,
    I noticed this topic has been discussed before. But the only thing I learned from it is to set the debuglevel to 4 and I received the following errors under the server status tab:



    [SARCH] UPACS THREAD 72431: STARTED AT: Fri Sep 28 15:50:12 2007
    [SARCH] A-ASSOCIATE-RQ Packet Dump
    [SARCH] Calling Application Title : "A_SSC "
    [SARCH] Called Application Title : "SARCH "
    [SARCH] Application Context : "1.2.840.10008.3.1.1.1"
    [SARCH] Number of Proposed Presentation Contexts: 1
    [SARCH] Presentation Context 0 "1.2.840.10008.5.1.4.1.1.20"
    [SARCH] Server Command := 0001
    [SARCH] FreeStore Left 835201 on E:\
    [SARCH] ***Failed SQLExecDirect : INSERT INTO DICOMStudies (StudyInsta, StudyDate, StudyTime, StudyID, StudyDescr, AccessionN, StudyModal, StationNam, PatientNam, PatientBir, PatientSex, PatientID, AccessTime) VALUES ('1.2.752.37.1.1.65541250.4.132920031204', '20031204', '084558', '########20031204', 'CVS', '########20031204', 'NM', 'server1', '*****^*****', '192605197O', 'O', '########', 1191008992)
    [SARCH] ***Error: 1406: S1000: [MySQL][ODBC 3.51 Driver][mysqld-5.0.45-community-nt]Data too long for column 'PatientBir' at row 1
    [SARCH] ***Unable to DB.Add()
    [SARCH] ***SQL: INSERT INTO DICOMStudies (StudyInsta, StudyDate, StudyTime, StudyID, StudyDescr, AccessionN, StudyModal, StationNam, PatientNam, PatientBir, PatientSex, PatientID, AccessTime) VALUES ('1.2.752.37.1.1.65541250.4.132920031204', '20031204', '084558', '########20031204', 'CVS', '########20031204', 'NM', 'hserver1', '****^******', '192605197O', 'O', '########', 1191008992)
    [SARCH] ***Error: 1406: S1000: [MySQL][ODBC 3.51 Driver][mysqld-5.0.45-community-nt]Data too long for column 'PatientBir' at row 1
    [SARCH] ***Error saving to SQL: 10153385\1.2.752.37.1.1.212298535.5.1794052_0001_000001_1191009012971e.v2
    [SARCH] UPACS THREAD 72431: ENDED AT: Fri Sep 28 15:50:12 2007
    [SARCH] UPACS THREAD 72431: TOTAL RUNNING TIME: 0 SECONDS


    I looked at the value contained "Patient DOB" from the Calling station (the source) and it looks like a normal Date of birth. It had the date "26:06:1971". But in the SQL statement above it has the value "192605197O".
    I don't understand the discrepancy.
    Also, I created another Conquest server with a blank repository and this problem did not exist.
    What could be causing this problem. Thank you.


    PS: I changed any confidential information to "*" or "#".

  • Hi,


    The date format in DICOM images must be YYYYMMDD. Any other format will not be correctly handled (as you have shown) and lead to a rejected database insert when the resulting string is too long (more than 8 chars).


    The too long date string should have been truncated by our server and give a warning message. That this does not happen is a known bug.


    Marcel

Participate now!

Don’t have an account yet? Register yourself now and be a part of our community!