GoldenGate 12.3

AYE! GoldenGate 12.3 is now released!

http://www.oracle.com/technetwork/middleware/goldengate/downloads/index.html

Capturar

What it brings?

– Support for Oracle Database 12.2.0.1
– Microservices Architecture
– Parallel Replicat
– Automatic Conflict-Detection-Resolution (CDR) without application changes
– Procedural Replication to enable simpler application migrations and upgrades
– Database Sharding
– Fast Start Capture

Let’s test this new features 🙂

Cheers!

OGG-00446 No data selecting position from checkpoint table GGATE.CHECKPOINTTABLE for group

After GoldenGate upgrade GoldenGate from 12.1 to 12.2, replicat abend with error:

ERROR OGG-00446 No data selecting position from checkpoint table GGATE.CHECKPOINTTABLE for group ‘R_CRM’, key 2028080425 (0x78e20d29), SQL .

ERROR OGG-01668 PROCESS ABENDING.

It appears replicat is not registered on CHECKPOINTTABLE (is’t true, it’s registered)

Try below:

As a workaround you can ALTER the replicat to the same checkpoint location when you do an INFO REP , DETAIL and then START.

Ex:

GGSCI (labp.grepora.net) 27> info R_CRM

REPLICAT   R_CRM     Last Started 2017-05-09 13:03   Status STOPPED
Checkpoint Lag       00:00:00 (updated 02:40:11 ago)
Log Read Checkpoint  File ./dirdat/s5000609
                     2017-07-04 10:51:44.035765  RBA 98381832


GGSCI (labp.grepora.net) 28> alter R_CRM extseqno 00609 extrba 98381832

2017-07-04 14:44:39  INFO    OGG-06594  Replicat R_CRMhas been altered through GGSCI. Even the start up position might be updated, duplicate suppression remains active in next startup. To override duplicate suppression, start R_CRM with NOFILTERDUPTRANSACTIONS option.

REPLICAT altered.


GGSCI (labp.grepora.net) 29> start R_CRM

Sending START request to MANAGER ...
REPLICAT R_CRM starting

Cheers!

ORA-00600: internal error code, arguments: [17147]

Hello all!
Having this error? Probably something like this:

ORA-00600: internal error code, arguments: [17147], [0x7F0315C53788], [], [], [], [], [], [], [], [], [], []

This is a known error. The best match on MOS is GoldenGate 12c IntRep Crash W/ ORA-600 [kghfrmrg:nxt] ;ORA-600[kghfrh:ds]; ORA 600 [17114]; [17147] (Doc ID 1666909.1)

More“ORA-00600: internal error code, arguments: [17147]”

GoldenGate ACCESSRULE – OGG-01235 Command not allowed by receiving manager process.

GoldenGate Datapump or Extract Abend with OGG-01235?

ERROR OGG-01235 Command not allowed by receiving manager process.

ERROR OGG-01668 PROCESS ABENDING.

Sounds remote GoldenGate client are denying Datapump / Extract remote connection.

Suggest check and edit GoldenGate manager parameter file.

--IPs addr from source GoldenGate Pump
ACCESSRULE, PROG *, IPADDR your.ip.addr.here, ALLOW

 Oracle documentation is good here.
Valid for Manager

Use ACCESSRULE to control connection access to the Manager process and the processes under its control. You can establish multiple rules by specifying multiple ACCESSRULE statements in the parameter file and control their priority. There is no limit to the number of rules that you can specify. To establish priority, you can either list the rules in order from most important to least important, or you can explicitly set the priority of each rule with the PRI option.

OGG-01411 – Cannot convert input file ./dirdat/xx with format RELEASE 9.0/9.5 to output file ./dirdat/zz

Hi.

If you search solutions to this Error, you will perceived only one documented root cause:

Error:

OGG-01411  Cannot convert input file ./dirdat/xx000549 with format RELEASE 9.0/9.5 to output file ./dirdat/zz000034 with format RELEASE 12.1.

Cause:

“The output trail of the data pump has a different format (version) than the input trail of the data pump”

If you are using GG 12.1 version, and all trails (rmttrail and exttrail) are correctly set with “format release”, you fell into a bug.

Oracle recommend to do upgrade to GG 12.2.

To work around this issue and start process, you need write a new trail, perform etrollover and reposition pump process.

On the Target System, process works fine, but not receive new trails, because pump process are abended.

GGSCI (lab2.grepora.net) 001> info rep01

REPLICAT rep01 Last Started 2017-03-20 12:08 Status RUNNING
Checkpoint Lag 00:00:00 (updated 00:00:09 ago)
Process ID 13563
Log Read Checkpoint File ./dirdat/zz000034
2017-03-22 09:53:31.004144 RBA 30683971

More“OGG-01411 – Cannot convert input file ./dirdat/xx with format RELEASE 9.0/9.5 to output file ./dirdat/zz”

How To Delete Archive Logs From Downstream Database

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?
check this:

GGSCI (dbcloud) 3> send ETL01 showtrans

Sending SHOWTRANS request to EXTRACT ETL01 ...

Oldest redo log files necessary to restart Extract are:
------------------------------------------------------------
XID:                  14.6.3931092
Items:                1
Extract:              ETL01
Redo Thread:          1
Start Time:           2017-00-00:00:00:00
SCN:                  1682.4049305132 (7228184297004)
Redo Seq:             8612
Redo RBA:             20965491728
Status:               Running
------------------------------------------------------------

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
e_type='DOWNSTREAM')
and purgeable='YES'
order by modified_time;
spool off

Schedule the output in automation tool (crontab / dba_job / windows job scheduler, (whatever)):