My Oracle Support Banner

High CPU Utilization and Archivelog Generation When Starting Streams Capture Process (Doc ID 259949.1)

Last updated on MARCH 07, 2019

Applies to:

Oracle Database - Enterprise Edition - Version 9.2.0.4 to 9.2.0.4 [Release 9.2]
Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Database Cloud Exadata Service - Version N/A and later
Information in this document applies to any platform.

NOTE: In the images and/or the document content below, the user information and data used represents fictitious data from the Oracle sample schema(s) or Public Documentation delivered with an Oracle database product. Any similarity to actual persons, living or dead, is purely coincidental and not intended in any manner.

Symptoms

When starting a Streams capture process, the following symptoms are noted:

1) CPU utilization spikes to high levels.
A check of OS processes reveals that it is the Oracle user that is consuming the CPU.

2) Archivelogs are generated at a very high rate, and continue to generate even if left to run
for a long time.

3) APPLIED_SCN in the DBA_CAPTURE view does not increment, forcing the retention of
the archivelogs.

4) Transactions at the capture site are no longer propagated to the apply site.

5) Using LogMiner (see <Note:111886.1> for instructions on how to user LogMiner) on one
of the archivelogs reveals the statement similar to the following repeated over and over, filling
the archivelogs:


SQL> select timestamp, username, sql_redo
from v$logmnr_contents
where rownum < 1000;

TIMESTAMP USERNAME SQL_REDO
-------------- --------------- ---------------------------------
11-DEC-03
set transaction read write;

11-DEC-03
select * from "SYS"."AQ$_SCHEDULES"
where ROWID = 'AAAA5AAABAAACAqAAB' for update;

11-DEC-03
update "SYS"."AQ$_SCHEDULES"
set
"LAST_RUN" = TO_DATE('21-NOV-03', 'DD-MON-RR'),
"JOBNO" = '71177',
"FAILURES" = '4',
"DISABLED" = 'N',
"ERROR_TIME" = TO_DATE('10-DEC-03', 'DD-MON-RR'),
"LAST_ERROR_MSG" = 'ORA-06550:
line 1, column 36: PLS-00553: character set name is not recognized
ORA-06550: line 0, column 0, PL/SQL: Compilation unit analysis terminated',
"CUR_START_TIME" = TO_DATE('20-NOV-03',
'DD-MON-RR'), "NEXT_RUN" = NULL, "PROCESS_NAME" = 'J000',
"SID" = '19',
"SERIAL" = '1254',
"TOTAL_TIME" = '6',
"TOTAL_MSGS" = '58',
"TOTAL_BYTES" = '37177',
"TOTAL_WINDOWS" = '1',
"WIN_MSGS" = '58',
"WIN_BYTES" = '37177',
"MAX_NUM_PER_WIN" = '58',
"MAX_SIZE" = '37177',
"SPARE1" = '50'
where "LAST_RUN" = TO_DATE('21-NOV-03', 'DD-MON-RR')
and "JOBNO" = '71177'
and "FAILURES" = '4'
and "DISABLED" = 'N'
and "ERROR_TIME" = TO_DATE('10-DEC-03', 'DD-MON-RR')
and "LAST_ERROR_MSG" = 'ORA-06550: line 1, column 36: PLS-00553: character set name is not recognized
ORA-06550: line 0, column 0: PL/SQL: Compilation unit analysis terminated'
and "CUR_START_TIME" = TO_DATE('20-NOV-03', 'DD-MON-RR')
and "NEXT_RUN" IS NULL
and "PROCESS_NAME" = 'J000'
and "SID" = '19'
and "SERIAL" = '1254'
and "TOTAL_TIME" = '6'
and "TOTAL_MSGS" = '58'
and "TOTAL_BYTES" = '37177'
and "TOTAL_WINDOWS" = '1'
and "WIN_MSGS" = '58'
and "WIN_BYTES" = '37177'
and "MAX_NUM_PER_WIN" = '58'
and "MAX_SIZE" = '37177'
and "SPARE1" = '50'
and ROWID = 'AAAA5AAABAAACAqAAB';

11-DEC-03
commit;


6) ORA-600 errors may also be reported in the alert log, though this has not been noted in
every occurrence:

ORA-600: internal error code, arguments: [kwqpbqdeqr: !qobjorspse], [], [], [], [], [],
ORA-600: internal error code, arguments: [kwqpspscflg: !elem], [], [], [], [], [], [], []

Changes

This problem can occur after upgrade to 9.2.0.4 and a database stop and restart.

Cause

To view full details, 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 a vibrant support community of peers and Oracle experts.