数据库故障处理的案例-归档目录空间满（一）

最新推荐文章于 2023-06-09 17:06:25 发布
最新推荐文章于 2023-06-09 17:06:25 发布
阅读量1.7k 收藏
点赞数
分类专栏： ORACLE 文章标签： 数据库服务器 异常
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
本文链接：https://blog.csdn.net/alangmei/article/details/27167191
版权
某单位机房突然掉电，导致数据库异常，是否发现存储也有异常以及数据库管理的不善，导致一序列的问题接踵而来，还好本次的故障虽然问题好几次，但幸运的是数据库还是救了回来。
    数据库环境：Oracle 10.2.0.5 Rac For Linux X86_64，使用OCFS+ASM方式， 下面请看日志：
ORA-06512: at line 1
Tue May 13 10:59:26 2014
Thread 2 advanced to log sequence 11976 (LGWR switch)
  Current log# 4 seq# 11976 mem# 0: +DG/dqb/onlinelog/group_4.266.803845083
Tue May 13 13:09:24 2014
Thread 2 advanced to log sequence 11977 (LGWR switch)
  Current log# 3 seq# 11977 mem# 0: +DG/dqb/onlinelog/group_3.268.803845083
Tue May 13 16:30:39 2014
Starting ORACLE instance (normal)
LICENSE_MAX_SESSION = 0
LICENSE_SESSIONS_WARNING = 0
Interface type 1 eth1 192.168.1.0 configured from OCR for use as a cluster interconnect
Interface type 1 eth0 10.177.1.0 configured from OCR for use as  a public interface
Picked latch-free SCN scheme 3
Autotune of undo retention is turned on. 
LICENSE_MAX_USERS = 0
SYS auditing is disabled
ksdpec: called for event 13740 prior to event group initialization
Starting up ORACLE RDBMS Version: 10.2.0.4.0.
System parameters with non-default values:
  processes                = 300
  sessions                 = 335
  __shared_pool_size       = 637534208
  __large_pool_size        = 16777216
  __java_pool_size         = 16777216
  __streams_pool_size      = 0
  spfile                   = +DG/dqb/spfiledqb.ora
  sga_target               = 1610612736
  control_files            = +DG/dqb/controlfile/current.272.803844991
  control_file_record_keep_time= 8
  db_block_size            = 8192
  __db_cache_size          = 922746880
  compatible               = 10.2.0.3.0
  log_archive_dest_1       = LOCATION=+dg/dqb/arch/arch1
  db_file_multiblock_read_count= 16
  cluster_database         = TRUE
  cluster_database_instances= 2
  db_create_file_dest      = +DG
  thread                   = 2
  instance_number          = 2
  undo_management          = AUTO
  undo_tablespace          = UNDOTBS2
  remote_login_passwordfile= EXCLUSIVE
  db_domain                = 
  dispatchers              = (PROTOCOL=TCP) (SERVICE=dqbXDB)
  remote_listener          = LISTENERS_DQB
  job_queue_processes      = 10
  background_dump_dest     = /oracle/product/admin/dqb/bdump
  user_dump_dest           = /oracle/product/admin/dqb/udump
  core_dump_dest           = /oracle/product/admin/dqb/cdump
  audit_file_dest          = /oracle/product/admin/dqb/adump
  db_name                  = dqb
  open_cursors             = 300
  pga_aggregate_target     = 3363831808
Cluster communication is configured to use the following interface(s) for this instance
  192.168.1.2
Tue May 13 16:30:39 2014
cluster interconnect IPC version:Oracle UDP/IP (generic)
IPC Vendor 1 proto 2
PMON started with pid=4, OS id=13983
DIAG started with pid=8, OS id=13985
PSP0 started with pid=12, OS id=13987
LMON started with pid=16, OS id=13989
LMD0 started with pid=2, OS id=13991
LMS0 started with pid=6, OS id=13993
LMS1 started with pid=3, OS id=13997
LMS2 started with pid=20, OS id=14001
LMS3 started with pid=5, OS id=14005
LMS4 started with pid=10, OS id=14009
LMS5 started with pid=7, OS id=14014
LMS6 started with pid=24, OS id=14022
LMS7 started with pid=9, OS id=14026
MMAN started with pid=28, OS id=14030
DBW0 started with pid=14, OS id=14032
DBW1 started with pid=11, OS id=14034
DBW2 started with pid=32, OS id=14036
DBW3 started with pid=13, OS id=14038
LGWR started with pid=15, OS id=14040
CKPT started with pid=36, OS id=14042
SMON started with pid=40, OS id=14044
RECO started with pid=44, OS id=14046
CJQ0 started with pid=18, OS id=14048
MMON started with pid=48, OS id=14050
Tue May 13 16:30:40 2014
starting up 1 dispatcher(s) for network address '(ADDRESS=(PARTIAL=YES)(PROTOCOL=TCP))'...
MMNL started with pid=52, OS id=14052
Tue May 13 16:30:40 2014
starting up 1 shared server(s) ...
Tue May 13 16:30:40 2014
lmon registered with NM - instance id 2 (internal mem no 1)
Tue May 13 16:30:40 2014
Reconfiguration started (old inc 0, new inc 2)
List of nodes:
 1
 Global Resource Directory frozen
* allocate domain 0, invalid = TRUE 
 Communication channels reestablished
 Master broadcasted resource hash value bitmaps
 Non-local Process blocks cleaned out
Tue May 13 16:30:40 2014
 LMS 1: 0 GCS shadows cancelled, 0 closed
Tue May 13 16:30:40 2014
 LMS 2: 0 GCS shadows cancelled, 0 closed
Tue May 13 16:30:40 2014
 LMS 6: 0 GCS shadows cancelled, 0 closed
Tue May 13 16:30:40 2014
 LMS 3: 0 GCS shadows cancelled, 0 closed
Tue May 13 16:30:40 2014
 LMS 0: 0 GCS shadows cancelled, 0 closed
Tue May 13 16:30:40 2014
 LMS 4: 0 GCS shadows cancelled, 0 closed
Tue May 13 16:30:40 2014
 LMS 5: 0 GCS shadows cancelled, 0 closed
Tue May 13 16:30:40 2014
 LMS 7: 0 GCS shadows cancelled, 0 closed
 Set master node info 
 Submitted all remote-enqueue requests
 Dwn-cvts replayed, VALBLKs dubious
 All grantable enqueues granted
 Post SMON to start 1st pass IR
Tue May 13 16:30:40 2014
 LMS 2: 0 GCS shadows traversed, 0 replayed
Tue May 13 16:30:40 2014
 LMS 3: 0 GCS shadows traversed, 0 replayed
Tue May 13 16:30:40 2014
 LMS 0: 0 GCS shadows traversed, 0 replayed
Tue May 13 16:30:40 2014
 LMS 7: 0 GCS shadows traversed, 0 replayed
Tue May 13 16:30:40 2014
 LMS 1: 0 GCS shadows traversed, 0 replayed
Tue May 13 16:30:40 2014
 LMS 5: 0 GCS shadows traversed, 0 replayed
Tue May 13 16:30:40 2014
 LMS 4: 0 GCS shadows traversed, 0 replayed
Tue May 13 16:30:40 2014
 LMS 6: 0 GCS shadows traversed, 0 replayed
Tue May 13 16:30:40 2014
 Submitted all GCS remote-cache requests
 Fix write in gcs resources
Reconfiguration complete
LCK0 started with pid=30, OS id=14059
Tue May 13 16:30:41 2014
ALTER DATABASE   MOUNT
Tue May 13 16:30:41 2014
This instance was first to mount
Tue May 13 16:30:41 2014
Starting background process ASMB
ASMB started with pid=56, OS id=14070
Starting background process RBAL
RBAL started with pid=60, OS id=14074
Tue May 13 16:30:44 2014
SUCCESS: diskgroup DG was mounted
Tue May 13 16:30:49 2014
Setting recovery target incarnation to 2
Tue May 13 16:30:49 2014
Successful mount of redo thread 2, with mount id 4126418993
Tue May 13 16:30:49 2014
Database mounted in Shared Mode (CLUSTER_DATABASE=TRUE)
Completed: ALTER DATABASE   MOUNT
Tue May 13 16:30:49 2014
ALTER DATABASE OPEN
This instance was first to open
Tue May 13 16:30:53 2014
Beginning crash recovery of 2 threads
 parallel recovery started with 16 processes
Tue May 13 16:30:55 2014
Started redo scan
Tue May 13 16:30:55 2014
Completed redo scan
 0 redo blocks read, 0 data blocks need recovery
Tue May 13 16:30:55 2014
Started redo application at
 Thread 1: logseq 15107, block 142214
 Thread 2: logseq 11977, block 43783
Tue May 13 16:30:55 2014
Recovery of Online Redo Log: Thread 1 Group 1 Seq 15107 Reading mem 0
  Mem# 0: +DG/dqb/onlinelog/group_1.271.803844993
Tue May 13 16:30:55 2014
Recovery of Online Redo Log: Thread 2 Group 3 Seq 11977 Reading mem 0
  Mem# 0: +DG/dqb/onlinelog/group_3.268.803845083
Tue May 13 16:30:55 2014
Completed redo application
Tue May 13 16:30:55 2014
Completed crash recovery at
 Thread 1: logseq 15107, block 142214, scn 13881050933462
 Thread 2: logseq 11977, block 43783, scn 13881050931946
 0 data blocks read, 0 data blocks written, 0 redo blocks read
Tue May 13 16:30:55 2014
Thread 1 advanced to log sequence 15108 (thread recovery)
Picked broadcast on commit scheme to generate SCNs
Tue May 13 16:30:55 2014
LGWR: STARTING ARCH PROCESSES
ARC0 started with pid=58, OS id=14186
Tue May 13 16:30:55 2014
ARC0: Archival started
ARC1: Archival started
LGWR: STARTING ARCH PROCESSES COMPLETE
ARC1 started with pid=39, OS id=14188
Tue May 13 16:30:55 2014
Thread 2 advanced to log sequence 11978 (thread open)
Thread 2 opened at log sequence 11978
  Current log# 4 seq# 11978 mem# 0: +DG/dqb/onlinelog/group_4.266.803845083
Successful open of redo thread 2
Tue May 13 16:30:55 2014
MTTR advisory is disabled because FAST_START_MTTR_TARGET is not set
Tue May 13 16:30:55 2014
ARC1: Becoming the 'no FAL' ARCH
ARC1: Becoming the 'no SRL' ARCH
Tue May 13 16:30:55 2014
ARC0: Becoming the heartbeat ARCH
Tue May 13 16:30:55 2014
SMON: enabling cache recovery
Tue May 13 16:30:56 2014
ARC1: Log corruption near block 43776 change 13881059254746 time ?
Tue May 13 16:30:56 2014
Errors in file /oracle/product/admin/dqb/bdump/dqb2_arc1_14188.trc:
ORA-00354: corrupt redo log block header
ORA-00353: log corruption near block 43776 change 13881059254746 time 05/13/2014 13:09:24
ORA-00312: online log 3 thread 2: '+DG/dqb/onlinelog/group_3.268.803845083'
ARC1: All Archive destinations made inactive due to error 354
Tue May 13 16:30:56 2014
ARC1: Closing local archive destination LOG_ARCHIVE_DEST_1: '+DG/dqb/arch/arch1/2_11977_803844992.dbf' (error 354)
 (dqb2)
Committing creation of archivelog '+DG/dqb/arch/arch1/2_11977_803844992.dbf' (error 354)
ARCH: Archival stopped, error occurred. Will continue retrying
Tue May 13 16:30:56 2014
ORACLE Instance dqb2 - Archival Error
Tue May 13 16:30:56 2014
ORA-16038: log 3 sequence# 11977 cannot be archived
ORA-00354: corrupt redo log block header
ORA-00312: online log 3 thread 2: '+DG/dqb/onlinelog/group_3.268.803845083'
Tue May 13 16:30:56 2014
Errors in file /oracle/product/admin/dqb/bdump/dqb2_arc1_14188.trc:
ORA-16038: log 3 sequence# 11977 cannot be archived
ORA-00354: corrupt redo log block header
ORA-00312: online log 3 thread 2: '+DG/dqb/onlinelog/group_3.268.803845083'
Tue May 13 16:30:56 2014
Successfully onlined Undo Tablespace 5.
Tue May 13 16:30:56 2014
SMON: enabling tx recovery
Tue May 13 16:30:56 2014
Database Characterset is ZHS16GBK
Opening with internal Resource Manager plan
where NUMA PG = 4, CPUs = 20
Tue May 13 16:30:57 2014
Errors in file /oracle/product/admin/dqb/udump/dqb2_ora_14120.trc:
ORA-00354: corrupt redo log block header
ORA-00353: log corruption near block 43776 change 13881059258085 time 05/13/2014 13:58:35
ORA-00334: archived log: '+DG/dqb/onlinelog/group_3.268.803845083'
Tue May 13 16:30:57 2014
Errors in file /oracle/product/admin/dqb/udump/dqb2_ora_14120.trc:
ORA-00600: internal error code, arguments: [4194], [65], [47], [], [], [], [], []
Tue May 13 16:30:59 2014
Errors in file /oracle/product/admin/dqb/udump/dqb2_ora_14120.trc:
ORA-00354: corrupt redo log block header
ORA-00353: log corruption near block 43776 change 13881059258085 time 05/13/2014 13:58:35
ORA-00334: archived log: '+DG/dqb/onlinelog/group_3.268.803845083'
ORA-00600: internal error code, arguments: [4194], [65], [47], [], [], [], [], []
Tue May 13 16:31:00 2014
Trace dumping is performing id=[cdmp_20140513163100]
Tue May 13 16:31:00 2014
Errors in file /oracle/product/admin/dqb/udump/dqb2_ora_14120.trc:
ORA-00354: corrupt redo log block header
ORA-00353: log corruption near block 43776 change 13881059258085 time 05/13/2014 13:58:35
ORA-00334: archived log: '+DG/dqb/onlinelog/group_3.268.803845083'
ORA-00600: internal error code, arguments: [4194], [65], [47], [], [], [], [], []
Tue May 13 16:31:00 2014
Doing block recovery for file 6 block 4405
Block recovery from logseq 11978, block 89 to scn 13881066792885
Tue May 13 16:31:00 2014
Recovery of Online Redo Log: Thread 2 Group 4 Seq 11978 Reading mem 0
  Mem# 0: +DG/dqb/onlinelog/group_4.266.803845083
Block recovery stopped at EOT rba 11978.91.16
Block recovery completed at rba 11978.91.16, scn 3231.4027457777
Doing block recovery for file 6 block 121
Block recovery from logseq 11978, block 89 to scn 13881066791152
Tue May 13 16:31:00 2014
Recovery of Online Redo Log: Thread 2 Group 4 Seq 11978 Reading mem 0
  Mem# 0: +DG/dqb/onlinelog/group_4.266.803845083
Block recovery completed at rba 11978.91.16, scn 3231.4027457777
Tue May 13 16:31:00 2014
Errors in file /oracle/product/admin/dqb/udump/dqb2_ora_14120.trc:
ORA-00354: corrupt redo log block header
ORA-00353: log corruption near block 43776 change 13881059258085 time 05/13/2014 13:58:35
ORA-00334: archived log: '+DG/dqb/onlinelog/group_3.268.803845083'
Tue May 13 16:31:00 2014
Errors in file /oracle/product/admin/dqb/udump/dqb2_ora_14120.trc:
ORA-00600: internal error code, arguments: [4193], [25330], [25385], [], [], [], [], []
Tue May 13 16:31:00 2014
Errors in file /oracle/product/admin/dqb/bdump/dqb2_smon_14044.trc:
ORA-00354: corrupt redo log block header
ORA-00353: log corruption near block 43776 change 13881059258085 time 05/13/2014 13:58:35
ORA-00334: archived log: '+DG/dqb/onlinelog/group_3.268.803845083'
Tue May 13 16:31:00 2014
Errors in file /oracle/product/admin/dqb/bdump/dqb2_smon_14044.trc:
ORA-00600: internal error code, arguments: [4194], [43], [26], [], [], [], [], []
Tue May 13 16:31:01 2014
Errors in file /oracle/product/admin/dqb/bdump/dqb2_smon_14044.trc:
ORA-00354: corrupt redo log block header
ORA-00353: log corruption near block 43776 change 13881059258085 time 05/13/2014 13:58:35
ORA-00334: archived log: '+DG/dqb/onlinelog/group_3.268.803845083'
ORA-00600: internal error code, arguments: [4194], [43], [26], [], [], [], [], []
Tue May 13 16:31:01 2014
Doing block recovery for file 6 block 4718
Block recovery from logseq 11978, block 100 to scn 13881066792905
Tue May 13 16:31:01 2014
Recovery of Online Redo Log: Thread 2 Group 4 Seq 11978 Reading mem 0
  Mem# 0: +DG/dqb/onlinelog/group_4.266.803845083
Block recovery stopped at EOT rba 11978.101.16
Block recovery completed at rba 11978.101.16, scn 3231.4027459528
Doing block recovery for file 6 block 105
Block recovery from logseq 11978, block 100 to scn 13881066792903
Tue May 13 16:31:01 2014
Recovery of Online Redo Log: Thread 2 Group 4 Seq 11978 Reading mem 0
  Mem# 0: +DG/dqb/onlinelog/group_4.266.803845083
Block recovery completed at rba 11978.101.16, scn 3231.4027459528
Tue May 13 16:31:01 2014
Errors in file /oracle/product/admin/dqb/bdump/dqb2_smon_14044.trc:
ORA-01595: error freeing extent (4) of rollback segment (17))
ORA-00600: internal error code, arguments: [4194], [43], [26], [], [], [], [], []
Tue May 13 16:31:03 2014
Errors in file /oracle/product/admin/dqb/udump/dqb2_ora_14120.trc:
ORA-00354: corrupt redo log block header
ORA-00353: log corruption near block 43776 change 13881059258085 time 05/13/2014 13:58:35
ORA-00334: archived log: '+DG/dqb/onlinelog/group_3.268.803845083'
ORA-00600: internal error code, arguments: [4193], [25330], [25385], [], [], [], [], []
Tue May 13 16:31:03 2014
Errors in file /oracle/product/admin/dqb/udump/dqb2_ora_14120.trc:
ORA-00354: corrupt redo log block header
ORA-00353: log corruption near block 43776 change 13881059258085 time 05/13/2014 13:58:35
ORA-00334: archived log: '+DG/dqb/onlinelog/group_3.268.803845083'
ORA-00600: internal error code, arguments: [4193], [25330], [25385], [], [], [], [], []
Tue May 13 16:31:03 2014
Doing block recovery for file 6 block 301
Block recovery from logseq 11978, block 91 to scn 13881066792908
Tue May 13 16:31:03 2014
Recovery of Online Redo Log: Thread 2 Group 4 Seq 11978 Reading mem 0
  Mem# 0: +DG/dqb/onlinelog/group_4.266.803845083
Block recovery stopped at EOT rba 11978.101.16
Block recovery completed at rba 11978.101.16, scn 3231.4027459528
Doing block recovery for file 6 block 153
Block recovery from logseq 11978, block 91 to scn 13881066792887
Tue May 13 16:31:03 2014
Recovery of Online Redo Log: Thread 2 Group 4 Seq 11978 Reading mem 0
  Mem# 0: +DG/dqb/onlinelog/group_4.266.803845083
Block recovery completed at rba 11978.93.16, scn 3231.4027459513
replication_dependency_tracking turned off (no async multimaster replication found)
Starting background process QMNC
QMNC started with pid=66, OS id=14288
Tue May 13 16:31:04 2014
Errors in file /oracle/product/admin/dqb/udump/dqb2_ora_14120.trc:
ORA-00354: corrupt redo log block header
ORA-00353: log corruption near block 43776 change 13881059258085 time 05/13/2014 13:58:35
ORA-00334: archived log: '+DG/dqb/onlinelog/group_3.268.803845083'
Tue May 13 16:31:04 2014
Errors in file /oracle/product/admin/dqb/udump/dqb2_ora_14120.trc:
ORA-00600: internal error code, arguments: [4193], [25330], [25385], [], [], [], [], []
Tue May 13 16:31:07 2014
Errors in file /oracle/product/admin/dqb/udump/dqb2_ora_14120.trc:
ORA-00354: corrupt redo log block header
ORA-00353: log corruption near block 43776 change 13881059258085 time 05/13/2014 13:58:35
ORA-00334: archived log: '+DG/dqb/onlinelog/group_3.268.803845083'
ORA-00600: internal error code, arguments: [4193], [25330], [25385], [], [], [], [], []
Tue May 13 16:31:07 2014
Doing block recovery for file 6 block 301
Block recovery from logseq 11978, block 91 to scn 13881066792908
Tue May 13 16:31:07 2014
Recovery of Online Redo Log: Thread 2 Group 4 Seq 11978 Reading mem 0
  Mem# 0: +DG/dqb/onlinelog/group_4.266.803845083
Tue May 13 16:31:07 2014
Trace dumping is performing id=[cdmp_20140513163107]
Tue May 13 16:31:07 2014
Block recovery completed at rba 11978.101.16, scn 3231.4027459534
Doing block recovery for file 6 block 153
Block recovery from logseq 11978, block 91 to scn 13881066792913
Tue May 13 16:31:07 2014
Recovery of Online Redo Log: Thread 2 Group 4 Seq 11978 Reading mem 0
  Mem# 0: +DG/dqb/onlinelog/group_4.266.803845083
Block recovery completed at rba 11978.104.16, scn 3231.4027459538
Error 0 in kwqmnpartition(), aborting txn 
Tue May 13 16:31:07 2014
Errors in file /oracle/product/admin/dqb/udump/dqb2_ora_14120.trc:
ORA-00354: corrupt redo log block header
ORA-00353: log corruption near block 43776 change 13881059258085 time 05/13/2014 13:58:35
ORA-00334: archived log: '+DG/dqb/onlinelog/group_3.268.803845083'
Tue May 13 16:31:07 2014
ksdpec: called for event 13740 prior to event group initialization
Starting up ORACLE RDBMS Version: 10.2.0.4.0.
System parameters with non-default values:
  processes                = 300
  sessions                 = 335
  __shared_pool_size       = 637534208
  __large_pool_size        = 16777216
  __java_pool_size         = 16777216
  __streams_pool_size      = 0
  spfile                   = +DG/dqb/spfiledqb.ora
  sga_target               = 1610612736
  control_files            = +DG/dqb/controlfile/current.272.803844991
  control_file_record_keep_time= 8
  db_block_size            = 8192
  __db_cache_size          = 922746880
  compatible               = 10.2.0.3.0
  log_archive_dest_1       = LOCATION=+dg/dqb/arch/arch1
  db_file_multiblock_read_count= 16
  cluster_database         = TRUE
  cluster_database_instances= 2
  db_create_file_dest      = +DG
  db_recovery_file_dest_size= 10737418240
  thread                   = 2
  instance_number          = 2
  undo_management          = AUTO
  undo_tablespace          = UNDOTBS2
  remote_login_passwordfile= EXCLUSIVE
  db_domain                = 
  dispatchers              = (PROTOCOL=TCP) (SERVICE=dqbXDB)
  remote_listener          = LISTENERS_DQB
  job_queue_processes      = 10
  background_dump_dest     = /oracle/product/admin/dqb/bdump
  user_dump_dest           = /oracle/product/admin/dqb/udump
  core_dump_dest           = /oracle/product/admin/dqb/cdump
  audit_file_dest          = /oracle/product/admin/dqb/adump
  db_name                  = dqb
  open_cursors             = 300
  pga_aggregate_target     = 3363831808
Cluster communication is configured to use the following interface(s) for this instance
  192.168.1.2
Wed May 14 11:31:48 2014
cluster interconnect IPC version:Oracle UDP/IP (generic)
IPC Vendor 1 proto 2
PMON started with pid=2, OS id=32760
DIAG started with pid=6, OS id=32762
PSP0 started with pid=10, OS id=32764
LMON started with pid=14, OS id=32766
LMD0 started with pid=18, OS id=300
LMS0 started with pid=22, OS id=302
LMS1 started with pid=3, OS id=306
LMS2 started with pid=4, OS id=310
LMS3 started with pid=5, OS id=314
LMS4 started with pid=26, OS id=318
LMS5 started with pid=7, OS id=322
LMS6 started with pid=8, OS id=326
LMS7 started with pid=9, OS id=330
MMAN started with pid=30, OS id=334
DBW0 started with pid=34, OS id=336
DBW1 started with pid=11, OS id=338
DBW2 started with pid=12, OS id=340
DBW3 started with pid=13, OS id=342
LGWR started with pid=15, OS id=344
CKPT started with pid=38, OS id=346
SMON started with pid=42, OS id=348
RECO started with pid=46, OS id=350
CJQ0 started with pid=50, OS id=395
MMON started with pid=54, OS id=397
Wed May 14 11:31:49 2014
starting up 1 dispatcher(s) for network address '(ADDRESS=(PARTIAL=YES)(PROTOCOL=TCP))'...
MMNL started with pid=58, OS id=399
Wed May 14 11:31:49 2014
starting up 1 shared server(s) ...
Wed May 14 11:31:49 2014
lmon registered with NM - instance id 2 (internal mem no 1)
Wed May 14 11:31:49 2014
Reconfiguration started (old inc 0, new inc 2)
List of nodes:
 1
 Global Resource Directory frozen
* allocate domain 0, invalid = TRUE 
 Communication channels reestablished
 Master broadcasted resource hash value bitmaps
 Non-local Process blocks cleaned out
Wed May 14 11:31:49 2014
 LMS 0: 0 GCS shadows cancelled, 0 closed
Wed May 14 11:31:49 2014
 LMS 1: 0 GCS shadows cancelled, 0 closed
Wed May 14 11:31:49 2014
 LMS 3: 0 GCS shadows cancelled, 0 closed
Wed May 14 11:31:49 2014
 LMS 2: 0 GCS shadows cancelled, 0 closed
Wed May 14 11:31:49 2014
 LMS 4: 0 GCS shadows cancelled, 0 closed
Wed May 14 11:31:49 2014
 LMS 5: 0 GCS shadows cancelled, 0 closed
Wed May 14 11:31:49 2014
 LMS 6: 0 GCS shadows cancelled, 0 closed
Wed May 14 11:31:49 2014
 LMS 7: 0 GCS shadows cancelled, 0 closed
 Set master node info 
 Submitted all remote-enqueue requests
 Dwn-cvts replayed, VALBLKs dubious
 All grantable enqueues granted
 Post SMON to start 1st pass IR
Wed May 14 11:31:49 2014
 LMS 1: 0 GCS shadows traversed, 0 replayed
Wed May 14 11:31:49 2014
 LMS 0: 0 GCS shadows traversed, 0 replayed
Wed May 14 11:31:49 2014
 LMS 6: 0 GCS shadows traversed, 0 replayed
Wed May 14 11:31:49 2014
 LMS 2: 0 GCS shadows traversed, 0 replayed
Wed May 14 11:31:49 2014
 LMS 7: 0 GCS shadows traversed, 0 replayed
Wed May 14 11:31:49 2014
 LMS 3: 0 GCS shadows traversed, 0 replayed
Wed May 14 11:31:49 2014
 LMS 5: 0 GCS shadows traversed, 0 replayed
Wed May 14 11:31:49 2014
 LMS 4: 0 GCS shadows traversed, 0 replayed
Wed May 14 11:31:49 2014
 Submitted all GCS remote-cache requests
 Fix write in gcs resources
Reconfiguration complete
LCK0 started with pid=70, OS id=405
Wed May 14 11:31:50 2014
ALTER DATABASE   MOUNT
Wed May 14 11:31:50 2014
This instance was first to mount
Wed May 14 11:31:50 2014
Starting background process ASMB
ASMB started with pid=78, OS id=416
Starting background process RBAL
RBAL started with pid=82, OS id=420
Wed May 14 11:31:53 2014
SUCCESS: diskgroup DG was mounted
Wed May 14 11:31:57 2014
Setting recovery target incarnation to 2
Wed May 14 11:31:57 2014
Successful mount of redo thread 2, with mount id 4126510502
Wed May 14 11:31:57 2014
Database mounted in Shared Mode (CLUSTER_DATABASE=TRUE)
Completed: ALTER DATABASE   MOUNT
Wed May 14 11:31:57 2014
ALTER DATABASE OPEN
This instance was first to open
Picked broadcast on commit scheme to generate SCNs
Wed May 14 11:31:58 2014
LGWR: STARTING ARCH PROCESSES
ARC0 started with pid=90, OS id=475
Wed May 14 11:31:58 2014
ARC0: Archival started
ARC1 started with pid=23, OS id=477
Wed May 14 11:31:58 2014
ARC1: Archival started
LGWR: STARTING ARCH PROCESSES COMPLETE
Wed May 14 11:31:58 2014
ARC1: Becoming the 'no FAL' ARCH
ARC1: Becoming the 'no SRL' ARCH
Wed May 14 11:31:58 2014
ARC0: Becoming the heartbeat ARCH
Wed May 14 11:31:58 2014
ARCH: Log corruption near block 43776 change 13881059254746 time ?
Wed May 14 11:31:58 2014
Errors in file /oracle/product/admin/dqb/udump/dqb2_ora_466.trc:
ORA-00354: corrupt redo log block header
ORA-00353: log corruption near block 43776 change 13881059254746 time 05/13/2014 13:09:24
ORA-00312: online log 3 thread 2: '+DG/dqb/onlinelog/group_3.268.803845083'
ARCH: All Archive destinations made inactive due to error 354
Wed May 14 11:32:01 2014
ARCH: Closing local archive destination LOG_ARCHIVE_DEST_1: '+DG/dqb/arch/arch1/2_11977_803844992.dbf' (error 354)
 (dqb2)
Committing creation of archivelog '+DG/dqb/arch/arch1/2_11977_803844992.dbf' (error 354)
Wed May 14 11:32:01 2014
Errors in file /oracle/product/admin/dqb/udump/dqb2_ora_466.trc:
ORA-16038: log 3 sequence# 11977 cannot be archived
ORA-00354: corrupt redo log block header
ORA-00312: online log 3 thread 2: '+DG/dqb/onlinelog/group_3.268.803845083'
USER: terminating instance due to error 16038
Wed May 14 11:32:01 2014
Errors in file /oracle/product/admin/dqb/bdump/dqb2_lms1_306.trc:
ORA-16038: log  sequence#  cannot be archived
Wed May 14 11:32:01 2014
Errors in file /oracle/product/admin/dqb/bdump/dqb2_lms2_310.trc:
ORA-16038: log  sequence#  cannot be archived
Wed May 14 11:32:01 2014
Errors in file /oracle/product/admin/dqb/bdump/dqb2_lms3_314.trc:
ORA-16038: log  sequence#  cannot be archived
Wed May 14 11:32:01 2014
Errors in file /oracle/product/admin/dqb/bdump/dqb2_lms6_326.trc:
ORA-16038: log  sequence#  cannot be archived
Wed May 14 11:32:01 2014
System state dump is made for local instance
System State dumped to trace file /oracle/product/admin/dqb/bdump/dqb2_diag_32762.trc
Wed May 14 11:32:01 2014
Trace dumping is performing id=[cdmp_20140514113201]
Wed May 14 11:32:04 2014
Instance terminated by USER, pid = 466
Wed May 14 11:32:53 2014

出现上面的解决办法当然是删除无用的过期归档日志，腾出归档空间，以便数据库启动后执行归档进程恢复动作。
1、登陆到数据库服务器,并切换到oracle安装用户
#su - ora10g
$export ORACLE_SID=+ASM1   输出环境变量进入asm实例命令行
$asmcmd
asmcmd>pwd
+DG
asmcmd>cd +DG/.....
.......
番薯伯
关注
  • 0
    点赞
  • 踩
  • 0
    收藏
    觉得还不错? 一键收藏
  • 0
    评论
专栏目录
oracle启动卡住了,oracle总是死机
weixin_31446315的博客
04-03 1082
客户端在使用过程中总是莫名的死机，ORACLE所在服务器也挂了，下面是ALTERLOG日志，大虾们帮分析一下，急，谢了Sun Jul 30 09:13:54 2006ORACLE V9.2.0.4.0 - Production vsnsta=0vsnsql=12 vsnxtr=3Windows 2000 Version 5.2 , CPU type 586Sun Jul 30 09:13:54 2...
数据库常见问题处理
weixin_47450720的博客
04-06 2410
数据库是系统中最重要的组成部分之一，需要经常维护和监控，及时发现和解决问题，以确保系统的正常运行。在实际运维工作中，需要根据具体情况采取相应的措施，以保证数据库的可靠性和安全性。
日志损坏处理ORA-0035 ORA-00353 ORA-00312
LUMIS的博客
05-14 2673
Starting up ORACLE RDBMS Version: 10.2.0.4.0. System parameters with non-default values:   processes                = 300   sessions                 = 335   __shared_pool_size       = 687865856  
ORA-07445: exception encountered导致数据库实例无法启动问题处理
m0_37625564的博客
03-25 2392
数据库版本：Oracle 11.2.0.4 数据库启动后其中一个节点Instance terminated by PMON, pid = 44253导致数据库实例无法启动 告警日志： Fri Mar 25 17:41:08 2022 RCBG started with pid=51, OS id=44654 replication_dependency_tracking turned off (no async multimaster replication found) Starting backgro
数据库故障的发现与处理
LinkSLA的博客
06-09 1585
数据库健康检查：运行数据库的健康检查工具，如Oracle的DBVERIFY、MySQL的CHECK TABLE等。检查数据库配置：检查数据库的配置文件或管理工具中的配置参数，确保它们与实际要求和最佳实践相匹配。日志分析：仔细分析数据库的日志文件，如事务日志、错误日志等，查找任何与故障相关的异常记录。检查数据库空间：检查数据库的磁盘空间使用情况，包括数据文件、日志文件等。升级到较新的数据库版本或应用相关的修补程序。包括优化查询语句、调整索引、增加硬件资源、调整数据库参数等，以提高数据库的响应性能和吞吐量。
解决Oracle数据库归档日志占满磁盘空间问题
09-09
Oracle数据库的归档日志（Archived Logs）是数据库运行过程中不可或缺的一部分，它们记录了数据库事务的更改历史，用于在发生故障时进行恢复...在实际操作中，应谨慎处理归档日志，以免影响数据库的完整性和可恢复性。
数据库ORA-01196故障-归档日志丢失恢复详解
12-16
当数据库发生故障时，可以通过应用归档日志来恢复到故障发生前的一个已知良好状态。当数据库关闭时，如果有未提交的事务，这些信息会被写入归档日志，因此在重启数据库时，系统会要求执行介质恢复来应用这些归档日志...
Oracle数据库系统紧急故障处理方法
12-15
Oracle数据库系统在运行过程中可能会遇到各种紧急故障，如物理文件损坏、控制文件损坏或重做日志文件损坏等。这些故障可能导致数据库无法正常运行，甚至完全瘫痪。本教程将详细讲解如何处理这些紧急情况。 1. **...
数据库切换故障案例分析.doc
12-22
本文档总结了一次数据库切换故障案例分析，旨在总结和分享数据库切换故障案例的经验和教训。该案例分析了数据库切换故障的整个过程，包括数据库切换前的准备工作、数据库切换过程、故障出现原因、故障解决方法和最终...
记一次RAC Brain Split脑裂分析过程
cuizhi4718的博客
01-19 622
1.环境介绍： DB版本：11.2.0.4 64位 OS版本：AIX 6.1 位 2.错误现象 node1 节点1ASM实例日志： Mon Jan 12 09:08:48 2015 Reconfiguration s...
mysql 故障案例_性能问题导致的数据库严重故障案例之一
weixin_42511373的博客
01-27 225
好久不来这里写东西，今天有点时间，来这里写点最近遇到的事情。前段时间，某电信业务用户因某核心生产库最近多次宕机重启，多方人员介入无果后，给我发来了邮件，大概意思就是现在该问题已经造成了比较严重的后果，希望能帮助介入分析、诊断并解决该问题。好久不来这里写东西，今天有点时间，来这里写点最近遇到的事情。前段时间，某电信业务用户因某核心生产库最近多次宕机重启，多方人员介入无果后，给我发来了邮件，大概意思就...
KingbaseES V8R6单实例外部备份故障案例
lyu1026的博客
06-11 808
案例说明: 在KingbaseES V8R6单实例环境，配置外部备份服务器使用sys_backup.sh物理备份时，出现以下”WAL segment xxx was not archived before the 60000ms timeout“故障。操作步骤见：《KingbaseES V8R6 单实例sys_backup.sh外部备份案例》https://www.cnblogs.com/ti...
数据库的故障和恢复
qq_41033011的博客
11-26 4712
1. 数据库的故障和恢复方法 错误的数据输入：应用程序的检测机制进行检测。 系统错误：断电或软件错误。通过数据库的恢复机制进行恢复。 介质故障：磁盘故障，可用数据存储的奇偶校验进行校正，或采用 RAID 技术。 灾难性故障：火灾。及时备份（远程备份)。 2. 事务和日志的概念 事务：一系列的操作集合。 特性（ACID）: 原子性（Atomicity）：要么全部成功，要么全部失败。 一致性（Consistency）：事务必须从一个一致状态转变到另一个一致状态。 隔离性（Isolation）：多个用
数据库三种故障及其恢复手段
qq_48206320的博客
12-23 9265
三种故障： 1.事务故障：事务内部的故障，主要有可预期和不可预期的。 解决办法：可预期的用户会在写应用程序的时候用 if 语句避免，不可预期的系统自动根据日志文件对事务进行撤销和重做。 2.系统故障：由于各种原因导致系统停止运行，使得缓冲区里的数据没写进磁盘造成的故障，对数据库无损害。 基本解决方法： （1）正向扫描日志文件找到找到已提交的事务和 未提交的事务 （2）已提交的加入redo队列，未提交的加入undo队列。 （3）反向扫描日志文件对undo队列里所有事务执行逆操作，正向扫描日志文件对redo队列
(二)数据库故障处理的案例-处理归档不能执行
LUMIS的博客
05-27 3592
Starting up ORACLE RDBMS Version: 10.2.0.4.0. System parameters with non-default values:   processes                = 300   sessions                 = 335   __shared_pool_size       = 6878
MySQL数据库最常见的6种故障的排除方法
m0_45312259的博客
05-24 7218
95%的 bug 都是和具体的sql 相关，通常是 MySQL crash 前执行的最后一个sql 有问题，因此定位 bug 时应打开 general query log，根据最后一个 sql 来查找线索。第二个参数是--console，这个参数会把错误信息输出到屏幕上，这个参数带来的一个弊端是所有的信息都输出到屏幕上，让屏幕显得比较乱，但对于我们调试却是很方便的;然后再在后面加上有把握的参数，可以一次只加一个参数，然后启动 mysqld，采用排除法逐步找出错误的参数。
oracle集群现状,最近ORACLE RAC反复出现这个状况，正在找原因
weixin_29948389的博客
04-05 442
Sun Nov 22 14:08:15 2009starting up 1 shared server(s) ...Sun Nov 22 14:08:15 2009lmon registered with NM - instance id 1 (internal mem no 0)Sun Nov 22 14:08:19 2009Reconfiguration started (old inc 0,...
Oracle数据库adg数据没同步,adg备库磁盘空间不足，主库添加数据文件导致同步异常...
weixin_27964579的博客
04-03 1238
下午收到告警，某同城adg同步异常，数据库比较重要，需要紧急处理。一、分析1、查看同步状态该环境是主备均为两节点的rac adg结构，登录备库1节点，查询同步进程状态。SQL>setline999SQL>selectinst_id,thread#,process,pid,status,client_process,client_pid,sequence#,block#,act...
数据库开发基础案例 - jdbc 技术应用
最新发布
06-28
### 回答1： 数据库开发基础案例中，JDBC技术是非常重要的应用。JDBC是Java数据库连接的缩写，它提供了一种标准的API，用于连接和操作各种类型的数据库。通过JDBC技术，我们可以在Java应用程序中连接数据库，执行SQL语句，获取和处理查询结果等。 在实际开发中，我们可以使用JDBC技术来实现各种数据库操作，例如创建数据库、创建表、插入数据、更新数据、删除数据等。具体来说，我们可以通过JDBC API中的Connection、Statement、ResultSet等类来实现这些操作。 除了基本的数据库操作，JDBC技术还可以与其他技术结合使用，例如使用JSP和Servlet来实现Web应用程序中的数据库操作，或者使用Spring框架来实现更加高级的数据库操作。 总之，JDBC技术是数据库开发中不可或缺的一部分，掌握它可以让我们更加高效地进行数据库开发。 ### 回答2： JDBC技术是Java程序连接数据库的标准API。JDBC提供了一个接口，使Java开发人员可以与数据库进行交互，从而从中检索和修改信息。JDBC技术可以集成在Java应用程序中，可以帮助我们连接并操作各种类型的关系数据库。 JDBC的使用步骤包括： 1.加载JDBC驱动程序 在使用JDBC之前，我们必须使用Class.forName()加载相应的驱动程序，以便能够与特定数据库进行交互。例如，如果你想要与MySQL数据库连接，你可以加载com.mysql.jdbc.Driver类。 2.连接到数据库 在驱动程序加载完成后，我们可以使用DriverManager类来建立与数据库的连接。需要提供连接URL、用户名和密码等信息。 3.创建Statement对象 需要利用Connection对象来创建Statement对象，Statement对象用于执行SQL语句。Statement对象有三种类型：普通Statement对象、PreparedStatement对象和CallableStatement对象，它们的参数以及执行SQL语句的方式有所不同。 4.执行查询 利用Statement对象，我们可以执行普通的SQL查询语句，例如SELECT语句，通过ResultSet对象返回查询结果集。 5.执行更新 利用Statement对象，我们可以执行插入、更新、删除等操作，这些操作会改变数据库的状态。执行更新操作的方法是executeUpdate()，返回受影响的行数。 6.关闭资源 最后，我们必须关闭连接、Statement对象和ResultSet对象等资源，以避免内存泄漏和其他资源泄漏问题。 JDBC是Java应用程序连接数据库的标准方式，拥有丰富的API和灵活的使用方式。在企业级应用程序中，我们通常需要使用对象关系映射框架（ORM）来简化数据库操作。ORM框架可以自动将Java对象映射到关系数据库中的表，并且支持许多高级数据库操作，例如缓存、延迟加载和数据验证等。ORM框架可以大大简化开发人员对数据库的操作和管理，提高应用程序的开发效率和质量。 ### 回答3： JDBC是Java开发中最常用的关系型数据库连接技术，它允许开发者通过Java程序来访问和管理数据库。JDBC的使用非常广泛，无论是大型企业级应用程序，还是简单的个人应用程序都会用到它。下面我们来看一下如何在Java中使用JDBC技术来进行数据库开发。 一、数据库连接 在使用JDBC进行数据库开发之前，我们需要首先连接数据库。JDBC提供了一个标准接口，可以用来连接各种不同的数据库。连接数据库的代码如下： 1. 加载数据库驱动程序： Class.forName("com.mysql.jdbc.Driver"); 2. 获取数据库连接： Connection conn = DriverManager.getConnection("jdbc:mysql://localhost/test?user=root&password=root"); 其中，第一行代码是加载MySQL数据库驱动程序，第二行代码连接test数据库。在这个例子中，我们使用了MySQL数据库，但它也可以用来连接Oracle、SQL Server等其他数据库。 二、执行SQL语句 连接成功之后，我们就可以执行SQL语句了。JDBC提供了Statement和PreparedStatement两种接口来执行SQL语句。 1. Statement接口 Statement是最简单的执行SQL语句的接口。它允许我们执行任意的SQL语句，包括增删改查操作。下面是一个使用Statement执行查询语句的例子： Statement stmt = conn.createStatement(); ResultSet rs = stmt.executeQuery("select * from user"); 其中，conn是连接数据库的Connection对象，stmt使用Connection对象创建，用来执行SQL语句，rs是执行查询语句返回的结果集。 2. PreparedStatement接口 PreparedStatement是通过预编译方式执行SQL语句的接口。它预先编译SQL语句，避免了每次执行SQL语句时的解析操作，可以提高执行效率。下面是一个使用PreparedStatement执行查询语句的例子： PreparedStatement pstmt = conn.prepareStatement("select * from user where id = ?"); pstmt.setInt(1, 1); ResultSet rs = pstmt.executeQuery(); 其中，pstmt是通过Connection对象创建的，第一步预编译SQL语句，第二步通过setInt()方法设置参数，最后通过executeQuery()方法执行SQL语句并返回结果集。 三、事务处理 在进行数据库操作时，通常需要保证数据的一致性和完整性。JDBC提供了对事务的支持，允许我们在一系列操作中，将它们作为一个整体操作来执行。在JDBC中，我们可以使用Connection对象来处理事务。下面是一个简单的事务处理代码： try{ conn.setAutoCommit(false); //执行一系列操作... conn.commit(); }catch(Exception e){ conn.rollback(); }finally{ conn.setAutoCommit(true); } 其中，将AutoCommit设置为false表示开启事务处理，执行操作过程中出现异常时进行回滚操作，执行完成后将AutoCommit设置为true，表示恢复自动提交模式。 总结 以上就是JDBC在Java中进行数据库开发的基础案例。在实际的开发中，需要根据具体的场景进行选择和使用不同的JDBC接口。使用JDBC开发数据库程序，不仅可以让我们更好地管理数据库，还能提高程序的执行效率，为程序的稳定性和可靠性带来重要的保障。

“相关推荐”对你有帮助么？

  • 非常没帮助
  • 没帮助
  • 一般
  • 有帮助
  • 非常有帮助
提交
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值