My Oracle Support Banner

Database Session Hangs with 'cr Request Retry' (Doc ID 2260686.1)

Last updated on MARCH 22, 2024

Applies to:

Oracle Database Cloud Exadata Service - Version N/A and later
Oracle Database Backup Service - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Database Cloud Service - Version N/A and later
Oracle Database - Enterprise Edition - Version 10.2.0.2 to 11.1.0.7 [Release 10.2 to 11.1]
Information in this document applies to any platform.

Symptoms


One of the application session got hang with "'cr request retry' " and repeatedly going to same block and file.


.10046 trace for the session and saw it is spinning on same objects and block.

 

WAIT #2: nam='cr request retry' ela= 1 file#=2492 block#=567711 p3=0 obj#=417646 tim=1492719728895117
WAIT #2: nam='cr request retry' ela= 2 file#=2492 block#=567711 p3=0 obj#=417646 tim=1492719728895315

 

 

grant 0xc8ce897b0 cvt (nil) send (nil),0 write (nil),0@-1
flag 0x0 mdrole 0x1 mode 1 scan 0 role LOCAL
disk: 0x0000.00000000 write: 0x0000.00000000 cnt 0x0 hist 0x0
xid 0x0000.000.00000000 sid 1 pkwait 0s rmacks 0 weak: 0x0000.00000000
pkey 644803 tsn 0 stat 0 masters[32767, 0->0] reminc 24 RM# 1650 flg x0 type x0
hv 42 [stat 0x0, 1->1, wm 32767, RMno 0, reminc 24, dom 0]
kjga st 0x4, step 0.0.0, cinc 24, rmno 1869, flags 0x0
lb 0, hb 0, myb 38195, drmb 38195, apifrz 0
GCS SHADOW 0xc8ce897b0,8 resp[0xc8baea430,0x8a99f.9bc0000] pkey 644803
grant 1 cvt 0 mdrole 0x1 st 0x140 GRANTQ rl LOCAL
master 0 owner 1 sid 1 remote[0x64ffea4b8,53] hist 0x9f3e7cf9f3e7cf9f
history 0x1f.0x1f.0x1f.0x1f.0x1f.0x1f.0x1f.0x1f.0x1f.0x1.
cflag 0x0 sender 0 flags 0x0 replay# 0
disk: 0x0000.00000000 write request: 0x0000.00000000
pi scn: 0x0000.00000000 sq[0xc8baea458,0xc8baea458]
msgseq 0x1 updseq 0x0 reqids[53,0,0] infop (nil)
GCS SHADOW END
GCS RESOURCE END
kjbmbassert [0x8a99f.9bc0000]
2017-04-20 14:26:59.115314 : kjbmsassert(0x8a99f.9bc0000)(1)
<-ksedsts()+315<-kjbhistory()+650<-kjbcropen()+1677<-kclscrs()+757<-kclgclks()+2728<-kcbz_multi_file_get_locks()+1134<-kcbzib()+27706<-kcbgtcr()+11998<-ktecgetsh()+7780<-ktecgshx()+34<-kxfrExtInfo()+873<-kxfrialo()+1043<-kxfralo()+301<-qerpx_rowsrc_start()+1649
<-qerpxStart()+261<-selexe0()+1064<-opiexe()+17728<-kpoal8()+2551<-opiodr()+1220<-ttcpip()+1227<-opitsk()+1449<-opiino()+1026<-opiodr()+1220<-opidrv()+580<-sou2o()+90<-opimai_real()+145<-ssthrdmain()+177<-main()+215<-__libc_start_main()+244<-_start()+412017-04-20 14:29:02.166858 : kjbhistory[0x8a99f.9bc0000,(pkey 644803)(where 1)]

*** 2017-04-20 14:29:02.166

 

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Cause
Solution


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.