Announcement

Collapse
No announcement yet.

dbpatch_55.sql has an error

Collapse
X
Collapse
 
  • Page of 1
  • Time
  • Show
Clear All
new posts
Previous template Next
  • #1

    dbpatch_55.sql has an error

    hello,
    after running dbpatch_55.sql i get this error
    Error applying patch patch6376059:
    ORA-02291: integrity constraint (GLOGOWNER.FK_TRNSD_TRANSLATION_GID) violated - parent key not found
    patch6395779 CU4

    the rest worked well but can anyone tell my what went wrong with this one?

    gerhard
    Tags: cu4, dbpatch55sql, dbpatch_55, error, installation, ora 02291, otmfaq.com, patch6376059
    • #2
      Re: dbpatch_55.sql has an error

      I have the same problem (fresh install). In decided for the time being to ignore it - it seems the patch is about an error message text, and I can probably live with that. In case you found a way to fix it, please share - I will do the same.

      Regards,
      Sven

        Comment

        • #3
          Re: dbpatch_55.sql has an error

          Originally posted by svenhaul
          I have the same problem (fresh install). In decided for the time being to ignore it - it seems the patch is about an error message text, and I can probably live with that. In case you found a way to fix it, please share - I will do the same.

          Regards,
          Sven

          I wouldn't ever recommend to ignore any errors. What I have found out from clients doing this is in the past is that when you try migrating to a new version of OTM, it will cause you a lot of pain if your initial db scripts are not clean. This error is being caused by an entry which is missing in the translation table which is trying to be inserted in the translation_d table. I would suggest contacting Oracle support and get this fixed.
          If my post was helpful please click on the Thanks! button

          MavenWire Hosting Admin
          15 years of OTM experience

            Comment

            • #4
              Re: dbpatch_55.sql has an error

              I'm with Nick on this one, don't ignore the error. Were you only running the script as part of applying the new CU? If it is a fresh install, I'd go back and look at my process and see if another error occured in an earlier step, expecially during the import and the scripts execute shortly after that.

              John

                Comment

                • #5
                  Re: dbpatch_55.sql has an error

                  John, I triple-checked the previous import steps, and evertyhing apparently went fine, all object counts were correct. So search me why it could happen that these entries are missing.
                  I agree with Nick that this cannot be ignored for anything that is to stay. But the current installation is for a quick and dirty trial, basically to get a feeling for the UI beyond the powerpoints. It will definetely be scrapped as soon (and if) we go for a real pilot installation.
                  Thank you for the advice, I really appreciate it. You guys have already been a real help!

                    Comment

                    Previous template Next
                    Working...
                    X
                    😀
                    🥰
                    🤢
                    😎
                    😡
                    👍
                    👎