Main Note - Oracle GoldenGate - ASM
(Doc ID 1304627.1)
Last updated on NOVEMBER 04, 2019
Oracle GoldenGate - Version 5.0.0 and later Information in this document applies to any platform.
This Note offers other notes and comments on issues with ASM as relates to its usage in OGG.
When Automatic Storage Management (ASM) is in use, Oracle GoldenGate must specify in the Extract parameter file
the TRANLOGOPTIONS parameter with the DBLOGREADER option to provide access to ASM. DBLOGREADER Causes Extract to use a newer API that is available as of Oracle 10.2.0.5 and 188.8.131.52. This API uses the database server to access the redo and archive logs. The database must contain the libraries that contain the API modules and must be running hence the DB release requirements.
Previous release of the db can still use ASM but use a different TRANSLOGOPTION:
If you are running Oracle 10.2.0.4 or below Oracle 184.108.40.206, and or Oracle Goldengate 10.x,
Oracle GoldenGate requires a user for the Extract process to access the ASM instance. Oracle GoldenGate
does not support using operating-system authentication for the ASM user. You can use
SYS user or any user with SYSDBA privileges in the ASM instance and add
TRANLOGOPTIONS parameter with the ASMUSER and ASMPASSWORD options for the ASM user.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!