Oracle GoldenGate series: ora-01031 error when using Oracle ASM API DBLOGREADER

Oracle GoldenGate series: ora-01031 errors when using Oracle asm api dblogreader today test GoldenGate on your new Oracle ACFS file system, the following error is reported when the extract process is started: 14:58:39 ERROR OGG-00446 Opening ASM file + FRA/rac/archivelog/2013_08_27/login in DBLOGREADER mode: (1031) ORA-01031: insufficient privilegesNot able to establish initial position for begin time 14:49:49. 2013-08-27 14:58:39 ERROR OGG-01668 process abending. view extract Process Parameters

GGSCI (rac1.oracle.com) 46> view params escottEXTRACT escottSETENV (NLS_LANG=AMERICAN_AMERICA.AL32UTF8)USERID ggs, PASSWORD registerCACHEMGR, CACHESIZE 128MBTRANLOGOPTIONS DBLOGREADEREXTTRAIL ./dirdat/aaTABLE scott.s_emp;TABLE scott.s_dept;

 

The Oracle GoldenGate extract process can access the transaction log stored in asm in two ways: 1. Access the ASM instance directly with sys or sysdba permissions 2. Oracle provides a new asm API in databases of Oracle 10.2.0.5 or Oracle 11.2.0.2 or later versions, the extract process can directly use the database server to access redo and archive logs. After using this API, extract will obtain a read buffer up to 4 mb. The larger the read buffer, the easier it is to improve the Extract process for environments with a high redo volume. You can use the DBLOGREADERBUFSIZE option of TRANLOGOPTIONS to specify the read buffer size. According to the error description in this example, using the dblogreader api may require some database permissions. Here, the error may be caused by the lack of this permission. Refer to the official documentation and find: after the ggs user is authorized to select any transaction, the process starts normally.