background preloader

Ganglia Monitoring System

Ganglia Monitoring System

www.myoracleworld.net - Setup a yum or up2date repository to use a locally mounted DVD Solution: For RH5/6 do the following: Mount the RH6 ISO as /mnt/mntisoimage using the command below mount -t iso9660 -o loop /root/rpm/rhel-server-6.0-x86_64-dvd.iso /mnt/isoimage/ Create a dvd.repotext file in /etc/yum.repos.d/with the following content: [dvd] mediaid=1285193176.460470* name=DVD for RHEL6 baseurl= enabled=1 gpgcheck=0 (*) The mediaid= value comes from the .discinfo file located in the root of the DVD. [root@rh6pw7 yum.repos.d]# more /mnt/isoimage/.discinfo 1285193176.460470 Red Hat Enterprise Linux 6.0 x86_64 1 If problems occur while trying this procedure, run yum clean all and try running yum install again. Note: This will only work for the "base" rpm pakages under the /Server directory; if access is needed to the rest of the software in the Red Hat Enterprise Linux Server DVD (Cluster, ClusterStorage and VT), add the following stanzas to the dvd.repo file: Dependencies Resolved

artoftheproblem Course Catalog Online Shopping India - Buy Books, Mobile Phones, Digital Cameras, Laptops, Watches & Other Products @ FlipKart Oracle in World MySQL: Using Views as Performance Improvement Tools | ovais.tariq The most basic and most oft-repeated task that a DBA has to accomplish is to look at slow logs and filter out queries that are suboptimal, that consume lots of unnecessary resources and that hence slow down the database server. The most obvious reason for these suboptimal queries is that their authors are generally not that good at writing complex queries. A DBA has a far better chance of writing an optimal query as compared to any other database user, because a DBA has a better understanding of the internals of the database server (query optimizer, etc). The problem Normally looking at logs, one would find a host of suboptimal operations that are performed, for example the use of SELECT * when you only need a few columns. The solution The most obvious solution to this problem is limiting access to the database, relieving database users of the task of creating optimal queries. Some planning is required

Related: