When starting an Oracle instance, the DB_FILES initialization parameter indicates the amount of SGA space to reserve for datafile information and thus, the maximum number of datafiles that can be created for the instance. This limit applies for the life of the instance. You can change the value of DB_FILES (by changing the initialization parameter setting), but the new value does not take effect until you shut down and restart the instance.
When determining a value for DB_FILES, take the following into consideration:
- If the value of
DB_FILESis too low, you cannot add datafiles beyond theDB_FILESlimit without first shutting down the database. - If the value of
DB_FILESis too high, memory is unnecessarily consumed.
Limitations When Adding Datafiles to a Tablespace
You can add datafiles to tablespaces, subject to the following limitations:
- Operating systems often impose a limit on the number of files a process can open simultaneously. More datafiles cannot be created when the operating system limit of open files is reached.
- Operating systems impose limits on the number and size of datafiles.
- Oracle imposes a maximum limit on the number of datafiles for any Oracle database opened by any instance. This limit is operating system specific.
- You cannot exceed the number of datafiles specified by the
DB_FILESinitialization parameter. - When you issue
CREATE DATABASEorCREATE CONTROLFILEstatements, theMAXDATAFILESparameter specifies an initial size of the datafile portion of the control file. However, if you attempt to add a new file whose number is greater thanMAXDATAFILES, but less than or equal toDB_FILES, the control file will expand automatically so that the datafiles section can accommodate more files.
No comments:
Post a Comment