Re- organize a tablespace

how do i re-organize a tablespace.
For example,
Extent
Tablespace Segment Segment Block size
name Status name type number (blocks)
TASK1 Space allocated for T1 TABLE 9 8
TASK1 Space allocated for T1 TABLE 17 8
TASK1 Free space 25 16
TASK1 Space allocated for T1 TABLE 41 8
how to i move T1 to occupy the first 4 extents?
do i have to use DBMS_ROWID.ROWID_ROW_NUMBER(ROWID) etc?
Edited by: user11298107 on Nov 15, 2009 8:18 PM
Edited by: user11298107 on Nov 15, 2009 8:19 PM

ALTER TABLE t1 MOVE TABLESPACE task;to move t1 to another extent(s) within the same tablespace.
However, once you move a table, you HAVE to rebuild all indexes on that table.
ALTER INDEX indexname REBUILD TABLESPACE indextablespace;for every indexname on table t1.
Generally, there shouldn't be reason to do this within the same tablespace. You could be moving tables and indexes to new or other tablespaces eg
ALTER TABLE t1 MOVE TABLESPACE other_tbs;
ALTER INDEX indexname REBUILD TABLESPACE other_index_tbs;Hemant K Chitale

Similar Messages

Segment organization within tablespace

Hi There,
I was trying to organize objects within the tablespaces and moving things around when I got up to this:
I needed to get rid of the PROD_T3 tablespace so I moved everything out of it apart from the below
SQL> select owner,segment_name,segment_type, TABLESPACE_NAME,bytes/1024/1204 from dba_Segments where tablespace_name='PROD_T3' order by 3;
OWNER                SEGMENT_NAME                   SEGMENT_TYPE       TABLESPACE_NAME                BYTES/1024/1204
PROD                 PK_VOTER_REG_DOC               INDEX              PROD_T3                          122.471761
PROD                 SYS_IL0000186869C00026$$       LOBINDEX           PROD_T3                          .053156146
PROD                 SYS_LOB0000186869C00026$$      LOBSEGMENT         PROD_T3                          .053156146
PROD                 PLAN_TABLE                     TABLE              PROD_T3                          .106312292
PROD                 BIN$IEDOLJmsSj6isKTb5Z2cOQ==$0 TABLE              PROD_T3                          .053156146and so I started investigating each segment in the tablespace:
SQL> select owner, index_name, table_name, tablespace_name, status from dba_indexes where index_name='PK_VOTER_REG_DOC';
OWNER                INDEX_NAME                     TABLE_NAME                     TABLESPACE_NAME        STATUS
PROD                 PK_VOTER_REG_DOC               VOTER_REG_DOC                  PROD_T3                VALID
SQL> select owner, table_name, tablespace_name, status from dba_tables where table_name='VOTER_REG_DOC';
OWNER                TABLE_NAME                     TABLESPACE_NAME                STATUS
PROD                 VOTER_REG_DOC                                                 VALIDI'm a bit surprised form the above that there isn't a tablespace?!! I can describe the table and get a count for the number of rows in there:
SQL> desc prod.VOTER_REG_DOC
Name                                                                     Null?    Type
VOTER_ID                                                           NOT NULL NUMBER(10)
CARD_NO                                                              NOT NULL CHAR(9)
SQL> select count(*) from prod.VOTER_REG_DOC;
COUNT(*)
   3656468But when I look at dba_segments, I can't see it:
SQL> select owner,segment_name, segment_type , tablespace_name from dba_segments where owner='PROD' and segment_name='VOTER_REG_DOC' order by 1,2
no rows selected
SQL>
SQL> select owner,segment_name, segment_type , tablespace_name from dba_segments where owner='PROD' and segment_name like '%VOTER_REG%' order by 2,3;
OWNER                SEGMENT_NAME                   SEGMENT_TYPE       TABLESPACE_NAME
PROD                 PK_VOTER_REG_DOC               INDEX              PROD_T3
SQL>Where am I going wrong with this? Also, I was surprised to see an object or a segment called "BIN$IEDOLJmsSj6isKTb5Z2cOQ==$0" ? I thought any BIN* would be sitting in DBA_RECYCLEBIN as the object(s) been deleted or am I wrong?
Appreciate the help.
Cheers

>
I believe you will find that you are looking at the definition entry for an index organized table.
select IOT_TYPE from dba_tables where table_name = 'VOTER_REG_DOC'
if it returns 'IOT' then that is what you have.
>
Bingo..
SQL> select owner, IOT_TYPE from dba_tables where table_name = 'VOTER_REG_DOC';
OWNER                IOT_TYPE
PROD                 IOTNow that's that sorted; how about the BIN$ item? can I drop this item? How can go on about investigating it?
SQL> r
1* select owner,segment_name,segment_type, TABLESPACE_NAME,bytes/1024/1204 from dba_Segments where tablespace_name='PROD_T3' order
by segment_type
OWNER                SEGMENT_NAME                   SEGMENT_TYPE       TABLESPACE_NAME                BYTES/1024/1204
PROD                 SYS_IL0000186869C00026$$       LOBINDEX           PROD_T3                          .053156146
PROD                 SYS_LOB0000186869C00026$$      LOBSEGMENT         PROD_T3                          .053156146
PROD                 PLAN_TABLE                     TABLE              PROD_T3                          .106312292
PROD                 BIN$IEDOLJmsSj6isKTb5Z2cOQ==$0 TABLE              PROD_T3                          .053156146Edited by: rsar001 on Mar 19, 2010 1:37 PM

How do I increase the length in data file

I have been getting this error, can anyone tell me why I'm getting the error below and help me fix the the error( increase the length of data file.
This is my Control file
LOAD DATA
INFILE Job.dat
APPEND INTO TABLE job
FIELDS TERMINATED BY x'09'
(PositionID, jobID, title, code, family)
This is my data in my data file
PositionID JobID Title Code family
50003490 1 NULL 001610 NULL
50004865 1 NULL 001615 NULL
ERROR
SQL*Loader: Release 10.2.0.1.0 - Production on Fri Jul 13 10:17:33 2007
Copyright (c) 1982, 2005, Oracle. All rights reserved.
Control File: Position1.ctl
Data File: Job.dat
Bad File: Job.bad
Discard File: none specified
(Allow all discards)
Number to load: ALL
Number to skip: 0
Errors allowed: 50
Bind array: 64 rows, maximum of 256000 bytes
Continuation: none specified
Path used: Conventional
Table JOB, loaded from every logical record.
Insert option in effect for this table: APPEND
Column Name Position Len Term Encl Datatype
POSITIONID FIRST * WHT CHARACTER
JOBID NEXT * WHT CHARACTER
TITLE NEXT * WHT CHARACTER
CODE NEXT * WHT CHARACTER
FAMILY NEXT * WHT CHARACTER
Record 1: Rejected - Error on table JOB, column POSITIONID.
Field in data file exceeds maximum length
Record 2: Rejected - Error on table JOB, column POSITIONID.
Field in data file exceeds maximum length
Record 3: Rejected - Error on table JOB, column POSITIONID.
Field in data file exceeds maximum length
Record 4: Rejected - Error on table JOB, column POSITIONID.

this is the structure of my table
create table job (PositionID number(20) not null,
jobID number(20) not null, title nvarchar2(255), code nvarchar2(255), family nvarchar2(255),
constraint job primary key (PositionID, jobID))
organization index
Tablespace Position
pctthreshold 20
overflow tablespace users;
comment on table job is 'This table defines the job(s) associated with the position. There can be multiple jobs allowed although the preferred business rule is for one job per position.';
alter table job add constraint FKjob373174 foreign key (PositionID) references Position;

Regarding Overflow segments in IOT

can any one please tell me what will be contents of the overflow segments in an IOT.
documentation says
An OVERFLOW clause, which preserves dense clustering of the B-tree index by storing the row column values exceeding a specified threshold in a separate overflow data segment. This data segment can be in another tablespace also.
An OVERFLOW clause, which preserves dense clustering of the B-tree index by enabling the storage of some of the nonkey columns in a separate overflow data segment.
during the insert operations if the data extent threshold limit is reached it alloates a overflow segment right..
in the documentation it also says that non key columns in the table are also stored in the overflow segments.
CAN ANY ONE TELL ME WHAT WILL BE THE CONTENTS OF INDEX SEGMENTS AND OVERFLOW SEGMENTS FOR THE FOLLOWING TABLE.
CREATE TABLE admin_docindex2(
token CHAR(20),
doc_id NUMBER,
token_frequency NUMBER,
token_offsets VARCHAR2(512),
CONSTRAINT pk_admin_docindex2 PRIMARY KEY (token, doc_id))
ORGANIZATION INDEX
TABLESPACE admin_tbs
PCTTHRESHOLD 20
INCLUDING token_frequency
OVERFLOW TABLESPACE admin_tbs2;

The contents of the oveflow segment will be all columns defined after the including token_frequency column, in your case the token_offsets column.
As definitions for all the remaining columns within the index structure are relatively small, the pctthreashold value of 20% is not likely to come into play.
Cheers
Richard Foote
http://richardfoote.wordpress.com/

Upgrade to 11g on Windows Server 2008

Hi
I'm planning an upgrade of a 9.2.0.8 32-bit database to 11g 64-bit. The database is around 250GB in size, and is hosted on a Windows 2003 server. The plan is to host the upgraded database on a new Windows 2008 64-bit server. I have a maximum two-hour outage window
My initial thoughts for the upgrade procedure were as follows:
1) Install 9i 32-bit and 11g 64-bit on the new 2008 server
2) A day or two before the upgrade, clone the 9i database to the new 2008 server and open the database in recovery mode
3) Rollforward the clone database by applying archive logs from the source until the start of the outage window
4) Shutdown the old database, copy the last logs to the new server, apply them to the clone database, and run the upgrade procedure.
Then I realised that 9.2.0.8 won't install on Windows Server 2008 as it's not certified.
Does anyone have any suggestions regarding the best way I could do this?

250GB is not all current data and hopefully is partitioned. Approach this from the standpoint of moving 90+% before the outage. Tell us more about the organization and tablespaces.
Amazon.com has got the upgrade in place optimized to only to 16 minutes per database. I can't tell you the details but I can tell you that much of what Oracle does in its upgrade scripts can be done prior to the outage. And some of it after the database is opened again. See if you can slice and dice the upgrade script to minimize downtime too.

NEED HELP ASAP-populate contents from 5 tables into one master table

Scenario:
Assign a new_customer_id to each existing customer of our three business. A master lookup table (M) was given to me with pre-populated (SEQ_NOs), (NEW_CUSTIDs), and NULL in (OLD_CUSTIDS). My duty is to
(1) Fill the M.OLD_CUSTID column with existing customer ids from T1, T2, T3 (uniquely).
(2) Once the master lookup table is filled, add (SEQ_NO), and (NEW_CUSTID) column to the 3 existing customer tables to hold the new information.
(3) At the end of the project, remove the existing customer ids from the T1, T2, T3.
My problem is that there are no associations between the master table and existing customer tables (no keys). The code would be:
update M
set OLD_CUSTID= (select OLD_CUSTID from T1 where M.??=T1.??)
Since the M.OLD_CUSTID and T1.NEW_CUSTID are NULL at this stage, and there are no keys to tie them together. I don't know how to fill both tables. Can someone help me ASAP? Thanks in Advance.
-ORACLE Newbi

I am building a "MASTER LOOKUP TABLE" to map the NEW_CUSTID and the OLD_CUSTID. The columns in this M table are:
CREATE TABLE MKT.M
     "LOOKUP_SEQ" INTEGER, <=== from sequence
     "NEW_CUSTID" CHAR(6), <=== populated with strings given by biz analyst
     "OLD_CUSTID" INTEGER, <=== need to dump all existing custid (unique)
     PRIMARY KEY ("NEW_CUSTID") RELY NOVALIDATE
     ORGANIZATION INDEX TABLESPACE "MKT"
Table T1/T2/T3 are slightly different but they all contain:
CUST_ID INTEGER
CUST_NAME CHAR(50)
CUST_SINCE DATE
CUST_ADDR1 CHAR(30)
CUST_ADDR2 CHAR(30)
DITY CHAR(30)
STATE CHAR(2), etc.
Since M is the lookup table for old-to-new customer ID mapping. There are no need to associat other than just enter the old IDs into the M table.
Thanks for helping me. Any suggestion?

TEMP table & IOT table

Hi all,
I have the following observation related to TEMP table. I am wondering if it is always correct.
When you query dba_tables the tablespace_name is empty if it is a temporary table. Also it has 0 records.
Also I just found one index organized table in our db (first time see this creature) based on iot_type = ‘IOT’. It also has tablespace_name column empty and 0 records in table. Based on the knowledge I got from reading the index organized table should just like regular table except that its data is sorted when saved in the database. So if it is being used it should have non zero records in the table, right?
Thanks a lot for your info.
Shirley

Hi..
21:37:05 ravan >conn anand/xxxxxx
Connected.
21:37:46 ravan >21:38:01 ravan >CREATE TABLE t1 (c1 NUMBER PRIMARY KEY, c2 VARCHAR2(30)) ORGANIZATION INDEX tablespace users;
Table created.
Elapsed: 00:00:00.01
21:38:51 ravan >select OWNER,TABLE_NAME,TABLESPACE_NAME,IOT_NAME,IOT_TYPE from dba_tables where table_name='T1';
OWNER                          TABLE_NAME                     TABLESPACE_NAME                IOT_NAME                       IOT_TYPE
ANAND                          T1                                                                                   IOT
21:49:02 ravan >insert into t1 values (1,'a');
1 row created.
Elapsed: 00:00:00.00
21:49:21 ravan >insert into t1 values (2,'b');
1 row created.
Elapsed: 00:00:00.00
21:49:25 ravan >insert into t1 values (3,'c');
1 row created.
Elapsed: 00:00:00.00
21:49:29 ravan >insert into t1 values (4,'d');
1 row created.
Elapsed: 00:00:00.00
21:49:33 ravan >
21:49:34 ravan >commit;
Commit complete.
Elapsed: 00:00:00.00
21:49:36 ravan >
21:49:36 ravan >
21:49:36 ravan >
21:49:37 ravan >select * from t1;
        C1 C2
         1 a
         2 b
         3 c
         4 d
Elapsed: 00:00:00.00
21:50:40 ravan >conn sys/xxxxxx as sysdba
Connected.
21:51:20 ravan >exec dbms_stats.gather_table_stats(ownname =>'ANAND',tabname =>'T1',cascade =>true);
PL/SQL procedure successfully completed.
21:55:34 ravan >select table_name,owner,tablespace_name,num_rows,last_analyzed,avg_row_len,blocks FROM dba_tables WHERE table_name like UPPER('%&table_name%');
Enter value for table_name: t1
TABLE_NAME                     OWNER                          TABLESPACE_NAME        NUM_ROWS LAST_ANAL AVG_ROW_LEN     BLOCKS
T1                             ANAND                                                        4 05-MAR-09           5
21:56:50 ravan >select table_owner,table_name,owner AS index_owner,index_name,tablespace_name,num_rows,status,index_type FROM dba_indexes WHERE table_owner = UPPER('&owner') AND table_name = UPPER('&table_name') ORDER BY table_owner, table_name, index_owner, index_name;
Enter value for owner: anand
Enter value for table_name: t1
TABLE_OWNER          TABLE_NAME                     INDEX_OWNER          INDEX_NAME                  TABLESPACE_NAME        NUM_ROWS STATUS      INDEX_TYPE
ANAND                T1                             ANAND                SYS_IOT_TOP_28811           USERS                            4 VALID    IOT - TOP
Elapsed: 00:00:00.00HTH
Anand

One db and user for multiple tablespaces or schemas per server?

Hello again.
I installed Oracle 11g on server_1 and created one database db_1.
Using Enterprise Manager, I did the following:
Created a tablespace myname_1.
Created a user myname_1.
Logged in as myname_1 and created a table into the default tablespace myname_1.
When creating this table, the schema field defaulted to myname_1.
Created another tablespace myname_2.
My confusion about the relationship between tablespaces, users, and schemas starts here:
When I try to create a new table for tablespace myname_2, I get an error:
"user myname_2 does not exist"
I am seeking some clarification on these levels of organization in Oracle.
My goal is to setup my server with one database each and one user each per database.
Then, I think I want to create multiple tablespaces and organize objects per tablespace.
Or should it be per schema?
Eventually each tablespace will be moved to a separate server.
Any comments and suggestions are greatly appreciated.
Thank you for helping.

Hello,
This error means user MYNAME_2 doesn't exists and you have to create one.
Example 1:
CREATE USER MYNAME_2
IDENTIFIED BY "my_password"
DEFAULT TABLESPACE MYNAME_1
TEMPORARY TABLESPACE TEMP
PROFILE DEFAULT
ACCOUNT UNLOCK;
-- 4 Roles for KLONDIKE
GRANT RESOURCE TO MYNAME_2; ---> This privs give unlimited quota on all the tablespaces
GRANT CONNECT TO MYNAME_2;
ALTER USER MYNAME_2 DEFAULT ROLE NONE;
Then create your table (you were missing "AS" )
create table myname_2.mytable_1 as
select * from source_table@dblink_2;Example 2: If you want to create table mytable_1 in tablespace myname_2 then you have to create tablespace myname_2 first. To create table in different tablespace than user default tablespace
create table mytable_1 tablespace myname_2 as select * from source_table@dblink;Regards
OrionNet

Tablespaces and block size in Data Warehouse

We are preparing to implement Data Warehouse on Oracle 11g R2 and currently I am trying to set up some storage strategy - unfortunately I have very little experience with that. The question is what are general advices in such considerations according table spaces and block size? I made some research and it is hard to find some clear answer, there are resources advising that block size is not important and can be left small (8 KB), others state that it is crucial and should be the biggest possible (64KB). The other thing is what part of data should be placed where? Many resources state that keeping indexes apart from its data is a myth and a bad practice as it may lead to decrease of performance, others say that although there is no performance benefit, index table spaces do not need to be backed up and thats why it should be split. The next idea is to have separate table spaces for big tables, small tables, tables accessed frequently and infrequently. How should I organize partitions in terms of table spaces? Is it a good idea to have "old" data (read only) partitions on separate table spaces?
Any help highly appreciated and thank you in advance.

Wojtus-J wrote:
We are preparing to implement Data Warehouse on Oracle 11g R2 and currently I am trying to set up some storage strategy - unfortunately I have very little experience with that. With little experience, the key feature is to avoid big mistakes - don't try to get too clever.
The question is what are general advices in such considerations according table spaces and block size? If you need to ask about block sizes, use the default (i.e. 8KB).
I made some research and it is hard to find some clear answer, But if you get contradictory advice from this forum, how would you decide which bits to follow ?
A couple of sensible guidelines when researching on the internet - look for material that is datestamped with recent dates (last couple of years), or references recent - or at least relevant - versions of Oracle. Give preference to material that explains WHY an idea might be relevant, give greater preference to material that DEMONSTRATES why an idea might be relevant. Check that any explanations and demonstrations are relevant to your planned setup.
The other thing is what part of data should be placed where? Many resources state that keeping indexes apart from its data is a myth and a bad practice as it may lead to decrease of performance, others say that although there is no performance benefit, index table spaces do not need to be backed up and thats why it should be split. The next idea is to have separate table spaces for big tables, small tables, tables accessed frequently and infrequently. How should I organize partitions in terms of table spaces? Is it a good idea to have "old" data (read only) partitions on separate table spaces?
It is often convenient, and sometimes very important, to separate data into different tablespaces based on some aspect of functionality. The performance thing was mooted (badly) in an era when discs were small and (disk) partitions were hard; but all your other examples of why to split are potentially valid for administrative. Big/Small, table/index, old/new, read-only/read-write, fact/dimension etc.
For data warehouses a fairly common practice is to identify some sort of aging pattern for the data, and try to pick a boundary that allows you to partition data so that a large fraction of the data can eventually be made read-only: using tablespaces to mark time-boundaries can be a great convenience - note that the tablespace boundary need not match the partition boudary - e.g. daily partitions in a monthly tablespace. If you take this type of approach, you might have a "working" tablespace for recent data, and then copy the older data to "time-specific" tablespace, packing it and making it readonly as you do so.
Tablespaces are (broadly speaking) about strategy, not performance. (Temporary tablespaces / tablespace groups are probably the exception to this thought.)
Regards
Jonathan Lewis

Tablespace Reorganisation in Oracle 10g Database

Dear All,
I'm planning of doing a carrying out a Tablespace Reorganisation of the schema tablespace on the production server. I need your views regarding the process to be taken and tuning that is required before carrying out such an activity. For your information, the size of the tablespace is around 3TB. Also, since it is the production server, we can't have an outage for more than 24hrs. Hence, I would like some help from all of you in order to carry out this activity successfully in the time frame.
Regarding the process :
I have some ideas about how to do the tablespace reorganisation in oracle 10g. But, if I carry out the activity my way, its going it to take atleast 3-4 days to complete (which won't be acceptable).
Areas of concern :
1) Steps to perform the tablespace reorganisation in Oracle 10g DB.
2) Size of the temporary tablespace before starting the Reorg.
3) Any further suggestions / recomendations regarding tuning up of Oracle Parameters for enhancement of speed and acuracy of the activity.
System Specifications :
SAP - BI 7.0 (SAP NetWeaver 2004s)
DB - Oracle 10.2.0.2.0, DBSL Patch Level - 158
OS - AIX 5.3
Looking forward to some good and prompt suggestions from all of you !!
Please provide your valuable inputs.
NOTE :: We have successfully performed the reorganization in the rest of the landscape on the same schema tablespace without any issues.
Thanks and Regards,
Deoraj Alok.

It is quite an old thread, but let me put in my view points, which could help others.
1. The Size of PSAPTEMP and PSAPUNDO tablespace should be 1.5*largest Table Size.
2. Another Important thing is , if the time is in an issue, what you can do is to reorg. only top 50 largest tables where maximum space is being wasted. Folowing is the query to determine the TOP 50 tables which has the highest WASTED size.
SELECT * FROM
(SELECT
SUBSTR(TABLE_NAME, 1, 21) TABLE_NAME,
NUM_ROWS,
AVG_ROW_LEN ROWLEN,
BLOCKS,
+ROUND((AVG_ROW_LEN + 1) * NUM_ROWS / 1000000, 0) NET_MB,+
+ROUND(BLOCKS * (8000 - 23 * INI_TRANS) *+
(1 - PCT_FREE / 100) / 1000000, 0) GROSS_MB,
ROUND((BLOCKS * (8000 - 23 * INI_TRANS) * (1 - PCT_FREE / 100) -
+(AVG_ROW_LEN + 1) * NUM_ROWS) / 1000000) "WASTED_MB",+
Tablespace_Name
FROM DBA_TABLES
WHERE
NUM_ROWS IS NOT NULL AND
OWNER LIKE 'SAP%' AND
PARTITIONED = 'NO' AND
(IOT_TYPE != 'IOT' OR IOT_TYPE IS NULL)
ORDER BY 7 DESC)
WHERE ROWNUM <=50;
I am sure that, only these 50 tables will reduce the maximum space and you can ignore rest of the tables.
3. Even you can find out all the Tables which are having LONG and LONG RAW fields by using this query
Select Distinct TABLE_NAME From dba_tab_cols Where Owner='SAPYSP' and (DATA_TYPE='LONG' OR DATA_TYPE='LONG RAW');
Now, from the results of this query you can see how many Tables are present in the Top 50 Tables. There will be a few only and you can export/import these few tables in offline mode.
4. After reorg, fi you want to claim the free disk space also, it would not be that easy because of the high water mark present in datafiles but you can try with
Alter datafile <datafile id> resize <Size>M
5. If free disk space is the first priority the you need to create another Table space (which should have size as big as it can have all the tables) and you re-organize in this new tablespace. After Reorg, drop the old tablespace and rename the new Table space with the old one (Rename Tablespace Command will work only in Oracle 10g).
I hope this information helps all those who are going to do reorg in their respective projects. However, You can further put your question if in doubt and I will try to answer them.

Oracle Tablespace issue

Hi,
I am having problem with one of our tablespace. I receive a error message saying unable to extent tablespace very often, even though we have enough space in tablespace, And i also observerd that max(bytes) in dba_free_Space is decreasing everyday. We have oracle 11g and tablespaces are locally manged with ASSM.
Space in our tablespace is as follows:
TSName Tot_Size Tot_free PCT_free Max_Free Chunk_Free
User 44,746,932,224 3,656,908,800 8 1,966,080 4,668
I get the above result when i execute the following query:
select a.tablespace_name,sum(a.tots) Tot_Size,
sum(a.sumb) Tot_Free,
sum(a.sumb)*100/sum(a.tots) Pct_Free,
sum(a.largest) Max_Free,sum(a.chunks) Chunks_Free
from
select tablespace_name,0 tots,sum(bytes) sumb,
max(bytes) largest,count(*) chunks
from dba_free_space a
group by tablespace_name
union
select tablespace_name,sum(bytes) tots,0,0,0 from
dba_data_files
group by tablespace_name) a
group by a.tablespace_name;
Why is the Max_free very less and it keep decreasing daily. I tried to shrink tables and rebuild indexes to gain some space , nothing helped. Can anyone help me if i am missing anything here ? And also please let me know if you need more information
Thanks for your time.

I have read the SAP notes suggested by Alpesh and Harleen. I spoke to the Database admin regarding the following tables for re-organization:
Tables: VIRSA_CC_ACTVL
            VIRSA_CC_BKGINP
            VIRSA_CC_JOBHST
            VIRSA_CC_PRMVL
            VIRSA_CC_SCHEDULER
            VIRSA_CC_THREAD
He said that it will save around 4Gb only.
Can you tell me if by setting the following thing in CC>Config>"Additional Options"
Enable Offline Risk Analysis   - No
Will we be able to save up space? Our main concern is not to increase further the size because of cost issues. We already increased the size twice earlier. The system was designed as per the sizing guidelines earlier. Thhanks both.
Thanks for your reply Sudip as well...We will configure automatic addition of tablespace soon after we resolve this issue....
Regards,
Venkateswara Rao

How to find the partition/overflow tablespace for hash partition?

CREATE TABLE sales(acct_no NUMBER(5),
acct_name CHAR(30),
amount_of_sale NUMBER(6),
week_no INTEGER,
sale_details VARCHAR2(1000),
PRIMARY KEY (acct_no, acct_name, week_no))
ORGANIZATION INDEX
INCLUDING week_no
OVERFLOW
PARTITION BY HASH (week_no)
PARTITIONS 16
STORE IN (tsp101, tbs_scott01)
OVERFLOW STORE IN (tsp101, tbs_scott01);
Query the partition tablespace like below, get null instead of 'tsp101' and 'tbs_scott01':
SELECT tp.PARTITION_NAME, tp.TABLESPACE_NAME
FROM ALL_TAB_PARTITIONS tp, ALL_PART_TABLES pt
WHERE tp.TABLE_NAME='SALES'
AND tp.TABLE_OWNER = pt.OWNER(+) AND tp.TABLE_NAME = pt.TABLE_NAME(+)
ORDER BY PARTITION_POSITION

CREATE TABLE sales(acct_no NUMBER(5),
acct_name CHAR(30),
amount_of_sale NUMBER(6),
week_no INTEGER,
sale_details VARCHAR2(1000),
PRIMARY KEY (acct_no, acct_name, week_no))
ORGANIZATION INDEX
INCLUDING week_no
OVERFLOW
PARTITION BY HASH (week_no)
PARTITIONS 16
STORE IN (tsp101, tbs_scott01)
OVERFLOW STORE IN (tsp101, tbs_scott01);
Query the partition tablespace like below, get null instead of 'tsp101' and 'tbs_scott01':
SELECT tp.PARTITION_NAME, tp.TABLESPACE_NAME
FROM ALL_TAB_PARTITIONS tp, ALL_PART_TABLES pt
WHERE tp.TABLE_NAME='SALES'
AND tp.TABLE_OWNER = pt.OWNER(+) AND tp.TABLE_NAME = pt.TABLE_NAME(+)
ORDER BY PARTITION_POSITION

ORA-00959: tablespace 'EXAMPLE' does not exist

hi ! i want to import hr schema to my application server 10g from oracle 10g database.
oracle application server:
[oracle@apps ~]$ sqlplus / as sysdba
SQL> SQL> SELECT * FROM V$VERSION ;
BANNER
Oracle Database 10g Enterprise Edition Release 10.1.0.4.2 - Prod
PL/SQL Release 10.1.0.4.2 - Production
CORE 10.1.0.4.0 Production
TNS for Linux: Version 10.1.0.4.0 - Production
NLSRTL Version 10.1.0.4.2 - Production
oracle database 10g;
[oracle@test ~]$ sqlplus / as sysdba
SQL> SELECT * FROM V$VERSION ;
BANNER
Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Prod
PL/SQL Release 10.2.0.1.0 - Production
CORE 10.2.0.1.0 Production
TNS for Linux: Version 10.2.0.1.0 - Production
NLSRTL Version 10.2.0.1.0 - Production
exporting schema in oracle database 10g.................
[oracle@test dpdump]$ expdp DIRECTORY=DATA_PUMP_DIR DUMPFILE=hrschema.dmp logfile=hrschema.log SCHEMAS=hr version=10.1.0.4.2
Export: Release 10.2.0.1.0 - Production on Friday, 30 April, 2010 9:45:30
Copyright (c) 2003, 2005, Oracle. All rights reserved.
Username: sys as sysdba
Password:
Connected to: Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Production
With the Partitioning, OLAP and Data Mining options
Starting "SYS"."SYS_EXPORT_SCHEMA_01": sys/******** AS SYSDBA DIRECTORY=DATA_PUMP_DIR DUMPFILE=hrschema.dmp logfile=hrschema.log SCHEMAS=hr version=10.1.0.4.2
Estimate in progress using BLOCKS method...
Processing object type SCHEMA_EXPORT/TABLE/TABLE_DATA
Total estimation using BLOCKS method: 448 KB
Processing object type SCHEMA_EXPORT/USER
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/PRE_SCHEMA/PROCACT_SCHEMA
Processing object type SCHEMA_EXPORT/SEQUENCE/SEQUENCE
Processing object type SCHEMA_EXPORT/TABLE/TABLE
Processing object type SCHEMA_EXPORT/TABLE/GRANT/OWNER_GRANT/OBJECT_GRANT
Processing object type SCHEMA_EXPORT/TABLE/INDEX/INDEX
Processing object type SCHEMA_EXPORT/TABLE/CONSTRAINT/CONSTRAINT
Processing object type SCHEMA_EXPORT/TABLE/INDEX/STATISTICS/INDEX_STATISTICS
Processing object type SCHEMA_EXPORT/TABLE/COMMENT
Processing object type SCHEMA_EXPORT/PROCEDURE/PROCEDURE
Processing object type SCHEMA_EXPORT/PROCEDURE/ALTER_PROCEDURE
Processing object type SCHEMA_EXPORT/VIEW/VIEW
Processing object type SCHEMA_EXPORT/TABLE/CONSTRAINT/REF_CONSTRAINT
Processing object type SCHEMA_EXPORT/TABLE/TRIGGER
Processing object type SCHEMA_EXPORT/TABLE/STATISTICS/TABLE_STATISTICS
. . exported "HR"."COUNTRIES" 6.085 KB 25 rows
. . exported "HR"."DEPARTMENTS" 6.632 KB 27 rows
. . exported "HR"."EMPLOYEES" 15.76 KB 107 rows
. . exported "HR"."JOBS" 6.609 KB 19 rows
. . exported "HR"."JOB_HISTORY" 6.585 KB 10 rows
. . exported "HR"."LOCATIONS" 7.710 KB 23 rows
. . exported "HR"."REGIONS" 5.289 KB 4 rows
Master table "SYS"."SYS_EXPORT_SCHEMA_01" successfully loaded/unloaded
Dump file set for SYS.SYS_EXPORT_SCHEMA_01 is:
/d01/app/oracle/product/10.2.0/db/admin/orcl/dpdump/hrschema.dmp
^[[AJob "SYS"."SYS_EXPORT_SCHEMA_01" successfully completed at 09:45:50
*transfering the schema dump file to appliaction server..............................*
[oracle@test dpdump]$ scp hrschema.dmp apps:/d01/backupdp/hrschema.dmp
oracle@apps's password:
hrschema.dmp 100% 596KB 596.0KB/s 00:00
[oracle@test dpdump]$
Now importing datapump schema from that dump file............................
[oracle@apps backupdp]$ ls
example01.dbf hrschema.dmp
[oracle@apps backupdp]$ impdp DIRECTORY=backupdp DUMPFILE=hrschema.dmp logfile=hrschema.log SCHEMAS=hr
Import: Release 10.1.0.4.2 - Production on Friday, 30 April, 2010 9:54
Copyright (c) 2003, Oracle. All rights reserved.
Username: sys as sysdba
Password:
Connected to: Oracle Database 10g Enterprise Edition Release 10.1.0.4.2 - Production
With the Partitioning, OLAP and Data Mining options
Master table "SYS"."SYS_IMPORT_SCHEMA_01" successfully loaded/unloaded
Starting "SYS"."SYS_IMPORT_SCHEMA_01": sys/******** AS SYSDBA DIRECTORY=backupdp DUMPFILE=hrschema.dmp logfile=hrschema.log SCHEMAS=hr
Processing object type SCHEMA_EXPORT/USER
ORA-31684: Object type USER:"HR" 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/PRE_SCHEMA/PROCACT_SCHEMA
Processing object type SCHEMA_EXPORT/SEQUENCE/SEQUENCE
Processing object type SCHEMA_EXPORT/TABLE/TABLE
ORA-39083: Object type TABLE failed to create with error:
ORA-00959: tablespace 'EXAMPLE' does not exist
Failing sql is:
CREATE TABLE "HR"."COUNTRIES" ("COUNTRY_ID" CHAR(2) CONSTRAINT "COUNTRY_ID_NN" NOT NULL ENABLE, "COUNTRY_NAME" VARCHAR2(40), "REGION_ID" NUMBER, CONSTRAINT "COUNTRY_C_ID_PK" PRIMARY KEY ("COUNTRY_ID") ENABLE) ORGANIZATION INDEX NOCOMPRESS PCTFREE 10 INITRANS 2 MAXTRANS 255 NOLOGGING STORAGE(INITIAL 65536 NEXT 1048576 MINEXTENTS 1 MAXEXTENTS 2147483645 PCTINCREASE 0 FREELISTS 1 FREELIST
ORA-39083: Object type TABLE failed to create with error:
ORA-00959: tablespace 'EXAMPLE' does not exist
Failing sql is:
CREATE TABLE "HR"."REGIONS" ("REGION_ID" NUMBER CONSTRAINT "REGION_ID_NN" NOT NULL ENABLE, "REGION_NAME" VARCHAR2(25)) PCTFREE 10 PCTUSED 40 INITRANS 1 MAXTRANS 255 NOCOMPRESS NOLOGGING STORAGE(INITIAL 65536 NEXT 1048576 MINEXTENTS 1 MAXEXTENTS 2147483645 PCTINCREASE 0 FREELISTS 1 FREELIST GROUPS 1 BUFFER_POOL DEFAULT) TABLESPACE "EXAMPLE"
ORA-39083: Object type TABLE failed to create with error:
ORA-00959: tablespace 'EXAMPLE' does not exist
Failing sql is:
CREATE TABLE "HR"."LOCATIONS" ("LOCATION_ID" NUMBER(4,0), "STREET_ADDRESS" VARCHAR2(40), "POSTAL_CODE" VARCHAR2(12), "CITY" VARCHAR2(30) CONSTRAINT "LOC_CITY_NN" NOT NULL ENABLE, "STATE_PROVINCE" VARCHAR2(25), "COUNTRY_ID" CHAR(2)) PCTFREE 10 PCTUSED 40 INITRANS 1 MAXTRANS 255 NOCOMPRESS NOLOGGING STORAGE(INITIAL 65536 NEXT 1048576 MINEXTENTS 1 MAXEXTENTS 2147483645 PCTINCREASE 0 FREELI
ORA-39083: Object type TABLE failed to create with error:
ORA-00959: tablespace 'EXAMPLE' does not exist
Failing sql is:
CREATE TABLE "HR"."DEPARTMENTS" ("DEPARTMENT_ID" NUMBER(4,0), "DEPARTMENT_NAME" VARCHAR2(30) CONSTRAINT "DEPT_NAME_NN" NOT NULL ENABLE, "MANAGER_ID" NUMBER(6,0), "LOCATION_ID" NUMBER(4,0)) PCTFREE 10 PCTUSED 40 INITRANS 1 MAXTRANS 255 NOCOMPRESS NOLOGGING STORAGE(INITIAL 65536 NEXT 1048576 MINEXTENTS 1 MAXEXTENTS 2147483645 PCTINCREASE 0 FREELISTS 1 FREELIST GROUPS 1 BUFFER_POOL DEFAULT
ORA-39083: Object type TABLE failed to create with error:
ORA-00959: tablespace 'EXAMPLE' does not exist
Failing sql is:
CREATE TABLE "HR"."JOBS" ("JOB_ID" VARCHAR2(10), "JOB_TITLE" VARCHAR2(35) CONSTRAINT "JOB_TITLE_NN" NOT NULL ENABLE, "MIN_SALARY" NUMBER(6,0), "MAX_SALARY" NUMBER(6,0)) PCTFREE 10 PCTUSED 40 INITRANS 1 MAXTRANS 255 NOCOMPRESS NOLOGGING STORAGE(INITIAL 65536 NEXT 1048576 MINEXTENTS 1 MAXEXTENTS 2147483645 PCTINCREASE 0 FREELISTS 1 FREELIST GROUPS 1 BUFFER_POOL DEFAULT) TABLESPACE "EXAMPL
ORA-39083: Object type TABLE failed to create with error:
ORA-00959: tablespace 'EXAMPLE' does not exist
Failing sql is:
CREATE TABLE "HR"."EMPLOYEES" ("EMPLOYEE_ID" NUMBER(6,0), "FIRST_NAME" VARCHAR2(20), "LAST_NAME" VARCHAR2(25) CONSTRAINT "EMP_LAST_NAME_NN" NOT NULL ENABLE, "EMAIL" VARCHAR2(25) CONSTRAINT "EMP_EMAIL_NN" NOT NULL ENABLE, "PHONE_NUMBER" VARCHAR2(20), "HIRE_DATE" DATE CONSTRAINT "EMP_HIRE_DATE_NN" NOT NULL ENABLE, "JOB_ID" VARCHAR2(10) CONSTRAINT "EMP_JOB_NN" NOT NULL ENABLE, "SALARY" NUM
ORA-39083: Object type TABLE failed to create with error:
ORA-00959: tablespace 'EXAMPLE' does not exist
Failing sql is:
CREATE TABLE "HR"."JOB_HISTORY" ("EMPLOYEE_ID" NUMBER(6,0) CONSTRAINT "JHIST_EMPLOYEE_NN" NOT NULL ENABLE, "START_DATE" DATE CONSTRAINT "JHIST_START_DATE_NN" NOT NULL ENABLE, "END_DATE" DATE CONSTRAINT "JHIST_END_DATE_NN" NOT NULL ENABLE, "JOB_ID" VARCHAR2(10) CONSTRAINT "JHIST_JOB_NN" NOT NULL ENABLE, "DEPARTMENT_ID" NUMBER(4,0)) PCTFREE 10 PCTUSED 40 INITRANS 1 MAXTRANS 255 NOCOMPRESS
Processing object type SCHEMA_EXPORT/TABLE/TABLE_DATA
Processing object type SCHEMA_EXPORT/TABLE/GRANT/OWNER_GRANT/OBJECT_GRANT
ORA-39112: Dependent object type OBJECT_GRANT:"HR" skipped, base object type TABLE:"HR"."COUNTRIES" creation failed
ORA-39112: Dependent object type OBJECT_GRANT:"HR" skipped, base object type TABLE:"HR"."COUNTRIES" creation failed
ORA-39112: Dependent object type OBJECT_GRANT:"HR" skipped, base object type TABLE:"HR"."LOCATIONS" creation failed
ORA-39112: Dependent object type OBJECT_GRANT:"HR" skipped, base object type TABLE:"HR"."LOCATIONS" creation failed
ORA-39112: Dependent object type OBJECT_GRANT:"HR" skipped, base object type TABLE:"HR"."DEPARTMENTS" creation failed
ORA-39112: Dependent object type OBJECT_GRANT:"HR" skipped, base object type TABLE:"HR"."JOBS" creation failed
ORA-39112: Dependent object type OBJECT_GRANT:"HR" skipped, base object type TABLE:"HR"."EMPLOYEES" creation failed
ORA-39112: Dependent object type OBJECT_GRANT:"HR" skipped, base object type TABLE:"HR"."EMPLOYEES" creation failed
ORA-39112: Dependent object type OBJECT_GRANT:"HR" skipped, base object type TABLE:"HR"."JOB_HISTORY" creation failed
Processing object type SCHEMA_EXPORT/TABLE/INDEX/INDEX
ORA-39112: Dependent object type INDEX:"HR"."REG_ID_PK" skipped, base object type TABLE:"HR"."REGIONS" creation failed
ORA-39112: Dependent object type INDEX:"HR"."LOC_ID_PK" skipped, base object type TABLE:"HR"."LOCATIONS" creation failed
ORA-39112: Dependent object type INDEX:"HR"."LOC_CITY_IX" skipped, base object type TABLE:"HR"."LOCATIONS" creation failed
ORA-39112: Dependent object type INDEX:"HR"."LOC_STATE_PROVINCE_IX" skipped, base object type TABLE:"HR"."LOCATIONS" creation failed
ORA-39112: Dependent object type INDEX:"HR"."LOC_COUNTRY_IX" skipped, base object type TABLE:"HR"."LOCATIONS" creation failed
ORA-39112: Dependent object type INDEX:"HR"."DEPT_ID_PK" skipped, base object type TABLE:"HR"."DEPARTMENTS" creation failed
ORA-39112: Dependent object type INDEX:"HR"."DEPT_LOCATION_IX" skipped, base object type TABLE:"HR"."DEPARTMENTS" creation failed
ORA-39112: Dependent object type INDEX:"HR"."JOB_ID_PK" skipped, base object type TABLE:"HR"."JOBS" creation failed
ORA-39112: Dependent object type INDEX:"HR"."EMP_EMAIL_UK" skipped, base object type TABLE:"HR"."EMPLOYEES" creation failed
ORA-39112: Dependent object type INDEX:"HR"."EMP_EMP_ID_PK" skipped, base object type TABLE:"HR"."EMPLOYEES" creation failed
ORA-39112: Dependent object type INDEX:"HR"."EMP_DEPARTMENT_IX" skipped, base object type TABLE:"HR"."EMPLOYEES" creation failed
ORA-39112: Dependent object type INDEX:"HR"."EMP_JOB_IX" skipped, base object type TABLE:"HR"."EMPLOYEES" creation failed
ORA-39112: Dependent object type INDEX:"HR"."EMP_MANAGER_IX" skipped, base object type TABLE:"HR"."EMPLOYEES" creation failed
ORA-39112: Dependent object type INDEX:"HR"."EMP_NAME_IX" skipped, base object type TABLE:"HR"."EMPLOYEES" creation failed
ORA-39112: Dependent object type INDEX:"HR"."JHIST_EMP_ID_ST_DATE_PK" skipped, base object type TABLE:"HR"."JOB_HISTORY" creation failed
ORA-39112: Dependent object type INDEX:"HR"."JHIST_JOB_IX" skipped, base object type TABLE:"HR"."JOB_HISTORY" creation failed
ORA-39112: Dependent object type INDEX:"HR"."JHIST_EMPLOYEE_IX" skipped, base object type TABLE:"HR"."JOB_HISTORY" creation failed
ORA-39112: Dependent object type INDEX:"HR"."JHIST_DEPARTMENT_IX" skipped, base object type TABLE:"HR"."JOB_HISTORY" creation failed
Processing object type SCHEMA_EXPORT/TABLE/CONSTRAINT/CONSTRAINT
ORA-39112: Dependent object type CONSTRAINT:"HR"."REG_ID_PK" skipped, base object type TABLE:"HR"."REGIONS" creation failed
ORA-39112: Dependent object type CONSTRAINT:"HR"."LOC_ID_PK" skipped, base object type TABLE:"HR"."LOCATIONS" creation failed
ORA-39112: Dependent object type CONSTRAINT:"HR"."DEPT_ID_PK" skipped, base object type TABLE:"HR"."DEPARTMENTS" creation failed
ORA-39112: Dependent object type CONSTRAINT:"HR"."JOB_ID_PK" skipped, base object type TABLE:"HR"."JOBS" creation failed
ORA-39112: Dependent object type CONSTRAINT:"HR"."EMP_SALARY_MIN" skipped, base object type TABLE:"HR"."EMPLOYEES" creation failed
ORA-39112: Dependent object type CONSTRAINT:"HR"."EMP_EMAIL_UK" skipped, base object type TABLE:"HR"."EMPLOYEES" creation failed
ORA-39112: Dependent object type CONSTRAINT:"HR"."EMP_EMP_ID_PK" skipped, base object type TABLE:"HR"."EMPLOYEES" creation failed
ORA-39112: Dependent object type CONSTRAINT:"HR"."JHIST_DATE_INTERVAL" skipped, base object type TABLE:"HR"."JOB_HISTORY" creation failed
ORA-39112: Dependent object type CONSTRAINT:"HR"."JHIST_EMP_ID_ST_DATE_PK" skipped, base object type TABLE:"HR"."JOB_HISTORY" creation failed
Processing object type SCHEMA_EXPORT/TABLE/INDEX/STATISTICS/INDEX_STATISTICS
ORA-39112: Dependent object type INDEX_STATISTICS skipped, base object type INDEX:"HR"."REG_ID_PK" creation failed
ORA-39112: Dependent object type INDEX_STATISTICS skipped, base object type TABLE:"HR"."COUNTRIES" creation failed
ORA-39112: Dependent object type INDEX_STATISTICS skipped, base object type INDEX:"HR"."LOC_ID_PK" creation failed
ORA-39112: Dependent object type INDEX_STATISTICS skipped, base object type INDEX:"HR"."LOC_CITY_IX" creation failed
ORA-39112: Dependent object type INDEX_STATISTICS skipped, base object type INDEX:"HR"."LOC_STATE_PROVINCE_IX" creation failed
ORA-39112: Dependent object type INDEX_STATISTICS skipped, base object type INDEX:"HR"."LOC_COUNTRY_IX" creation failed
ORA-39112: Dependent object type INDEX_STATISTICS skipped, base object type INDEX:"HR"."DEPT_ID_PK" creation failed
ORA-39112: Dependent object type INDEX_STATISTICS skipped, base object type INDEX:"HR"."DEPT_LOCATION_IX" creation failed
ORA-39112: Dependent object type INDEX_STATISTICS skipped, base object type INDEX:"HR"."JOB_ID_PK" creation failed
ORA-39112: Dependent object type INDEX_STATISTICS skipped, base object type INDEX:"HR"."EMP_EMAIL_UK" creation failed
ORA-39112: Dependent object type INDEX_STATISTICS skipped, base object type INDEX:"HR"."EMP_EMP_ID_PK" creation failed
ORA-39112: Dependent object type INDEX_STATISTICS skipped, base object type INDEX:"HR"."EMP_DEPARTMENT_IX" creation failed
ORA-39112: Dependent object type INDEX_STATISTICS skipped, base object type INDEX:"HR"."EMP_JOB_IX" creation failed
ORA-39112: Dependent object type INDEX_STATISTICS skipped, base object type INDEX:"HR"."EMP_MANAGER_IX" creation failed
ORA-39112: Dependent object type INDEX_STATISTICS skipped, base object type INDEX:"HR"."EMP_NAME_IX" creation failed
ORA-39112: Dependent object type INDEX_STATISTICS skipped, base object type INDEX:"HR"."JHIST_EMP_ID_ST_DATE_PK" creation failed
ORA-39112: Dependent object type INDEX_STATISTICS skipped, base object type INDEX:"HR"."JHIST_JOB_IX" creation failed
ORA-39112: Dependent object type INDEX_STATISTICS skipped, base object type INDEX:"HR"."JHIST_EMPLOYEE_IX" creation failed
ORA-39112: Dependent object type INDEX_STATISTICS skipped, base object type INDEX:"HR"."JHIST_DEPARTMENT_IX" creation failed
Processing object type SCHEMA_EXPORT/TABLE/COMMENT
ORA-39112: Dependent object type COMMENT skipped, base object type TABLE:"HR"."COUNTRIES" creation failed
ORA-39112: Dependent object type COMMENT skipped, base object type TABLE:"HR"."COUNTRIES" creation failed
ORA-39112: Dependent object type COMMENT skipped, base object type TABLE:"HR"."COUNTRIES" creation failed
ORA-39112: Dependent object type COMMENT skipped, base object type TABLE:"HR"."COUNTRIES" creation failed
ORA-39112: Dependent object type COMMENT skipped, base object type TABLE:"HR"."LOCATIONS" creation failed
ORA-39112: Dependent object type COMMENT skipped, base object type TABLE:"HR"."LOCATIONS" creation failed
ORA-39112: Dependent object type COMMENT skipped, base object type TABLE:"HR"."LOCATIONS" creation failed
ORA-39112: Dependent object type COMMENT skipped, base object type TABLE:"HR"."LOCATIONS" creation failed
ORA-39112: Dependent object type COMMENT skipped, base object type TABLE:"HR"."LOCATIONS" creation failed
ORA-39112: Dependent object type COMMENT skipped, base object type TABLE:"HR"."LOCATIONS" creation failed
ORA-39112: Dependent object type COMMENT skipped, base object type TABLE:"HR"."LOCATIONS" creation failed
ORA-39112: Dependent object type COMMENT skipped, base object type TABLE:"HR"."DEPARTMENTS" creation failed
ORA-39112: Dependent object type COMMENT skipped, base object type TABLE:"HR"."DEPARTMENTS" creation failed
ORA-39112: Dependent object type COMMENT skipped, base object type TABLE:"HR"."DEPARTMENTS" creation failed
ORA-39112: Dependent object type COMMENT skipped, base object type TABLE:"HR"."DEPARTMENTS" creation failed
ORA-39112: Dependent object type COMMENT skipped, base object type TABLE:"HR"."DEPARTMENTS" creation failed
ORA-39112: Dependent object type COMMENT skipped, base object type TABLE:"HR"."JOBS" creation failed
ORA-39112: Dependent object type COMMENT skipped, base object type TABLE:"HR"."JOBS" creation failed
ORA-39112: Dependent object type COMMENT skipped, base object type TABLE:"HR"."JOBS" creation failed
ORA-39112: Dependent object type COMMENT skipped, base object type TABLE:"HR"."JOBS" creation failed
ORA-39112: Dependent object type COMMENT skipped, base object type TABLE:"HR"."JOBS" creation failed
ORA-39112: Dependent object type COMMENT skipped, base object type TABLE:"HR"."EMPLOYEES" creation failed
ORA-39112: Dependent object type COMMENT skipped, base object type TABLE:"HR"."EMPLOYEES" creation failed
ORA-39112: Dependent object type COMMENT skipped, base object type TABLE:"HR"."EMPLOYEES" creation failed
ORA-39112: Dependent object type COMMENT skipped, base object type TABLE:"HR"."EMPLOYEES" creation failed
ORA-39112: Dependent object type COMMENT skipped, base object type TABLE:"HR"."EMPLOYEES" creation failed
ORA-39112: Dependent object type COMMENT skipped, base object type TABLE:"HR"."EMPLOYEES" creation failed
ORA-39112: Dependent object type COMMENT skipped, base object type TABLE:"HR"."EMPLOYEES" creation failed
ORA-39112: Dependent object type COMMENT skipped, base object type TABLE:"HR"."EMPLOYEES" creation failed
ORA-39112: Dependent object type COMMENT skipped, base object type TABLE:"HR"."EMPLOYEES" creation failed
ORA-39112: Dependent object type COMMENT skipped, base object type TABLE:"HR"."EMPLOYEES" creation failed
ORA-39112: Dependent object type COMMENT skipped, base object type TABLE:"HR"."EMPLOYEES" creation failed
ORA-39112: Dependent object type COMMENT skipped, base object type TABLE:"HR"."EMPLOYEES" creation failed
ORA-39112: Dependent object type COMMENT skipped, base object type TABLE:"HR"."JOB_HISTORY" creation failed
ORA-39112: Dependent object type COMMENT skipped, base object type TABLE:"HR"."JOB_HISTORY" creation failed
ORA-39112: Dependent object type COMMENT skipped, base object type TABLE:"HR"."JOB_HISTORY" creation failed
ORA-39112: Dependent object type COMMENT skipped, base object type TABLE:"HR"."JOB_HISTORY" creation failed
ORA-39112: Dependent object type COMMENT skipped, base object type TABLE:"HR"."JOB_HISTORY" creation failed
ORA-39112: Dependent object type COMMENT skipped, base object type TABLE:"HR"."JOB_HISTORY" creation failed
Processing object type SCHEMA_EXPORT/PROCEDURE/PROCEDURE
Processing object type SCHEMA_EXPORT/PROCEDURE/ALTER_PROCEDURE
ORA-39082: Object type ALTER_PROCEDURE:"HR"."ADD_JOB_HISTORY" created with compilation warnings
Processing object type SCHEMA_EXPORT/VIEW/VIEW
ORA-39082: Object type VIEW:"HR"."EMP_DETAILS_VIEW" created with compilation warnings
Processing object type SCHEMA_EXPORT/TABLE/CONSTRAINT/REF_CONSTRAINT
ORA-39112: Dependent object type REF_CONSTRAINT:"HR"."COUNTR_REG_FK" skipped, base object type TABLE:"HR"."COUNTRIES" creation failed
ORA-39112: Dependent object type REF_CONSTRAINT:"HR"."LOC_C_ID_FK" skipped, base object type TABLE:"HR"."LOCATIONS" creation failed
ORA-39112: Dependent object type REF_CONSTRAINT:"HR"."DEPT_MGR_FK" skipped, base object type TABLE:"HR"."DEPARTMENTS" creation failed
ORA-39112: Dependent object type REF_CONSTRAINT:"HR"."DEPT_LOC_FK" skipped, base object type TABLE:"HR"."DEPARTMENTS" creation failed
ORA-39112: Dependent object type REF_CONSTRAINT:"HR"."EMP_MANAGER_FK" skipped, base object type TABLE:"HR"."EMPLOYEES" creation failed
ORA-39112: Dependent object type REF_CONSTRAINT:"HR"."EMP_JOB_FK" skipped, base object type TABLE:"HR"."EMPLOYEES" creation failed
ORA-39112: Dependent object type REF_CONSTRAINT:"HR"."EMP_DEPT_FK" skipped, base object type TABLE:"HR"."EMPLOYEES" creation failed
ORA-39112: Dependent object type REF_CONSTRAINT:"HR"."JHIST_DEPT_FK" skipped, base object type TABLE:"HR"."JOB_HISTORY" creation failed
ORA-39112: Dependent object type REF_CONSTRAINT:"HR"."JHIST_EMP_FK" skipped, base object type TABLE:"HR"."JOB_HISTORY" creation failed
ORA-39112: Dependent object type REF_CONSTRAINT:"HR"."JHIST_JOB_FK" skipped, base object type TABLE:"HR"."JOB_HISTORY" creation failed
Processing object type SCHEMA_EXPORT/TABLE/TRIGGER
ORA-39112: Dependent object type TRIGGER:"HR"."SECURE_EMPLOYEES" skipped, base object type TABLE:"HR"."EMPLOYEES" creation failed
ORA-39112: Dependent object type TRIGGER:"HR"."UPDATE_JOB_HISTORY" skipped, base object type TABLE:"HR"."EMPLOYEES" creation failed
Processing object type SCHEMA_EXPORT/TABLE/STATISTICS/TABLE_STATISTICS
ORA-39112: Dependent object type TABLE_STATISTICS skipped, base object type TABLE:"HR"."REGIONS" creation failed
ORA-39112: Dependent object type TABLE_STATISTICS skipped, base object type TABLE:"HR"."COUNTRIES" creation failed
ORA-39112: Dependent object type TABLE_STATISTICS skipped, base object type TABLE:"HR"."LOCATIONS" creation failed
ORA-39112: Dependent object type TABLE_STATISTICS skipped, base object type TABLE:"HR"."DEPARTMENTS" creation failed
ORA-39112: Dependent object type TABLE_STATISTICS skipped, base object type TABLE:"HR"."JOBS" creation failed
ORA-39112: Dependent object type TABLE_STATISTICS skipped, base object type TABLE:"HR"."EMPLOYEES" creation failed
ORA-39112: Dependent object type TABLE_STATISTICS skipped, base object type TABLE:"HR"."JOB_HISTORY" creation failed
Job "SYS"."SYS_IMPORT_SCHEMA_01" completed with 123 error(s) at 09:55
[oracle@apps backupdp]$ ls
example01.dbf hrschema.dmp hrschema.log
*[oracle@apps backupdp]$ more hrschema.log*
Import: Release 10.1.0.4.2 - Production on Friday, 30 April, 2010 9:54
Copyright (c) 2003, Oracle. All rights reserved.
Connected to: Oracle Database 10g Enterprise Edition Release 10.1.0.4.2 - Producti
on
With the Partitioning, OLAP and Data Mining options
Master table "SYS"."SYS_IMPORT_SCHEMA_01" successfully loaded/unloaded
Starting "SYS"."SYS_IMPORT_SCHEMA_01": sys/******** AS SYSDBA DIRECTORY=backupdp
DUMPFILE=hrschema.dmp logfile=hrschema.log SCHEMAS=hr
Processing object type SCHEMA_EXPORT/USER
ORA-31684: Object type USER:"HR" 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/PRE_SCHEMA/PROCACT_SCHEMA
Processing object type SCHEMA_EXPORT/SEQUENCE/SEQUENCE
Processing object type SCHEMA_EXPORT/TABLE/TABLE
ORA-39083: Object type TABLE failed to create with error:
*ORA-00959: tablespace 'EXAMPLE' does not exist*
Failing sql is:
CREATE TABLE "HR"."COUNTRIES" ("COUNTRY_ID" CHAR(2) CONSTRAINT "COUNTRY_ID_NN" NOT
NULL ENABLE, "COUNTRY_NAME" VARCHAR2(40), "REGION_ID" NUMBER, CONSTRAINT "COUNTR
Y_C_ID_PK" PRIMARY KEY ("COUNTRY_ID") ENABLE) ORGANIZATION INDEX NOCOMPRESS PCTFRE
E 10 INITRANS 2 MAXTRANS 255 NOLOGGING STORAGE(INITIAL 65536 NEXT 1048576 MINEXTEN
TS 1 MAXEXTENTS 2147483645 PCTINCREASE 0 FREELISTS 1 FREELIST
ORA-39083: Object type TABLE failed to create with error:
ORA-00959: tablespace 'EXAMPLE' does not exist
Failing sql is:
CREATE TABLE "HR"."REGIONS" ("REGION_ID" NUMBER CONSTRAINT "REGION_ID_NN" NOT NULL
[oracle@apps backupdp]$
[oracle@apps backupdp]$
now it is giving error that EXAMPLE tablespace doesnot exist .....so now should i use transporatble tablespace for to trasport example tablepsace from oracle 10g to application server 10g.
please help.......

Then i use Transportable tablespaces for transporting example tablespace to application server from oracle 10g.....................
exported in oracle 10g;
[oracle@test orcl]$ sqlplus / as sysdba
SQL*Plus: Release 10.2.0.1.0 - Production on Fri Apr 30 10:08:06 2010
Copyright (c) 1982, 2005, Oracle. All rights reserved.
Connected to:
Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Production
With the Partitioning, OLAP and Data Mining options
SQL>
SQL> alter tablespace example read only;
alter tablespace example read only
ERROR at line 1:
ORA-01644: tablespace 'EXAMPLE' is already read only
[oracle@test dpdump]$ expdp DIRECTORY=DATA_PUMP_DIR DUMPFILE=exampletbs.dmp transport_tablespaces=example logfile=exampletbs.log version=10.1.0.4.2;
Export: Release 10.2.0.1.0 - Production on Friday, 30 April, 2010 10:03:29
Copyright (c) 2003, 2005, Oracle. All rights reserved.
Username: sys as sysdba
Password:
Connected to: Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Production
With the Partitioning, OLAP and Data Mining options
Starting "SYS"."SYS_EXPORT_TRANSPORTABLE_01": sys/******** AS SYSDBA DIRECTORY=DATA_PUMP_DIR DUMPFILE=exampletbs.dmp transport_tablespaces=example logfile=exampletbs.log version=10.1.0.4.2
Processing object type TRANSPORTABLE_EXPORT/PLUGTS_BLK
Processing object type TRANSPORTABLE_EXPORT/TYPE/TYPE_SPEC
Processing object type TRANSPORTABLE_EXPORT/TABLE
Processing object type TRANSPORTABLE_EXPORT/GRANT/OWNER_GRANT/OBJECT_GRANT
Processing object type TRANSPORTABLE_EXPORT/INDEX
Processing object type TRANSPORTABLE_EXPORT/CONSTRAINT/CONSTRAINT
Processing object type TRANSPORTABLE_EXPORT/INDEX_STATISTICS
Processing object type TRANSPORTABLE_EXPORT/COMMENT
Processing object type TRANSPORTABLE_EXPORT/CONSTRAINT/REF_CONSTRAINT
Processing object type TRANSPORTABLE_EXPORT/TRIGGER
Processing object type TRANSPORTABLE_EXPORT/INDEX/FUNCTIONAL_AND_BITMAP/INDEX
Processing object type TRANSPORTABLE_EXPORT/INDEX/STATISTICS/FUNCTIONAL_AND_BITMAP/INDEX_STATISTICS
Processing object type TRANSPORTABLE_EXPORT/TABLE_STATISTICS
Processing object type TRANSPORTABLE_EXPORT/DOMAIN_INDEX/INDEX
Processing object type TRANSPORTABLE_EXPORT/MATERIALIZED_VIEW
Processing object type TRANSPORTABLE_EXPORT/POST_INSTANCE/PROCACT_INSTANCE
Processing object type TRANSPORTABLE_EXPORT/POST_INSTANCE/PROCDEPOBJ
Processing object type TRANSPORTABLE_EXPORT/POST_INSTANCE/PLUGTS_BLK
Master table "SYS"."SYS_EXPORT_TRANSPORTABLE_01" successfully loaded/unloaded
Dump file set for SYS.SYS_EXPORT_TRANSPORTABLE_01 is:
/d01/app/oracle/product/10.2.0/db/admin/orcl/dpdump/exampletbs.dmp
Job "SYS"."SYS_EXPORT_TRANSPORTABLE_01" successfully completed at 10:04:01
transfer the example datafile to application server.............
[oracle@test dpdump]$ scp exampletbs.dmp apps:/d01/backupdp/exampletbs.dmp
oracle@apps's password:
exampletbs.dmp 100% 3528KB 3.5MB/s 00:00
[oracle@test dpdump]$
[oracle@test dpdump]$
Import in oracle application server................
[oracle@apps backupdp]$ ls
exampletbs.dmp hrschema.dmp hrschema.log
[oracle@apps backupdp]$ impdp DIRECTORY=backupdp DUMPFILE=exampletbs.dmp transport_datafiles='/d01/backupdp/example01.dbf' logfile=exampletbs.log;
Import: Release 10.1.0.4.2 - Production on Friday, 30 April, 2010 10:20
Copyright (c) 2003, Oracle. All rights reserved.
Username: sys as sysdba
Password:
Connected to: Oracle Database 10g Enterprise Edition Release 10.1.0.4.2 - Production
With the Partitioning, OLAP and Data Mining options
Master table "SYS"."SYS_IMPORT_TRANSPORTABLE_03" successfully loaded/unloaded
Starting "SYS"."SYS_IMPORT_TRANSPORTABLE_03": sys/******** AS SYSDBA DIRECTORY=backupdp DUMPFILE=exampletbs.dmp transport_datafiles=/d01/backupdp/example01.dbf logfile=exampletbs.log
Processing object type TRANSPORTABLE_EXPORT/PLUGTS_BLK
ORA-39123: Data Pump transportable tablespace job aborted
ORA-00721: changes by release 10.2.0.1.0 cannot be used by release 10.1.0.2.0
Job "SYS"."SYS_IMPORT_TRANSPORTABLE_03" stopped due to fatal error at 10:21
[oracle@apps backupdp]$
[oracle@apps backupdp]$ more exampletbs.log
Import: Release 10.1.0.4.2 - Production on Friday, 30 April, 2010 10:20
Copyright (c) 2003, Oracle. All rights reserved.
Connected to: Oracle Database 10g Enterprise Edition Release 10.1.0.4.2 - Producti
on
With the Partitioning, OLAP and Data Mining options
Master table "SYS"."SYS_IMPORT_TRANSPORTABLE_03" successfully loaded/unloaded
Starting "SYS"."SYS_IMPORT_TRANSPORTABLE_03": sys/******** AS SYSDBA DIRECTORY=ba
ckupdp DUMPFILE=exampletbs.dmp transport_datafiles=/d01/backupdp/example01.dbf log
file=exampletbs.log
Processing object type TRANSPORTABLE_EXPORT/PLUGTS_BLK
ORA-39123: Data Pump transportable tablespace job aborted
ORA-00721: changes by release 10.2.0.1.0 cannot be used by release 10.1.0.2.0
Job "SYS"."SYS_IMPORT_TRANSPORTABLE_03" stopped due to fatal error at 10:21
[oracle@apps backupdp]$
please can anybody help........................

Temporary tablespace/OS-Oracle DB/Redo change vector

At minimum, this tablespace should be as large as the
largest index that will be created, plus 10% for
overhead. Can anyone please throw more light on this . Why is this .Is this a hard and fast rule and left to the discretion of the DBA?
This is just a general question.How big of an impact can an operating system have on an oracle database . I mean with respect to everything . Performance/security etc. Unix vs Windows . I do know that on a Unix based system it will be more better to have oracle installed. But isn't there anything that can be done to have the same efffect in every aspect oracle for an database on a windows machine ?
Responses are appreciated!
A redo record consists of
1.redo record header
2.one or more change vectors
What is this change vector.This vwent over my head.Can anyone please elaborate on this.
null
null

Within the limits of the Windows operating system, sure.
Realistically, most organizations use Unix for their large databases because
- when they made the decision about what operating system to use a decade (or more) ago, Windows was nowhere near enterprise ready
- given the human capital they have invested in Unix, there would be no point to moving to Windows
- there are many fewer high-quality Windows admins and Oracle DBAs with substantial Windows skills than Unix admins and Oracle DBAs with Unix experience
There is plenty that can be done to run a large Oracle database on a Windows machine successfully. Unfortunately, doing all these things tends to be harder on Windows, finding people knowledgable enough to do them properly tends to be hard, and relatively few organizations are invested enough in Windows to bother. That's changing over time, though-- there are a lot more Oracle databases on Windows today than there were 5 years ago.
Justin

A confused newbie: SQLServer database vs. ORACLE Tablespace

Guys, excuse me for asking some surely stupid questions, but I'm really confused.
In SQLServer, I can simply create a new database and it has it's own physical files. This means that - for example - it is really trivial to have multiple releases of the same database setup concurrently.
In Oracle, I'm simply blown away at the complexity of this seemingly simple requirement. Here are some of the problems I have doing this with Orcale:
- I can create a second tablespace but then my sequences clash with sequences already in place for tables in the other table space
- I can't simply drop a tablespace and the sequences drop too
- I don't know how to connect to a new database (somehow I seem to have to create a listener too)
OK, I doubt that Oracle is so useless, I'm far more convinced that the "useless" attribute is better suited to my Oracle skills. That is why I can't wait to get some pointers to how I can achieve what I want to achieve useing Oracle.
Pete
Message was edited by:
petehug

A tablespace is just a logical collection of objects that happen to reside in the data file, so there is technically no reason that you would need separate tablespaces here. Probably a good idea for organizational purposes, but not strictly necessary.
If we're going to set up version 5.12 of the database...
1) Create the tablespace (optional). Note that the exact syntax will depend on how you've configured your database (i.e. whether you're using Oracle Managed Files, ASM, etc).
CREATE TABLESPACE ts_lima_512_md
DATAFILE 'ts_lima_512_md.dbf' SIZE 100M;2) Create the user/ schema
CREATE USER lima_512_md
IDENTIFEID BY <<password>>
DEFAULT TABLESPACE ts_lima_512_md;3) Log in as the user you just created and create whatever objects you need to create. Assuming you don't specify a tablespace in your DDL, the default tablespace for the user will be used. Otherwise, it would be perfectly valid to have different users/ schemas own objects of the same name in the same tablespace.
4) Create a role that gives other users whatever permissions they'll need on objects and grant the role those privileges, i.e. for read-only access to tables
CREATE ROLE lima_512_md_read_only;
FOR x IN (SELECT * FROM user_tables)
LOOP
EXECUTE IMMEDIATE 'GRANT SELECT ON lima_512_md.' ||
x.table_name ||
' TO lima_512_md_read_only';
END LOOP;5) Grant this role to whatever other users you'd like
GRANT lima_512_md_read_only TO scott;6) Now, you can log in as scott, set the current_schema in the session, and query any of the tables in the LIMA_512_MD schema.
Justin

Re- organize a tablespace

Similar Messages

Maybe you are looking for