Discussions
Categories
- 196.8K All Categories
- 2.2K Data
- 235 Big Data Appliance
- 1.9K Data Science
- 449.9K Databases
- 221.6K General Database Discussions
- 3.8K Java and JavaScript in the Database
- 31 Multilingual Engine
- 549 MySQL Community Space
- 478 NoSQL Database
- 7.9K Oracle Database Express Edition (XE)
- 3K ORDS, SODA & JSON in the Database
- 532 SQLcl
- 4K SQL Developer Data Modeler
- 186.9K SQL & PL/SQL
- 21.3K SQL Developer
- 295.4K Development
- 17 Developer Projects
- 138 Programming Languages
- 292.1K Development Tools
- 104 DevOps
- 3.1K QA/Testing
- 645.9K Java
- 28 Java Learning Subscription
- 37K Database Connectivity
- 154 Java Community Process
- 105 Java 25
- 22.1K Java APIs
- 138.1K Java Development Tools
- 165.3K Java EE (Java Enterprise Edition)
- 17 Java Essentials
- 158 Java 8 Questions
- 85.9K Java Programming
- 79 Java Puzzle Ball
- 65.1K New To Java
- 1.7K Training / Learning / Certification
- 13.8K Java HotSpot Virtual Machine
- 94.2K Java SE
- 13.8K Java Security
- 203 Java User Groups
- 24 JavaScript - Nashorn
- Programs
- 401 LiveLabs
- 37 Workshops
- 10.2K Software
- 6.7K Berkeley DB Family
- 3.5K JHeadstart
- 5.6K Other Languages
- 2.3K Chinese
- 171 Deutsche Oracle Community
- 1.1K Español
- 1.9K Japanese
- 230 Portuguese
Facing an issue in accessing a sequence concurrently

Working on the order integration using staging schema between ERP and CRM.
Facing an issue :- Used one procedure to integrate the data from CRM to ERP and which is being called in two different order type simultaneously. In this procedure I have used a sequence which will be a primary key. The logic written is 1. fetching value from a sequence and 2. creating a record in the table.
In the above scenario, it is being observed that some times it is getting same sequence no in both the jobs and hence the result of the same triggers to failure of the transaction.
Need help to resolve this issue.
Regards,
Rajendra
Answers
-
Impossible for a sequence generator (Oracle object) to hand out the same sequence twice.
If it could, it would be a serious bug. And a known bug.
As this is not the case, and you have failed to provide any evidence to the contrary, the logical reaction is that you have a bug in your code - and you are misdiagnosing that bug as the same sequence reusing the same number more than once.
-
In addition to Billy:
You should always provide your full database version. ( the result of: select * from v$version; )
There's a known issue with sequences on multi-node RAC:
If you have access to Metalink/MyOracleSupport, then do a search there as well.
But I'd put my $0.02 to Billy's reply and check your code.