Objects (table, index, partition) fragmented

Hi all,
I run the script bellow to find fragmented objects:
select segment_name, segment_type, count(*) from dba_extents
where owner = ownname
group by segment_name, segment_type
having count(*) > 1
order by 3
And i get some liste like this:
object_names object_types 249
My question is the objects that i have are fragmented and what can i do to solve that fragmentation i mean to avoid object fragmentation.
regards
raistarevo

Hi,
You can go to the 8i documentation for more information:
http://download-west.oracle.com/docs/cd/A87860_01/doc/appdev.817/a76936/dbms_s2a.htm#1004668
But I advice you to read this thread below first.
http://asktom.oracle.com/pls/asktom/f?p=100:11:0::::P11_QUESTION_ID:8381899310385
Cheers

Similar Messages

IN_WRONG_TABLESPACE, object: table/index

Hi all,
Apologies for the repost of this topic. I have seen it a few times but without resolutions. My problem is as follows.
BR0970W Database administration alert - level: WARNING, type: IN_WRONG_TABLESPACE, object: (index) SAPSR3.D010INC~1, value: PSAPSR346C
BR0970W Database administration alert - level: WARNING, type: IN_WRONG_TABLESPACE, object: (table) SAPSR3.D010L, value: PSAPSR346C
This is IAORA.
TABART
TABSPACE
PCTINC
OFREELIST
OPCTFREE
APPL0
PSAPSR3
0000
1
10
APPL1
PSAPSR3
0000
1
10
APPL2
PSAPSR3
0000
1
10
CLUST
PSAPSR3
0000
1
10
POOL
PSAPSR3
0000
1
10
SDIC
PSAPSR3
0
1
10
SDOCU
PSAPSR3
0000
1
10
SLDEF
PSAPSR346D
0000
1
10
SLEXC
PSAPSR346D
0000
1
10
SLOAD
PSAPSR3
0000
1
10
SPROT
PSAPSR3
0000
1
10
SSDEF
PSAPSR346D
0000
1
10
SSEXC
PSAPSR346D
0000
1
10
SSRC
PSAPSR3
0000
1
10
TEMP
PSAPSR3
0000
1
10
USER
PSAPSR3USR
0000
1
10
USER1
PSAPSR3USR
0000
1
10
This is TAORA.
TABART
TABSPACE
PCTINC
OFREELIST
OFREEGROUP
OPCTFREE
OPCTUSED
APPL0
PSAPSR3
0000
001
01
10
40
APPL1
PSAPSR3
0000
1
1
10
40
APPL2
PSAPSR3
0000
1
1
10
40
CLUST
PSAPSR3
0000
1
1
10
40
POOL
PSAPSR3
0000
1
1
10
40
SDIC
PSAPSR3
0
1
1
10
40
SDOCU
PSAPSR3
0000
1
1
10
40
SLDEF
PSAPSR346D
0000
1
1
10
40
SLEXC
PSAPSR346D
0000
1
1
10
40
SLOAD
PSAPSR3
0000
1
1
10
40
SPROT
PSAPSR3
0000
1
1
10
40
SSDEF
PSAPSR346D
0000
1
1
10
40
SSEXC
PSAPSR346D
0000
1
1
10
40
SSRC
PSAPSR3
0000
1
1
10
40
TEMP
PSAPSR3
0000
1
1
10
40
USER
PSAPSR3USR
0000
1
1
10
40
USER1
PSAPSR3USR
0000
1
1
10
40
select tablespace_name from dba_tablespaces;
SYSTEM,PSAPUNDO,SYSAUX,PSAPTEMP,PSAPSR3,PSAPSR346C,PSAPSR3USR
Tablespace does exist as you can see above now to determine type of tablespace, and as per below query you can see it contains
both data and indexes.
select distinct(segment_type), tablespace_name from dba_segments order by tablespace_name;
SEGMENT_TYPE       TABLESPACE_NAME
INDEX              PSAPSR3
TABLE              PSAPSR3
INDEX              PSAPSR346C
TABLE              PSAPSR346C
TABLE              PSAPSR3USR
TYPE2 UNDO         PSAPUNDO
INDEX              SYSAUX
INDEX PARTITION    SYSAUX
LOB PARTITION      SYSAUX
LOBINDEX           SYSAUX
LOBSEGMENT         SYSAUX
As per note 655162 option 1 and 2 are applicable to me. But as this tablespace seems to be both a data and index tablespace I am thinking I need to create the tablespace entry in IAORA and TAORA.
How would I correctly edit these table entries and which of the following tables might also have to be edited?
DDART and DARTT are used to maintain the classes ( tabarts)
DD09L maps the tables to each class ( tabart)
TAORA/IAORA maps the classes to the tablespaces
TSORA lists the tablespaces.
As a non dba I find the sap note a bit confusing please advise.
Kind Regards,
Johan

Hi guys,
For clarification:
disp+work information
kernel release                46D
kernel make variant           46D_EXT
DBMS client library           OCI_920__OCI_7_API
DBSL shared library version   46D.00
compiled on                   Linux 2.6.5-7.202.5-smp #1_SMP_Thu_Aug_25_06:20:45_UTC_2005 x86_64
compiled for                  64 BIT
compile time                  Aug 10 2008 21:39:12
update level                  0
patch number                  2415
source id                     0.2415
supported environment
database (SAP, table SVERS)   46A
                              46B
                              46C
                              46D
DBMS server                   ORACLE 8.0.5..
                              ORACLE 8.0.6..
                              ORACLE 8.1.6..
                              ORACLE 8.1.7..
                              ORACLE 9.2.0..
                              ORACLE 10.2.0..
operating system              Linux 2.6
                              System build information:
                              LCHN :
System components:
ST-PI     2008_1_46C
ST-A/PI     01J_R3_46C
SAP_NOTES     46C
SAP_HR     46C
SAP_BASIS     46C
SAP_APPL     46C
SAP_ABA     46C
Regards,
J

Function based indexes on object tables

Hi,
I am trying to create a function based index on an object table. I am getting the following error:
SQL> create index cell1_indx on cell1(create_cell1(id)) indextype is mdsys.spatial_index;
create index cell1_indx on cell1(create_cell1(id)) indextype is mdsys.spatial_index
ERROR at line 1:
ORA-29855: error occurred in the execution of ODCIINDEXCREATE routine
ORA-13249: internal error in Spatial index: [mdidxrbd]
ORA-13249: Error in Spatial index: index build failed
ORA-13249: Stmt-Execute Failure: SELECT num_rows from all_tables where owner='ASHE' and table_name=
'CELL1'
ORA-06512: at "MDSYS.SDO_INDEX_METHOD_9I", line 7
ORA-06512: at line 1
Here cell1 is an object table.
Is the procedure for creating function based indexes on object tables different from relational tables?
Chinni

One of the many new features in Oracle 8i is the Function-Based Index (we will refrain from using FBI, but only just). This allows the DBA to create indexes on functions or expressions; these functions can be user generated pl/sql functions, standard SQL functions (non-aggregate only) or even a C callout.
A classic problem the DBA faces in SQL Tuning is how to tune those queries that use function calls in the where clause, and result in indexes created on these columns not to be used.
Example
Standard B-Tree index on SURNAME with cost based optimizer
create index non_fbi on sale_contacts (surname);
analyze index non_fbi compute statistics;
analyze table sale_contacts compute statistics;
SELECT count(*) FROM sale_contacts
WHERE UPPER(surname) = 'ELLISON';
Execution Plan
0 SELECT STATEMENT Optimizer=CHOOSE (Cost=3 Card=1 Bytes=17)
1 0 SORT (AGGREGATE)
2 1 TABLE ACCESS (FULL) OF 'SALES_CONTACTS' (Cost=3 Card=16 Bytes=272)
Now we use a function based index
create index fbi on sale_contacts (UPPER(surname));
analyze index fbi compute statistics;
analyze table sale_contacts compute statistics;
SELECT count(*) FROM sale_contacts WHERE UPPER(surname) = 'ELLISON';
Execution Plan
0 SELECT STATEMENT Optimizer=CHOOSE (Cost=2 Card=1 Bytes=17)
1 0 SORT (AGGREGATE)
2 1 INDEX (RANGE SCAN) OF 'FBI' (NON-UNIQUE) (Cost=2 Card=381 Bytes=6477)
The function-based index has forced the optimizer to use index range scans (retuning zero or more rowids) on the surname column rather than doing a full table scan (non-index lookup). Optimal performance does vary depending on table size, uniqueness and selectivity of columns, use of fast full table scans etc. Therefore try both methods to gain optimal performance in your database.
It is important to remember that the function-based B*Tree index does not store the expression results in the index but uses an "expression tree". The optimizer performs expression matching by parsing the expression used in the SQL statement and comparing the results against the expression-tree values in the function-based index. This comparison IS case sensitive (ignores spaces) and therefore your function-based index expressions should match expressions used in the SQL statement where clauses.
Init.ora Parameters
The following parameter must be set in your parameter file: QUERY_REWRITE_INTEGRITY = TRUSTED
QUERY_REWRITE_ENABLED = TRUE
COMPATIBLE = 8.1.0.0.0 (or higher)
Grants
Grants To create function-based indexes the user must be granted CREATE INDEX and QUERY REWRITE, or alternatively be granted CREATE ANY INDEX and GLOBAL QUERY REWRITE. The index owner must have EXECUTE access on the function used for the index. If execute access is revoked then the function-based index will be "disabled" (see dba_indexes).
Disabled Indexes
If your function-based index has a status of "disabled" the DBA can do one of the following:
a) drop and create the index (take note of its current settings)
b) alter index enable, function-based indexes only, also use disable keyword as required
c) alter index unusable.
Queries on a DISABLED index fail if the optimizer chooses to use the index.Here is an example ORA error:
ERROR at line 1: ORA-30554: function-based index MYUSER.FBI is disabled.
All DML operations on a DISABLED index also fail unless the index is also marked UNUSABLE and the initialization parameter SKIP_UNUSABLE_INDEXES is set to true.
Some more Examples
CREATE INDEX expression_ndx
ON mytable ((mycola + mycolc) * mycolb);
SELECT mycolc FROM mytable
WHERE (mycola + mycolc) * mycolb <= 256;
..or a composite index..
CREATE INDEX example_ndx
ON myexample (mycola, UPPER(mycolb), mycolc);
SELECT mycolc FROM myexample
WHERE mycola = 55 AND UPPER(mycolb) = 'JONES';
Restriction & Rule Summary
The following restrictions apply to function based indexes. You may not index:
a) LOB columns
b) REF
c) Nested table column
d) Objects types with any of the above data types.
Function-based indexes must always follow these rules:
a) Cost Based optimizer only, must generate statistics after the index is created
b) Can not store NULL values (function can not return NULL under any circumstance)
c) If a user defined pl/sql routine is used for the function-based index, and is invalidated, the index will become "disabled"
d) Functions must be deterministic (always return the same value for a known input)
e) The index owner must have "execute" access on function used in the function-based index. Revocation of the privilege will render the index "disabled"
f) May have a B-Tree and Bitmap index type only
g) Can not use expressions that are based on aggregate functions, ie. SUM, AVG etc.
h) To alter a function-based index as enabled, the function used must be valid, deterministic and the signature of the function matches the signature of the function when it was created.
Joel P�rez

ORA-00604 ORA-00904 When query partitioned table with partitioned indexes

Got ORA-00604 ORA-00904 When query partitioned table with partitioned indexes in the data warehouse environment.
Query runs fine when query the partitioned table without partitioned indexes.
Here is the query.
SELECT al2.vdc_name, al7.model_series_name, COUNT (DISTINCT (al1.vin)),
al27.accessory_code
FROM vlc.veh_vdc_accessorization_fact al1,
vlc.vdc_dim al2,
vlc.model_attribute_dim al7,
vlc.ppo_list_dim al18,
vlc.ppo_list_indiv_type_dim al23,
vlc.accy_type_dim al27
WHERE ( al2.vdc_id = al1.vdc_location_id
AND al7.model_attribute_id = al1.model_attribute_id
AND al18.mydppolist_id = al1.ppo_list_id
AND al23.mydppolist_id = al18.mydppolist_id
AND al23.mydaccytyp_id = al27.mydaccytyp_id
AND ( al7.model_series_name IN ('SCION TC', 'SCION XA', 'SCION XB')
AND al2.vdc_name IN
('PORT OF BALTIMORE',
'PORT OF JACKSONVILLE - LEXUS',
'PORT OF LONG BEACH',
'PORT OF NEWARK',
'PORT OF PORTLAND'
AND al27.accessory_code IN ('42', '43', '44', '45')
GROUP BY al2.vdc_name, al7.model_series_name, al27.accessory_code

I would recommend that you post this at the following OTN forum:
Database - General
General Database Discussions
and perhaps at:
Oracle Warehouse Builder
Warehouse Builder
The Oracle OLAP forum typically does not cover general data warehousing topics.

Database objects Tables, Views, Indexes not expand in Connections navigator

In SQL Developer tool when I clicked on any database object: Tables, Views, Indexes, Packages, Procedures, Functions, and Triggers none of them expands in Connections navigator so I am not able to see all tables, Views, Indexes in this schema objects.
Please advise
Thanks a lot
Vincent

If the user you're connecting with is not the owner of the objects, you can access them through the Other Users node.
Hope that helps,
K.

A question regarding database table partitioning and table indexes in 10g

We are considering partitioning a large table in our 10g database, in order to improve response time. I believe I understand the various partitioning options, but am wondering about the indexes built over the table. When the table is partitioned, will the indexes also be partitioned "automatically"? Or do I need to also partition the indexes as well?
Thank you in advance to any and all who respond to this question.

Hello,
When you build your partiton table you just need to create indexes locally and they will be partitioned automatically, see following example
CREATE TABLE YY_EVENT
PART_KEY       DATE                              NOT NULL,
SUBPART_VALUE NUMBER                             NULL,
EVENT_NAME     VARCHAR2(30 BYTE)                  NULL,
EVENT_VALUE    NUMBER                             NULL
TABLESPACE TEST_DATA
PARTITION BY RANGE (PART_KEY)
PARTITION Y_EVENT_200901 VALUES LESS THAN (TO_DATE(' 2009-02-01 00:00:00', 'SYYYY-MM-DD HH24:MI:SS', 'NLS_CALENDAR=GREGORIAN'))
    TABLESPACE TEST_DATA,
PARTITION Y_EVENT_200902 VALUES LESS THAN (TO_DATE(' 2009-03-01 00:00:00', 'SYYYY-MM-DD HH24:MI:SS', 'NLS_CALENDAR=GREGORIAN'))
    TABLESPACE TEST_DATA
-- This will create paritioned indexes automatically
CREATE INDEX MY_IDX ON YY_EVENT
(EVENT_NAME)
TABLESPACE TEST_DATA
LOGGING
LOCAL;Regards
Edited by: OrionNet on Feb 25, 2009 12:05 PM

Loading data to indexed partitioned table

Hi,
My table is partitioned on day wise and index is created on first column (non unique)
is it possible to disable the last partition index disable to increase the speed of data loading to last partition.
create table my_table(sr_no,sr_name,doj)
partitioned on day wise field doj (date of joining).
my table size is very high (1TB) ,

OraFighter wrote:
Is it possible to disable only last partition..?
modify_index_partition
Use the modify_index_partition clause to modify the real physical attributes, logging attribute, or storage characteristics of index partition partition or its subpartitions. For a hash-partitioned global index, the only subclause of this clause you can specify is UNUSABLE.
when all else fails Read The Fine Manual
ALTER INDEX

Partitioning Tables/Indexes

Hi,
Oracle Version 10.2.0
O/S Version: SUSE Linux
Currently all the tables and indexes are stored in the NFS mount ponit. I would like to know whether can I partition the tables/indexes onto local storage temporarily.
Thanks

Hi
Yes you can do this. But if you have some partitions on NAS and some on local disk then depending on the nature of the queries/DML you will see some performance issues.
MSK

Impossible to create an index with an object table

Is it possible to use object tables with Oracle Spatial ?
With Oracle 8.1.7.0.0, here is the example where I encounter a problem (this example works of course with an equivalent relational table) :
create or replace type zonegeo as object (
id integer, definitionGeo MDSYS.SDO_GEOMETRY
create table essaigeo of zonegeo (id PRIMARY KEY)
OBJECT ID PRIMARY KEY;
INSERT INTO USER_SDO_GEOM_METADATA
VALUES ('ESSAIGEO','DEFINITIONGEO',
MDSYS.SDO_DIM_ARRAY(
MDSYS.SDO_DIM_ELEMENT('X', 47680.000, 1197822.000, 0.005),
MDSYS.SDO_DIM_ELEMENT('Y', 1620431.000, 2677441.000, 0.005)
NULL -- SRID
CREATE INDEX ESSAIGEO_SPATIAL_IDX
ON ESSAIGEO(DEFINITIONGEO)
INDEXTYPE IS MDSYS.SPATIAL_INDEX
PARAMETERS ('SDO_LEVEL = 6);
ERREUR ` la ligne 1 :
ORA-29855: erreur d'exicution de la routine ODCIINDEXCREATE
ORA-13203: ichec de lecture de la table USER_SDO_GEOM_METADATA
ORA-13203: ichec de lecture de la table USER_SDO_GEOM_METADATA
ORA-06512: ` "MDSYS.SDO_INDEX_METHOD", ligne 8
ORA-06512: ` ligne 1

In Oracle 8.1.7 you cannot embed a geometry type in another type and index it.
In 9i, you can , but not in the way you've defined it, i.e. you have to create a regular
table, and have a column of type zonegeo, and make a few other changes, i.e.:
create or replace type zonegeo as object (
id integer, definitionGeo MDSYS.SDO_GEOMETRY
create table essaigeo (zone zonegeo);
INSERT INTO USER_SDO_GEOM_METADATA
VALUES ('ESSAIGEO','ZONE.DEFINITIONGEO',
MDSYS.SDO_DIM_ARRAY(
MDSYS.SDO_DIM_ELEMENT('X', 47680.000, 1197822.000, 0.005),
MDSYS.SDO_DIM_ELEMENT('Y', 1620431.000, 2677441.000, 0.005)
NULL -- SRID
CREATE INDEX ESSAIGEO_SPATIAL_IDX
ON ESSAIGEO(ZONE.DEFINITIONGEO)
INDEXTYPE IS MDSYS.SPATIAL_INDEX
PARAMETERS ('SDO_LEVEL = 6);

Run Rebuild Index Task daily on database but about 77 tables still highly fragmented over 80% !!!

Hello everyone
On our particular database server, we run the Rebuild Index Task (Using classic Maintenance Plan Designer) every night. Running the script below, I saw that about 77 tables had an avg_fragmentation_in_percentage between 80% and 99% !!
SELECT OBJECT_NAME(ind.OBJECT_ID) AS TableName,
ind.name AS IndexName, indexstats.index_type_desc AS IndexType,
indexstats.avg_fragmentation_in_percent
FROM sys.dm_db_index_physical_stats(DB_ID(), NULL, NULL, NULL, NULL) indexstats
INNER JOIN sys.indexes ind
ON ind.object_id = indexstats.object_id
AND ind.index_id = indexstats.index_id
WHERE indexstats.avg_fragmentation_in_percent > 30--You can specify the percent as you want
ORDER BY indexstats.avg_fragmentation_in_percent DESC
I dont understand why these tables are highly fragmented after a daily index rebuild! Unless the users are doing heavy inserts/updates/deletes during the day.
Anyone has an idea of the possible causes of these results??
Thank you all in advance

Hallo Efyuzegeekgurl,
this is a normal behaviour when your table is only a small one. The reason for that behaviour is the following:
The dmv sys.dm_db_index_physical_stats counts each page which is not located at the very next one of the same table as a "fragment". If the first data page is 1700 and the second one is located on 1705 SQL server will count it as a fragment.
The basic allocation algorithm of Microsoft SQL Server is that new data pages will be created in "mixed extents". An extent is a contigious line of 8 consecutive data pages. This is for historical reasons when storage was expensive and data should
use as much as possible of allocated storage.
If a new table will be created the very first 8 pages are not located one after the other but "could" be located on different extents. If your table has only 9 data pages than 8 pages will count as "fragmented" because of their non consecutive
allocation. After 8 pages have been allocated Microsoft SQL Server will ALWAYS use a full extent for the next 8 pages (and so on!).
To understand this behaviour use the following example which creates a table with a record length of 8K. The next command will create 10 records (which means 10 data pages).
CREATE TABLE dbo.foo
Id INT NOT NULL IDENTITY (1, 1),
c1 CHAR(8000) NOT NULL DEFAULT ('filler')
GO
SET NOCOUNT ON;
GO
INSERT INTO dbo.foo DEFAULT VALUES
GO 10
When you check the page allocation you'll find the first 8 data pages not in a consecutive row but "scrambled" into different pages:
SELECT database_id,
index_id,
partition_id,
allocation_unit_type_desc,
extent_page_id,
allocated_page_page_id,
is_mixed_page_allocation,
page_type_desc
FROM sys.dm_db_database_page_allocations
DB_ID(),
OBJECT_ID('dbo.foo', 'U'),
0,
NULL,
'DETAILED'
) AS DDDPA
WHERE
DDDPA.is_allocated = 1
ORDER BY
DDDPA.is_iam_page DESC,
DDDPA.page_level DESC;
GO
You will see that the first 8 pages are located in a MIXED extent. Although the pages are in a consecutive order in the extent 221112 it is not guaranteed!
You can see from the very first three records that they are not in a consecutive row stored.
Now the fragmentation of the data seems to be quite high because we have 4 breaks in the rows. If we compare this value to the "fragmentation in sys.dm_db_index_physical_stats we will see at least the same result:
SELECT index_type_desc,
alloc_unit_type_desc,
DDIPS.avg_fragmentation_in_percent,
DDIPS.fragment_count,
DDIPS.page_count,
avg_page_space_used_in_percent
FROM sys.dm_db_index_physical_stats
DB_ID(),
OBJECT_ID('dbo.foo', 'U'),
NULL,
NULL,
'DETAILED'
) AS DDIPS;
So - just from my point of view - don't count only to the fragmentation in percent because if the table is to small it will ALWAYS be over 30%. Take more into account the density of the pages and - as all others have mentioned - the number of pages of the
index.
I would consider indexes with more or equal to 1.000 pages.
Another tip: Forget about the f... maintenance plans. These "plans" are not worth the time and money because you cannot control it in a more precise way. Have a look to the solution of Ola Hallengren and implement his solution - a great master
piece of index maintenance:
http://ola.hallengren.com
All the best to the community :)
MCM - SQL Server 2008
MCSE - SQL Server 2012
db Berater GmbH
SQL Server Blog (german only)

(oracle 8i)Alter Table table coalesce partition

Hi all,
Need assistance in solving a problem. I have a possibly large fragemented table. I tried to run a coalese command ALTER TABLE EMPTY_COPY COALESCE PARTITION
got an error: 'ora -14501 - object is not partitioned'
NOt sure how to proceed, I am working in oracle 8i environment.
Should I do :
ALTER TABLESPACE MY_DATA COALESCE
ALTER INDEX EMPTY_COPY_PK COALESCE
ALTER INDEX EMPTY_COPY_PK REBUILD
ALTER TABLE MY_DATA.EMPTY_COPY MOVE TABLESPACE NEW_DATA
Not sure if the syntax is correct or which to use, are there any redundancies in the commands above.
Thanks kindly for any input you may provide.

thanks.
My real problem is an ora 1653 'UNABLE TO EXTEND TABLE' error where I could not insert into a table. The PCT_INCREASE was at 25 and the next_extext was at 160mb. Way too large. There still looks to be l plenty of space available for an another extent but it is not being allocated.
Would this apply?

Processing SCHEMA_EXPORT/TABLE/INDEX/DOMAIN_INDEX/INDEX

I tried to import my 20GB data into my database but it is pending/hanging almost 1 day at this line, which is
Processing SCHEMA_EXPORT/TABLE/INDEX/DOMAIN_INDEX/INDEX .
My db version is :Version 11.1.0.7.0
What could be the reason? Why it is waiting so long on this line? It is locking indexes?

Windows Server 2008 R2 Enterprise
impdp user/pass@DB exclude=statistics schemas=user dumpfile=a.dmp log=a.log
Import: Release 11.1.0.7.0 - 64bit Production on Friday, 10 August, 2012 17:04:03
Copyright (c) 2003, 2007, Oracle. All rights reserved.
Connected to: Oracle Database 11g Enterprise Edition Release 11.1.0.7.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
Master table "ODB"."SYS_IMPORT_FULL_01" successfully loaded/unloaded
Starting "ODB"."SYS_IMPORT_FULL_01": odb/********@TEST parallel=4 dumpfile=UAT_08082012.DMP
Processing object type SCHEMA_EXPORT/USER
ORA-31684: Object type USER:"ODB" already exists
Processing object type SCHEMA_EXPORT/SYSTEM_GRANT
Processing object type SCHEMA_EXPORT/ROLE_GRANT
Processing object type SCHEMA_EXPORT/DEFAULT_ROLE
Processing object type SCHEMA_EXPORT/TABLESPACE_QUOTA
Processing object type SCHEMA_EXPORT/PRE_SCHEMA/PROCACT_SCHEMA
Processing object type SCHEMA_EXPORT/TYPE/TYPE_SPEC
Processing object type SCHEMA_EXPORT/DB_LINK
Processing object type SCHEMA_EXPORT/SEQUENCE/SEQUENCE
Processing object type SCHEMA_EXPORT/TABLE/TABLE
Processing object type SCHEMA_EXPORT/TABLE/TABLE_DATA
. . imported "ODB"."PN_INVENTORY_HISTORY" 218.6 MB 1302517 rows
SCHEMA_EXPORT/TABLE/INDEX/STATISTICS/FUNCTIONAL_AND_BITMAP/INDEX_STATISTICS
Processing object type SCHEMA_EXPORT/TABLE/STATISTICS/TABLE_STATISTICS
Processing object type SCHEMA_EXPORT/TABLE/INDEX/DOMAIN_INDEX/INDEX
and waiting here since 1 day..
alert log file has some warnings like:
<txt>Warning: drop_queue_table: No evaluation for the queue table: ODB.ROS_IN_QUEUE_TABLE
</txt>
</msg>
<msg time='2012-08-11T00:29:21.710+03:00' org_id='oracle' comp_id='rdbms'
client_id='' type='UNKNOWN' level='16'
Thread 1 advanced to log sequence 91 (LGWR switch)
Current log# 1 seq# 91 mem# 0: D:\APP\TRAXADMIN\ORADATA\TEST\REDO01.LOG
Sat Aug 11 10:16:16 2012
Thread 1 advanced to log sequence 92 (LGWR switch)
Current log# 2 seq# 92 mem# 0: D:\APP\TRAXADMIN\ORADATA\TEST\REDO02.LOG
Sat Aug 11 10:16:40 2012
Thread 1 cannot allocate new log, sequence 93
Checkpoint not complete_
Current log# 2 seq# 92 mem# 0: D:\APP\TRAXADMIN\ORADATA\TEST\REDO02.LOG_
Thread 1 advanced to log sequence 93 (LGWR switch)_
Current log# 3 seq# 93 mem# 0: D:\APP\TRAXADMIN\ORADATA\TEST\REDO03.LOG_
Thread 1 cannot allocate new log, sequence 94_
Checkpoint not complete_
Current log# 3 seq# 93 mem# 0: D:\APP\TRAXADMIN\ORADATA\TEST\REDO03.LOG_
Thread 1 advanced to log sequence 94 (LGWR switch)_
Current log# 1 seq# 94 mem# 0: D:\APP\TRAXADMIN\ORADATA\TEST\REDO01.LOG_
Sat Aug 11 10:16:56 2012_
Thread 1 cannot allocate new log, sequence 95_
Checkpoint not complete_
Current log# 1 seq# 94 mem# 0: D:\APP\TRAXADMIN\ORADATA\TEST\REDO01.LOG
Thread 1 advanced to log sequence 95 (LGWR switch)
Current log# 2 seq# 95 mem# 0: D:\APP\TRAXADMIN\ORADATA\TEST\REDO02.LOG
<txt>Errors in file d:\app\traxadmin\diag\rdbms\test\test\trace\test_j003_6036.trc:
ORA-12012: error on auto execute of job 74639
ORA-20111: ORA-24010: QUEUE ODB.IFACE_AEX_IN_Q does not exist
ORA-06512: at "ODB.PKG_IFACE_QUEUE", line 80
ORA-24010: QUEUE ODB.IFACE_AEX_IN_Q does not exist
ORA-06512: at "ODB.PKG_IFACE_QUEUE", line 48
ORA-06512: at "ODB.PKG_AEX_INBOUND"
Edited by: user638937 on 11.Ağu.2012 00:27

Troubles editing tables with partitions

I'm running SQL Developer 1.5.3 against Oracle 10/11 databases and SQL Developer has trouble with my partitioned tables. Both the schema owner and sys users experience the same problems.
The first time I try to edit a table, I get an "Error Loading Objects" dialog with a NullPointException message. If I immediately turn around and try to edit the table again, I get the Edit Table dialog. That's annoying but there's at least a work-around.
Next, if I select the Indexes pane, I can view the first index but selecting another one results in an "Index Error on <table>" error dialog. The message is "There are no table partitions on which to define local index partitions". At this point, selecting any of the other panes (Columns, Primary Key, etc.) results in the same dialog. While the main Partitions tab shows my partitions, I cannot see them in the Edit Table dialog. In fact, the Partition Definitions and Subpartition Templates panes are blank.
Does anyone else see this behavior? Version 1.5.1 behaved the same way so it's not new.
Of course I've figured out how to do everything I need through SQL but it would be handy if I could just use the tool.
Thank you.

Most of my tables are generated from a script so this morning I decided to just create a very basic partitioned table. It contained a NUMBER primary key and a TIMESTAMP(6) column to use with partitioning. That table worked just fine in SQL Developer.
At that point I tried to figure out what is different about my tables and I finally found the difference... Oracle Spatial. If I add an MDSYS.SDO_GEOMETRY column to my partitioned table, SQL Developer starts having issues.
I also have the GeoRaptor plugin installed so I had to wonder if it was interfering with SQL Developer. I couldn't find an option to uninstall an extension so I went into the sqldeveloper/extensions directory and removed GeoRaptorLibs and org.GeoRaptor.jar. GeoRaptor doesn't appear to be installed in SQL Developer anymore but I still see the same behavior.
It appears that there is an issue in SQL Developer with Oracle Spatial and partitioning. Can someone confirm this?

Regarding Renaming INDEX Partitions

Hi All,
I have the following syntax for renaming table partitions/subpartitions :
ALTER TABLE SMTP_MSG_TRAFFIC_FCT RENAME PARTITION FOR (20100310) TO BASE_FACT_20100310;
ALTER TABLE SMTP_MSG_TRAFFIC_FCT RENAME SUBPARTITION FOR (20100310,19) TO BASE_FACT_20100310_MAILBOX;
I want to do the same thing for renaming the index partitions/subpartitions :
ALTER INDEX SMTP_MSG_TF_FX02_ARR_TM_DIM_ID RENAME PARTITION FOR (20100310) TO BASE_FACT_20100310;
ALTER TABLE SMTP_MSG_TF_FX02_ARR_TM_DIM_ID RENAME SUBPARTITION FOR (20100310,19) TO BASE_FACT_20100310_MAILBOX;
But I get the following error:
SQL> ALTER INDEX SMTP_MSG_TF_FX02_ARR_TM_DIM_ID RENAME PARTITION FOR (20100310) TO BASE_FACT_20100310;
ALTER INDEX SMTP_MSG_TF_FX02_ARR_TM_DIM_ID RENAME PARTITION FOR (20100310) TO BASE_FACT_20100310
ERROR at line 1:
ORA-14006: invalid partition name
Is it possible to rename the partition in this way? Or can I set any parameter that will ensure that when the base table partition name changes, it will also change the index partition name?
Thanks & Regards,
Aniket

yes its possible:
SQL>ALTER INDEX index_name RENAME PARTITION index_partiton_name TO new_index_partition;
You are getting error because :
a partition name is expected but not present as you typed,
enter an appropriate partition name, will solve the problem.
Edited by: adnanKaysar on Mar 18, 2010 12:32 PM

New tables & indexes created do not show up in dba_segments view

Dear all,
I have created 3 tables and some indexes, but these objects do not show up in dba_segments view. Is this a normal behaviour? Previously, with dictionary managed tablespace, I can specify the minimum extent to create, when the table/index is created. But I'm not sure how the locally managed tablespace work. Please do advice. Thank you very much in advance.
I'm using Oracle 11g R2 (11.2.0.1.0) for Microsoft Windows (x64), running on Windows 7.
For the purpose of reproducing this issue, I have created the tablespaces as follow:
CREATE TABLESPACE CUST_DATA
DATAFILE 'd:\app\asus\oradata\orcl11gr2\CUST_DATA01.DBF' SIZE 512K
AUTOEXTEND ON NEXT 256K MAXSIZE 2000K
EXTENT MANAGEMENT LOCAL UNIFORM SIZE 256K
SEGMENT SPACE MANAGEMENT AUTO;
CREATE TABLESPACE CUST_INDX
DATAFILE 'd:\app\asus\oradata\orcl11gr2\CUST_INDX.DBF' SIZE 256K
AUTOEXTEND ON NEXT 128K MAXSIZE 2000K
EXTENT MANAGEMENT LOCAL UNIFORM SIZE 128K
SEGMENT SPACE MANAGEMENT AUTO;
CREATE TABLE CUSTOMER_MASTER (CUST_ID VARCHAR2 (10),
CUST_NAME VARCHAR2 (30),
EMAIL VARCHAR2 (30),
DOB DATE,
ADD_TYPE CHAR (2) CONSTRAINT CK_ADD_TYPE CHECK (ADD_TYPE IN ('B1','B2','H1','H2')),
CRE_USER VARCHAR2 (5) DEFAULT USER,
CRE_TIME TIMESTAMP (3) DEFAULT SYSTIMESTAMP,
MOD_USER VARCHAR2 (5),
MOD_TIME TIMESTAMP (3),
CONSTRAINT PK_CUSTOMER_MASTER PRIMARY KEY (CUST_ID) USING INDEX TABLESPACE CUST_INDX)
TABLESPACE CUST_DATA;
SQL> SELECT TABLE_NAME, TABLESPACE_NAME
2 FROM USER_TABLES
3 WHERE TABLE_NAME LIKE 'CUST%';
TABLE_NAME TABLESPACE_NAME
CUSTOMER_MASTER CUST_DATA
SQL> SELECT INDEX_NAME, TABLESPACE_NAME
2 FROM USER_INDEXES
3 WHERE TABLE_NAME LIKE '%CUST%';
INDEX_NAME TABLESPACE_NAME
PK_CUSTOMER_MASTER CUST_INDX
SQL> SELECT SEGMENT_NAME, SEGMENT_TYPE, TABLESPACE_NAME, BYTES
2 FROM USER_SEGMENTS;
no rows selected

Prior to 11g, when you created a table or whatever, you automatically allocated one extent.
This is now no longer true and depends on a parameter I don't remember.
dba_segments is a summary of dba_extents.
Obviously, if there is no extent allocated, the table (view is defined with inner join) will not show up.
You could qualify this is as a bug and submit a SR to Oracle. But then the performance impact may be huge.
Sybrand Bakker
Senior Oracle DBA

Objects (table, index, partition) fragmented

Similar Messages

Maybe you are looking for