Crash recovery everytime starting an instance
Is it normal that a crash recovery is started every time I start
an Oracle instance on a WinNT 4.0 system.
The xxxALRT.log file contains messages like this:
alter database open
Beginning crash recovery of 1 threads
Thread recovery: start rolling forward thread 1
and so on ...
The database startup takes a long time but after that the db
works normal.
Oracle always does recovery processing on startup. If you
shutdown abort your startup will take longer because there is
more recovery processing that has to be done. Shutting down
immediate takes longer because it performs clean up process so
that when you startup not as much recovery processing is needed.
Similar Messages
-
Hello,
Who initiate the crash recovery? SMON process or any other process?
In the ealier version of oracle (Oracle 7.3), it was instance recovery,
Now in Oracle 9i there are two types of recovery one crash recovery and another is instance recovery.
I want to know that whether in prior to Oracle 9i, there were two such recovery or only one?
Thanks.crash recovery
The automatic application of online redo records to a database after either a single-instance database crashes or all instances of an Oracle Real Applications Cluster configuration crash. Crash recovery only requires redo from the online logs: archived redo logs are not required.
In crash recovery, an instance automatically recovers the database before opening it. In general, the first instance to open the database after a crash or SHUTDOWN ABORT automatically performs crash recovery.
instance recovery
In an Oracle Real Applications Cluster configuration, the application of redo data to an open database by an instance when this instance discovers that another instance has crashed.
Hope it helps.
http://download.oracle.com/docs/cd/B10501_01/server.920/a96519/glossary.htm#432431
Adith -
Crash recovery/ instance recovery
Hi,
How do oracle identifies crash recovery/ instance recovery
is required?
Regards,
MathewHi,
>>But how do oracle identifies dabase is abnormally down and crash recovery is required?
I think that the checkpoint information that is desynchronized in redo log files and datafiles. It is necessary understand what is a checkpoint and what the CKPT process do. A checkpoint is a moment in time when all the changes (dirty blocks) made in the database buffer cache are made to the data files. The checkpoint is performed by the CKPT process and it creates an entry in the control file to identify the point in the online redo log file from where the instance recovery should begin in case of an instance failure. One of the ways a checkpoint is initiated is by the data block writer (DBWR) process. The DBWR process initiates a checkpoint by writing all modified data blocks in the data buffers (dirty buffers) to the data files. After a checkpoint is performed, all committed transactions are written to the data files. If the instance were to crash at this point, only new transactions that occurred after this checkpoint would need to be applied to the database to enable a complete recovery. Therefore, the checkpoint process determines which transactions from the redo logs need to be applied to the database in the event of a failure and subsequent recovery.
Cheers -
Crash recovery of productive db very slow
We had to shutdown a productive database with db2_kill, because it couldn't be stopped normally and had problem with a full FAILARCHPATH (After TSM server had problems, the archiving to TSM has not been successfully any more, even after TSM Server was up again: We had this problems before....)
The crash recovery takes very long. Sometimes even db2 list utilities <show details> seems to hang.
With db2pd -everything I can see the progress of the crash recovery:
Database Partition 0 -- Database PC1 -- Active -- Up 0 days 01:57:14 -- Date 05/07/2008 11:34:59
Recovery:
Recovery Status 0x00000C01
Current Log S0003363.LOG
Current LSN 061F2B330DBA
Job Type CRASH RECOVERY
Job ID 1
Job Start Time (1210145904) Wed May 7 09:38:24 2008
Job Description Crash Recovery
Invoker Type User
Total Phases 2
Current Phase 1
Progress:
Address PhaseNum Description StartTime CompletedWork TotalWork
0x000000020018E580 1 Forward Wed May 7 09:38:24 2008 786766439 bytes 1998253346 bytes
0x000000020018E670 2 Backward NotStarted 0 bytes 1998253346 bytes
So the db has now finished approx 1/3 of the bytes of the forward phase and then also have the backward phase!
In the db2diag.log there are no more entries after beginning of the crash recovery of 09:38.
We have move one logfile from the FAILARCHPATH directory (which was 100% full) to a different directory to be sure, that the slow crash recovery has nothing to do with the full FAILARCHPATH.
The log_dir directory has 20 logfiles (LOGPRIMARY+ LOGSECOND) in it (more could not be allocated there because the log_dir is sized according to the LOG-Parameters)
Parameter UTIL_HEAP_SZ = 150.000
Does anybody have an idea, why the crash recovery is so slow ?
Kind regards,
UtaHello Ralph,
the needed logfiles were all there and we didn't need to restore any logfiles from tsm (the "active" logfiles, which are needed for crash recovery should always reside in the log_dir...)
At 2008-05-07-14.17.07.357544 crash recovery was completed successfully.
At 2008-05-07-13.56.41.297552 the db has started archiving to tsm again:
ADM1844I Started archive for log file "S0003329.LOG".
According to dba collegues the crash recovery were only 50 % finished and then suddenly everything was finished. Since the "db2 list utilities" takes forward and backward phase into account for percentage, I assume that the backward phase was very fast.
The dba collegues have also recognized, that in the log_dir there were logfiles which were archived to tsm already. So they moved them out of the log_dir, and additional logfiles could be allocated (Before no add. logfile could be allocated). I couldn't say, if this was the reason, why the recovery was finished then afterwards.
The only problem is, that the database doesn't want to archive Logfiles S0003329- S0003350. Strange is also, that logfile 3329 was archived to the FAILARCHPATH yesterday successfully,
2008-05-06-12.27.10.316403+120 E4284459A420 LEVEL: Warning
PID : 3907 TID : 1 PROC : db2logmgr (PC1) 0
INSTANCE: db2pc1 NODE : 000
FUNCTION: DB2 UDB, data protection, sqlpgArchiveLogFile, probe:3170
MESSAGE : ADM1846I Completed archive for log file "S0003329.LOG" to
"/db2/PC1/log_archive/db2pc1/PC1/NODE0000/C0000009/" from
"/db2/PC1/log_dir/".
and now the db searches in the log_dir:
2008-05-07-13.57.02.525715+120 E25224816A315 LEVEL: Warning
PID : 28182 TID : 1 PROC : db2logmgr (PC1) 0
INSTANCE: db2pc1 NODE : 000
FUNCTION: DB2 UDB, data protection, sqlpgArchiveLogFile, probe:3108
MESSAGE : ADM1844I Started archive for log file "S0003329.LOG".
2008-05-07-13.57.02.526949+120 I25225132A364 LEVEL: Error
PID : 28182 TID : 1 PROC : db2logmgr (PC1) 0
INSTANCE: db2pc1 NODE : 000
FUNCTION: DB2 UDB, data protection, sqlpgArchiveLogVendor, probe:1630
RETCODE : ZRC=0x860F000A=-2045837302=SQLO_FNEX "File not found."
DIA8411C A file "" could not be found.
2008-05-07-13.57.02.527866+120 E25225497A367 LEVEL: Warning
PID : 28182 TID : 1 PROC : db2logmgr (PC1) 0
INSTANCE: db2pc1 NODE : 000
FUNCTION: DB2 UDB, data protection, sqlpgArchiveLogFile, probe:3150
MESSAGE : ADM1848W Failed archive for log file "S0003329.LOG" to "TSM chain 9"
2008-05-07-13.57.02.528352+120 I25225865A370 LEVEL: Error
PID : 28182 TID : 1 PROC : db2logmgr (PC1) 0
INSTANCE: db2pc1 NODE : 000
FUNCTION: DB2 UDB, data protection, sqlpgArchiveLogFile, probe:3160
MESSAGE : Failed to archive log file S0003329.LOG to TSM chain 9 from
/db2/PC1/log_dir/ with rc = -2045837302.
and this was none of the logfiles, which the collegue moved out of log_dir.
Has anybody seen the situation that the db couldn't archive from failarchpath to TSM after failure. We don't want to control every FAILARCHPATH after TSM-Failures....
Kind regards,
Uta -
ASM on one node crashes when we start the other two nodes ASM
We completed database build in Aug 2010
We complete PSU patching in Jan ending
Feb 4th the database crashed
We cannot start ASM on node1
ASM starts good on node2 and node3 but node1 cannot join
If ASM is down on node2, node3 then we can start ASM node1Reconfiguration started (old inc 0, new inc 6)
ASM instance
List of nodes:
0 1 2
Global Resource Directory frozen
* allocate domain 0, invalid = TRUE
Communication channels reestablished
* allocate domain 1, invalid = TRUE
* allocate domain 2, invalid = TRUE
Mon Mar 01 16:53:00 2010
Trace dumping is performing id=[cdmp_20100301165301]
Mon Mar 01 16:53:55 2010
ERROR: LMD0 (ospid: 274638) detects an idle connection to instance 2
Mon Mar 01 16:54:44 2010
Errors in file /oradb/oracle/diag/asm/+asm/+ASM1/trace/+ASM1_lmon_860280.trc (incident=116865):
ORA-29740: evicted by member 1, group incarnation 8
Incident details in: /oradb/oracle/diag/asm/+asm/+ASM1/incident/incdir_116865/+ASM1_lmon_860280_i116865.trc
Errors in file /oradb/oracle/diag/asm/+asm/+ASM1/trace/+ASM1_lmon_860280.trc:
ORA-29740: evicted by member 1, group incarnation 8
LMON (ospid: 860280): terminating the instance due to error 29740
Mon Mar 01 16:54:46 2010
System state dump is made for local instance
Errors in file /oradb/oracle/diag/asm/+asm/+ASM1/trace/+ASM1_diag_614488.trc (incident=116833):
ORA-29740: evicted by member , group incarnation
Incident details in: /oradb/oracle/diag/asm/+asm/+ASM1/incident/incdir_116833/+ASM1_diag_614488_i116833.trc
Mon Mar 01 16:54:46 2010
ORA-1092 : opitsk aborting process
Errors in file /oradb/oracle/diag/asm/+asm/+ASM1/trace/+ASM1_diag_614488.trc:
ORA-29740: evicted by member , group incarnation
Trace dumping is performing id=[cdmp_20100301165446]
Instance terminated by LMON, pid = 860280
Another thing we found that when we start ASM on node1, the cluster interconnect hangs when we try to ping
We did modify the cluster_interconnect parameter to try to start using public interface but the issued remained the same and we were not able to ping public interface
The crs is fine
$ crs_stat -t
Name Type Target State Host
ora....p1.inst application ONLINE OFFLINE
ora....p2.inst application ONLINE ONLINE noden2
ora....p3.inst application ONLINE ONLINE noden3
ora....1p2.srv application ONLINE ONLINE noden2
ora....1p3.srv application ONLINE ONLINE noden3
ora.....net.cs application ONLINE ONLINE noden1
ora.appl.db application ONLINE ONLINE noden1
ora....SM1.asm application ONLINE OFFLINE
ora....N1.lsnr application ONLINE ONLINE noden1
ora....8n1.gsd application ONLINE ONLINE noden1
ora....8n1.ons application ONLINE ONLINE noden1
ora....8n1.vip application ONLINE ONLINE noden1
ora....SM2.asm application ONLINE ONLINE noden2
ora....N2.lsnr application ONLINE ONLINE noden2
ora....8n2.gsd application ONLINE ONLINE noden2
ora....8n2.ons application ONLINE ONLINE noden2
ora....8n2.vip application ONLINE ONLINE noden2
ora....SM3.asm application ONLINE ONLINE noden3
ora....N3.lsnr application ONLINE ONLINE noden3
ora....8n3.gsd application ONLINE ONLINE noden3
ora....8n3.ons application ONLINE ONLINE noden3
ora....8n3.vip application ONLINE ONLINE noden3
Any inpts can helpEnv
3-node RAC
oracle version 11.1.0.7
Latest PSU Jan applied
OS is AIX version is 6100-02==========
LMON trace files
==========
Trace file /oradb/oracle/diag/asm/+asm/+ASM1/trace/+ASM1_lmon_860280.trc
Oracle Database 11g Enterprise Edition Release 11.1.0.7.0 - 64bit Production
With the Partitioning, Real Application Clusters, OLAP, Data Mining
and Real Application Testing options
ORACLE_HOME = /oradb/oracle/product/11.1/asm_1
System name: AIX
Node name: host-node1
Release: 1
Version: 6
Machine: 00C39EA44C00
Instance name: +ASM1
Redo thread mounted by this instance: 0 <none>
Oracle process number: 8
Unix process pid: 860280, image: oracle@host-node1 (LMON)
*** 2010-03-01 16:50:23.023
*** SESSION ID:(218.1) 2010-03-01 16:50:23.023
*** CLIENT ID:() 2010-03-01 16:50:23.023
*** SERVICE NAME:() 2010-03-01 16:50:23.023
*** MODULE NAME:() 2010-03-01 16:50:23.023
*** ACTION NAME:() 2010-03-01 16:50:23.023
GES resources 5596 pool 6
GES enqueues 7959
GES IPC: Receivers 2 Senders 2
GES IPC: Buffers Receive 1000 Send (i:1150 b:482) Reserve 402
GES IPC: Msg Size Regular 416 Batch 8192
Batching factor: enqueue replay 201, ack 224
Batching factor: cache replay 126 size per lock 64
kjxggin: CGS tickets = 1000
kjxgrdmpcpu: CPU Total 6 Core 3 Socket -1 OCPU 6
kjxgrdmpcpu: High load threshold 21504
*** 2010-03-01 16:50:23.362
kjxgmrcfg: Reconfiguration started, type 1
kjxgmcs: Setting state to 0 0.
*** 2010-03-01 16:50:23.363
Name Service frozen
kjxgmcs: Setting state to 0 1.
kjxgrdecidever: No old version members in the cluster
kjxgrssvote: reconfig bitmap chksum 0x88477268 cnt 3 master 0 ret 0
ksirValidateModuleInfo: action = 10 startup = 0
Name Service Mode: multi (0x21)
kjfcpiora: published my fusion master weight 5322
kjfcpiora: publish my flogb 9
kjfcpiora: publish my cluster_database_instances parameter=3
kjxggpoll: change poll time to 50 ms
kjxgrpropmsg: SSMEMI: inst 1 - no disk vote
kjxgrpropmsg: SSMEMI: inst 1 - no disk vote
kjxgrpropmsg: SSMEMI: inst 2 - no disk vote
SSVOTE: Master indicates no Disk Voting
kjxgmps: proposing substate 2
kjxgmcs: Setting state to 6 2.
kjfmuin: bitmap 0 1 2
kjfmmhi: received msg from 0 (inc 6)
kjfmmhi: received msg from 1 (inc 2)
kjfmmhi: received msg from 2 (inc 4)
Performed the unique instance identification check
kjxgmps: proposing substate 3
kjxgmcs: Setting state to 6 3.
Name Service recovery started
Deleted all dead-instance name entries
kjxgmps: proposing substate 4
kjxgmcs: Setting state to 6 4.
Multicasted all local name entries for publish
Replayed all pending requests
kjxgmps: proposing substate 5
kjxgmcs: Setting state to 6 5.
Name Service normal
Name Service recovery done
*** 2010-03-01 16:50:23.889
*** 2010-03-01 16:50:23.958
kjxgmps: proposing substate 6
kjxgmcs: Setting state to 6 6.
kjxggpoll: change poll time to 600 ms
2010-03-01 16:50:23.980620 :
********* kjfcrfg() called, BEGIN LMON RCFG *********
kjfcrfg: DRM window size = 0->128 (min lognb = 9)
2010-03-01 16:50:23.980811 :
Reconfiguration started (old inc 0, new inc 6)
ASM instance
Send timeout: 300 secs
Defer Queue timeout: 360 secs
Synchronization timeout: 420 sec
List of nodes:
0 1 2
*** 2010-03-01 16:50:24.023
2010-03-01 16:50:24.034432 : Global Resource Directory frozen
node 0
release 11 1 0 7
node 1
release 11 1 0 7
node 2
release 11 1 0 7
number of mastership buckets = 128
2010-03-01 16:50:24.034959 :
domain attach called for domid 0
* kjbdomalc: domain 0 invalid = TRUE
* kjbdomatt: first attach for domain 0
asby init, 0/0/x1
asby returns, 0/0/x1/false
* Domain maps before reconfiguration:
* DOMAIN 0 (valid 1): 0
* End of domain mappings
* Domain maps after recomputation:
* DOMAIN 0 (valid 1): 0 1 2
* End of domain mappings
Dead inst
Join inst 0 1 2
Exist inst
Active Sendback Threshold = 50 %
Communication channels reestablished
2010-03-01 16:50:24.152688 :
received all domreplay (6.6)
2010-03-01 16:50:24.152732 :
sent master 1 (6.6)
*** 2010-03-01 16:53:00.494
kjfmReceiverHealthCB_Check: Reciever [0] is healthy.
2010-03-01 16:52:56.921800 : Received comm error info from 2 (cnt 1)
kjxgrvalid: valid - 0.1 : (6 6) from 2
kjxgrrcfgchk: Initiating reconfig, reason=3
kjxgrrcfgchk: COMM rcfg - Disk Vote Required
2010-03-01 16:52:57.077877 : kjxgrnetchk: start 0x53001440, end 0x53019ae0
2010-03-01 16:52:57.077906 : kjxgrnetchk: Sending comm check req to 1
2010-03-01 16:52:57.078140 : kjxgrnetchk: Sending comm check req to 2
kjxgrrcfgchk: prev pstate 5 mapsz 512
kjxgrrcfgchk: new bmp: 0 1 2
kjxgrrcfgchk: work bmp: 0 1 2
kjxgrrcfgchk: rr bmp: 0 1 2
*** 2010-03-01 16:53:00.792
kjxgmrcfg: Reconfiguration started, type 3
kjxgmcs: Setting state to 6 0.
*** 2010-03-01 16:53:00.792
Name Service frozen
kjxgmcs: Setting state to 6 1.
kjxgrdecidever: No old version members in the cluster
kjxgrmsghndlr: Queue msg (0x110a21e50->0x110f09b90) type 7 for later
*** 2010-03-01 16:54:43.233
kjxgrssvote: reconfig bitmap chksum 0x88477268 cnt 3 master 2 ret 0
kjxgrrcfgchk: disable CGS timeout
kjxggpoll: change poll time to 50 ms
* kjfcchknested: CGS rcfg detected in step 7.0.0
SSVOTE: Master indicates Disk Voting required
2010-03-01 16:54:37.535518 : kjxgrmsghndlr: evict req from 1 for 0, seq (8, 8) vers 2193970751
2010-03-01 16:54:37.535587 : kjxgrdtrt: Evicted by 1, seq (8, 8)
IMR state information
Member 0, thread -1, state 0x2:c, flags 0x2c48
RR seq commit 6 cur 8
Propstate 3 prv 2 pending 0
rcfg rsn 3, rcfg time 1392514113, mem ct 3
master 2, master rcfg time 1392479783
evicted memcnt 0, starttm 0 chkcnt 0
system load 241 (normal)
Member information:
Member 0, incarn 6, version 0x82c5563f, thrd -1
prev thrd -1, status 0x1203 (JR..), err 0x0000
Member 1, incarn 6, version 0x82c1073b, thrd 2
prev thrd -1, status 0x1007 (JRM.), err 0x0002
Member 2, incarn 6, version 0x82c114ee, thrd 3
prev thrd -1, status 0x0007 (JRM.), err 0x0000
=====================================================
Group name: +ASM
Member id: 0
Cached KGXGN event: 0
Group State:
State: 6 1
Reconfig started start-tm 0x4b8c373c tmout period 0xffffffff state 0x2
Reconfig INPG type 3 inc 6 rsn 0 data 0x0
Reconfig COMP type 1 inc 6 rsn 0 data 0x0
Commited Map: 0 1 2
New Map: 0 1 2
KGXGN Map: 0 1 2
KGXGN Map2: 0 1 2
Master node: 0
Memcnt 3 Rcvcnt 0
Substate Proposal: false
Inc Proposal:
incarn 0 memcnt 0 master 0
proposal false matched false
map:
Master Inc State:
incarn 0 memcnt 0 agrees 0 flag 0x1
wmap:
nmap:
ubmap:
Substate Handler Execution State
substate 0 status done
substate 1 status done
substate 2 status done
substate 3 status done
substate 4 status done
substate 5 status done
substate 6 status done
IMR hist: 20[0x0a00:0x53019b0e] 4[0x0007:0x53019b0e] 3[0x0006:0x53019b0e]
IMR hist: 20[0x0902:0x53019b0e] 20[0x0702:0x53019b0b] 20[0x0702:0x53019b0a]
IMR hist: 20[0x0702:0x53019b0a] 1[0x0006:0x53019b0a] 20[0x0702:0x53019aff]
IMR hist: 10[0x0006:0x52fdbdb1] 20[0x0b00:0x52fdbdb1] 9[0x0006:0x52fdbdaf]
IMR hist: 20[0x0a02:0x52fdbdaf] 20[0x0a01:0x52fdbce1] 20[0x0a00:0x52fdbc8a]
IMR hist: 4[0x0005:0x52fdbc86] 3[0x0004:0x52fdbc4c] 20[0x0900:0x52fdbc4c]
IMR hist: 20[0x0802:0x52fdbc08] 20[0x0801:0x52fdbc08] 20[0x0801:0x52fdbc08]
IMR hist: 20[0x0602:0x52fdbc08] 20[0x0601:0x52fdbc08] 20[0x0601:0x52fdbc08]
IMR hist: 20[0x0800:0x52fdbc08] 20[0x0700:0x52fdbc08] 20[0x0602:0x52fdbc07]
IMR hist: 20[0x0800:0x52fdbc07] 20[0x0700:0x52fdbc07] 1[0x0000:0x52fdbbb8]
IMR hist: 0[0x0000:0x00000000] 0[0x0000:0x00000000]
KJM HIST LMD0:
7:0 6:0 5:7:0 12:97697 7:0 6:0 5:7:0 12:97696 7:0 6:0
5:7:0 12:97703 7:0 6:0 5:7:0 2:0 1:0 12:97713 7:0 6:0
5:7:0 12:97766 7:0 6:0 5:7:0 12:97782 7:0 6:0 5:7:0 12:97778
7:0 6:0 5:7:0 12:97799 7:0 6:0 5:7:0 12:97771 7:0 6:0
5:7:0 12:97784 7:0 6:0 5:7:0 12:97805 7:0 6:0 5:7:0 12:97785
7:0 6:0 5:7:0 12:97757 7:0 6:0 5:7:0 12:97770 7:0 6:0
5:7:0 12:97784 7:0 6:0
KJM HIST LMS0:
7:0 6:0 5:7:0 10:0 12:97697 7:0 6:0 5:7:0 10:0 12:97696
7:0 6:0 5:7:0 10:0 12:97703 7:0 6:0 5:7:0 10:0 12:97713
7:0 6:0 5:7:0 10:0 2:0 12:97766 7:0 6:0 5:7:0 10:0
12:97782 7:0 6:0 5:7:0 10:0 12:97778 7:0 6:0 5:7:0 10:0
12:97799 7:0 6:0 5:7:0 10:0 12:97771 7:0 6:0 5:7:0 10:0
12:97784 7:0 6:0 5:7:0 10:0 12:97805 7:0 6:0 5:7:0 10:0
12:97785 7:0 6:0 5:7:0
DUMP state for lmd0 (ospid 274638)
DUMP IPC context for lmd0 (ospid 274638)
Dumping process 9.274638 info:
*** 2010-03-01 16:54:43.664
Process diagnostic dump for oracle@host-node1 (LMD0), OS id=274638,
pid: 9, proc_ser: 1, sid: 217, sess_ser: 1
loadavg : 1.72 1.07 0.90
swap info: free_mem = 28642.09M rsv = 16.00M
alloc = 21.13M avail = 4096.00M swap_free = 4074.87M
F S UID PID PPID C PRI NI ADDR SZ WCHAN STIME TTY TIME CMD
240001 A oracle 274638 1 0 60 20 12ca9f590 156060 16:50:23 - 0:00 asm_lmd0_+ASM1
Short stack dump:
<-ksedsts()+0254<-ksdxfstk()+0028<-ksdxcb()+05d8<-sspuser()+0074<-4750<-poll()+000c<-sskgxp_select()+00e4<-skgxpiwait()+08a4<-skgxpwait()+06fc<-ksxpwait()+081c<-ksliwat()+0a58<-kslwaitctx()+0150<-kslwait()+006c<-ksxprcvimd()+0368<-kjctr_rksxp()+013c<-kjctrcv()+0160<-kjcsrmg()+005c<-kjmdm()+2454<-ksbrdp()+075c<-opirip()+0444<-opidrv()+0414<-sou2o()+0090<-opimai_real()+0148<-main()+0090<-__start()+0070
Process diagnostic dump actual duration=0.161000 sec
(max dump time=30.000000 sec)
*** 2010-03-01 16:54:43.825
SO: 0x70000001ff913a0, type: 2, owner: 0x0, flag: INIT/-/-/0x00 if: 0x3 c: 0x3
proc=0x70000001ff913a0, name=process, file=ksu.h LINE:10706 ID:, pg=0
(process) Oracle pid:9, ser:1, calls cur/top: 0x70000001f733140/0x70000001f733140
flags : (0x6) SYSTEM
flags2: (0x100), flags3: (0x0)
int error: 0, call error: 0, sess error: 0, txn error 0
ksudlp FALSE at location: 0
(post info) last post received: 0 0 83
last post received-location: kji.h LINE:2369 ID:kjga: clear wait for lmon
last process to post me: 70000001ff903b0 1 6
last post sent: 0 0 25
last post sent-location: ksa2.h LINE:282 ID:ksasnd
last process posted by me: 70000001ff903b0 1 6
(latch info) wait_event=68 bits=0
Process Group: DEFAULT, pseudo proc: 0x70000001f4851d0
O/S info: user: oracle, term: UNKNOWN, ospid: 274638
OSD pid info: Unix process pid: 274638, image: oracle@host-node1 (LMD0)
Dump of memory from 0x070000001FF70038 to 0x070000001FF70240
70000001FF70030 00000000 00000000 [........]
70000001FF70040 00000000 00000000 00000000 00000000 [................]
Repeat 31 times
SO: 0x70000001f6de4a0, type: 4, owner: 0x70000001ff913a0, flag: INIT/-/-/0x00 if: 0x3 c: 0x3
proc=0x70000001ff913a0, name=session, file=ksu.h LINE:10719 ID:, pg=0
(session) sid: 217 ser: 1 trans: 0x0, creator: 0x70000001ff913a0
flags: (0x51) USR/- flags_idl: (0x1) BSY/-/-/-/-/-
flags2: (0x408) -/-
DID: , short-term DID:
txn branch: 0x0
oct: 0, prv: 0, sql: 0x0, psql: 0x0, user: 0/SYS
ksuxds FALSE at location: 0
service name: SYS$BACKGROUND
Current Wait Stack:
0: waiting for 'ges remote message'
waittime=40, loop=0, p3=44
wait_id=2613 seq_num=2614 snap_id=1
wait times: snap=0.018269 sec, exc=0.018269 sec, total=0.018269 sec
wait times: max=0.080000 sec
wait counts: calls=1 os=1
in_wait=1 iflags=0x5a8
Wait State:
auto_close=0 flags=0x22 boundary=0x0/-1
Session Wait History:
0: waited for 'ges remote message'
waittime=40, loop=0, p3=44
wait_id=2612 seq_num=2613 snap_id=1
wait times: snap=0.160172 sec, exc=0.160172 sec, total=0.160172 sec
wait times: max=0.080000 sec
wait counts: calls=1 os=1
occurred after 0.000008 sec of elapsed time
1: waited for 'ges remote message'
waittime=40, loop=0, p3=44
wait_id=2611 seq_num=2612 snap_id=1
wait times: snap=0.096359 sec, exc=0.096359 sec, total=0.096359 sec
wait times: max=0.080000 sec
wait counts: calls=1 os=1
occurred after 0.000008 sec of elapsed time
2: waited for 'ges remote message'
waittime=40, loop=0, p3=44
wait_id=2610 seq_num=2611 snap_id=1
wait times: snap=0.098065 sec, exc=0.098065 sec, total=0.098065 sec
wait times: max=0.080000 sec
wait counts: calls=1 os=1
occurred after 0.000007 sec of elapsed time
3: waited for 'ges remote message'
waittime=40, loop=0, p3=44
wait_id=2609 seq_num=2610 snap_id=1
wait times: snap=0.097831 sec, exc=0.097831 sec, total=0.097831 sec
wait times: max=0.080000 sec
wait counts: calls=1 os=1
occurred after 0.000014 sec of elapsed time
4: waited for 'ges remote message'
waittime=40, loop=0, p3=44
wait_id=2608 seq_num=2609 snap_id=1
wait times: snap=0.095876 sec, exc=0.095876 sec, total=0.095876 sec
wait times: max=0.080000 sec
wait counts: calls=1 os=1
occurred after 0.000008 sec of elapsed time
5: waited for 'ges remote message'
waittime=40, loop=0, p3=44
wait_id=2607 seq_num=2608 snap_id=1
wait times: snap=0.098788 sec, exc=0.098788 sec, total=0.098788 sec
wait times: max=0.080000 sec
wait counts: calls=1 os=1
occurred after 0.000006 sec of elapsed time
6: waited for 'ges remote message'
waittime=40, loop=0, p3=44
wait_id=2606 seq_num=2607 snap_id=1
wait times: snap=0.098854 sec, exc=0.098854 sec, total=0.098854 sec
wait times: max=0.080000 sec
wait counts: calls=1 os=1
occurred after 0.000007 sec of elapsed time
7: waited for 'ges remote message'
waittime=40, loop=0, p3=44
wait_id=2605 seq_num=2606 snap_id=1
wait times: snap=0.098040 sec, exc=0.098040 sec, total=0.098040 sec
wait times: max=0.080000 sec
wait counts: calls=1 os=1
occurred after 0.000008 sec of elapsed time
8: waited for 'ges remote message'
waittime=40, loop=0, p3=44
wait_id=2604 seq_num=2605 snap_id=1
wait times: snap=0.097322 sec, exc=0.097322 sec, total=0.097322 sec
wait times: max=0.080000 sec
wait counts: calls=1 os=1
occurred after 0.000007 sec of elapsed time
9: waited for 'ges remote message'
waittime=40, loop=0, p3=44
wait_id=2603 seq_num=2604 snap_id=1
wait times: snap=0.097334 sec, exc=0.097334 sec, total=0.097334 sec
wait times: max=0.080000 sec
wait counts: calls=1 os=1
occurred after 0.000008 sec of elapsed time
Sampled Session History
The sampled session history is constructed by sampling
the target session every 1 second. The sampling process
captures at each sample if the session is in a non-idle wait,
an idle wait, or not in a wait. If the session is in a
non-idle wait then one interval is shown for all the samples
the session was in the same non-idle wait. If the
session is in an idle wait or not in a wait for
consecutive samples then one interval is shown for all
the consecutive samples. Though we display these consecutive
samples in a single interval the session may NOT be continuously
idle or not in a wait (the sampling process does not know).
The history is displayed in reverse chronological order.
sample interval: 1 sec, max history 120 sec
KSFD PGA DUMPS
Number of completed I/O requests=0 flags=0
END OF PROCESS STATE
LMON IPC context:
ksxpdmp: facility 0 (?) (0x1, 0x0) counts 0, 0
ksxpdmp: Dumping the osd context
SKGXP: SKGXPCTX: 0x1103bfb58 ctx
SKGXP:
SKGXP: WAIT HISTORY
SKGXP: Time(msec) Wait Type Return Code
SKGXP: ---------- --------- ------------
SKGXP: 0 NORMAL SUCC
SKGXP: 0 NORMAL SUCC
SKGXP: 0 NORMAL SUCC
SKGXP: 0 NORMAL SUCC
SKGXP: 0 NORMAL TIMEDOUT
SKGXP: 12 NORMAL TIMEDOUT
SKGXP: 0 NORMAL TIMEDOUT
SKGXP: 20 NORMAL TIMEDOUT
SKGXP: 0 NORMAL TIMEDOUT
SKGXP: 19 NORMAL TIMEDOUT
SKGXP: 0 NORMAL TIMEDOUT
SKGXP: 20 NORMAL TIMEDOUT
SKGXP: 0 NORMAL TIMEDOUT
SKGXP: 19 NORMAL TIMEDOUT
SKGXP: 0 NORMAL TIMEDOUT
SKGXP: 20 NORMAL TIMEDOUT
SKGXP: wait delta 0 sec (27 msec) ctx ts 0x3e377 last ts 0x3e381
SKGXP: user cpu time since last wait 0 sec 0 ticks
SKGXP: system cpu time since last wait 0 sec 0 ticks
SKGXP: locked 1
SKGXP: blocked 51
SKGXP: timed wait receives 0
SKGXP: admno 0x485303b1 admport:
SKGXP: SSKGXPT 0x103c0a74 flags sockno 12 IP 192.168.253.49 UDP 49777
SKGXP: context timestamp 0x3e377
SKGXP: buffers queued on port 1105aa950
SKGXP:
SKGXP: Dumping Connection Handle Table
SKGXP: sconno accono ertt state seq# RcvPid TotCreditsSKGXP: sent rtrans acks
SKGXP: CNH Table Bucket: 10
SKGXP: 0x339d0248 0x6dd6841c 64 4 32838 589900 8SKGXP: 75d 5d 32838d
SKGXP: CNH Table Bucket: 11
SKGXP: 0x339d0249 0x75ef4c98 32 4 32811 1007758 8SKGXP: 48d 12d 32811d
SKGXP: CNH Table Bucket: 12
SKGXP: 0x339d024a 0x75703ec2 16 4 32763 524518 8SKGXP: 0d 0d 0d
SKGXP: CNH Table Bucket: 13
SKGXP: 0x339d024b 0x41094259 16 4 32763 520260 8SKGXP: 0d 0d 0d
SKGXP: CNH Table Bucket: 14
SKGXP: 0x339d024c 0x7c1c696c 16 4 32763 585808 8SKGXP: 0d 0d 0d
SKGXP: CNH Table Bucket: 15
SKGXP: 0x339d024d 0x138c8c4a 16 4 32763 843952 8SKGXP: 0d 0d 0d
SKGXP:
SKGXP: Dumping Accept Handle Table
SKGXP: ach accono sconno admno state SndPid seq# rcv rtrans acks credits
SKGXP: ACH Table Bucket: 1472
SKGXP: 0x111088010 0x48cb4387 0x3365b236 0x1fe7dc68 40 1007758 32812 49 0 26 8
SKGXP: ACH Table Bucket: 1474
SKGXP: 0x11108b730 0x48cb4389 0x1c69654a 0x7183ff4c 40 589900 32838 75 0 52 8
Incident 116865 created, dump file: /oradb/oracle/diag/asm/+asm/+ASM1/incident/incdir_116865/+ASM1_lmon_860280_i116865.trc
ORA-29740: evicted by member 1, group incarnation 8
error 29740 detected in background process
ORA-29740: evicted by member 1, group incarnation 8
*** 2010-03-01 16:54:46.430
LMON (ospid: 860280): terminating the instance due to error 29740
ksuitm: waiting up to [5] seconds before killing DIAG
==========
DIAG trace files
=========
Oracle Database 11g Enterprise Edition Release 11.1.0.7.0 - 64bit Production
With the Partitioning, Real Application Clusters, OLAP, Data Mining
and Real Application Testing options
ORACLE_HOME = /oradb/oracle/product/11.1/asm_1
System name: AIX
Node name: host-node1
Release: 1
Version: 6
Machine: 00C39EA44C00
Instance name: +ASM1
Redo thread mounted by this instance: 0 <none>
Oracle process number: 4
Unix process pid: 614488, image: oracle@host-node1 (DIAG)
*** 2010-03-01 16:50:22.947
*** SESSION ID:(222.1) 2010-03-01 16:50:22.947
*** CLIENT ID:() 2010-03-01 16:50:22.947
*** SERVICE NAME:() 2010-03-01 16:50:22.947
*** MODULE NAME:() 2010-03-01 16:50:22.947
*** ACTION NAME:() 2010-03-01 16:50:22.947
Node id: 0
List of nodes: 0, 1, 2,
*** 2010-03-01 16:50:22.948
Reconfiguration starts [incarn=0]
*** 2010-03-01 16:50:22.948
I'm the master node
Group reconfiguration cleanup
*** 2010-03-01 16:50:23.602
A rcfg proposal from node 2 is received
*** 2010-03-01 16:50:23.602
A rcfg proposal from node 1 is received
*** 2010-03-01 16:50:23.602
Reconfiguration completes [incarn=3]
*** 2010-03-01 16:53:00.877
A dump event msg is rcv'd
REQUEST:trace dump in directory cdmp_20100301165301
*** 2010-03-01 16:53:00.877
Trace dumping is performing id=[cdmp_20100301165301]....
*** 2010-03-01 16:53:01.041
Trace dumping is done
*** 2010-03-01 16:54:46.560
Instance is terminating by process 860280 [ospid=oracle@host-node1 (LMON)]
Performing diagnostic data dump for this instance
Incident 116833 created, dump file: /oradb/oracle/diag/asm/+asm/+ASM1/incident/incdir_116833/+ASM1_diag_614488_i116833.trc
ORA-29740: evicted by member , group incarnation
Error 29740 encountered during system state dump
*** 2010-03-01 16:54:49.280
----- Error Stack Dump -----
ORA-29740: evicted by member , group incarnation
*** 2010-03-01 16:54:49.281
Trace dumping is performing id=[cdmp_20100301165446]....
*** 2010-03-01 16:54:49.433
Trace dumping is done -
"Beginning crash recovery of 1 threads"
Hi there!
Can you please inform if this is a problem? I'm getting "Beginning crash recovery of 1 threads" on every database startup (alert.log)
ThanksHere is my alert log from a few days:
Sun May 30 00:01:31 2010
ORACLE V10.2.0.4.0 - 64bit Production vsnsta=0
vsnsql=14 vsnxtr=3
Windows NT Version V6.0 Service Pack 2
CPU : 8 - type 8664, 8 Physical Cores
Process Affinity : 0x0000000000000000
Memory (Avail/Total): Ph:17900M/20477M, Ph+PgF:36037M/37825M
Sun May 30 00:01:31 2010
Starting ORACLE instance (restrict)
LICENSE_MAX_SESSION = 0
LICENSE_SESSIONS_WARNING = 0
Picked latch-free SCN scheme 3
Autotune of undo retention is turned on.
IMODE=BR
ILAT =18
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 = 150
__shared_pool_size = 1526726656
__large_pool_size = 0
__java_pool_size = 16777216
__streams_pool_size = 0
nls_language = AMERICAN
nls_territory = AMERICA
sga_target = 10737418240
control_files = E:\ORADATA\MYDB\CONTROL01.CTL, F:\ORADATA\MYDB\CONTROL02.CTL, H:\ORADATA\MYDB\CONTROL03.CTL
db_block_size = 8192
__db_cache_size = 9177137152
compatible = 10.2.0.3.0
log_archive_dest_1 = LOCATION=g:\archives\MYDB
log_archive_format = ARC%S_%R.%T
db_file_multiblock_read_count= 16
undo_management = AUTO
undo_tablespace = UNDOTBS1
remote_login_passwordfile= EXCLUSIVE
db_domain =
dispatchers = (PROTOCOL=TCP) (SERVICE=MYDBXDB)
local_listener = (ADDRESS=(PROTOCOL=TCP)(HOST=192.2.6.154)(PORT=1521))
remote_dependencies_mode = SIGNATURE
job_queue_processes = 10
audit_file_dest = H:\ADMIN\MYDB\ADUMP
background_dump_dest = H:\ADMIN\MYDB\BDUMP
user_dump_dest = H:\ADMIN\MYDB\UDUMP
core_dump_dest = H:\ADMIN\MYDB\CDUMP
db_name = MYDB
open_cursors = 300
pga_aggregate_target = 1073741824
PMON started with pid=2, OS id=1808
PSP0 started with pid=3, OS id=4848
MMAN started with pid=4, OS id=4824
DBW0 started with pid=5, OS id=4604
LGWR started with pid=6, OS id=776
CKPT started with pid=7, OS id=2012
SMON started with pid=8, OS id=4404
RECO started with pid=9, OS id=4484
CJQ0 started with pid=10, OS id=4396
MMON started with pid=11, OS id=5088
Sun May 30 00:01:31 2010
starting up 1 dispatcher(s) for network address '(ADDRESS=(PARTIAL=YES)(PROTOCOL=TCP))'...
MMNL started with pid=12, OS id=4552
Sun May 30 00:01:31 2010
starting up 1 shared server(s) ...
Oracle Data Guard is not available in this edition of Oracle.
Sun May 30 00:01:31 2010
alter database "MYDB" mount exclusive
Sun May 30 00:01:35 2010
Setting recovery target incarnation to 2
Sun May 30 00:01:36 2010
Successful mount of redo thread 1, with mount id 4241184411
Sun May 30 00:01:36 2010
Database mounted in Exclusive Mode
Completed: alter database "MYDB" mount exclusive
Sun May 30 00:01:36 2010
alter database open
Sun May 30 00:01:37 2010
Beginning crash recovery of 1 threads
Sun May 30 00:01:37 2010
Started redo scan
Sun May 30 00:01:37 2010
Completed redo scan
895 redo blocks read, 112 data blocks need recovery
Sun May 30 00:01:37 2010
Started redo application at
Thread 1: logseq 8835, block 70913
Sun May 30 00:01:37 2010
Recovery of Online Redo Log: Thread 1 Group 3 Seq 8835 Reading mem 0
Mem# 0: H:\ORADATA\MYDB\REDO03.LOG
Sun May 30 00:01:37 2010
Completed redo application
Sun May 30 00:01:37 2010
Completed crash recovery at
Thread 1: logseq 8835, block 71808, scn 282384241
112 data blocks read, 112 data blocks written, 895 redo blocks read
Sun May 30 00:01:37 2010
LGWR: STARTING ARCH PROCESSES
ARC0 started with pid=16, OS id=1780
Sun May 30 00:01:37 2010
ARC0: Archival started
ARC1: Archival started
LGWR: STARTING ARCH PROCESSES COMPLETE
ARC1 started with pid=17, OS id=2524
Sun May 30 00:01:37 2010
Thread 1 advanced to log sequence 8836 (thread open)
Thread 1 opened at log sequence 8836
Current log# 1 seq# 8836 mem# 0: H:\ORADATA\MYDB\REDO01.LOG
Successful open of redo thread 1
Sun May 30 00:01:37 2010
ARC0: Becoming the 'no FAL' ARCH
ARC0: Becoming the 'no SRL' ARCH
Sun May 30 00:01:37 2010
ARC1: Becoming the heartbeat ARCH
Sun May 30 00:01:37 2010
SMON: enabling cache recovery
Sun May 30 00:01:39 2010
Successfully onlined Undo Tablespace 1.
Sun May 30 00:01:39 2010
SMON: enabling tx recovery
Sun May 30 00:01:39 2010
Database Characterset is WE8ISO8859P1
replication_dependency_tracking turned off (no async multimaster replication found)
Starting background process QMNC
QMNC started with pid=18, OS id=4716
Sun May 30 00:01:42 2010
Completed: alter database open
Sun May 30 00:01:43 2010
ALTER SYSTEM disable restricted session;
Sun May 30 00:07:39 2010
Thread 1 advanced to log sequence 8837 (LGWR switch)
Current log# 2 seq# 8837 mem# 0: H:\ORADATA\MYDB\REDO02.LOG
Sun May 30 00:10:27 2010
Thread 1 advanced to log sequence 8838 (LGWR switch)
Current log# 3 seq# 8838 mem# 0: H:\ORADATA\MYDB\REDO03.LOG
Sun May 30 00:11:25 2010
Thread 1 advanced to log sequence 8839 (LGWR switch)
Current log# 1 seq# 8839 mem# 0: H:\ORADATA\MYDB\REDO01.LOG
Sun May 30 00:12:30 2010
Thread 1 advanced to log sequence 8840 (LGWR switch)
Current log# 2 seq# 8840 mem# 0: H:\ORADATA\MYDB\REDO02.LOG
Sun May 30 00:17:07 2010
Thread 1 advanced to log sequence 8841 (LGWR switch)
Current log# 3 seq# 8841 mem# 0: H:\ORADATA\MYDB\REDO03.LOG
Sun May 30 00:21:15 2010
Thread 1 advanced to log sequence 8842 (LGWR switch)
Current log# 1 seq# 8842 mem# 0: H:\ORADATA\MYDB\REDO01.LOG
Sun May 30 00:22:31 2010
Thread 1 advanced to log sequence 8843 (LGWR switch)
Current log# 2 seq# 8843 mem# 0: H:\ORADATA\MYDB\REDO02.LOG
Sun May 30 00:23:44 2010
Thread 1 advanced to log sequence 8844 (LGWR switch)
Current log# 3 seq# 8844 mem# 0: H:\ORADATA\MYDB\REDO03.LOG
Sun May 30 00:26:44 2010
Thread 1 advanced to log sequence 8845 (LGWR switch)
Current log# 1 seq# 8845 mem# 0: H:\ORADATA\MYDB\REDO01.LOG
Sun May 30 00:27:51 2010
Thread 1 advanced to log sequence 8846 (LGWR switch)
Current log# 2 seq# 8846 mem# 0: H:\ORADATA\MYDB\REDO02.LOG
Sun May 30 00:30:51 2010
Thread 1 advanced to log sequence 8847 (LGWR switch)
Current log# 3 seq# 8847 mem# 0: H:\ORADATA\MYDB\REDO03.LOG
Sun May 30 01:01:42 2010
Thread 1 advanced to log sequence 8848 (LGWR switch)
Current log# 1 seq# 8848 mem# 0: H:\ORADATA\MYDB\REDO01.LOG
Sun May 30 01:01:58 2010
Thread 1 advanced to log sequence 8849 (LGWR switch)
Current log# 2 seq# 8849 mem# 0: H:\ORADATA\MYDB\REDO02.LOG
Sun May 30 01:02:13 2010
Thread 1 advanced to log sequence 8850 (LGWR switch)
Current log# 3 seq# 8850 mem# 0: H:\ORADATA\MYDB\REDO03.LOG
Sun May 30 01:02:29 2010
Thread 1 advanced to log sequence 8851 (LGWR switch)
Current log# 1 seq# 8851 mem# 0: H:\ORADATA\MYDB\REDO01.LOG
Sun May 30 01:02:44 2010
Thread 1 advanced to log sequence 8852 (LGWR switch)
Current log# 2 seq# 8852 mem# 0: H:\ORADATA\MYDB\REDO02.LOG
Sun May 30 01:02:54 2010
Thread 1 advanced to log sequence 8853 (LGWR switch)
Current log# 3 seq# 8853 mem# 0: H:\ORADATA\MYDB\REDO03.LOG
Sun May 30 13:00:58 2010
Thread 1 advanced to log sequence 8854 (LGWR switch)
Current log# 1 seq# 8854 mem# 0: H:\ORADATA\MYDB\REDO01.LOG
Dump file h:\admin\MYDB\bdump\alert_MYDB.log
Mon May 31 00:00:33 2010
ORACLE V10.2.0.4.0 - 64bit Production vsnsta=0
vsnsql=14 vsnxtr=3
Windows NT Version V6.0 Service Pack 2
CPU : 8 - type 8664, 8 Physical Cores
Process Affinity : 0x0000000000000000
Memory (Avail/Total): Ph:18101M/20477M, Ph+PgF:35984M/37825M
Mon May 31 00:00:33 2010
Starting ORACLE instance (restrict)
LICENSE_MAX_SESSION = 0
LICENSE_SESSIONS_WARNING = 0
Picked latch-free SCN scheme 3
Autotune of undo retention is turned on.
IMODE=BR
ILAT =18
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 = 150
__shared_pool_size = 1526726656
__large_pool_size = 0
__java_pool_size = 16777216
__streams_pool_size = 0
nls_language = AMERICAN
nls_territory = AMERICA
sga_target = 10737418240
control_files = E:\ORADATA\MYDB\CONTROL01.CTL, F:\ORADATA\MYDB\CONTROL02.CTL, H:\ORADATA\MYDB\CONTROL03.CTL
db_block_size = 8192
__db_cache_size = 9177137152
compatible = 10.2.0.3.0
log_archive_dest_1 = LOCATION=g:\archives\MYDB
log_archive_format = ARC%S_%R.%T
db_file_multiblock_read_count= 16
undo_management = AUTO
undo_tablespace = UNDOTBS1
remote_login_passwordfile= EXCLUSIVE
db_domain =
dispatchers = (PROTOCOL=TCP) (SERVICE=MYDBXDB)
local_listener = (ADDRESS=(PROTOCOL=TCP)(HOST=192.2.6.154)(PORT=1521))
remote_dependencies_mode = SIGNATURE
job_queue_processes = 10
audit_file_dest = H:\ADMIN\MYDB\ADUMP
background_dump_dest = H:\ADMIN\MYDB\BDUMP
user_dump_dest = H:\ADMIN\MYDB\UDUMP
core_dump_dest = H:\ADMIN\MYDB\CDUMP
db_name = MYDB
open_cursors = 300
pga_aggregate_target = 1073741824
PMON started with pid=2, OS id=1068
PSP0 started with pid=3, OS id=4512
MMAN started with pid=4, OS id=4452
DBW0 started with pid=5, OS id=784
LGWR started with pid=6, OS id=4608
CKPT started with pid=7, OS id=4524
SMON started with pid=8, OS id=1976
RECO started with pid=9, OS id=3808
CJQ0 started with pid=10, OS id=4056
MMON started with pid=11, OS id=4792
Mon May 31 00:00:33 2010
starting up 1 dispatcher(s) for network address '(ADDRESS=(PARTIAL=YES)(PROTOCOL=TCP))'...
MMNL started with pid=12, OS id=4208
Mon May 31 00:00:33 2010
starting up 1 shared server(s) ...
Oracle Data Guard is not available in this edition of Oracle.
Mon May 31 00:00:33 2010
alter database "MYDB" mount exclusive
Mon May 31 00:00:37 2010
Setting recovery target incarnation to 2
Mon May 31 00:00:37 2010
Successful mount of redo thread 1, with mount id 4241228001
Mon May 31 00:00:37 2010
Database mounted in Exclusive Mode
Completed: alter database "MYDB" mount exclusive
Mon May 31 00:00:37 2010
alter database open
Mon May 31 00:00:38 2010
Beginning crash recovery of 1 threads
Mon May 31 00:00:38 2010
Started redo scan
Mon May 31 00:00:38 2010
Completed redo scan
815 redo blocks read, 108 data blocks need recovery
Mon May 31 00:00:38 2010
Started redo application at
Thread 1: logseq 8854, block 31079
Mon May 31 00:00:38 2010
Recovery of Online Redo Log: Thread 1 Group 1 Seq 8854 Reading mem 0
Mem# 0: H:\ORADATA\MYDB\REDO01.LOG
Mon May 31 00:00:38 2010
Completed redo application
Mon May 31 00:00:38 2010
Completed crash recovery at
Thread 1: logseq 8854, block 31894, scn 282601383
108 data blocks read, 108 data blocks written, 815 redo blocks read
Mon May 31 00:00:38 2010
LGWR: STARTING ARCH PROCESSES
ARC0 started with pid=16, OS id=1792
Mon May 31 00:00:38 2010
ARC0: Archival started
ARC1: Archival started
LGWR: STARTING ARCH PROCESSES COMPLETE
ARC1 started with pid=17, OS id=5048
Mon May 31 00:00:38 2010
Thread 1 advanced to log sequence 8855 (thread open)
Thread 1 opened at log sequence 8855
Current log# 2 seq# 8855 mem# 0: H:\ORADATA\MYDB\REDO02.LOG
Successful open of redo thread 1
Mon May 31 00:00:38 2010
ARC1: Becoming the 'no FAL' ARCH
ARC1: Becoming the 'no SRL' ARCH
Mon May 31 00:00:38 2010
ARC0: Becoming the heartbeat ARCH
Mon May 31 00:00:38 2010
SMON: enabling cache recovery
Mon May 31 00:00:40 2010
Successfully onlined Undo Tablespace 1.
Mon May 31 00:00:40 2010
SMON: enabling tx recovery
Mon May 31 00:00:40 2010
Database Characterset is WE8ISO8859P1
replication_dependency_tracking turned off (no async multimaster replication found)
Starting background process QMNC
QMNC started with pid=18, OS id=4612
Mon May 31 00:00:42 2010
Completed: alter database open
Mon May 31 00:00:42 2010
ALTER SYSTEM disable restricted session;
Mon May 31 00:06:45 2010
Thread 1 advanced to log sequence 8856 (LGWR switch)
Current log# 3 seq# 8856 mem# 0: H:\ORADATA\MYDB\REDO03.LOG
Mon May 31 00:09:34 2010
Thread 1 advanced to log sequence 8857 (LGWR switch)
Current log# 1 seq# 8857 mem# 0: H:\ORADATA\MYDB\REDO01.LOG
Mon May 31 00:10:33 2010
Thread 1 advanced to log sequence 8858 (LGWR switch)
Current log# 2 seq# 8858 mem# 0: H:\ORADATA\MYDB\REDO02.LOG
Mon May 31 00:11:38 2010
Thread 1 advanced to log sequence 8859 (LGWR switch)
Current log# 3 seq# 8859 mem# 0: H:\ORADATA\MYDB\REDO03.LOG
Mon May 31 00:16:13 2010
Thread 1 advanced to log sequence 8860 (LGWR switch)
Current log# 1 seq# 8860 mem# 0: H:\ORADATA\MYDB\REDO01.LOG
Mon May 31 00:20:09 2010
Thread 1 advanced to log sequence 8861 (LGWR switch)
Current log# 2 seq# 8861 mem# 0: H:\ORADATA\MYDB\REDO02.LOG
Mon May 31 00:21:28 2010
Thread 1 advanced to log sequence 8862 (LGWR switch)
Current log# 3 seq# 8862 mem# 0: H:\ORADATA\MYDB\REDO03.LOG
Mon May 31 00:22:37 2010
Thread 1 advanced to log sequence 8863 (LGWR switch)
Current log# 1 seq# 8863 mem# 0: H:\ORADATA\MYDB\REDO01.LOG
Mon May 31 00:25:42 2010
Thread 1 advanced to log sequence 8864 (LGWR switch)
Current log# 2 seq# 8864 mem# 0: H:\ORADATA\MYDB\REDO02.LOG
Mon May 31 00:26:47 2010
Thread 1 advanced to log sequence 8865 (LGWR switch)
Current log# 3 seq# 8865 mem# 0: H:\ORADATA\MYDB\REDO03.LOG
Mon May 31 00:29:52 2010
Thread 1 advanced to log sequence 8866 (LGWR switch)
Current log# 1 seq# 8866 mem# 0: H:\ORADATA\MYDB\REDO01.LOG
Mon May 31 10:43:39 2010
Thread 1 advanced to log sequence 8867 (LGWR switch)
Current log# 2 seq# 8867 mem# 0: H:\ORADATA\MYDB\REDO02.LOG
Mon May 31 11:30:27 2010
Thread 1 advanced to log sequence 8868 (LGWR switch)
Current log# 3 seq# 8868 mem# 0: H:\ORADATA\MYDB\REDO03.LOG
Mon May 31 12:57:56 2010
Thread 1 advanced to log sequence 8869 (LGWR switch)
Current log# 1 seq# 8869 mem# 0: H:\ORADATA\MYDB\REDO01.LOG
Mon May 31 15:19:50 2010
Thread 1 advanced to log sequence 8870 (LGWR switch)
Current log# 2 seq# 8870 mem# 0: H:\ORADATA\MYDB\REDO02.LOG
Mon May 31 22:00:52 2010
Thread 1 advanced to log sequence 8871 (LGWR switch)
Current log# 3 seq# 8871 mem# 0: H:\ORADATA\MYDB\REDO03.LOG
Mon May 31 22:01:02 2010
Thread 1 advanced to log sequence 8872 (LGWR switch)
Current log# 1 seq# 8872 mem# 0: H:\ORADATA\MYDB\REDO01.LOG
Mon May 31 22:01:27 2010
Thread 1 advanced to log sequence 8873 (LGWR switch)
Current log# 2 seq# 8873 mem# 0: H:\ORADATA\MYDB\REDO02.LOG
Mon May 31 22:01:47 2010
Thread 1 advanced to log sequence 8874 (LGWR switch)
Current log# 3 seq# 8874 mem# 0: H:\ORADATA\MYDB\REDO03.LOG
Mon May 31 22:02:09 2010
Thread 1 advanced to log sequence 8875 (LGWR switch)
Current log# 1 seq# 8875 mem# 0: H:\ORADATA\MYDB\REDO01.LOG
Mon May 31 22:02:24 2010
Thread 1 advanced to log sequence 8876 (LGWR switch)
Current log# 2 seq# 8876 mem# 0: H:\ORADATA\MYDB\REDO02.LOG
Mon May 31 22:02:30 2010
Thread 1 advanced to log sequence 8877 (LGWR switch)
Current log# 3 seq# 8877 mem# 0: H:\ORADATA\MYDB\REDO03.LOG
Mon May 31 22:02:37 2010
Thread 1 advanced to log sequence 8878 (LGWR switch)
Current log# 1 seq# 8878 mem# 0: H:\ORADATA\MYDB\REDO01.LOG
Mon May 31 22:02:45 2010
Thread 1 advanced to log sequence 8879 (LGWR switch)
Current log# 2 seq# 8879 mem# 0: H:\ORADATA\MYDB\REDO02.LOG
Mon May 31 22:02:50 2010
Thread 1 advanced to log sequence 8880 (LGWR switch)
Current log# 3 seq# 8880 mem# 0: H:\ORADATA\MYDB\REDO03.LOG
Mon May 31 22:02:54 2010
Thread 1 advanced to log sequence 8881 (LGWR switch)
Current log# 1 seq# 8881 mem# 0: H:\ORADATA\MYDB\REDO01.LOG
Mon May 31 22:02:58 2010
Thread 1 advanced to log sequence 8882 (LGWR switch)
Current log# 2 seq# 8882 mem# 0: H:\ORADATA\MYDB\REDO02.LOG
Mon May 31 22:03:15 2010
Thread 1 advanced to log sequence 8883 (LGWR switch)
Current log# 3 seq# 8883 mem# 0: H:\ORADATA\MYDB\REDO03.LOG
Dump file h:\admin\MYDB\bdump\alert_MYDB.log
Tue Jun 01 00:01:05 2010
ORACLE V10.2.0.4.0 - 64bit Production vsnsta=0
vsnsql=14 vsnxtr=3
Windows NT Version V6.0 Service Pack 2
CPU : 8 - type 8664, 8 Physical Cores
Process Affinity : 0x0000000000000000
Memory (Avail/Total): Ph:18247M/20477M, Ph+PgF:36004M/37825M
Tue Jun 01 00:01:05 2010
Starting ORACLE instance (restrict)
LICENSE_MAX_SESSION = 0
LICENSE_SESSIONS_WARNING = 0
Picked latch-free SCN scheme 3
Autotune of undo retention is turned on.
IMODE=BR
ILAT =18
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 = 150
__shared_pool_size = 1526726656
__large_pool_size = 0
__java_pool_size = 16777216
__streams_pool_size = 0
nls_language = AMERICAN
nls_territory = AMERICA
sga_target = 10737418240
control_files = E:\ORADATA\MYDB\CONTROL01.CTL, F:\ORADATA\MYDB\CONTROL02.CTL, H:\ORADATA\MYDB\CONTROL03.CTL
db_block_size = 8192
__db_cache_size = 9177137152
compatible = 10.2.0.3.0
log_archive_dest_1 = LOCATION=g:\archives\MYDB
log_archive_format = ARC%S_%R.%T
db_file_multiblock_read_count= 16
undo_management = AUTO
undo_tablespace = UNDOTBS1
remote_login_passwordfile= EXCLUSIVE
db_domain =
dispatchers = (PROTOCOL=TCP) (SERVICE=MYDBXDB)
local_listener = (ADDRESS=(PROTOCOL=TCP)(HOST=192.2.6.154)(PORT=1521))
remote_dependencies_mode = SIGNATURE
job_queue_processes = 10
audit_file_dest = H:\ADMIN\MYDB\ADUMP
background_dump_dest = H:\ADMIN\MYDB\BDUMP
user_dump_dest = H:\ADMIN\MYDB\UDUMP
core_dump_dest = H:\ADMIN\MYDB\CDUMP
db_name = MYDB
open_cursors = 300
pga_aggregate_target = 1073741824
PMON started with pid=2, OS id=2724
PSP0 started with pid=3, OS id=5088
MMAN started with pid=4, OS id=4436
DBW0 started with pid=5, OS id=4400
LGWR started with pid=6, OS id=792
CKPT started with pid=7, OS id=4036
SMON started with pid=8, OS id=4220
RECO started with pid=9, OS id=1856
CJQ0 started with pid=10, OS id=332
MMON started with pid=11, OS id=4224
Tue Jun 01 00:01:05 2010
starting up 1 dispatcher(s) for network address '(ADDRESS=(PARTIAL=YES)(PROTOCOL=TCP))'...
MMNL started with pid=12, OS id=4784
Tue Jun 01 00:01:05 2010
starting up 1 shared server(s) ...
Oracle Data Guard is not available in this edition of Oracle.
Tue Jun 01 00:01:05 2010
alter database "MYDB" mount exclusive
Tue Jun 01 00:01:10 2010
Setting recovery target incarnation to 2
Tue Jun 01 00:01:10 2010
Successful mount of redo thread 1, with mount id 4241292930
Tue Jun 01 00:01:10 2010
Database mounted in Exclusive Mode
Completed: alter database "MYDB" mount exclusive
Tue Jun 01 00:01:10 2010
alter database open
Tue Jun 01 00:01:10 2010
Beginning crash recovery of 1 threads
Tue Jun 01 00:01:10 2010
Started redo scan
Tue Jun 01 00:01:11 2010
Completed redo scan
893 redo blocks read, 96 data blocks need recovery
Tue Jun 01 00:01:11 2010
Started redo application at
Thread 1: logseq 8883, block 18558
Tue Jun 01 00:01:11 2010
Recovery of Online Redo Log: Thread 1 Group 3 Seq 8883 Reading mem 0
Mem# 0: H:\ORADATA\MYDB\REDO03.LOG
Tue Jun 01 00:01:11 2010
Completed redo application
Tue Jun 01 00:01:11 2010
Completed crash recovery at
Thread 1: logseq 8883, block 19451, scn 283448451
96 data blocks read, 96 data blocks written, 893 redo blocks read
Tue Jun 01 00:01:11 2010
LGWR: STARTING ARCH PROCESSES
ARC0 started with pid=16, OS id=1804
Tue Jun 01 00:01:11 2010
ARC0: Archival started
ARC1: Archival started
LGWR: STARTING ARCH PROCESSES COMPLETE
ARC1 started with pid=17, OS id=4988
Tue Jun 01 00:01:11 2010
Thread 1 advanced to log sequence 8884 (thread open)
Thread 1 opened at log sequence 8884
Current log# 1 seq# 8884 mem# 0: H:\ORADATA\MYDB\REDO01.LOG
Successful open of redo thread 1
Tue Jun 01 00:01:11 2010
ARC1: Becoming the 'no FAL' ARCH
ARC1: Becoming the 'no SRL' ARCH
Tue Jun 01 00:01:11 2010
ARC0: Becoming the heartbeat ARCH
Tue Jun 01 00:01:11 2010
SMON: enabling cache recovery
Tue Jun 01 00:01:11 2010
Successfully onlined Undo Tablespace 1.
Tue Jun 01 00:01:11 2010
SMON: enabling tx recovery
Tue Jun 01 00:01:11 2010
Database Characterset is WE8ISO8859P1
replication_dependency_tracking turned off (no async multimaster replication found)
Starting background process QMNC
QMNC started with pid=18, OS id=244
Tue Jun 01 00:01:13 2010
Completed: alter database open
Tue Jun 01 00:01:13 2010
ALTER SYSTEM disable restricted session;
Tue Jun 01 00:07:16 2010
Thread 1 advanced to log sequence 8885 (LGWR switch)
Current log# 2 seq# 8885 mem# 0: H:\ORADATA\MYDB\REDO02.LOG
Tue Jun 01 00:10:00 2010
Thread 1 advanced to log sequence 8886 (LGWR switch)
Current log# 3 seq# 8886 mem# 0: H:\ORADATA\MYDB\REDO03.LOG
Tue Jun 01 00:10:58 2010
Thread 1 advanced to log sequence 8887 (LGWR switch)
Current log# 1 seq# 8887 mem# 0: H:\ORADATA\MYDB\REDO01.LOG
Tue Jun 01 00:12:03 2010
Thread 1 advanced to log sequence 8888 (LGWR switch)
Current log# 2 seq# 8888 mem# 0: H:\ORADATA\MYDB\REDO02.LOG
Tue Jun 01 00:16:44 2010
Thread 1 advanced to log sequence 8889 (LGWR switch)
Current log# 3 seq# 8889 mem# 0: H:\ORADATA\MYDB\REDO03.LOG
Tue Jun 01 00:20:52 2010
Thread 1 advanced to log sequence 8890 (LGWR switch)
Current log# 1 seq# 8890 mem# 0: H:\ORADATA\MYDB\REDO01.LOG
Tue Jun 01 00:22:10 2010
Thread 1 advanced to log sequence 8891 (LGWR switch)
Current log# 2 seq# 8891 mem# 0: H:\ORADATA\MYDB\REDO02.LOG
Tue Jun 01 00:23:28 2010
Thread 1 advanced to log sequence 8892 (LGWR switch)
Current log# 3 seq# 8892 mem# 0: H:\ORADATA\MYDB\REDO03.LOG
Tue Jun 01 00:27:03 2010
Thread 1 advanced to log sequence 8893 (LGWR switch)
Current log# 1 seq# 8893 mem# 0: H:\ORADATA\MYDB\REDO01.LOG
Tue Jun 01 00:28:23 2010
Thread 1 advanced to log sequence 8894 (LGWR switch)
Current log# 2 seq# 8894 mem# 0: H:\ORADATA\MYDB\REDO02.LOG
Tue Jun 01 00:32:03 2010
Thread 1 advanced to log sequence 8895 (LGWR switch)
Current log# 3 seq# 8895 mem# 0: H:\ORADATA\MYDB\REDO03.LOG -
ESSSVR.exe crashes after service start
Greeting everyone,
We have a dedicated Essbase server. Today we started getting a TCP/IP protocol timeout error when trying to connect to EAS.
The first thing we noticed was the "OPMN service for Essbase" was actually running --this is the only Essbase service on this server.
At first we tried to restart the service, but the problem persisted. Then we tried to restart the server, but this didn't help neither.
Finally, we noticed that when you launch the service start (by using the oracle provided .bat files), while the service is starting, an ESSSVR.exe process shows up in the task manager, but once the service is started, the ESSSVER.exe process crashes and disappears from the task manager.
What can be wrong?
Thank you.
Regards,
G.SanchezThank you, John.
Looking at the OPMN logs, I can see the following the problem started after a scheduled service restart. Prior to it and up to 11-20-2012 at 4:00 AM, everything was fine. When the service was automatically restarted at 4:40 AM after perfoming an automated back up (which is performed daily), the logs started to show errors and warnings. I pasted them here --maybe you can give me some ideas:
opmn.log (nothing odd appears to be here)
[2012-11-20T04:01:56][opmn][TRACE:1][668][OPMN]Request 3 Completed. Command: /shutdown
[2012-11-20T04:01:56][opmn][TRACE:1][][OPMN][code:pm-requests]Http 3
EPM_epmsystem3~Essbase1~EssbaseAgent~AGENT~161747104:6416
Status: Stopped
Operation: request (time out while waiting for a managed process to stop)
ErrFile: C:\Oracle\Middleware\user_projects\epmsystem3\diagnostics\logs\OPMN\opmn\console~Essbase1~EssbaseAgent~AGENT~1.log
String: second stop attempted
EPM_epmsystem3~Essbase1~EssbaseAgent~AGENT~161747104:6416
Status: Stopped
Operation: request (success)
ErrFile: C:\Oracle\Middleware\user_projects\epmsystem3\diagnostics\logs\OPMN\opmn\console~Essbase1~EssbaseAgent~AGENT~1.log
[2012-11-20T04:01:56][opmn][TRACE:1][666][OPMN][code:pm-process]Process Stopped: Essbase1~EssbaseAgent~AGENT~1 (161747104:6416)
[2012-11-20T04:40:15][opmn][NOTIFICATION:1][90][OPMN][code:ons-internal]ONS server initiated
[2012-11-20T04:40:15][opmn][NOTIFICATION:1][522][OPMN][code:pm-internal]PM state directory exists: C:\Oracle\Middleware\user_projects\epmsystem3\config\OPMN\opmn\states
[2012-11-20T04:40:15][opmn][NOTIFICATION:1][675][OPMN][code:pm-internal]OPMN server ready. Request handling enabled.
[2012-11-20T04:40:15][opmn][TRACE:1][667][OPMN][code:pm-requests]Request 2 Started. Command: /start
[2012-11-20T04:40:15][opmn][TRACE:1][662][OPMN][code:pm-process]Starting Process: Essbase1~EssbaseAgent~AGENT~1 (161747105:0)
[2012-11-20T04:40:35][opmn][TRACE:1][662][OPMN][code:pm-process]Starting Process: Essbase1~EssbaseAgent~AGENT~1 (161747105:0)
[2012-11-20T04:40:46][opmn][TRACE:1][662][OPMN][code:pm-process]Starting Process: Essbase1~EssbaseAgent~AGENT~1 (161747105:0)
[2012-11-20T04:40:54][opmn][TRACE:1][668][OPMN][code:pm-requests]Request 2 Completed. Command: /start
*service.log*
12/11/20 04:00:48 shutdown
12/11/20 04:40:16 startproc
================================================================================
opmn id=DESHYPDB02.codere.com:6712
0 of 1 processes started.
ias-instance id=EPM_epmsystem3
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
ias-component/process-type/process-set:
Essbase1/EssbaseAgent/AGENT/
Error
--> Process (index=1,uid=161747105,pid=6612)
failed to start a managed process after the maximum retry limit
Log:
C:\Oracle\Middleware\user_projects\epmsystem3\diagnostics\logs\OPMN\opmn\console~Essbase1~EssbaseAgent~AGENT~1.log
*console~Essbase1~EssbaseAgentÃGENT~1.log* (I copy what seems to be the most relevant information)
Read Error:Fatal Error. C:\Oracle\Middleware\user_projects\epmsystem3\EssbaseServer\essbaseserver1\bin\*TEMPESSBASE.SEC is corrupt*
Fatal Error: Essbase did not shutdown cleanly. Please remove TEMPESSBASE.SEC and restart Essbase with the ESSBASE.SEC file. Some security changes could have been lost
According to this last error, shall I just remove (or back up) the TEMPESSBASE.SEC file, leave ESSBASE.SEC and try a restart?
Many thanks,
G.Sanchez -
When occurs crash recovery,why use active online redo log not archived log?
If current redo log had archived, but it's still 'ACTIVE'. As we all know, archived log is just an archived copy of the current redo log which is still 'ACTIVE', they have the same data. But why use active online redo log not archived log for crash recovery?(I think, if crash recovery can use archived log, then whether the online redo log is 'ACTIVE' or not, it can be overwritten)
Quote:
Re: v$log : How redo log file can have a status ACTIVE and be already archived?
Hemant K Chitale
If your instance crashes, Oracle attempts Instance Recovery -- reading from the Online Redo Logs. It doesn't need ArchiveLogs for Instance Recovery.
TanelPoder
Whether the log is already archived or not doesn't matter here, when the instance crashes, Oracle needs some blocks from that redolog. Archivelog is just an archived copy of the redolog, so you could use either the online or achive log for the recovery, it's the same data in there (Oracle reads the log/archivelog file header when it tries to use it for recovery and validates whether it contains the changes (RBA range) in it what it needs).Aman.... wrote:
John,
Are you sure that the instance recovery (not the media recovery) would be using the archived redo logs? Since the only thing that would be lost is the isntance, there wouldn't be any archived redo log generated from the Current redo log and the previous archived redo logs, would be already checkpointed to the data file, IMHO archived redo logs won't participate in the instance recovery process. Yep, shall watch the video but tomorrow .
Regards
Aman....
That's what I said. Or meant to say. If Oracle used archivelogs for instance recovery, it would not be possible to recover in noarchive log mode. So recovery relies exclusively on the online log.
Sorry I wasted your time, I'll try to be less ambiguous in future -
Aborting crash recovery due to error 354
Help, What do I do?
alter database open
Mon Jun 16 06:47:10 2008
Beginning crash recovery of 1 threads
Mon Jun 16 06:47:10 2008
Started redo scan
Mon Jun 16 06:47:34 2008
Errors in file c:\oraclexe\app\oracle\admin\xe\udump\xe_ora_3496.trc:
ORA-00354: corrupt redo log block header
ORA-00353: log corruption near block 18350 change 56285546348545 time 06/04/2008 13:42:02
ORA-00334: archived log: 'C:\ORACLEXE\APP\ORACLE\FLASH_RECOVERY_AREA\XE\ONLINELOG\O1_MF_2_2R411073_.LOG'
Mon Jun 16 06:47:34 2008
Aborting crash recovery due to error 354
Mon Jun 16 06:47:34 2008
Errors in file c:\oraclexe\app\oracle\admin\xe\udump\xe_ora_3496.trc:
ORA-00354: corrupt redo log block header
ORA-00353: log corruption near block 18350 change 56285546348545 time 06/04/2008 13:42:02
ORA-00312: online log 2 thread 1: 'C:\ORACLEXE\APP\ORACLE\FLASH_RECOVERY_AREA\XE\ONLINELOG\O1_MF_2_2R411073_.LOG'
ORA-354 signalled during: alter database open...
Mon Jun 16 07:09:38 2008
db_recovery_file_dest_size of 10240 MB is 0.98% used.You are certified but you don't know how to to recover a database with corrupt redo logs? There you have my problem with certificates: they don't tell you jack about the true knowledge of the DBA and his problem solving skills. (or is this exactly what you are saying with "book knowledge"? I am no native English speaker, so I might have misunderstood).
Just enter your ORA-error in a metalink search and you will find notes that explain exactly what to do (the how-to's you mention ;)) -
What are the three steps to start an instance
To start an instance, what should we do and whatâs the meaning of three steps of the oracle instance startup?
Jau-Wei Ju-Chen,
Your question is in two parts
1. To start an instance, what should we do and
2. Whatâs the meaning of three steps of the oracle instance startup
To start Oracle Instance, you would need to do the following
1. Log in sqlplus as sysdba
sqlplus /nolog
connect sys as sysdba
2. You would need to check whether the instance is runing or not. give command
show sga
3. If it shows a message "ORACLE not available", then your DB is down and you can issue command
startup
This would automatically start the instance (tells Oracle to go through all three stages of the startup process)
Three steps of the oracle instance startup
You can also start by giving
startup nomount;
alter database mount;
alter database open;
1. startup nomount
This create the SGA. Control file and datafiles are not accessed at this stage. The database is unavailable to the users
2. alter database mount
This checks the control file, collects all the information about the DB.. like what all datafiles are there and where they are kept, still the datafiles are not accessed. The database is still unavailable to the users.
3. alter database open
Using the control file, Oracle checks SCN on each datafile. If there is a mismatch, then recovery is done from redo-logs. Database is opened. From this point onwards database is available to user. Enteries in the rollback segment are rolled-back after opening the DB.
Hope this makes it more clear. -
Crash recovery: recreating invalid indexes
I want to discuss a phaenomen, which we often have saw during crash recoveries:
The "startsap db" is hanging, because after the crash recocvery itself is completed (according to db2diag.log), the connection to the database ist still hanging because the database recreate invalid indexes.
sf503:db2p02 10% db2 list utilities
ID = 2
Type = RESTART RECREATE INDEX
Database Name = P02
Partition Number = 0
Description = Recreating Invalid Index Objects
Start Time = 05/08/2007 09:37:42.721072
Sometimes this can take up to 25 minutes until this is finished and the connect is finished.
The strange thing is:
If a 2. connection to the database is made during "recreating indexes", this 2. connection is successfull and selects from t000 are successfull.
So, it is possible to execute "startsap r3" while the first connection is still blocked with recreating indexes.
I don't understand this behaviour:
- If the database really needs the recreation of invalid index objects for sucessfull database operation, then it should block ALL connections and not only the first one.
- If it's not urgently necessary, the database should done the recreating indexes in background and not block the first connection.
Also in the Recovery& High Availibility IBM Handbook I have nothing found about the "recreating invalid index objects"-feature.
Kind regards
UtaHello Jens,
thanks for the detailed answer!
As you wrote, the only workarond with changing db cfg parameter from "restart" to "access" needs some manual intervention if we don't want to risk the limit of maximum dialog runtime. So actually we will leave it as it is. We have a workaround with starting sap in a second window, when the crash recovery is finished according to db2diag.log and the 1. connection (startsap db) ist still recreating invalid indexes.
How can one determine the invalid indexes, who need recreation ?
Joachim: we don't have a real problem at our site. Fortunatelly we have crash recoveries only in the rare cases of system crashes, etc. So we are lucky not to have it every day....
Hopefully the behaviour will be changed to background index recreation in some later DB release. -
"cache recovery" vs "crash recovery" ?
Dear Friends ,
Would anybody plz tell me the difference between "cache recovery" and "crash recovery" in oracle ?
I search in google but dont get satisfactory answer ... ...shipon_97 wrote:
Dear Friends ,
Would anybody plz tell me the difference between "cache recovery" and "crash recovery" in oracle ?
I search in google but dont get satisfactory answer ... ...Crash recovery is performed whenever their is instance failure (single instance or RAC)
Crash recovery is done in two phase 1) Cache recovery 2) Transaction Recovery.
So crash recovery includes cache recovery.
Cache recovery means to apply redo log from log cache to the datafiles which may contain uncommitted transaction also.
These uncommitted transactions should be rolled back during crash recovery, and hence in transaction recovery it applied undo for all such uncommitted transaction.
Regards
Anurag -
Hi. I'm trying to help a friend but I'm not terribly experienced with laptops. She has a Toshiba Satelite L300 but when she got it and turned it on the first time she skipped the step for making the recovery discs. Now her computer has completely crashed, gets to the repair-or-boot-to-Windows screen and neither choice goes anywhere useful. I tried to boot to the last-known-successful, but that didn't work either. I found the Recovery Disc Creator for Windows Vista but I can't work out how to use it or if it's even useful on a computer this out of whack. I downloaded it, burned it onto a cd and booted her computer with it, making sure it could boot from a cd, but that didn't seem to work. I actually ran it on my own computer because I thought maybe I needed to create an image before burning it to a cd, the name did seem to suggest that, but if it created an image I don't know where it went.
I'm on the wrong track aren't I? Is there clear instructions anywhere for how to use that file? I've been trying to work this out all weekend.
Thanks in advance
j
Solved!
Go to Solution.Julanna, turn the computer on and immediately press and hold the F8 key. Can you reach the Advanced Boot Options menu? If so, choose Repair Your Computer. Can you reach the System Recovery Options menu? If so, click Startup Repair.
If you cannot reach the System Recovery Options menu, see the section Hard Disk Drive Recovery using the recovery partition, starting on p. 62 of the User's Guide.
Satellite L300 Series User’s Guide
Which Satellite L300?
-Jerry -
Starting CF instances using different jvm.config files
Hi.
There are instructions for creating/using individual JVM
configs for each
CF server instance here:
http://www.macromedia.com/cfusion/knowledgebase/index.cfm?id=tn_18206
The instructions cover starting the instance and specifying
the alternate
config via both command line, or as a Windows Service.
But what about via JRun Administrator? I see no option to
specify any
arguments for the "start" process.
(I have to concede whilst I've *started* googling for an
answer, I am being
lazy and asking here before I've got too far with it: sorry).
Adambrahms_x01, while this doesn't help the orginial poster -
have you ever considered spending $195 and calling support for
help? You'll spend _A LOT_ more than that upheaving and moving to a
new application server (which will also have its own set of unique
issues - including crashing). If all you've done is complain about
your problems on the fourms, then I've got no sympathy for you.
This isn't an official support center.
nyck6623 is on the right path. The default GC, quite frankly,
sucks. But you need to be _very_ careful switching out your GC. Do
it wrong, you can make things much worse. See these documents:
http://www.javaperformancetuning.com/
http://www.pixl8.co.uk/index.cfm/pcms/site.resources.cfmxtuning/
http://java.sun.com/performance/reference/whitepapers/tuning.html
http://java.sun.com/performance/
As always, becareful in what you do, and load test load test
load test. You also might want to look into turning on VerboseGC so
that you can see what your heap is doing. It'll write out to your
server-out.log file. That'll help you tune the JVM as well.
Finally, you might want to stop the GC from running every 60
seconds. When the GC is running, ColdFusion isn't.
Turn on VerboseGC = -verbose:gc -XX:+PrintGCDetails
-XX:+PrintGCTimeStamps -XX:+PrintHeapAtGC
Force GC = -Dsun.rmi.dgc.server.gcInterval=3600000
I'd bump your threads up to 10 or 12, and limit the cached
queries to 50. And if you can afford to do it, add some memory to
the servers so you can up your -Xmx limit. CF likes to breathe,
deeply. I've got 4GB in my servers, and I set -Xmx1024M and the
heap routinely runs around 700MB (with CF actually using around
200MB).
You might also want to consider turning on metrics so you can
see how your threads and memory are doing.
Turn on Metrics =
http://www.macromedia.com/cfusion/knowledgebase/index.cfm?id=tn_19120 -
My hard drive with library crashed, can i start on new computer with music on my touch
my hard drive with library crashed, can i start on new computer with music on my touch
The easiest way to get back missing items? Restore your whole hard drive with all your irreplaceable things like photos in about 20 minutes from the backup clone you make on a regular basis.
Your i-device was not designed for unique storage of your media. It is not a backup device and media transfer is designed for you maintaining a master copy of your media on a computer which is itself properly backed up against loss. Syncing is one way, computer to device, updating the device content to the content on the computer, not updating or restoring content on a computer. The exception is purchased content.
iTunes Store: Transferring purchases from your iOS device or iPod to a computer - http://support.apple.com/kb/HT1848 - only media purchased from iTunes Store
For transferring other items from an i-device to a computer you will have to use third party commercial software. Examples (check the web for others; this is not an exhaustive listing, nor do I have any idea if they are any good):
- Senuti - http://www.fadingred.com/senuti/
- Phoneview - http://www.ecamm.com/mac/phoneview/
- MusicRescue - http://www.kennettnet.co.uk/products/musicrescue/ - Mac & Windows
- Sharepod (free) - http://download.cnet.com/SharePod/3000-2141_4-10794489.html?tag=mncol;2 - Windows
- Snowfox/iMedia - http://www.mac-videoconverter.com/imedia-transfer-mac.html - Mac & PC
- iexplorer (free) - http://www.macroplant.com/iexplorer/ - Mac&PC
- Yamipod (free) - http://www.yamipod.com/main/modules/downloads/ - PC, Linux, Mac [Still updated for use on newer devices? No edits to site since 2010.]
- 2010 Post by Zevoneer: iPod media recovery options - https://discussions.apple.com/message/11624224 - this is an older post and many of the links are also for old posts, so bear this in mind when reading them.
Syncing to a "New" Computer or replacing a "crashed" Hard Drive - https://discussions.apple.com/docs/DOC-3141 - dates from 2008 and some outdated information now.
Copying Content from your iPod to your Computer - The Definitive Guide - http://www.ilounge.com/index.php/articles/comments/copying-music-from-ipod-to-co mputer/ - Information about use in disk mode pertains only to older model iPods.
Get Your Music Off of Your iPod - http://howto.wired.com/wiki/Get_Your_Music_Off_of_Your_iPod - I am not sure but this may only work with some models and not newer Touch, iPhone, or iPad.
Additional information here https://discussions.apple.com/message/18324797
Maybe you are looking for
-
Shutdown/reboot occasionally takes a long time - log attached
Shutting down or rebooting occasionally takes around a minute to finish. It always hangs when rebooting from gnome, but shuts down normally when gdm is disabled. Hoping somebody can help me figure out the issue. The log was generated from following t
-
Sales order Userexit to copy item text from one line item to other
Hi Gurus, I have an urgent issue. Based on item category in sales order, for one line item, I am getting item text. Now I have to copy same item text to other line item. Till now I tried save_document_prep & save_document to build object
-
What drive to choose, MacBook Pro Retina 15"
Hi, I'm considering buying a new MacBook Pro (15" 2,7 GHz quad-core, NVIDIA GeForce GT 650M / 1GB). But could you give me advice on the following. Since this MacBook has flashmemory, I wonder if it's still necessary to work with a external harddrive
-
Hi, Please explain me of what is AE NetWeaver I understand that AE is Access Enforcer Also let me know if we require any new hardware for the same. If so what are the minimum configuration
-
Why is my trackpad not working?
I updated to the Mavwricks and now my trackpad is not working. How do I fix this?