On Fri, 16 May 2003 18:25:27 -0700, Teresa wrote:
> Hello all
>
> I have a oracle database v8174 running on a solaris 5.8 64bit, Iwas
> creating a tablespace then I got the following error message:
>
> "ORA-00059: MAXIMUM NUMBER OF DB_FILES exceeded"
>
> I have made a query to the database to v$controlfile_record_section
> and is showing that
> my record size is 180, records used 200 and total records 215 on the
> datafile site. ALso I have viewed the database creation script and
> there is not maxfiles parameter, which to my knowledge means that
> oracle is taking the default 200? My question is if I change the
> init.ora to db_files = 1000, then restart oracle is there anything
> else at OS level that I should be looking into? I'm really worried
> about this, if I change the init.ora and if oracle does not came
> up.... or something else
>
> I would really apreciate any help
> Thanks
> Teresa
You should do something like
ALTER DATABASE BACKUP CONTROLFILE TO TRACE;
then go to your USER_DUMP_DEST and take a look at the control file,
edit it appropriately and re-create it with 8192 "MAXDATAFILES".
Here is what the resulting file looks like:
/oracle/admin/o9i/udump/o9i_ora_2521.trc
Oracle9i Enterprise Edition Release 9.2.0.3.0 - Production
With the Partitioning option
JServer Release 9.2.0.3.0 - Production
ORACLE_HOME = /oracle/product/9.2.0
System name: Linux
Node name: medo.adelphia.net
Release: 2.4.20
Version: #5 Sun Apr 27 02:16:17 EDT 2003
Machine: i686
Instance name: o9i
Redo thread mounted by this instance: 1
Oracle process number: 13
Unix process pid: 2521, image: oracle_at_medo.adelphia.net (TNS V1-V3)
- SESSION ID:(11.11) 2003-05-17 01:52:30.242
- 2003-05-17 01:52:30.242
# The following are current System-scope REDO Log Archival related
# parameters and can be included in the database initialization file.
#
# LOG_ARCHIVE_DEST=''
# LOG_ARCHIVE_DUPLEX_DEST=''
#
# LOG_ARCHIVE_FORMAT=%t_%s.dbf
# REMOTE_ARCHIVE_ENABLE=TRUE
# LOG_ARCHIVE_MAX_PROCESSES=2
# STANDBY_FILE_MANAGEMENT=MANUAL
# STANDBY_ARCHIVE_DEST=?/dbs/arch
# FAL_CLIENT=''
# FAL_SERVER=''
#
# LOG_ARCHIVE_DEST_1='LOCATION=/oracle/product/9.2.0/dbs/arch'
# LOG_ARCHIVE_DEST_1='MANDATORY NOREOPEN NODELAY'
# LOG_ARCHIVE_DEST_1='ARCH NOAFFIRM SYNC'
# LOG_ARCHIVE_DEST_1='NOREGISTER NOALTERNATE NODEPENDENCY'
# LOG_ARCHIVE_DEST_1='NOMAX_FAILURE NOQUOTA_SIZE NOQUOTA_USED'
# LOG_ARCHIVE_DEST_STATE_1=ENABLE
#
# Below are two sets of SQL statements, each of which creates a new
# control file and uses it to open the database. The first set opens
# the database with the NORESETLOGS option and should be used only if
# the current versions of all online logs are available. The second
# set opens the database with the RESETLOGS option and should be used
# if online logs are unavailable.
# The appropriate set of statements can be copied from the trace into
# a script file, edited as necessary, and executed when there is a
# need to re-create the control file.
#
# Set #1. NORESETLOGS case
#
# The following commands will create a new control file and use it
# to open the database.
# Data used by the recovery manager will be lost. Additional logs may
# be required for media recovery of offline data files. Use this
# only if the current version of all online logs are available.
STARTUP NOMOUNT
CREATE CONTROLFILE REUSE DATABASE "O9I" NORESETLOGS NOARCHIVELOG
-- SET STANDBY TO MAXIMIZE PERFORMANCE
MAXLOGFILES 5
MAXLOGMEMBERS 3
MAXDATAFILES 100
MAXINSTANCES 1
MAXLOGHISTORY 226
LOGFILE
GROUP 1 '/data/oradata/redo/redo01.rdo' SIZE 16M,
GROUP 2 '/data/oradata/redo/redo02.rdo' SIZE 16M,
GROUP 3 '/data/oradata/redo/redo03.rdo' SIZE 16M
-- STANDBY LOGFILE
DATAFILE
'/data/oradata/system/system01.dbf',
'/data/oradata/system/undotbs01.dbf',
'/data/oradata/system/drsys01.dbf',
'/data/oradata/data/example01.dbf',
'/data/oradata/data/indx01.dbf',
'/data/oradata/data/tools01.dbf',
'/data/oradata/data/users01.dbf',
'/data/oradata/data/xdb01.dbf'
CHARACTER SET WE8ISO8859P1
;
# Recovery is required if any of the datafiles are restored backups,
# or if the last shutdown was not normal or immediate.
RECOVER DATABASE
# Database can now be opened normally.
ALTER DATABASE OPEN;
# Commands to add tempfiles to temporary tablespaces.
# Online tempfiles have complete space information.
# Other tempfiles may require adjustment.
ALTER TABLESPACE TEMP ADD TEMPFILE '/data/oradata/system/temp01.dbf'
SIZE 67108864 REUSE AUTOEXTEND ON NEXT 67108864 MAXSIZE 32767M;
# End of tempfile additions.
#
# Set #2. RESETLOGS case
#
# The following commands will create a new control file and use it
# to open the database.
# The contents of online logs will be lost and all backups will
# be invalidated. Use this only if online logs are damaged.
STARTUP NOMOUNT
CREATE CONTROLFILE REUSE DATABASE "O9I" RESETLOGS NOARCHIVELOG
-- SET STANDBY TO MAXIMIZE PERFORMANCE
MAXLOGFILES 5
MAXLOGMEMBERS 3
MAXDATAFILES 100
MAXINSTANCES 1
MAXLOGHISTORY 226
LOGFILE
GROUP 1 '/data/oradata/redo/redo01.rdo' SIZE 16M,
GROUP 2 '/data/oradata/redo/redo02.rdo' SIZE 16M,
GROUP 3 '/data/oradata/redo/redo03.rdo' SIZE 16M
-- STANDBY LOGFILE
DATAFILE
'/data/oradata/system/system01.dbf',
'/data/oradata/system/undotbs01.dbf',
'/data/oradata/system/drsys01.dbf',
'/data/oradata/data/example01.dbf',
'/data/oradata/data/indx01.dbf',
'/data/oradata/data/tools01.dbf',
'/data/oradata/data/users01.dbf',
'/data/oradata/data/xdb01.dbf'
CHARACTER SET WE8ISO8859P1
;
# Recovery is required if any of the datafiles are restored backups,
# or if the last shutdown was not normal or immediate.
RECOVER DATABASE USING BACKUP CONTROLFILE
# Database can now be opened zeroing the online logs.
ALTER DATABASE OPEN RESETLOGS;
# Commands to add tempfiles to temporary tablespaces.
# Online tempfiles have complete space information.
# Other tempfiles may require adjustment.
ALTER TABLESPACE TEMP ADD TEMPFILE '/data/oradata/system/temp01.dbf'
SIZE 67108864 REUSE AUTOEXTEND ON NEXT 67108864 MAXSIZE 32767M;
# End of tempfile additions.
--
Mladen Gogala
Software is like sex, it is better when it is free.
Linus Torvalds
Received on Sat May 17 2003 - 00:56:21 CDT
