After deploy GoldenGate with downstream database option archives from downstream database not cleaning ? All database transaction are gracefull, but archives (from downstream) are not cleaning?
Are no log transactions registered on GG Extract?
GGSCI (dbcloud) 3> send ETL01 showtrans
Sending SHOWTRANS request to EXTRACT ETL01 ...
Oldest redo log files necessary to restart Extract are:
Redo Thread: 1
Start Time: 2017-00-00:00:00:00
SCN: 1682.4049305132 (7228184297004)
Redo Seq: 8612
Redo RBA: 20965491728
If you on same case, make this:
It should reach (and delete) JUST archived log that have already read by GoldenGate.
set serveroutput on size unlimited
set line 1000
set trimsp on
set feed off
set pages 5000
set pagesize 0
spool [[ some_dir ]]/delete_archives__dowstream_goldengate.sh
-- SR 3-14409179111 - Golden Gate Configuration, How To Delete Archive Logs From Downstream Database (Doc ID 2011174.1)
SELECT 'rm ' || r.NAME
-- case when (r.next_scn > c.required_checkpoint_scn) then 'NO' else 'YES' end purgable
FROM DBA_REGISTERED_ARCHIVED_LOG r, DBA_CAPTURE c
WHERE r.CONSUMER_NAME = c.CAPTURE_NAME and r.source_database = c.source_database and r.next_scn < ( select min(required_checkpoint_scn) from dba_capture where captur
order by modified_time;
Schedule the output in automation tool (crontab / dba_job / windows job scheduler, (whatever)):
Quick one today!
Having message below in your 126.96.36.199 on AIX like this?
WARNING: Heavy swapping observed on system in last 5 mins.
pct of memory swapped in [31.28%] pct of memory swapped out [3.81%].
Please make sure there is no memory pressure and the SGA and PGA are configured correctly.
Look at DBRM trace file for more details.
Stand down, this issue is caused by unpublished Bug 11801934, mentioned in MOS False Swap Warning Messages Printed To Alert.log On AIX (Doc ID 1508575.1).
Basically happens because the v$osstat does not reflect proper stats for the swap space paging.
So, stay calm and see you next week!
GoldenGate Extract / Replicat abend with bellow error:
Source Context :
SourceModule : [ggdb.ora.sess]
SourceID : [/scratch/aime/adestore/views/aime_stuya22/oggcore/OpenSys/src/gglib/ggdbora/ocisess.c]
SourceFunction : [OCISESS_context_def::oci_try(int, const char *, ...)]
SourceLine : 
2017-04-19 07:52:07 ERROR OGG-00665 OCI Error executing single row select (status = 3113-ORA-03113: end-of-file on communication channel)
It’s is a common stuff in Oracle Database not stable or it’s taking some 00600.
- Oracle Database alert log
- If user process has been killed
- Network communication (IPTABLES stuff)
- Server crash
Suggest you to review ‘Master Note: Troubleshooting ORA-03113 (Doc ID 1506805.1)‘ on Oracle support services and keep database away from ORA-03113.
Getting this error? OMS 188.8.131.52?
Ok… After an investigation on MOS and also a SR opened with Oracle is was pointed to relation with Bug 17575631 CLUSTER DB HOME PAGE ERRORS- REGIONS FETCH REAL TIME DATA WILL NOT BE DISPLAYED on Database Plugin.
It’s solved in OMS 184.108.40.206 and also in 220.127.116.11.1 EM Database Plugin Bundle patch.
I’ll show you how to workaround it. 🙂
Just letting you know I’ll be speaking in DBA Brasil 2.0 about Oracle Database Backup Service and specially about it use for On-Premise databases. I’ll be at room 94, from 9 to 10AM BRT.
The session is made for DBAs and Managers being focused on covering ROI, SLAs, Legal Aspect and Pros/Cons on this solution. This session includes a demo on this solution.
The participation is free! Please make your self present through: http://www.dbabr.com.br/dbabrasil2/inscricao/.
For complete list of sessions: http://www.dbabr.com.br/dbabrasil2/grade/
See you there!
This days I faced some ORA-600 as per below in a database:
ORA-00600: internal error code, arguments: , , , , , , , , , , 
Checking for error in Database I find it was related to a pretty complex UPDATE, as per:
This post is just a reflection, basically based on my last post about Adaptive Query Optimization/SQL Plan Directives. Several times we find some situations that can be solved by setting a parameter (likely a “_”) and we just proceed with an “alter system” disregarding about all the impact of this.
This is specially important when talking about “optimizer” parameters even for bugs causing ORA-600’s or performance issues… Changing those parameters in system will affect not only the SQL with the error but all SQLs in database, which may cause a really bad effect in some cases.
Ok Matheus, but what can I do?
Let’s to the obvious and generally applied methods: