add extract ext1,tranlog,threads 2,begin now
TRANLOGOPTIONS DBLOGREADER

2012-01-10 10:49:52 ERROR OGG-00446 Oracle GoldenGate Capture for Oracle, ext1.prm: Getting attributes for ASM file +DATA/rgst/onlinelog/redo103.log, SQL : (6550) ORA-06550: line 1, column 7: PLS-00201: identifier 'DBMS_DISKGROUP.GETFILEATTR' must be declared ORA-06550: line 1, column 7: PL/SQL: Statement ignoredNot able to establish initial position for begin time 2012-01-10 10:17:00.
2012-01-10 10:49:52 ERROR OGG-01668 Oracle GoldenGate Capture for Oracle, ext1.prm: PROCESS ABENDING.

Troubleshooting ORA-15173 in Oracle GoldenGate Extract When Reading Redo Logs on ASM [ID 1315404.1]

		修改时间 13-MAY-2011 类型 TROUBLESHOOTING 状态 PUBLISHED

In this Document
  Purpose
  Last Review Date
  Instructions for the Reader
  Troubleshooting Details

Applies to:

Middleware > Data Integration > GoldenGate
Information in this document applies to any platform.

Purpose

When redo/archived logs are on ASM, Oracle GoldenGate (OGG) extract may read them in two ways:
1. in 10.2.0.5 or up in Oracle 10g, or 11.2.0.2 in Oracle 11g, OGG version 11.1 and up extract may read the redo/archived logs from rdbms instance directly using the parameter "TRANLOGOPTIONS DBLOGREADER"

2. for other version combinations, the extract must login to the ASM instance to read the redo/archived logs on ASM.

This note describes for the setup 2., how to troubleshoot the error ORA-15173
i.e..,
2011-04-18 00:49:11 ERROR OGG-00446 Getting attributes for ASM file +REDO/oramcbta/onlinelog/group_3.268.748539783, SQL '+REDO/oramcbta/onlinelog/group_3.268.748539783', :filetype, :filesize, :lblksize); END;>: (15056) ORA-15056: additional error message
ORA-15173: entry 'oramcbta' does not exist in directory '/'

Last Review Date

April 20, 2011

Instructions for the Reader

A Troubleshooting Guide is provided to assist in debugging a specific issue. When possible, diagnostic tools are included in the document to assist in troubleshooting.

Troubleshooting Details

1. make sure the RDBMS/ASM version and OGG build match each other

2. make sure the OGG extract is logging in to the right ASM instance
e.g. with parameter: TRANLOGOPTIONS ASMUSER sys@ASM, ASMPASSWORD XYZ

To test this, perform. these actions:

(1) set the environment the same as the OGG environment

(2) test the login via sqlplus

sqlplus sys@ASM as sysdba
select instance_name from v$instance;

3. after confirming 2., restart OGG manager and restart extract

4. if 3. fails, login to ASM instance as described in step 2. and run the following pl/sql

declare
fileType varchar2(4000);
fileName varchar2(4000);
fileSz number;
blkSz number;
hdl number;
plkSz number;
data_buf raw(4096);
begin
fileName := '+REDO/oramcbta/onlinelog/group_3.268.748539783'; --- filename may need to be replaced
dbms_diskgroup.getfileattr(fileName,fileType,fileSz, blkSz);
dbms_diskgroup.open(fileName,'r',fileType,blkSz, hdl,plkSz, fileSz);
dbms_drs.sleep(5); -- sleep for 5 seconds
dbms_diskgroup.close(hdl);
end;
/

If this does not provide determination of the cause, please contact Oracle GoldenGate support by opening an SR ticket.

goldengate + asm + rac

Applies to:

Purpose

Last Review Date

Instructions for the Reader

Troubleshooting Details