In this Document
APPLIES TO:
Oracle GoldenGate - Version 12.2.0.1.0 and later
Information in this document applies to any platform.
GOAL
In 12.2 GG version, if we use TRANLOGOPTIONS DBLOGREADER it abend with below error
2016-02-27 05:57:56 ERROR OGG-10144 Oracle GoldenGate Capture for Oracle,etest.prm: (etest.prm) line 9: Parameter [DBLOGREADER] is not valid for this configuration.
I ended disabling this parameter in extract and then it started running again.
--TRANLOGOPTIONS DBLOGREADER
While integrated extract with parameter TRANLOGOPTIONS DBLOGREADER in earlier release (12.1) never hit same issue, it just ignores.
SOLUTION
TRANLOGOPTIONS parameter to control the way that Extract interacts with the transaction log or with the API that passes transaction data, depending on the database or capture mode.
The parameter is for classic.
Snippet from 12.2 reference guide.
DBLOGREADER
(Oracle) Valid for Extract in classic capture mode.
You can remove TRANLOGOPTIONS DBLOGREADER and restart the extract. It is documented along with the checkprm utility that was new in 12.2
So how to check which goldengate parameter are valid or not in 12.2 , please use checkprm utility as below
If you run checkprm utility like below, it does not pass parameter DBLOGREADER.
GGSCI> sh checkprm /home/oracle/gg12201/dirprm/etest.prm -C extract -m integrated -V
Parameter file validation context:
component(s): EXTRACT
mode(s) : Integrated Extract
platform(s) : Linux
database(s) : Oracle 11g
/home/oracle/gg12201/dirprm/etest.prm
extract etest
userid <OGG admin> password : <password>
tranlogoptions integratedparams : (MAX_SGA_SIZE 100)
exttrail /home/oracle/gg12201/dirdat/lu
logallsupcols
updaterecordformat COMPACT
table : test.*;
(etest.prm) line 7: Parameter [DBLOGREADER] is not valid for this configuration.
2016-03-25 16:33:06 INFO OGG-10139 Parameter file /home/oracle/gg12201/dirprm/etest.prm: Validity check: FAIL.
GGSCI>
So this parameter should not be used in 12.2.
