Creating tablespace,datafiles,logfiles, controlfiles etc on ASM

What is command to create tablespace,datafiles,logfiles, controlfiles etc on ASM disk group? Send me few example sql commands plz.

You might find Chapter 12 of the Administrators Guide to be some help in understanding ASM. The chapter has many examples.
http://download-east.oracle.com/docs/cd/B19306_01/server.102/b14231/storeman.htm#i1021337

Similar Messages

Process that creates tablespaces

Hi,
I wondered, and guessing, it is the server process that creates (create, and format) tablespaces & datafiles, logfiles, standby-log-files, standby control-files? Am I correct?
I am trying to google it out for myself, but... :)
Thanks in advance.

805683 wrote:
Hi aswin,
FMON is the process that deals with the changes to the datafiles.805683 -
What you copied from the Database Administrator Guide is correct. Unfortunately it is not relevant to the question posed by the OP.
FMON is used to manage the mapping between tablespace blocks and other database files to the actual device. For regular file systems and simple disks, the mapping is pretty simple and FMON is not required. When interfacing to EMC frames and the like, the mapping can be important and can be a critical tool in troubleshooting. This is discussed in the DBA Guide a few paragraphs before the part you copied.
aswin -
The server process operating on behalf of dbca or sqlplus that is used to create the database will be responsible for initiating the creation of the log files, control files, alert log, data files and everything else. However, the server process will probably not be the one to create the files. Instead, it will flag requirements and other processes will likely be the ones to carry out the operations in response to the request. This can be checked on Linux/Unix with tools like truss.
For example, log file management (switch into & create if missing), archive log file management and creation, etc. will occur even if there is no user attached and therefore no server process.
Most of the database file (dbfile) management (such as creating a new datafile for a tablespace) is initiated by the server process attached to the client used by a DBA. However, auto-extending a datafile does not require a DBA to be connected, although it is always(1) in response to an action requested by a client and therefore the clients server process.
Control file and data file header management are delegated to other processes, such as checkpoint process.
((1) never say never, never say always .... there can be exceptions.)
I would be interested in knowing why you care about this level of detail. It is not relevant to any tuning or DBA activity that I can foresee at this time but you may have other insight.

RMAN duplicate target database for standby from active fails to create newname for system tablespace/datafile

When executing 'duplicate target database for standby from active' the system tablespace/datafile (datafile 1) is not cloned. All other datafiles clone successfully. The RMAN process aborts with the following errors while attempting to clone the system tablespace/datafile.
ORA-19558: error de-allocating device
ORA-19557: device error, device type: DISK, device name:
ORA-17627: ORA-01041: internal error. hostdef extension doesn't exist
ORA-17627: ORA-01041: internal error. hostdef extension doesn't exist
ORA-03135: connection lost contact
Here are the details:
Primary is 11.2.0.2 RAC database on an Exadata platform
Standby is 11.2.0.2 Single Instance database (same patch level as primary) on a Red Hat Linux box
This is an ASM to ASM duplication.
This is not unique to this database. We tried another database and go the same behavior - all datafiles clone successfully with the exception of the system tablespace/datafile.
We have traced the RMAN execution and it seems to fail when it is trying to assign a NEWNAME to the system tablespace/datafile.
We even issued an explicit SET NEWNAME command but RMAN ignored it.
We also shutdown the primary and started is up in mount mode thinking that something had ahold of the System Tablespace/datafile.
We also opened up the network firewall to allow permit any,any traffic.
We increased the max_server_processes
and added TCP.NODELAY=yes to the sqlnet.ora file.
There seems to be some artifact present in our Primary System tablespace/data file that is preventing it form being cloned.
checked all alert files grid, asm, and dbhome - no abnormal messages.
We are in the process of restoring the database from a backup but we would prefer to get this working using the 'Active Database' methodology

I successfully created the standby database using RMAN backup and recovery.
I started the managed recovery. Archive logs are being sent from the primary to the standby ( I can see them in ASM), but the standby is not applying them.
I get the following messages in the standby alert log...
Fetching gap sequence in thread 2, gap sequence 154158-154257
Tue Nov 26 16:19:58 2013
Using STANDBY_ARCHIVE_DEST parameter default value as USE_DB_RECOVERY_FILE_DEST
Using STANDBY_ARCHIVE_DEST parameter default value as USE_DB_RECOVERY_FILE_DEST
Tue Nov 26 16:20:01 2013
Fetching gap sequence in thread 2, gap sequence 154158-154257
Tue Nov 26 16:20:11 2013
Fetching gap sequence in thread 2, gap sequence 154158-154257
Tue Nov 26 16:20:22 2013
Fetching gap sequence in thread 2, gap sequence 154158-154257
Tue Nov 26 16:20:32 2013
Fetching gap sequence in thread 2, gap sequence 154158-154257
I don't see any MRP processes:
select process,
status,
    thread#,
    sequence#,
   block#,
blocks
7     from v$managed_standby;
PROCESS   STATUS          THREAD# SEQUENCE#     BLOCK#     BLOCKS
ARCH      CLOSING               2     154363          1        132
ARCH      CONNECTED             0          0          0          0
ARCH      CONNECTED             0          0          0          0
ARCH      CONNECTED             0          0          0          0
ARCH      CONNECTED             0          0          0          0
ARCH      CONNECTED             0          0          0          0
ARCH      CONNECTED             0          0          0          0
ARCH      CONNECTED             0          0          0          0
RFS       IDLE                  0          0          0          0
RFS       IDLE                  1     145418        121          1
RFS       IDLE                  0          0          0          0
PROCESS   STATUS          THREAD# SEQUENCE#     BLOCK#     BLOCKS
RFS       IDLE                  0          0          0          0
12 rows selected.
SQL> SELECT THREAD#, SEQUENCE#, APPLIED FROM V$ARCHIVED_LOG;
   THREAD# SEQUENCE# APPLIED
         2     154356 NO
         2     154357 NO
         1     145411 NO
         2     154358 NO
         2     154360 NO
         2     154361 NO
         1     145414 NO
         1     145415 NO
         2     154362 NO
         2     154363 NO
         1     145416 NO
11 rows selected.
I do have the archive logs that cover sequences 154158-154257
Crosschecked 38 objects
Crosschecked 62 objects
Finished implicit crosscheck backup at 26-NOV-13
Starting implicit crosscheck copy at 26-NOV-13
using channel ORA_DISK_1
using channel ORA_DISK_2
Crosschecked 2 objects
archived log file name=+RECO_XORA/nmuasb00/archivelog/2013_11_26/thread_2_seq_154377.344.832521989 RECID=29 STAMP=832521990
validation succeeded for archived log
archived log file name=+RECO_XORA/nmuasb00/archivelog/2013_11_26/thread_2_seq_154378.346.832521991 RECID=31 STAMP=832521993
Crosschecked 31 objects

Create tablespace error on ASM

SQL> CREATE TABLESPACE "SYS-AUDIT_D1"
2 DATAFILE '+DATA/LUCMT/SYS_AUDIT';
CREATE TABLESPACE "SYS-AUDIT_D1"
ERROR at line 1:
ORA-01119: error in creating database file '+DATA/LUCMT/SYS_AUDIT'
ORA-17502: ksfdcre:3 Failed to create file +DATA/LUCMT/SYS_AUDIT
ORA-15173: entry 'SYS_AUDIT' does not exist in directory 'LUCMT'
ANY IDEA?
thnx in advance

bcm@bcm-laptop:~$ oerr ora 15173
15173, 00000, "entry '%s' does not exist in directory '%s'"
// *Cause: The specified alias did not exist in the given directory.
// *Action: Correct the alias path and try again.
bcm@bcm-laptop:~$ oerr ora 17502
17502, 00000, "ksfdcre:%s Failed to create file %s"
// *Cause: file creation failed due to either insufficient OS permission or
// the file already exists
// *Action: check additional error messages
bcm@bcm-laptop:~$ oerr ora 1119
01119, 00000, "error in creating database file '%s'"
// *Cause: Usually due to not having enough space on the device.
// *Action:

Create tablespace with extend, etc.

Hi guys,
I am typing the following commands bellow: (ORACLE_HOME and ORACLE_SID is set up correctly).
#sqlplus sys/<sys-password> as sysdba ==> worked very well, of course !
SQL> create tablespace imm datafile $ORACLE_HOME/oradata/$ORACLE_SID/imm01.dbf size 100M autoextend on next 100M;
ERROR at line 1:
ORA-01034: ORACLE not available
I have the below scripts set up correctly. Any one know how can I solve this problem ?!
Any help is appreciate !
# dbstart
SQL*Plus: Release 9.2.0.1.0 - Production on Fri Apr 7 16:46:24 2006
Copyright (c) 1982, 2002, Oracle Corporation. All rights reserved.
SQL> Connected to an idle instance.
SQL> ORACLE instance started.
Total System Global Area 672223892 bytes
Fixed Size 455316 bytes
Variable Size 268435456 bytes
Database Buffers 402653184 bytes
Redo Buffers 679936 bytes
Database mounted.
Database opened.
SQL> Disconnected from Oracle9i Release 9.2.0.1.0 - Production
JServer Release 9.2.0.1.0 - Production
Database "immdb" warm started.
# lsnrctl start
LSNRCTL for Solaris: Version 9.2.0.1.0 - Production on 07-APR-2006 16:46:46
Copyright (c) 1991, 2002, Oracle Corporation. All rights reserved.
Starting /apps/oracle/OraHome//bin/tnslsnr: please wait...
TNSLSNR for Solaris: Version 9.2.0.1.0 - Production
System parameter file is /apps/oracle/OraHome/network/admin/listener.ora
Log messages written to /apps/oracle/OraHome/network/log/listener.log
Listening on: (DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(KEY=EXTPROC)))
Listening on: (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=gama2)(PORT=1521)))
Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=IPC)(KEY=EXTPROC)))
STATUS of the LISTENER
Alias LISTENER
Version TNSLSNR for Solaris: Version 9.2.0.1.0 - Production
Start Date 07-APR-2006 16:46:46
Uptime 0 days 0 hr. 0 min. 0 sec
Trace Level off
Security OFF
SNMP OFF
Listener Parameter File /apps/oracle/OraHome/network/admin/listener.ora
Listener Log File /apps/oracle/OraHome/network/log/listener.log
Listening Endpoints Summary...
(DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(KEY=EXTPROC)))
(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=gama2)(PORT=1521)))
Services Summary...
Service "PLSExtProc" has 1 instance(s).
Instance "PLSExtProc", status UNKNOWN, has 1 handler(s) for this service...
Service "immdb.gama2" has 1 instance(s).
Instance "immdb", status UNKNOWN, has 1 handler(s) for this service...
Service "oradb.gama2" has 1 instance(s).
Instance "oradb", status UNKNOWN, has 1 handler(s) for this service...
The command completed successfully
Cheers,
Murilo

Can i perhaps add Operating system environment variable to DATAFILE value somehow? I don't want to create tablespace with full file path, starting from drive name and ending with file name.You can use variables in dbca when you create a database (I already can hear you say you don't want that)
You can also use Oracle Managed Files for the entire database ( I already can hear you say you don't want that)
You can not use relative paths, which begs the question why you don't want to use an absolute path, assuming you seldomly create a tablespace.
I don't want to see posts like yours with unjustified 'complaints', yet I do respond to it.
Sybrand Bakker
Senior Oracle DBA

How to add more than one datafile while creating tablespace

how to add more than one datafile while creating tablespace. I know by using alter command i can add datafile but i want while creating tablespace

Hi Dadivela,
how to add more than one datafile while creating tablespace.Here is the syntax:
!http://www.dba-oracle.com/images/create_tablespace.jpg!
I do it like this:
create tablespace myts
datafile
*'/u01/app/oracle/db1.dbf' size 100m,*
*'/u02/app/oracle/db2.dbf' size 200m;*
Here are my complete notes:
http://www.dba-oracle.com/t_tablespace_create_alter.htm
Hope this answers your question . . .
Donald K. Burleosn
Oracle Press author

CREATE TABLESPACES

i need your advise:
is advisable to create tablespaces on folder where it is database file as (redo, system, controlfiles) or is better to create a folder on other disk for creating tablespaces.
thanks..

The whole concept of dealing with datafiles, controlfiles & logfiles on the disk layer is a little outdated, in my view.
On a very small system - you have just 2 drives - then yes: It is important to use a separate drive to store your backups & archivelogs and to put your mirrored controlfiles & logfile members on. In other words: one drive for the Recovery Area. The other drive is for the Database Area.
For a database of significant size and/or with I/O Performance critical, you will use as many drives as you can get and Stripe And Mirror Everything (SAME) upon those drives - with 2 ASM diskgroups (One Database Area, one Recovery Area) preferrable. ASM is the technical Implementation of the SAME concept.
Kind regards
Uwe Hesse
http://uhesse.wordpress.com

Ora-1276 cannot add controlfile - rman duplicate asm database

Hi,
I am trying to duplicate an asm database olddb -> asm database dup in the same diskgroup. somehow got error 0ra-1276 Cannot add file +DISK1/dup/controlfile/current.1669.754164181. File has an Oracle Managed Files file name.
There is nothing in the asm directory +DISK1/dup/controllfile before I run the rman.
in the initdup.ora
control_files=+DISK1,+DISK1 <--- just the disk group, not the file name
db_name='dup'
db_file_name_convert=+DISK1,+DISK1/dup
log_file_name_convert=+DISK1,+DISK1
Recovery Manager: Release 10.2.0.5.0 - Production on Sat Jun 18 20:58:06 2011
Copyright (c) 1982, 2007, Oracle. All rights reserved.
RMAN> connect target sys/oracle@OLDDB
connect auconnected to target database: OLDDB (DBID=1142960293)
RMAN> xiliary /
connected to auxiliary database: DUP (not mounted)
RMAN> duplicate target database to dup
logfile group 1 ('+DISK1/dup') size 200k ,
group 2 ('+DISK1') size 200k;
2> 3>
Starting Duplicate Db at 2011/06/18 20:58:39
using target database control file instead of recovery catalog
allocated channel: ORA_AUX_DISK_1
channel ORA_AUX_DISK_1: sid=153 devtype=DISK
WARNING: DB_FILE_NAME_CONVERT resulted in invalid ASM names; names changed to diskgroup only.
contents of Memory Script:
set until scn 1613638;
set newname for datafile 1 to
"+DISK1";
set newname for datafile 2 to
"+DISK1";
set newname for datafile 3 to
"+DISK1";
set newname for datafile 4 to
"+DISK1";
set newname for datafile 6 to
"+DISK1";
restore
check readonly
clone database
executing Memory Script
executing command: SET until clause
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
Starting restore at 2011/06/18 20:58:42
using channel ORA_AUX_DISK_1
channel ORA_AUX_DISK_1: starting datafile backupset restore
channel ORA_AUX_DISK_1: specifying datafile(s) to restore from backup set
restoring datafile 00001 to +DISK1
restoring datafile 00002 to +DISK1
restoring datafile 00003 to +DISK1
restoring datafile 00004 to +DISK1
restoring datafile 00006 to +DISK1
channel ORA_AUX_DISK_1: reading from backup piece +DISK1/OLDDB/backupset/2011_05_22/nnndf0_tag20110522t000530_0.1691.751766731
channel ORA_AUX_DISK_1: restored backup piece 1
piece handle=+DISK1/OLDDB/backupset/2011_05_22/nnndf0_tag20110522t000530_0.1691.751766731 tag=TAG20110522T000530
channel ORA_AUX_DISK_1: restore complete, elapsed time: 00:01:06
Finished restore at 2011/06/18 20:59:48
sql statement: CREATE CONTROLFILE REUSE SET DATABASE "DUP" RESETLOGS ARCHIVELOG
MAXLOGFILES 192
MAXLOGMEMBERS 3
MAXDATAFILES 1024
MAXINSTANCES 32
MAXLOGHISTORY 292
LOGFILE
GROUP 1 ( '+DISK1/dup' ) SIZE 200 K ,
GROUP 2 ( '+DISK1' ) SIZE 200 K
DATAFILE
'+DISK1/dup/datafile/system.1674.754174727'
CHARACTER SET WE8ISO8859P1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of Duplicate Db command at 06/18/2011 20:59:48
RMAN-06136: ORACLE error from auxiliary database: ORA-01503: CREATE CONTROLFILE failed
ORA-01276: Cannot add file +DISK1/dup/controlfile/current.1669.754164181. File has an Oracle Managed Files file name.
RMAN>
thank you very much for your help.
thanks
andrew

RMAN-06136: ORACLE error from auxiliary database: ORA-01503: CREATE CONTROLFILE failed
ORA-01276: Cannot add file +DISK1/dup/controlfile/current.1669.754164181. File has an Oracle Managed Files file name.Are you sure is it running under pfile?
Ok, connect to auxiliary intance and post
show parameter db_create
show parameter control_filesIn your pfile, Have you mentioned single quotes?
If your database with OMF then if you give it as below. as there is some work around
Control_files='+DISK1/DUP/controlfile/control01.ctl','+DISK1/DUP/controlfile/control02.ctl'
Check this too *Ora-1276 Error Recreating The Controlfile When Using +Asm [ID 303187.1]*

ORA-15005 when creating tablespaces

Database oracle 10g
OS Redhat EL4
Using RAC and +ASM
Hi
I created a load of tablespaces with specific datafiles.
create tablespace whatever datafile '+DATA01/etc/etc.dbf' size 100M
I then realised I had mixed up all the datafile names so dropped them all
drop tablespace whatever;
After this I fixed up the naming and tried to recreate the tablespaces but get the following error
ORA-01119: error in creating database file '+DATA01/etc
ORA-15005: name etc/etc is already used by an existing alias
Any ideas how I get rid of these so I can start again?
Thanks for help in advance

Hi,
you should drop the alias first.
ALTER DISKGROUP dgroup# DROP FILE '+dgroup/etc/etc.dbf';
dBarak.
Message was edited by:
dBarak

Create new DataFile in another partition??

Hi,
I used database oracle10g, and I set (oradata) in partition (C) and i want to load large data on database but i haven't enough space in this partition .
Can I create new DataFile in another partition like partition (D) ???
And if yes, will it effect in the Performance the Database ???
Thank For Replay

user12254348 wrote:
Hi,
I used database oracle10g, and I set (oradata) in partition (C) and i want to load large data on database but i haven't enough space in this partition .
Can I create new DataFile in another partition like partition (D) ???
And if yes, will it effect in the Performance the Database ???
Thank For ReplayDepends on a lot of things:
1- D and C are physically separated disks OR there are part of the same physical disk but logically separated ?
2- Where are located your system datafiles, controlfile, logfile, indexes?
3- Are you using ASM?
It depends a lot of your storage and database design.
I suggest you test and compare the performance using AWR reports and view Oracle statistics via the Windows Performance Monitor (perfmon)..

Error During Installation: ORA-02180: invalid option for CREATE TABLESPACE

Hi all,
This is our enviroment,
Windows 2000 Service Pack 4
We are installing SAP R/3 Enterprise 4.7 Ext. 200 SR1
First we installed:
Oracle: 9.2
Patch: 9.2.0.7
SAP Central Instance
Now we are installing the DB Instance, but it gives this error:
INFO 2007-11-22 16:58:20
Working directory changed to C:\Program Files\sapinst_instdir\R3E47X2\SYSTEM\ABAP\ORA\NUC\DB.
ERROR 2007-11-22 16:58:21
CJS-00084 SQL statement or script failed.DIAGNOSIS: Error message: ORA-02180: invalid option for CREATE TABLESPACE
We are in the step 19 of 34
Create Tablespaces
Please some tips.
Regards,
Erick

Hi! Thanks a lot for the reply.
This is our <b>ora_sql_results.log</b>
================================================================================
2007-11-23, 07:31:09 SAPINST ORACLE start logging for
connect / as sysdba ;
set newpage 0
set space 0
set pagesize 0
set linesize 32767
set markup HTML off
set heading off
set verify off
set feedback off
set trimspool on
set sqlprompt SQL>
set termout on
set verify off
set echo off
spool ora_query3_tmp0_1.res
SELECT STATUS FROM V$INSTANCE;
spool off
exit;
Output of SQL executing program:
SQL*Plus: Release 9.2.0.7.0 - Production on Fri Nov 23 07:31:09 2007
Copyright (c) 1982, 2002, Oracle Corporation. All rights reserved.
Connected.
OPEN
Disconnected from Oracle9i Enterprise Edition Release 9.2.0.7.0 - Production
With the Partitioning, OLAP and Oracle Data Mining options
JServer Release 9.2.0.7.0 - Production
SAPINST: End of output of SQL executing program D:\oracle\TVD\920/bin/sqlplus.
2007-11-23, 07:31:10 SAPINST ORACLE stop logging
================================================================================
2007-11-23, 07:31:10 SAPINST ORACLE start logging for
connect / as sysdba ;
CREATE TABLESPACE PSAP@SCHEMAID@ DATAFILE 'E:\oracle\TVD\sapdata4\psap@schemaid@_1\psap@[email protected]' SIZE 2000M REUSE AUTOEXTEND ON NEXT 20M MAXSIZE 10000M LOGGING ONLINE PERMANENT EXTENT MANAGEMENT LOCAL AUTOALLOCATE SEGMENT SPACE MANAGEMENT AUTO ;
exit;
Output of SQL executing program:
SQL*Plus: Release 9.2.0.7.0 - Production on Fri Nov 23 07:31:10 2007
Copyright (c) 1982, 2002, Oracle Corporation. All rights reserved.
Connected.
CREATE TABLESPACE PSAP@SCHEMAID@ DATAFILE 'E:\oracle\TVD\sapdata4\psap@schemaid@_1\psap@[email protected]' SIZE 2000M REUSE AUTOEXTEND     ON NEXT 20M MAXSIZE 10000M LOGGING ONLINE PERMANENT EXTENT MANAGEMENT LOCAL     AUTOALLOCATE SEGMENT SPACE MANAGEMENT AUTO
ERROR at line 1:
ORA-02180: invalid option for CREATE TABLESPACE
Disconnected from Oracle9i Enterprise Edition Release 9.2.0.7.0 - Production
With the Partitioning, OLAP and Oracle Data Mining options
JServer Release 9.2.0.7.0 - Production
SAPINST: End of output of SQL executing program D:\oracle\TVD\920/bin/sqlplus.
SAPINST found errors.
SAPINST The current process environment may be found in sapinst_ora_environment.log.
2007-11-23, 07:31:10 SAPINST ORACLE stop logging
And this is <b>our alert_SID.log</b>
Dump file d:\oracle\tvd\saptrace\background\alert_tvd.log
Thu Nov 22 16:27:45 2007
ORACLE V9.2.0.7.0 - Production vsnsta=0
vsnsql=12 vsnxtr=3
Windows 2000 Version 5.0 Service Pack 4, CPU type 586
Thu Nov 22 16:27:45 2007
Starting ORACLE instance (normal)
LICENSE_MAX_SESSION = 0
LICENSE_SESSIONS_WARNING = 0
SCN scheme 2
LICENSE_MAX_USERS = 0
SYS auditing is disabled
Starting up ORACLE RDBMS Version: 9.2.0.7.0.
System parameters with non-default values:
processes                = 80
sessions                 = 96
shared_pool_size         = 251658240
sga_max_size             = 546906620
shared_pool_reserved_size= 24363663
enqueue_resources        = 8000
control_files            = E:\oracle\TVD\origlogA\cntrl\cntrlTVD.dbf, E:\oracle\TVD\sapdata1\system_1\cntrl\cntrlTVD.dbf, D:\oracle\TVD\saparch\cntrl\cntrlTVD.dbf
db_block_size            = 8192
db_cache_size            = 251658240
compatible               = 9.2.0
log_archive_start        = TRUE
log_archive_dest         = D:\oracle\TVD\oraarch\TVDarch
log_buffer               = 1048576
log_checkpoint_interval = 0
db_files                 = 254
fast_start_mttr_target   = 900
log_checkpoints_to_alert = TRUE
control_file_record_keep_time= 30
dml_locks                = 4000
transaction_auditing     = FALSE
undo_management          = AUTO
undo_tablespace          = PSAPUNDO
undo_retention           = 43200
remote_os_authent        = TRUE
hash_join_enabled        = FALSE
background_dump_dest     = D:\oracle\TVD\saptrace\background
user_dump_dest           = D:\oracle\TVD\saptrace\usertrace
core_dump_dest           = D:\oracle\TVD\saptrace\background
optimizer_features_enable= 9.2.0
sort_area_size           = 2097152
sort_area_retained_size = 0
db_name                  = TVD
open_cursors             = 800
pga_aggregate_target     = 324848844
workarea_size_policy     = AUTO
statistics_level         = typical
PMON started with pid=2
DBW0 started with pid=3
LGWR started with pid=4
CKPT started with pid=5
SMON started with pid=6
RECO started with pid=7
Thu Nov 22 16:27:48 2007
ARCH: STARTING ARCH PROCESSES
ARC0 started with pid=8
ARC1 started with pid=9
Thu Nov 22 16:27:48 2007
ARC0: Archival started
Thu Nov 22 16:27:48 2007
ARCH: STARTING ARCH PROCESSES COMPLETE
Thu Nov 22 16:27:48 2007
ARC1: Archival started
Thu Nov 22 16:27:48 2007
ARC0: Becoming the 'no FAL' ARCH
Thu Nov 22 16:27:48 2007
ARC1: Becoming the heartbeat ARCH
Thu Nov 22 16:27:48 2007
ARC0: Becoming the 'no FAL' ARCHARC0: Thread not mounted
Thu Nov 22 16:27:48 2007
ARC1: Becoming the heartbeat ARCHARC1: Thread not mounted
Thu Nov 22 16:27:49 2007
alter database mount exclusive
Thu Nov 22 16:27:49 2007
ORA-00202: controlfile: 'E:\oracle\TVD\origlogA\cntrl\cntrlTVD.dbf'
ORA-27041: unable to open file
OSD-04002: unable to open file
O/S-Error: (OS 2) The system cannot find the file specified.
Thu Nov 22 16:27:50 2007
ORA-205 signalled during: alter database mount exclusive...
Shutting down instance (abort)
License high water mark = 1
Instance terminated by USER, pid = 1768
Thu Nov 22 16:28:05 2007
Starting ORACLE instance (normal)
LICENSE_MAX_SESSION = 0
LICENSE_SESSIONS_WARNING = 0
SCN scheme 2
LICENSE_MAX_USERS = 0
SYS auditing is disabled
Starting up ORACLE RDBMS Version: 9.2.0.7.0.
System parameters with non-default values:
processes                = 80
sessions                 = 96
shared_pool_size         = 251658240
sga_max_size             = 546906620
shared_pool_reserved_size= 24363663
enqueue_resources        = 8000
control_files            = E:\oracle\TVD\origlogA\cntrl\cntrlTVD.dbf, E:\oracle\TVD\sapdata1\system_1\cntrl\cntrlTVD.dbf, D:\oracle\TVD\saparch\cntrl\cntrlTVD.dbf
db_block_size            = 8192
db_cache_size            = 251658240
compatible               = 9.2.0
log_archive_start        = TRUE
log_archive_dest         = D:\oracle\TVD\oraarch\TVDarch
log_buffer               = 1048576
log_checkpoint_interval = 0
db_files                 = 254
fast_start_mttr_target   = 900
log_checkpoints_to_alert = TRUE
control_file_record_keep_time= 30
dml_locks                = 4000
transaction_auditing     = FALSE
undo_management          = AUTO
undo_tablespace          = PSAPUNDO
undo_retention           = 43200
remote_os_authent        = TRUE
hash_join_enabled        = FALSE
background_dump_dest     = D:\oracle\TVD\saptrace\background
user_dump_dest           = D:\oracle\TVD\saptrace\usertrace
core_dump_dest           = D:\oracle\TVD\saptrace\background
optimizer_features_enable= 9.2.0
sort_area_size           = 2097152
sort_area_retained_size = 0
db_name                  = TVD
open_cursors             = 800
pga_aggregate_target     = 324848844
workarea_size_policy     = AUTO
statistics_level         = typical
PMON started with pid=2
DBW0 started with pid=3
LGWR started with pid=4
CKPT started with pid=5
SMON started with pid=6
RECO started with pid=7
Thu Nov 22 16:28:08 2007
ARCH: STARTING ARCH PROCESSES
ARC0 started with pid=8
ARC0: Archival started
ARC1 started with pid=9
Thu Nov 22 16:28:08 2007
ARCH: STARTING ARCH PROCESSES COMPLETE
Thu Nov 22 16:28:08 2007
ARC0: Becoming the 'no FAL' ARCH
ARC0: Becoming the 'no FAL' ARCHARC0: Thread not mounted
Thu Nov 22 16:28:09 2007
ARC1: Archival started
Thu Nov 22 16:28:09 2007
ARC1: Becoming the heartbeat ARCH
ARC1: Becoming the heartbeat ARCHARC1: Thread not mounted
Thu Nov 22 16:28:11 2007
CREATE DATABASE TVD CONTROLFILE REUSE MAXLOGFILES 255 MAXLOGMEMBERS 3 MAXLOGHISTORY 1000 MAXDATAFILES 254 MAXINSTANCES 50 NOARCHIVELOG CHARACTER SET WE8DEC NATIONAL CHARACTER SET UTF8 DATAFILE 'E:\oracle\TVD\sapdata1\system_1\system.data1' SIZE 550M REUSE AUTOEXTEND ON NEXT 20M MAXSIZE 10000M EXTENT MANAGEMENT LOCAL DEFAULT TEMPORARY TABLESPACE PSAPTEMP TEMPFILE 'E:\oracle\TVD\sapdata3\temp_1\temp.data1' SIZE 540M REUSE AUTOEXTEND ON NEXT 20M MAXSIZE 10000M UNDO TABLESPACE PSAPUNDO DATAFILE 'E:\oracle\TVD\sapdata2\undo_1\undo.data1' SIZE 700M REUSE AUTOEXTEND ON NEXT 20M MAXSIZE 10000M
LOGFILE GROUP 1 ('E:
oracle/TVD/origlogA/log_g11m1.dbf',
'D:
oracle/TVD/mirrlogA/log_g11m2.dbf') SIZE 50M REUSE ,
GROUP 2 ('E:
oracle/TVD/origlogB/log_g12m1.dbf',
'D:
oracle/TVD/mirrlogB/log_g12m2.dbf') SIZE 50M REUSE ,
GROUP 3 ('E:
oracle/TVD/origlogA/log_g13m1.dbf',
'D:
oracle/TVD/mirrlogA/log_g13m2.dbf') SIZE 50M REUSE ,
GROUP 4 ('E:
oracle/TVD/origlogB/log_g14m1.dbf',
'D:
oracle/TVD/mirrlogB/log_g14m2.dbf') SIZE 50M REUSE
Thu Nov 22 16:28:12 2007
Database mounted in Exclusive Mode.
Thu Nov 22 16:28:29 2007
Successful mount of redo thread 1, with mount id 1434613531
Assigning activation ID 1434613531 (0x5582771b)
Thread 1 opened at log sequence 1
Thu Nov 22 16:28:30 2007
ARC1: Media recovery disabled
Thu Nov 22 16:28:31 2007
Current log# 1 seq# 1 mem# 0: E:\ORACLE\TVD\ORIGLOGA\LOG_G11M1.DBF
Current log# 1 seq# 1 mem# 1: D:\ORACLE\TVD\MIRRLOGA\LOG_G11M2.DBF
Successful open of redo thread 1
Thu Nov 22 16:28:31 2007
ARC0: Media recovery disabled
Thu Nov 22 16:28:31 2007
SMON: enabling cache recovery
Thu Nov 22 16:28:32 2007
WARNING: Default passwords for SYS and SYSTEM will be used.
         Please change the passwords.
Thu Nov 22 16:28:32 2007
create tablespace SYSTEM datafile 'E:\oracle\TVD\sapdata1\system_1\system.data1' SIZE 550M REUSE AUTOEXTEND ON NEXT 20M MAXSIZE 10000M
EXTENT MANAGEMENT LOCAL online
Thu Nov 22 16:28:51 2007
Completed: create tablespace SYSTEM datafile 'E:\oracle\TVD\
Thu Nov 22 16:28:51 2007
create rollback segment SYSTEM tablespace SYSTEM
storage (initial 50K next 50K)
Completed: create rollback segment SYSTEM tablespace SYSTEM
Thu Nov 22 16:29:08 2007
ARC1: Media recovery disabled
Thu Nov 22 16:29:10 2007
CREATE UNDO TABLESPACE PSAPUNDO DATAFILE 'E:\oracle\TVD\sapdata2\undo_1\undo.data1' SIZE 700M REUSE AUTOEXTEND ON NEXT 20M MAXSIZE 10000M
Thu Nov 22 16:29:35 2007
Successfully onlined Undo Tablespace 1.
Completed: CREATE UNDO TABLESPACE PSAPUNDO DATAFILE 'E:\orac
Thu Nov 22 16:29:36 2007
CREATE TEMPORARY TABLESPACE PSAPTEMP TEMPFILE 'E:\oracle\TVD\sapdata3\temp_1\temp.data1' SIZE 540M REUSE AUTOEXTEND ON NEXT 20M MAXSIZE 10000M
Completed: CREATE TEMPORARY TABLESPACE PSAPTEMP TEMPFILE 'E:
Thu Nov 22 16:29:36 2007
ALTER DATABASE DEFAULT TEMPORARY TABLESPACE PSAPTEMP
Completed: ALTER DATABASE DEFAULT TEMPORARY TABLESPACE PSAPTE
Thu Nov 22 16:29:39 2007
SMON: enabling tx recovery
Thu Nov 22 16:29:39 2007
Beginning local checkpoint up to RBA [0x1.538b.10], SCN: 0x0000.000019d9
Completed checkpoint up to RBA [0x1.538b.10], SCN: 0x0000.000019d9
kwqplbsc: open notifier exception err 604
replication_dependency_tracking turned off (no async multimaster replication found)
Completed: CREATE DATABASE TVD CONTROLFILE REUSE MAXLOGFILES
Thu Nov 22 16:30:08 2007
ARC1: Media recovery disabled
Thu Nov 22 16:31:08 2007
ARC1: Media recovery disabled
Thu Nov 22 16:31:28 2007
Beginning log switch checkpoint up to RBA [0x2.2.10], SCN: 0x0000.00006489
Thread 1 advanced to log sequence 2
Thu Nov 22 16:31:28 2007
ARC1: Media recovery disabled
Thu Nov 22 16:31:29 2007
Current log# 2 seq# 2 mem# 0: E:\ORACLE\TVD\ORIGLOGB\LOG_G12M1.DBF
Current log# 2 seq# 2 mem# 1: D:\ORACLE\TVD\MIRRLOGB\LOG_G12M2.DBF
Thu Nov 22 16:32:08 2007
ARC1: Media recovery disabled
Thu Nov 22 16:33:08 2007
ARC0: Media recovery disabled
Thu Nov 22 16:33:08 2007
ARC1: Media recovery disabled
Thu Nov 22 16:33:16 2007
Completed checkpoint up to RBA [0x2.2.10], SCN: 0x0000.00006489
Thu Nov 22 16:33:26 2007
Beginning log switch checkpoint up to RBA [0x3.2.10], SCN: 0x0000.00009227
Thread 1 advanced to log sequence 3
Thu Nov 22 16:33:26 2007
ARC0: Media recovery disabled
Thu Nov 22 16:33:26 2007
Current log# 3 seq# 3 mem# 0: E:\ORACLE\TVD\ORIGLOGA\LOG_G13M1.DBF
Current log# 3 seq# 3 mem# 1: D:\ORACLE\TVD\MIRRLOGA\LOG_G13M2.DBF
Thu Nov 22 16:34:08 2007
ARC1: Media recovery disabled
Thu Nov 22 16:35:08 2007
ARC1: Media recovery disabled
Thu Nov 22 16:35:19 2007
Completed checkpoint up to RBA [0x3.2.10], SCN: 0x0000.00009227
Thu Nov 22 16:35:28 2007
Beginning log switch checkpoint up to RBA [0x4.2.10], SCN: 0x0000.0000b0ac
Thread 1 advanced to log sequence 4
Current log# 4 seq# 4 mem# 0: E:\ORACLE\TVD\ORIGLOGB\LOG_G14M1.DBF
Thu Nov 22 16:35:28 2007
ARC1: Media recovery disabled
Thu Nov 22 16:35:28 2007
Current log# 4 seq# 4 mem# 1: D:\ORACLE\TVD\MIRRLOGB\LOG_G14M2.DBF
Thu Nov 22 16:36:08 2007
ARC1: Media recovery disabled
Thu Nov 22 16:37:08 2007
ARC1: Media recovery disabled
Thu Nov 22 16:38:08 2007
ARC0: Media recovery disabled
Thu Nov 22 16:38:08 2007
ARC1: Media recovery disabled
Thu Nov 22 16:38:51 2007
Completed checkpoint up to RBA [0x4.2.10], SCN: 0x0000.0000b0ac
Thu Nov 22 16:38:59 2007
Beginning log switch checkpoint up to RBA [0x5.2.10], SCN: 0x0000.0000e12b
Thread 1 advanced to log sequence 5
Thu Nov 22 16:38:59 2007
Current log# 1 seq# 5 mem# 0: E:\ORACLE\TVD\ORIGLOGA\LOG_G11M1.DBF
Current log# 1 seq# 5 mem# 1: D:\ORACLE\TVD\MIRRLOGA\LOG_G11M2.DBF
Thu Nov 22 16:39:00 2007
ARC0: Media recovery disabled
Thu Nov 22 16:39:08 2007
ARC1: Media recovery disabled
Thu Nov 22 16:40:08 2007
ARC1: Media recovery disabled
Thu Nov 22 16:41:08 2007
ARC1: Media recovery disabled
Thu Nov 22 16:41:09 2007
Completed checkpoint up to RBA [0x5.2.10], SCN: 0x0000.0000e12b
Thu Nov 22 16:41:18 2007
Beginning log switch checkpoint up to RBA [0x6.2.10], SCN: 0x0000.0000ee94
Thread 1 advanced to log sequence 6
Current log# 2 seq# 6 mem# 0: E:\ORACLE\TVD\ORIGLOGB\LOG_G12M1.DBF
Current log# 2 seq# 6 mem# 1: D:\ORACLE\TVD\MIRRLOGB\LOG_G12M2.DBF
Thu Nov 22 16:41:18 2007
ARC1: Media recovery disabled
Thu Nov 22 16:42:08 2007
Fri Nov 23 07:38:10 2007
ARC1: Media recovery disabled
Regards,
Erick

CREATING TABLESPACES

hi,
while creating tablespaces is it possible to give create tablespace <tablespace_name>.i dont want to add any datafiles while creating tablespaces...
could anybody tell the syntax.
Thanks in advance,
R.Ratheesh

Use Oracle Managed Files (OMF), OMF simplifies the creation of databases as Oracle does all OS operations and file naming. It has several advantages including:
Automatic cleanup of the filesystem when database objects are dropped.
Standardized naming of database files.
Increased portability since file specifications are not needed.
Simplified creation of test systems on differing operating systems.
No unused files wasting disk space.
The location of database files is defined using the DB_CREATE_FILE_DEST parameter. If it is defined on its own all files are placed in the same location. If the DB_CREATE_ONLINE_LOG_DEST_n parameter is defined alternate locations and levels of multiplexing can be defined for Logfiles. These parameters are dymanic and can be changed using the ALTER SYSTEM statement:
ALTER SYSTEM SET DB_CREATE_FILE_DEST='C:\Oracle\Oradata\TSH1';
Files typically have a default size of 100M and are named using the following formats where u% is a unique 8 digit code, g% is the logfile group number, and %t is the tablespace name:
File Type Format
Controlfiles ora_%u.ctl
Redo Log Files ora_%g_%u.log
Datafiles ora_%t_%u.dbf
Temporary Datafiles ora_%t_%u.tmp
Managing Controlfiles Using OMF
Managing Redo Log Files Using OMF
Managing Tablespaces Using OMF
Default Temporary Tablespace
Managing Controlfiles Using OMF
During database creation the controlfile names are not specified. Instead, a controlfile is created for each DB_CREATE_ONLINE_LOG_DEST_n specified in the init.ora file. Once the database creation is complete the CONTROL_FILES parameter can be set in the init.ora file using the generated names shown in the V$CONTROLFILE view.
Managing Redo Log Files Using OMF
When using OMF for redo logs the DB_CREAT_ONLINE_LOG_DEST_n parameters in the init.ora file decide on the locations and numbers of logfile members. For exmple:
DB_CREATE_ONLINE_LOG_DEST_1 = c:\Oracle\Oradata\TSH1
DB_CREATE_ONLINE_LOG_DEST_2 = d:\Oracle\Oradata\TSH1
The above parameters mean two members will be created for the logfile group in the specified locations when the ALTER DATABASE ADD LOGFILE; statement is issued. Oracle will name the file and increment the group number if they are not specified.
The ALTER DATABASE DROP LOGFILE GROUP 3; statement will remove the group and it members from the database and delete the files at operating system level.
Managing Tablespaces Using OMF
As shown previously the DB_CREATE_FILE_DEST parameter in the init.ora file specifies the location of the datafiles for OMF tablespaces. Since the file location is specified and Oracle will name the file, new tablespaces can be created using the following statement:
CREATE TABLESPACE tsh_data;
The resultant datafiles will have a default size of 100M and AUTOEXTEND UNLIMITED. For a specific size file use:
CREATE TABLESPACE tsh_data DATAFILE SIZE 150M;
To add a datafile to a tablespace use:
ALTER TABLESPACE tsh_data ADD DATAFILE;
If a tablespace is dropped, Oracle will remove the OS files also. For tablespaces not using the OMF feature this cleanup can be performed by issuing the statement:
DROP TABLESPACE tsh_data INCLUDING CONTENTS AND DATAFILES;

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.

Create Tablespace

Hello,
I need some help. I need to create new tablespace in Oracle 10g. Since we are using ASM technology. I can't see the exact path to create tablespace...I query to see the location of the datafile it gave me following path.
+ASMDG1/ORACLE/USERS.DBF
Can you guys help me out to create new tablespace.
REGARDS,

Hi,
I location of datafiles and tablespace as well but it is showing the following path.
+ASMDG1/ORACLE/USERS.DBF . The problem is when i use this path to create tablespace like:
CREATE TABLESPACE CARE
DATAFILE '+ASMDG1/ORACLE/CARE.DBF' SIZE 10G;
It show the error that path doesn't exist.
Can anybody help me out to solve this problem. I tried possible ways but couldn't create tablespace.
Regards

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

Creating tablespace,datafiles,logfiles, controlfiles etc on ASM

Similar Messages

Maybe you are looking for