What database is my environment hitting ?

 6 Replies
 0 Subscribed to this topic
 27 Subscribed to this forum
Sort:
Author
Messages
Robert W. Schottman
New Member
Posts: 3
New Member
    I am having two issues with getting my test environment up and running that I can't seem to find any good info on our there in Lawson support land. #1) My test environment, while up and running, is still pulling data from my production database, not my test database. I found the CAPS file = MICROSOFT, but any manipulation of that file doesn't seem to have any bearing on where the environment gets it's data. #2) I mistakenly ran "laconfig -install" while trying to figure out issue #1. It saw my existing LSFPROD, didn't change anything in the settings, but now the lawson.insight service in the windows services list is gone ??? I am running LSF9.0.1.4. Way behind, we know, but any help you could give me would be greatly appreciated.
    Jimmy Chiu
    Veteran Member
    Posts: 641
    Veteran Member
      Did you clone your test environment?
      Kwane McNeal
      Veteran Member
      Posts: 479
      Veteran Member
        I thought about this over the weekend, and I wondered the same thing as Jimmy.

        If you cloned your productline into a running environment (regardless of whether that enviroment was cloned), then the first access will cache the MICROSOFT file.

        So I ask the following:
        1) Have you changed your LAWDIR/pline/MICROSOFT file to reflect the test database?
        2) Have you EITHER restarted your test environment OR run 'dbadmin idleAll', *when your environment was quiet*?
        (NOTE: for dbadmin to work, there can be NO accesses to a productline. This is usually hard to ensure with WebSphere running, thus it is easier to restart)

        Kwane
        Robert W. Schottman
        New Member
        Posts: 3
        New Member
          Yes, I ghosted my servers in an attempt to clone my production environment and thereby get a test environment. Dealt with MicroFocus. Everything seemed fine at that point, but I was unsure. I asked my AP/AR and Payroll officers to do some things in the test system to see what data it was hitting, and 'lo and behold it is hitting my production data. I have edited the LAWDIR/prodline/MICROSOFT file. I put in the pure IP address of the test database server. The database name is the same. When I do that, it breaks lawson. If I use the hostname, even though I have it where that hostname gets resolved to the new/test database server, it still hits the production server. Puzzling. Apparently, there are hooks to data in other places. That's all I can figure. I have NOT run "dbadmin idleALL". I can, but can you tell me what exactly it is that this will do to "aim" my environment at the new/test database server and database ?
          Kwane McNeal
          Veteran Member
          Posts: 479
          Veteran Member
            Bob,
            This is fairly complex, and ghosting your environment would be a very bad way to do this. Call me offline for me to explain, as I have a few minutes during my lunch break.

            Kwane
            505-433-7744
            Kwane McNeal
            Veteran Member
            Posts: 479
            Veteran Member
              Also, my advice would be to immediately stop running transactions through this clone, until you get the linkage cleaned up, as there's a fair bit more than modifying your MICROSOFT files

              Kwane
              Robert W. Schottman
              New Member
              Posts: 3
              New Member
                I wish I had come back to check the forum out sooner after my last posting. I got tied up in other things. Yep, we figured it out quickly enough that we didn't do any damage to our production database. We have the turned off the clone and have left it off.
                How much more could there possibly be in there in terms of how it gets to it's data ? You'd think there was a Lawson KB on it, but I have yet to find it.