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

PXE boot a LiveCD image

Summary: I have wanted to build a kickstart environment which hosted a "rescue CD" or LiveCD to allow you to boot over the network after you blew your stuff up and needed to repair a few things.  Today I have worked through a method of doing so, with the help of the people who published a succinct script with the Red Hat Enterprise Virtualization Hypervisor.  (the script will be at the bottom of this post - if I have somehow not followed the GPL, please let me know and I will correct whatever is necessary) NOTE/Warning: The boot will fail due the initrd being too large (645mb).  I'm not sure how to proceed.  This procedure worked for RHEVh, because it is quite a bit smaller.  Hopefully I can report back with progress on this? :-$ Procedure: download your LiveCD image to /export/isos/RESCUE/Fedora-16-i686-Live-Desktop.iso # cd /var/tmp # vi livecd-iso-to-pxeboot (populate the file with the script shown below) # chmod 754 ./livecd-iso-to-pxeb...

"Error getting authority: Error initializing authority: Could not connect: No such file or directory (g-io-error-quark, 1)"

"Error getting authority: Error initializing authority: Could not connect: No such file or directory (g-io-error-quark, 1)" One issue that may cause this to arise is if you managed to break your /etc/fstab We had an engineer add a line with the intended options of "nfsvers=3" but instead added "-onfsvers=3" and it broke the system fairly catastrophically.

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...