-
When I execute the CREATE DATABASE statement, I'm getting the following error:
"SQL Statement not properly ended"
Here's my CREATE DATABASE STATEMENT:
CREATE DATABASE CIT
CONTROLFILE REUSE
DATAFILE '/u03/oradata/CIT/CIT_sys1.dbf' SIZE 20M AUTOEXTEND ON NEXT 10M MAXSIZE 150M
EXTENT MANAGEMENT LOCAL UNIFORM SIZE 1M
LOGFILE
GROUP 1 ('/u04/oradata/CIT/CIT_rdo1.rdo',
'/u04/oradata/CIT/CIT_rdo2.rdo') SIZE 2M REUSE,
GROUP 2 ('/u06/oradata/CIT/CIT_rdo3.rdo',
'/u06/oradata/CIT/CIT_rdo4.rdo') SIZE 2M REUSE
MAXLOGFILES 16
MAXDATAFILES 16
MAXLOGMEMBERS 4
CHARACTER SET "WE8DEC"
MAXINSTANCES 1
NOARCHIVELOG
Thanks
-
You have to specify the filesize (2M e.g.) for each file and not for the group.
-
no arshiah.
My problem has to do with the fact that I'm trying to create the SYSTEM tablespace with "EXTENT MANAGEMENT LOCAL SIZE 1M".
I get rid of this line and it work. But I still want to know how to specified this during the database creation.
Thanks.
-
Tablespace SYSTEM is not supported to use local managed tablespaces. It still has to be dictionary managed
-
to pando,
Generally also we don't have much control on SYSTEM tablespace other than resize/increase the tablespace. It creates its own extents by default and what are the issues in modfying system tablespaces extents ? Any Idea ?
-
Hi
you can modify sql.bsq before create the database, in sql.bsq default extent initial, next sizes are defined. Although rumour says that if we modified sql.bsq we have to face the consequences without Oracle support however I have read in metalink suggesting experienced DBAs change sql.bsq... so I dunno what´s true :P
