Exadata: Large trace Files On Physical Standby (Doc ID 1577013.1)

Last updated on SEPTEMBER 26, 2013

Applies to:

Oracle Exadata Hardware - Version 11.2.0.3 and later
Exadata Database Machine V2 - Version All Versions and later
Exadata Database Machine X2-8 - Version All Versions and later
Exadata Database Machine X2-2 Hardware - Version All Versions and later
Exadata X3-2 Hardware - Version All Versions and later
Information in this document applies to any platform.

Symptoms

On Physical Standby huge  trace files are generated. Apparently, the information in the files is related to function [kdstProcessSageData].This fills up whole os file partition and cause disk space issues. Content is repeated with the following information:

 

Sample output:
=========
kcbl_sage_block_check: rdba: 222013433 rdba_kcbh: 222013434 buf:0xf8902130
flag: 0x 5 frmt: 0xa2 data_len: 639128 bsz: 8192
kcbl_sage_block_check: rdba: 222013434 rdba_kcbh: 222013435 buf:0xf8904130
flag: 0x 5 frmt: 0xa2 data_len: 639128 bsz: 8192
kcbl_sage_block_check: rdba: 222013435 rdba_kcbh: 222013436 buf:0xf8906130
flag: 0x 5 frmt: 0xa2 data_len: 639128 bsz: 8192
kcbl_sage_block_check: rdba: 222013436 rdba_kcbh: 222013437 buf:0xf8908130
flag: 0x 5 frmt: 0xa2 data_len: 639128 bsz: 8192
kdstProcessSageData : unknown opcode - 0
kdstProcessSageData : unknown opcode - 0



Cause

Sign In with your My Oracle Support account

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

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms