以下是日志内容：
Thu Apr 10 15:41:30 2014
Starting ORACLE instance (normal)
LICENSE_MAX_SESSION = 0
LICENSE_SESSIONS_WARNING = 0
Initial number of CPU is 24
Number of processor cores in the system is 12
Number of processor sockets in the system is 2
Shared memory segment for instance monitoring created
CELL communication is configured to use 0 interface(s):
CELL IP affinity details:
NUMA status: NUMA system w/ 2 process groups
cellaffinity.ora status: cannot find affinity map at '/etc/oracle/cell/network-config/cellaffinity.ora' (see trace file for details)
CELL communication will use 1 IP group(s):
Grp 0:
Picked latch-free SCN scheme 3
Using LOG_ARCHIVE_DEST_1 parameter default value as USE_DB_RECOVERY_FILE_DEST
WARNING: db_recovery_file_dest is same as db_create_file_dest
Autotune of undo retention is turned on.
IMODE=BR
ILAT =168
LICENSE_MAX_USERS = 0
SYS auditing is disabled
NUMA system with 2 nodes detected
Starting up:
Oracle Database 11g Enterprise Edition Release 11.2.0.4.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options.
ORACLE_HOME = /oracle/database/oracle/product/11.2.0.3/db_1
System name: Linux
Node name: mobile220
Release: 2.6.39-300.17.3.el6uek.x86_64
Version: #1 SMP Wed Dec 19 06:28:03 PST 2012
Machine: x86_64
Using parameter settings in client-side pfile /oracle/database/oracle/admin/mobile/pfile/init.ora on machine mobile220
System parameters with non-default values:
processes = 1000
sessions = 1536
memory_target = 22656M
db_block_size = 32768
compatible = "11.2.0.4.0"
db_create_file_dest = "+DATA"
db_recovery_file_dest = "+DATA"
db_recovery_file_dest_size= 4977M
undo_tablespace = "UNDOTBS1"
remote_login_passwordfile= "EXCLUSIVE"
db_domain = ""
dispatchers = "(PROTOCOL=TCP) (SERVICE=mobileXDB)"
audit_file_dest = "/oracle/database/oracle/admin/mobile/adump"
audit_trail = "DB"
db_name = "mobile"
open_cursors = 300
diagnostic_dest = "/oracle/database/oracle"
Thu Apr 10 15:41:32 2014
PMON started with pid=2, OS id=24893
Thu Apr 10 15:41:32 2014
PSP0 started with pid=3, OS id=24895
Thu Apr 10 15:41:33 2014
VKTM started with pid=4, OS id=24897 at elevated priority
VKTM running at (1)millisec precision with DBRM quantum (100)ms
Thu Apr 10 15:41:33 2014
GEN0 started with pid=5, OS id=24901
Thu Apr 10 15:41:33 2014
DIAG started with pid=6, OS id=24903
Thu Apr 10 15:41:33 2014
DBRM started with pid=7, OS id=24905
Thu Apr 10 15:41:33 2014
DIA0 started with pid=8, OS id=24907
Thu Apr 10 15:41:33 2014
MMAN started with pid=9, OS id=24909
Thu Apr 10 15:41:33 2014
DBW0 started with pid=10, OS id=24911
Thu Apr 10 15:41:33 2014
DBW1 started with pid=11, OS id=24913
Thu Apr 10 15:41:33 2014
DBW2 started with pid=12, OS id=24915
Thu Apr 10 15:41:33 2014
LGWR started with pid=13, OS id=24917
Thu Apr 10 15:41:33 2014
CKPT started with pid=14, OS id=24919
Thu Apr 10 15:41:33 2014
SMON started with pid=15, OS id=24921
Thu Apr 10 15:41:33 2014
RECO started with pid=16, OS id=24923
Thu Apr 10 15:41:33 2014
MMON started with pid=17, OS id=24925
Thu Apr 10 15:41:33 2014
MMNL started with pid=18, OS id=24927
starting up 1 dispatcher(s) for network address '(ADDRESS=(PARTIAL=YES)(PROTOCOL=TCP))'...
starting up 1 shared server(s) ...
ORACLE_BASE from environment = /oracle/database/oracle
Thu Apr 10 15:41:33 2014
CREATE DATABASE "mobile"
MAXINSTANCES 8
MAXLOGHISTORY 1
MAXLOGFILES 16
MAXLOGMEMBERS 3
MAXDATAFILES 100
DATAFILE SIZE 700M AUTOEXTEND ON NEXT 10240K MAXSIZE UNLIMITED
EXTENT MANAGEMENT LOCAL
SYSAUX DATAFILE SIZE 600M AUTOEXTEND ON NEXT 10240K MAXSIZE UNLIMITED
SMALLFILE DEFAULT TEMPORARY TABLESPACE TEMP TEMPFILE SIZE 20M AUTOEXTEND ON NEXT 640K MAXSIZE UNLIMITED
SMALLFILE UNDO TABLESPACE "UNDOTBS1" DATAFILE SIZE 200M AUTOEXTEND ON NEXT 5120K MAXSIZE UNLIMITED
CHARACTER SET ZHS16GBK
NATIONAL CHARACTER SET AL16UTF16
LOGFILE GROUP 1 SIZE 4096M,
GROUP 2 SIZE 4096M,
GROUP 3 SIZE 4096M,
GROUP 4 SIZE 4096M,
GROUP 5 SIZE 4096M
USER SYS IDENTIFIED BY USER SYSTEM IDENTIFIED BY
Starting background process ASMB
Thu Apr 10 15:41:33 2014
ASMB started with pid=22, OS id=24934
Starting background process RBAL
Thu Apr 10 15:41:33 2014
RBAL started with pid=23, OS id=24938
NOTE: initiating MARK startup
Starting background process MARK
Thu Apr 10 15:41:33 2014
MARK started with pid=24, OS id=24940
NOTE: MARK has subscribed
NOTE: Loaded library: /opt/oracle/extapi/64/asm/orcl/1/libasm.so
NOTE: Loaded library: System
SUCCESS: diskgroup DATA was mounted
ERROR: failed to establish dependency between database mobile and diskgroup resource ora.DATA.dg
Database mounted in Exclusive Mode
Lost write protection disabled
Thu Apr 10 15:43:06 2014
Errors in file /oracle/database/oracle/diag/rdbms/mobile/mobile/trace/mobile_ora_24932.trc:
ORA-19815: WARNING: db_recovery_file_dest_size of 5218762752 bytes is 100.00% used, and has 0 remaining bytes available.
************************************************************************
You have following choices to free up space from recovery area:
1. Consider changing RMAN RETENTION POLICY. If you are using Data Guard,
then consider changing RMAN ARCHIVELOG DELETION POLICY.
2. Back up files to tertiary device such as tape using RMAN
BACKUP RECOVERY AREA command.
3. Add disk space and increase db_recovery_file_dest_size parameter to
reflect the new space.
4. Delete unnecessary files using RMAN DELETE command. If an operating
system command was used to delete files, then use RMAN CROSSCHECK and
DELETE EXPIRED commands.
************************************************************************
Errors in file /oracle/database/oracle/diag/rdbms/mobile/mobile/trace/mobile_ora_24932.trc:
ORA-01501: CREATE DATABASE failed
ORA-19809: limit exceeded for recovery files
ORA-19804: cannot reclaim 4296015872 bytes disk space from 5218762752 limit
Error 19809 happened during database creation, shutting down database
USER (ospid: 24932): terminating the instance due to error 19809
Instance terminated by USER, pid = 24932
ORA-1092 signalled during: CREATE DATABASE "mobile"
MAXINSTANCES 8
MAXLOGHISTORY 1
MAXLOGFILES 16
MAXLOGMEMBERS 3
MAXDATAFILES 100
DATAFILE SIZE 700M AUTOEXTEND ON NEXT 10240K MAXSIZE UNLIMITED
EXTENT MANAGEMENT LOCAL
SYSAUX DATAFILE SIZE 600M AUTOEXTEND ON NEXT 10240K MAXSIZE UNLIMITED
SMALLFILE DEFAULT TEMPORARY TABLESPACE TEMP TEMPFILE SIZE 20M AUTOEXTEND ON NEXT 640K MAXSIZE UNLIMITED
SMALLFILE UNDO TABLESPACE "UNDOTBS1" DATAFILE SIZE 200M AUTOEXTEND ON NEXT 5120K MAXSIZE UNLIMITED
CHARACTER SET ZHS16GBK
NATIONAL CHARACTER SET AL16UTF16
LOGFILE GROUP 1 SIZE 4096M,
GROUP 2 SIZE 4096M,
GROUP 3 SIZE 4096M,
GROUP 4 SIZE 4096M,
GROUP 5 SIZE 4096M
USER SYS IDENTIFIED BY USER SYSTEM IDENTIFIED BY ...
NOTE: force a map free for map id 8
NOTE: force a map free for map id 7
NOTE: force a map free for map id 6
opiodr aborting process unknown ospid (24932) as a result of ORA-1092
Thu Apr 10 15:43:08 2014
ORA-1092 : opitsk aborting process
我看提示是闪回区只有4个G，小了，但是后来我把闪回区改到20G，还是报一样的错
4 个解决方案
#1
看上去像空间问题，检查磁盘空间是否足够？
#2
WARNING: db_recovery_file_dest_size of 5218762752 bytes is 100.00% used, and has 0 remaining bytes availa
空间用完，可能没有空间去创建了。
空间用完，可能没有空间去创建了。
#3
20G是肯定不够用的，给70个G还差不错，日志显示出来空间不足的问题了，
WARNING: db_recovery_file_dest_size of 5218762752 bytes is 100.00% used, and has 0 remaining bytes available.
查看日志真的对学习数据库来说很重要。
WARNING: db_recovery_file_dest_size of 5218762752 bytes is 100.00% used, and has 0 remaining bytes available.
查看日志真的对学习数据库来说很重要。
#4
磁盘空间不够。
#1
看上去像空间问题，检查磁盘空间是否足够？
#2
WARNING: db_recovery_file_dest_size of 5218762752 bytes is 100.00% used, and has 0 remaining bytes availa
空间用完，可能没有空间去创建了。
空间用完，可能没有空间去创建了。
#3
20G是肯定不够用的，给70个G还差不错，日志显示出来空间不足的问题了，
WARNING: db_recovery_file_dest_size of 5218762752 bytes is 100.00% used, and has 0 remaining bytes available.
查看日志真的对学习数据库来说很重要。
WARNING: db_recovery_file_dest_size of 5218762752 bytes is 100.00% used, and has 0 remaining bytes available.
查看日志真的对学习数据库来说很重要。
#4
磁盘空间不够。