Prev
Next
Forums S3 Systems Administration

How to rebuild logan database

Sort:
You are not authorized to post a reply.
Author
Messages
Xin Li
Veteran Member
Posts: 133
Veteran Member
9/22/2009 1:39 PM
    My test product line logan has been restored with production poruct line logan that should not been done in the first place. Does anyone have the experience as how to rebuild logan product line?

    Derek Czarny
    Veteran Member
    Posts: 63
    Veteran Member
    9/22/2009 5:02 PM
      I have always wondered what I would do with the exact same problem.  I would probably restore from backup the LOGAN database backup from my test system.  If I did not do backups of LOGAN on my test system.  I think I would search all the tables in LOGAN for any servername values and update them with my test server name.  Just a thought, but I would be interested in the solution.
      Norm
      Veteran Member
      Posts: 40
      Veteran Member
      9/23/2009 5:10 PM
        Whenever we restore our test databases from Production, a standard step is to export the LOGAN (and now GEN) tables prior to the refresh. They are then re-imported after the refresh is done. That's the safest way to insure the integrity of your EDI and ProcessFlow tables for LOGAN, and your security tables for GEN.

        Unfortunately, lots of GEN and LOGAN tables contain product line and/or file path information that might be different between test and production (they are for us).

        This doesn't help you much for your current situation, sorry. I think Derek's answer, to restore from a current backup is about the best you can hope for. Otherwise, you'll spend a lot of time fudging records all over the place trying to get it to work again
        You are not authorized to post a reply.