A customer told me today that the logs of the slave database of a core database are increasing rapidly. Through checking, alert logs continuously report errors, as shown below:
The code is as follows: |
Copy code |
Fri Dec 11 20:48:37 2015 Incomplete read from log member '/arch2/2_82548_864474703.dbf'. Trying next member. Incomplete read from log member '/arch2/2_82548_864474703.dbf'. Trying next member. Archived Log entry 101817 added for thread 2 sequence 82548 ID 0xedd14d2a dest 1: Incomplete read from log member '/arch2/2_82548_864474703.dbf'. Trying next member. Errors in file/oracle/app/oracle/diag/rdbms/crmadg/crmdb2/trace/crmdb2_ora_15304.trc (incident = 711224 ): ORA-00353: log uption near block 900532 change 14410909668198 time 12/11/2015 20:42:40 ORA-00334: archived log: '/arch2/2_82548_864474703.dbf' Errors in file/oracle/app/oracle/diag/rdbms/crmadg/crmdb2/trace/crmdb2_ora_15305.trc (incident = 711216 ): ORA-00353: log uption near block 900532 change 14410909668198 time 12/11/2015 20:42:40 ORA-00334: archived log: '/arch2/2_82548_864474703.dbf' Fri Dec 11 20:48:37 2015 Errors in file/oracle/app/oracle/diag/rdbms/crmadg/crmdb2/trace/crmdb2_ora_13484.trc (incident = 711238 ): ORA-00353: log uption near block 900532 change 14410909668198 time 12/11/2015 20:42:40 ORA-00334: archived log: '/arch2/2_82548_864474703.dbf' Fri Dec 11 20:49:13 2015 Sweep [inc] [711238]: completed |
You can view the following trace information:
The code is as follows: |
Copy code |
*** Action name :() 21:58:10. 036 Kcrfrxini: Limitread is not enabled for standby db Kcrfrxini: Limitread is not enabled for standby db Kcrfrxini: Limitread is not enabled for standby db
|
....
I Googled it and found that nothing was actually done... From the time when alert log first reported an error, I suspect it has something to do with the recently deployed goldengate.
Later I searched the keyword ORA-00353 log into uption ogg extract and found that someone on the mos Forum encountered a similar problem, the Post mentioned the use of the following parameters:
The code is as follows: |
Copy code |
TranLogOptions DBLOGREADER TranLogOptions BUFSIZE 4096000 TranLogOptions DBLOGREADERBUFSIZE 4096000 |
The environment of this brother is oracle 11.2.0.3 rac, and the ogg version is 11.2.0.1.5;
Finally, it is said that the buffersize and DBLOGREADERBUFSIZE parameters are adjusted to solve this problem. It seems that the solution has not been mentioned yet, but it has not yet appeared.
Considering that this is the Oracle 11.2.0.4 environment, although it is the ASM environment, archiving logs are stored on the local file system.
Check the goldengate extract parameter again:
The code is as follows: |
Copy code |
Ogg_eda @ xxx:/ogg_eda $./ggsci Oracle GoldenGate Command Interpreter for Oracle Version 11.2.1.0.27 19591627 OGGCORE_11.2.1.0.0OGGBP_PLATFORMS_141006.1156 HP/UX, IA64, 64bit (optimized), Oracle 11g on Oct 6 2014 13:37:58 Copyright (C) 1995,201 4, Oracle and/or its affiliates. All rights reserved. GGSCI (xxx) 2> info all Program Status Group Lag at Chkpt Time Since Chkpt MANAGER RUNNING Extract running DPEODS1 00:00:00 00:00:00 Extract running DPEODS2 00:00:00 Extract running DPEODS3 00:00:00 Extract running DPEODS4 00:00:00 00:00:08 Extract running EXTODS1 00:00:00 00:00:06 Extract running EXTODS2 00:00:00 00:00:00 Extract running EXTODS3 00:00:00 00:00:03 Extract running EXTODS4 00:00:00 00:00:03 GGSCI (xxx) 3> view param EXTODS1 EXTRACT extods1 Setenv (NLS_LANG = "AMERICAN_AMERICA.ZHS16GBK ") SETENV (ORACLE_HOME = "/oracle/app/oracle/product/11.2.0 ") SETENV (ORACLE_SID = "xxx2 ") USERID ogg_eda, PASSWORD aacaaaaaaaaaiarcqihgoiwcqjxitb, ENCRYPTKEY default Tranlogoptions altarchivelogdest primary instance crmdb2/arch2, ALTARCHIVELOGDEST primary instance crmdb1/arch2 TRANLOGOPTIONS ARCHIVEDLOGONLY Tranlogoptions altarchivedlogformat % t _ % s _ % r. dbf TranlogOptions DBLOGREADER Reportcount every 1 MINUTES, RATE DISCARDFILE./dirrpt/extods1.dsc, APPEND, MEGABYTES 1024 DBOPTIONS ALLOWUNUSEDCOLUMN WARNLONGTRANS 2 h, CHECKINTERVAL 3 m EXTTRAIL./dirdat/ods/o1 FETCHOPTIONS NOUSESNAPSHOT .....
|
Because it extracts active uplouard and only extracts archivelog, it is not necessary to add the TranlogOptions DBLOGREADER parameter.
I suspect it is related to this parameter. After blocking this parameter, no error is reported. It seems that this is an unknown bug of GoldengGate!