Oracle 22.214.171.124, 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
* 126.96.36.199 + ATG PF.H RUP 6 and higher
* Linux x86 (Oracle Linux 4, 5)
* Linux x86 (RHEL 4, 5)
* Linux x86 (SLES 10)
* Linux x86-64 (Oracle Linux 4, 5)
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.
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)
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.
In this article I will tell you how you can make a dynamic List of values in oracle forms builder, most developer use many techniques to make List of values.
This post is to discuss about the Best Practices that was followed in implementing a new Self Service Applications using OA Framework.
A College needed a web based enrollment system for its students to enroll online without needing to fill up a paper. This was designed for a new i-module for Student Enrolment was developed in OA Framework, using jDeveloper,Rapid Application Development Environment. The benefits of the RAD environment and OA Framework Technology was well utilized to meet the deadlines.
The main challenges faced by the project were , I identification of a roadmap to transform existing system and there was no proper oracle documentation on how to develop a transaction page in OA Framework.
LOBs deal with unstructured data, the ones which are the most difficult to store and retrieve in a relational database.
In this article, I am going to discuss extensively and manipulate the ORACLE
* LOBs that are stored in the database itself like BLOB,CLOB,NCLOB ,and
* LOBs like BFILE which are Stored outside the database as Operating System files.
First let us create a directory :
create or replace directory my_dir as 'D:\pics';
BFILEs act as a pointer and store the location of the external OS files in database tables.
For any company the most important asset is data and the most challenging job is to recovery the database with less downtime with out any data loss, in the event of database failure. In many situations users end up with incomplete recovery of the database with out knowing which data files backed and which data files need to backup. You should ensure that your database is backed up efficiently and should restore successfully when needed. The RMAN reporting provides effective and easy way to determine database backup for a successful recovery.