[Hibernate-JIRA] Created: (HHH-5208) Oracle 11g R2 RAC - Test SequenceIdentityTest fails because first value of sequence is "2"
1:46 p.m.
Oracle 11g R2 RAC - Test SequenceIdentityTest fails because first value of sequence is
"2"
------------------------------------------------------------------------------------------
Key: HHH-5208
URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5208
Project: Hibernate Core
Issue Type: Bug
Components: core
Affects Versions: 3.5.1, 3.5.x
Environment: Oracle 11g R2 (RAC)
Reporter: Strong Liu
Starting with Oracle 11g R2 (RAC), the behavior of the CREATE TABLE statement has changed,
when creating a conventional table in a database created with the default options then the
initial segment is not created until the first row is inserted into the table.
see
http://download.oracle.com/docs/cd/E11882_01/server.112/e10595/tables002....
for more details.
We found a potential downside to this change :
The sequences created as default ( start with 1 increment by 1) are not staring with
'1′ when used in insert query script, Instead they are starting with 2 or 4, this can
not be changed even explicitly tell Oracle that the first value is "1".
In another words, when using Hibernate with Oracle 11g R2 (RAC), if the ID generator class
is "sequence-identity", the first value is NOT 1.
Two ways to work around this issue:
1. Using another ID generator class.
2. Disable deferred segment creation of Oracle by setting the initialization parameter
DEFERRED_SEGMENT_CREATION to FALSE. The new clauses SEGMENT CREATION DEFERRED and SEGMENT
CREATION IMMEDIATE are available for the CREATE TABLE statement. These clauses override
the setting of the DEFERRED_SEGMENT_CREATION initialization parameter.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators....
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
1:46 p.m.
New subject: [Hibernate-JIRA] Commented: (HHH-5208) Oracle 11g R2 RAC - Test SequenceIdentityTest fails because first value of sequence is "2"
[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-5208?page=c...
]
Strong Liu commented on HHH-5208:
---------------------------------
org.hibernate.test.generatedkeys.seqidentity.SequenceIdentityTest.testSequenceIdentityGenerator
Oracle 11g R2 RAC - Test SequenceIdentityTest fails because first
value of sequence is "2"
------------------------------------------------------------------------------------------
Key: HHH-5208
URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5208
Project: Hibernate Core
Issue Type: Bug
Components: core
Affects Versions: 3.5.1, 3.5.x
Environment: Oracle 11g R2 (RAC)
Reporter: Strong Liu
Starting with Oracle 11g R2 (RAC), the behavior of the CREATE TABLE statement has
changed, when creating a conventional table in a database created with the default options
then the initial segment is not created until the first row is inserted into the table.
see
http://download.oracle.com/docs/cd/E11882_01/server.112/e10595/tables002....
for more details.
We found a potential downside to this change :
The sequences created as default ( start with 1 increment by 1) are not staring with
'1′ when used in insert query script, Instead they are starting with 2 or 4, this can
not be changed even explicitly tell Oracle that the first value is "1".
In another words, when using Hibernate with Oracle 11g R2 (RAC), if the ID generator
class is "sequence-identity", the first value is NOT 1.
Two ways to work around this issue:
1. Using another ID generator class.
2. Disable deferred segment creation of Oracle by setting the initialization parameter
DEFERRED_SEGMENT_CREATION to FALSE. The new clauses SEGMENT CREATION DEFERRED and SEGMENT
CREATION IMMEDIATE are available for the CREATE TABLE statement. These clauses override
the setting of the DEFERRED_SEGMENT_CREATION initialization parameter.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators....
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:42 p.m.
New subject: [Hibernate-JIRA] Commented: (HHH-5208) Oracle 11g R2 RAC - Test SequenceIdentityTest fails because first value of sequence is "2"
[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-5208?page=c...
]
Strong Liu commented on HHH-5208:
---------------------------------
from Juca:
A small test which can be reproduced directly in Oracle (in our lab) shows it's not a
problem in the driver nor in Hibernate:
create table my_entity (id number(19,0) not null, name varchar2(255 char) not null,
primary key (id), unique (name));
create sequence hibernate_sequence;
insert into my_entity (id, name) values (hibernate_sequence.nextval, 'test');
--- the ID for the record above is 2
delete from my_entity;
drop sequence hibernate_sequence;
create sequence hibernate_sequence;
insert into my_entity (id, name) values (hibernate_sequence.nextval, 'test');
--- the ID for the record above is 1
Oracle 11g R2 RAC - Test SequenceIdentityTest fails because first
value of sequence is "2"
------------------------------------------------------------------------------------------
Key: HHH-5208
URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5208
Project: Hibernate Core
Issue Type: Bug
Components: core
Affects Versions: 3.5.1, 3.5.x
Environment: Oracle 11g R2 (RAC)
Reporter: Strong Liu
Starting with Oracle 11g R2 (RAC), the behavior of the CREATE TABLE statement has
changed, when creating a conventional table in a database created with the default options
then the initial segment is not created until the first row is inserted into the table.
see
http://download.oracle.com/docs/cd/E11882_01/server.112/e10595/tables002....
for more details.
We found a potential downside to this change :
The sequences created as default ( start with 1 increment by 1) are not staring with
'1′ when used in insert query script, Instead they are starting with 2 or 4, this can
not be changed even explicitly tell Oracle that the first value is "1".
In another words, when using Hibernate with Oracle 11g R2 (RAC), if the ID generator
class is "sequence-identity", the first value is NOT 1.
Two ways to work around this issue:
1. Using another ID generator class.
2. Disable deferred segment creation of Oracle by setting the initialization parameter
DEFERRED_SEGMENT_CREATION to FALSE. The new clauses SEGMENT CREATION DEFERRED and SEGMENT
CREATION IMMEDIATE are available for the CREATE TABLE statement. These clauses override
the setting of the DEFERRED_SEGMENT_CREATION initialization parameter.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators....
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:30 a.m.
New subject: [Hibernate-JIRA] Assigned: (HHH-5208) Oracle 11g R2 RAC - Test SequenceIdentityTest fails because first value of sequence is "2"
[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-5208?page=c...
]
Strong Liu reassigned HHH-5208:
-------------------------------
Assignee: Strong Liu
Oracle 11g R2 RAC - Test SequenceIdentityTest fails because first
value of sequence is "2"
------------------------------------------------------------------------------------------
Key: HHH-5208
URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5208
Project: Hibernate Core
Issue Type: Bug
Components: core
Affects Versions: 3.5.1, 3.5.x
Environment: Oracle 11g R2 (RAC)
Reporter: Strong Liu
Assignee: Strong Liu
Starting with Oracle 11g R2 (RAC), the behavior of the CREATE TABLE statement has
changed, when creating a conventional table in a database created with the default options
then the initial segment is not created until the first row is inserted into the table.
see
http://download.oracle.com/docs/cd/E11882_01/server.112/e10595/tables002....
for more details.
We found a potential downside to this change :
The sequences created as default ( start with 1 increment by 1) are not staring with
'1′ when used in insert query script, Instead they are starting with 2 or 4, this can
not be changed even explicitly tell Oracle that the first value is "1".
In another words, when using Hibernate with Oracle 11g R2 (RAC), if the ID generator
class is "sequence-identity", the first value is NOT 1.
Two ways to work around this issue:
1. Using another ID generator class.
2. Disable deferred segment creation of Oracle by setting the initialization parameter
DEFERRED_SEGMENT_CREATION to FALSE. The new clauses SEGMENT CREATION DEFERRED and SEGMENT
CREATION IMMEDIATE are available for the CREATE TABLE statement. These clauses override
the setting of the DEFERRED_SEGMENT_CREATION initialization parameter.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators....
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:34 a.m.
New subject: [Hibernate-JIRA] Resolved: (HHH-5208) Oracle 11g R2 RAC - Test SequenceIdentityTest fails because first value of sequence is "2"
[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-5208?page=c...
]
Strong Liu resolved HHH-5208.
-----------------------------
Resolution: Fixed
Fix Version/s: 3.6
3.5.2
3.3.x
Oracle 11g R2 RAC - Test SequenceIdentityTest fails because first
value of sequence is "2"
------------------------------------------------------------------------------------------
Key: HHH-5208
URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5208
Project: Hibernate Core
Issue Type: Bug
Components: core
Affects Versions: 3.5.1, 3.5.x
Environment: Oracle 11g R2 (RAC)
Reporter: Strong Liu
Assignee: Strong Liu
Fix For: 3.3.x, 3.5.2, 3.6
Starting with Oracle 11g R2 (RAC), the behavior of the CREATE TABLE statement has
changed, when creating a conventional table in a database created with the default options
then the initial segment is not created until the first row is inserted into the table.
see
http://download.oracle.com/docs/cd/E11882_01/server.112/e10595/tables002....
for more details.
We found a potential downside to this change :
The sequences created as default ( start with 1 increment by 1) are not staring with
'1′ when used in insert query script, Instead they are starting with 2 or 4, this can
not be changed even explicitly tell Oracle that the first value is "1".
In another words, when using Hibernate with Oracle 11g R2 (RAC), if the ID generator
class is "sequence-identity", the first value is NOT 1.
Two ways to work around this issue:
1. Using another ID generator class.
2. Disable deferred segment creation of Oracle by setting the initialization parameter
DEFERRED_SEGMENT_CREATION to FALSE. The new clauses SEGMENT CREATION DEFERRED and SEGMENT
CREATION IMMEDIATE are available for the CREATE TABLE statement. These clauses override
the setting of the DEFERRED_SEGMENT_CREATION initialization parameter.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators....
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
1:04 p.m.
New subject: [Hibernate-JIRA] Updated: (HHH-5208) Oracle 11g R2 RAC - Test SequenceIdentityTest fails because first value of sequence is "2"
[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-5208?page=c...
]
Gail Badner updated HHH-5208:
-----------------------------
Fix Version/s: (was: 3.3.x)
Hi Strong, I noticed 3.3.x was listed as a fix version but it wasn't fixed in
Branch_3_3, so I've removed it from the list. If it really does need to be fixed in
3.3.x, please clone this issue to fix for that version.
Oracle 11g R2 RAC - Test SequenceIdentityTest fails because first
value of sequence is "2"
------------------------------------------------------------------------------------------
Key: HHH-5208
URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5208
Project: Hibernate Core
Issue Type: Bug
Components: core
Affects Versions: 3.5.1, 3.5.x
Environment: Oracle 11g R2 (RAC)
Reporter: Strong Liu
Assignee: Strong Liu
Fix For: 3.5.2, 3.6
Starting with Oracle 11g R2 (RAC), the behavior of the CREATE TABLE statement has
changed, when creating a conventional table in a database created with the default options
then the initial segment is not created until the first row is inserted into the table.
see
http://download.oracle.com/docs/cd/E11882_01/server.112/e10595/tables002....
for more details.
We found a potential downside to this change :
The sequences created as default ( start with 1 increment by 1) are not staring with
'1′ when used in insert query script, Instead they are starting with 2 or 4, this can
not be changed even explicitly tell Oracle that the first value is "1".
In another words, when using Hibernate with Oracle 11g R2 (RAC), if the ID generator
class is "sequence-identity", the first value is NOT 1.
Two ways to work around this issue:
1. Using another ID generator class.
2. Disable deferred segment creation of Oracle by setting the initialization parameter
DEFERRED_SEGMENT_CREATION to FALSE. The new clauses SEGMENT CREATION DEFERRED and SEGMENT
CREATION IMMEDIATE are available for the CREATE TABLE statement. These clauses override
the setting of the DEFERRED_SEGMENT_CREATION initialization parameter.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators....
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
1:06 p.m.
New subject: [Hibernate-JIRA] Commented: (HHH-5208) Oracle 11g R2 RAC - Test SequenceIdentityTest fails because first value of sequence is "2"
[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-5208?page=c...
]
Strong Liu commented on HHH-5208:
---------------------------------
that's fine, i marked 3.3.x to say it fixed in branch 3.3.2.cp
Oracle 11g R2 RAC - Test SequenceIdentityTest fails because first
value of sequence is "2"
------------------------------------------------------------------------------------------
Key: HHH-5208
URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5208
Project: Hibernate Core
Issue Type: Bug
Components: core
Affects Versions: 3.5.1, 3.5.x
Environment: Oracle 11g R2 (RAC)
Reporter: Strong Liu
Assignee: Strong Liu
Fix For: 3.5.2, 3.6
Starting with Oracle 11g R2 (RAC), the behavior of the CREATE TABLE statement has
changed, when creating a conventional table in a database created with the default options
then the initial segment is not created until the first row is inserted into the table.
see
http://download.oracle.com/docs/cd/E11882_01/server.112/e10595/tables002....
for more details.
We found a potential downside to this change :
The sequences created as default ( start with 1 increment by 1) are not staring with
'1′ when used in insert query script, Instead they are starting with 2 or 4, this can
not be changed even explicitly tell Oracle that the first value is "1".
In another words, when using Hibernate with Oracle 11g R2 (RAC), if the ID generator
class is "sequence-identity", the first value is NOT 1.
Two ways to work around this issue:
1. Using another ID generator class.
2. Disable deferred segment creation of Oracle by setting the initialization parameter
DEFERRED_SEGMENT_CREATION to FALSE. The new clauses SEGMENT CREATION DEFERRED and SEGMENT
CREATION IMMEDIATE are available for the CREATE TABLE statement. These clauses override
the setting of the DEFERRED_SEGMENT_CREATION initialization parameter.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators....
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:21 p.m.
New subject: [Hibernate-JIRA] Commented: (HHH-5208) Oracle 11g R2 RAC - Test SequenceIdentityTest fails because first value of sequence is "2"
[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-5208?page=c...
]
Mike Youngstrom commented on HHH-5208:
--------------------------------------
I wonder if fixing this issue might have caused a regression. In my application I'm
using Oracle and @SequenceGenerator with an allocationSize=1 after upgrading to 3.5.2 I
get the following error on startup: If I change my allocationSize to 2 then it starts up
fine.
Caused by: javax.persistence.PersistenceException: [PersistenceUnit:
org.lds.stack.stack-pet-store-ws] Unable to build EntityManagerFactory
at
org.hibernate.ejb.Ejb3Configuration.buildEntityManagerFactory(Ejb3Configuration.java:896)
at
org.hibernate.ejb.HibernatePersistence.createContainerEntityManagerFactory(HibernatePersistence.java:73)
at
org.springframework.orm.jpa.LocalContainerEntityManagerFactoryBean.createNativeEntityManagerFactory(LocalContainerEntityManagerFactoryBean.java:225)
at
org.springframework.orm.jpa.AbstractEntityManagerFactoryBean.afterPropertiesSet(AbstractEntityManagerFactoryBean.java:308)
at
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.invokeInitMethods(AbstractAutowireCapableBeanFactory.java:1469)
at
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1409)
... 38 more
Caused by: org.hibernate.MappingException: Could not instantiate id generator
[entity-name=org.lds.stack.petstore.model.Animal]
at
org.hibernate.id.factory.DefaultIdentifierGeneratorFactory.createIdentifierGenerator(DefaultIdentifierGeneratorFactory.java:117)
at org.hibernate.mapping.SimpleValue.createIdentifierGenerator(SimpleValue.java:178)
at org.hibernate.impl.SessionFactoryImpl.<init>(SessionFactoryImpl.java:257)
at org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1385)
at
org.hibernate.cfg.AnnotationConfiguration.buildSessionFactory(AnnotationConfiguration.java:954)
at
org.hibernate.ejb.Ejb3Configuration.buildEntityManagerFactory(Ejb3Configuration.java:887)
... 43 more
Caused by: org.hibernate.HibernateException: increment size cannot be less than 1
at
org.hibernate.id.enhanced.OptimizerFactory$LegacyHiLoAlgorithmOptimizer.<init>(OptimizerFactory.java:336)
at org.hibernate.id.SequenceHiLoGenerator.configure(SequenceHiLoGenerator.java:64)
at
org.hibernate.id.factory.DefaultIdentifierGeneratorFactory.createIdentifierGenerator(DefaultIdentifierGeneratorFactory.java:110)
... 48 more
Oracle 11g R2 RAC - Test SequenceIdentityTest fails because first
value of sequence is "2"
------------------------------------------------------------------------------------------
Key: HHH-5208
URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5208
Project: Hibernate Core
Issue Type: Bug
Components: core
Affects Versions: 3.5.1, 3.5.x
Environment: Oracle 11g R2 (RAC)
Reporter: Strong Liu
Assignee: Strong Liu
Fix For: 3.5.2, 3.6
Starting with Oracle 11g R2 (RAC), the behavior of the CREATE TABLE statement has
changed, when creating a conventional table in a database created with the default options
then the initial segment is not created until the first row is inserted into the table.
see
http://download.oracle.com/docs/cd/E11882_01/server.112/e10595/tables002....
for more details.
We found a potential downside to this change :
The sequences created as default ( start with 1 increment by 1) are not staring with
'1′ when used in insert query script, Instead they are starting with 2 or 4, this can
not be changed even explicitly tell Oracle that the first value is "1".
In another words, when using Hibernate with Oracle 11g R2 (RAC), if the ID generator
class is "sequence-identity", the first value is NOT 1.
Two ways to work around this issue:
1. Using another ID generator class.
2. Disable deferred segment creation of Oracle by setting the initialization parameter
DEFERRED_SEGMENT_CREATION to FALSE. The new clauses SEGMENT CREATION DEFERRED and SEGMENT
CREATION IMMEDIATE are available for the CREATE TABLE statement. These clauses override
the setting of the DEFERRED_SEGMENT_CREATION initialization parameter.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators....
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:13 a.m.
New subject: [Hibernate-JIRA] Commented: (HHH-5208) Oracle 11g R2 RAC - Test SequenceIdentityTest fails because first value of sequence is "2"
[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-5208?page=c...
]
Strong Liu commented on HHH-5208:
---------------------------------
definitely no regression, because of I only changed the test code :D
Oracle 11g R2 RAC - Test SequenceIdentityTest fails because first
value of sequence is "2"
------------------------------------------------------------------------------------------
Key: HHH-5208
URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5208
Project: Hibernate Core
Issue Type: Bug
Components: core
Affects Versions: 3.5.1, 3.5.x
Environment: Oracle 11g R2 (RAC)
Reporter: Strong Liu
Assignee: Strong Liu
Fix For: 3.5.2, 3.6
Starting with Oracle 11g R2 (RAC), the behavior of the CREATE TABLE statement has
changed, when creating a conventional table in a database created with the default options
then the initial segment is not created until the first row is inserted into the table.
see
http://download.oracle.com/docs/cd/E11882_01/server.112/e10595/tables002....
for more details.
We found a potential downside to this change :
The sequences created as default ( start with 1 increment by 1) are not staring with
'1′ when used in insert query script, Instead they are starting with 2 or 4, this can
not be changed even explicitly tell Oracle that the first value is "1".
In another words, when using Hibernate with Oracle 11g R2 (RAC), if the ID generator
class is "sequence-identity", the first value is NOT 1.
Two ways to work around this issue:
1. Using another ID generator class.
2. Disable deferred segment creation of Oracle by setting the initialization parameter
DEFERRED_SEGMENT_CREATION to FALSE. The new clauses SEGMENT CREATION DEFERRED and SEGMENT
CREATION IMMEDIATE are available for the CREATE TABLE statement. These clauses override
the setting of the DEFERRED_SEGMENT_CREATION initialization parameter.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators....
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:27 a.m.
New subject: [Hibernate-JIRA] Commented: (HHH-5208) Oracle 11g R2 RAC - Test SequenceIdentityTest fails because first value of sequence is "2"
[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-5208?page=c...
]
Mike Youngstrom commented on HHH-5208:
--------------------------------------
:) Then I'm going to point my finger at HHH-5042
Oracle 11g R2 RAC - Test SequenceIdentityTest fails because first
value of sequence is "2"
------------------------------------------------------------------------------------------
Key: HHH-5208
URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5208
Project: Hibernate Core
Issue Type: Bug
Components: core
Affects Versions: 3.5.1, 3.5.x
Environment: Oracle 11g R2 (RAC)
Reporter: Strong Liu
Assignee: Strong Liu
Fix For: 3.5.2, 3.6
Starting with Oracle 11g R2 (RAC), the behavior of the CREATE TABLE statement has
changed, when creating a conventional table in a database created with the default options
then the initial segment is not created until the first row is inserted into the table.
see
http://download.oracle.com/docs/cd/E11882_01/server.112/e10595/tables002....
for more details.
We found a potential downside to this change :
The sequences created as default ( start with 1 increment by 1) are not staring with
'1′ when used in insert query script, Instead they are starting with 2 or 4, this can
not be changed even explicitly tell Oracle that the first value is "1".
In another words, when using Hibernate with Oracle 11g R2 (RAC), if the ID generator
class is "sequence-identity", the first value is NOT 1.
Two ways to work around this issue:
1. Using another ID generator class.
2. Disable deferred segment creation of Oracle by setting the initialization parameter
DEFERRED_SEGMENT_CREATION to FALSE. The new clauses SEGMENT CREATION DEFERRED and SEGMENT
CREATION IMMEDIATE are available for the CREATE TABLE statement. These clauses override
the setting of the DEFERRED_SEGMENT_CREATION initialization parameter.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators....
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:28 p.m.
New subject: [Hibernate-JIRA] Closed: (HHH-5208) Oracle 11g R2 RAC - Test SequenceIdentityTest fails because first value of sequence is "2"
[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-5208?page=c...
]
Steve Ebersole closed HHH-5208.
-------------------------------
Oracle 11g R2 RAC - Test SequenceIdentityTest fails because first
value of sequence is "2"
------------------------------------------------------------------------------------------
Key: HHH-5208
URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5208
Project: Hibernate Core
Issue Type: Bug
Components: core
Affects Versions: 3.5.1, 3.5.3
Environment: Oracle 11g R2 (RAC)
Reporter: Strong Liu
Assignee: Strong Liu
Fix For: 3.5.2, 3.6
Starting with Oracle 11g R2 (RAC), the behavior of the CREATE TABLE statement has
changed, when creating a conventional table in a database created with the default options
then the initial segment is not created until the first row is inserted into the table.
see
http://download.oracle.com/docs/cd/E11882_01/server.112/e10595/tables002....
for more details.
We found a potential downside to this change :
The sequences created as default ( start with 1 increment by 1) are not staring with
'1′ when used in insert query script, Instead they are starting with 2 or 4, this can
not be changed even explicitly tell Oracle that the first value is "1".
In another words, when using Hibernate with Oracle 11g R2 (RAC), if the ID generator
class is "sequence-identity", the first value is NOT 1.
Two ways to work around this issue:
1. Using another ID generator class.
2. Disable deferred segment creation of Oracle by setting the initialization parameter
DEFERRED_SEGMENT_CREATION to FALSE. The new clauses SEGMENT CREATION DEFERRED and SEGMENT
CREATION IMMEDIATE are available for the CREATE TABLE statement. These clauses override
the setting of the DEFERRED_SEGMENT_CREATION initialization parameter.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators....
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
5275
days inactive
5344
days old
hibernate-issues@lists.jboss.org
10 comments
4 participants
participants (4)
-
Gail Badner (JIRA) -
Mike Youngstrom (JIRA)
-
Steve Ebersole (JIRA)
-
Strong Liu (JIRA)