Blog

Managing SQL Query Time using Oracle Database Resource Manager

Session Control with Oracle Database Resource Manager

The Oracle Database Resource Manager (DBRM) provides a wealth of functionality to control what user workloads are able to consume server and database resources. I have recently used the DBRM to provide the following functionality to the application:

  • Provide the ability to limit the duration of reports that are run through the DBMS_SCHEDULER.
  • Provide the ability to cancel and/or limit the duration a query submitted from the application user interface can run.

Oracle Database Operational Design Requirements

I spend a lot of time working on issues of performance and scalability for clients systems. The bulk of this work is around database and application transaction processing as these areas typically have the greatest business visibility. An area that does not seem to have the same level of visibility is how operationally efficient these same environments are – not through neglect however, but as a result of operational support requirements not being included as a part of the core requirements during a design phase.

Streamlining Oracle eBusiness Suite Maintenance

Reducing Oracle eBusiness Suite Maintenance Overhead

Streamlining Oracle eBusiness suite maintenance provides opportunities to reduce system downtime and opportunities for human error.

Those who are responsible for maintaining an Oracle eBusiness Suite environment will be familiar with the adpatch, adadmin and adctrl tools. Any patching or maintenance activities on the Oracle eBusiness Suite application tier will usually require running these tools at some point during the maintenance activities.

Running these tools will also present the usual familiar prompts that require the same keystrokes every single time. This can become a fairly tedious exercise even if you have a single APPL_TOP let alone an environment with multiple application tiers and no shared APPL_TOP.

Oracle Database Flashback Physical Standby

Oracle Flashback Physical Standby Database

This third instalment covering some of the flashback features in Oracle 10g takes a look at combining flashback with using a physical standby. I will take a look at two usage scenarios in which I think could offer significant benefit to anyone using Oracle Database Flashback with a physical standby. This post will cover the use of the physical standby as a read/write copy of a production database.

Oracle Flashback Query

Oracle Flashback Query

The next requirement that I found a very good use for Oracle Flashback Query came about as part of a tuning exercise.

I was working through an issue where an application would use a table to temporarily store data before presenting the data to the client program. What was happening was a classic case of incorrect statistics on the table segment resulting in incorrect SQL execution plans.

Even by using the automatic statistics collection features in Oracle Database 10g this problem would not go away. Basically the application performed the following across multiple sessions:

  1. Populate table with data.
  2. Query data to present to user.
  3. Delete data from table.