Manually modify ‘sequence’ setting - Manually modify ‘sequence’ setting - Saperion ECM - Saperion - Saperion-ECM/Saperion/Foundation-EP7/Saperion-Update-Guide/Migrate-from-previous-versions-to-Foundation-EP7/Manually-modify-sequence-setting - Foundation EP7 - Foundation EP7

Saperion Update Guide
Platform
Saperion ECM
Product
Saperion
Release
Foundation EP7
License
ft:lastPublication
2026-03-26T12:00:19.359000
ft:locale
en-US

Since version 8.x, Saperion needs sequences for counterfields at database server. Use of table xuid, which contains all counters, is no longer supported.

When you upgrade from 7.5.6, the sequence setting in the previous version is retained. If you are using an Oracle or MSSQL database, ensure that the value for the "sequence" parameter is set to TRUE. If the value is FALSE, it must be changed manually.

Note: It is recommended that you contact Professional Services to manually update the sequence setting. However, the steps to modify this setting is mentioned in this section for your convenience.

To manually update the sequence setting, complete the following steps.

  1. Stop Java Core Server.
  2. In the archief.ini file, verify the following setting. 
    archief.ini
[odbc.setup32.<dsn>]
Sequence=TRUE
  3. Verify that XID values in xuid table are equal to max(counterfield) in indextable.
  4. Create statements for sequences:
    • For Oracle
      SELECT 'create sequence "SEQ_' || upper(replace
(XCONTEXT, '.', '_')) || '" cache 1 start with ' || to_char( + 1) ||' maxvalue 99999999999 
increment by 1;' FROM XUID;
    • For MSSQL
      SELECT concat('create table ','SEQ_', upper(replace([XCONTEXT], '.', '_')),
 '(SeqID int identity(',[XID]+1,',1) primary key, SeqUUID varchar(33));') FROM [XUID];select concat
( 'create index [SeqUUID] on [','SEQ_' + upper(replace([XCONTEXT], '.', '_')),'] ([SeqUUID]);') FROM [XUID];
  5. Rename xuid table.
  6. Start Java Core Server.