Large sequence numbers on FWSM

We recently installed a 6509 with FWSM and noticing pretty large sequence numbers like this:
" %FWSM-6-302016: Teardown UDP connection 144551535502653717"
Is that normal?

Yes. Either a reload or after its hits the maximum decimal integer made up of these 8 bytes(64 bits), I believe 20 digits is hit it will reset back to the smaller number. So according to all 1s 64 digits the max decimal number is
18446744073709551615 (20 digits).
I used this site to convert binary to decimal:
http://www.exploringbinary.com/binary-converter/
-Kureli

Similar Messages

Iterate sequence numbers?

Sequences are exported early. Log files are exported later. While people are actively working, the sequence numbers continue to increment and are recorded as IDs in the logs. By the time the logs are dumped, the sequence numbers (used as IDs) are larger than the seq.nextval.
The sequences should be iterated by an acceptable factor subsequent to the import. A script could be written which would perform this work on all sequences in the schema without incurring the overhead of querying for the maximum key value of each sequence supported column.
Help?

Hi,
In one of my former projects I encountered the more or less the same problem. I wrote a PL/SQL procedure that checks for the nextval of all sequences, and then checks for all id columns in the corresponding tables.
If the sequences are out of sync, it genrates code to change the increment. (positive or negative), fetches the next val and sets back the increment to 1 again.
You can execute or skip the code, giving you maximum control. It doesnot execute by itself.
If you're interested I could drop the pl/sql code or send it to you if you leave your email adress here.
Site note: it assumes that all names of sequences and id columns are in line
for instance -> SEQ_employee , T_employee , ID_employee , otherwise it doesn't work.
I guess your naming conventions will be different then ours, but it's a starter that you could adapt to your own needs.
Rergards,
Toin.
// Corrected a typo.
Message was edited by:
Toin

Sql Developer 1.5.5 bug with large sequence start values.

We have a small table in our sql server 2005 schema (~700) rows. Its primary key is a bigint. We randomly generate ids for this table (don't ask). We have ids for this table which are larger than 2147483647. (java.lang.Integer.MAX_VALUE). I'm using a Windows 10g instance as the repository:
SQL> select * from v$version
2 ;
BANNER
Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Prod
PL/SQL Release 10.2.0.1.0 - Production
CORE 10.2.0.1.0 Production
TNS for 32-bit Windows: Version 10.2.0.1.0 - Production
NLSRTL Version 10.2.0.1.0 - Production
Capturing this model works fine.
Converting this model works fine.
When the converted model is "Generated", Sql Developer stops generating the script before the worksheet window is opened with the generated sql. If run from sqldeveloper/bin, this exception is output to the console:
java.lang.Exception: java.util.NoSuchElementException
at oracle.dbtools.migration.workbench.core.ui.AbstractMigrationProgressRunnable.start(AbstractMigrationProgressRunnable.java:141)
at oracle.dbtools.migration.workbench.core.GenerateInitiator.launch(GenerateInitiator.java:42)
at oracle.dbtools.raptor.controls.sqldialog.ObjectActionController.handleEvent(ObjectActionController.java:149)
at oracle.ide.controller.IdeAction.performAction(IdeAction.java:524)
at oracle.ide.controller.IdeAction.actionPerformedImpl(IdeAction.java:855)
at oracle.ide.controller.IdeAction.actionPerformed(IdeAction.java:496)
at javax.swing.AbstractButton.fireActionPerformed(AbstractButton.java:1995)
at javax.swing.AbstractButton$Handler.actionPerformed(AbstractButton.java:2318)
at javax.swing.DefaultButtonModel.fireActionPerformed(DefaultButtonModel.java:387)
at javax.swing.DefaultButtonModel.setPressed(DefaultButtonModel.java:242)
at javax.swing.AbstractButton.doClick(AbstractButton.java:357)
at javax.swing.plaf.basic.BasicMenuItemUI.doClick(BasicMenuItemUI.java:1225)
at javax.swing.plaf.basic.BasicMenuItemUI$Handler.mouseReleased(BasicMenuItemUI.java:1266)
at java.awt.Component.processMouseEvent(Component.java:6134)
at javax.swing.JComponent.processMouseEvent(JComponent.java:3265)
at java.awt.Component.processEvent(Component.java:5899)
at java.awt.Container.processEvent(Container.java:2023)
at java.awt.Component.dispatchEventImpl(Component.java:4501)
at java.awt.Container.dispatchEventImpl(Container.java:2081)
at java.awt.Component.dispatchEvent(Component.java:4331)
at java.awt.LightweightDispatcher.retargetMouseEvent(Container.java:4301)
at java.awt.LightweightDispatcher.processMouseEvent(Container.java:3965)
at java.awt.LightweightDispatcher.dispatchEvent(Container.java:3895)
at java.awt.Container.dispatchEventImpl(Container.java:2067)
at java.awt.Window.dispatchEventImpl(Window.java:2458)
at java.awt.Component.dispatchEvent(Component.java:4331)
at java.awt.EventQueue.dispatchEvent(EventQueue.java:599)
at java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:269)
at java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:184)
at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:174)
at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:169)
at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:161)
at java.awt.EventDispatchThread.run(EventDispatchThread.java:122)
Caused by: java.util.NoSuchElementException
at oracle.dbtools.metadata.persistence.PersistableObjectIterator.next(PersistableObjectIterator.java:131)
at oracle.dbtools.migration.generate.GenerateWorker.generateSequences(GenerateWorker.java:862)
at oracle.dbtools.migration.generate.GenerateWorker.generateIndividualSchema(GenerateWorker.java:456)
at oracle.dbtools.migration.generate.GenerateWorker.generateSchema(GenerateWorker.java:365)
at oracle.dbtools.migration.generate.GenerateWorker.runGenerate(GenerateWorker.java:220)
at oracle.dbtools.migration.workbench.core.ui.GenerateRunner.doWork(GenerateRunner.java:71)
at oracle.dbtools.migration.workbench.core.ui.AbstractMigrationProgressRunnable.run(AbstractMigrationProgressRunnable.java:161)
at oracle.dbtools.migration.workbench.core.ui.MigrationProgressBar.run(MigrationProgressBar.java:569)
at java.lang.Thread.run(Thread.java:619)
A problem row can be viewed by issuing this query against the repository:
select * from md_sequences where seq_start > 2147483647;
We have one row returned. The oracle.dbtools.metadata.persistence.MdSequence class uses a java.lang.Integer value to store the start value for the sequence. The value stored in the repository's MD_SEQUENCE table overflows the Integer type.
Updating the SEQ_START column in the MD_SEQUENCE table fixed our problem. (Well, I can now generate the schema. I may have other problems with the sequence being off).
I've written this post to save someone else the day it took me to diagnose this problem with Sql Developer 1.5.5. At the very least Sql Developer should inform the user that it could not generate the script because of the large sequence start value. It basically swallows any error and terminates script generation without any type of feedback.

Update: I was able to recreate the problem!
1. Create a new table (I used TEST).
2. Mark first column af primary key.
3. Save the table.
Notice the name of the primary key index created: (TEST_PK in my case)
4. Edit the table.
5. Under constraints change the name of the primary key constraint.
6. Save the table.
Notice that the index still has its original name.
7. Edit the table.
8. Change something.
9. Attempt to save changes (Fails).
Conclusion:
Either SQL Developer should be aware of indexes with different name than a constraint,
or when SQL Developer changes the name of a constraint with an index, both the constraint and the index should be renamed.

Operations on very large binary numbers

Hi guys,
I'm trying to write a java class for manipulations of very large binary numbers.
I'm representing the BN internally as boolean[] (array of booleans false for 0 & true for 1).
I want to write an algorithm for the following operations :
shifLeft (boolean[] b,int n) : shifting binary number to left by n positions.preferably a circular shift .
and also the corresponding shiftRight() method.
can some one guide me on how to implement this ?
thanks.

Consider an array of ascii chars....
array => | |a|b|c|d|
offset = 1
len = 4In the above there are actually five spots in the
array but the offset points to the second position in
the array and the length is 4.
If I was to extract the value it would be "abcd"
because of the offset and the length.
Now a 'shift right' means that if it is "abcd" then
it should now be "abc" (because the d fell off the
end.)
I can do that like this.
array => | |a|b|c|d|
offset = 1
len = 3Notice in the above that nothing changed except the
length. But because the length changed if I
extracted the value I would get "abc" because the
offset is 1 and the length is three.
Notice also that there was no array copying.Are you sure shifting works like that ?
what I know about left shifting is that the 'd' should be moved left -toghether with a, b, c- and we append a 0 in place of 'd' .
from what you said the 'd' would be gone , or am I again wrong ?
it seems i still didn't get any satisfactory answer to this problem...

Finding missed sequence numbers and rows from a fact table

Finding missed sequence numbers and rows from a fact table
Hi
I am working on an OLAP date cube with the following schema:
As you can see there is a fact transaction with two dimensions called cardNumber and Sequence. Card dimension contains about three million card numbers.
Sequence dimension contains a sequence number from 0 to 255. Fact transaction contains about 400 million transactions of those cards.
Each transaction has a sequence number in 0 to 255 ranges. If sequence number of transactions of a card reaches to 255 the next transaction would get 0 as a sequence number.
For example if a card has 1000 transactions then sequence numbers are as follows;
Transaction 1 to transaction 256 with sequences from 0 to 255
Transaction 257 to transaction 512 with sequences from 0 to 255
Transaction 513 to transaction 768 with sequences from 0 to 255
Transaction 769 to transaction 1000 with sequences from 0 to 231
The problem is that:
Sometimes there are several missed transactions. For example instead of sequence from 0 to 255, sequences are from 0 to 150 and then from 160 to 255. Here 10 transactions have been missed.
How can I find all missed transactions of all cards with a MDX QUERY?
I really appreciate for helps

Thank you Liao
I need to find missed numbers, In this scenario I want the query to tell the missed numbers are: 151,152,153,154,155,156,157,158,159
Relative transactions are also missed, so I think it is impossible to get them by your MDX query
Suppose this:
date
time
sequence
20140701
23:22:00
149
20140701
23:44:00
150
20140702
8:30:00
160
20140702
9:30:00
161
20140702
11:30:00
162
20140702
11:45:00
163
As you can see the sequence number of the last transaction at the 20140701 is 150
We expecting that the first transaction of the next day should be 151 but it is 160. Those 10 transactions are totally missed and we just need to
find missed sequence numbers

XML Report comes up as blank when a very large sequence is run

Forum,
We have multiple test sequences which me mix and match to do testing on different producst in our product line. We have no issues when we are working with small sequences ( small sequences : Which generate reports upto 12-50MB ). However when the sequences become large ( ~100-200 tests at one go , we get a blank report with the following text:
Begin Sequence:
No Sequence Results Found
We notice this typically for report sizes 60MB and more. Is there a limit to how much teststands result collection memory can store ?
My predominant report options
-- On the fly reporting disabled
-- XML - expand.xsl selected
The same set of settings do not make any difference for smaller reports, but give error for larger sequences - So I suspect its something to do with size of report being generated !

I created a simple sequence file which had a 100 Pass/Fail steps using the None Adaptor. These 100 steps in the form of 10 SequenceCall steps each performed 10 Pass/Fail step was placed in a For loop in the MainSequence. The loop was set to run 1000 iterations. The ReportOptions were set for XML horizonal, On the Fly enabled.
This I set running. Explorer was open at the folder where the result file was being stored. Two files were generated, the actual result file and a temporay file. I also had the Taskmanager open to monitor the performance.
As the result file got larger, about 20MB, I noticed that the size of the file was first set to zero and the data was written to the file. (It seemed like the file was deleted and generated each step result time). I also noticed that as the file got larger and larger, the storing of the step results was having an effect on the performance of the Test Sequence execution.
I left this running over night and sometime later the execution crashed. (see attached image). Before closing the dialog, I checked explorer to see what the state of the result file was. The both files was empty.
I repeated the run but this time the number of iteration was set to 500, again the execution crashed but this time the result file did have some data, rather a lot of data, over 50MBs.
I tried to open the file to check the contents but unfortunately my PC didn't seem to beable to handle a file of that size, as it was taking a long time to load, so I kill the process.
I dont think changing the iterations from 100 to 500 had anything to do with the getting the results on the second. I just think the point were it crashed was slightly different allowing the result to be transferred back to the file.
It would be interesting to find out whats going on the On the fly routine.
It also seems that On the fly seems no better that normal reports generation. It also seems pointless generating a very large file of results and that generating smaller files would be the better way to go. Using HTML or XML a top level report file could be used to link all the smaller files together.
Regards
Ray Farmer
Regards
Ray Farmer

LR3 Web Gallery Sequence Numbering bug?

Anyone else getting this problem with sequence numbering in the web HTML templates? Basically, as you jump through photos the photo number is always stuck on #1, never changes when you go to the next photo - should go 1, 2, 3, 4, 5...
I just sent a bug report but, wondering if anyone else found a fix for this yet.
This is in LR3 on Mac - really trying to do this on TTG Highslide gallery but, same problem occurs in default Lightroom HTML gallery.
Thanks.
******BUG******
Concise problem statement:
Steps to reproduce bug:
1. Go to Web Module
2. Choose default HTML Gallery
3. Under Image Info set Caption to Sequence
Results:
Sequence caption always shows 1/total images.
i.e. 1/10, 1/10, 1/10, 1/10
Expected results:
Sequence should increment current image number / total images as you click through images.
i.e. 1/10, 2/10, 3/10, 4/10

Yeah, still have the numbering problem using the Image Info sequence outputs.
But, if you use the standard Lightroom Flash Gallery it has it's own sequence numbering output (that does not use Image Info captions) and it does work correctly. These show up as 1/9, 2/9, 3/9 etc. on each photo down by the back/next buttons.
Also, the Cell Numbering does work when using the Lightroom HTML Gallery - though, those numbers only appear on the index page not on individual photos.
But, haven't seen a good work-around yet for sequence numbering in Image Info area. Only option there seems to be typing numbers manually into the caption. Or, if you need the caption for other info maybe use one of the IPTC fields like Headline to type in your numbers. You can then do a Custom Setting in web module to have those text fields show up with your photos.
Really hoping we will see a LR 3.1 sometime soon with a fix - should be an easy correction for Adobe.

Sequence numbers not generated sequentially?

Our situation: We have encountered an issue with our database, where it appears that a sequence has generated a number out of sequence, that is, to fill in a gap left previously. That is, in the affected table, we have records like:
Seq No Date (DD/MM/YY)
1 29/12/08
2 29/12/08
3 4/1/09
4 29/12/08
The code that actually updates the database is from a third party, so I am unable to prove the following, but the vendor assures me that:
1. The sequence numbers are generated using "select message_number.nextval from dual".
2. The Date column is not modified after the record is created. ( Nor is it supposed to be )
The sequence is created by "CREATE SEQUENCE MESSAGE_NUMBER START WITH 10000000 INCREMENT BY 1 MINVALUE 10000000 CACHE 20 NOCYCLE NOORDER"
This was detected only yesterday, after the event, and is very uncommon ( I have not found another instance, but there are over 7,000,000 records, so I haven't performed an exhaustive search). We are relying on the sequence numbers always being generated sequentially, as in each message_number.nextval is greater than the previous one.
I don't think that the date change was due to a user accidentaly changing the date. Related records to '3' are also dated 4/1/09, there is no facility for a user to change the date outside of accessing the database directly, and even the developers do not have write access to this database.
My questions:
1. Is this normal behaviour for a sequence? To go back and fill in a gap like this? If so we'll have to change one of the assumptions of one of our modules.
2. Should the sequence be defined with 'ORDER' rather than 'NOORDER' to stop this?
3. Could this be a bug in the sequence number generation? We are using Oracle 9.2.0.1.0.
4. Is this situation "impossible", and therefore there is a bug in the vendor library that we need to track down.
Thanks for your help,
Wayne.

wayneb wrote:
Our situation: We have encountered an issue with our database, where it appears that a sequence has generated a number out of sequence, that is, to fill in a gap left previously. That is, in the affected table, we have records like:
Seq No Date (DD/MM/YY)
1 29/12/08
2 29/12/08
3 4/1/09
4 29/12/08
The code that actually updates the database is from a third party, so I am unable to prove the following, but the vendor assures me that:
1. The sequence numbers are generated using "select message_number.nextval from dual".
2. The Date column is not modified after the record is created. ( Nor is it supposed to be )There might be a delay between fetching the sequence and storing the sysdate? value in the database.
maybe some user prepared a new record. Then went to some new years eve party and when he came back at the begining of next year he commited the data (record send to database, database is adding date column by some trigger...).
>
The sequence is created by "CREATE SEQUENCE MESSAGE_NUMBER START WITH 10000000 INCREMENT BY 1 MINVALUE 10000000 CACHE 20 NOCYCLE NOORDER"
This was detected only yesterday, after the event, and is very uncommon ( I have not found another instance, but there are over 7,000,000 records, so I haven't performed an exhaustive search). We are relying on the sequence numbers always being generated sequentially, as in each message_number.nextval is greater than the previous one.
I don't think that the date change was due to a user accidentaly changing the date. Related records to '3' are also dated 4/1/09, there is no facility for a user to change the date outside of accessing the database directly, and even the developers do not have write access to this database.
My questions:
1. Is this normal behaviour for a sequence? To go back and fill in a gap like this? If so we'll have to change one of the assumptions of one of our modules.No sequences don't fill gaps. However it is possible to fetch and cache values from a sequence for later usage. Especially in a RAC environment you can get sequence values that are not in order of time.
2. Should the sequence be defined with 'ORDER' rather than 'NOORDER' to stop this?No.
3. Could this be a bug in the sequence number generation? We are using Oracle 9.2.0.1.0.Extremly unlikely, but you can always check Metalink.
4. Is this situation "impossible", and therefore there is a bug in the vendor library that we need to track down.You can create such situations programatically. Whether it is a bug depends on the specifications for the software.
>
Thanks for your help,
Wayne.Edited by: Sven W. on Mar 24, 2009 5:00 PM

Page item sequence numbers

Maybe this one is for a future improvement...
After reordering page items using the drag and drop feature the items all have a sequence number one greater than it's predecessor.
This makes it hard to put a new item in between existing ones. Generating sequence numbers 5 or 10 apart would make this a bit easier.

hi,
i dont know whether you have tried this before...
10
10.1
10.2
10.3
20
20.1
20.2
30
this is acceptable in apex item sequence number for inserting new items .
Thanks
Mark Wyatt
Edited by: Websoft on Sep 30, 2009 6:33 AM

Documents Sequence numbering for each Branch (Branch as segment)

dear Brother's
can help me in this case
Documents Sequence numbering for each Branch (Branch as segment)
Each branch have an own sequence
I implement oracle Business suite ERP for Five Branch ( KSA,INDIA,DUBIA ,JORDAN ,SYRIA )
I want to segregate sequence numbering for each branch, sequence for (
Sales order, invoice, purchase order, Invoice)
Is there a possibility to link sequence with any segment I define it in COA like Branch
Note: I work in single Operating Unit

Hi,
You might be able to adapt this solution to work for your case: https://acrobat.com/#d=*2slxPLc6c-H0U449vA4jQ. It's more about page numbers for different Master Pages, but you may be able to tie it to the different data nodes.
Niall

How to read sequence numbers from RTP packets

hi everyone.
i want to know how to read sequence numbers of RTP packets. I will need that to reconstruct my stream from packet losses.
URGENT Help needed!!

The StreamTokenizer parses all numbers into only one type of value, a double. If you know that all the numeric values in the file will be integers, you could just cast the nval double field to an int and the toString() method will format it correctly.
If you want to have different tokens and value types for different kinds of numbers, you will have to sub-class StreamTokenizer and add these capabilities yourself. You can add the type constant TT_INT, and provide an int field named ival. The toString() method would then format the value in the correct manner.
If, on the other hand, you are actually looking for the exact text that was parsed, you could add code that collects the characters as they are parsed for any token type into the sval field in the nextToken() method, just like it already does when the token is a TT_WORD. In this manner sval is always valid for any token type.
I hope you find this of some help.

Deleting specific sequence numbers

Gurus!
I have a scenario in which , I would like to revoke / delete the disabled java.io.filepermissions on a Specific Oracle9i Schema.
i tried to delete the KEY values from DBA_JAVA_POLICY / USER_JAVA_POLICY
then i came to a point that as these both are Views we cannt delete the data.
So I tried to delete a specific sequence numbers ( 71 to 79) for a GRANTEE# number 31 from the base table that is java$policy$ but still am not able to . the errors SQL command terminated improperly ( somehting like that)
Please help me out with this. as I already upset with this.

You are not supposed to mess with the data dictionary, otherwise unexpected results may start to show up.
Granting or revoking privileges must be done with proper commands provided explicilty for that pourpose.
Verify database privileges here.
~ Madrid.

MIRO document sequence numbering

Hi Experts,
We are facing an issue in MIRO document sequence numbering; please see the document numbers with dates:
Document No             Yr      DocTye     Document Date                Posting Date          Entry Date
5105600850              2011            RE      23.02.2011                          11.04.2011          11.04.2011
5105600865              2011            RE     27.03.2011          07.04.2011         07.04.2011
5105600866              2011            RE     27.03.2011          07.04.2011         07.04.2011
5105600866              2011           RE     27.03.2011          07.04.2011         07.04.2011
5105600867              2011           RE     27.03.2011          07.04.2011         07.04.2011
5105600869              2011           RE     29.03.2011          07.04.2011          08.04.2011
From the above document list doc no 5105600850 is been posted on 11.04.2011 but doc no 5105600866 is been posted on 07.04.2011 but still the sequence of the document numbers are not correct, though it doc no 5105600850 posted before the doc no 5105600866.
Why is this behavior of the system? Is there any buffer concept in MIRO posting?
Thanks in advance.
Br,
Shilpa

Please check whether the number range is used up or not.
Sometime system will take the used number range if the range is over.
Or you can check this ling for Buffer
[MIRO document Number range buffering problem |MIRO document Number range buffering problem;

Sequence numbers - with no gaps!

I seek some advice from anyone with first hand experience in this area.
My need is simple; generate a new ID number for every order for use as the primary key.
Obviously this simple exercise could be a bottleneck as volumes ramp up, so I was pleased to find the Oracle feature to generate such numbers (efficiently presumably). However, upon closer reading it was apparent that aborted transactions would result in the loss of the number allocated to to that order if another transaction had obtained the next sequence number already (as one would want it to, rather than serializing transactions).
I don't want to have gaps in the sequence as the system needs a high degree of auditability. I am thinking of utilising the Autonomous Transaction feature to write the newly acquired sequence number to the order file with a flag indicating that the record is incomplete, and that record is to be skipped by normal system applications (but available to audit reports which will interpret the reason correctly), then returning to the far more extensive main transaction which updates many tables.
The other alternative is to control sequence numbers within the application itself, or try to get the sequence number as the very last step before writing the new order record, but this probably won't guarantee gapless reliability either. The ID itself has no significance, and it doesn't matter if an ID was used out of strict date/time sequence, so I really don't want to execute these updates serially.
So, my question is this:
a) do most people use the builtin sequence number feature?
b) if so, is there a standard technique for avoiding or accounting for gaps?
c) if the application must take over this task, should the counter for the last used ID be in a single row table to minimise bottlenecks caused by the thisrecord being locked? There will be several such counters for different aspects of the application, and i thought of having each in its own row in a small table, but I'm concerned about the whole table getting locked and freezing out otherwise-unrelated updates.
Thanks for any advice you may have.
CS

user8821725 wrote:
I seek some advice from anyone with first hand experience in this area.
My need is simple; generate a new ID number for every order for use as the primary key.
Obviously this simple exercise could be a bottleneck as volumes ramp up, so I was pleased to find the Oracle feature to generate such numbers (efficiently presumably). However, upon closer reading it was apparent that aborted transactions would result in the loss of the number allocated to to that order if another transaction had obtained the next sequence number already (as one would want it to, rather than serializing transactions).
I don't want to have gaps in the sequence as the system needs a high degree of auditability. One of the very very few reasons for me to have a requirement for "gapless" sequences is if you have a kind of checking mechanism outside of the database that is implemented using this gapless number. I had such a requirement once, when exchanging files with another bank where we had to ensure that each file was transferred correctly and in the right order. Your "high degree of auditability" might be a similiar requirement. Just remember as long as you are still inside the database you can use other mechanisms to increase auditability.
I am thinking of utilising the Autonomous Transaction feature to write the newly acquired sequence number to the order file with a flag indicating that the record is incomplete, and that record is to be skipped by normal system applications (but available to audit reports which will interpret the reason correctly), then returning to the far more extensive main transaction which updates many tables.Hm. I don't see why you want to use Autonomous Transactions for this. It might be useful to lessen locking conflicts , depending how your future sequence mechanism will be built.
>
The other alternative is to control sequence numbers within the application itself, or try to get the sequence number as the very last step before writing the new order record, but this probably won't guarantee gapless reliability either. The ID itself has no significance, and it doesn't matter if an ID was used out of strict date/time sequence, so I really don't want to execute these updates serially.I would go for generating the sequence as the very last step. It needs to be set to NOCACHE of cause. This will garantee that the sequence fetched from mySeq.nextval is gapless. The problem is then in your application. Your application must be built in a way that it ensures to use this sequence, or at least to create a noticable alert when this generated sequence can't be used anymore. In essence this means. Each unhandled (database) error that happens after you fetched the next sequence value must be raised in a way that informs all relevant people about this error.
Example: It might be that you use the sequence to write an order file. What happens if halfway through writing the file your disk runs out of space? This can be such an issue where a sequenced value will be lost. Your organisation must take care of those things.
>
So, my question is this:
a) do most people use the builtin sequence number feature?Yes. But for some tasks a sequence is not the best way, for example if you want a numbering for each item of your order. This "sequence" needs to restart with every new order.
b) if so, is there a standard technique for avoiding or accounting for gaps?NOCACHE => Avoids gaps during generation
Database Trigger => Tries to use the sequence as late as possible
c) if the application must take over this task, should the counter for the last used ID be in a single row table to minimise bottlenecks caused by the thisrecord being locked? There will be several such counters for different aspects of the application, and i thought of having each in its own row in a small table, but I'm concerned about the whole table getting locked and freezing out otherwise-unrelated updates.This is a possibility and the issues you describe are why we avoid such a solution in general. Autonomous transactions help to reduce the locking conflict, but they increase the chance that you produce gaps.
>
Thanks for any advice you may have.
CSOracle can guarantee to produce gapless sequences. But it can't guarantee that your application uses such a sequence in a gapless way.

70D changed sequence numbers from 6.. to 5...

Month old 70D was issuing sequnce numbers OK in August 31 in the 600 range but on September 2 (the next time I used the camera) the sequence numbers changed to 5000. I manually changed the date to October but the sequence numbers remained in the 5000 range so it probably had nothing to do with the month change. I did a menu RESET, took a photo and it was just the next number (5102) so no help there. In both cases there is a number 100 and a dash preceding the sequence number. Any suggestions? Thanks
BTW the camera FILE NUMBERING setting is CONTINUOUS
Solved!
Go to Solution.

Hello bob70D,
The most likely culprit with something like this is going to be the card. It is very likely that the camera is reading an old file numbering scheme (could even be from another Canon EOS DSLR) and "picking up" where the numbers leave off.
To test this, and really to resolve this issue, you'd need to format the card. Only do this in the camera and only once you've backed up your pictures. First, set the camera's file numbering to Manual Reset and then Format. It will bring everything back to 0001. Then go back into the Menu and back to file numbering and choose Continuous this time.
Did this answer your question? Please click the Accept as Solution button so that others may find the answer as well.

Large sequence numbers on FWSM

Similar Messages

Maybe you are looking for