While adding columns on source and on target (with replicate DDL on) This will cause ORA-01430: column being added already exists in table.
Event log:
10/11/06 13:42 Notice: ORA-01430: column being added already exists in
table. [sp_opst(osp)/23771]
10/11/06 13:42 Internal error: Poster exit on 9i ddl error due to
ORA-01430: column being added already exists in table. on ALTER TA
BLE DMD_PROD.DACC_ATTRIBUTES ADD(MEDIAFLO VARC... [sp_opst (for
o.dmdqa1-o.dmdqa queue dmdqa1)/23771]
DDL messages are stuck in the post queue as they DDL operation was already performed on the target.
Set the SP_OPO_CONT_ON_ERR parameter and ignore the ORA-01430 error so post continues posting on the target. Once the messages have been posted then you can unset this parameter.
SP_OPO_CONT_ON_ERR parameter controls whether or not Post stops when it encounters Oracle errors that can be corrected. It can be changed from the default of 0 (stop on Oracle errors) to 1, which instructs SharePlex to ignore the error messages and continue posting. Before changing the setting to 1, be sure to add the Oracle error number to the oramsglist file on the target system. This file is in the data sub-directory in the SharePlex variable-data directory.
To set up the parameter, follow these steps:
1. Stop Post.
sp_ctrl> stop post
2. Open the oramsglist file on the target system and increase the number on the first line by one
(This number tells SharePlex how many error messages are in the file).
3. At the end of the file, add the message number of the Oracle error 1430 Post should bypass:
4. sp_ctrl>set param SP_OPO_CONT_ON_ERR 1
sp_ctrl>set param SP_OPO_STOP_ON_DDL_ERR 0
5. Start Post.
Post will not stop when it encounters ORA-01430
6. Once the error has been bypassed, unset by (sp_ctrl> reset param SP_OPO_CONT_ON_ERR & sp_ctrl> reset param SP_OPO_STOP_ON_DDL_ERR ).
.
The steps in resolution will ignore all DDL that fail with ORA-01430. This can cause problems if one wants to retain other DDL that have ORA-01430 and one would like to correct the underlying database issues instead of ignoring the problem DDLs. To selectively ignore a single DDL contact support for assistance.
© 2024 Quest Software Inc. ALL RIGHTS RESERVED. Feedback Terms of Use Privacy Cookie Preference Center