Skip to main content

REDO Opcode


<<Back to DB Administration Main Page

REDO Opcode 

Each change vector has an operation code. The operation code consists of a major number and a minor number.
These OPCODES are the REDO OPCODES for what layer/action occurred. Actions within each layer can be located by locating the KCOCOMP() macro. This information is the OPCODE in the REDO VECTOR.

Layer 1 : Transaction Control - KCOCOTCT             
 Opcode 1.1 : KTZ ForMaT block - KTZFMT         
 Opcode 1.2 : Transaction Z Redo Data Header - KTZRDH         
 Opcode 1.3 : KTZ Allocate Record Callback - KTZARC        
 Opcode 1.4 : KTZ REPlace record value - KTZREP        
 Opcode 1.5 : KTZ Undo for RePlace - KTZURP

Layer 2 : Transaction Read -  KCOCOTRD

Layer 3 : Transaction Update -  KCOCOTUP

Layer 4 : Transaction Block -  KCOCOTBK     [ktbcts.h]        
 Opcode 4.1 : Block cleanout opcode - KTBOPCLN        
 Opcode 4.2 : physical cleanout opcode - KTBPHCLN        
 Opcode 4.3 : single array change - KTBSARC        
 Opcode 4.4 : Multiple changes to an array - KTBMARC        
 Opcode 4.5 : format block - KTBOPFMB        
 Opcode 4.6 : commit-time block cleanout opcode - KTBOPBCC        
 Opcode 4.7 : ITL cleanout callback - KTBOPCLNL        
 Opcode 4.8 : Transaction Block Redo Block Commit Cleanout - KTBOPBCCL

Layer 5 : Transaction Undo -  KCOCOTUN     [ktucts.h]        
Opcode 5.1 : Undo block or undo segment header - KTURDB        
Opcode 5.2 : Update rollback segment header - KTURDH        
Opcode 5.3 : Rollout a transaction begin - KTURBG        
Opcode 5.4 : Commit transaction (transaction table update) - KTURCM - no undo record         
Opcode 5.5 : Create rollback segment (format) - no undo record - KTUFMT        
Opcode 5.6 : Rollback record index in an undo block - KTUIRB        
Opcode 5.7 : Begin transaction (transaction table update) - KTUUBG        
Opcode 5.8 : Mark transaction as dead - KTURMR        
Opcode 5.9 : Undo routine to rollback the extend of a rollback segment - KTUUAE        
Opcode 5.10 : Redo to perform the rollback of extend of rollback segment - KTUREH to the segment header.         
Opcode 5.11 : Rollback DBA in transaction table entry - KTUBRB         
Opcode 5.12 : Change transaction state (in transaction table entry) - KTURST        
Opcode 5.13 : Convert rollback segment format (V6 -> V7) - KTURCT        
Opcode 5.14 : Change extent allocation parameters in a rollback segment - KTURUC        
Opcode 5.15 : Undo Redo ConverT transaction table - KTURCTS        
Opcode 5.16 : KTU - Redo for ConverT to Unlimited extents format - KTURCTU        
Opcode 5.17 : KTU Redo - Convert for extent Move in extent map in - KTURCTM unlimited format to segment header        
Opcode 5.18 : Transaction Undo segment Redo set Parent Xid - KTURPX        
Opcode 5.19 : Transaction start audit log record - KTUTSL        
Opcode 5.20 : Transaction continue audit log record - KTUTSC            
Opcode 5.21 : Transaction Control Redo ConverT undo seg Down to 8.0 format- KTURCVD        
Opcode 5.22 : Transaction Redo - PHysical Changes - KTURPHC        
Opcode 5.23 : Disable Block level Recovery - KTURDBR        
Opcode 5.24 : Kernel Transaction Undo Relog CHanGe - KTURLGU        
Opcode 5.25 : Join sub Transaction - KTURJT        
Opcode 5.26 : Undo STopper undo callback - KTUUST
Opcode 5.27 : Transaction Control System Managed us Format - KTUSMFMT       
Opcode 5.28 : Undo Need To Propagate - KTUUNTP        
Opcode 5.29 : big undo - KTUBDB        
Opcode 5.30 : change ondisk state for a distributed transaction - KTURCDTS        
Opcode 5.31 : Flashback Archive Txn Table Redo Callback - KTUFATTRC        
Opcode 5.32 : Flashback Archive Txn Table Redo Set - KTUFATTRS        
Opcode 5.33 : change notification commit marker - KTUCHNF        
Opcode 5.34 : NTP bit for change notfn - KTUQCNTTRC        
Opcode 5.35 : Flashback Archive Collect Txn Table Redo Set - KTUFACTTRS

Layer 6 : Control File -  KCOCODCF     [tbs.h]        
 Opcode 6.1 : TaBleSpace Remove DataFile - TBSCRDF        
 Opcode 6.2 : TaBleSpace Add DataFile - TBSCADF        
 Opcode 6.3 : TaBleSpace OFfLine - TBSCOFL        
 Opcode 6.4 : TaBleSpace ONLine - TBSCONL        
 Opcode 6.5 : TaBleSpace ReaD-Write - TBSCRDW        
 Opcode 6.6 : TaBleSpace ReaD-Only - TBSCRDO        
 Opcode 6.7 : TaBleSpace Remove TableSpace - TBSCRTS        
 Opcode 6.8 : TaBleSpace Add TableSpace - TBSCATS        
 Opcode 6.9 : TaBleSpace Undo TsPitr - TBSCUTP        
 Opcode 6.10 : TaBleSpace undo plugged datafile convert - TBSCUCV        
 Opcode 6.11 : Tablespace Undo Rename - TBSCREN

 Layer 10 : INDEX -  KCOCODIX     [kdi.h]        
 Opcode 10.1 : load index block (Loader with direct mode) - KDICPDO        
 Opcode 10.2 : Insert leaf row - KDICLIN        
 Opcode 10.3 : Purge leaf row - KDICLPU        
 Opcode 10.4 : Mark leaf row deleted - KDICLDE        
 Opcode 10.5 : Restore leaf row (clear leaf delete flags) - KDICLRE        
 Opcode 10.6 : Lock index block - KDICLOK        
 Opcode 10.7 : Unlock index block - KDICULO        
 Opcode 10.8 : Initialize new leaf block - KDICLNE        
 Opcode 10.9 : Apply Itl Redo - KDICAIR        
 Opcode 10.10 :Set leaf block next link - KDICLNX        
 Opcode 10.11 :Set leaf block previous link - KDICLPR        
 Opcode 10.12 :Init root block after split - KDICRSP        
 Opcode 10.13 :Make leaf block empty - KDICLEM        
 Opcode 10.14 :Restore block before image - KDICIMA        
 Opcode 10.15 :Branch block row insert - KDICBIN        
 Opcode 10.16 :Branch block row purge - KDICBPU        
 Opcode 10.17 :Initialize new branch block - KDICBNE        
 Opcode 10.18 :Update keydata in row - KDICLUP        
 Opcode 10.19 :Clear row's split flag - KDICLCL        
 Opcode 10.20 :Set row's split flag - KDICLSE        
 Opcode 10.21 :General undo above the cache (undo) - KDICUGE        
 Opcode 10.22 :Undo operation on leaf key above the cache (undo) - KDICULK        
 Opcode 10.23 :Restore block to b-tree - KDICREB        
 Opcode 10.24 :Shrink ITL (transaction entries) - KDICSIT        
 Opcode 10.25 :Format root block redo - KDICFRB       
 Opcode 10.26 :Undo of format root block (undo) - KDICUFB        
 Opcode 10.27 :Redo for undo of format root block - KDICUFR       
 Opcode 10.28 :Undo for migrating block - KDICUMG        
 Opcode 10.29 :Redo for migrating block - KDICMG        
 Opcode 10.30 :IOT leaf block nonkey update - KDICLNU        
 Opcode 10.31 :Direct load root redo - KDICDLR        
 Opcode 10.32 :Combine operation for insert and restore rows - KDICCOM        
 Opcode 10.33 : Temp index redo apply - KDICTIX        
 Opcode 10.34 : Remove block from b-tree and empty block - KDICFRE        
 Opcode 10.35 :  - KDICLCU        
 Opcode 10.36 : Supplemental logging - KDICLMN        
 Opcode 10.37 : Undo of non-key updates - KDICULN        
 Opcode 10.38 : Logical non-key update - KDICICU        
 Opcode 10.39 : Branch update range - KDICBUR        
 Opcode 10.40 : Branch DBA update - KDICBDU

Layer 11 : Row Access -  KCOCODRW     [kdocts.h]        
 Opcode 11.1 : Interpret Undo Record (Undo) - KDOIUR        
 Opcode 11.2 : Insert Row Piece - KDOIRP        
 Opcode 11.3 : Drop Row Piece - KDODRP        
 Opcode 11.4 : Lock Row Piece - KDOLKR        
 Opcode 11.5 : Update Row Piece - KDOURP        
 Opcode 11.6 : Overwrite Row Piece - KDOORP        
 Opcode 11.7 : Manipulate First Column (add or delete the 1st column) - KDOMFC        
 Opcode 11.8 : Change Forwarding address - KDOCFA
 Opcode 11.9 : Change the Cluster Key Index - KDOCKI        
 Opcode 11.10 : Set Key Links- KDOSKL Change the forward & backward key links on a cluster key        
 Opcode 11.11 : Quick Multi-Insert (ex: insert as select ...) - KDOQMI        
 Opcode 11.12 : Quick Multi-Delete - KDOQMD        
 Opcode 11.13 : Toggle Block Header flags - KDOTBF        
 Opcode 11.14 : KDODSC        
 Opcode 11.15 : KDOMBC
 Opcode 11.16 : Logminer support - RM for rowpiece with only logminer columns - KDOLMN        
 Opcode 11.17 : Logminer support - RM for LOB id key information - KDOLLB        
 Opcode 11.18 : Logminer support - RM for LOB operation errors - KDOLBE        
 Opcode 11.19 : Logminer support - array updates - KDOURA        
 Opcode 11.20 : Logminer support - KDOSHK        
 Opcode 11.21 : Logminer support - KDOURP2        
 Opcode 11.22 : Logminer support - KDOCMP        
 Opcode 11.23 : Logminer support - KDODCU        
 Opcode 11.24 : Logminer support - KDOMRK        
 Opcode 11.25 : Logminer support - KDOAIR 

Layer 12 : Cluster -  KCOCODCL     [?]
   
Layer 13 : Transaction Segment -  KCOCOTSG     [ktscts.h]
 Opcode 13.1 : Data Segment Format - KTSDSF        
 Opcode 13.2 : format free list block - KTSFFB        
 Opcode 13.3 : redo for convert to unlimited extents format - KTSRCTU        
 Opcode 13.4 : fix segment header by moving its extent to ext 0 - KTSRFSH        
 Opcode 13.5 : format data block - KTSFRBFMT        
 Opcode 13.6 : set link value on block - KTSFRBLNK        
 Opcode 13.7 : freelist related fgroup/segheader redo - KTSFRGRP        
 Opcode 13.8 : freelist related fgroup/segheader undo - KTSFUGRP        
 Opcode 13.9 : undo for linking block to xnt freelist - KTSFUNLK        
 Opcode 13.10 : BITMAP - format segment header - KTSBSFO        
 Opcode 13.11 : BITMAP - format bitmap block - KTSBBFO        
 Opcode 13.12 : BITMAP - format bitmap index block - KTSBIFO        
 Opcode 13.13 : BITMAP - redo for bmb - KTSBBREDO        
 Opcode 13.14 : BITMAP - undo for BMB - KTSBBUNDO        
 Opcode 13.15 : BITMAP - redo for index map - KTSBIREDO        
 Opcode 13.16 : BITMAP - undo for index map - KTSBIUNDO        
 Opcode 13.17 : Bitmap Seg - format segment Header - KTSPHFO        
 Opcode 13.18 : Bitmap Seg - format First level bitmap block - KTSPFFO        
 Opcode 13.19 : Bitmap Seg - format Second level bitmap block - KTSPSFO        
 Opcode 13.20 : Bitmap Seg - format Third level bitmap block - KTSPTFO        
 Opcode 13.21 : Bitmap Seg - format data block - KTSPBFO        
 Opcode 13.22 : Bitmap Seg - Redo for L1 bmb - KTSPFREDO        
 Opcode 13.23 : Bitmap Seg - Undo for L1 BMB - KTSPFUNDO        
 Opcode 13.24 : Bitmap Seg - Redo for L2 bmb - KTSPSREDO        
 Opcode 13.25 : Bitmap Seg - Undo for L2 BMB - KTSPSUNDO        
 Opcode 13.26 : Bitmap Seg - Redo for L3 bmb - KTSPTREDO        
 Opcode 13.27 : Bitmap Seg - Undo for L3 BMB - KTSPTUNDO        
 Opcode 13.28 : Bitmap Seg - Redo for pagetable segment header block - KTSPHREDO        
 Opcode 13.29 : Bitmap Seg - Undo for pagetable segment header block - KTSPHUNDO        
 Opcode 13.30 : Bitmap Seg - format L1 BMB for LOB segments - KTSPLBFFO        
 Opcode 13.31 : Bitmap Seg - Shrink redo for L1 - KTSKFREDO        
 Opcode 13.32 : Bitmap Seg - Shrink redo for segment header - KTSKHREDO        
 Opcode 13.33 : Bitmap Seg - Shrink redo for extent map blk - KTSKEREDO        
 Opcode 13.34 : Bitmap Seg - Shrink undo for segment header - KTSKHUNDO        
 Opcode 13.35 : Bitmap Seg - Shrink undo for L1 - KTSKFUNDO        
 Opcode 13.36 : Bitmap Seg shrink related - KTSKSREDO        
 Opcode 13.37 : Bitmap Seg shrink related - KTSKSUNDO        
 Opcode 13.38 : Bitmap Seg shrink related - KTSKTREDO        
 Opcode 13.39 : Bitmap Seg shrink related - KTSKTUNDO        
 Opcode 13.40 : Bitmap Seg - Shrink redo for extent map blk - KTSKEUNDO        
 Opcode 13.41 : NGLOB format opcode Extent Header - KTSLEFREDO        
 Opcode 13.42 : NGLOB format opcode Persistent Undo - KTSLPFREDO        
 Opcode 13.43 : NGLOB format opcode Hash bucket - KTSLHFREDO        
 Opcode 13.44 : NGLOB format opcode Free SPace - KTSLFFREDO        
 Opcode 13.45 : NGLOB format opcode Segment Header - KTSLSFREDO        
 Opcode 13.46 : NGLOB format opcode data block - KTSLBFREDO        
 Opcode 13.47 : NGLOB block update Extent Header redo - KTSLEUREDO        
 Opcode 13.48 : NGLOB block update Extent Header undo - KTSLEUUNDO        
 Opcode 13.49 : NGLOB block update Hash Bucket redo - KTSLHUREDO        
 Opcode 13.50 : NGLOB block update Hash Bucket undo - KTSLHUUNDO        
 Opcode 13.51 : NGLOB block update Free Space redo - KTSLFUREDO        
 Opcode 13.52 : NGLOB block update Free Space undo - KTSLFUUNDO        
 Opcode 13.53 : NGLOB block update Persistent Undo redo - KTSLPUREDO
 Opcode 13.54 : NGLOB block update Persistent Undo undo - KTSLPUUNDO        
 Opcode 13.55 : NGLOB block update Segment Header redo - KTSLSUREDO        
 Opcode 13.56 : NGLOB block update Segment Header undo - KTSLSUUNDO

Layer 14 : Transaction Extent -  KCOCOTEX     [kte.h]        
 Opcode 14.1 : Unlock Segment Header - KTECUSH        
 Opcode 14.2 : Redo set extent map disk LocK - KTECRLK        
 Opcode 14.3 : redo for conversion to unlimited format - KTEFRCU        
 Opcode 14.4 : extent operation redo - KTEOPEMREDO        
 Opcode 14.5 : extent operation undo - KTEOPEUNDO        
 Opcode 14.6 : extent map format redo - KTEOPEFREDO        
 Opcode 14.7 : redo - KTECNV        
 Opcode 14.8 : undo for truncate ops, flush the object - KTEOPUTRN        
 Opcode 14.9 : undo for reformat of a ctl block - KTEFUCTL        
 Opcode 14.10 : redo to facilitate above undo - KTEFRCTL        
 Opcode 14.11 : redo to clean xids in seghdr/fgb - KTECRCLN        
 Opcode 14.12 : SMU-Retention: Redo to propagate extent commit time - KTEOPRPECT
 
Layer 15 : Table Space -  KCOCOTTS     [ktt.h]        
 Opcode 15.1 : format save undo header - KTTFSU        
 Opcode 15.2 : add save undo record - KTTSUN        
 Opcode 15.3 : move to next block - KTTNBK        
 Opcode 15.4 : point to next save undo record - KTTNAS        
 Opcode 15.5 : update saveundo blk during save undo application - KTTUSB
    
Layer 16 : Row Cache -  KCOCOQRC          

Layer 17 : Recovery (REDO) -  KCOCORCV     [kcv.h]        
 Opcode 17.1 : End Hot Backup - KCVOPEHB This operation clears the hot backup in-progress flags    in the indicated list of files         
 Opcode 17.2 : ENable Thread - KCVOPENT This operation creates a redo record  signalling that a      thread has been enabled         
 Opcode 17.3 : Crash Recovery Marker - KCVOPCRM        
 Opcode 17.4 : ReSiZeable datafiles - KCVOPRSZ        
 Opcode 17.5 : tablespace ONline - KCVOPONL        
 Opcode 17.6 : tablespace OFFline - KCVOPOFF        
 Opcode 17.7 : tablespace ReaD Write - KCVOPRDW        
 Opcode 17.8 : tablespace ReaD Only - KCVOPRDO        
 Opcode 17.9 : ADDing datafiles to database - KCVOPADD        
 Opcode 17.10 : tablespace DRoP - KCVOPDRP        
 Opcode 17.11 : Tablespace PitR - KCVOPTPR        
 Opcode 17.12 : PLUgging datafiles to database - KCVOPPLG_PRE10GR2        
 Opcode 17.13 : convert plugged in datafiles - KCVOPCNV        
 Opcode 17.14 : ADding dataFiles to database - KCVOPADF_PRE10GR2        
 Opcode 17.15 : heart-beat redo - KCVOPHBR        
 Opcode 17.16 : tablespace rename - KCVOPTRN        
 Opcode 17.17 : ENable Thread - KCVOPENT_10GR2        
 Opcode 17.18 : tablespace ONline - KCVOPONL_10GR2        
 Opcode 17.19 : tablespace OFFline - KCVOPOFF_10GR2        
 Opcode 17.20 : tablespace ReaD Write - KCVOPRDW_10GR2        
 Opcode 17.21 : tablespace ReaD Only - KCVOPRDO_10GR2        
 Opcode 17.22 : PLUgging datafiles to db - KCVOPPLG_10GR2        
 Opcode 17.23 : ADding dataFiles to database - KCVOPADF_10GR2        
 Opcode 17.24 : convert plugged in datafiles - KCVOPCNV_10GR2        
 Opcode 17.25 : Tablespace PitR - KCVOPTPR_10GR2        
 Opcode 17.26 : for file drop in tablespace - KCVOPFDP        
 Opcode 17.27 : for internal thread enable - KCVOPIEN        
 Opcode 17.28 : readable standby metadata flush - KCVOPMFL        
 Opcode 17.29 : database key creation (after bumping compatible to 11g) - KCVOPDBK        
 Opcode 17.30 : ADding dataFiles to database - KCVOPADF        
 Opcode 17.31 : PLUgging datafiles to db - KCVOPPLG        
 Opcode 17.32 : for modifying space header info - KCVOPSPHUPD        
 Opcode 17.33 : TSE Masterkey Rekey - KCVOPTMR

Layer 18 : Hot Backup Log Blocks -  KCOCOHLB     [kcb.h] / [kcb2.h]        
 Opcode 18.1 : Log block image - KCBKCOLB        
 Opcode 18.2 : Recovery testing - KCBKCORV        
 Opcode 18.3 : Object/Range reuse - KCBKCOREU

Layer 19 : Direct Loader Log Blocks - KCOCODLB     [kcbl.h]        
 Opcode 19.1 : Direct block logging - KCBLCOLB
 Opcode 19.2 : Invalidate range - KCBLCOIR        
 Opcode 19.3 : Direct block relogging - KCBLCRLB        
 Opcode 19.4 : Invalidate range relogging - KCBLCRIR             
 Opcode 19.6 : nologging standby load performance range - KCBLCNLP        
 Opcode 19.7 : nologging standby delayed block image - KCBLCNDI        
 Opcode 19.8 : op-code for ghost invalidate & new block - KCBLCONI        
 Opcode 19.9 : op-code for ghost invalidate,new blk relogging  - KCBLCONR        
 Opcode 19.10: lost write new block logging - KCBLCLWR        
 Opcode 19.11: lost write new relogging - KCBLCLRR        
 Opcode 19.12: out of band block image - fabricated only - KCBLCOBI

 Layer 20 : Compatibility Segment operations - KCOCOKCK  [kck.h]        
 Opcode 20.1 : Format compatibility segment -  KCKFCS        
 Opcode 20.2 : Update compatibility segment - KCKUCS        
 Opcode 20.3 : Update Root Dba in controlfile and file header 1 - KCKURD        
 Opcode 20.4 : Set bit in a SQL Tuning Existence Bit Vector - KCK_INV_SQL_SIG        
 Opcode 20.5 : Invalidate an SQL Statement by Signature - KCK_INV_SQL_SIG        
 Opcode 20.6 : Unauthorize cursors after sys privilege revoke - KCK_UNAUTH_CUR

 Layer 21 : LOB segment operations - KCOCOLFS     [kdl2.h]        
 Opcode 21.1 : Write data into ILOB data block - KDLOPWRI

 Layer 22 : Tablespace bitmapped file operations -  KCOCOTBF [ktfb.h]        
 Opcode 22.1 : format space header (block type=K_BTBFSH=29)  - KTFBHFO        
 Opcode 22.2 : space header generic redo - KTFBHREDO        
 Opcode 22.3 : space header undo - KTFBHUNDO        
 Opcode 22.4 : format bitmapped file space bitmap block (block type=K_BTBFSB=30) - KTFBBFO        
 Opcode 22.5 : bitmap block generic redo - KTFBBREDO 12c bigfile tablespace:        
 Opcode 22.6 : format bitmapped file space file header block (block type=K_BTBFHB=76)  - KTFBNB_HFMT            Opcode 7 : redo for bitmapped file space file header block - KTFBNB_HREDO          
 Opcode 22.8 : undo for bitmapped file space file header block - KTFBNB_HUNDO          
 Opcode 22.9 : format bitmapped file space 2nd level bitmap block (block type=K_BTBFTB=77) -KTFBNB_SFMT           
 Opcode 22.10 : redo for bitmapped file space 2nd level bitmap block - KTFBNB_SREDO          
 Opcode 22.11 : undo for bitmapped file space 2nd level bitmap block - KTFBNB_SUNDO          
 Opcode 22.12 : format bitmapped file space 1st level bitmap block (block type=K_BTBFFB=78) -KTFBNB_FFMT           
 Opcode 22.13 : redo for bitmapped file space 1st level bitmap block - KTFBNB_FREDO          
 Opcode 22.14 : undo for bitmapped file space 1st level bitmap block - KTFBNB_FUNDO          
 Opcode 22.15 : format bigfile - property map block (block type=K_BTBFPM=80) - KTFBNB_PMFMT          
 Opcode 22.16 : redo for property map block - KTFBNB_PMREDO         
 Opcode 22.17 : undo for property map block - KTFBNB_PMUNDO

Layer 23 : write behind logging of blocks - KCOCOLWR [kcbb.h]        
 Opcode 23.1 : Dummy block written callback - KCBBLWR        
 Opcode 23.2 : log reads - KCBBLRD        
 Opcode 23.3 : log DirectWrites - KCBBLDWR

Layer 24 : Logminer related (DDL or OBJV# redo) - KCOCOKRV [krv0.h]        
 Opcode 24.1 : common portion of the ddl - KRVDDL        
 Opcode 24.2 : direct load redo - KRVDLR         
 Opcode 24.3 : lob related info - KRVLOB        
 Opcode 24.4 : misc info - KRVMISC         
 Opcode 24.5 : user info - KRVUSER        
 Opcode 24.6 : direct load redo 10i - KRVDLR10          
 Opcode 24.7 : logminer undo opcode - KRVUOP        
 Opcode 24.8 : xmlredo - doc or dif - opcode - KRVXML         
 Opcode 24.9 : PL/SQL redo - KRVPLSQL         
 Opcode 24.10 : Uniform Redo Unchained - KRVURU         
 Opcode 24.11 : txn commit marker - KRVCMT         
 Opcode 24.12 : supplog marker - KRVCFF

Layer 25 : Queue Related - KCOCOQUE [kdqs.h]        
 Opcode 25.1 : undo - KDQSUN        
 Opcode 25.2 : init - KDQSIN        
 Opcode 25.3 : enqueue - KDQSEN        
 Opcode 25.4 : update - KDQSUP        
 Opcode 25.5 : delete - KDQSDL        
 Opcode 25.6 : lock - KDQSLK        
 Opcode 25.7 : min/max - KDQSMM

Layer 26 : Local LOB Related - KCOCOLOB [kdli3.h]        
 Opcode 26.1 : generic lob undo  - KDLIRUNDO        
 Opcode 26.2 : generic lob redo  - KDLIRREDO        
 Opcode 26.3 : lob block format redo - KDLIRFRMT        
 Opcode 26.4 : lob invalidation redo  - KDLIRINVL        
 Opcode 26.5 : lob cache-load redo  - KDLIRLOAD        
 Opcode 26.6 : direct lob direct-load redo - KDLIRBIMG        
 Opcode 26.7 : dummy calibration redo  - KDLIRCALI

 Layer 27 : Block Change Tracking - KCOCOBCT [krc2.h]        
 Opcode 27.1 : op-code for bitmap switch - KRCPBSW

Layer 28 : Pluggable database - KCOCOPDB [kpdb0.h]        
 Opcode 28.1 : Undo create pdb  - KPDBUCRT        
 Opcode 28.2 : Undo drop pdb  - KPDBUDRPP        
 Opcode 28.3 : Undo drop tablespace (part of drop pdb) - KPDBUDRPT        
 Opcode 28.4 : Undo drop file (part of drop pdb)  - KPDBUDRPF        
 Opcode 28.5 : Undo rename pdb  - KPDBURNM        
 Opcode 28.6 : Undo open pdb - KPDBUOPN        
 Opcode 28.7 : Undo close pdb  - KPDBUCLS

Comments

  1. 난항상November 25, 2021 at 1:41 AM

    Hello, I found new OP Code, OP 11.28. but I don't know what it is. could you tell me what it is ?

    ReplyDelete

Post a Comment

Popular posts from this blog

How to Power On/off Oracle Exadata Machine

<<Back to Exadata Main Page How to Power On/off Oracle Exadata Machine Oracle Exadata machines can be powered on/off either by pressing the power button on front of the server or by logging in to the ILOM interface. Powering on servers using  button on front of the server The power on sequence is as follows. 1. Start Rack, including switches  Note:- Ensure the switches have had power applied for a few minutes to complete power on  configuration before starting Exadata Storage Servers 2.Start Exadata Storage Servers  Note:- Ensure all Exadata Storage Servers complete the boot process before starting the   database servers 3. Start Database Servers Powering On Servers Remotely using ILOM The ILOM can be accessed using the Web console, the command-line interface (CLI), IPMI, or SNMP. For example, to apply power to server dm01cel01 using IPMI, where dm01cel01-ilom is the host name of the ILOM for the server to be powered on, run the
Post a Comment
Read more

ORA-28374: typed master key not found in wallet

<<Back to Oracle DB Security Main Page ORA-46665: master keys not activated for all PDBs during REKEY SQL> ADMINISTER KEY MANAGEMENT SET KEY FORCE KEYSTORE IDENTIFIED BY xxxx WITH BACKUP CONTAINER = ALL ; ADMINISTER KEY MANAGEMENT SET KEY FORCE KEYSTORE IDENTIFIED BY xxxx WITH BACKUP CONTAINER = ALL * ERROR at line 1: ORA-46665: master keys not activated for all PDBs during REKEY I found following in the trace file REKEY: Create Key in PDB 3 resulted in error 46658 *** 2019-02-06T15:27:04.667485+01:00 (CDB$ROOT(1)) REKEY: Activation of Key AdnU5OzNP08Qv1mIyXhP/64AAAAAAAAAAAAAAAAAAAAAAAAAAAAA in PDB 3 resulted in error 28374 REKEY: Keystore needs to be restored from the REKEY backup.Aborting REKEY! Cause: All this hassle started because I accidently deleted the wallet and all wallet backup files too and also forgot the keystore password. There was no way to restore the wallet back. Fortunately in my case the PDB which had encrypted data was supposed to be deco
7 comments
Read more

How to Find VIP of an Oracle RAC Cluster

<<Back to Oracle RAC Main Page How to Find Out VIP of an Oracle RAC Cluster Login clusterware owner (oracle) and execute the below command to find out the VIP hostname used in Oracle RAC $ olsnodes -i node1     node1-vip node2     node2-vip OR $ srvctl config nodeapps -viponly Network 1 exists Subnet IPv4: 10.0.0.0/255.255.0.0/bondeth0, static Subnet IPv6: Ping Targets: Network is enabled Network is individually enabled on nodes: Network is individually disabled on nodes: VIP exists: network number 1, hosting node node1 VIP Name: node1-vip VIP IPv4 Address: 10.0.0.1 VIP IPv6 Address: VIP is enabled. VIP is individually enabled on nodes: VIP is individually disabled on nodes: VIP exists: network number 1, hosting node node2 VIP Name: node2-vip VIP IPv4 Address: 10.0.0.2 VIP IPv6 Address: VIP is enabled. VIP is individually enabled on nodes: VIP is individually disabled on nodes:
1 comment
Read more

ORA-16905: The member was not enabled yet

<<Back to Oracle DataGuard Main Page ORA-16905 Physical Standby Database is disabled DGMGRL> show configuration; Configuration - DG_ORCL1P   Protection Mode: MaxPerformance   Members:   ORCL1PP - Primary database     ORCL1PS - Physical standby database (disabled)       ORA-16905: The member was not enabled yet. Fast-Start Failover:  Disabled Configuration Status: SUCCESS   (status updated 58 seconds ago) DGMGRL> DGMGRL> enable database 'ORCL1PS'; Enabled. DGMGRL>  show configuration; Configuration - DG_ORCL1P   Protection Mode: MaxPerformance   Members:   ORCL1PP - Primary database     ORCL1PS - Physical standby database Fast-Start Failover:  Disabled Configuration Status: SUCCESS   (status updated 38 seconds ago)
Post a Comment
Read more

How to Switch Log File from All Instances in RAC

<<Back to Oracle RAC Main Page Switch The Log File of All Instances in Oracle RAC. In many cases you need to switch the logfile of the database. You can switch logfile using alter system switch logfile command but if you want to switch the logfile from all the instances you need to execute the command on all the instances individually and therefore you must login on all the instances. You can avoid this and switch logfile of all instances by just running the below command from any of the instance in RAC database SQL> ALTER SYSTEM SWITCH ALL LOGFILE;   System altered.
Post a Comment
Read more

ORA-65104: operation not allowed on an inactive pluggable database alter pluggable database open

<<Back to DB Administration Main Page ORA-65104: operation not allowed on an inactive pluggable database SQL> alter pluggable database TEST_CLON open; alter pluggable database TEST_CLON open * ERROR at line 1: ORA-65104: operation not allowed on an inactive pluggable database Cause The pluggable database status was UNUSABLE. It was still being created or there was an error during the create operation. A PDB can only be opened if it is successfully created and its status is marked as NEW in cdb_pdbs.status column SQL> select PDB_NAME,STATUS from cdb_pdbs; PDB_NAME             STATUS -------------------- --------------------------- PDB$SEED             NORMAL TEST_CLON            UNUSABLE Solution:  Drop the PDB and create it again. Related Posts How to Clone Oracle PDB (Pluggable Database) with in the Same Container
Post a Comment
Read more

ORA-46630: keystore cannot be created at the specified location

<<Back to DB Administration Main Page ORA-46630: keystore cannot be created at the specified location CDB011> ADMINISTER KEY MANAGEMENT CREATE KEYSTORE '+DATAC4/CDB01/wallet/' IDENTIFIED BY "xxxxxxx"; ADMINISTER KEY MANAGEMENT CREATE KEYSTORE '+DATAC4/CDB01/wallet/' IDENTIFIED BY "EncTest123" * ERROR at line 1: ORA-46630: keystore cannot be created at the specified location Cause  Creating a keystore at a location where there is already a keystore exists Solution To solve the problem, use a different location to create a keystore (use ENCRYPTION_WALLET_LOCATION in sqlnet.ora file to specify the keystore location), or move this ewallet.p12 file to some other location. Note: Oracle does not recommend deleting keystore file (ewallet.p12) that belongs to a database. If you have multiple keystores, you can choose to merge them rather than deleting either of them.
Post a Comment
Read more

Starting RMAN and connecting to Database

  <<Back to Oracle Backup & Recovery Main Page Starting RMAN and connecting to Database Starting RMAN and connecting to Database To start RMAN you need to set the environment and type rman and press enter. You can connect to database either using connect command or using command line option. using command line option localhost:$ export ORACLE_HOME=/ora_app/product/18c/dbd2 localhost:$ export PATH=$ORACLE_HOME/bin:$PATH localhost:$ export ORACLE_SID=ORCL1P localhost:$ rman target / Recovery Manager: Release 18.0.0.0.0 - Production on Sun Apr 4 08:11:01 2021 Version 18.11.0.0.0 Copyright (c) 1982, 2018, Oracle and/or its affiliates.  All rights reserved. connected to target database: ORCL1P (DBID=4215484517) RMAN> using connect option localhost:$ rman RMAN> connect target sys@ORCL1P  target database Password:******** connected to target database: ORCL1P (DBID=4215484517) NOTE: To use connect command you need to ensure that  you have proper TNS sentry for database (ORCL
Post a Comment
Read more

How to Attach to a Datapump Job and Check Status of Export or Import

<<Back to Oracle DATAPUMP Main Page How to check the progress of  export or import Jobs You can attach to the export/import  job using ATTACH parameter of oracle datapump utility. Once you are attached to the job you check its status by typing STATUS command. Let us see how Step1>  Find the Export/Import Job Name You can find the datapump job information from  DBA_DATAPUMP_JOBS or  USER_DATAPUMP_JOBS view. SQL> SELECT OWNER_NAME,JOB_NAME,OPERATION,JOB_MODE,STATE from DBA_DATAPUMP_JOBS; OWNER_NAME JOB_NAME                       OPERATION            JOB_MODE   STATE ---------- ------------------------------ -------------------- ---------- ---------- SYSTEM     SYS_EXPORT_FULL_02             EXPORT               FULL       EXECUTING OR You can also find the job name for export/import in logfile in beginning itself. Step2>Attach to the Job and check status One you get the Export/Import Job Name attach the job and check its status. You can attach or det
7 comments
Read more

Step by Step how to Create Virtual Machine using Virtualbox

<<Back to Linux Main Page How to Create New Virtual Machine Using Oracle Virtual Box Step1:   Open Oracle Virtual Box --> Click New Provide Name, Type and Version as shown in the image below and click Next  Step2:  Adjust memory (RAM) as per the requirement and availability   and click Next.  NOTE:- Remember to leave enough memory for the host OS to work properly.  Step3:   Select the option to create a new virtual hard drive and click "Create"  (erzeugen) button.  Step4:  Accept Default and click next (weiter)   Step5: Accept the dynamically allocated option by clicking the "Next" (weiter) button.  Step6:  If you don't want to use the defaults, enter the required location, name and size of the virtual disk and click the "Create" (erzeugen) button. Note:- At this point your virtual machine is created and ready for OS installation Preparing the Virtual machine for Oracle RAC Installation Step1:   Select t
Post a Comment
Read more