Prev
Next
Forums S3 Customization/Development

PA100HR

Sort:
You are not authorized to post a reply.
Author
Messages
Chesca
Veteran Member
Posts: 490
Veteran Member
5/31/2013 1:29 PM
    PA100HR went in recovery mode due to a duplicate record.  How can I find the duplicate record or data that's causing this issue other than animating the program? 
    Errror message:
     ** Creating .prt and .dtl files
                    Processing PA100 (Action Update)
                    File PROD9/PGEMPLOYEE.
                    FindDBRec error is A duplicate record was added in deferred mode
                    Additional Text is:
                    FlushPendingInserts(LAWSON9."PGEMPLOYEE")
                    OCIStmtExecute() returned OCI_ERROR code 1 parse offset 0 (
                    ORA-00001: unique constraint (LAWSON9.PGESET1) violated
    Ragu Raghavan
    Veteran Member
    Posts: 469
    Veteran Member
    5/31/2013 3:45 PM
      vwdblog or
      lashow $LAWDIR/system/ladb.log may have the details
      Kwane McNeal
      Veteran Member
      Posts: 479
      Veteran Member
      5/31/2013 4:02 PM
        Actually, in your LAWDIR//ORACLE file, set the INSERTBUFSIZE=1, and rerun the job. that will tell you. There used to be a KB on this, but I don't know it's still around
        Chesca
        Veteran Member
        Posts: 490
        Veteran Member
        5/31/2013 4:18 PM
          Thank you. I looked in the ladb.log file and I think I found the record.
          FlushPendingInserts(LAWSON9."PGEMPLOYEE")
          OCIStmtExecute() returned OCI_ERROR code 60 parse offset 0 (
          ORA-00060: deadlock detected while waiting for resource
          )

          insert into LAWSON9."PGEMPLOYEE" ("COMPANY", "GROUP_NAME", "EMPLOYEE", "LAST_NAM
          E", "FIRST_NAME", "MIDDLE_INIT") values (:1, :2, :3, :4, :5, :6)
          --- Start of Key area dump ---
          "COMPANY"=0001
          "GROUP_NAME"=XXX-ALL
          "EMPLOYEE"=0000123
          "LAST_NAME"=
          "FIRST_NAME"=
          "MIDDLE_INIT"=
          --- End of Key area dump ---
          *** end oradb10 error message ***
          Chesca
          Veteran Member
          Posts: 490
          Veteran Member
          5/31/2013 4:45 PM
            Thank you. I looked in the ladb.log file and I think I found the record.
            FlushPendingInserts(LAWSON9."PGEMPLOYEE")
            OCIStmtExecute() returned OCI_ERROR code 60 parse offset 0 (
            ORA-00060: deadlock detected while waiting for resource
            )

            insert into LAWSON9."PGEMPLOYEE" ("COMPANY", "GROUP_NAME", "EMPLOYEE", "LAST_NAM
            E", "FIRST_NAME", "MIDDLE_INIT") values (:1, :2, :3, :4, :5, :6)
            --- Start of Key area dump ---
            "COMPANY"=0001
            "GROUP_NAME"=XXX-ALL
            "EMPLOYEE"=0000123
            "LAST_NAME"=
            "FIRST_NAME"=
            "MIDDLE_INIT"=
            --- End of Key area dump ---
            *** end oradb10 error message ***
            You are not authorized to post a reply.