This single script provides the overall picture of the database in terms of Waits events, Active/Inactive killed sessions, Top Processes (physical I/O, logical I/O, memory and CPU processes), Top CPU usage by users, etc.

[code]set serveroutput on
declare
cursor c1 is select version
from v$instance;
cursor c2 is
select
host_name
, instance_name
, to_char(sysdate, 'HH24:MI:SS DD-MON-YY') currtime
, to_char(startup_time, 'HH24:MI:SS DD-MON-YY') starttime
from v$instance;
cursor c4 is
select * from (SELECT count(*) cnt, substr(event,1,50)

There are three levels of reporting currencies.
Subledger, Journal and Balance.

The data will be create for those ledgers, when the following processes have been run.
Create Accounting - Journals will be created in SLA.
Transfer to GL & Journal Import - Journals will be created in GL.
Post to GL - Balances will be created / updated in GL.

Subledger Level - It maintains data in SLA for ALC also, you can view the accounting in SLA OA pages and other reports.

Oracle 11.2.0.3, the second patch set for the 11gR2 database, is now certified with with E-Business Suite and is available for download in 32 and 64-bit.

You can download it from only your meta link account credential.

Patch No: 10404530

Oracle E-Business Suite Release 11i

Prerequisites

* 11.5.10.2 + ATG PF.H RUP 6 and higher

Certified Platforms

* Linux x86 (Oracle Linux 4, 5)
* Linux x86 (RHEL 4, 5)
* Linux x86 (SLES 10)
* Linux x86-64 (Oracle Linux 4, 5)

EPractize Labs Software, an emerging global provider for Java Certification Preparation released world’s first exam study guide (Training Lab) for Oracle Certified Associate, Java SE 7 Programmer certification. Download your FREE copy today and empower your preparation.

Oracle offers variety of Java Certifications for all Java Editions (Java SE, Java EE and Java ME).

Why do you sometimes not get partitionwise joins? Because the optimizer isn't clever enough. Reference partitioning has many benefits, one of which is that the optimizer understands it. You will always get a partitionwise join if your tables are reference partitioned.

Oracle offers variety of Java Certifications for all Java Editions (Java SE, Java EE and Java ME).

When we launch a long operation, such as a RMAN backup or rebuild of a large index, we can come to despair of not having an estimate of the time it may take. We can even come to think that is doing nothing.

For the progress of a long operation we can query the view V$SESSION_LONGOPS, first obtaining the process ID from V$SESSION. In the case of DBA, we know exactly which user is rebuilding the index, so we can simplify it into a single query.

The following example shows the progress of the reconstruction of a partition of an index.

Several times I have had to deal with people who do not want to define constraints. I have never understood why they don't, because my experience is that the more constraints you can define, the better Oracle will perform. If anyone knows where the idea that not defining constraints is a Good Thing comes from, I would be interested to know.

Following are two very simple examples of constraints allowing the optimizer to develop better plans.

First, foreign key constraints. These give the optimizer a lot of information about the data that may mean it can cut out whole tables from a query.

One of the great features about partitioning, and most specifically range-based partitioning, is the ability to load data quickly and easily with minimal impact on the current users using:

alter table call exchange partition data_2007 with table call_temp;

Star Transformation in Siebel Analytics (OBIEE)

(Subrata Dass)

Introduction

Star Transformation is a join method mostly used in Data Warehousing Environments to fine tune typical query performance. It is of utmost importance in DB environments where reporting tools like Siebel Analytics (OBIEE) is in use. It can also be used for other tools such as Business Objects. The conventional join mechanisms that the star transformation seeks to supersede are Hash join, nested-loops and sort merge join.

This paper shows how to take full advantage of this RDBMS feature.