Create a dictionary managed tablespace error.

When I use the following script to create a tablespace.
create tablespace DATA01
datafile 'c:\oracle\oradata\orawin2k\U04\data01.dbf' size 2M
EXTENT MANAGEMENT DICTIONARY;
But the oracle return this error.
ORA-12913: Cannot create dictionary managed table.
My Oracle Server is 9i Release in Window 2000.
Does any one know why? Please Help.

Check with docu: Oracle9i Database Error Messages
Error means "An attempt was made to create a dictionary managed tablespace in a database whose SYSTEM tablespace is locally managed."
So you can't create any DMTs.

Similar Messages

ORA-12913: Cannot create dictionary managed tablespace

I am using the following statement:
CREATE TABLESPACE data01
DATAFILE 'D:\ORACLE\ORADATA\SSR\data01.dbf' SIZE 2M
EXTENT MANAGEMENT DICTIONARY;
and I get the following error message:
ORA-12913: Cannot create dictionary managed tablespace
If I take off EXTENT MANAGEMENT DICTIONARY, the statement executes. What am I doing wrong?

Details about create a tablespace:
CREATE TABLESPACE
Purpose
Use the CREATE TABLESPACE statement to create a tablespace, which is an allocation of space in the database that can contain persistent schema objects.
When you create a tablespace, it is initially a read/write tablespace. You can subsequently use the ALTER TABLESPACE statement to take the tablespace offline or online, add datafiles to it, or make it a read-only tablespace.
You can also drop a tablespace from the database with the DROP TABLESPACE statement.
You can use the CREATE TEMPORARY TABLESPACE statement to create tablespaces that contain schema objects only for the duration of a session.
See Also:
Oracle9i Database Concepts for information on tablespaces
ALTER TABLESPACE for information on modifying tablespaces
DROP TABLESPACE for information on dropping tablespaces
CREATE TEMPORARY TABLESPACE
http://download-west.oracle.com/docs/cd/B10501_01/server.920/a96540/statements_74a.htm#SQLRF01403
Joel P�rez

Couldn't create dictionary managed tablespace

In Oracle9i release 2 I couldn't create tablespace of type dictionary managed
is there someway to do it???

This is just one of the RESTRICTIONS of Having a Locally Managed SYSTEM Tablespace. Dictionary managed tablespaces can not be created in a database with a locally managed SYSTEM tablespace.

Dictionary manage tablespace in 11 version

Hi,
Is it possible to create Dictionary manage tablespace in oracle 11 version
I try as below and get error
SQL> CREATE TABLESPACE test111
2 DATAFILE 'd:\test1\test1userdata01.dbf' SIZE 50M
3 EXTENT MANAGEMENT DICTIONARY
4 DEFAULT STORAGE ( initial 1M NEXT 1M );
CREATE TABLESPACE test111
ORA-12913: Cannot create dictionary managed tablespace
Can I create Dictionary manage tablespace in oracle 10 version?

iruss wrote:
Hi,
Is it possible to create Dictionary manage tablespace in oracle 11 version
I try as below and get error
SQL> CREATE TABLESPACE test111
2 DATAFILE 'd:\test1\test1userdata01.dbf' SIZE 50M
3 EXTENT MANAGEMENT DICTIONARY
4 DEFAULT STORAGE ( initial 1M NEXT 1M );
CREATE TABLESPACE test111
ORA-12913: Cannot create dictionary managed tablespace
Can I create Dictionary manage tablespace in oracle 10 version?You've gotten the answer on if you can. I'd be curious to know why you'd want to. This is akin to asking if you can put a hand-crank starter on your new Ferrari, "like I had on my Model-T".

Explain local manage tablespace and dictionary manage tablespace

hi all,
kindly help me to understand local manage and dictionary manage tablespace
i have read search result and oracle corporation book still unable to understand
what i know that local is managed by bitmap(no redo) and dictionary is managed by dictionary(generates redo) plz explain this as well
and also suggest me some documentation.
thanks
Navin

Navin,
These are excerpts from Oracle documentation
Dictionary Managed Tablespace_
If you created your database with an earlier version of Oracle, then you could be using dictionary managed tablespaces. For a tablespace that uses the data dictionary to manage its extents, Oracle updates the appropriate tables in the data dictionary whenever an extent is allocated or freed for reuse. Oracle also stores rollback information about each update of the dictionary tables. Because dictionary tables and rollback segments are part of the database, the space that they occupy is subject to the same space management operations as all other data.
Lcaolly Managed Tablesapce_
A tablespace that manages its own extents maintains a bitmap in each datafile to keep track of the free or used status of blocks in that datafile. Each bit in the bitmap corresponds to a block or a group of blocks. When an extent is allocated or freed for reuse, Oracle changes the bitmap values to show the new status of the blocks. These changes do not generate rollback information because they do not update tables in the data dictionary (except for special cases such as tablespace quota information).
Locally managed tablespaces have the following advantages over dictionary managed tablespaces:
Local management of extents automatically tracks adjacent free space, eliminating the need to coalesce free extents.
Local management of extents avoids recursive space management operations. Such recursive operations can occur in dictionary managed tablespaces if consuming or releasing space in an extent results in another operation that consumes or releases space in a data dictionary table or rollback segment.
The sizes of extents that are managed locally can be determined automatically by the system. Alternatively, all extents can have the same size in a locally managed tablespace and override object storage options.
http://download.oracle.com/docs/cd/B19306_01/server.102/b14220/physical.htm#sthref518
Regards

Is it possible to rename dictionary managed tablespace in oracle 10g?

Hi,
Assume my system tablespace is dictionary managed in oracle 10g and one of my permanent tablespace is dictionary managed.
Pls let me know that permanent dictionary managed tablespace can be renamed or not using rename tablespace command or only locally managed tablespaces can be renamed?
thanks,
DB

Hi Guys,
thanks for the replies.
As suggested, i created a database with dictionary managed system tablespace and users tablespace .
I was able to rename users tablespace to users_test.
Eventhough dictionary managed tablespace is deprecated in oracle 10g, it will be better if they just add a line in the 10gR2 documentation under renaming tablespaces section that dictionary managed tablespaces also can be renamed.
SQL> alter tablespace users rename to users_test;
Tablespace altered.
SQL> select tablespace_name,extent_management from dba_tablespaces;
TABLESPACE_NAME EXTENT_MAN
SYSTEM DICTIONARY
UNDOTBS1 LOCAL
SYSAUX LOCAL
TEMP LOCAL
USERS_TEST DICTIONARY
SQL> select * from v$instance;
INSTANCE_NUMBER INSTANCE_NAME HOST_NAME VERSION
1 dictest XXXXXX 10.2.0.1.0

Can I convert my tablespaces to dictionary managed if..?

...If my system tablespace is locally managed can I convert my tablespaces to dictionary managed? If yes, can you show me how?

If you try to create or convert a tablespace to dictionary managed when the system tablespace is locally managed you will get this error:
ORA-12913 Cannot create dictionary managed tablespace
Cause: An attempt was made to create a dictionary managed tablespace in a database whose SYSTEM tablespace is locally managed.
Action: Create a locally managed tablespace.
Joel PÃ©rez
http://www.oracle.com/technology/experts

Ora-12913 cannot create managed tablespace

I want to create dictionary managed tablespace so when i type create command i got error ora-12913 cannot create dictionary tablespace .
so at that time I have created locally managed tablespace still iam getting 'ora-12913 cannot create managed tablespace'

ORA-12913: Cannot create dictionary managed tablespace
Cause: Attemp to create dictionary managed tablespace in database which has system tablespace as locally managed
Action: Create a locally managed tablespace.
=============================================================================
It's not possible to create a dictionary managed tablespace in a database which has a locally managed SYSTEM tablespace.

Move Table on Ora 9.2 from tablespace to another (dictionary managed)

Hello,
is it possible to move tables with brtools from dictionary managed tablespace to another dictionary managed tablespace on Oracle 9.2 ?

Hello Axel,
this is a case where the BRSPACE error is not nice, because you have no easy chance to move this one table to a LMTS tablespace. In this case I would propose you to execute ALTER TABLE MOVE directly on Oracle side:
ALTER TABLE <table_name> MOVE TABLESPACE <target_tablespace>;
Afterwards all indexes of the table have to be rebuilt in order to validate them again:
ALTER INDEX <index_name> REBUILD ONLINE;
Kind regards
Martin

Dictionary managed tablepsaces on Oracle 9.2

Hello,
We have an application that needs some adjustment before it can use LMT efficiently.
I have two questions:
1
===
Can I configure Oracle 9.2 to work with DMT ?
I tried creating one as described in the 9.2 docs and get the following response:
SQL> CREATE TABLESPACE test
2 DATAFILE 'D:\oracle\oradata\studio92\test.dbf' SIZE 10M
3 EXTENT MANAGEMENT DICTIONARY
4 DEFAULT STORAGE (
5 INITIAL 100K
6 NEXT 5120K
7 MINEXTENTS 2
8 MAXEXTENTS unlimited
9 PCTINCREASE 0);
CREATE TABLESPACE test
ERROR at line 1:
ORA-12913: Cannot create dictionary managed tablespace
When I check what is ORA-12913, I see that if I have LMT system I can not use DMT , is that true ?
2
===
If I do change my system tbs to work with DMT, will I be able to use DMT.
Guys, try answering the direct questions instead of telling me that LMT is better, as I wrote above, there is a functional problem in my application that currently can not use it.
TIA
Tal Olier ([email protected]).

As I understand the situation, your SYSTEM tablespace must be a DMT in order to create non-SYSTEM DMT's. If you move SYSTEM back to a DMT, you shouldn't have problems creating new DMT's.
Here's the appropriate section of the Database Concepts guide.
http://download-west.oracle.com/docs/cd/B10501_01/server.920/a96524/c04space.htm#1003

Locally Managed tablespaces?

Into the Design Editor, Admin tab: How can I define a tablespace as Locally Managed?

Harvinder,
Locally managed tablespaces are part of the new features of Oracle 8i. the advantages
are when they database objects need to allocate space, they need not go through the
data dictionary, they can find the free space
through bitmaps in the datafile, hence the name locally managed tablespaces.
this improves performance because recursive sql (update/insert/select of data dictionary tables) is avoided.
temporary tablespaces are prime candidates for locally managed tablespaces.
yes the whole database can be created with locally managed tablespaces..but with some restrictions. see oracle documentation for further details.
Mukundan.

Recycle bin LMT Vs Dictionary Managed

Hi,
Am I right in thinking you only get a recycle bin for LMT's?
So any dictionary managed tablespaces will not have a recycle bin even if recyclebin is on for the database.
Thanks.

You're correct that DMTs cannot make use of the recyclebin functionality.
create tablespace hjr datafile 'C:\ORACLE\PRODUCT\10.2.0\ORADATA\TEST\hjr01.dbf' size 10m extent management dictionary;
create table t1 (col1 char(5)) tablespace hjr;
show recyclebin;
{nothing returned}
drop table t1;
show recyclebin;
{nothing returned}BUT...
create tablespace hjr2 datafile 'C:\ORACLE\PRODUCT\10.2.0\ORADATA\TEST\hjr201.dbf' size 10m extent management local;
create table t1 (col1 char(5)) tablespace hjr2;
show recyclebin;
{nothing returned}
drop table t1;
show recyclebin;
ORIGINAL NAME RECYCLEBIN NAME OBJECT TYPE DROP TIME
T1 BIN$zq24aOXxRGitS2FnP8SUjQ==$0 TABLE 2008-01-07:22:09:02It comes down to the fact that the recyclebin isn't a separate place where tables are moved to, but simply a means of marking extents for over-writing without actually vacating them. In DMT, that would potentially mean updating lots of rows in the UET$ table, and that would be expensive. In LMT, you simply set lots of bits.
The recyclebin is simply not feasible in DMT, in other words.

Default storage for locally managed tablespaces

the documentation says you cannot have a default storage parameter for locally managed tablespaces. Does this mean that we cannot specify
INITIAL
NEXT
PCTINCREASE
MINEXTENTS
MAXEXTENTS for such tablespaces, or is there another way we can, without using default storage?
thanks

I amnot sure where you read that part that the default storage clause can't be given.Please see here,
http://download.oracle.com/docs/cd/B19306_01/server.102/b14231/tspaces.htm#sthref1149
From the doc,
Creating a Locally Managed Tablespace
If the CREATE TABLESPACE statement includes a DEFAULT storage clause, then the database considers the following:
If you specified the MINIMUM EXTENT clause, the database evaluates whether the values of MINIMUM EXTENT, INITIAL, and NEXT are equal and the value of PCTINCREASE is 0. If so, the database creates a locally managed uniform tablespace with extent size = INITIAL. If the MINIMUM EXTENT, INITIAL, and NEXT parameters are not equal, or if PCTINCREASE is not 0, the database ignores any extent storage parameters you may specify and creates a locally managed, autoallocated tablespace.
If you did not specify MINIMUM EXTENT clause, the database evaluates only whether the storage values of INITIAL and NEXT are equal and PCTINCREASE is 0. If so, the tablespace is locally managed and uniform. Otherwise, the tablespace is locally managed and autoallocated.
HTH
Aman....

Locally managed tablespaces in Apps 11.0.3

Hi,
we are on Oracle Apps 11.0.3. we recently upgraded the database to 8i ( 8.1.7.4 ). I would like to change some high activity tablespaces to locally managed tablespaces to improve performance. Are there any issues in doing this ? Can I benefit from this or will I have any issues.
thanks
Ram

We moved all the tablespaces to locally managed. Although we convereted the tablespaces to locally managed, occassionally we would see some of the ddl commands hang, cause being system still trying to update fet$ and uet$ tables. We were able to fix this by creating new locally managed tablespaces and move the contents to new locally managed tablespaces.

Logminer error while creating a dictionary file

Hi ,
I am working on logminer.
i got the following error while creating a dictionary file :--
please help me out.
SQL> show parameter utl_
NAME TYPE VALUE
utl_file_dir string $ORACLE_BASE/utl_file/cecms
SQL> execute dbms_logmnr_d.build(dictionary_filename => 'dictionary.ora',dictionary_location => '/u00/oracle/utl_file/cecms');
BEGIN dbms_logmnr_d.build(dictionary_filename => 'dictionary.ora',dictionary_location => '/u00/oracle/utl_file/cecms'); END;
ERROR at line 1:
ORA-01336: specified dictionary file cannot be opened
ORA-29280: invalid directory path
ORA-06512: at "SYS.DBMS_LOGMNR_D", line 928
ORA-06512: at "SYS.DBMS_LOGMNR_D", line 2052
ORA-06512: at line 1
Asif

ORA-01336: specified dictionary file cannot be opened
Cause: The dictionary file or directory does not exist or is inaccessible.
Action: Make sure that the dictionary file and directory exist and are accessible.
Probably an issue with the rights on the directories.
To confirm the same, try writing a sample procedure with UTL_FILE to create a file at this location and capture the error. It will give you more details about the problem.

Create a dictionary managed tablespace error.

Similar Messages

Maybe you are looking for