Prev
Next
Forums Infor / Lawson Platforms S3 Systems Administration

Oracle 11gR2 slow?

 10 Replies
 0 Subscribed to this topic
 27 Subscribed to this forum
Sort:
Author
Messages
Gary Padgett
Veteran Member
Posts: 90
Veteran Member
9/7/2012 2:23 PM
    We are doing a big-bang annual upgrade, and among the upgrades is Oracle - from 11.1 to 11.2.  We noticed in particular that batch jobs are running much longer - a payroll run took twice as long, and an HR155 took 3 times as long.
    We did a DR exercise that rolled back the rest of the upgrade, leaving only the Oracle 11gR2 as the only upgraded component - and batch jobs are just as slow.  So I should be able to rule out anything on the Lawson side.
    Any ideas about settings/tweaks/etc that can fix this performance issue?
    Greg Moeller
    Veteran Member
    Posts: 1498
    Veteran Member
    9/7/2012 3:02 PM
      Did your upgrade also include a new version of DB2? Seems to me that there were/are some config files that we needed to tweak there. Do you have LBI integrated with Portal? If so, there's more advice I can give.
      badri
      Basic Member
      Posts: 11
      Basic Member
      9/7/2012 3:10 PM
        Hi Gary, You may want to check the execution plans which have some "quirks" in 11gr2. Also you can monitor v$session_longops (which am sure you are doing already).
        HTH
        Gary Padgett
        Veteran Member
        Posts: 90
        Veteran Member
        9/7/2012 3:20 PM
          Greg, we don't have DB2. Badri, I will pass this along to our DBAs to monitor. Thanks to both
          Greg Moeller
          Veteran Member
          Posts: 1498
          Veteran Member
          9/7/2012 4:52 PM
            If you don't have DB2, are you storing the Lawson security information in Oracle?
            Gary Padgett
            Veteran Member
            Posts: 90
            Veteran Member
            9/7/2012 5:10 PM
              LDAP is MS ADAM; gen info etc is in the Oracle instance
              Greg Moeller
              Veteran Member
              Posts: 1498
              Veteran Member
              9/7/2012 7:13 PM
                By chance do you have any materialized views that are updating during the day? We found a tremendous job run time savings by redoing/optimizing those views.
                Gary Padgett
                Veteran Member
                Posts: 90
                Veteran Member
                9/7/2012 7:33 PM
                  On this non-production machine, those views are not being rebuilt (the job is commented out in cron for now). When they do get rebuilt, it's at 4 AM only. So that does not appear to be an issue in this case.
                  Gary Padgett
                  Veteran Member
                  Posts: 90
                  Veteran Member
                  9/10/2012 5:04 PM
                    I ran the statistics for a GL293 job that currently runs in under 15 minutes in production and is taking approx 48 minutes on this system with 11gR2.
                    It shows that 90 percent of the time is taken up with FindBegRng calls against GLAMOUNTS table. Other FindBegRng calls also seem to be kind of slow, but I can't tell for sure.
                    badri
                    Basic Member
                    Posts: 11
                    Basic Member
                    9/10/2012 5:46 PM
                      Gary,
                      The DBA should be able to compare the execution plans on both the 'old' and 'new' (ie pre-upgrade and post-upgrade). Is this RAC or non-RAC ? Could be a bug in 11gr2.
                      Check out SQL Plan Management in 11g from the Gridcontrol /OEM.
                      HTH
                      Gary Padgett
                      Veteran Member
                      Posts: 90
                      Veteran Member
                      9/20/2012 4:47 PM
                        We deleted the 11.2 instance and reinstalled an 11.1 instance (matching our production and other non-production instances). Also backed out my upgrade altogether. Apparently we are having some system slowness related to this LPAR. We ran a GL293 job and ran truss against it. The IPC appears to be 2 to 3 times slower than on my other non-production LPAR. They are supposed to be identical, but...
                        Both of these LPARs were moved from IBM p570 to p770 a few months ago. This system is not used a lot until we are testing an upgrade. So we are concentrating more on this LPAR now.