Sequence creation in DB

I Want to store collection id in a table column through a sequence
The sequence should start from CL00001 , CL00002 , etc
Can we write a sequence in which it includes alphabets also

SQL>
SQL> CREATE Sequence seq_test
2      MINVALUE 1
3      MAXVALUE 999999999999999999999999999
4      START WITH 1
5      INCREMENT BY 1
6      CACHE 20;
Sequence created
SQL> select seq_test.nextval from dual;
   NEXTVAL
         1
SQL> select 'CL0000'||seq_test.nextval from dual;
'CL0000'||SEQ_TEST.NEXTVAL
CL00002
SQL> /
'CL0000'||SEQ_TEST.NEXTVAL
CL00003
SQL> /
'CL0000'||SEQ_TEST.NEXTVAL
CL00004
SQL> /
'CL0000'||SEQ_TEST.NEXTVAL
CL00005
SQL>

Similar Messages

Sequence Creation Date

Is there a way to see the sequence creation or modification date on Premiere Pro?

Maybe I'm doing something wrong but In my machine I can't see neither Creation or Modification Date for my sequences.
Is there something I have to change?
Thanks in Advance,
v

Sequence creation for Super Type and Sub Type (Parent-Child)

Data Model is structured with Super Type-Sub Type Concept.When data is being inserted in the Super Type table, I will be using a sequence Supertype.NEXTVAL as Primary Key.Now the same sequence will be the Primary Key for Sub Type table also. Can I use Supertype.CURRVAL during insertion in Sub Type table?
If Yes, I have lot of records being created in Super Type table within a second. So before data is being inserted in Subtype table there may be chance of a row being inserted in Super Type table and if I use Supertype.CURRVAL it may lead to wrong data.
How can I make sure that Supertype Primary Key is being inserted as Primary key in sub type table?

What happens when you try it? Something like:
session1> select t_seq.nextval from dual;
   NEXTVAL
     40061
session2> select t_seq.nextval from user_objects;
   NEXTVAL
     40062
     40063
     40064
     <snip>
     40270
     40271
     40272
211 rows selected.
session1> select t_seq.currval from dual;
   CURRVAL
     40061john

Regarding Sequence creation

i have tried to create a sequence like 'e0001', 'e0002','e0003',.........'e0010'............ 'e0100'....... using concatenation operator in insert statement.
But the problem m facing is how it will automatically use the remaining zeros as it increments.. plz help

may be like this
select 'e'||lpad(seq.nextval,4,'0') from dual;Vivek L

About runtime sequence creation and view dare pre commmit.

Dear All,
My 2 New Question are:
1)Could Oracle suggest to create sequence(DDL) from run-time.That means I need(My client requirement) regenerate of sequence(I know it is possible by cycle but i don't know MAX value when it will cycle)as monthly or a specific time so I want to drop sequence and create sequence by a)Programmetically runtime
b) Oracle scheduler runtime .
Have any good and better Idea? Any risk factor?
Note that at a time possibly more than 100 users will data entry with our software.
2)My New query is Could I view table data which was not yet COMMITTED from other session-other user.
Regards and Thanking you,
ZAKIR
Analyst ,
SynesisIT,
www.Synesisit.com
=====

I tried that, but there are too many trouble.
For only references.
-- Usage
Procedures
　execute periodic_seq.seq_def   create sequence
　execute periodic_seq.seq_undef drop sequence
Functions
　　periodic_seq.nextvalue
　　　get nextval of specified sequence
　　periodic_seq.currvalue
　　　get currval of specified sequence
seq_def
　in_seq_name varchar2 (30)
    sequence name (current schema)
　in_trunc_unit varchar2
　　'yyyy','mm','dd','hh24','mi' : format on trunc(date)
seq_def
　in_owner varchar2 (30)
　　schema name
　in_seq_name varchar2 (30)
　　sequence name
　in_trunc_unit varchar2
　　'yyyy','mm','dd','hh24','mi' : format on trunc(date)
　incr_by integer (default:1)
　　increment by
　start_with integer (default:1)
　　start with
　maxvalue integer (default:to_number('1e27'))
　　maxvalue
　minvalue integer (default:1)
　　minvalue
　cycle varchar2 (default:'N')
　　'Y':cycle/'N':nocycle
　cache integer (default:20)
　　cache
　time_order varchar2 (default:'N')
　　'Y':order/'N':noorder
seq_undef
　in_seq_name varchar2 (30)
    sequence name (current schema)
seq_undef
　in_owner varchar2 (30)
　　schema name
　in_seq_name varchar2 (30)
　　sequence name
nextvalue
　in_seq_name varchar2 (30)
    sequence name (current schema)
nextvalue
in_owner varchar2 (30)
　　schema name
　in_seq_name varchar2 (30)
　　sequence name
currvalue
　in_seq_name varchar2 (30)
    sequence name (current schema)
currvalue
in_owner varchar2 (30)
　　schema name
　in_seq_name varchar2 (30)
　　sequence name
-- Source --
-- Control table
create table cycle_seq_ctrl
(sequence_name varchar2(30) not null
,min_value integer
,max_value integer
,increment_by integer not null
,cycle_term varchar(10) default('dd') not null
,last_number integer not null
,reset_time date
,prev_nextval integer not null
,constraint pkey_cycle_seq_ctrl primary key (sequence_name)
organization index
create or replace
package cycle_seq
authid current_user
is
function nextvalue
(seq_name varchar2
,in_date date := sysdate
) return integer
function currvalue
(seq_name varchar2
) return integer
procedure seq_def
(seq_name varchar2
,cycleterm varchar2 := 'DD' /* Defaults : reset by a day */
,incr_by integer := 1
,start_with integer := 1
,maxvalue integer := to_number('1e27')
,minvalue integer := 1
procedure seq_undef
(seq_name varchar2
end; -- package cycle_seq
create or replace
package body cycle_seq
is
type currval_tab_type is table of integer index by varchar2(30);
currval_tab currval_tab_type;
function nextvalue
(seq_name varchar2
,in_date date := sysdate
) return integer
is
pragma autonomous_transaction;
timeout_on_nowait exception;
timeout_on_wait_sec exception;
pragma exception_init(timeout_on_nowait, -54);
pragma exception_init(timeout_on_wait_sec, -30006);
p_seqname cycle_seq_ctrl.sequence_name%type;
p_ctrl cycle_seq_ctrl%rowtype;
p_currtime date;
p_nextval integer;
begin
p_currtime := in_date;
p_seqname := upper(trim(seq_name));
select *
    into p_ctrl
    from cycle_seq_ctrl
   where sequence_name = p_seqname
for update wait 1
if (p_ctrl.cycle_term<>'SS') then
    p_currtime := trunc(p_currtime,p_ctrl.cycle_term);
end if;
-- need to reset
if (p_ctrl.reset_time < p_currtime) then
    if (p_ctrl.increment_by > 0) then
      p_nextval := p_ctrl.min_value;
    elsif (p_ctrl.increment_by < 0) then
      p_nextval := p_ctrl.max_value;
    else
      p_nextval := p_ctrl.last_number;
    end if;
    update cycle_seq_ctrl
      set last_number = p_nextval
         ,reset_time = p_currtime
         ,prev_nextval = last_number + increment_by
    where sequence_name = p_seqname
    currval_tab(p_seqname) := p_nextval;
    commit;
    return p_nextval;
end if;
-- already reseted (in a same second)
if (p_ctrl.reset_time = p_currtime) then
    p_nextval := p_ctrl.last_number + p_ctrl.increment_by;
    update cycle_seq_ctrl
      set last_number = p_nextval
    where sequence_name = p_seqname
    currval_tab(p_seqname) := p_nextval;
    commit;
    return p_nextval;
-- already reseted
else
    p_nextval := p_ctrl.prev_nextval + p_ctrl.increment_by;
    update cycle_seq_ctrl
      set prev_nextval = p_nextval
    where sequence_name = p_seqname
    currval_tab(p_seqname) := p_nextval;
    commit;
    return p_nextval;
end if;
exception
when no_data_found then
    raise_application_error(-20800,
       'cycle_seq.seq_def('''||seq_name
       ||''') has not been called.');
when timeout_on_nowait or timeout_on_wait_sec then
    raise_application_error(-20899,
       'cycle_seq.nextvalue('''||seq_name
       ||''') is time out.');
when others then
    raise;
end
function currvalue
(seq_name varchar2
) return integer
is
p_seqname cycle_seq_ctrl.sequence_name%type;
begin
p_seqname := upper(trim(seq_name));
return currval_tab(upper(seq_name));
exception
when no_data_found then
    raise_application_error(-20802,
       'cycle_seq.nextvalue('''
       ||seq_name||''') has not been called in this session.');
when others then
    raise;
end
procedure seq_def
(seq_name varchar2
,cycleterm varchar2 := 'DD'
,incr_by integer := 1
,start_with integer := 1
,maxvalue integer := to_number('1e27')
,minvalue integer := 1
is
p_seqname cycle_seq_ctrl.sequence_name%type;
p_currtime date;
p_cycleterm cycle_seq_ctrl.cycle_term%type;
begin
p_currtime := sysdate;
p_seqname := upper(trim(seq_name));
p_cycleterm := upper(trim(cycleterm));
if (p_cycleterm<>'SS') then
    p_currtime := trunc(p_currtime,cycleterm);
end if;
insert into cycle_seq_ctrl
    (sequence_name
    ,min_value
    ,max_value
    ,increment_by
    ,cycle_term
    ,last_number
    ,reset_time
    ,prev_nextval
values
    (p_seqname
    ,minvalue
    ,maxvalue
    ,incr_by
    ,p_cycleterm
    ,start_with - incr_by
    ,p_currtime
    ,start_with - incr_by
commit; -- Because this is as like a DDL
exception
when dup_val_on_index then
    raise_application_error(-20955,
       'already defined with '
      ||'cycle_seq.seq_def('''||seq_name||''')');
when others then
    raise;
end
procedure seq_undef
(seq_name varchar2
is
p_seqname cycle_seq_ctrl.sequence_name%type;
begin
p_seqname := upper(trim(seq_name));
delete from cycle_seq_ctrl
where sequence_name = p_seqname
commit; -- Because this is as like a DDL
end
end; -- package body cycle_seq
/

Sequence creation

I want to create a sequence which start from the value in a table.
Like, create sequence seq1 start with (select max(seq_values) from sequence_table)
How to specify this type of dynamic value in "start with" clause?
Thanks in Advance
Aji

> I want to create a sequence which start from the value in a table.
A very strange request. You mind explaining your requirement, as the solution you've chosen is flawed?
Remember that the only purpose of a sequence is to deliver a unique number. Nothing else. Not sequential gap free numbers. Not numbers with a specific meaning.
A sequence is intended to be used for surrogate keys. Relational design is very specific that a surrogate key only requirement is that it is unique. Nothing more.
By attempting to build (dynamic?) sequences from a table is by all sounds, a very flawed solution. If you can tell the forum your requirement instead, maybe the forum can provide alternative/working solutions instead.

Issue in creation of group in oim database through sql query.

hi guys,
i am trying to create a group in oim database through sql query:
insert into ugp(ugp_key,ugp_name,ugp_create,ugp_update,ugp_createby,ugp_updateby,)values(786,'dbrole','09-jul-12','09-jul-12',1,1);
it is inserting the group in ugp table but it is not showing in admin console.
After that i also tried with this query:
insert into gpp(ugp_key,gpp_ugp_key,gpp_write,gpp_delete,gpp_create,gpp_createby,gpp_update,gpp_updateby)values(786,1,1,1,'09-jul-12',1,'09-jul-12',1);
After that i tried with this query.but still no use.
and i also tried to assign a user to the group through query:
insert into usg(ugp_key,usr_key,usg_priority,usg_create,usg_update,usg_createby,usg_updateby)values(4,81,1,'09-jul-12','09-jul-12',1,1);
But still the same problem.it is inserting in db.but not listing in admin console.
thanks,
hanuman.

Hanuman Thota wrote:
hi vladimir,
i didn't find this 'ugp_seq'.is this a table or column?where is it?
It is a sequence.
See here for details on oracle sequences:
http://www.techonthenet.com/oracle/sequences.php
Most of the OIM database schema is created with the following script, located in the RCU distribution:
$RCU_HOME/rcu/integration/oim/sql/xell.sql
there you'll find plenty of sequence creation directives like:
create sequence UGP_SEQ
increment by 1
start with 1
cache 20
to create a sequence, and
INSERT INTO UGP (UGP_KEY, UGP_NAME, UGP_UPDATEBY, UGP_UPDATE, UGP_CREATEBY, UGP_CREATE,UGP_ROWVER, UGP_DATA_LEVEL, UGP_ROLE_CATEGORY_KEY, UGP_ROLE_OWNER_KEY, UGP_DISPLAY_NAME, UGP_ROLENAME, UGP_DESCRIPTION, UGP_NAMESPACE)
VALUES (ugp_seq.nextval,'SYSTEM ADMINISTRATORS', sysadmUsrKey , SYSDATE,sysadmUsrKey , SYSDATE, hextoraw('0000000000000000'), 1, roleCategoryKey, sysadmUsrKey, 'SYSTEM ADMINISTRATORS', 'SYSTEM ADMINISTRATORS', 'System Administrator role for OIM', 'Default');
as a sequence usage example.
Regards,
Vladimir

ORA-04016 - Sequence no longer exists

Hi,
In the below scenario
1. All the sequences are dropped
2. When a process requires a value from a sequence and the sequence is not available, it is created and then a sequence.nextval is executed.
This statement is returning a ORA-04016 - Sequence <XXX> no longer exists.
Based on the following Metalink 1300837.1, we tried putting a sleep(5) between the sequence creation and fetch. The problem still occurs intermittently.
DB Version is 11.2.0.2 on Exadata with 6 nodes.
Even after an extensive search on the web, I could not find anything.
Is there any workaround for this or is there some DB patch to be applied?
Thanks

Have you tried sleeping for longer?
Alternative approaches that spring to mind are:
1) Ensure that the statements that create the sequence and those that subsequently use it are executed on the same node when executed in close succession.
2) Trap the error and retry in your code.
I'd be inclined to favour suggestion 1 if possible in your environment.
Is your code in PL/SQL?

Sequencing and Trigger on Oracle 9i lite database

We created a schema (TESTSCHEMA) on Oracle 8.1.7 Enterprise edition and have a created a trigger which will use the sequence object to generate primary key for the table (TEST_TABLE)
Sequence creation:
CREATE SEQUENCE TESTSCHEMA.TEST_TABLE_SEQUENCE START WITH 6000 INCREMENT BY 1 MINVALUE 6000 MAXVALUE 6999 NOCACHE NOCYCLE NOORDER ;
Trigger creation:
CREATE OR REPLACE TRIGGER TEST_TABLE INSERT BEFORE INSERT ON TEST_TABLE FOR EACH ROW
DECLARE
pkValue NUMBER;
BEGIN
pkValue := 0;
Select TEST_TABLE_SEQUENCE.NextVal into pkValue from dual;
:NEW.TEST_KEY := pkValue;
END TEST_TABLE_INSERT;
We have created a snapshot of the schema on mobile server, synchronized the data with the client (Win32 for testing purpose).
The trigger works fine on the server, but when I run the same query on the lite database with msql it gives me an error:
[POL-3221] null key in primary index
I was wondering if Sequence generation and Triggers are supported on Oracle 9i lite database ? Or am I missing out something ??
Any information/ help is appreaciated
Thanks
Neeraj

You can't use SAVEPOINT / ROLLBACK TO SAVEPOINT statements in the database trigger:
ORA-04092: cannot SET SAVEPOINT in a trigger
ORA-04092: cannot ROLLBACK in a trigger
I am not sure what you need exactly, but you can try this:
Simulating ROLLBACK TO SAVEPOINT Behavior in a Database Trigger
http://www.quest-pipelines.com/pipelines/plsql/tips02.htm#JUNE
Regards,
Zlatko Sirotic

Dynamic link problem, PPro cs5 - AE cs5, multi-cam sequence

This is odd. I'm working on a two camera interview in Production Premium CS5. Did the standard stuff - a source sequence with both cameras, did some rough editing here (syncing the two cameras, trimming the clips, etc.). Then nested the source sequence into a multi-cam edit sequence. Used the multi-cam monitor to switch back and forth between cameras, etc. All is good.
But my editor wants to make three separate videos from this interview. So the logical thing (so I thought anyway) would be to nest this muiti-cam edit squence into three separate target sequences. Then I could get the camera switching done just once, and slice-'n-dice the three target sequences to make the short-'n-sweet individual videos that make my editor happy. Did this for the first target (a single question and answer). The result looks fine in PPro, and editor approves. All that's left is adding the lower thirds.
Everything fine until I go to export to AE via dynamic link so I can add lower thirds and finish up. What PPro sends to AE isn't just my target sequence, but it also sends the multi-cam edit sequence and the source sequence as well. But.... it ignores it all and will only show me the Acam footage. Bcam doesn't show up at all. Clearly this isn't working. But now I find that I can't even break the links. So I can't even start over. Sigh...
Two questions: First, how does one export a multi-cam edit sequence via dynamic link from PPro to AE, and have it show up in AE looking like it does in PPro? In other words, what did I do wrong?
Second, how can I recover from this? Do I really have to delete my target sequence in PPro and start over (and by extension, delete the AE project also)? Is there no way to sever a dynamic link once it's made?
Bruce Watson

Um.... didn't work. Seems that AE and PPro have different ideas of what "transparency" mean. The lower thirds composition in AE has a transparent (black) background which works fine in AE (I've used this lower thirds quite a bit in AE so I know it works pretty well), but when I import it into PPro it shows as white, and is completely opaque. Lettering doesn't show up either (but the letters are white so that's not such a surprise given the background), but the motion is still there. None-the-less, either way I tried it (copy and paste, or export from AE as a PPro project, then import it in PPro and drag the AE built sequence to the timeline) didn't work.
Trying to export just the lower third comp from AE through dynamic link as a PPro project didn't work either. Failed weirdly. It popped up the right sequence creation box in PPro, so I could pick AVCHD 1080p30 as the sequence type (matching the other sequences in the project), and created the new sequence with the correct name. But the sequence was empty. It wouldn't let me drag the lower third sequence anywhere either, so I couldn't put it on a timeline.
Sigh... this isn't supposed to be this difficult. But hey, if it was easy anyone could do it, yes?

Reset sequence after data import

Hi all,
I've got a problem where we import data into a table with an auto-incremented field for a primary key. After the data import, I can drop the sequence, check the max(primary key), and re-create it to start at the max value + 1. My problem is that I need to do this for a large number of tables and don't know how to write a script to do it. In the Create Sequence command, whenever I try to use a variable in the "START WITH" clause, I get an error.
Thanks in advance,
Raymond

Spool sequence creation scipt result in a file and then run it.
Or use dynamic sql.
Or You can "drive" sequence forward issuing select myseq.nextval from dual; apropriate times. If You need "drive" sequence backwards alter it with increment -1, issue select myseq.nextval from dual; apropriate times and alter it with previous increment.

Golden Gate Sequence Value replication?

Hi all,
I have searched the web, and read the Golden Gate documentation but I've found mixed answers.
I'm just trying to ascertain for certain whether it's possible to automatically replicate sequence values in a bi-directional configuration. Both databases will be identical and both will be 11gR2 with the latest version of GG.
If it is not possible to automatically increment sequences in a bi-directional configuration, what are the best practices for maintaing them?
One option is the alternate sequences on each database, one with even values (for example) and one with odd values, but this requires deployment of new sequences on both databases, something we were hoping would be taken care of by the replication. (yes the sequence creation can be taken care of but the value is not incremented on the target database).
another way that we thought of off the top of our heads is to have an on insert trigger (we only use sequences to generate surrogate keys) which will select nextval from the target database via a db link, but this seems somewhat cumbersome.
What is best practice?

Use sequence parameter... here is from Golden gate document:
SEQUENCE
Valid for Extract
Use the SEQUENCE parameter to extract sequence values from the transaction log forpropagation to a GoldenGate trail and delivery to another database. Currently, GoldenGate supports sequences for the Oracle database.
NOTE DDL support for sequences (CREATE, ALTER, DROP, RENAME) is compatible with, but not required for, replicating sequence values. To replicate just sequence values, you do not need to install the GoldenGate DDL support environment. You can just use the SEQUENCE parameter.
GoldenGate ensures that the values of a target sequence are:
● higher than the source values if the increment interval is positive
● lower than the source values if the increment interval is negative
Depending on the increment direction, Replicat applies one of the following formulas as a test when it performs an insert:
source_highwater_value + (source_cache_size * source_increment_size * source_RAC_nodes) <= target_highwater_value
Or...
source_highwater_value + (source_cache_size * source_increment_size * source_RAC_nodes) >= target_highwater_value
If the formula evaluates to FALSE, the target sequence is updated to be higher than the source value (if sequences are incremented) or lower than the source value (if sequences are decremented). The target must always be ahead of, or equal to, the expression in the parentheses in the formula. For example, if the source highwater value is 40, and CACHE is 20, and the source INCREMENTBY value is 1, and there are two source RAC nodes, the target highwater value should be at least 80:
40 + (20*1*2) <80
If the target highwater value is less than 80, GoldenGate updates the sequence to increase the highwater value, so that the target remains ahead of the source. To get the current highwater value, perform this query:
SELECT last_number FROM all_sequences WHERE sequence_owner=upper('SEQUENCEOWNER') AND sequence_name=upper('SEQUENCENAME');

AIR Help - Why is Print Sequence Disabled?

Hi all,
I have experimented with a copy of a client's Help system in
both RH7 w/packager and the RH8 trial, generating output to the AIR
Help format. After generating & installing the .air package,
and viewing the new .exe help file, I notice the following: Click
the dropdown next to the Print icon and three options are listed
(Print this page, Print sequence, Print entire Help). No matter
what is selected below, Print sequence is always unavailable
(grayed out). This is the case when I generate with either version.
Am I missing something in the settings?
Thanks,
Katie
Katie Carver
Senior Technical Writer
Docs-to-You, LLC

Hi all
In addition to what my colleague and fellow Adobe Community
Expert Peter suggested, I read this thread and am inferring that
perhaps Katie doesn't fully understand how Browse Sequences work.
Particularly in WebHelp. So I see this could impact the operation
of things.
Please allow me to try and explain.
A Browse Sequence is merely a pre-defined path that traverses
two or more topics so that they are presented in a logical order.
You said that you created a Browse Sequence using the Auto-create
feature so I'm assuming you now have several different sequences.
This is because until you change the number of Book levels, you end
up with several sequences. If you wanted a single sequence that
spanned all of the TOC, you would need to auto-create the sequence
and specify 0 as the book levels.
That bit will hopefully help you sort the sequence creation.
Now let's address the sequence *USE*.
When you have created WebHelp output by clicking File >
Generate Primary Layout (assuming the primary is WebHelp) you see
four or five intermediate dialogs that allow you to specify
different parameters that govern how that layout is created.
Typically on the second dialog is an option for Browse Sequences.
So once you have created a sequence, you have to remember to enable
it in WebHelp in order to see it work. At this point, I'm thinking
you *MAY* have done this but it isn't clear. After all, if you have
never used them before, you may not have realized you needed to do
this step. You also may not realize how the sequence appears in
WebHelp.
So once you have defined the sequence and told WebHelp to
present it, you generate and the sequence is presented as two icons
in the "Navigation mini-toolbar". The little toolbar that sits
majestically perched at the top of the TOC, Index, Search, Glossary
and just below the main toolbar. So here's why you may think it's
not working in WebHelp. The behavior of the Previous and Next icons
will change depending on which topic you are viewing. If the topic
presented in the Topic pane is part of a sequence, one or both of
the buttons will be enabled. If the topic is the *FIRST* topic of a
sequence, the Next button will be enabled but Previous will not be.
This is because you cannot go further backward. The topic begins
the sequence. Assuming there are more than two topics in the
sequence, you click the Next button and the next topic in the
sequence is presented in the topic pane. This should then cause the
Previous button to enable and work when you click it. Once the last
topic in a sequence is presented, the Next button disables as you
cannot go further.
The bottom line here is that if you are displaying a topic
that is not part of a browse sequence, bot buttons will be disabled
and dead to the user.
Now shift focus to AIR Help. It seems reasonable to me that
if the AIR Help is presenting a topic that isn't part of the Browse
Sequence, just as WebHelp disables both the Previous and Next
buttons in the mini toolbar, AIR Help may disable the Print
Sequence feature.
Now that it's hopefully clear how this all works, please
ensure you are displaying a topic that is included in a Browse
Sequence and see if you now have an available option. I'm not
looking at AIR Help at the moment as I have no access to RoboHelp
8. So you might be seeing a bug or you might find it now works as
designed. Only you can say for certain.
Keep in mind that when you create AIR Help, I believe it has
to be installed after created in order to see it work. So just to
be on the safe side, after you ensure things are configured as
outlined, try generating to a different output file name, then
install and test that.
Whew... Rick

ORA-02289 (10: 10): PL/SQL: ORA-02289: sequence does not exist

Hi,
I want to run a trigger on SCOTT account.But wheni try to run it.I am getting ' ORA-02289 (10: 10): PL/SQL: ORA-02289: sequence does not exist'.PLease help out

Sequence FUNCTION_SEQ does not exist...
Pease run
Select * from user_objects
where object_type='SEQUENCE'
and object_name='FUNCTION_SEQ'In order to see that this object doesnt exist on your schema...
Maybe you are trying to use sequence in different schema... Check it out too
Select * from all_objects
where object_type='SEQUENCE'
and object_name='FUNCTION_SEQ'And if you has access to DBA_ views check this too...
Select * from dba_objects
where object_type='SEQUENCE'
and object_name='FUNCTION_SEQ'If you need such sequence please give us an example of values you need and will provide a sequence creation script for you..

Suppress auto sequence and trigger DDL for surrogate keys?

Is there a way to suppress trigger and sequence creation for surrogate keys when export to DDL file?
I know most of the time the automatic sequence and trigger creation is welcome and very handy.
However I'm migrating from an old Designer model and there only the needed sequences are created.
They have a different name and trigger logic is custom (and generated outside designer).
There is a lot of package code depending on this. So I prefer to create and use different sequences.
Is there a way to achieve this? Any tips are welcome.Create

Hi,
Note that generating the DDL for Oracle 12c means that it will attempt to use your Oracle 12c Physical model. So if you normally use Oracle 10g or 11g, you will find that any details from your Oracle 10g or 11g Physical Model will not be included. So this approach may have other implications for you.
If you are not using Oracle 12c, there are some relevant properties on the Auto Increment tab of the Relational Model properties dialog for the Column which may help:
Sequence Name - allows you to specify the name of the Sequence (which can be the name of a Sequence defined in the relevant Physical Model).
Trigger Name - allows you to specify the name of a Trigger (which can be the name of a Trigger that is defined for the Table in the Physical Model).
Generate Trigger - unsetting this will stop the Trigger being generated.
David

Sequence creation in DB

Similar Messages

Maybe you are looking for