1. Oracle GoldenGate Classic Architecture Documentation
  2. Extract
  3. Additional Configuration Steps for Using Classic Capture
  4. Mining ASM-stored Logs in Classic Capture Mode
  5. ASM Direct Connection

ASM Direct Connection

If the RDBMS version is not one of those listed in Reading Transaction Logs Through the RDBMS, do the following:

  1. Create a user for the Extract process to access the ASM instance directly. Assign this user SYS or SYSDBA privileges in the ASM instance. Oracle GoldenGate does not support using operating-system authentication for the ASM user.
    ASM password configuration(1) Permitted user

    ASM instance and the database share a password file

    You can use the Oracle GoldenGate source database user if you grant that user SYSDBA, or you can use any other database user that has SYSDBA privileges.

    ASM instance and the source database have separate password files

    You can overwrite the ASM password file with the source database password file, understanding that this procedure changes the SYS password in the ASM instance to the value that is contained in the database password file, and it also grants ASM access to the other users in the database password file. Save a copy of the ASM file before overwriting it.

    Footnote 1 To view how the current ASM password file is configured, log on to the ASM instance and issue the following command in SQL*Plus: SQL> SELECT name, value FROM v$parameter WHERE name = 'remote_login_passwordfile';

  2. Add the ASM user credentials to the Oracle GoldenGate credential store by issuing the ALTER CREDENTIALSTORE command. See Parameters and Functions Reference for Oracle GoldenGate for usage instructions and syntax.
  3. Specify the ASM login alias in the Extract parameter file by including the TRANLOGOPTIONS parameter with the ASMUSERALIAS option. For more information about TRANLOGOPTIONS, see Parameters and Functions Reference for Oracle GoldenGate.