Consultor Eletrônico

Status: Verified

SYMPTOM(s):

Error 2913 when dumping new sequence CURRENT-VALUE's from Target database

Unknown sequence expression <new_sequence name>. (2913)

Error 2913 only for CURRENT-VALUE of sequences that have been added to the source database after enablesitereplication

Error 2913 displaying CURRENT-VALUE of a sequence in target database

FACT(s) (Environment):

Any records that are created on the source db with a new sequence have the correct CURRENT-VALUE sequence recorded in the target database .d
Any new records created with these new sequences are visible in the TARGET database (and .d) with the correct CURRENT-VALUE.
Once the TARGET database has been transitioned, CURRENT-VALUE are dumped for the new sequences
Existing CURRENT-VALUE of sequence at creation of TARGET db do not produce error 2913 when dumped.
Any new sequences are visible in the TARGET schema _sequence.df
All Supported Operating Systems
OpenEdge Replication
Fathom Replication

CAUSE:

Bug# OE00106935

FIX:

Suggested workaround:

If the reason that data are being dumped from the TARGET database are to create a new production database on a new server, the full set of sequence current values (SCV) are therefore not needed until the source database on the new server is put into production.

Action Plan:
1.) Continue the daily dump of .d and incremental.df files from the TARGET database, thereby relieving the stress on the live database. Since this database is not being used in production, no new records are being created so the correct next sequence value is not needed and the daily dump of .d's contain the correct scv's.
2.) When the database on the new server needs to be put into production, transition the target database and perform a final dump of .d's, incremental.df and the full set of sequence current values will be available for loading onto the new server so that when this database is put into production all new records using these scv's will have the correct 'next sequence number.'