I think I understand the problem.
postgres created the sequences automatically and named them token_id_seq. The problem is, that Oracle does not create sequences automatically. This is why we added them to the schema in version 2.20.
This does work fine with MySQL, MariaDB, Oracle and SQLite.
Perfect, you recreated new sequences and you have to take care about, that the new sequence number is higher than the existing one - just as you mentioned.
I would prefer to be able to rename the sequences, this would be probably the easier solution, which does not include searching for old values of the old sequences. I will have a look at that.
According to https://www.postgresql.org/docs/9.1/static/sql-altersequence.html you should also be able to do
ALTER SEQUENCE audit_id_seq RENAME TO audit_seq;
ALTER SEQUENCE caconfig_id_seq RENAME TO caconfig_seq;
ALTER SEQUENCE caconnector_id_seq RENAME TO caconnector_seq;
ALTER SEQUENCE challenge_id_seq RENAME TO challenge_seq;
ALTER SEQUENCE clientapp_id_seq RENAME TO clientapp_seq;
ALTER SEQUENCE eventhandler_id_seq RENAME TO eventhandler_seq;
ALTER SEQUENCE machineresolver_id_seq RENAME TO machineresolver_seq;
ALTER SEQUENCE machineresolverconf_id_seq RENAME TO machineresolverconf_seq;
ALTER SEQUENCE machinetoken_id_seq RENAME TO machine_seq;
ALTER SEQUENCE machtokenopt_id_seq RENAME TO machtokenopt_seq;
ALTER SEQUENCE policy_id_seq RENAME TO policy_seq;
ALTER SEQUENCE privacyideaserver_id_seq RENAME TO privacyideaserver_seq;
ALTER SEQUENCE pwreset_id_seq RENAME TO pwreset_seq;
ALTER SEQUENCE radiusserver_id_seq RENAME TO radiusserver_seq;
ALTER SEQUENCE realm_id_seq RENAME TO realm_seq;
ALTER SEQUENCE resolver_id_seq RENAME TO resolver_seq;
ALTER SEQUENCE resolverconf_id_seq RENAME TO resolverconf_seq;
ALTER SEQUENCE resolverrealm_id_seq RENAME TO resolverrealm_seq;
ALTER SEQUENCE smsgateway_id_seq RENAME TO smsgateway_seq;
ALTER SEQUENCE smsgwoption_id_seq RENAME TO smsgwoption_seq;
ALTER SEQUENCE smtpserver_id_seq RENAME TO smtpserver_seq;
ALTER SEQUENCE subscription_id_seq RENAME TO subscription_seq;
ALTER SEQUENCE token_id_seq RENAME TO token_seq;
ALTER SEQUENCE tokeninfo_id_seq RENAME TO tokeninfo_seq;
ALTER SEQUENCE usercache_id_seq RENAME TO usercache_seq;
ALTER SEQUENCE authcache_id_seq RENAME TO authcache_seq;
I will check, if these are all right. Some tables were not available in 2.19.