Bigfile 10g

for Bigfile 10g
ASM is not only recommended, but a requirement because of inode issues: "If you create a truly large bigfile tablespace on a traditional file system, you will suffer from horrendous inode locking issues. That is why ASM is not really an optional “
My question is How inode locking issue can negatively effect bigfile issue?

Does the following link answer your question?
http://kevinclosson.wordpress.com/2006/10/30/bigfile-tablspaces-require-asm-huh/

Similar Messages

Bigfile in oracle 10g

Hi All,
I have a bigfile in oracle 10g which is of size 110G and its located in E drive.Now the problem i am facing is Drive E:\ has only 5GB free space left and the considering the data growth 5GB wont sufice long.Other drives in server have sufficient space.As increasing space in E:\drive wont be feasible immediately.Kindly provide your inputs for the same.
Regards
Vijay

Simple solution is drop unwanted objects which are occupying more space.
During table move the data in those tables will not available for some time.
Any indexes on the moved table will need to be rebuilt. The table being
moved will be locked for the duration of the move. Plus, sql run against
the table that tries to use the indexes will fail until they are
rebuilt.
One other point, make sure that you do not have any columns marked as
UNUSED on the table being moved. table that had UNUSED
columns dropped data from a VALID column next to the UNUSED
column.

Oracle 10G New Feature........Part 1

Dear all,
from last couple of days i was very busy with my oracle 10g box,so i think this is right time to
share some intresting feature on 10g and some internal stuff with all of you.
Have a look :-
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Oracle 10g Memory and Storage Feature.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1.Automatic Memory Management.
2.Online Segment Shrink
3.Redolog Advisor, checkpointing
4.Multiple Temporary tablespace.
5.Automatic Workload Repository
6.Active Session History
7.Misc
a)Rename Tablespace
b)Bigfile tablespace
c)flushing buffer cache
8.ORACLE INTERNAL
a)undocumented parameter (_log_blocks_during_backup)
b)X$ view (x$messages view)
c)Internal Structure of Controlfile
1.Automatic memory management
================================
This feature reduce the overhead of oracle DBA.previously mostly time we need to set diff oracle SGA parameter for
better performance with the help of own experience,advice views and by monitoring the behaviour
of oracle database.
this was just time consuming activity.........
Now this feature makes easy life for oracle DBA.
Just set SGA_TARGET parameter and it automatically allocate memory to different SGA parameter.
it focus on DB_CACHE_SIZE
SHARED_POOL_SIZE
LARGE_POOL
JAVA_POOL
and automatically set it as
__db_cache_size
__shared_pool_size
__large_pool_size
__java_pool_size
check it in alert_log
MMAN(memory manager) process is new in 10g and this is responsible for sga tuning task.
it automatically increase and decrease the SGA parameters value as per the requirement.
Benefit:- Maximum utlization of available SGA memory.
2.Online Segment Shrink.
==========================
hmmmmm again a new feature by oracle to reduce the downtime.Now oracle mainly focus on availablity
thats why its always try to reduce the downtime by intrducing new feature.
in previous version ,reducing High water mark of table was possible by
Exp/imp
or
alter table move....cmd. but on these method tables was not available for normal use for long hrs if it has more data.
but in 10g with just few command we can reduce the HWmark of table.
this feature is available for ASSM tablespaces.
1.alter table emp enable row movement.
2.alter table emp shrink space.
the second cmd have two phases
first phase is to compact the segment and in this phase DML operations are allowed.
second phase(shrink phase)oracle shrink the HWM of table, DML operation will be blocked at that time for short duration.
So if want to shrink the HWM of table then we should use it with two diff command
first compact the segment and then shrink it on non-peak hrs.
alter table emp shrink space compact. (This cmd doesn't block the DML operation.)
and alter table emp shrink space. (This cmd should be on non-peak hrs.)
Benefit:- better full table scan.
3.Redolog Advisor and checkpointing
================================================================
now oracle will suggest the size of redo log file by V$INSTANCE_RECOVERY
SELECT OPTIMAL_LOGFILE_SIZE
FROM V$INSTANCE_RECOVERY
this value is influence with the value of FAST_START_MTTR_TARGET .
Checkpointing
Automatic checkpointing will be enable after setting FAST_START_MTTR_TARGET to non-zero value.
4.Multiple Temporary tablespace.
==================================
Now we can manage multiple temp tablespace under one group.
we can create a tablespace group implicitly when we include the TABLESPACE GROUP clause in the CREATE TEMPORARY TABLESPACE or ALTER TABLESPACE statement and the specified tablespace group does not currently exist.
For example, if group1 is not exists,then the following statements create this groups with new tablespace
CREATE TEMPORARY TABLESPACE temp1 TEMPFILE '/u02/oracle/data/temp01.dbf'
SIZE 50M
TABLESPACE GROUP group1;
--Add Existing temp tablespace into group by
alter tablespace temp2 tablespace group group1.
--we can also assign the temp tablespace group on database level as default temp tablespace.
ALTER DATABASE <db name> DEFAULT TEMPORARY TABLESPACE group1;
benefit:- Better I/O
One sql can use more then one temp tablespace
5.AWR(Automatic Workload Repository):-
================================== AWR is built in Repository and Central point of Oracle 10g.Oracle self managing activities
is fully dependent on AWR.by default after 1 hr, oracle capure all database uses information and store in AWR with the help of
MMON process.we called it Memory monitor process.and all these information are kept upto 7 days(default) and after that it automatically purge.
we can generate a AWR report by
SQL> @?/rdbms/admin/awrrpt
Just like statspack report but its a advance and diff version of statspack,it provide more information of Database as well as OS.
it show report in Html and Text format.
we can also take manually snapshot for AWR by
BEGIN
DBMS_WORKLOAD_REPOSITORY.CREATE_SNAPSHOT ();
END;
**The STATISTICS_LEVEL initialization parameter must be set to the TYPICAL or ALL to enable the Automatic Workload Repository.
[oracle@RMSORA1 oracle]$ sqlplus / as sysdba
SQL*Plus: Release 10.1.0.2.0 - Production on Fri Mar 17 10:37:22 2006
Copyright (c) 1982, 2004, Oracle. All rights reserved.
Connected to:
Oracle Database 10g Enterprise Edition Release 10.1.0.2.0 - Production
With the Partitioning, OLAP and Data Mining options
SQL> @?/rdbms/admin/awrrpt
Current Instance
~~~~~~~~~~~~~~~~
DB Id DB Name Inst Num Instance
4174002554 RMSORA 1 rmsora
Specify the Report Type
~~~~~~~~~~~~~~~~~~~~~~~
Would you like an HTML report, or a plain text report?
Enter 'html' for an HTML report, or 'text' for plain text
Defaults to 'html'
Enter value for report_type: text
Type Specified: text
Instances in this Workload Repository schema
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
DB Id Inst Num DB Name Instance Host
* 4174002554 1 RMSORA rmsora RMSORA1
Using 4174002554 for database Id
Using 1 for instance number
Specify the number of days of snapshots to choose from
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Entering the number of days (n) will result in the most recent
(n) days of snapshots being listed. Pressing <return> without
specifying a number lists all completed snapshots.
Listing the last 3 days of Completed Snapshots
Snap
Instance DB Name Snap Id Snap Started Level
rmsora RMSORA 16186 16 Mar 2006 17:33 1
16187 16 Mar 2006 18:00 1
16206 17 Mar 2006 03:30 1
16207 17 Mar 2006 04:00 1
16208 17 Mar 2006 04:30 1
16209 17 Mar 2006 05:00 1
16210 17 Mar 2006 05:31 1
16211 17 Mar 2006 06:00 1
16212 17 Mar 2006 06:30 1
16213 17 Mar 2006 07:00 1
16214 17 Mar 2006 07:30 1
16215 17 Mar 2006 08:01 1
16216 17 Mar 2006 08:30 1
16217 17 Mar 2006 09:00 1
Specify the Begin and End Snapshot Ids
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Enter value for begin_snap: 16216
Begin Snapshot Id specified: 16216
Enter value for end_snap: 16217
End Snapshot Id specified: 16217
Specify the Report Name
~~~~~~~~~~~~~~~~~~~~~~~
The default report file name is awrrpt_1_16216_16217.txt. To use this name,
press <return> to continue, otherwise enter an alternative.
Benefit:- Now DBA have more free time to play games.....................:-)
Advance version of statspack
more DB and OS information with self managing capabilty
New Automatic alert and database advisor with the help of AWR.
6.Active Session History:-
==========================
V$active_session_history is view that contain the recent session history.
the memory for ASH is comes from SGA and it can't more then 5% of Shared pool.
So we can get latest and active session report from v$active_session_history view and also get histortical data of
of session from DBA_HIST_ACTIVE_SESS_HISTORY.
v$active_session_history include some imp column like:-
~SQL identifier of SQL statement
~Object number, file number, and block number
~Wait event identifier and parameters
~Session identifier and session serial number
~Module and action name
~Client identifier of the session
7.Misc:-
========
Rename Tablespace:-
=================
in 10g,we can even rename a tablespace by
alter tablespace <tb_name> rename to <tb_name_new>;
This command will update the controlfile,data dictionary and datafile header,but dbf filename will be same.
**we can't rename system and sysaux tablespace.
Bigfile tablespace:-
====================
Bigfile tablespace contain only one datafile.
A bigfile tablespace with 8K blocks can contain a 32 terabyte datafile.
Bigfile tablespaces are supported only for locally managed tablespaces with automatic segment-space management.
we can take the advantage of bigfile tablespace when we are using ASM or other logical volume with RAID.
without ASM or RAID ,it gives poor response.
syntax:-
CREATE BIGFILE TABLESPACE bigtbs
Flushing Buffer Cache:-
======================
This option is same as flushing the shared pool,but only available with 10g.
but i don't know, whats the use of this command in prod database......
anyway we can check and try it on test server for tuning n testing some query etc....
SQL> alter system flush buffer_cache;
System altered.
++++++++++++++++++
8.Oracle Internal
++++++++++++++++++
Here is some stuff that is not related with 10g but have some intresting things.
a)undocumented parameter "_log_blocks_during_backup"
++++++++++++++++++++++++
as we know that oracle has generate more redo logs during hotbackup mode because
oracle has to maintain the a complete copy of block into redolog due to split block.
we can also change this behaviour by setting this parameter to False.
If Oracle block size equals the operating system block size.thus reducing the amount of redo generated
during a hot backup.
WITHOUT ORACLE SUPPORT DON'T SET IT ON PROD DATABASE.THIS DOCUMENT IS JUST FOR INFORMATIONAL PURPOSE.
b)some X$ views (X$messages)
++++++++++++++++
if you are intresting in oracle internal architecture then x$ view is right place for getting some intresting things.
X$messages :-it show all the actions that a background process do.
select * from x$messages;
like:-
lock memory at startup MMAN
Memory Management MMAN
Handle sga_target resize MMAN
Reset advisory pool when advisory turned ON MMAN
Complete deferred initialization of components MMAN
lock memory timeout action MMAN
tune undo retention MMNL
MMNL Periodic MQL Selector MMNL
ASH Sampler (KEWA) MMNL
MMON SWRF Raw Metrics Capture MMNL
reload failed KSPD callbacks MMON
SGA memory tuning MMON
background recovery area alert action MMON
Flashback Marker MMON
tablespace alert monitor MMON
Open/close flashback thread RVWR
RVWR IO's RVWR
kfcl instance recovery SMON
c)Internal Structure of Controlfile
++++++++++++++++++++++++++++++++++++
The contents of the current controlfile can be dumped in text form.
Dump Level Dump Contains
1 only the file header
2 just the file header, the database info record, and checkpoint progress records
3 all record types, but just the earliest and latest records for circular reuse record types
4 as above, but includes the 4 most recent records for circular reuse record types
5+ as above, but the number of circular reuse records included doubles with each level
the session must be connected AS SYSDBA
alter session set events 'immediate trace name controlf level 5';
This dump show lots of intresting information.
it also show rman recordes if we used this controlfile in rman backup.
Thanks
Kuljeet Pal Singh

You can find each doc in html and pdf format on the Documentation Library<br>
You can too download all the documentation in html format to have all on your own computer here (445.8MB)<br>
<br>
Nicolas.

Restore Database to non-ASM Storage - Issue with Bigfile Tablespace

I have been testing a restore of my prod database that uses ASM (and oracle managed files) for storage to a different server and non-ASM storage. Oracle version is 10g EE. My database has one bigfile tablespace and it's datafile is about 250GB. The restore fails and it has something to do with the bigfile tablespace.
Here is the rman restore script:
run
set newname for datafile 1 to '/ora01/db/ehr/system01.dbf';
set newname for datafile 2 to '/ora01/db/ehr/undotbs01.dbf';
set newname for datafile 3 to '/ora01/db/ehr/sysaux01.dbf';
set newname for datafile 4 to '/ora01/db/ehr/undotbs02.dbf';
set newname for datafile 5 to '/ora01/db/ehr/users01.dbf';
set newname for datafile 6 to '/ora01/db/ehr/apolloaud01.dbf';
set newname for datafile 7 to '/ora01/db/ehr/apollohist01.dbf';
set newname for datafile 8 to '/ora01/db/ehr/apolloidx01.dbf';
set newname for datafile 9 to '/ora01/db/ehr/apollotab01.dbf';
set newname for datafile 10 to '/ora01/db/ehr/apollotab02.dbf';
set newname for datafile 11 to '/ora02/db/ehr/apollolob01.dbf';
set newname for datafile 12 to '/ora01/db/ehr/apollofdb01.dbf';
set newname for datafile 13 to '/ora01/db/ehr/apolloidx02.dbf';
set newname for datafile 14 to '/ora01/db/ehr/apolloidx03.dbf';
set newname for datafile 15 to '/ora01/db/ehr/apolloaud02.dbf';
set newname for datafile 16 to '/ora01/db/ehr/apollotab03.dbf';
set until sequence 60298 thread 2;
restore database;
switch datafile all;
recover database;
Datafile 11 is the datafile in the bigfile tablespace. Here are the weird things about the restore:
1. The restore output shows this:
creating datafile fno=11 name=/ora02/db/ehr/apollolob01.dbf
channel ORA_DISK_1: starting datafile backupset restore
channel ORA_DISK_1: specifying datafile(s) to restore from backup set
restoring datafile 00001 to /ora01/db/ehr/system01.dbf
restoring datafile 00002 to /ora01/db/ehr/undotbs01.dbf
restoring datafile 00003 to /ora01/db/ehr/sysaux01.dbf
restoring datafile 00004 to /ora01/db/ehr/undotbs02.dbf
restoring datafile 00005 to /ora01/db/ehr/users01.dbf
restoring datafile 00006 to /ora01/db/ehr/apolloaud01.dbf
restoring datafile 00007 to /ora01/db/ehr/apollohist01.dbf
restoring datafile 00008 to /ora01/db/ehr/apolloidx01.dbf
restoring datafile 00009 to /ora01/db/ehr/apollotab01.dbf
restoring datafile 00010 to /ora01/db/ehr/apollotab02.dbf
restoring datafile 00012 to /ora01/db/ehr/apollofdb01.dbf
restoring datafile 00013 to /ora01/db/ehr/apolloidx02.dbf
restoring datafile 00014 to /ora01/db/ehr/apolloidx03.dbf
restoring datafile 00015 to /ora01/db/ehr/apolloaud02.dbf
restoring datafile 00016 to /ora01/db/ehr/apollotab03.dbf
Why at the beginning is it "creating" datafile 11? Then it doesnt even say it is "restoring" that datafile. Only restoring datafiles 1,2,3,4,5,6,7,8,9,10,12,13,14,15, and 16.
When it creates datafile 11 it is only 26GB, that is much smaller than it should be according to v$datafile view on source prod database. Also even though it says it is creating datafile 11 as /ora02/db/ehr/apollolob01.dbf it actually creates it as an oracle managed file at /ora02/db/ehr/EHR/datafile/o1_mf_apollolo_6crxyqs2_.dbf
After the datafiles are restored the "switch datafile all" command fails:
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of switch command at 10/18/2010 13:58:37
ORA-19625: error identifying file /ora02/db/ehr/apollolob01.dbf
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3
So my question is how do I get this database restored to non-ASM (and non omf)?

So I tried using a different scn with my "set until scn #####" then the restore created 2 datafiles. The datafile for apollolob and apollotab02.dbf. So I think I have narrowed the problem to be that I am not using the correct scn number so RMAN can successfully restore those datafiles and recreates them instead. How do I find the correct scn to use to do a successful restore of the entire database? I have seen different methods on the web, but cant figure it out. Ive used "select archivelog_change#-1 from v$database;" and I also did "list backup of archivelog all" and used the latest sequence number. How can I find the correct scn to use so the entire database will restore?
Here is the output of "list backup":
List of Backup Sets
===================
BS Key Size Device Type Elapsed Time Completion Time
19724 41.12M DISK 00:00:10 14-OCT-10
BP Key: 65840 Status: AVAILABLE Compressed: YES Tag: TAG20101014T210022
Piece Name: /mnt/migrate/rman/EHR_dbid3632734257_set113195_piece1_copy1_20101014
List of Archived Logs in backup set 19724
Thrd Seq Low SCN Low Time Next SCN Next Time
1 50439 3230234843 14-OCT-10 3230268282 14-OCT-10
1 50440 3230268282 14-OCT-10 3230286806 14-OCT-10
2 60280 3230234852 14-OCT-10 3230251419 14-OCT-10
2 60281 3230251419 14-OCT-10 3230268263 14-OCT-10
2 60282 3230268263 14-OCT-10 3230286809 14-OCT-10
BS Key Type LV Size Device Type Elapsed Time Completion Time
19725 Full 126.40G DISK 09:11:51 15-OCT-10
List of Datafiles in backup set 19725
File LV Type Ckp SCN Ckp Time Name
1 Full 3230287009 14-OCT-10 +DATA/ehr/datafile/system.625.609259453
2 Full 3230287009 14-OCT-10 +DATA/ehr/datafile/undotbs1.620.609259461
3 Full 3230287009 14-OCT-10 +DATA/ehr/datafile/sysaux.768.609259463
4 Full 3230287009 14-OCT-10 +DATA/ehr/datafile/undotbs2.632.609259467
5 Full 3230287009 14-OCT-10 +DATA/ehr/datafile/users.257.609259471
6 Full 3230287009 14-OCT-10 +DATA/ehr/datafile/apolloaud.316.619537285
7 Full 3230287009 14-OCT-10 +DATA/ehr/datafile/apollohist.629.619538155
8 Full 3230287009 14-OCT-10 +DATA/ehr/datafile/apolloidx.312.619538169
9 Full 3230287009 14-OCT-10 +DATA/ehr/datafile/apollotab.276.619538487
10 Full 3230287009 14-OCT-10 +DATA/ehr/datafile/apollotab.576.619539331
11 Full 3230287009 14-OCT-10 +DATA/ehr/datafile/apollolob.570.619539593
12 Full 3230287009 14-OCT-10 +DATA/ehr/datafile/apollofdb.750.645974339
13 Full 3230287009 14-OCT-10 +DATA/ehr/datafile/apolloidx.429.651171265
14 Full 3230287009 14-OCT-10 +DATA/ehr/datafile/apolloidx.705.688680793
15 Full 3230287009 14-OCT-10 +DATA/ehr/datafile/apolloaud.747.699632315
16 Full 3230287009 14-OCT-10 +DATA/ehr/datafile/apollotab.330.715622123
Backup Set Copy #1 of backup set 19725
Device Type Elapsed Time Completion Time Compressed Tag
DISK 09:11:51 20-OCT-10 YES TAG20101014T210039
List of Backup Pieces for backup set 19725 Copy #1
BP Key Pc# Status Piece Name
65851 1 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece1_copy1_20101014
65862 2 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece2_copy1_20101014
65873 3 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece3_copy1_20101014
65884 4 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece4_copy1_20101014
65895 5 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece5_copy1_20101014
65901 6 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece6_copy1_20101014
65902 7 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece7_copy1_20101014
65903 8 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece8_copy1_20101014
65904 9 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece9_copy1_20101014
65841 10 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece10_copy1_20101014
65842 11 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece11_copy1_20101014
65843 12 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece12_copy1_20101014
65844 13 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece13_copy1_20101014
65845 14 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece14_copy1_20101014
65846 15 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece15_copy1_20101014
65847 16 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece16_copy1_20101014
65848 17 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece17_copy1_20101014
65849 18 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece18_copy1_20101014
65850 19 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece19_copy1_20101014
65852 20 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece20_copy1_20101014
65853 21 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece21_copy1_20101014
65854 22 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece22_copy1_20101015
65855 23 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece23_copy1_20101015
65856 24 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece24_copy1_20101015
65857 25 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece25_copy1_20101015
65858 26 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece26_copy1_20101015
65859 27 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece27_copy1_20101015
65860 28 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece28_copy1_20101015
65861 29 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece29_copy1_20101015
65863 30 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece30_copy1_20101015
65864 31 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece31_copy1_20101015
65865 32 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece32_copy1_20101015
65866 33 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece33_copy1_20101015
65867 34 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece34_copy1_20101015
65868 35 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece35_copy1_20101015
65869 36 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece36_copy1_20101015
65870 37 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece37_copy1_20101015
65871 38 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece38_copy1_20101015
65872 39 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece39_copy1_20101015
65874 40 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece40_copy1_20101015
65875 41 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece41_copy1_20101015
65876 42 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece42_copy1_20101015
65877 43 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece43_copy1_20101015
65878 44 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece44_copy1_20101015
65879 45 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece45_copy1_20101015
65880 46 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece46_copy1_20101015
65881 47 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece47_copy1_20101015
65882 48 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece48_copy1_20101015
65883 49 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece49_copy1_20101015
65885 50 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece50_copy1_20101015
65886 51 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece51_copy1_20101015
65887 52 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece52_copy1_20101015
65888 53 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece53_copy1_20101015
65889 54 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece54_copy1_20101015
65890 55 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece55_copy1_20101015
65891 56 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece56_copy1_20101015
65892 57 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece57_copy1_20101015
65893 58 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece58_copy1_20101015
65894 59 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece59_copy1_20101015
65896 60 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece60_copy1_20101015
65897 61 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece61_copy1_20101015
65898 62 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece62_copy1_20101015
65899 63 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece63_copy1_20101015
65900 64 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece64_copy1_20101015
BS Key Size Device Type Elapsed Time Completion Time
19726 228.10M DISK 00:00:49 15-OCT-10
BP Key: 65905 Status: AVAILABLE Compressed: YES Tag: TAG20101015T061242
Piece Name: /mnt/migrate/rman/EHR_dbid3632734257_set113197_piece1_copy1_20101015
List of Archived Logs in backup set 19726
Thrd Seq Low SCN Low Time Next SCN Next Time
1 50441 3230286806 14-OCT-10 3230331993 14-OCT-10
1 50442 3230331993 14-OCT-10 3230401945 14-OCT-10
1 50443 3230401945 14-OCT-10 3230469794 15-OCT-10
1 50444 3230469794 15-OCT-10 3230555010 15-OCT-10
1 50445 3230555010 15-OCT-10 3230618396 15-OCT-10
1 50446 3230618396 15-OCT-10 3230695020 15-OCT-10
2 60283 3230286809 14-OCT-10 3230304858 14-OCT-10
2 60284 3230304858 14-OCT-10 3230330891 14-OCT-10
2 60285 3230330891 14-OCT-10 3230354275 14-OCT-10
2 60286 3230354275 14-OCT-10 3230366292 14-OCT-10
2 60287 3230366292 14-OCT-10 3230399805 14-OCT-10
2 60288 3230399805 14-OCT-10 3230423577 14-OCT-10
2 60289 3230423577 14-OCT-10 3230446176 15-OCT-10
2 60290 3230446176 15-OCT-10 3230469756 15-OCT-10
2 60291 3230469756 15-OCT-10 3230496786 15-OCT-10
2 60292 3230496786 15-OCT-10 3230524710 15-OCT-10
2 60293 3230524710 15-OCT-10 3230554981 15-OCT-10
2 60294 3230554981 15-OCT-10 3230583802 15-OCT-10
2 60295 3230583802 15-OCT-10 3230610465 15-OCT-10
2 60296 3230610465 15-OCT-10 3230617887 15-OCT-10
2 60297 3230617887 15-OCT-10 3230673207 15-OCT-10
2 60298 3230673207 15-OCT-10 3230695022 15-OCT-10

Maximum Data file size in 10g,11g

DB Versions:10g, 11g
OS & versions: Aix 6.1, Sun OS 5.9, Solaris 10
This is what Oracle 11g Documentation
http://download.oracle.com/docs/cd/B28359_01/server.111/b28320/limits002.htm
says about the Maximum Data file size
Operating system dependent. Limited by maximum operating system file size;typically 2^22 or 4 MB blocksI don't understand what this 2^22 thing is.
In our AIX machine and ulimit command show
$ ulimit -a
time(seconds)        unlimited
file(blocks)         unlimited <-------------------------------------------
data(kbytes)         unlimited
stack(kbytes)        4194304
memory(kbytes)       unlimited
coredump(blocks)     unlimited
nofiles(descriptors) unlimited
threads(per process) unlimited
processes(per user) unlimitedSo, this means, In AIX that both the OS and Oracle can create a data file of any Size. Right?
What about 10g, 11g DBs running on Sun OS 5.9 and Solaris 10 ? Is there any Limit on the data file size?

How do i determine maximum number of blocks for an OS?df -g would give you the block size. OS blocksize is 512 bytes on AIX.
Lets say the db_block_size is 8k. What would the maximum file size for data file in Small File tablespace and Big File tablespace be?Smallfile (traditional) Tablespaces - A smallfile tablespace is a traditional Oracle tablespace, which can contain 1022 datafiles or tempfiles, each of which can contain up to approximately 4 million (222) blocks. - 32G
A bigfile tablespace contains only one datafile or tempfile, which can contain up to approximately 4 billion ( 232 ) blocks. The maximum size of the single datafile or tempfile is 128 terabytes (TB) for a tablespace with 32K blocks and 32TB for a tablespace with 8K blocks.
HTH
-Anantha

Maximum number of blocks for a bigfile datafile?

Hello,
In 10g, when using bigfile tablespaces, the maximum size of a datafile can be between 8TB to 128TB depending on the block size (2K to 32K). The formula given to calculate the max size of a bigfile datafile is:
Maximum datafile size = db_block_size * maximum number of blocks
So my question is how do you calculate the max number of blocks? Oracle documentation states that the max number of blocks is 4,294,967,296 (4 billion) 2^32. But where do they get this number from? I read, on a different site (not Oracle), that it is the addressing scheme used in ROWID that changed permitting the possibility of addressing 4 billion blocks instead of 4 million:
This is due to a new addressing scheme Oracle uses internally. Oracle ROWID, addressing a database object stored in a traditional SMALLFILE tablespace, divides the 12 bytes thusly: 3 bytes for the Relative File#, 6 bytes for the Block# and 3 bytes for the object. The same rowid addressing an object stored in a new BIGFILE tablespace uses the 9 bytes to store the Block# within the unique file, as there is no reason to use the 3 bytes for the Relative File# since there is only one file in that tablespace. Thus the new addressing scheme permits up to 4Gblocks (4,294,967,296) in a single data file and the maximum file size can reach 8 TB for a blocksize of 2K and 128 TB for a blocksize of 32K.
But, even with this explanation, 4 billion still makes no sense because using 9 bytes equates to 2^72 addressable blocks, not 2^32. Am I missing something?
Thanks,
Mark

Thanks for the answer.
I'm almost tempted to accept the explanation that the 4,294,967,296 addressable blocks is a 32bit platform limitation... Do you or anyone know of any official Oracle documentation explaining where they get this magic number from?

Need clarification on Bigfile Tablespaces

In the following Oracle Documentation Lirbary PDF,
    Oracle® Database
    Concepts
    10g Release 2 (10.2)
    B14220-02
    October 2005
section
    Overview of Tablespaces
    Bigfile Tablespaces (page: 3-5)
it says,
    Benefits of Bigfile Tablespaces
    * Bigfile tablespaces can significantly increase the storage capacity of an Oracle database. Smallfile tablespaces can contain up to 1024 files, but bigfile tablespaces contain only one file that can be 1024 times larger than a smallfile tablespace. The total tablespace capacity is the same for smallfile tablespaces and bigfile tablespaces. However, because there is a limit of 64K database for each database, a database can contain 1024 times more bigfile tablespaces than smallfile tablespaces, so bigfile tablespaces increase the total database capacity by 3 orders of magnitude. In other words, 8 exabytes is the maximum size of the Oracle database when bigfile tablespaces are used with the maximum block size (32k).
I need clarification on how to arrive at 8 exabytes ?
1024 x 32k x 64,000 ??
According to the exerpt above, there's no mention of maximum number of Operating System blocks per extent. Unless this was assumed knowledge ... how do I get 8 exabytes ?
And if "a database can contain 1024 times more bigfile tablespaces than smallfile tablespaces", then what's the upper limit on smallfile tablespaces ? -- was this sentence referring to the number of datafiles per smallfile tablespace ? ...
O_o
Thanks !
Message was edited by:
mvanle

Hi,
According to [url http://download-west.oracle.com/docs/cd/B19306_01/server.102/b14237/limits002.htm#i287915]Physical Database Limits page, a bigfile tablespace contains only one datafile or tempfile, which can contain up to approximately 4 billion ( 232 ) blocks. The maximum size of the single datafile or tempfile is 128 terabytes (TB) for a tablespace with 32K blocks and 32TB for a tablespace with 8K blocks. In resume, A bigfile tablespace is a tablespace containing a single datafile that can be as large as 128 terabytes (TB), depending on the block size of the tablespace. In conjunction with setting the initialization parameter DB_FILES to the maximum value of 65,635 the total size of the database can be more than 8 exabytes (EB)
>>how do I get 8 exabytes ?
You can calculate the maximum amount of space (M) in a single Oracle database as the maximum number of datafiles (D) multiplied by the maximum number of blocks per datafile (F) multiplied by the tablespace block size (B):
M = D * F * B. Therefore, the maximum database size, given the maximum block size and the maximum number of datafiles, is:
65,535 datafiles * 4,294,967,296 blocks per datafile * 32,768 block size = 9,223,231,299,366,420,480 = 8EB.Cheers
Legatti

ROWID in Oracle 10g

What is the major change of using ROWID from 9i to 10g?

For tables in a default "smallfile" tablespace the rowid format has not changed. The rowid format does change for tables stored in the new "bigfile" tablespace.
A bigfile tablespace has only one file and the relative file number is always the same (1024 on most platforms).
The dbms_utility procedures DATA_BLOCK_ADDRESS_FILE and DATA_BLOCK_ADDRESS_BLOCK should not be used with bigfiles.
The dbms_rowid package has been modified and several of its routines accept "bigfile" as a parameter. But you have to identify the input rowid is for a bigfile to get back correct results.
HTH -- Mark D Powell --

Bigfile tablespace.

Can someone tell me wat is the max size of Bigfile Tablespace in Oracle 10g???????????

Oracle Reference has database limit list,
http://download.oracle.com/docs/cd/B19306_01/server.102/b14237/limits002.htm#i287915
For user625868, if you want good alignment of output, use pre /pre with [] to wrap around your result.
For example, unwraped output of desc looks like,
desc dba_users
Name Null? Type
USERNAME NOT NULL VARCHAR2(30)
USER_ID NOT NULL NUMBER
PASSWORD VARCHAR2(30)
ACCOUNT_STATUS NOT NULL VARCHAR2(32)
LOCK_DATE DATE
EXPIRY_DATE DATE
DEFAULT_TABLESPACE NOT NULL VARCHAR2(30)
TEMPORARY_TABLESPACE NOT NULL VARCHAR2(30)
CREATED NOT NULL DATE
PROFILE NOT NULL VARCHAR2(30)
INITIAL_RSRC_CONSUMER_GROUP VARCHAR2(30)
EXTERNAL_NAME VARCHAR2(4000)
This one is better
desc dba_users
Name                                      Null?    Type
USERNAME                                  NOT NULL VARCHAR2(30)
USER_ID                                   NOT NULL NUMBER
PASSWORD                                           VARCHAR2(30)
ACCOUNT_STATUS                            NOT NULL VARCHAR2(32)
LOCK_DATE                                          DATE
EXPIRY_DATE                                        DATE
DEFAULT_TABLESPACE                        NOT NULL VARCHAR2(30)
TEMPORARY_TABLESPACE                      NOT NULL VARCHAR2(30)
CREATED                                   NOT NULL DATE
PROFILE                                   NOT NULL VARCHAR2(30)
INITIAL_RSRC_CONSUMER_GROUP                        VARCHAR2(30)
EXTERNAL_NAME                                      VARCHAR2(4000)

OCM 10g objectives confusion

Hi all,
I started preparing for OCM 11g. Unfortunately the objectives aren't known yet, but I assume that they will be in the same line as those for OCM 10g.
There are some objectives in OCM 10g for which I'm not 100 % sure what they mean.
Does anyone know what's meant with the following objectives?
1) "Configure the database environment to support optimal data access performance."
-> I guess they mean follow OFA standards and placement of database files:
index/data datafiles on separate disks, archive logs on separate disks, redo logs on your fastest disks...?
2) "Create and manage multiple network configuration files"
3) "Configure the network environment to allow connections to multiple databases."-> db links or anything else you could think of?
4) "Choose the appropriate tablespace type for the intended use"
I guess this means chose between smallfile and bigfile.
Permanent/temporary and undo are also 'tablespace types', but this seems would seem an odd objective.
5) "Create and manage objects to accommodate different data access methods (schema tuning)"
I guess indexes/IOT/materialized views? Or anything else you can think of?
Thanks,
David

David_S wrote:
Hi all,
I started preparing for OCM 11g. Unfortunately the objectives aren't known yet, but I assume that they will be in the same line as those for OCM 10g.
There are some objectives in OCM 10g for which I'm not 100 % sure what they mean.
Does anyone know what's meant with the following objectives?
1) "Configure the database environment to support optimal data access performance."
-> I guess they mean follow OFA standards and placement of database files:
index/data datafiles on separate disks, archive logs on separate disks, redo logs on your fastest disks...?I suspect they mean "understand system performance tuning"
>
2) "Create and manage multiple network configuration files"More than 1 ORACLE_HOME, each with it's own TNSNAMES.ORA?
>
3) "Configure the network environment to allow connections to multiple databases."-> db links or anything else you could think of?Understand and manage TNSNAMES.ORA?
>
4) "Choose the appropriate tablespace type for the intended use"
I guess this means chose between smallfile and bigfile.
Permanent/temporary and undo are also 'tablespace types', but this seems would seem an odd objective.
Yes to all.
5) "Create and manage objects to accommodate different data access methods (schema tuning)"
I guess indexes/IOT/materialized views? Or anything else you can think of?
Appropriate use of all schema objects, including the 3 you mention. As well as sequences, different table types (heap/IOT/clusters), lob segment management, etc. And when/how to use temp segments. And appropriate parameters such as those affectinig block reuse.
Thanks,
DavidOCM is supposed to be a comprehensive "I know how to DBA in a production world" exam. I suspect anything can show up.

Bigfile tablespaces requirment

version 10g/11g
I am just trying to clear my concepts about VLDBs,
How the disk should be configured to support bigfile tablespace for example 2 tablespace 10TB/each(one for data, one for index)
How i can tell my Disk support bigfile tablespace (commands?)
what should be the best practice to implement this ?
any other suggestion/metalink notes for further research would help....

http://download.oracle.com/docs/cd/B19306_01/server.102/b14231/tspaces.htm#sthref1288
OR
http://download.oracle.com/docs/cd/B19306_01/server.102/b14231/tspaces.htm#i1007169

Report developed in 6i and open and run in 10g, Web Layout is not working

Hi,
Initially reports were developed in Reports 6i now we need to convert into 10g. I just opened the .rdf in Reports10g. Report is successfully running in paper layout and showing the data. But when i try to run the report in Web Layout im getting a BLANK INTERNET EXPLORER SCREEN. Why is it so? What should i do to run my report successfully in Web Layout? When i see Web Source, i am seeing the below code,
<%@ taglib uri="/WEB-INF/lib/reports_tld.jar" prefix="rw" %>
<%@ page language="java" import="java.io.*" errorPage="/rwerror.jsp" session="false" %>
<%@ page contentType="text/html;charset=ISO-8859-1" %>

<html>
<head>
<meta name="GENERATOR" content="Oracle 9i Reports Developer"/>
<title> Your Title </title>
<rw:style id="yourStyle">

</rw:style>
</head>
<body>
<rw:dataArea id="yourDataArea">

</rw:dataArea>
</body>
</html>

Please, guide to achive the Web Layout Report.
Thanks & Rgds,
M Thiyagarajan

Hello,
The answer is in the Migration FAQ :
When I open an Oracle6i Reports Developer report in the Oracle Reports Builder 10g and run my Web layout, I get an empty Web page in my browser.
http://www.oracle.com/technology/products/reports/htdocs/faq/faq_migration.htm#368
Regards

NULL and Unspecified in Dashboard prompts after upgrading 10g to 11g OBIEE

Hi All,
We are working on OBI upgradation project from 10g to 11.1.1.6.5. We are facing one issue in Dashboard prompt level. If we can create Dashboard prompt on a column, its giving "NULL", "Unspecified" additionally. But, in 10g there are no extra values.
And the 10g, 11g instances are pointing to the same database and there are no NULL, Unspecified values in Database level.
Through some blogs and articles we found some solutions n are below.
To remove NULL:
-->Go to the Physical Column properties in Physical Layer and Disable the Nullable option by uncheck the box.
-->Go to the Database Features in Physical Layer and disable value to NULL_SUPPORTED.
-->Go to Edit Dashboard Prompt, in Choice List Values drop-down list select SQL Results.
To remove Unspecified:
-->Go to Edit Dashboard Prompt, in Choice List Values drop-down list select SQL Results, then write the SQL statements as columnname is not equals to "Unspecfied" ( In this way we can able to remove Null's also.)
-->Go to Content tab of LTS, in Where clause write an SQL query to restrict Unspecified values.
Note: CHeck with ETL, because if they maintains the Default value is Null when the Datatype is Character and they can maintain 9999 or #### if the datatype is Numeric. And check the Physical query and debug it carefully.
But, we have very big Repository and we have huge no.of Dashboard prompts. So, its not an easy thing to manage by using above solutions. Correct me if there are any mistakes in above.
Any ideas on this...?
Appreciate your help on this..!
Thanks in Advance,
Raghu Nagadasari

Hi Frnds,
As of now, i found the only solution for the above mentioned issue that how to avoid NULL in dashboard prompt level:
Go to the Physical Column properties in Physical Layer and Disable the Nullable option by uncheck the box.
We have done this manually for all tables.
Appreciate if u have any other ideas.!!
Thanks,
Raghu Nagadasari

Report performance issue in oracle database 10g to 11g

Hi All,
We have one test instance for database 10g where the report is working fine below is the plan for report.
SELECT STATEMENT
VIEW APPS
SORT UNIQUE
UNION-ALL
HASH JOIN
TABLE ACCESS BY INDEX ROWID INV.MTL_SYSTEM_ITEMS_B
NESTED LOOPS
MERGE JOIN CARTESIAN
TABLE ACCESS FULL INV.MTL_PARAMETERS
BUFFER SORT
TABLE ACCESS BY INDEX ROWID APPLSYS.FND_LOOKUP_VALUES
INDEX RANGE SCAN APPLSYS.FND_LOOKUP_VALUES_U2
INDEX RANGE SCAN INV.MTL_SYSTEM_ITEMS_B_XX1
TABLE ACCESS FULL ONT.OE_ORDER_LINES_ALL
NESTED LOOPS ANTI
HASH JOIN
TABLE ACCESS BY INDEX ROWID MRP.MRP_GROSS_REQUIREMENTS
INDEX SKIP SCAN MRP.MRP_GROSS_REQUIREMENTS_N2
TABLE ACCESS BY INDEX ROWID INV.MTL_SYSTEM_ITEMS_B
NESTED LOOPS
MERGE JOIN CARTESIAN
TABLE ACCESS FULL INV.MTL_PARAMETERS
BUFFER SORT
TABLE ACCESS BY INDEX ROWID APPLSYS.FND_LOOKUP_VALUES
INDEX RANGE SCAN APPLSYS.FND_LOOKUP_VALUES_U2
INDEX RANGE SCAN INV.MTL_SYSTEM_ITEMS_B_XX1
TABLE ACCESS BY INDEX ROWID ONT.OE_ORDER_LINES_ALL
INDEX RANGE SCAN ONT.OE_ORDER_LINES_N3
We have one more instance whose database is 11g and the same report is migrated but it is taking too long time to execute the report output. Please advise why it is happening even why the plan is difference.
SELECT STATEMENT
VIEW APPS
SORT UNIQUE
UNION-ALL
NESTED LOOPS
NESTED LOOPS
NESTED LOOPS
NESTED LOOPS
NESTED LOOPS
INDEX RANGE SCAN INV.MTL_ITEM_CATEGORIES_U1
INDEX UNIQUE SCAN INV.MTL_CATEGORY_SETS_B_U1
TABLE ACCESS BY INDEX ROWID INV.MTL_CATEGORIES_B
INDEX UNIQUE SCAN INV.MTL_CATEGORIES_B_U1
INDEX UNIQUE SCAN INV.MTL_CATEGORIES_TL_U1
INDEX UNIQUE SCAN INV.MTL_CATEGORY_SETS_TL_U1
TABLE ACCESS BY INDEX ROWID INV.MTL_CATEGORY_SETS_TL
SORT AGGREGATE
TABLE ACCESS BY INDEX ROWID BOM.BOM_STRUCTURES_B
INDEX RANGE SCAN BOM.BOM_STRUCTURES_B_N2
SORT AGGREGATE
INDEX RANGE SCAN BOM.BOM_OPERATIONAL_ROUTINGS_U2
SORT AGGREGATE
TABLE ACCESS BY INDEX ROWID BOM.CST_ITEM_COSTS
INDEX UNIQUE SCAN BOM.CST_ITEM_COSTS_U1
SORT AGGREGATE
TABLE ACCESS BY INDEX ROWID BOM.CST_ITEM_COSTS
INDEX UNIQUE SCAN BOM.CST_ITEM_COSTS_U1
SORT AGGREGATE
FILTER
NESTED LOOPS
NESTED LOOPS
MERGE JOIN CARTESIAN
NESTED LOOPS
NESTED LOOPS
TABLE ACCESS BY INDEX ROWID QP.QP_LIST_HEADERS_TL
INDEX RANGE SCAN QP.QP_LIST_HEADERS_TL_U1
INDEX UNIQUE SCAN QP.QP_LIST_HEADERS_B_PK
TABLE ACCESS BY INDEX ROWID QP.QP_LIST_HEADERS_B
BUFFER SORT
TABLE ACCESS BY INDEX ROWID QP.QP_PRICING_ATTRIBUTES
INDEX SKIP SCAN QP.QP_PRICING_ATTRIBUTES_N11
INDEX UNIQUE SCAN QP.QP_LIST_LINES_PK
TABLE ACCESS BY INDEX ROWID QP.QP_LIST_LINES
TABLE ACCESS BY INDEX ROWID QP.QP_PRICING_ATTRIBUTES
INDEX RANGE SCAN QP.QP_PRICING_ATTRIBUTES_N3
TABLE ACCESS BY INDEX ROWID QP.QP_PRICING_ATTRIBUTES
INDEX RANGE SCAN QP.QP_PRICING_ATTRIBUTES_N3
TABLE ACCESS BY INDEX ROWID QP.QP_PRICING_ATTRIBUTES
INDEX RANGE SCAN QP.QP_PRICING_ATTRIBUTES_N3
SORT AGGREGATE
FILTER
NESTED LOOPS
NESTED LOOPS
MERGE JOIN CARTESIAN
NESTED LOOPS
NESTED LOOPS
TABLE ACCESS BY INDEX ROWID QP.QP_LIST_HEADERS_TL
INDEX RANGE SCAN QP.QP_LIST_HEADERS_TL_U1
INDEX UNIQUE SCAN QP.QP_LIST_HEADERS_B_PK
TABLE ACCESS BY INDEX ROWID QP.QP_LIST_HEADERS_B
BUFFER SORT
TABLE ACCESS BY INDEX ROWID QP.QP_PRICING_ATTRIBUTES
INDEX SKIP SCAN QP.QP_PRICING_ATTRIBUTES_N11
INDEX UNIQUE SCAN QP.QP_LIST_LINES_PK
TABLE ACCESS BY INDEX ROWID QP.QP_LIST_LINES
TABLE ACCESS BY INDEX ROWID QP.QP_PRICING_ATTRIBUTES
INDEX RANGE SCAN QP.QP_PRICING_ATTRIBUTES_N3
TABLE ACCESS BY INDEX ROWID QP.QP_PRICING_ATTRIBUTES
INDEX RANGE SCAN QP.QP_PRICING_ATTRIBUTES_N3
TABLE ACCESS BY INDEX ROWID QP.QP_PRICING_ATTRIBUTES
INDEX RANGE SCAN QP.QP_PRICING_ATTRIBUTES_N3
SORT AGGREGATE
NESTED LOOPS
TABLE ACCESS BY INDEX ROWID MRP.MRP_ASSIGNMENT_SETS
INDEX UNIQUE SCAN MRP.MRP_ASSIGNMENT_SETS_U2
INDEX RANGE SCAN MRP.MRP_SR_ASSIGNMENTS_N3
SORT AGGREGATE
TABLE ACCESS BY INDEX ROWID PO.PO_APPROVED_SUPPLIER_LIST
INDEX RANGE SCAN PO.PO_APPROVED_SUPPLIER_LIST_N1
SORT AGGREGATE
TABLE ACCESS BY INDEX ROWID INV.MTL_ONHAND_QUANTITIES_DETAIL
INDEX RANGE SCAN INV.MTL_ONHAND_QUANTITIES_N6
SORT AGGREGATE
TABLE ACCESS BY INDEX ROWID INV.MTL_ONHAND_QUANTITIES_DETAIL
INDEX RANGE SCAN INV.MTL_ONHAND_QUANTITIES_N6
SORT AGGREGATE
TABLE ACCESS BY INDEX ROWID ONT.OE_ORDER_LINES_ALL
INDEX RANGE SCAN ONT.OE_ORDER_LINES_N3
SORT AGGREGATE
TABLE ACCESS BY INDEX ROWID ONT.OE_ORDER_LINES_ALL
INDEX RANGE SCAN ONT.OE_ORDER_LINES_N3
NESTED LOOPS
NESTED LOOPS
NESTED LOOPS
INDEX RANGE SCAN INV.MTL_ITEM_CATEGORIES_U1
TABLE ACCESS BY INDEX ROWID INV.MTL_CATEGORIES_B
INDEX UNIQUE SCAN INV.MTL_CATEGORIES_B_U1
INDEX UNIQUE SCAN INV.MTL_CATEGORY_SETS_TL_U1
TABLE ACCESS BY INDEX ROWID INV.MTL_CATEGORY_SETS_TL
HASH JOIN
NESTED LOOPS
NESTED LOOPS
MERGE JOIN CARTESIAN
TABLE ACCESS FULL INV.MTL_PARAMETERS
BUFFER SORT
TABLE ACCESS BY INDEX ROWID APPLSYS.FND_LOOKUP_VALUES
INDEX RANGE SCAN APPLSYS.FND_LOOKUP_VALUES_U2
INDEX RANGE SCAN INV.MTL_SYSTEM_ITEMS_B_XX1
TABLE ACCESS BY INDEX ROWID INV.MTL_SYSTEM_ITEMS_B
TABLE ACCESS FULL ONT.OE_ORDER_LINES_ALL
NESTED LOOPS
NESTED LOOPS
NESTED LOOPS
NESTED LOOPS
NESTED LOOPS
INDEX RANGE SCAN INV.MTL_ITEM_CATEGORIES_U1
INDEX UNIQUE SCAN INV.MTL_CATEGORY_SETS_B_U1
TABLE ACCESS BY INDEX ROWID INV.MTL_CATEGORIES_B
INDEX UNIQUE SCAN INV.MTL_CATEGORIES_B_U1
INDEX UNIQUE SCAN INV.MTL_CATEGORIES_TL_U1
INDEX UNIQUE SCAN INV.MTL_CATEGORY_SETS_TL_U1
TABLE ACCESS BY INDEX ROWID INV.MTL_CATEGORY_SETS_TL
TABLE ACCESS BY INDEX ROWID BOM.BOM_STRUCTURES_B
INDEX RANGE SCAN BOM.BOM_STRUCTURES_B_N2
INDEX RANGE SCAN BOM.BOM_OPERATIONAL_ROUTINGS_U2
TABLE ACCESS BY INDEX ROWID BOM.CST_ITEM_COSTS
INDEX UNIQUE SCAN BOM.CST_ITEM_COSTS_U1
TABLE ACCESS BY INDEX ROWID BOM.CST_ITEM_COSTS
INDEX UNIQUE SCAN BOM.CST_ITEM_COSTS_U1
FILTER
NESTED LOOPS
NESTED LOOPS
MERGE JOIN CARTESIAN
NESTED LOOPS
NESTED LOOPS
TABLE ACCESS BY INDEX ROWID QP.QP_LIST_HEADERS_TL
INDEX RANGE SCAN QP.QP_LIST_HEADERS_TL_U1
INDEX UNIQUE SCAN QP.QP_LIST_HEADERS_B_PK
TABLE ACCESS BY INDEX ROWID QP.QP_LIST_HEADERS_B
BUFFER SORT
TABLE ACCESS BY INDEX ROWID QP.QP_PRICING_ATTRIBUTES
INDEX SKIP SCAN QP.QP_PRICING_ATTRIBUTES_N11
INDEX UNIQUE SCAN QP.QP_LIST_LINES_PK
TABLE ACCESS BY INDEX ROWID QP.QP_LIST_LINES
TABLE ACCESS BY INDEX ROWID QP.QP_PRICING_ATTRIBUTES
INDEX RANGE SCAN QP.QP_PRICING_ATTRIBUTES_N3
TABLE ACCESS BY INDEX ROWID QP.QP_PRICING_ATTRIBUTES
INDEX RANGE SCAN QP.QP_PRICING_ATTRIBUTES_N3
TABLE ACCESS BY INDEX ROWID QP.QP_PRICING_ATTRIBUTES
INDEX RANGE SCAN QP.QP_PRICING_ATTRIBUTES_N3
FILTER
NESTED LOOPS
NESTED LOOPS
MERGE JOIN CARTESIAN
NESTED LOOPS
NESTED LOOPS
TABLE ACCESS BY INDEX ROWID QP.QP_LIST_HEADERS_TL
INDEX RANGE SCAN QP.QP_LIST_HEADERS_TL_U1
INDEX UNIQUE SCAN QP.QP_LIST_HEADERS_B_PK
TABLE ACCESS BY INDEX ROWID QP.QP_LIST_HEADERS_B
BUFFER SORT
TABLE ACCESS BY INDEX ROWID QP.QP_PRICING_ATTRIBUTES
INDEX SKIP SCAN QP.QP_PRICING_ATTRIBUTES_N11
INDEX UNIQUE SCAN QP.QP_LIST_LINES_PK
TABLE ACCESS BY INDEX ROWID QP.QP_LIST_LINES
TABLE ACCESS BY INDEX ROWID QP.QP_PRICING_ATTRIBUTES
INDEX RANGE SCAN QP.QP_PRICING_ATTRIBUTES_N3
TABLE ACCESS BY INDEX ROWID QP.QP_PRICING_ATTRIBUTES
INDEX RANGE SCAN QP.QP_PRICING_ATTRIBUTES_N3
TABLE ACCESS BY INDEX ROWID QP.QP_PRICING_ATTRIBUTES
INDEX RANGE SCAN QP.QP_PRICING_ATTRIBUTES_N3
SORT UNIQUE NOSORT
NESTED LOOPS
TABLE ACCESS BY INDEX ROWID MRP.MRP_ASSIGNMENT_SETS
INDEX UNIQUE SCAN MRP.MRP_ASSIGNMENT_SETS_U2
INDEX RANGE SCAN MRP.MRP_SR_ASSIGNMENTS_N3
SORT UNIQUE NOSORT
TABLE ACCESS BY INDEX ROWID PO.PO_APPROVED_SUPPLIER_LIST
INDEX RANGE SCAN PO.PO_APPROVED_SUPPLIER_LIST_N1
SORT AGGREGATE
TABLE ACCESS BY INDEX ROWID INV.MTL_ONHAND_QUANTITIES_DETAIL
INDEX RANGE SCAN INV.MTL_ONHAND_QUANTITIES_N6
SORT AGGREGATE
TABLE ACCESS BY INDEX ROWID INV.MTL_ONHAND_QUANTITIES_DETAIL
INDEX RANGE SCAN INV.MTL_ONHAND_QUANTITIES_N6
SORT AGGREGATE
INDEX RANGE SCAN MRP.MRP_GROSS_REQUIREMENTS_N1
SORT AGGREGATE
INDEX RANGE SCAN MRP.MRP_GROSS_REQUIREMENTS_N1
NESTED LOOPS
NESTED LOOPS
NESTED LOOPS
INDEX RANGE SCAN INV.MTL_ITEM_CATEGORIES_U1
TABLE ACCESS BY INDEX ROWID INV.MTL_CATEGORIES_B
INDEX UNIQUE SCAN INV.MTL_CATEGORIES_B_U1
INDEX UNIQUE SCAN INV.MTL_CATEGORY_SETS_TL_U1
TABLE ACCESS BY INDEX ROWID INV.MTL_CATEGORY_SETS_TL
NESTED LOOPS ANTI
HASH JOIN
TABLE ACCESS BY INDEX ROWID MRP.MRP_GROSS_REQUIREMENTS
INDEX SKIP SCAN MRP.MRP_GROSS_REQUIREMENTS_N2
NESTED LOOPS
NESTED LOOPS
MERGE JOIN CARTESIAN
TABLE ACCESS FULL INV.MTL_PARAMETERS
BUFFER SORT
TABLE ACCESS BY INDEX ROWID APPLSYS.FND_LOOKUP_VALUES
INDEX RANGE SCAN APPLSYS.FND_LOOKUP_VALUES_U2
INDEX RANGE SCAN INV.MTL_SYSTEM_ITEMS_B_XX1
TABLE ACCESS BY INDEX ROWID INV.MTL_SYSTEM_ITEMS_B
TABLE ACCESS BY INDEX ROWID ONT.OE_ORDER_LINES_ALL
INDEX RANGE SCAN ONT.OE_ORDER_LINES_N3
}

Hi All,
We have one test instance for database 10g where the report is working fine below is the plan for report.
SELECT STATEMENT
VIEW APPS
SORT UNIQUE
UNION-ALL
HASH JOIN
TABLE ACCESS BY INDEX ROWID INV.MTL_SYSTEM_ITEMS_B
NESTED LOOPS
MERGE JOIN CARTESIAN
TABLE ACCESS FULL INV.MTL_PARAMETERS
BUFFER SORT
TABLE ACCESS BY INDEX ROWID APPLSYS.FND_LOOKUP_VALUES
INDEX RANGE SCAN APPLSYS.FND_LOOKUP_VALUES_U2
INDEX RANGE SCAN INV.MTL_SYSTEM_ITEMS_B_XX1
TABLE ACCESS FULL ONT.OE_ORDER_LINES_ALL
NESTED LOOPS ANTI
HASH JOIN
TABLE ACCESS BY INDEX ROWID MRP.MRP_GROSS_REQUIREMENTS
INDEX SKIP SCAN MRP.MRP_GROSS_REQUIREMENTS_N2
TABLE ACCESS BY INDEX ROWID INV.MTL_SYSTEM_ITEMS_B
NESTED LOOPS
MERGE JOIN CARTESIAN
TABLE ACCESS FULL INV.MTL_PARAMETERS
BUFFER SORT
TABLE ACCESS BY INDEX ROWID APPLSYS.FND_LOOKUP_VALUES
INDEX RANGE SCAN APPLSYS.FND_LOOKUP_VALUES_U2
INDEX RANGE SCAN INV.MTL_SYSTEM_ITEMS_B_XX1
TABLE ACCESS BY INDEX ROWID ONT.OE_ORDER_LINES_ALL
INDEX RANGE SCAN ONT.OE_ORDER_LINES_N3
We have one more instance whose database is 11g and the same report is migrated but it is taking too long time to execute the report output. Please advise why it is happening even why the plan is difference.
SELECT STATEMENT
VIEW APPS
SORT UNIQUE
UNION-ALL
NESTED LOOPS
NESTED LOOPS
NESTED LOOPS
NESTED LOOPS
NESTED LOOPS
INDEX RANGE SCAN INV.MTL_ITEM_CATEGORIES_U1
INDEX UNIQUE SCAN INV.MTL_CATEGORY_SETS_B_U1
TABLE ACCESS BY INDEX ROWID INV.MTL_CATEGORIES_B
INDEX UNIQUE SCAN INV.MTL_CATEGORIES_B_U1
INDEX UNIQUE SCAN INV.MTL_CATEGORIES_TL_U1
INDEX UNIQUE SCAN INV.MTL_CATEGORY_SETS_TL_U1
TABLE ACCESS BY INDEX ROWID INV.MTL_CATEGORY_SETS_TL
SORT AGGREGATE
TABLE ACCESS BY INDEX ROWID BOM.BOM_STRUCTURES_B
INDEX RANGE SCAN BOM.BOM_STRUCTURES_B_N2
SORT AGGREGATE
INDEX RANGE SCAN BOM.BOM_OPERATIONAL_ROUTINGS_U2
SORT AGGREGATE
TABLE ACCESS BY INDEX ROWID BOM.CST_ITEM_COSTS
INDEX UNIQUE SCAN BOM.CST_ITEM_COSTS_U1
SORT AGGREGATE
TABLE ACCESS BY INDEX ROWID BOM.CST_ITEM_COSTS
INDEX UNIQUE SCAN BOM.CST_ITEM_COSTS_U1
SORT AGGREGATE
FILTER
NESTED LOOPS
NESTED LOOPS
MERGE JOIN CARTESIAN
NESTED LOOPS
NESTED LOOPS
TABLE ACCESS BY INDEX ROWID QP.QP_LIST_HEADERS_TL
INDEX RANGE SCAN QP.QP_LIST_HEADERS_TL_U1
INDEX UNIQUE SCAN QP.QP_LIST_HEADERS_B_PK
TABLE ACCESS BY INDEX ROWID QP.QP_LIST_HEADERS_B
BUFFER SORT
TABLE ACCESS BY INDEX ROWID QP.QP_PRICING_ATTRIBUTES
INDEX SKIP SCAN QP.QP_PRICING_ATTRIBUTES_N11
INDEX UNIQUE SCAN QP.QP_LIST_LINES_PK
TABLE ACCESS BY INDEX ROWID QP.QP_LIST_LINES
TABLE ACCESS BY INDEX ROWID QP.QP_PRICING_ATTRIBUTES
INDEX RANGE SCAN QP.QP_PRICING_ATTRIBUTES_N3
TABLE ACCESS BY INDEX ROWID QP.QP_PRICING_ATTRIBUTES
INDEX RANGE SCAN QP.QP_PRICING_ATTRIBUTES_N3
TABLE ACCESS BY INDEX ROWID QP.QP_PRICING_ATTRIBUTES
INDEX RANGE SCAN QP.QP_PRICING_ATTRIBUTES_N3
SORT AGGREGATE
FILTER
NESTED LOOPS
NESTED LOOPS
MERGE JOIN CARTESIAN
NESTED LOOPS
NESTED LOOPS
TABLE ACCESS BY INDEX ROWID QP.QP_LIST_HEADERS_TL
INDEX RANGE SCAN QP.QP_LIST_HEADERS_TL_U1
INDEX UNIQUE SCAN QP.QP_LIST_HEADERS_B_PK
TABLE ACCESS BY INDEX ROWID QP.QP_LIST_HEADERS_B
BUFFER SORT
TABLE ACCESS BY INDEX ROWID QP.QP_PRICING_ATTRIBUTES
INDEX SKIP SCAN QP.QP_PRICING_ATTRIBUTES_N11
INDEX UNIQUE SCAN QP.QP_LIST_LINES_PK
TABLE ACCESS BY INDEX ROWID QP.QP_LIST_LINES
TABLE ACCESS BY INDEX ROWID QP.QP_PRICING_ATTRIBUTES
INDEX RANGE SCAN QP.QP_PRICING_ATTRIBUTES_N3
TABLE ACCESS BY INDEX ROWID QP.QP_PRICING_ATTRIBUTES
INDEX RANGE SCAN QP.QP_PRICING_ATTRIBUTES_N3
TABLE ACCESS BY INDEX ROWID QP.QP_PRICING_ATTRIBUTES
INDEX RANGE SCAN QP.QP_PRICING_ATTRIBUTES_N3
SORT AGGREGATE
NESTED LOOPS
TABLE ACCESS BY INDEX ROWID MRP.MRP_ASSIGNMENT_SETS
INDEX UNIQUE SCAN MRP.MRP_ASSIGNMENT_SETS_U2
INDEX RANGE SCAN MRP.MRP_SR_ASSIGNMENTS_N3
SORT AGGREGATE
TABLE ACCESS BY INDEX ROWID PO.PO_APPROVED_SUPPLIER_LIST
INDEX RANGE SCAN PO.PO_APPROVED_SUPPLIER_LIST_N1
SORT AGGREGATE
TABLE ACCESS BY INDEX ROWID INV.MTL_ONHAND_QUANTITIES_DETAIL
INDEX RANGE SCAN INV.MTL_ONHAND_QUANTITIES_N6
SORT AGGREGATE
TABLE ACCESS BY INDEX ROWID INV.MTL_ONHAND_QUANTITIES_DETAIL
INDEX RANGE SCAN INV.MTL_ONHAND_QUANTITIES_N6
SORT AGGREGATE
TABLE ACCESS BY INDEX ROWID ONT.OE_ORDER_LINES_ALL
INDEX RANGE SCAN ONT.OE_ORDER_LINES_N3
SORT AGGREGATE
TABLE ACCESS BY INDEX ROWID ONT.OE_ORDER_LINES_ALL
INDEX RANGE SCAN ONT.OE_ORDER_LINES_N3
NESTED LOOPS
NESTED LOOPS
NESTED LOOPS
INDEX RANGE SCAN INV.MTL_ITEM_CATEGORIES_U1
TABLE ACCESS BY INDEX ROWID INV.MTL_CATEGORIES_B
INDEX UNIQUE SCAN INV.MTL_CATEGORIES_B_U1
INDEX UNIQUE SCAN INV.MTL_CATEGORY_SETS_TL_U1
TABLE ACCESS BY INDEX ROWID INV.MTL_CATEGORY_SETS_TL
HASH JOIN
NESTED LOOPS
NESTED LOOPS
MERGE JOIN CARTESIAN
TABLE ACCESS FULL INV.MTL_PARAMETERS
BUFFER SORT
TABLE ACCESS BY INDEX ROWID APPLSYS.FND_LOOKUP_VALUES
INDEX RANGE SCAN APPLSYS.FND_LOOKUP_VALUES_U2
INDEX RANGE SCAN INV.MTL_SYSTEM_ITEMS_B_XX1
TABLE ACCESS BY INDEX ROWID INV.MTL_SYSTEM_ITEMS_B
TABLE ACCESS FULL ONT.OE_ORDER_LINES_ALL
NESTED LOOPS
NESTED LOOPS
NESTED LOOPS
NESTED LOOPS
NESTED LOOPS
INDEX RANGE SCAN INV.MTL_ITEM_CATEGORIES_U1
INDEX UNIQUE SCAN INV.MTL_CATEGORY_SETS_B_U1
TABLE ACCESS BY INDEX ROWID INV.MTL_CATEGORIES_B
INDEX UNIQUE SCAN INV.MTL_CATEGORIES_B_U1
INDEX UNIQUE SCAN INV.MTL_CATEGORIES_TL_U1
INDEX UNIQUE SCAN INV.MTL_CATEGORY_SETS_TL_U1
TABLE ACCESS BY INDEX ROWID INV.MTL_CATEGORY_SETS_TL
TABLE ACCESS BY INDEX ROWID BOM.BOM_STRUCTURES_B
INDEX RANGE SCAN BOM.BOM_STRUCTURES_B_N2
INDEX RANGE SCAN BOM.BOM_OPERATIONAL_ROUTINGS_U2
TABLE ACCESS BY INDEX ROWID BOM.CST_ITEM_COSTS
INDEX UNIQUE SCAN BOM.CST_ITEM_COSTS_U1
TABLE ACCESS BY INDEX ROWID BOM.CST_ITEM_COSTS
INDEX UNIQUE SCAN BOM.CST_ITEM_COSTS_U1
FILTER
NESTED LOOPS
NESTED LOOPS
MERGE JOIN CARTESIAN
NESTED LOOPS
NESTED LOOPS
TABLE ACCESS BY INDEX ROWID QP.QP_LIST_HEADERS_TL
INDEX RANGE SCAN QP.QP_LIST_HEADERS_TL_U1
INDEX UNIQUE SCAN QP.QP_LIST_HEADERS_B_PK
TABLE ACCESS BY INDEX ROWID QP.QP_LIST_HEADERS_B
BUFFER SORT
TABLE ACCESS BY INDEX ROWID QP.QP_PRICING_ATTRIBUTES
INDEX SKIP SCAN QP.QP_PRICING_ATTRIBUTES_N11
INDEX UNIQUE SCAN QP.QP_LIST_LINES_PK
TABLE ACCESS BY INDEX ROWID QP.QP_LIST_LINES
TABLE ACCESS BY INDEX ROWID QP.QP_PRICING_ATTRIBUTES
INDEX RANGE SCAN QP.QP_PRICING_ATTRIBUTES_N3
TABLE ACCESS BY INDEX ROWID QP.QP_PRICING_ATTRIBUTES
INDEX RANGE SCAN QP.QP_PRICING_ATTRIBUTES_N3
TABLE ACCESS BY INDEX ROWID QP.QP_PRICING_ATTRIBUTES
INDEX RANGE SCAN QP.QP_PRICING_ATTRIBUTES_N3
FILTER
NESTED LOOPS
NESTED LOOPS
MERGE JOIN CARTESIAN
NESTED LOOPS
NESTED LOOPS
TABLE ACCESS BY INDEX ROWID QP.QP_LIST_HEADERS_TL
INDEX RANGE SCAN QP.QP_LIST_HEADERS_TL_U1
INDEX UNIQUE SCAN QP.QP_LIST_HEADERS_B_PK
TABLE ACCESS BY INDEX ROWID QP.QP_LIST_HEADERS_B
BUFFER SORT
TABLE ACCESS BY INDEX ROWID QP.QP_PRICING_ATTRIBUTES
INDEX SKIP SCAN QP.QP_PRICING_ATTRIBUTES_N11
INDEX UNIQUE SCAN QP.QP_LIST_LINES_PK
TABLE ACCESS BY INDEX ROWID QP.QP_LIST_LINES
TABLE ACCESS BY INDEX ROWID QP.QP_PRICING_ATTRIBUTES
INDEX RANGE SCAN QP.QP_PRICING_ATTRIBUTES_N3
TABLE ACCESS BY INDEX ROWID QP.QP_PRICING_ATTRIBUTES
INDEX RANGE SCAN QP.QP_PRICING_ATTRIBUTES_N3
TABLE ACCESS BY INDEX ROWID QP.QP_PRICING_ATTRIBUTES
INDEX RANGE SCAN QP.QP_PRICING_ATTRIBUTES_N3
SORT UNIQUE NOSORT
NESTED LOOPS
TABLE ACCESS BY INDEX ROWID MRP.MRP_ASSIGNMENT_SETS
INDEX UNIQUE SCAN MRP.MRP_ASSIGNMENT_SETS_U2
INDEX RANGE SCAN MRP.MRP_SR_ASSIGNMENTS_N3
SORT UNIQUE NOSORT
TABLE ACCESS BY INDEX ROWID PO.PO_APPROVED_SUPPLIER_LIST
INDEX RANGE SCAN PO.PO_APPROVED_SUPPLIER_LIST_N1
SORT AGGREGATE
TABLE ACCESS BY INDEX ROWID INV.MTL_ONHAND_QUANTITIES_DETAIL
INDEX RANGE SCAN INV.MTL_ONHAND_QUANTITIES_N6
SORT AGGREGATE
TABLE ACCESS BY INDEX ROWID INV.MTL_ONHAND_QUANTITIES_DETAIL
INDEX RANGE SCAN INV.MTL_ONHAND_QUANTITIES_N6
SORT AGGREGATE
INDEX RANGE SCAN MRP.MRP_GROSS_REQUIREMENTS_N1
SORT AGGREGATE
INDEX RANGE SCAN MRP.MRP_GROSS_REQUIREMENTS_N1
NESTED LOOPS
NESTED LOOPS
NESTED LOOPS
INDEX RANGE SCAN INV.MTL_ITEM_CATEGORIES_U1
TABLE ACCESS BY INDEX ROWID INV.MTL_CATEGORIES_B
INDEX UNIQUE SCAN INV.MTL_CATEGORIES_B_U1
INDEX UNIQUE SCAN INV.MTL_CATEGORY_SETS_TL_U1
TABLE ACCESS BY INDEX ROWID INV.MTL_CATEGORY_SETS_TL
NESTED LOOPS ANTI
HASH JOIN
TABLE ACCESS BY INDEX ROWID MRP.MRP_GROSS_REQUIREMENTS
INDEX SKIP SCAN MRP.MRP_GROSS_REQUIREMENTS_N2
NESTED LOOPS
NESTED LOOPS
MERGE JOIN CARTESIAN
TABLE ACCESS FULL INV.MTL_PARAMETERS
BUFFER SORT
TABLE ACCESS BY INDEX ROWID APPLSYS.FND_LOOKUP_VALUES
INDEX RANGE SCAN APPLSYS.FND_LOOKUP_VALUES_U2
INDEX RANGE SCAN INV.MTL_SYSTEM_ITEMS_B_XX1
TABLE ACCESS BY INDEX ROWID INV.MTL_SYSTEM_ITEMS_B
TABLE ACCESS BY INDEX ROWID ONT.OE_ORDER_LINES_ALL
INDEX RANGE SCAN ONT.OE_ORDER_LINES_N3
}

Sorting in 6i and 10g reports

Hello All,
I am running 6i and 10g reports against a 10g database.
I ran one of the 6i report and it generated a report in one sorting ordear
and when i ran the same report on 10g ,it generated the report in ddifferent order.
Both the reports r run against the same 10g database.
The order by clause on the columns of the records r identical.
Now i wanted to understand how it is sorting in different orders in both 6i and 10g reports?
Thanks,
Ranz

Hi,
Please note the fact that 6i Reports is not certified to work with 10g Database. Hence it becomes impossible to address the sorting behavior of 6i Reports, though there is nothing different in the way it works. I would suggest you to use 10gR2 version of Reports services with 10g Database which is certified and supported. Thanks for your understanding.
Regards,
Anand

Bigfile 10g

Similar Messages

Maybe you are looking for