1 person found this helpful
2 things which I can think of. not sure if they will work:
on target side write one more pump this will read incoming trail and write it for ur replicat.
and here on target try using GLOBALS
- not sure if this will work as target pump will also be on 12.1
if you will use format release on source, wont it will understand automatically as it has to write to lower version therefore write in 6 digit - and if not may it shd and is eligible for Oracle bug ?
example OGG 12.3 to OGG 11.2
off-course we will mention format release here. Ideally by itself it shd generate trail of 6 digit not 9 digit
Mark post helpful, correct or like it. this will help others too
Thanks , Hope the first alternative will not work since the source pump itself not coming up due to this digit issue , the target GG 12.2 wont accept the 9 digit trail coming from source 12.3 .
Regarding second alternative , Can you please share the exacgt format release parameter for 12.3 to 12.1
Also We could see below in Oracle Notes
The default behavior for FORMAT RELEASE settings supported with EXTTRAIL, RMTTRAIL, EXTFILE and RMTFILE has changed. This is due to changes need to support PDBs with Local Undos. The three bullet points below provide a summary of what has changed.
- Non-CDB databases with compatibility set to 12.1, FORMAT RELEASE 12.2 or above is supported.
- Non-CDB databases with compatibility set to 12.2, FORMAT RELEASE 12.2 or above is supported.
- CDB/PDB databases with compatibility set to 12.2, only FORMAT RELEASE 12.3 is supported. This is due to the use of local undo for PDBs, which requires augmenting the transaction ID with the PDB number to ensure uniqueness of trx IDs.