streams errors:

################################################################################
################################################################################
#######
ORA-25333: Buffered Queue to Queue propagation did not connect to the correct in
stance
ORA-04031: unable to allocate nn bytes of shared memory
ORA-23603: STREAMS enqueue aborted due to low SGA
ORA-02063: preceding stringstring from stringstring
Cause: an Oracle error was received from a remote database link.
Action: refer to the preceding error message(s)
ORA-02063: preceding line from <name of a database link>
This also happens when a select is issued over a database link, and not a distri
buted transaction
Solution Description
--------------------
The ORA-2063 indicates that this must be done at the remote database.
Explanation
-----------
When the error is generated at the remote database it is accompanied with an
ORA-2063. In this case the parameter distributed_transactions must be increased
at the remote database.
If there is no ORA-2063 the parameter distributed_transactions must be
increased at the local database.
In a distributed environment, if a select is issued in a session without the
SET TRANSACTION READ ONLY command, the select query is considered a
distributed transaction.
If the parameter distributed_transactions is set too low, this too will result i
n an ORA-2042 and ORA-2063
It is important to note that ORA-02063 typically appears with ORA-02042

################################################################################
################################################################################
#######
ORA-26744: STREAMS capture process "CAP_WEBAPPS" does not support "IDENTITY"."C2
O_PHONE_STG" because of the following reason:
ORA-26773: Invalid data type for column "malformed redo"

ANALYSIS
~~~~~~~~~~~~
Since ddl for above mentioned table has NOLOGGING option enabled., enough redo i
nformation for the capture process was not available,
and hence CAPTURE failed with ORA-26744.
ACTION PLAN
~~~~~~~~~~~~
Recreated the affected table without NOLOGGING attribute.
################################################################################
################################################################################
#######
ORA-12801: error signaled in parallel query server P000, instance catlmsxt501.co
rp.cox.com:TATLCCO2 (2)
ORA-01688: unable to extend table SYS.STREAMS$_APPLY_SPILL_MSGS_PART partition P
10 by 128 in tablespace SYSAUX
action: increase the size of the tablespace.
################################################################################
################################################################################
#######
ORA-1280 Fatal LogMiner Error
-------------------------------
execute dbms_capture_adm.set_parameter('CAP_PROD','_SGA_SIZE','100');
################################################################################
################################################################################
#######
ORA-01732: data manipulation operation not legal on this view
-------------------------------------------------------------
Solution
1. Please set the hidden parameter in your init/spfile file and retest the worka
round.
_simple_view_merging = TRUE
2. If you have the error still in the apply error, You may re-execute the error
using.
dbms_apply.execute_error('LOCAL_TRANSACTION_ID');
---- Replace this with the real transaction id.
################################################################################
################################################################################
#######
DBMS_APPLY_ADM.SET_SCHEMA_INSTANTIATION_SCN fails with ORA-2019
---------------------------------------------------------------
Cause
This is due to Bug 4373687 SET_SCHEMA_INSTANTIATION_SCN does not error if databa
se link unavailable
The problem is due to 'RECURSIVE => TRUE' used in the package 'DBMS_APPLY_ADM.SE
T_SCHEMA_INSTANTIATION_SCN'.
Usage of 'RECURSIVE => TRUE' requires the dblink from target to source.
Note: Prior to 10.2.0.4, this error will not be reported due to Bug 4373687.
Bug 4373687 is fixed on 10.2.0.4
Solution
Create a dblink from target to source.
Now try the dbms_apply_adm.set_schema_instantiation_scn and check the behavior.

################################################################################
################################################################################
#######
alter capture process to current SCN fails with ora-03113 error:
exec dbms_capture_adm.alter_capture(capture_name=>'CAP_PROD',start_scn=>10625170
823306);
ORA-03113: end-of-file on communication channel
--------------------------------------------------------------------------------
----------------------
We have bugs logged on this behavior Bug 4100412 & Bug 6522364.
You need to run the alter command on instance which owns the queue.
SELECT q.OWNER, q.NAME, t.QUEUE_TABLE, q.enqueue_enabled,q.dequeue_enabled,t.pri
mary_instance,t.secondary_instance, t.owner_instance,
network_name, q.USER_COMMENT FROM DBA_QUEUES q, DBA_QUEUE_TABLES t WHERE t.OBJEC
T_TYPE = 'SYS.ANYDATA' AND q.QUEUE_TABLE = t.QUEUE_TABLE AND q.OWNER = t.OWNER;
ksedmp: internal or fatal error
ORA-07445: exception encountered: core dump [kwqbcresetcorr()+1902] [SIGSEGV] [A
ddress not mapped to object] [0x000000128] [] []
Current SQL statement for this session:
BEGIN dbms_capture_adm.alter_capture(capture_name=>'CAP_PROD',start_scn=>1062517
0823306); END;
---------------------------
Article-ID: Note 4100412.8
---------------------------
Title: Bug 4100412 - Dump (in kwqbcresetcorr) during capture from non-owner inst
ance
Description
ORA-600 [kwqbcresetcorr] during create capture from non-owner instance.
Workaround:
Create the capture process from the owner instance of the queue.
Bug 6522364 10.2.0.3 RDBMS 10.2.0.3 STRM CAPTURE PRODID-5 PORTID-268
Abstract: ALTERING THE START_SCN ON A NON OWNING INSTANCE - CORE DUMPS
WORKAROUND:
-----------
perform on an instance which owns the queue.
################################################################################
################################################################################
########
STREAMS PROPAGATION FAILS WITH ORA-12520 AND ORA-12541 WHEN SHUTDOWN LISTENER
WORKAROUND:
-----------
restart the listener or re-schedule the propagation
BEGIN
 DBMS_AQADM.SCHEDULE_PROPAGATION(
queue_name => 'STREAMS_ADMIN.QUEUE_NAME',
destination => '<TARGET_DB_NAME>');
END;
/
EXEC DBMS_PROPAGATION_ADM.START_PROPAGATION('PROPAGATION_NAME');
################################################################################
################################################################################
########