Sequences on more shemas. How to use???

Question

A big trouble using correctly sequences in oracle lite.
Since now i had only one olite publication linked to a schema on backend db, with many objects: tables, indexes, views and 5 sequences.
Example:
publication --> schema
schema.seq1, schema.seq2, ... , schema.seq5
reachable by olite client as:
db = $USER_PUBLICATION
Now i have to "duplicate" this schema and deploy another publication, adding a prefix.
Example:
new_publication -> new_schema
db = $USER_NEW_PUBLICATION
I found no problem for all objects but sequences,
because tables, index, etc had the right schema as "owner",
but i did not found any parameters like owner for sequences.
Explaining better,
i need to use the same sequence name: seq1, seq2, ..., seq5 for both publications,
referring to the right sequences on the right schema, but i'm not sure if (and how) this is possible.
Could you help me?
Thanks.
Daniele

Answer 1

we had a similar issue when we changed our application from 'standard' oracle lite (complete and fast refresh PIs) to use queue based PIs.
We did a workaound for the problem by
1) do not include the sequences at all in the second application (you get erors if you do)
2) run the following (fusionbci2 is our new application, fusionbci is the old, and fusionbci2 is effectively a clone of fusionbci)
-- fusionbci2_sequences.sql
-- associate all sequences with the fusionbci2 application
DECLARE
l_fusionbci2 VARCHAR2(30);
-- this cursor get the internal publication id for the fusionbci2 application
CURSOR c_fusionbci2 IS
SELECT name
FROM cv$all_publications
WHERE name_template LIKE 'fusionbci2%';
BEGIN
OPEN c_fusionbci2;
FETCH c_fusionbci2 INTO l_fusionbci2;
CLOSE c_fusionbci2;
-- this insert creates copies of the sequence relationship entries for the fusionbci application
-- linked to fusionbci2
INSERT INTO c$pub_objects
(pub_name
,db_name
,obj_id
,obj_type
,obj_weight)
SELECT l_fusionbci2
,'fusionbci2'
,obj_id
,obj_type
,obj_weight
FROM c$pub_objects
WHERE db_name='fusionbci'
AND obj_type='NA_SEQ';
END;
NOTE this works, but is probably not recommended by oracle, and should only be used where individual clients will only use one of the applications at a time (if they use both the sequence ranges are likely to overlap)