Looking for fix for duplicate data (item_id rows) in 3.0.4.x

Dear all,
in March an issue with duplicate rows of data was discovered (issue tracker # 0008293). I know that this issue has been resolved in 3.1 however we cannot update to 3.1 yet, mainly because of unsolved SPSS export issues.
Is there a fix for this problem in 3.0.4.1 or 3.0.4.2?
In the notes to issue #0008293 is sounds like there is also a script to identify and correct the issue with duplicate data sets.
We are using OpenClinica in an production environment, so solving the issue is very important to us. Any help is greatly appreciated.
Thank you.
Claudia Trepte
Data Manager
NovaShunt AG

Comments

  • Hi Claudia,
    If you download the latest release, unpack the ZIP archive and go to the \config\database\PostgreSQL\3.1.1\upgrade directory, you can find the scripts and instructions there. If you are running an Oracle database, you can find the scripts under the \config\database\Oracle\3.1.1\upgrade directory instead.
    You can also find instructions for this patch online, here:
    https://svn.akazaresearch.com/openclinica/OpenClinica/trunk2/projects/web/src/main/config/database/PostgreSQL/SNAPSHOT/upgrade/README_Instructions_for_Duplicate_Row_Fix.txt
    Hope this helps, Tom
    Tom Hickerson | Senior Tier-2 Engineer
    [email protected]
    www.openclinica.com
    Open Source Platform for Clinical Research
    -----Original Message-----
    Sent: Tue 8/30/2011 11:54
    To: User Forum OC
    Subject: [Users] Looking for fix for duplicate data (item_id rows) in 3.0.4.x

    Dear all,
    in March an issue with duplicate rows of data was discovered (issue
    tracker # 0008293). I know that this issue has been resolved in 3.1
    however we cannot update to 3.1 yet, mainly because of unsolved SPSS
    export issues.
    Is there a fix for this problem in 3.0.4.1 or 3.0.4.2?
    In the notes to issue #0008293 is sounds like there is also a script to
    identify and correct the issue with duplicate data sets.
    We are using OpenClinica in an production environment, so solving the
    issue is very important to us. Any help is greatly appreciated.
    Thank you.
    Claudia Trepte
    Data Manager
    NovaShunt AG
  • ctreptectrepte Posts: 100
    Dear Tom,
    we ran the Duplicate_Report.sql file on our database. It reported 0 duplicates. However, we definitely still have duplicates in there (see attached lists). Any explanation why they are not discovered by the Duplicate_Report.sql file?
    Best regards,
    Claudia Trepte
    Data Manager
    NovaShunt AG

    Am 8/30/2011 11:15 AM, schrieb Tom Hickerson:
    > Hi Claudia,
    >
    > If you download the latest release, unpack the ZIP archive and go to the \config\database\PostgreSQL\3.1.1\upgrade directory, you can find the scripts and instructions there. If you are running an Oracle database, you can find the scripts under the \config\database\Oracle\3.1.1\upgrade directory instead.
    >
    > You can also find instructions for this patch online, here:
    >
    > https://svn.akazaresearch.com/openclinica/OpenClinica/trunk2/projects/web/src/main/config/database/PostgreSQL/SNAPSHOT/upgrade/README_Instructions_for_Duplicate_Row_Fix.txt
    >
    > Hope this helps, Tom
    >
    > Tom Hickerson | Senior Tier-2 Engineer
    > [email protected]
    > www.openclinica.com
    > Open Source Platform for Clinical Research
    >
    >
    >
    > -----Original Message-----
    >
    > Sent: Tue 8/30/2011 11:54
    > To: User Forum OC
    > Subject: [Users] Looking for fix for duplicate data (item_id rows) in 3.0.4.x
    >
    > Dear all,
    >
    > in March an issue with duplicate rows of data was discovered (issue
    > tracker # 0008293). I know that this issue has been resolved in 3.1
    > however we cannot update to 3.1 yet, mainly because of unsolved SPSS
    > export issues.
    >
    > Is there a fix for this problem in 3.0.4.1 or 3.0.4.2?
    >
    > In the notes to issue #0008293 is sounds like there is also a script to
    > identify and correct the issue with duplicate data sets.
    >
    > We are using OpenClinica in an production environment, so solving the
    > issue is very important to us. Any help is greatly appreciated.
    >
    > Thank you.
    >
    > Claudia Trepte
    > Data Manager
    > NovaShunt AG
    >
This discussion has been closed.