GGS ERROR 160 Bad column index
最近由於一個資料庫正在升級“改造”,部分表結構做了一些調整,以致GoldenGate程式出現了ABENDED狀態,下面分享一個因GoldenGate源端表結構發生變化後,引起GoldenGate目標端Replicat程式ABENDED的案例。
透過view report rep_name檢視程式ABENDED的原因,發現如下錯誤:
Using the following key columns for target table ESS.TARGET_PROJECT_DEVICE: PROJECT_DEVICE_ID.
Source Context :
SourceModule : [ggstd.conv.endian]
SourceID : [$Id: //depot/releases/OpenSys/v10.4.0/src/gglib/ggstd/lecnv.c#1 $]
SourceFunction : [convCompSQL(char *, file_def *, rowlen_t)]
SourceLine : [522]
2012-08-13 16:23:30 GGS ERROR 160 Bad column index (25) specified for table CNN.SOURCE_PROJECT_DEVICE, max columns = 25.
透過驗證Source和Target兩端的表結構,發現在源端對應的表上增加了2個欄位。因此我們嘗試在GoldenGate的Target端增加上這兩個欄位,透過如下語句完成:
alter table SCHEMA.TABLE_NAME add (col1 datatype,col2 datatype); —為保護客戶資訊,該語句為參考使用。
在目標端為表新增上相應的欄位後,即兩端的表定義完全一致,再啟動Replicat程式,基本不會有什麼問題。
來自 “ ITPUB部落格 ” ,連結:http://blog.itpub.net/25834554/viewspace-740914/,如需轉載,請註明出處,否則將追究法律責任。
相關文章
- Error: no such columnError
- ogg GGS ERROR 500 Could not find archived logErrorHive
- Index column size too large. The maximum column size is 767 bytesIndex
- 高效的SQL(index values與index column values關係?)SQLIndex
- Index column size too large. The maximum column size is 767 bytes.Index
- ORA-28348, encryption column TDE, function indexFunctionIndex
- 1709 - Index column size too large. The maximum column size is 767 bytes.Index
- GGS ERROR 190 No Minimum Supplemental Logging Is EnabledError
- [Err] 1709 - Index column size too large. The maximum column size is 767 bytes.Index
- MySQL建立表失敗:Index column size too large. The maximum column size is 767 bytesMySqlIndex
- MySQL 5.7 到 5.6,出現 Index column size too large. The maximum column size is 767 bytesMySqlIndex
- AIX: 'GGS ERROR 190 ... : Received Signal: OMVS Shutdown (33).' [ID 969596.1]AIError
- Oracle 反向索引 where index_column like '%xxx'Oracle索引Index
- mysql specified key was too long與Index column size too large. The maximum column size is 767 bytes.MySqlIndex
- MySQL資料庫index column size too large. the maximum column size is 767 bytes問題解決MySql資料庫Index
- Unknown column ‘name‘ in ‘field list‘ ; bad SQL grammar []; nested exception is com.mysql.jdbc.excepExceptionMySqlJDBC
- mysql5.7 資料匯入5.6 Index column size too large. The maximum column size is 767 bytes.MySqlIndex
- Error parsing HTTP request header--400 bad requestErrorHTTPHeader
- mysql 主從同步 Error 'Out of range value for column的問題MySql主從同步Error
- 什麼是index的leading column(索引的前導列)?Index索引
- 執行node提示:events.js:160 throw er; // Unhandled 'error' eventJSError
- mysql Index column size too large 超過767錯誤解決方案(轉)MySqlIndex
- 'mysql.column_stats' doesn't exist and Table 'mysql.index_stats' doesn't existMySqlIndex
- SQLITE_ERROR - table sap_capire_bookshop_books has no column named currencySQLiteErrorAPI
- ndo2db: mysql_error: ‘Unknown column ‘importance’ in ‘field list”MySqlErrorImport
- 解決一個小坑:error on line 1 at column 1: Document is emptyError
- ERROR 1054 (42S22): Unknown column 'plugin' in 'mysql.user'ErrorPluginMySql
- [20180608]Wrong Results with IOT, Added Column and Secondary Index.txtIndex
- MySQL ERROR 1366(HY000):Incorrect string value:''for column''at row 1解決方案MySqlError
- 安裝mysql遇到ERROR: 1136 Column count doesn't match value count at row 1MySqlError
- FatalThrowableError in index.php line 554:Type error: Argument 1 passedErrorIndexPHP
- Bad Habits
- [20180609]Wrong Results with IOT, Added Column and Secondary Index2.txtIndex
- Oracle11gr2新增提示CHANGE_DUPKEY_ERROR_INDEXOracleErrorIndex
- Failed: error reading separator after document # 1: bad JSON array format - found no opening brackAIErrorJSONORM
- 【FAQ】appium npm install error:network read ECONNRESET,bad network settings!APPNPMError
- Column Monitoring
- 11G 新特性: 新加的提示 CHANGE_DUPKEY_ERROR_INDEXErrorIndex