FAQ
Standby database server: SUSE Linux Enterprise Server 10 (s390x)
2.6.16.54 0.2.5 (64-bit)
Production database server: SUSE Linux Enterprise Server 10 (s390x)
2.6.16.54 0.2.5 (64-bit)
EM: 10.2.0.5

I'm in the first stages of setting up a standby database. I requested that
my SAs set up the standby server to be identical to the production server.
Several things weren't set up correctly like the oracle user had no write
privileges anywhere, the wrong group designation, copied the wrong directory
for the oracle home, etc. So many things were wrong that I decided to use
EM to compare the two OS installations. EM says that several parameters are
different between the two servers but my SAs say they are identical. I
don't know where the SAs got their information only that EM is using
/sbin/sysctl. Since that is a binary file, I can't really look at it. What
might my SAs be looking at to see the parameter values? Some are
substantially different and I'd like to get his resolved before moving
forward. I'm trying to mitigate any unpleasant surprises due to differences
between the servers.

Search Discussions

  • Matthew Zito at Dec 22, 2009 at 9:54 pm
    Well, we'd need some examples of areas where there were disagreement,
    but if, for example, the shared memory settings were wrong, it may be
    that the SA has updated the /etc/sysctl.conf file but not run the sysctl
    command that causes it to be reread. In that situation, the sa will go:



    grep shmmax /etc/sysctl.conf



    and say "see, it's right"



    while EM says "/sbin/sysctl shmmax" (whatever the actual command is, I
    don't remember off the top of my head)



    and the system returns the current running value, not what it is set to
    be in the file.



    Matt



    From: oracle-l-bounce_at_freelists.org
    On Behalf Of Sandra Becker
    Sent: Tuesday, December 22, 2009 4:47 PM
    To: oracle-l
    Subject: Discrepancy in OS config between EM and sys admins



    Standby database server: SUSE Linux Enterprise Server 10 (s390x)
    2.6.16.54 0.2.5 (64-bit)

    Production database server: SUSE Linux Enterprise Server 10 (s390x)
    2.6.16.54 0.2.5 (64-bit)

    EM: 10.2.0.5

    I'm in the first stages of setting up a standby database. I requested
    that my SAs set up the standby server to be identical to the production
    server. Several things weren't set up correctly like the oracle user
    had no write privileges anywhere, the wrong group designation, copied
    the wrong directory for the oracle home, etc. So many things were wrong
    that I decided to use EM to compare the two OS installations. EM says
    that several parameters are different between the two servers but my SAs
    say they are identical. I don't know where the SAs got their
    information only that EM is using /sbin/sysctl. Since that is a binary
    file, I can't really look at it. What might my SAs be looking at to see
    the parameter values? Some are substantially different and I'd like to
    get his resolved before moving forward. I'm trying to mitigate any
    unpleasant surprises due to differences between the servers.
  • Guillermo Alan Bort at Dec 22, 2009 at 10:04 pm
    tell them to run sysctl -p, and make sure that /etc/sysctl.conf has the
    correct settings.

    hth
    Alan.-
    On Tue, Dec 22, 2009 at 7:54 PM, Matthew Zito wrote:

    Well, we�d need some examples of areas where there were disagreement, but
    if, for example, the shared memory settings were wrong, it may be that the
    SA has updated the /etc/sysctl.conf file but not run the sysctl command that
    causes it to be reread. In that situation, the sa will go:



    grep shmmax /etc/sysctl.conf



    and say �see, it�s right�



    while EM says �/sbin/sysctl shmmax� (whatever the actual command is, I
    don�t remember off the top of my head)



    and the system returns the current running value, not what it is set to be
    in the file.



    Matt


    ------------------------------

    *From:* oracle-l-bounce_at_freelists.org [mailto:
    oracle-l-bounce@freelists.org] *On Behalf Of *Sandra Becker
    *Sent:* Tuesday, December 22, 2009 4:47 PM
    *To:* oracle-l
    *Subject:* Discrepancy in OS config between EM and sys admins



    Standby database server: SUSE Linux Enterprise Server 10 (s390x)
    2.6.16.54 0.2.5 (64-bit)

    Production database server: SUSE Linux Enterprise Server 10 (s390x)
    2.6.16.54 0.2.5 (64-bit)

    EM: 10.2.0.5

    I'm in the first stages of setting up a standby database. I requested that
    my SAs set up the standby server to be identical to the production server.
    Several things weren't set up correctly like the oracle user had no write
    privileges anywhere, the wrong group designation, copied the wrong directory
    for the oracle home, etc. So many things were wrong that I decided to use
    EM to compare the two OS installations. EM says that several parameters are
    different between the two servers but my SAs say they are identical. I
    don't know where the SAs got their information only that EM is using
    /sbin/sysctl. Since that is a binary file, I can't really look at it. What
    might my SAs be looking at to see the parameter values? Some are
    substantially different and I'd like to get his resolved before moving
    forward. I'm trying to mitigate any unpleasant surprises due to differences
    between the servers.

    --
    Sandy
    Transzap, Inc.
    --
    http://www.freelists.org/webpage/oracle-l
  • Niall Litchfield at Dec 22, 2009 at 10:20 pm

    On Tue, Dec 22, 2009 at 9:54 PM, Matthew Zito wrote:

    while EM says �/sbin/sysctl shmmax� (whatever the actual command is, I
    don�t remember off the top of my head)
    sysctl -a|grep

    that's what kikstart or suse equivalent images are for of course.
  • Sandra Becker at Dec 23, 2009 at 3:20 pm
    I ran the commands to look at the parameters myself and I can't see any
    differences between the sysctl.conf files nor from running "sysctl
    -a|grep.... SAs are refusing to look at it anymore because they say it's
    correct. Is it possible that EM is incorrectly reporting the values? Is
    there some kind of refresh I need to do before the compare? I'm concerned
    because I remember the problems we had setting up the production server
    until we got some of the net.ivp4 settings correct.
  • Rich Jesse at Dec 23, 2009 at 3:32 pm
    Definitely possible, but perhaps the agent has not refreshed the information
    since it was last changed? I don't have the Configuration license pack, so
    I'm not able to see the info myself, nor how often the configuration data is
    collected.

    Just a thought...

    Merry Christmas!
    Rich
    I ran the commands to look at the parameters myself and I can't see any
    differences between the sysctl.conf files nor from running "sysctl
    -a|grep.... SAs are refusing to look at it anymore because they say it's
    correct. Is it possible that EM is incorrectly reporting the values? Is
    there some kind of refresh I need to do before the compare? I'm concerned
    because I remember the problems we had setting up the production server
    until we got some of the net.ivp4 settings correct.
    --
    http://www.freelists.org/webpage/oracle-l
  • John Piwowar at Dec 23, 2009 at 5:17 pm
    Sandra,

    As Rich suggests, it's possible that the agent hasn't collected kernel
    parameter settings recently. I'm going by pre-coffee memory here, but there
    should be a list of collected metrics under the "Monitoring Configuration"
    or "Metric and Policy Settings" link at the bottom of the EM page for your
    host that will tell you how frequently a given piece of data is collected.
    It may be that the collection is only done once per week, or month, or even
    disabled, in which case you should definitely disregard what EM is telling
    you favor of the checks you've already performed yourself with sysctl.

    Apologies if you already know this, but if you want to be sure that the
    current kernel settings are going to persist through the next server boot,
    you check the permanent settings in 3 possible places: /etc/sysctl.conf (as
    already mentioned), /etc/sysconfig/oracle (if you're using the SUSE
    orarun.rpm), and /etc/init.d/boot.local. I have't seen that last one used
    in a while, thankfully, but you never know. :)

    --

    Regards,

    John P.
    On Wed, Dec 23, 2009 at 3:20 PM, Sandra Becker wrote:


    I ran the commands to look at the parameters myself and I can't see any
    differences between the sysctl.conf files nor from running "sysctl
    -a|grep.... SAs are refusing to look at it anymore because they say it's
    correct. Is it possible that EM is incorrectly reporting the values? Is
    there some kind of refresh I need to do before the compare? I'm concerned
    because I remember the problems we had setting up the production server
    until we got some of the net.ivp4 settings correct.
    --
    Sandy
    Transzap, Inc.
    --
    http://www.freelists.org/webpage/oracle-l
  • Sandra Becker at Dec 23, 2009 at 5:54 pm

    Thanks for all the help. I had to stop/restart the agent on the standby
    server. Once it uploaded, everything was ok.

    --
    Sandy
    Transzap, Inc.

Related Discussions

Discussion Navigation
viewthread | post
Discussion Overview
grouporacle-l @
categoriesoracle
postedDec 22, '09 at 9:47p
activeDec 23, '09 at 5:54p
posts8
users6
websiteoracle.com

People

Translate

site design / logo © 2022 Grokbase