DB 9204 + bug 3329096 vs undo
Hi!
We have two 9.2.0.4 RDBMS environments on HP PA-RISC (64 bits) machines, a production and a replication site. The replication uses the standard repcat features, there is no special customizations, and the job runs in every 10th minute (with 1-2 minutes average run time). Database upgrade is out of question because of strict application developer's supporting licenses. (Yeah, we know it's ridiculous, but we're just DB operators and admins. The new 10g-based systems maybe will start this winter.)
Our big problem is the famous "ASSM bug" (3329096). There is no patch for HP PA-RISC, so we must use the common segment_fix_status workaround if the bug kicks in (most often in the replication log tables). But we're strongly suspecting that bug affects the automatic undo management too and this problem is most serious on the replication site. As we see in v$rollstat and dba_rollback_segs views, some of the undo segments just grows and never shrinks (or just sometimes, with a small amount). Because of this, the undo tablespace always slowly increases and we not see any sign of changing
We have two 9.2.0.4 RDBMS environments on HP PA-RISC (64 bits) machines, a production and a replication site. The replication uses the standard repcat features, there is no special customizations, and the job runs in every 10th minute (with 1-2 minutes average run time). Database upgrade is out of question because of strict application developer's supporting licenses. (Yeah, we know it's ridiculous, but we're just DB operators and admins. The new 10g-based systems maybe will start this winter.)
Our big problem is the famous "ASSM bug" (3329096). There is no patch for HP PA-RISC, so we must use the common segment_fix_status workaround if the bug kicks in (most often in the replication log tables). But we're strongly suspecting that bug affects the automatic undo management too and this problem is most serious on the replication site. As we see in v$rollstat and dba_rollback_segs views, some of the undo segments just grows and never shrinks (or just sometimes, with a small amount). Because of this, the undo tablespace always slowly increases and we not see any sign of changing
0