Creating tablespace and databasefiles

I am creating a tablespace with sets of database files within it with the following option
I get the following error:
CREATE SMALLFILE TABLESPACE "CLAIMS_NEW"
DATAFILE
'D:\ORACLE\PRODUCT\10.2.0\ORADATA\QAIDM2\CLAIMS_NEW1.DBF' SIZE 4096M REUSE AUTOEXTEND ON NEXT 8192K MAXSIZE 4096M,
'D:\ORACLE\PRODUCT\10.2.0\ORADATA\QAIDM2\CLAIMS_NEW2.DBF' SIZE 4096M REUSE AUTOEXTEND ON NEXT 8192K MAXSIZE 4096M,
'D:\ORACLE\PRODUCT\10.2.0\ORADATA\QAIDM2\CLAIMS_NEW3.DBF' SIZE 4096M REUSE AUTOEXTEND ON NEXT 8192K MAXSIZE 4096M,
'D:\ORACLE\PRODUCT\10.2.0\ORADATA\QAIDM2\CLAIMS_NEW4.DBF' SIZE 4096M REUSE AUTOEXTEND ON NEXT 8192K MAXSIZE 4096M,
'D:\ORACLE\PRODUCT\10.2.0\ORADATA\QAIDM2\CLAIMS_NEW5.DBF' SIZE 4096M REUSE AUTOEXTEND ON NEXT 8192K MAXSIZE 4096M,
'D:\ORACLE\PRODUCT\10.2.0\ORADATA\QAIDM2\CLAIMS_NEW6.DBF' SIZE 4096M REUSE AUTOEXTEND ON NEXT 8192K MAXSIZE 4096M,
'D:\ORACLE\PRODUCT\10.2.0\ORADATA\QAIDM2\CLAIMS_NEW7.DBF' SIZE 4096M REUSE AUTOEXTEND ON NEXT 8192K MAXSIZE 4096M,
'D:\ORACLE\PRODUCT\10.2.0\ORADATA\QAIDM2\CLAIMS_NEW8.DBF' SIZE 4096M REUSE AUTOEXTEND ON NEXT 8192K MAXSIZE 4096M,
'D:\ORACLE\PRODUCT\10.2.0\ORADATA\QAIDM2\CLAIMS_NEW9.DBF' SIZE 4096M REUSE AUTOEXTEND ON NEXT 8192K MAXSIZE 4096M,
'D:\ORACLE\PRODUCT\10.2.0\ORADATA\QAIDM2\CLAIMS_NEW10.DBF' SIZE 4096M REUSE AUTOEXTEND ON NEXT 8192K MAXSIZE 4096M,
'D:\ORACLE\PRODUCT\10.2.0\ORADATA\QAIDM2\CLAIMS_NEW11.DBF' SIZE 4096M REUSE AUTOEXTEND ON NEXT 8192K MAXSIZE 4096M,
'D:\ORACLE\PRODUCT\10.2.0\ORADATA\QAIDM2\CLAIMS_NEW12.DBF' SIZE 4096M REUSE AUTOEXTEND ON NEXT 8192K MAXSIZE 4096M,
'D:\ORACLE\PRODUCT\10.2.0\ORADATA\QAIDM2\CLAIMS_NEW13.DBF' SIZE 4096M REUSE AUTOEXTEND ON NEXT 8192K MAXSIZE 4096M,
'D:\ORACLE\PRODUCT\10.2.0\ORADATA\QAIDM2\CLAIMS_NEW14.DBF' SIZE 4096M REUSE AUTOEXTEND ON NEXT 8192K MAXSIZE 4096M,
'D:\ORACLE\PRODUCT\10.2.0\ORADATA\QAIDM2\CLAIMS_NEW15.DBF' SIZE 4096M REUSE AUTOEXTEND ON NEXT 8192K MAXSIZE 4096M
NOLOGGING EXTENT MANAGEMENT LOCAL SEGMENT SPACE MANAGEMENT AUTO;
Error:
Error at Command Line:1 Column:0
Error report:
SQL Error: ORA-00059: maximum number of DB_FILES exceeded
00059. 00000 - "maximum number of DB_FILES exceeded"
*Cause: The value of the DB_FILES initialization parameter was exceeded.
*Action: Increase the value of the DB_FILES parameter and warm start.
I am not sure how to rectify this error ? Do I have to reduce number of database files ?
Please advise
Thanks
Jay

Cause of The Problem
You have reached the limit of DB_FILES parameter. Before entering into solution part let's have an idea about DB_FILES and MAXDATAFILES parameter.
The DB_FILES parameter limits the maximum number of datafile can exist in oracle database. We can't change this parameter dynamically. We have to change it spfile by using ALTER SYSTEM .... SCOPE=SPFILE or in the pfile.
And the MAXDATAFILES parameter you can find with the CREATE DATABASE command or in CREATE CONTROLFILE command. It is also a limitation of maximum number of datafiles can be in the datafile. But starting from oracle 8 this hard limit parameter can be easily expanded up to DB_FILES parameter. So, if you attempt to add a new file whose number is greater than MAXDATAFILES, but less than or equal to DB_FILES, the MAXDATAFILES parameter of the control file will expand automatically to accommodate more files.
So, if you are after oracle 8i then we should just forget about MAXDATAFILES parameter. We should rather think about DB_FILES parameter.
Solution of The Problem
If you use pfile to startup the database then edit pfile and add/modify the DB_FILES parameter to a greater value so that it can accommodate higher number of datafiles. Then start the database using that pfile.
If you use spfile to startup the database then issue,
SQL> alter system set db_files=300 scope=spfile;
System altered.
Then start your database and either create tablespace or add datafile to an existing tablespace. Hopefully it will work.source:-
http://arjudba.blogspot.com/2008/08/maxdatafiles-dbfiles-parameters-and-ora.html
also refer,
http://laurentschneider.com/wordpress/2006/01/change-maxdatafiles-malogfiles-maxinstances-maxlogmembers-without-downtime.html

Similar Messages

CREATE TABLESPACE AND ORA-03214

when i create tablespace specifiled size less than 81,it occurs an error :ora-03214,the following code
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
SQL> CREATE TABLESPACE TEST DATAFILE '/u01/app/oracle/oradata/lonion/TEST01.dbf' SIZE 64K;
CREATE TABLESPACE TEST DATAFILE '/u01/app/oracle/oradata/lonion/TEST01.dbf' SIZE 64K
ERROR at line 1:
ORA-03214: File Size specified is smaller than minimum required
SQL> CREATE TABLESPACE TEST DATAFILE '/u01/app/oracle/oradata/lonion/TEST01.dbf' SIZE 65K;
CREATE TABLESPACE TEST DATAFILE '/u01/app/oracle/oradata/lonion/TEST01.dbf' SIZE 65K
ERROR at line 1:
ORA-03214: File Size specified is smaller than minimum required
SQL> CREATE TABLESPACE TEST DATAFILE '/u01/app/oracle/oradata/lonion/TEST01.dbf' SIZE 79K;
CREATE TABLESPACE TEST DATAFILE '/u01/app/oracle/oradata/lonion/TEST01.dbf' SIZE 79K
ERROR at line 1:
ORA-03214: File Size specified is smaller than minimum required
SQL> CREATE TABLESPACE TEST DATAFILE '/u01/app/oracle/oradata/lonion/TEST01.dbf' SIZE 80K;
CREATE TABLESPACE TEST DATAFILE '/u01/app/oracle/oradata/lonion/TEST01.dbf' SIZE 80K
ERROR at line 1:
ORA-03214: File Size specified is smaller than minimum required
SQL> CREATE TABLESPACE TEST DATAFILE '/u01/app/oracle/oradata/lonion/TEST01.dbf' SIZE 81K;
Tablespace created.
SQL> SELECT TABLESPACE_NAME,BLOCK_SIZE ,INITIAL_EXTENT FROM DBA_TABLESPACES WHERE TABLESPACE_NAME = 'TEST';
TABLESPACE_NAME            　　 BLOCK_SIZE    　   INITIAL_EXTENT
TEST                           8192             　    65536why the size is 81 can create tablespace successfully? how to calculate it?

Hi;
One 64k header block for the datafile plus one 16k header block for the tablespace or vice versa, plus 1 empty block.
64k + 16k + 8k(1 empty block) = 88k > 81kORA-03214: File Size specified is smaller than minimum required[b].
how to calculate the minimum required?
Answer:
ORA-3214 When Creating a Tablespace [ID 153869.1]
Regard
Helios

Can i create processor and player in same programm

hi,
We are doing video conferencing.For this we have to capture video and save this video in a file but we are not able to display the captured video before save it into file.
we are confused that weather we have to use createProcessor() or createRealizedProcessor()
so please anyone can help us ,
reply.

If you have connected to the database with an account that has these privileges.
Thus, for example, if your account has been granted the "DBA" role, then you can do so. Else, if your account has been granted the "CREATE TABLESPACE" and "CREATE USER", you can do so, even without the "DBA" role.
Granting specific privileges to allow an account to execute specific functions is far more secure than granting the "DBA" role.
Hemant K Chitale

Creating database and users while reverse engineering

While capturing design of existing databases we have to create tablespace and users.
Does this information have to be the same as the ones in the existing databases.
For ex: if i am capturing design of ESP schema our DBA has created tablespace ESP_dev1 and user ESP for this schema. When i reverse engineer i have to give the same info or this info is diff from real database and the designer repository. I don't understand this concept.
Can anybody explain this to me.
Thanks.
Navya.

So, when i make changes to the captured design and regerenate it's not going to use this info, right.
Since default settings are creating system and sys users which are not advisable to create in the real database.
Thanks,
Navya.

Creating new TableSpace and shifting existing ....

I created a database but it is using the default tablespace. I want to create a new tablespace and want to configure existing database to use new tablespace. How to do this? The database is having enough records.

>>alter user scott default tablespace system; 
 
Assume the default tablespaces for users USER1 and 
USER2 are TS1 and TS2 respectively, specified 
explicitly during user creation. The current 
default tablespace for the database is TS2, but 
later, the database default tablespace is changed to 
TS1. Even though USER2's default tablespace was 
explicitly specified as TS2 
 
 
sys@ORCL> create user user1 identified by user1 default tablespace system;
User created.
Elapsed: 00:00:00.06
sys@ORCL> create user user2 identified by user2 default tablespace system;
User created.
Elapsed: 00:00:00.01
sys@ORCL> select property_value
2 from database_properties
3 where property_name = 'DEFAULT_PERMANENT_TABLESPACE';
PROPERTY_VALUE
USERS
Elapsed: 00:00:00.00
sys@ORCL> select default_tablesapce
2 from dba_users
3 where username
4
sys@ORCL> select username, default_tablespace
2 from dba_users
3 where username in ('USER1', 'USER2');
USERNAME DEFAULT_TABLESPACE
USER1 SYSTEM
USER2 SYSTEM
Elapsed: 00:00:00.01
sys@ORCL> alter database default tablespace example;
Database altered.
Elapsed: 00:00:00.01
sys@ORCL> select username, default_tablespace
2 from dba_users
3 where username in ('USER1', 'USER2');
USERNAME DEFAULT_TABLESPACE
USER1 SYSTEM
USER2 SYSTEM
Elapsed: 00:00:00.01
sys@ORCL> select property_value
2 from database_properties
3 where property_name = 'DEFAULT_PERMANENT_TABLESPACE';
PROPERTY_VALUE
EXAMPLE
Elapsed: 00:00:00.00
sys@ORCL>

Doubt with parameters creating a tablespace and a table

I've created a tablespace and a table with these data:
CREATE TABLESPACE "TAB_FILE"
LOGGING
DATAFILE 'C:\TAB_FILE.ora' SIZE 20M
AUTOEXTEND ON NEXT 5M MAXSIZE 500M
EXTENT MANAGEMENT LOCAL
SEGMENT SPACE MANAGEMENT AUTO;
CREATE TABLE FILE
IDFILE NUMBER(16),
VERSION VARCHAR2(5) NOT NULL,
NAME VARCHAR2(40) NOT NULL,
TABLESPACE TAB_FILE,
PCTFREE 20,
PCTUSED 40,
INITRANS 6,
MAXTRANS 12,
STORAGE (INITIAL 1024K NEXT 1024K PCTINCREASE 0 MAXEXTENTS 8);
Is it useless (or not advisable) to write the parameters
PCTFREE,
PCTUSED,
INITRANS,
MAXTRANS and
STORAGE (INITIAL 1024K NEXT 1024K PCTINCREASE 0 MAXEXTENTS 8)
if I've written in the tablespace creation
EXTENT MANAGEMENT LOCAL
SEGMENT SPACE MANAGEMENT AUTO?
Thanks a lot

I've read that autoallocate parameter is worse than uniform size:
"Note - there is an autoallocate option for LMTs that can be used instead of uniform size X. This still slices the file up into uniform chunks (in this case always at 64K), and uses one bit per chunk. However, instead of equating one chunk with one extent, Oracle will consider past history and available gaps to decide what size extent to allocate. The extent will be one of a limited set of sizes - 64K, 1MB, 8MB, 64MB. For relatively small, simple systems where there isn't much information available about proper sizing requirements, this can be a minimum fuss mechanism to adopt; but in general I believe you should stick with uniform sizing.......But why is it so convenient to force every extent in the tablespace to be the same size ? (And at this point, you may appreciate my earlier comment about avoiding autoallocate LMTs, which allow for half a dozen sizes of extents). First, ease of monitoring space; secondly, convenience of data packing, and third, reliability of object rebuilds. "
Is it right? If yes, could anyone tell me with size could be correct? Does it depend on the size of the table, for example? Is there any formula to get the uniform size?
Message was edited by:
user573997

A script to accept dafault tablespace and tempspace at runtime create users

I need to write a script to accept default tablespace and temporary tablespace , then create the users in that tablespace. Please see the example but some how it is not working....
prompt Specify user's default tablespace
prompt Using &&default_tablespace for the default tablespace
prompt Specify user's temporary tablespace
prompt Using &&temporary_tablespace for the temporary tablespace
create user test identified by test default tablespace &&default_tablespace temporary tablespace &&temporary_tablespace ;
grant connect , resource to test;
Please help me in identifying the errors
Thanks in advance...
Message was edited by:
mvarier

some how it is not workingHow ? Doesn't the user get created ? Do you get errors ? which errors ?
(It worked to me)

What are differences between the target tablespace and the source tablespac

The IMPDP command create so manay errors. But the EXAMPLE tablespace is transported to the target database successfully. It seems that the transported tablespace is no difference with the source tablespace.
Why create so many errors?
How to avoid these errors?
What are differences between the target tablespace and the source tablespace?
Is this datapump action really successfull?
Thw following is the log output:
[oracle@hostp ~]$ impdp system/oracle dumpfile=user_dir:demo02.dmp tablespaces=example remap_tablespace=example:example
Import: Release 10.2.0.1.0 - Production on Sunday, 28 September, 2008 18:08:31
Copyright (c) 2003, 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
Master table "SYSTEM"."SYS_IMPORT_TABLESPACE_01" successfully loaded/unloaded
Starting "SYSTEM"."SYS_IMPORT_TABLESPACE_01": system/******** dumpfile=user_dir:demo02.dmp tablespaces=example remap_tablespace=example:example
Processing object type TABLE_EXPORT/TABLE/TABLE
ORA-39117: Type needed to create table is not included in this operation. Failing sql is:
CREATE TABLE "OE"."CUSTOMERS" ("CUSTOMER_ID" NUMBER(6,0), "CUST_FIRST_NAME" VARCHAR2(20) CONSTRAINT "CUST_FNAME_NN" NOT NULL ENABLE, "CUST_LAST_NAME" VARCHAR2(20) CONSTRAINT "CUST_LNAME_NN" NOT NULL ENABLE, "CUST_ADDRESS" "OE"."CUST_ADDRESS_TYP" , "PHONE_NUMBERS" "OE"."PHONE_LIST_TYP" , "NLS_LANGUAGE" VARCHAR2(3), "NLS_TERRITORY" VARCHAR2(30), "CREDIT_LIMIT" NUMBER(9,2), "CUST_EMAIL" VARCHAR2(30), "ACCOUNT_MGR_ID" NU
ORA-39117: Type needed to create table is not included in this operation. Failing sql is:
ORA-39117: Type needed to create table is not included in this operation. Failing sql is:
CREATE TABLE "IX"."ORDERS_QUEUETABLE" ("Q_NAME" VARCHAR2(30), "MSGID" RAW(16), "CORRID" VARCHAR2(128), "PRIORITY" NUMBER, "STATE" NUMBER, "DELAY" TIMESTAMP (6), "EXPIRATION" NUMBER, "TIME_MANAGER_INFO" TIMESTAMP (6), "LOCAL_ORDER_NO" NUMBER, "CHAIN_NO" NUMBER, "CSCN" NUMBER, "DSCN" NUMBER, "ENQ_TIME" TIMESTAMP (6), "ENQ_UID" VARCHAR2(30), "ENQ_TID" VARCHAR2(30), "DEQ_TIME" TIMESTAMP (6), "DEQ_UID" VARCHAR2(30), "DEQ_
Processing object type TABLE_EXPORT/TABLE/TABLE_DATA
. . imported "SH"."CUSTOMERS" 9.850 MB 55500 rows
. . imported "SH"."SUPPLEMENTARY_DEMOGRAPHICS" 695.9 KB 4500 rows
. . imported "OE"."PRODUCT_DESCRIPTIONS" 2.379 MB 8640 rows
. . imported "SH"."SALES":"SALES_Q4_2001" 2.257 MB 69749 rows
. . imported "SH"."SALES":"SALES_Q1_1999" 2.070 MB 64186 rows
. . imported "SH"."SALES":"SALES_Q3_2001" 2.129 MB 65769 rows
. . imported "SH"."SALES":"SALES_Q1_2000" 2.011 MB 62197 rows
. . imported "SH"."SALES":"SALES_Q1_2001" 1.964 MB 60608 rows
. . imported "SH"."SALES":"SALES_Q2_2001" 2.050 MB 63292 rows
. . imported "SH"."SALES":"SALES_Q3_1999" 2.166 MB 67138 rows
Processing object type TABLE_EXPORT/TABLE/GRANT/OWNER_GRANT/OBJECT_GRANT
ORA-39083: Object type OBJECT_GRANT failed to create with error:
ORA-01917: user or role 'USER1' does not exist
Failing sql is:
GRANT SELECT ON "HR"."REGIONS" TO "USER1"
ORA-39083: Object type OBJECT_GRANT failed to create with error:
ORA-01917: user or role 'EXAM_03' does not exist
Failing sql is:
GRANT SELECT ON "HR"."REGIONS" TO "EXAM_03"
ORA-39083: Object type OBJECT_GRANT failed to create with error:
ORA-01917: user or role 'USER1' does not exist
Failing sql is:
GRANT SELECT ON "HR"."COUNTRIES" TO "USER1"
ORA-39083: Object type OBJECT_GRANT failed to create with error:
ORA-01917: user or role 'EXAM_03' does not exist
Failing sql is:
GRANT SELECT ON "HR"."COUNTRIES" TO "EXAM_03"
ORA-39083: Object type OBJECT_GRANT failed to create with error:
ORA-01917: user or role 'USER1' does not exist
Failing sql is:
GRANT SELECT ON "HR"."LOCATIONS" TO "USER1"
ORA-39083: Object type OBJECT_GRANT failed to create with error:
ORA-01917: user or role 'EXAM_03' does not exist
Failing sql is:
GRANT SELECT ON "HR"."LOCATIONS" TO "EXAM_03"
ORA-39083: Object type OBJECT_GRANT failed to create with error:
ORA-01917: user or role 'USER1' does not exist
Failing sql is:
GRANT SELECT ON "HR"."DEPARTMENTS" TO "USER1"
ORA-39083: Object type OBJECT_GRANT failed to create with error:
ORA-01917: user or role 'EXAM_03' does not exist
Failing sql is:
GRANT SELECT ON "HR"."DEPARTMENTS" TO "EXAM_03"
ORA-39083: Object type OBJECT_GRANT failed to create with error:
ORA-01917: user or role 'USER1' does not exist
Failing sql is:
GRANT SELECT ON "HR"."JOBS" TO "USER1"
ORA-39083: Object type OBJECT_GRANT failed to create with error:
ORA-01917: user or role 'EXAM_03' does not exist
Failing sql is:
GRANT SELECT ON "HR"."JOBS" TO "EXAM_03"
ORA-39083: Object type OBJECT_GRANT failed to create with error:
ORA-01917: user or role 'USER1' does not exist
Failing sql is:
GRANT SELECT ON "HR"."EMPLOYEES" TO "USER1"
ORA-39083: Object type OBJECT_GRANT failed to create with error:
ORA-01917: user or role 'EXAM_03' does not exist
Failing sql is:
GRANT SELECT ON "HR"."EMPLOYEES" TO "EXAM_03"
ORA-39083: Object type OBJECT_GRANT failed to create with error:
ORA-01917: user or role 'USER1' does not exist
Failing sql is:
GRANT SELECT ON "HR"."JOB_HISTORY" TO "USER1"
ORA-39083: Object type OBJECT_GRANT failed to create with error:
ORA-01917: user or role 'EXAM_03' does not exist
Failing sql is:
GRANT SELECT ON "HR"."JOB_HISTORY" TO "EXAM_03"
ORA-39112: Dependent object type OBJECT_GRANT:"OE" skipped, base object type TABLE:"OE"."CUSTOMERS" creation failed
ORA-39112: Dependent object type OBJECT_GRANT:"OE" skipped, base object type TABLE:"OE"."CUSTOMERS" creation failed
Processing object type TABLE_EXPORT/TABLE/INDEX/INDEX
ORA-39112: Dependent object type INDEX:"OE"."CUSTOMERS_PK" skipped, base object type TABLE:"OE"."CUSTOMERS" creation failed
ORA-39112: Dependent object type INDEX:"OE"."CUST_ACCOUNT_MANAGER_IX" skipped, base object type TABLE:"OE"."CUSTOMERS" creation failed
ORA-39112: Dependent object type INDEX:"OE"."CUST_LNAME_IX" skipped, base object type TABLE:"OE"."CUSTOMERS" creation failed
ORA-39112: Dependent object type INDEX:"OE"."CUST_EMAIL_IX" skipped, base object type TABLE:"OE"."CUSTOMERS" creation failed
ORA-39112: Dependent object type INDEX:"PM"."PRINTMEDIA_PK" skipped, base object type TABLE:"PM"."PRINT_MEDIA" creation failed
Processing object type TABLE_EXPORT/TABLE/CONSTRAINT/CONSTRAINT
ORA-39112: Dependent object type CONSTRAINT:"OE"."CUSTOMER_CREDIT_LIMIT_MAX" skipped, base object type TABLE:"OE"."CUSTOMERS" creation failed
ORA-39112: Dependent object type CONSTRAINT:"OE"."CUSTOMER_ID_MIN" skipped, base object type TABLE:"OE"."CUSTOMERS" creation failed
ORA-39112: Dependent object type CONSTRAINT:"OE"."CUSTOMERS_PK" skipped, base object type TABLE:"OE"."CUSTOMERS" creation failed
ORA-39112: Dependent object type CONSTRAINT:"PM"."PRINTMEDIA__PK" skipped, base object type TABLE:"PM"."PRINT_MEDIA" creation failed
ORA-39112: Dependent object type CONSTRAINT:"IX"."SYS_C005192" skipped, base object type TABLE:"IX"."ORDERS_QUEUETABLE" creation failed
Processing object type TABLE_EXPORT/TABLE/INDEX/STATISTICS/INDEX_STATISTICS
ORA-39112: Dependent object type INDEX_STATISTICS skipped, base object type INDEX:"OE"."CUSTOMERS_PK" creation failed
ORA-39112: Dependent object type INDEX_STATISTICS skipped, base object type INDEX:"OE"."CUST_ACCOUNT_MANAGER_IX" creation failed
ORA-39112: Dependent object type INDEX_STATISTICS skipped, base object type INDEX:"OE"."CUST_LNAME_IX" creation failed
ORA-39112: Dependent object type INDEX_STATISTICS skipped, base object type INDEX:"OE"."CUST_EMAIL_IX" creation failed
ORA-39112: Dependent object type INDEX_STATISTICS skipped, base object type INDEX:"PM"."PRINTMEDIA_PK" creation failed
Processing object type TABLE_EXPORT/TABLE/COMMENT
ORA-39112: Dependent object type COMMENT skipped, base object type TABLE:"OE"."CUSTOMERS" creation failed
ORA-39112: Dependent object type COMMENT skipped, base object type TABLE:"OE"."CUSTOMERS" creation failed
ORA-39112: Dependent object type COMMENT skipped, base object type TABLE:"OE"."CUSTOMERS" creation failed
ORA-39112: Dependent object type COMMENT skipped, base object type TABLE:"OE"."CUSTOMERS" creation failed
ORA-39112: Dependent object type COMMENT skipped, base object type TABLE:"OE"."CUSTOMERS" creation failed
ORA-39112: Dependent object type COMMENT skipped, base object type TABLE:"OE"."CUSTOMERS" creation failed
ORA-39112: Dependent object type COMMENT skipped, base object type TABLE:"OE"."CUSTOMERS" creation failed
ORA-39112: Dependent object type COMMENT skipped, base object type TABLE:"OE"."CUSTOMERS" creation failed
ORA-39112: Dependent object type COMMENT skipped, base object type TABLE:"OE"."CUSTOMERS" creation failed
Processing object type TABLE_EXPORT/TABLE/CONSTRAINT/REF_CONSTRAINT
ORA-39112: Dependent object type REF_CONSTRAINT:"OE"."CUSTOMERS_ACCOUNT_MANAGER_FK" skipped, base object type TABLE:"OE"."CUSTOMERS" creation failed
ORA-39083: Object type REF_CONSTRAINT failed to create with error:
ORA-00942: table or view does not exist
Failing sql is:
ALTER TABLE "OE"."ORDERS" ADD CONSTRAINT "ORDERS_CUSTOMER_ID_FK" FOREIGN KEY ("CUSTOMER_ID") REFERENCES "OE"."CUSTOMERS" ("CUSTOMER_ID") ON DELETE SET NULL ENABLE
ORA-39112: Dependent object type REF_CONSTRAINT:"PM"."PRINTMEDIA_FK" skipped, base object type TABLE:"PM"."PRINT_MEDIA" creation failed
Processing object type TABLE_EXPORT/TABLE/TRIGGER
ORA-39082: Object type TRIGGER:"HR"."SECURE_EMPLOYEES" created with compilation warnings
ORA-39082: Object type TRIGGER:"HR"."SECURE_EMPLOYEES" created with compilation warnings
ORA-39082: Object type TRIGGER:"HR"."UPDATE_JOB_HISTORY" created with compilation warnings
ORA-39082: Object type TRIGGER:"HR"."UPDATE_JOB_HISTORY" created with compilation warnings
Processing object type TABLE_EXPORT/TABLE/INDEX/FUNCTIONAL_AND_BITMAP/INDEX
ORA-39112: Dependent object type INDEX:"OE"."CUST_UPPER_NAME_IX" skipped, base object type TABLE:"OE"."CUSTOMERS" creation failed
Processing object type TABLE_EXPORT/TABLE/INDEX/STATISTICS/FUNCTIONAL_AND_BITMAP/INDEX_STATISTICS
ORA-39112: Dependent object type INDEX_STATISTICS skipped, base object type INDEX:"OE"."CUST_UPPER_NAME_IX" creation failed
Processing object type TABLE_EXPORT/TABLE/STATISTICS/TABLE_STATISTICS
ORA-39112: Dependent object type TABLE_STATISTICS skipped, base object type TABLE:"OE"."CUSTOMERS" creation failed
ORA-39112: Dependent object type TABLE_STATISTICS skipped, base object type TABLE:"PM"."PRINT_MEDIA" creation failed
ORA-39112: Dependent object type TABLE_STATISTICS skipped, base object type TABLE:"PM"."PRINT_MEDIA" creation failed
ORA-39112: Dependent object type TABLE_STATISTICS skipped, base object type TABLE:"IX"."ORDERS_QUEUETABLE" creation failed
Processing object type TABLE_EXPORT/TABLE/INDEX/DOMAIN_INDEX/INDEX
Processing object type TABLE_EXPORT/TABLE/POST_INSTANCE/PROCACT_INSTANCE
ORA-39112: Dependent object type PROCACT_INSTANCE skipped, base object type TABLE:"IX"."ORDERS_QUEUETABLE" creation failed
ORA-39083: Object type PROCACT_INSTANCE failed to create with error:
ORA-01403: no data found
ORA-01403: no data found
Failing sql is:
BEGIN
SYS.DBMS_AQ_IMP_INTERNAL.IMPORT_SIGNATURE_TABLE('AQ$_ORDERS_QUEUETABLE_G');COMMIT; END;
Processing object type TABLE_EXPORT/TABLE/POST_INSTANCE/PROCDEPOBJ
ORA-39112: Dependent object type PROCDEPOBJ:"IX"."AQ$_ORDERS_QUEUETABLE_V" skipped, base object type TABLE:"IX"."ORDERS_QUEUETABLE" creation failed
ORA-39112: Dependent object type PROCDEPOBJ:"IX"."ORDERS_QUEUE_N" skipped, base object type TABLE:"IX"."ORDERS_QUEUETABLE" creation failed
ORA-39112: Dependent object type PROCDEPOBJ:"IX"."ORDERS_QUEUE_R" skipped, base object type TABLE:"IX"."ORDERS_QUEUETABLE" creation failed
ORA-39112: Dependent object type PROCDEPOBJ:"IX"."AQ$_ORDERS_QUEUETABLE_E" skipped, base object type TABLE:"IX"."ORDERS_QUEUETABLE" creation failed
ORA-39112: Dependent object type PROCDEPOBJ:"IX"."ORDERS_QUEUE" skipped, base object type TABLE:"IX"."ORDERS_QUEUETABLE" creation failed
Job "SYSTEM"."SYS_IMPORT_TABLESPACE_01" completed with 63 error(s) at 18:09:14

Short of trying to then reverse-engineer the objects that are in the dump file (I believe Data Pump export files contain some XML representations of DDL in addition to various binary bits, making it potentially possible to try to scan the dump file for the object definitions), I would tend to assume that the export didn't include those type definitions.
Since it looks like you're trying to set up the sample schemas, is there a reason that you wouldn't just run the sample schema setup scripts on the destination database? Why are you using Data Pump in the first place?
Justin

Error in creating tablespaces

hi,
I have installed oracle9i in HP-USserver.its installed successfully.
I ahve created the instance too with datafiles.but the problem is that due to shortage of disk space,iam unable to store datas.so i have dropped the tablespaces and tried to create to a new file system (in the sense a new hard drive) in the same server.while creating the tablespaces alone in a different path its
showing error as
SQL*Plus: Release 9.2.0.2.0 - Production on Sat Jul 28 13:18:44 2007
Copyright (c) 1982, 2002, Oracle Corporation. All rights reserved.
Enter user-name: sys as sysdbas
Enter password:
Connected to:
Oracle9i Enterprise Edition Release 9.2.0.2.0 - 64bit Production
With the Partitioning, OLAP and Oracle Data Mining options
JServer Release 9.2.0.2.0 - Production
SQL> CREATE TABLESPACE DATAXML
2 LOGGING DATAFILE
3 '/server47/Bankareas/CFC/oracledatafiles/globusdataxml01.dbf' SIZE 2048M AUTOEXTEND ON MAXSIZE UNLIMITED,
4 '/server47/Bankareas/CFC/oracledatafiles/globusdataxml02.dbf' SIZE 2048M AUTOEXTEND ON MAXSIZE UNLIMITED,
5 '/server47/Bankareas/CFC/oracledatafiles/globusdataxml03.dbf' SIZE 2048M AUTOEXTEND ON MAXSIZE UNLIMITED
6 EXTENT MANAGEMENT LOCAL
7 SEGMENT SPACE MANAGEMENT AUTO;
CREATE TABLESPACE DATAXML
ERROR at line 1:
ORA-01119: error in creating database file
'/server47/Bankareas/CFC/oracledatafiles/globusdataxml01.dbf'
ORA-27086: skgfglk: unable to lock file - already in use
HPUX-ia64 Error: 13: Permission denied
Additional information: 8
i want to know whether the tablespaces can be created in a seperate path apart from where oracle is installed?
anything to be exported??
can anybody please help me out in solving this problem.
thanks in advance ,
Ratheesh

You state you have dropped the tablespace (which does not necessarily automatically drop the datafiles in version 9i); and
You state you are trying to locate the tablespace's datafiles in a new file system where no files should exist.
Please post response to
ls -ld /server47/Bankareas/CFC/oracledatafiles
ls -l /server47/Bankareas/CFC/oracledatafiles/globusdataxml01.dbf

Error in creating tablespace

Machine has the following configuration,
Oracle 10g 10.2.0
Solaris 10
Sparc v9-64 bit
I have mounted NAS(Network attached Storage) device on solaris using NFS file system. The device has been mounted using sharity software.
The problem is that when i execute the following command in sqlplus,
create tablespace test datafile '/storage/test.dbf' size 1m autoextend on
(/storage is the mount point for NAS device)
then i get the following error message
ORA-01119: error in creating database file '/storage/test.dbf'
ORA-27054: NFS file system where the file is created or resides is not mounted with correct options.
Additional Information:2

this is the document
http://download-uk.oracle.com/docs/cd/B19306_01/install.102/b15660/app_nas.htm#BCFEAHIC
and this will help either
10gR2 "database backup" to nfs mounted dir results in ORA-27054 NFS error

Not able to Create TABLESPACE PSAPROLL|PSAPUNDO    with 728 MB

Hi Experts,
               When i an trying to upgrade PI 7.0 to pi 7.1 with EHP1 in checks roadmap in abap it throws error like
ERROR> Insufficient free space in the database as follows:
Create TABLESPACE PSAPROLL|PSAPUNDO    with 728 MB
INFO> To adjust the size of your tablespaces, you may use the commands
      in file '/oracle/stage/upg/abap/log/ORATBSXT.LST' using the 'brspace' utility.
      Please copy the file before making changes, as it may be
      overwritten in subsequent upgrade phases.
In the location
'/oracle/stage/upg/abap/log/ORATBSXT.LST
These are examples for brspace commands to extend/create the required
tablespaces. You can adapt them according to your own needs.
Add option '-c force' to call the commands in batch mode.
Change option '-autoextend' to 'yes' and set '-maxsize' and '-incrsize'
to create autoextensible segments.
brspace -function tscreate -tablespace PSAPROLL|PSAPUNDO -owner SAPSR3 -size 728 -autoe
xtend no
info while creating : PSAPUNDO: Command not found.
with the help of this above command i am not able to create the tablespace.
My Existing tabelspaces are
PSAPSR3
PSAPSR3700
PSAPSR3DB
PSAPSR3USR
PSAPTEMP
PSAPUNDO1
SYSAUX
SYSTEM
Plz help me on this ASAP.
Thanks,
Hari

Your real problem is that PSAPUNDO does not exist. For an unknown reason you are using PSAPUNDO1. so, you must fix this:
shutdown your DB.
rename tablespace PSAPUNDO1 to PSAPUNDO. this can be done with:
brspace -c force -f tsalter -a rename -t PSAPUNDO1 -n PSAPUNDO
you will also need to change parameter undo_tablespace to PSAPUNDO
if using initSID.ora, change this manually. or else, do this:
alter system set undo_tablespace=PSAPUNDO scope=both;
you might need to restart your database.
good luck.

Any way to create tablespace with name greater than 30 characters ?

Is there any way to create tablespace greater than 30 characters on solaris 10 and Oracle 10g. Any way ? because i have no other option.

desc dba_tablespaces
So clearly the answer is NO.
Tablespace names are invisible and irrelevant. Why the question?

Createtablespace.sql is creating tablespaces in wrong sid

Hi,
We are in the process of performing system copy of EHP4 for TDMS shell creation using standard system copy process as suggested by sap.
During export while SAPInst asked for Import Migration Directory we provided the export dump of target system ( modified as per TDMS shell creation)
During system copy we are getting the error during create table space phase. SAPinst is creating the tablespace with source system SID. .i.e instead of T02 it is taking P02.
create tablespace P02#USER1D
in nodegroup SAPNODEGRP_T02 pagesize 16k extentsize 8 prefetchsize automatic
no file system caching
Because of that we are getting following error during import phase.
ERROR 2009-08-10 07:24:33.154 [iaxxinscbk.cpp:260]
MDB-01999 Error occured, first error is: <SQL0204N "P02#DDICD" is an undefined name. SQLSTATE=42704>
Please suggest.
Sanjay

Hi,
I have recently expierienced a very simialr sort of error doing a EHP5 upgrade.
(it's similar because I did a standard system copy (export/import) and got the same error )
It's not realy a solution but guidance:
If you check this table DDSTORAGE and search for the incorrect sid:
eg (assuming P02 is the incorrect SID):
select * from <your_schema>.ddstorage where text like '%P02%
you'll probrably find the erronous entries.
Since this a rare occurance, the best advice would be to open a message to SAP.
They would probrably want to remotely connected to the system and have a look.
I don't think there is a gerneral fix and each occurance would have to be handle at an individual level.
Since I use DB2 I used this component when creating my OSS:
BC-DB-DB6-UPG
I know this thread is old but
I've answered here as hopefully it may benifit anyone else that finds this thread.
Kind Regards,
chris

Create tablespace in Oracle 10g Express

Hi,
I've been playing around over the last few days with Oracle 10g Express and I need to create my own tablespace and therefore create user associated with my custom table space.
I tried with the command create tablespace, but I am not successful with configuring the parameters such as the datafile location and such. I did go through the Oracle Concepts Guide which was very helpful, but I must be missing something.
Also assuming that my db scheme will be part of my application and therefore released to my client as script so they can re-create my database how would the table space integration work on their end.
I would I have to place my first line of the script to create the table space and ask them for database file location?
Any advice will be appreciated.
Thank you in advance.

user12359577 wrote:
The reason why I think I should create my own tablespace is because I am creating a database scheme and thus I think it is appropriate to place my db scheme in its own tablespace instead of simply using the Users tablespace default.
This is my command:
create tablespace MYTBLSPACE;
Error:
Error starting at line 1 in command:
create tablespace MYTBLSPACE
Error at Command Line:1 Column:32
Error report:
SQL Error: ORA-02199: missing DATAFILE/TEMPFILE clause
02199. 00000 - "missing DATAFILE/TEMPFILE clause"
*Cause: A CREATE TABLESPACE statement has no DATAFILE/TEMPFILE clause.
*Action: Specify a DATAFILE/TEMPFILE clause.
I am also not sure how to specify the datafile.
Thank you.How about checking with the fine SQL Reference manual for the syntax of the CREATE TABLESPACE command?
Learning where to look things up in the documentation is time well spent investing in your career. To that end, you should drop everything else you are doing and do the following:
Go to tahiti.oracle.com. Drill down to your product and version.
Spend a few minutes just getting familiar with what is available here. Take special note of the "books" and "search" tabs. Under the "books" tab you will find the complete documentation library.
Spend a few minutes just getting familiar with what kind of documentation is available there by simply browsing the titles under the "Books" tab.
Open the Reference Manual and spend a few minutes looking through the table of contents to get familiar with what kind of information is available there.
Do the same with the SQL Reference Manual.
Do the same with the Utilities manual.
You don't have to read the above in depth. They are reference manuals. Just get familiar with what is there to be referenced. Ninety percent of the questions asked on this forum can be answered in less than 5 minutes by simply searching one of the above manuals.
Then set yourself a plan to dig deeper.
- Read a chapter a day from the Concepts Manual.
- Take a look in your alert log. One of the first things listed at startup is the initialization parms with non-default values. Read up on each one of them in the Reference Manual.
- Take a look at your listener.ora, tnsnames.ora, and sqlnet.ora files. Go to the Network Administrators manual and read up on everything you see in those files.
- When you have finished reading the Concepts Manual, do it again.
Give a man a fish and he eats for a day. Teach a man to fish and he eats for a lifetime.
Edited by: EdStevens on Mar 3, 2010 10:13 AM
Edited by: EdStevens on Mar 3, 2010 10:15 AM

Import database from Linux to Windows fails with creating tablespaces

Using (Oracle10g/Linux) user/schema (i think)"Sys" i exported succesfully full database and produced a log file which looks like this:
Connected to: Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
Export done in UTF8 character set and AL16UTF16 NCHAR character set
server uses AL32UTF8 character set (possible charset conversion)
Note: table data (rows) will not be exported
About to export the entire database ...
exporting tablespace definitions
exporting profiles
exporting user definitions
exporting roles
exporting resource costs
exporting rollback segment definitions
exporting database links
. exporting sequence numbers
exporting directory aliases
exporting context namespaces
exporting foreign function library names
exporting PUBLIC type synonyms
exporting private type synonyms
exporting object type definitions
exporting system procedural objects and actions
exporting pre-schema procedural objects and actions
exporting cluster definitions
about to export SYSTEM's tables via Conventional Path ...
exporting table                    DEF$_AQCALL
exporting table                   DEF$_AQERROR
exporting table                  DEF$_CALLDEST
EXP-00091: Exporting questionable statistics.
Export terminated successfully with warnings.Now (in Oracle10 Express/ Windows) i'm importing the dmp-file using user/schema System, following errors occur:
Connected to: Oracle Database 10g Express Edition Release 10.2.0.1.0 - Production
Export file created by EXPORT:V10.02.01 via conventional path
Warning: the objects were exported by SYS, not by you
import done in AL32UTF8 character set and AL16UTF16 NCHAR character set
export client uses UTF8 character set (possible charset conversion)
. importing SYSTEM's objects into SYSTEM
IMP-00017: following statement failed with ORACLE error 1119:
"CREATE UNDO TABLESPACE "UNDOTBS1" BLOCKSIZE 8192 DATAFILE '/u01/app/oracle"
"/oradata/live/undotbs01.dbf' SIZE 251658240       AUTOEXTEND ON NEXT 524288"
"0 MAXSIZE 32765M EXTENT MANAGEMENT LOCAL "
IMP-00003: ORACLE error 1119 encountered
ORA-01119: error in creating database file '/u01/app/oracle/oradata/live/undotbs01.dbf'
ORA-27040: file create error, unable to create file
OSD-04002: unable to open file
O/S-Error: (OS 3) The system cannot find the path specified.
IMP-00015: following statement failed because the object already exists:
"CREATE TABLESPACE "SYSAUX" BLOCKSIZE 8192 DATAFILE '/u01/app/oracle/oradat"
"a/live/sysaux01.dbf' SIZE 346030080       AUTOEXTEND ON NEXT 10485760 MAXS"
"IZE 32765M EXTENT MANAGEMENT LOCAL AUTOALLOCATE ONLINE PERMANENT SEGMENT"
" SPACE MANAGEMENT AUTO"
IMP-00000: Import terminated unsuccessfullyWhy i get those errors when importing? Seems like the main problem is that the export was done in Linux which have it's own directories like '/u01/app/oracle/oradat' and others but in my Windows OS those folders don't exist? The whole import fails because tablespaces couldn't be created, later Schemas couldn't be created and tables also. Can i get the import work somehow?
I runned the import as following:
C:\Users\charlesr>imp userid=system/a FULL=Y FILE=exp_ddl.dmp log=imp.logMy Oracle 10 XE is installed into folder:
D:\oraclexe\app\oracle\product\10.2.0Maybe i should run the import command in drive D where my Oracle lives, not in drive C as i did?
And now when i tried to run the import on drive C, seems like my database user "system/a" is corrupted or password corrupted:
C:\Users\charlesr>d:
D:\>imp userid=system/a FULL=Y FILE=exp_ddl.dmp log=imp.log
Import: Release 10.2.0.1.0 - Production on R Sept 10 17:32:25 2010
Copyright (c) 1982, 2005, Oracle. All rights reserved.
IMP-00058: ORACLE error 1017 encountered
ORA-01017: invalid username/password; logon deniedUsername:I think i don't have on OS level rights to write to C-drive, that's why i got errors. But now i can't log in with system/a, why so?
Edited by: CharlesRoos on Sep 10, 2010 7:38 AM

CharlesRoos wrote:
Why i get those errors when importing? Seems like the main problem is that the export was done in Linux which have it's own directories like '/u01/app/oracle/oradat' and others but in my Windows OS those folders don't exist? The whole import fails because tablespaces couldn't be created, later Schemas couldn't be created and tables also. Can i get the import work somehow?Precreate tablespaces. You could use import option show=y to capture import run statements and find CREATE TABLESPACE statements. Keep in mind your target database already has undo, temp system, etc. tablespaces so you do not need to precreate them. Then rerun import.
SY.

Creating tablespace and databasefiles

Similar Messages

Maybe you are looking for