Skip to main content

More Satellite Foo - Database Edition

This particular post should not be taken lightly, nor implemented without consideration.  I believe our situation might be a bit different than most in that we rely on the clients to "pull" from the Satellite (using rhnsd and rhn_check).  I believe a better solution is to use OSAD - but at this point I am uneducated on such magic. :-(

The goal here is to increase the number of Oracle DB connections.


/bin/sqlplus rhnsat/rhnsat@rhnsat

== Check number of Oracle Processes
[root@rhnsat01 ~]# su - oracle
-bash-3.2$  ORACLE_SID=rhnsat sqlplus /nolog

SQL*Plus: Release 10.2.0.4.0 - Production on Tue Jul 16 12:03:19 2013

Copyright (c) 1982, 2007, Oracle.  All Rights Reserved.

SQL> connect
Enter user-name: XXXYYY
Enter password:
Connected.
SQL> show parameter process;

NAME                     TYPE     VALUE
------------------------------------ ----------- ------------------------------
aq_tm_processes              integer     0
db_writer_processes             integer     2
gcs_server_processes             integer     0
job_queue_processes             integer     10
log_archive_max_processes         integer     2
processes                 integer     400

SQL> show parameter sessions;

NAME                     TYPE     VALUE
------------------------------------ ----------- ------------------------------
java_max_sessionspace_size         integer     0
java_soft_sessionspace_limit         integer     0
license_max_sessions             integer     0
license_sessions_warning         integer     0
logmnr_max_persistent_sessions         integer     1
sessions                 integer     445
shared_server_sessions             integer

== Update the number of processes 

# su - oracle
$ ORACLE_SID=rhnsat sqlplus /nolog
SQL*Plus: Release 10.2.0.4.0 - Production on Tue Jul 16 11:53:38 2013

Copyright (c) 1982, 2007, Oracle.  All Rights Reserved. 
SQL> alter system set processes=300 scope=spfile;
SQL> commit; 

$ exit
# /usr/sbin/rhn-satellite restart 

Comments

Popular posts from this blog

P2V using dd for KVM-QEMU guest

Preface: I have certainly not exhaustively tested this process.  I had a specific need and found a specific solution that worked. Situation:  I was issued a shiny new laptop running Red Hat Enterprise Linux 7 (with Corp VPN, certs, Authentication configuration, etc...)  The image was great, but I needed more flexibility on my bare metal.  So, my goal was to P2V the corporate image so I could just run it as a VM. * Remove corporate drive and install new SSD * install corp drive in external USB-3 case * Install RHEL 7 on new SSD * dd old drive to a disk-image file in a temp location which will be an image which is the same size as your actual drive (unless you have enough space in your destination to contain a temp and converted image) * convert the raw disk-image to a qcow file while pushing it to the final location - this step should reduce the disk size - however, I believe it will only reduce/collapse zero-byte blocks (not just free space - i.e. if you de...

Sun USS 7100 foo

TIP: put ALL of your LUNs into a designated TARGET and INITIATOR group when you create them.  If you leave them in the "default" group, then everything that does an discovery against the array will find them :-( I'm struggling to recognize a reason that a default should even be present on the array. Also - who, exactly, is Sun trying to kid.  The USS is simply a box.. running Solaris .. with IPMP and ZFS.  Great.  If you have ever attempted to "break-in" or "p0wn" your IBM HMC, you know that there are people out there that can harden a box - then.. there's Sun.  After a recent meltdown at the office I had to get quite intimate with my USS 7110 and learned quite a bit.  Namely: there's a shell ;-) My current irritation is how they attempt to "warn you" away from using the shell (my coverage expired a long time ago to worry about that) and then how they try to hide things, poorly. I was curious as to what version of SunOS it ...

Extending SNMP to run arbitrary shell script

Why are we here... This is not likely something I would have pursued under normal circumstances.  I happen to be working for a customer/client who is not afforded a lot of flexibility to accomplish their goals.  In this case, the rigor is justified.  They have to sometimes be fairly creative with how they solve problems. In this case they would like to utilize an existing snmp implementation to execute a command (or shell script) on a remote system.  They came to me with the idea of using Net-SNMP extend. https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Deployment_Guide/sect-System_Monitoring_Tools-Net-SNMP-Extending.html NOTE:  This is NOT a good implementation strategy in the "real world"  it will simply allow you to test the functionality.  There are a TON of security implications which would need to be taken in to consideration. Implementation Steps: [root@rh7tst01 ~]# yum -y install net-snmp net-snmp-utils ...