<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/xsl" media="screen" href="/~d/styles/atom10full.xsl"?><?xml-stylesheet type="text/css" media="screen" href="http://feeds.feedburner.com/~d/styles/itemcontent.css"?><feed xmlns="http://www.w3.org/2005/Atom" xmlns:openSearch="http://a9.com/-/spec/opensearch/1.1/" xmlns:georss="http://www.georss.org/georss" xmlns:gd="http://schemas.google.com/g/2005" xmlns:thr="http://purl.org/syndication/thread/1.0" xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0" gd:etag="W/&quot;AkYEQ3c9eyp7ImA9WhRbEU0.&quot;"><id>tag:blogger.com,1999:blog-6848529073191969237</id><updated>2012-02-01T15:55:02.963+01:00</updated><category term="linux" /><category term="sap" /><category term="HA" /><category term="load balancing" /><category term="java" /><category term="sql" /><category term="php" /><category term="performance" /><category term="reconnoiter" /><category term="pound" /><category term="drcp" /><category term="oracle" /><category term="hadoop" /><title>Marmota Technica</title><subtitle type="html">Short articles about Systems architecture, Oracle, PHP, Web servers, performance, scalability and high availability.</subtitle><link rel="http://schemas.google.com/g/2005#feed" type="application/atom+xml" href="http://blog.taborsky.cz/feeds/posts/default" /><link rel="alternate" type="text/html" href="http://blog.taborsky.cz/" /><author><name>Michal Taborsky</name><uri>https://profiles.google.com/104538853785693278179</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="//lh3.googleusercontent.com/-2Rv4AdgInvU/AAAAAAAAAAI/AAAAAAABCGg/3y_nFknZ14M/s512-c/photo.jpg" /></author><generator version="7.00" uri="http://www.blogger.com">Blogger</generator><openSearch:totalResults>10</openSearch:totalResults><openSearch:startIndex>1</openSearch:startIndex><openSearch:itemsPerPage>25</openSearch:itemsPerPage><atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="self" type="application/atom+xml" href="http://feeds.feedburner.com/MarmotaTechnica" /><feedburner:info uri="marmotatechnica" /><atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="hub" href="http://pubsubhubbub.appspot.com/" /><entry gd:etag="W/&quot;Ak4FQXoyeCp7ImA9WhRTFU8.&quot;"><id>tag:blogger.com,1999:blog-6848529073191969237.post-7400708317569715261</id><published>2011-11-05T22:35:00.000+01:00</published><updated>2011-11-05T22:35:10.490+01:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2011-11-05T22:35:10.490+01:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="java" /><category scheme="http://www.blogger.com/atom/ns#" term="reconnoiter" /><category scheme="http://www.blogger.com/atom/ns#" term="hadoop" /><title>JMX metrics in Reconnoiter</title><link rel="replies" type="application/atom+xml" href="http://blog.taborsky.cz/feeds/7400708317569715261/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://blog.taborsky.cz/2011/11/jmx-metrics-in-reconnoiter.html#comment-form" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/6848529073191969237/posts/default/7400708317569715261?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/6848529073191969237/posts/default/7400708317569715261?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/MarmotaTechnica/~3/sJJOVPvAuzU/jmx-metrics-in-reconnoiter.html" title="JMX metrics in Reconnoiter" /><author><name>Michal Taborsky</name><uri>https://profiles.google.com/104538853785693278179</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="//lh3.googleusercontent.com/-2Rv4AdgInvU/AAAAAAAAAAI/AAAAAAABCGg/3y_nFknZ14M/s512-c/photo.jpg" /></author><thr:total>0</thr:total><content type="html">We started using Hadoop, written in Java and it exposes it's metrics thru JMX, which is a Java standard for monitoring and metrics publishing. Since we use Reconnoiter for all other metrics collection and graphing, I wanted to get this JMX data into it.

Reconnoiter has a Java component, called Jezebel, that functions as a bridge between Java world and Reconnoiter. What it does is it listens on 
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/gko1vqkRrJKEeW-aHMTWo_p83Po/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/gko1vqkRrJKEeW-aHMTWo_p83Po/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/gko1vqkRrJKEeW-aHMTWo_p83Po/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/gko1vqkRrJKEeW-aHMTWo_p83Po/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/MarmotaTechnica/~4/sJJOVPvAuzU" height="1" width="1"/&gt;</content><feedburner:origLink>http://blog.taborsky.cz/2011/11/jmx-metrics-in-reconnoiter.html</feedburner:origLink></entry><entry gd:etag="W/&quot;AkQFQ3Y8eSp7ImA9WhZTFU8.&quot;"><id>tag:blogger.com,1999:blog-6848529073191969237.post-7910203892503483070</id><published>2011-03-19T10:51:00.000+01:00</published><updated>2011-03-19T10:51:52.871+01:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2011-03-19T10:51:52.871+01:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="reconnoiter" /><category scheme="http://www.blogger.com/atom/ns#" term="drcp" /><category scheme="http://www.blogger.com/atom/ns#" term="php" /><category scheme="http://www.blogger.com/atom/ns#" term="oracle" /><title>DRCP Monitoring with Reconnoiter</title><link rel="replies" type="application/atom+xml" href="http://blog.taborsky.cz/feeds/7910203892503483070/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://blog.taborsky.cz/2011/03/drcp-monitoring-with-reconnoiter.html#comment-form" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/6848529073191969237/posts/default/7910203892503483070?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/6848529073191969237/posts/default/7910203892503483070?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/MarmotaTechnica/~3/bSl17OLmdas/drcp-monitoring-with-reconnoiter.html" title="DRCP Monitoring with Reconnoiter" /><author><name>Michal Taborsky</name><uri>https://profiles.google.com/104538853785693278179</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="//lh3.googleusercontent.com/-2Rv4AdgInvU/AAAAAAAAAAI/AAAAAAABCGg/3y_nFknZ14M/s512-c/photo.jpg" /></author><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="https://lh6.googleusercontent.com/-OWEytldw240/TYPY150HuPI/AAAAAAAA99Q/k3Px-_KRMhc/s72-c/ora-drcp.png" height="72" width="72" /><thr:total>0</thr:total><content type="html">This is a second part of my previous article Collecting Oracle metrics with Reconnoiter.

If you are using Database Resident Connection Pooling (DRCP) for connecting your application to Oracle Database (and if you are serious about scalability you should), then you probably know about the (G)V$CPOOL_STATS view, which shows the usage statistics of the pool, such as number of succesful connections 
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/X9gE5cSUFFuOx_M1RU4Vpip5rc4/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/X9gE5cSUFFuOx_M1RU4Vpip5rc4/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/X9gE5cSUFFuOx_M1RU4Vpip5rc4/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/X9gE5cSUFFuOx_M1RU4Vpip5rc4/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/MarmotaTechnica/~4/bSl17OLmdas" height="1" width="1"/&gt;</content><feedburner:origLink>http://blog.taborsky.cz/2011/03/drcp-monitoring-with-reconnoiter.html</feedburner:origLink></entry><entry gd:etag="W/&quot;A08NQn46eyp7ImA9Wx9aF00.&quot;"><id>tag:blogger.com,1999:blog-6848529073191969237.post-3570289941427303025</id><published>2011-03-09T21:34:00.003+01:00</published><updated>2011-03-09T23:31:33.013+01:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2011-03-09T23:31:33.013+01:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="reconnoiter" /><category scheme="http://www.blogger.com/atom/ns#" term="php" /><category scheme="http://www.blogger.com/atom/ns#" term="oracle" /><title>Collecting Oracle metrics with Reconnoiter</title><link rel="replies" type="application/atom+xml" href="http://blog.taborsky.cz/feeds/3570289941427303025/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://blog.taborsky.cz/2011/03/collecting-oracle-metrics-with.html#comment-form" title="3 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/6848529073191969237/posts/default/3570289941427303025?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/6848529073191969237/posts/default/3570289941427303025?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/MarmotaTechnica/~3/kwC9iW9ieAY/collecting-oracle-metrics-with.html" title="Collecting Oracle metrics with Reconnoiter" /><author><name>Michal Taborsky</name><uri>https://profiles.google.com/104538853785693278179</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="//lh3.googleusercontent.com/-2Rv4AdgInvU/AAAAAAAAAAI/AAAAAAABCGg/3y_nFknZ14M/s512-c/photo.jpg" /></author><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="https://lh4.googleusercontent.com/-4iIp_WtTsjI/TXdpR3ZNwoI/AAAAAAAA9tk/r4PftjwjazU/s72-c/resmon-ora.png" height="72" width="72" /><thr:total>3</thr:total><content type="html">Oracle database makes your life, as an operator, easier by measuring and providing tons of metrics. These metrics range from wait time counters, thru I/O operations and sizes to number of failed logins. Each new version adds even more useful metrics. For example, Oracle 11gR2 collects 628 different metrics.

These metrics are generally available thru the (G)V$SYSSTAT system view. This view can be
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/JNw_z5GgBtzT6A-kAGlftguHbLg/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/JNw_z5GgBtzT6A-kAGlftguHbLg/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/JNw_z5GgBtzT6A-kAGlftguHbLg/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/JNw_z5GgBtzT6A-kAGlftguHbLg/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/MarmotaTechnica/~4/kwC9iW9ieAY" height="1" width="1"/&gt;</content><feedburner:origLink>http://blog.taborsky.cz/2011/03/collecting-oracle-metrics-with.html</feedburner:origLink></entry><entry gd:etag="W/&quot;CUUBRXk6fSp7ImA9WxBUFUs.&quot;"><id>tag:blogger.com,1999:blog-6848529073191969237.post-5273737507821666683</id><published>2010-03-02T20:03:00.013+01:00</published><updated>2010-03-02T21:54:14.715+01:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2010-03-02T21:54:14.715+01:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="performance" /><category scheme="http://www.blogger.com/atom/ns#" term="php" /><title>Hidden errors in PHP affect performance</title><link rel="replies" type="application/atom+xml" href="http://blog.taborsky.cz/feeds/5273737507821666683/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://blog.taborsky.cz/2010/03/hidden-errors-in-php-affect-performance.html#comment-form" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/6848529073191969237/posts/default/5273737507821666683?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/6848529073191969237/posts/default/5273737507821666683?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/MarmotaTechnica/~3/rgCGR2atfZM/hidden-errors-in-php-affect-performance.html" title="Hidden errors in PHP affect performance" /><author><name>Michal Taborsky</name><uri>https://profiles.google.com/104538853785693278179</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="//lh3.googleusercontent.com/-2Rv4AdgInvU/AAAAAAAAAAI/AAAAAAABCGg/3y_nFknZ14M/s512-c/photo.jpg" /></author><thr:total>0</thr:total><content type="html">I've come across an interesting thing recently, that I didn't think mattered, but, as I'm about to demonstrate, it does. So we all know about different levels of error reporting in PHP, right? We all know, that we must pay close attention to E_WARNING and above, and sometimes the occasional E_NOTICE carries some wisdom. (Almost) nobody cares about those annoying E_STRICT messages. In fact, even 
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/k4kSUUvBzQk3XhxyP8RSdVUHCkM/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/k4kSUUvBzQk3XhxyP8RSdVUHCkM/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/k4kSUUvBzQk3XhxyP8RSdVUHCkM/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/k4kSUUvBzQk3XhxyP8RSdVUHCkM/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/MarmotaTechnica/~4/rgCGR2atfZM" height="1" width="1"/&gt;</content><feedburner:origLink>http://blog.taborsky.cz/2010/03/hidden-errors-in-php-affect-performance.html</feedburner:origLink></entry><entry gd:etag="W/&quot;DkIDQXo7cCp7ImA9WhRRFks.&quot;"><id>tag:blogger.com,1999:blog-6848529073191969237.post-5568894751348056998</id><published>2009-07-30T22:47:00.003+02:00</published><updated>2011-11-30T15:49:30.408+01:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2011-11-30T15:49:30.408+01:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="performance" /><category scheme="http://www.blogger.com/atom/ns#" term="oracle" /><title>Index usage monitoring in Oracle</title><link rel="replies" type="application/atom+xml" href="http://blog.taborsky.cz/feeds/5568894751348056998/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://blog.taborsky.cz/2009/07/index-usage-monitoring-in-oracle.html#comment-form" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/6848529073191969237/posts/default/5568894751348056998?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/6848529073191969237/posts/default/5568894751348056998?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/MarmotaTechnica/~3/e0FbLH1dNDw/index-usage-monitoring-in-oracle.html" title="Index usage monitoring in Oracle" /><author><name>Michal Taborsky</name><uri>https://profiles.google.com/104538853785693278179</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="//lh3.googleusercontent.com/-2Rv4AdgInvU/AAAAAAAAAAI/AAAAAAABCGg/3y_nFknZ14M/s512-c/photo.jpg" /></author><thr:total>0</thr:total><content type="html">Indices (or indexes, if you will) are always good, right? Well, Tom Kyte would disagree with you and so would I. In fact, indices will always impede data manipulation performance, so they should be used only where they are useful in queries. But determining if an index is useful can be sometimes pretty difficult, mainly in a complex application with thousands of different queries, some even 
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/GlZ3HcnijEO9LIiLjkzUZHnobk4/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/GlZ3HcnijEO9LIiLjkzUZHnobk4/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/GlZ3HcnijEO9LIiLjkzUZHnobk4/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/GlZ3HcnijEO9LIiLjkzUZHnobk4/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/MarmotaTechnica/~4/e0FbLH1dNDw" height="1" width="1"/&gt;</content><feedburner:origLink>http://blog.taborsky.cz/2009/07/index-usage-monitoring-in-oracle.html</feedburner:origLink></entry><entry gd:etag="W/&quot;DU8ARHw6fyp7ImA9WxJUFkU.&quot;"><id>tag:blogger.com,1999:blog-6848529073191969237.post-7351951052908210509</id><published>2009-07-15T21:21:00.005+02:00</published><updated>2009-07-15T21:57:25.217+02:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2009-07-15T21:57:25.217+02:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="sql" /><category scheme="http://www.blogger.com/atom/ns#" term="performance" /><category scheme="http://www.blogger.com/atom/ns#" term="oracle" /><title>The hunt for the UNKNOWN SQL in Oracle</title><link rel="replies" type="application/atom+xml" href="http://blog.taborsky.cz/feeds/7351951052908210509/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://blog.taborsky.cz/2009/07/hunt-for-unknown-sql-in-oracle.html#comment-form" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/6848529073191969237/posts/default/7351951052908210509?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/6848529073191969237/posts/default/7351951052908210509?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/MarmotaTechnica/~3/iL8APhbGodM/hunt-for-unknown-sql-in-oracle.html" title="The hunt for the UNKNOWN SQL in Oracle" /><author><name>Michal Taborsky</name><uri>https://profiles.google.com/104538853785693278179</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="//lh3.googleusercontent.com/-2Rv4AdgInvU/AAAAAAAAAAI/AAAAAAABCGg/3y_nFknZ14M/s512-c/photo.jpg" /></author><thr:total>0</thr:total><content type="html">If you are looking at your AWR report or browsing thru performance views in your Oracle Enterprise Manager console, chances are, that some of those SQLs, eating at your CPU or I/O bandwidth are marked as UNKNOWN. This is frustrating, to say the least, but in cases when these mysterious queries are killing your database, it may become a matter of life and death to find out just what does the 
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/21p4Ea1vrQ7fKKERsOEUhq-h2YU/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/21p4Ea1vrQ7fKKERsOEUhq-h2YU/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/21p4Ea1vrQ7fKKERsOEUhq-h2YU/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/21p4Ea1vrQ7fKKERsOEUhq-h2YU/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/MarmotaTechnica/~4/iL8APhbGodM" height="1" width="1"/&gt;</content><feedburner:origLink>http://blog.taborsky.cz/2009/07/hunt-for-unknown-sql-in-oracle.html</feedburner:origLink></entry><entry gd:etag="W/&quot;C0UDSHY5cCp7ImA9WxJUEk8.&quot;"><id>tag:blogger.com,1999:blog-6848529073191969237.post-1395075817399080807</id><published>2009-07-10T11:46:00.004+02:00</published><updated>2009-07-10T12:21:19.828+02:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2009-07-10T12:21:19.828+02:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="performance" /><category scheme="http://www.blogger.com/atom/ns#" term="oracle" /><title>Performance analysis reports in Oracle</title><link rel="replies" type="application/atom+xml" href="http://blog.taborsky.cz/feeds/1395075817399080807/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://blog.taborsky.cz/2009/07/performance-analysis-reports-in-oracle.html#comment-form" title="1 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/6848529073191969237/posts/default/1395075817399080807?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/6848529073191969237/posts/default/1395075817399080807?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/MarmotaTechnica/~3/x-GPKEd65M0/performance-analysis-reports-in-oracle.html" title="Performance analysis reports in Oracle" /><author><name>Michal Taborsky</name><uri>https://profiles.google.com/104538853785693278179</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="//lh3.googleusercontent.com/-2Rv4AdgInvU/AAAAAAAAAAI/AAAAAAABCGg/3y_nFknZ14M/s512-c/photo.jpg" /></author><thr:total>1</thr:total><content type="html">Sometimes you wonder why your database is slow or you just want to know what those oompa-loompas inside the Oracle black box are up to. One of the tools in your investigation can be the so-called Automatic Workload Repository, which contains an overload of information about what is going on in your database.Some information from AWR can be seen inside the Enterprise manager console, but for 
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/nuj8wBF_-jbCCCh04eV14NzUY7Q/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/nuj8wBF_-jbCCCh04eV14NzUY7Q/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/nuj8wBF_-jbCCCh04eV14NzUY7Q/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/nuj8wBF_-jbCCCh04eV14NzUY7Q/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/MarmotaTechnica/~4/x-GPKEd65M0" height="1" width="1"/&gt;</content><feedburner:origLink>http://blog.taborsky.cz/2009/07/performance-analysis-reports-in-oracle.html</feedburner:origLink></entry><entry gd:etag="W/&quot;DEIGQ3Y7fCp7ImA9WxJQGUg.&quot;"><id>tag:blogger.com,1999:blog-6848529073191969237.post-8102773099016857703</id><published>2009-06-02T16:45:00.004+02:00</published><updated>2009-06-02T17:28:42.804+02:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2009-06-02T17:28:42.804+02:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="linux" /><category scheme="http://www.blogger.com/atom/ns#" term="oracle" /><title>How to build Oracle Instant client under Linux</title><link rel="replies" type="application/atom+xml" href="http://blog.taborsky.cz/feeds/8102773099016857703/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://blog.taborsky.cz/2009/06/how-to-build-oracle-instant-client.html#comment-form" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/6848529073191969237/posts/default/8102773099016857703?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/6848529073191969237/posts/default/8102773099016857703?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/MarmotaTechnica/~3/KLQo8Wf_YkU/how-to-build-oracle-instant-client.html" title="How to build Oracle Instant client under Linux" /><author><name>Michal Taborsky</name><uri>https://profiles.google.com/104538853785693278179</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="//lh3.googleusercontent.com/-2Rv4AdgInvU/AAAAAAAAAAI/AAAAAAABCGg/3y_nFknZ14M/s512-c/photo.jpg" /></author><thr:total>0</thr:total><content type="html">The Oracle Intant Client is a minimalistic version of necessary runtime libraries needed to run an application which uses an OCI interface to connect to the Oracle database. In this article I will describe how to build your very own Instant client.If you ever installed a full Oracle client, you know how painfull process it is and how much diskspace you need. Especially if you are running a large 
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/yFc4uhiVpk01UnGt6z6RU0tD0qk/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/yFc4uhiVpk01UnGt6z6RU0tD0qk/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/yFc4uhiVpk01UnGt6z6RU0tD0qk/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/yFc4uhiVpk01UnGt6z6RU0tD0qk/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/MarmotaTechnica/~4/KLQo8Wf_YkU" height="1" width="1"/&gt;</content><feedburner:origLink>http://blog.taborsky.cz/2009/06/how-to-build-oracle-instant-client.html</feedburner:origLink></entry><entry gd:etag="W/&quot;A0MGQ3s8fyp7ImA9WxJQFUw.&quot;"><id>tag:blogger.com,1999:blog-6848529073191969237.post-449176999457436002</id><published>2009-05-28T15:38:00.005+02:00</published><updated>2009-05-28T16:03:42.577+02:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2009-05-28T16:03:42.577+02:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="sap" /><category scheme="http://www.blogger.com/atom/ns#" term="php" /><title>Calling SAP RFC from PHP thru message server</title><link rel="replies" type="application/atom+xml" href="http://blog.taborsky.cz/feeds/449176999457436002/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://blog.taborsky.cz/2009/05/calling-sap-rfc-from-php-thru-message.html#comment-form" title="2 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/6848529073191969237/posts/default/449176999457436002?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/6848529073191969237/posts/default/449176999457436002?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/MarmotaTechnica/~3/duwl0jyohyo/calling-sap-rfc-from-php-thru-message.html" title="Calling SAP RFC from PHP thru message server" /><author><name>Michal Taborsky</name><uri>https://profiles.google.com/104538853785693278179</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="//lh3.googleusercontent.com/-2Rv4AdgInvU/AAAAAAAAAAI/AAAAAAABCGg/3y_nFknZ14M/s512-c/photo.jpg" /></author><thr:total>2</thr:total><content type="html">If you have the need to call your SAP R/3 system from PHP (which we do), you have several possibilities to do so. One of them is using the proprietary RFC protocol. Fortunately, there exists a PHP SAPRFC library for this purpose. Because we want high availability and scalability in our SAP, we use multiple application servers and spread the load between them with help from a so called message 
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/3RlsvpS22QjODB-WEB0Fqjjejqk/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/3RlsvpS22QjODB-WEB0Fqjjejqk/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/3RlsvpS22QjODB-WEB0Fqjjejqk/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/3RlsvpS22QjODB-WEB0Fqjjejqk/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/MarmotaTechnica/~4/duwl0jyohyo" height="1" width="1"/&gt;</content><feedburner:origLink>http://blog.taborsky.cz/2009/05/calling-sap-rfc-from-php-thru-message.html</feedburner:origLink></entry><entry gd:etag="W/&quot;C08MRXo_eyp7ImA9WxJQE0k.&quot;"><id>tag:blogger.com,1999:blog-6848529073191969237.post-2631360254779731684</id><published>2009-05-25T23:33:00.011+02:00</published><updated>2009-05-26T14:44:44.443+02:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2009-05-26T14:44:44.443+02:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="performance" /><category scheme="http://www.blogger.com/atom/ns#" term="load balancing" /><category scheme="http://www.blogger.com/atom/ns#" term="HA" /><category scheme="http://www.blogger.com/atom/ns#" term="pound" /><title>Building a load balancer with open source software</title><link rel="replies" type="application/atom+xml" href="http://blog.taborsky.cz/feeds/2631360254779731684/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://blog.taborsky.cz/2009/05/building-load-balancer-with-open-source.html#comment-form" title="1 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/6848529073191969237/posts/default/2631360254779731684?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/6848529073191969237/posts/default/2631360254779731684?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/MarmotaTechnica/~3/z-eE-7_Nn3A/building-load-balancer-with-open-source.html" title="Building a load balancer with open source software" /><author><name>Michal Taborsky</name><uri>https://profiles.google.com/104538853785693278179</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="//lh3.googleusercontent.com/-2Rv4AdgInvU/AAAAAAAAAAI/AAAAAAABCGg/3y_nFknZ14M/s512-c/photo.jpg" /></author><thr:total>1</thr:total><content type="html">So your website has reached a level of traffic, where your old server is getting slower and slower and your users just keep coming and coming. You can always throw more hardware at it, but it gets more and more costly, when you want high performance from a single machine.And then there is the other problem: when your web server dies, your website dies with it. Of course you keep backups of 
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/_yAxl6zwaN2r-YJj28a0sMNoOu8/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/_yAxl6zwaN2r-YJj28a0sMNoOu8/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/_yAxl6zwaN2r-YJj28a0sMNoOu8/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/_yAxl6zwaN2r-YJj28a0sMNoOu8/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/MarmotaTechnica/~4/z-eE-7_Nn3A" height="1" width="1"/&gt;</content><feedburner:origLink>http://blog.taborsky.cz/2009/05/building-load-balancer-with-open-source.html</feedburner:origLink></entry></feed>

