Archive for the ‘Philosophic’ Category

Why are we using root cause analysis?

February 19, 2013 1 comment

RCA stands for Root-Cause Analysis. Why are we using RCA or specifically, why we are using RCA in operation.

It is clear that documenting, archiving, publishing RCA, helps to solve problems faster in re-occurences of problems.

But the there seems to be a deeper philosophy behind…

While looking at Project Management Quality Management topics in Rita Mulcahy(RIP), I see a good principle which may help us in future problems.


The 80 percent of problems are due to 20 percent of the root causes. [Pareto Principle, 80/20 principle by Joseph Juran]

If this is real then solving 20 percent of root causes will solve our 80 percent of our problems. So why not find and deal with those big fishes… Or preventing them before occuring.


Infrastructure Consolidation Projects

November 10, 2012 1 comment

What is consolidation? At first, it seems a process which enables making things with smaller number of resources.

Below picture that depicts the economy of using one resource, one jar, for many fish, which forms a real motivation to managers, and initial understanding of the concept.

I had a chance to coordinate and enroll in operational standardization, consolidation projects.

At first glance,  you may wonder why do we need consolidation or normalization projects? We may find the answers with more questions like following… Why systems fall in a state that are not economically operable? Why whole service responsibility is given on one or two super-persons who never gets ill, or goes to holiday,  having roles like database administration, application server administration, hardware&software procurement, application administration etc? Why not divide and conquer responsibility of service management? Why do we try to use one resource for all problems?

Why people tends to put one fish in one jar, instead of putting more fish in one jar. This maybe because of less knowledge/specialization/expertise in operation, fast, unplanned installations, badly managed projects and vendor driven configurations/installations for applications/services.

Let’s continue on consolidation projects… They took place among different divisions, teams, outsource companies, and tens of people, having goal of responsibility transition to several technology specialized groups such as database, application server, disk, test, security, resource management, procurement  from single responsible group.

After consolidating/normalizing our service/application infrastructure we found a pot of gold, here comes, what is in this pot:

– Opportunity to technology improvement like filesystem to ASM, legacy Sun Cluster to Oracle RAC. It is an opportunity, because you are not renovating, it is a process that designing the underlying infrastructure from scratch.

– Decreasing the number of hardware & software, licenses, operation personnel which lead great savings, which means decreasing OPEX (operational expenditure).

– Combining above two issues, recall that technology inevitably occurs in infrastructure every 3-5 years, due to organic growth of business, and maintenance cost increase, and manager’s will to prefer CAPEX with compared to OPEX.

– Have a chance to harden the underlying infrastructure, because we deal with fewer system. Hardening matrix example

– Adopt “service” concept to infrastructure, for example an application will go to database infrastructure over application server with its database service connection. This lead flexibility in locating services to database instances.

– Applying operational standards (backup, maintenance, patch, etc.), database security standards, change management, not using production for everything, change through development to test and to production environments.

– Compliance with security standards. In our case, compliance with ISO and SOX security requirements. Enabling segregation of duties or simply separation of duties. Centrify, guardium like technologies makes things easy.

– Specialization in operations: Special tasks must be operated by specialized people, in order to make it faster with high quality.

– At last, which is simpler? Defending tens of castles or only one. Such as monitoring a large database, application server, is always a lot more easier than managing tens of them. For example, you will only get one RMAN backup, instead of ten; this is not only database task, but also backup, and first line monitoring task. You could increase the examples for application server administration, Oracle Gateway administration, Oracle EM grid agent administration etc.

A picture which may lead understanding the compliance to security/operational standards, shows the real outcome value of consolidation projects. This is like putting the fish in a bag, and changing the water again and again because it is impossible to use air pump due to its cost or technology. Why not put these fish to modern aquarium with air pump, light, plants, thick glass.

I want to add more words for specialization… In Turkish, there is a saying, “If you own only a hammer, everything seems nail to you.” In real world, do you really have only hammer in your hand, and  nails to be nailed… or specialized tools like screw driver, pliers, saw for screwing a screw, gripping/bending a copper cable, cutting woods etc? You must utilize from specialized tools, people, in your systems… You must divide your service into specialized responsibility areas…

Why PLSQL is efficient than any other PL on Oracle database?

August 1, 2012 Leave a comment

12 years ago when I argued on the performance of  Programming Languages with an experienced Java programmer, who was developing CORBA like communication infrastructure and preferring only Java, confessed that a dba might develop better performance code than him in PLSQL.

In Turkish, there is a saying “tools work, hands take pride on”.  So why not use PLSQL much more…

PLSQL is really on database and closer to database layer any other Programming Languae could manage to be .

After years passed, using SQL instead of PLSQL was my first goal while implementing any requirement.

I had first seen below statement nearly 1 year ago, and it really fit my thoughts which I have not been clearly stated before. I really appreciated it and compelled to get my knowledge world.

My mantra, that I’ll be sticking with thank you very much, is:

  • You should do it in a single SQL statement if at all possible.
  • If you cannot do it in a single SQL Statement, then do it in PL/SQL.
  • If you cannot do it in PL/SQL, try a Java Stored Procedure.
  • If you cannot do it in Java, do it in a C external procedure.
  • If you cannot do it in a C external routine, you might want to seriously think about why it is you need to do it…

hello world from wordpress!

September 4, 2007 Leave a comment

Streams makes lake, many smalls make big! Then share, share, share… Many people even experts still continue to learn from others, learners live! I started this blog because I want to log what I learnt, and share with the Oracle community.

Categories: Philosophic
Don Charisma

because anything is possible with Charisma

Carol no Mundo!

Aventuras de uma intercambista a trabalho pelo mundo!

Blog do PHP

Oracle DBA for rookies!


Welcome to the world of Oracle with me....


News and reviews from the world of gadgets, gear, apps and the web is the best place for your personal blog or business site.

Gurcan Orhan's ODI and DWH Blog

Some words about Oracle Data Integrator and Data Warehousing.