IC86079: ALTER TABLE VIA IFX_GRID_CONNECT RESULTS IN ERROR 19995 WHEN REPLICATE IS NOT HAVING PARTICIPANTS ON ALL GRID NODES

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as documentation error.

Error description

  • When you have a setup of three enterprise replication instances
    (ER1, ER2, ER3), two "classic" replicates defined on a table to
    do an update anywhere like this
    
    Replicate 1 defined to have participants ER1 and ER2
    Replicate 2 defined to have participants ER1 and ER3
    
    and a grid which includes nodes ER1, ER2 and ER3.
    
    Then an alter table (to add a column for example) via the grid
    (by using ifx_grid_connect()) will fail:
    
    $ dbaccess ertest - <<!EOF
    execute procedure ifx_grid_connect('grid1', 1);
    begin work;
    alter table ertab1 add (c4 char(23));
    commit;
    execute procedure ifx_grid_disconnect();
    !EOF
    
    Started transaction.
    
    
    19995: Enterprise Replication error encountered while setting
    alter mode. See message
     log file to get the Enterprise Replication error code
    Error in line 1
    Near character position 42
    
    Data committed.
    

Local fix

  • To alter the table in this setup you can either redefine your
    replicate so that it includes all grid nodes as participants or
    use mastered replicates, do the alter via the grid with 0 as
    second argument and do a remaster afterwards.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * Users of 11.70.xC7 and earlier versions.                     *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * See Error Description for  "alter table via ifx_grid_connect *
    * results in error 19995 when replicate is not having          *
    * participants on all grid nodes".                             *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * There are two methods available for adding a replicate to a  *
    * grid if the replicate has been created outside the grid.     *
    * You can use the cdr change replicateset command or put the   *
    * session into a grid context and alter the table. Before you  *
    * use either of the methods, you must ensure the following:    *
    *                                                              *
    * - All the replicate participants are members of the grid.    *
    * - Each replicate participant's information refers to the     *
    * same database, owner, table name, and SELECT statement.      *
    * - The replicated table schema is the same among all          *
    * participants.                                                *
    * - The replicate does not belong to an exclusive replicate    *
    * set.                                                         *
    * - The replicate does not include TimeSeries columns.         *
    ****************************************************************
    

Problem conclusion

  • Clarification regarding adding a replicate to a grid if the
    replicate was created outside a grid:
    
    There are two methods available for adding a replicate to a grid
    if the replicate has been created outside the grid.  You can use
    the cdr change replicateset command or put the session into a
    grid context and alter the table. Before you use either of the
    methods, you must ensure the following:
    
    - All the replicate participants are members of the grid.
    - Each replicate participant's information refers to the same
    database, owner, table name, and SELECT statement.
    - The replicated table schema is the same among all
    participants.
    - The replicate does not belong to an exclusive replicate set.
    - The replicate does not include TimeSeries columns.
    

Temporary fix

Comments

APAR Information

  • APAR number

    IC86079

  • Reported component name

    INFORMIX SERVER

  • Reported component ID

    5725A3900

  • Reported release

    B70

  • Status

    CLOSED DOC

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2012-08-22

  • Closed date

    2014-02-26

  • Last modified date

    2014-02-26

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

Fix information

Applicable component levels



Rate this page:

(0 users)Average rating

Document information


More support for:

Informix Servers

Software version:

B70

Reference #:

IC86079

Modified date:

2014-02-26

Translate my page

Machine Translation

Content navigation