再次遭遇oracle BUG–6704410

     昨天完成了logical standby的建制，運行在預設模式最大效能模式，今天試著修改為最大可用模式時，發現主要資料庫報如下錯誤。上google,baidu均未找到答案。上metalink上查詢，發現一筆記錄，曰是oracle 的BUG.Oracle仍未提供修正程式，也沒有解決方式，又給改回最大效能模式。
錯誤如下：
LGWR: Error 4030 disconnecting from destination LOG_ARCHIVE_DEST_2 standby host 'its'
Tue Feb 05 13:12:36 2008
Errors in file d:\it\dump\bdump\it_lgwr_3508.trc:
ORA-04030: out of process memory when trying to allocate  bytes (,)

LGWR: Error 4030 creating archivelog file 'its'
LGWR: Failed to archive log 1 thread 1 sequence 35 (4030)
Thread 1 advanced to log sequence 35

metalink原文如下：
Bug No. 6704410
Filed 19-DEC-2007 Updated 24-JAN-2008
Product Oracle Server - Enterprise Edition Product Version  10.2.0.3
Platform Microsoft Windows Server 2003 R2 (64-bit AMD64 and Intel EM64T) Platform Version No Data
Database Version 10.2.0.3 Affects Platforms  Generic
Severity  Severe Loss of Service Status Duplicate Bug. To Filer
Base Bug 5618471 Fixed in Product Version No Data

Problem statement:

RFS PROCESS ACQUIRE HUGE MEMORY.
--------------------------------------------------------------------------------

  *** 12/19/07 12:18 am *** TAR: ---- . PROBLEM: -------- In customer's site, when instance of primary node 2 starts up, RFS process acquire huge memory. . -- result of v$sesstat. SPID   PROGRAM               SID NAME                          MEMORY ------ ------------------ ------ ------------------------- ---------- 7152   ORACLE.EXE (SHAD)     410 session pga memory        2284412296 < -- 7152   ORACLE.EXE (SHAD)     410 session pga memory max    2284412296 7152   ORACLE.EXE (SHAD)     410 session uga memory            158464 7152   ORACLE.EXE (SHAD)     410 session uga memory max        158464 . Moreover, lgwr of primary nodes face the following error and lgwr can not transfer redo log. .     Fri Dec 07 22:09:15 2007     LGWR: Error 4030 disconnecting from destination LOG_ARCHIVE_DEST_2       standby host 'LIFE_DR'     Fri Dec 07 22:09:15 2007     Errors in file ....     ORA-04030: .... . DIAGNOSTIC ANALYSIS: -------------------- . WORKAROUND: ----------- N/A . RELATED BUGS: ------------- . REPRODUCIBILITY: ---------------- . TEST CASE: ---------- N/A . STACK TRACE: ------------ . SUPPORTING INFORMATION: ----------------------- . 24 HOUR CONTACT INFORMATION FOR P1 BUGS: ---------------------------------------- . DIAL-IN INFORMATION: -------------------- . IMPACT DATE: ------------ . *** 12/19/07 12:22 am *** *** 12/19/07 05:49 pm *** (CHG: Sta-&gt;16) *** 12/19/07 06:01 pm *** (CHG: Asg-&gt;NEW OWNER) *** 12/21/07 12:02 am *** (CHG: Sta-&gt;10) *** 12/21/07 12:02 am *** *** 01/14/08 06:52 pm *** (CHG: Sta-&gt;16) *** 01/14/08 06:52 pm *** *** 01/15/08 11:10 pm *** (CHG: Sta-&gt;10) *** 01/15/08 11:10 pm *** *** 01/20/08 06:34 pm *** (CHG: Sta-&gt;16) *** 01/20/08 06:34 pm *** *** 01/20/08 09:42 pm *** (CHG: Sta-&gt;11 SubComp-&gt;DATAGUARD_PSBY) *** 01/20/08 09:42 pm *** *** 01/20/08 09:43 pm *** *** 01/20/08 09:43 pm *** (ADD: Impact/Symptom-&gt;MEMORY/OTHER RESOURC... *** 01/20/08 09:45 pm *** *** 01/20/08 09:45 pm *** (CHG: Asg-&gt;NEW OWNER) *** 01/20/08 09:45 pm *** *** 01/21/08 01:46 am *** (CHG: Confirmed Flag-&gt;Y) *** 01/21/08 01:46 am *** (CHG: Asg-&gt;NEW OWNER) *** 01/21/08 01:46 am *** *** 01/23/08 07:14 am *** *** 01/23/08 08:49 am *** *** 01/24/08 06:05 am *** *** 01/24/08 07:16 am *** (CHG: Sta-&gt;36) *** 01/24/08 07:16 am *** *** 01/24/08 07:53 am ***