Please check gg log file to fix: -- BAD COLUMN INDEX issue in Oracle GoldenGate
ERROR OGG-01161 Oracle GoldenGate Delivery for Oracle, st5_rep1.prm: Bad column index (10) specified for table NIM.LSRVINFO, max columns = 10.
To FIX:
This usually means the the columns on the target and source do not match. Compare the tables on target and source to see if all columns match. Update target to match source by adding a column or removing a column or altering the size of a column, etc... In this case we needed to add a column.
gglst1d2:/appl/gg/ggs/ $ sqlplus nim_st5/nim_st5
SQL*Plus: Release 11.1.0.7.0 - Production on Fri Oct 7 08:11:05 2011
Copyright (c) 1982, 2008, Oracle. All rights reserved.
Connected to:
Oracle Database 11g Enterprise Edition Release 11.1.0.7.0 - 64bit Production
SQL> Alter table nim_st5.lsrvinfo add ORIGINALFOCDUEDATE timestamp(6);
Table altered.
ERROR OGG-01161 Oracle GoldenGate Delivery for Oracle, st5_rep1.prm: Bad column index (10) specified for table NIM.LSRVINFO, max columns = 10.
To FIX:
This usually means the the columns on the target and source do not match. Compare the tables on target and source to see if all columns match. Update target to match source by adding a column or removing a column or altering the size of a column, etc... In this case we needed to add a column.
gglst1d2:/appl/gg/ggs/ $ sqlplus nim_st5/nim_st5
SQL*Plus: Release 11.1.0.7.0 - Production on Fri Oct 7 08:11:05 2011
Copyright (c) 1982, 2008, Oracle. All rights reserved.
Connected to:
Oracle Database 11g Enterprise Edition Release 11.1.0.7.0 - 64bit Production
SQL> Alter table nim_st5.lsrvinfo add ORIGINALFOCDUEDATE timestamp(6);
Table altered.
No comments:
Post a Comment