I also get this.  I have narrowed down the problems with PersistentBroker
(from junit test runs) to the following test cases for Oracle:

ProxyExamples
MtoNMapping
BidirectionalAssociationTest
AutoIncrementWithRelatedObjectTest

Since, I do not as yet use the features of OJB tested by these cases, I am
ignoring the errors for now.

----- Original Message -----
From: "CP Agrawal" <[EMAIL PROTECTED]>
To: "'OJB Users List'" <[EMAIL PROTECTED]>
Sent: Thursday, October 31, 2002 10:08 AM
Subject: Running junit target on Oracle fails for OJB (0.9.7) fails


>
> I still get same error when running junit target
> junit-no-compile-no-prepare
> Following is extract from the top of the test-broker.txt file:
> Any help will be appreciated. I switched useP6Spy to true and looked at
> the spy.log. It just lists the SQL statements OJB is generating behind
> the scene.
> Please find the spy.log also attached. I am just wondering if the
> example data and junit tests are out of sync?
> Any help in resolving this issue will be deeply appreciated.
>
> Testsuite: org.apache.ojb.broker.AllTests^M
> Tests run: 124, Failures: 3, Errors: 3, Time elapsed: 91.111 sec^M
> ------------- Standard Output ---------------^M
> [org.apache.ojb.broker.ta.PersistenceBrokerFactoryDefaultImpl] INFO:
> Already created persistence broker instances: 0^M
> settign eager: false^M
> [org.apache.ojb.broker.util.sequence.SequenceManagerFactory] INFO: Use
> sequence manager class: class org.apache.ojb.broker.util.sequence.Seq
> uenceManagerHiLoImpl^M
> [org.apache.ojb.broker.accesslayer.AbstractPoolableConnectionFactory]
> INFO: # Create connection pool for JdbcDescriptorKey -1334978004 #^M
> [org.apache.ojb.broker.ta.PersistenceBrokerFactoryDefaultImpl] INFO:
> Already created persistence broker instances: 1^M
> [org.apache.ojb.broker.ta.PersistenceBrokerFactoryDefaultImpl] INFO:
> Already created persistence broker instances: 2^M
> [org.apache.ojb.broker.ta.PersistenceBrokerFactoryDefaultImpl] INFO:
> Already created persistence broker instances: 3^M
> [org.apache.ojb.broker.ta.PersistenceBrokerFactoryDefaultImpl] INFO:
> Already created persistence broker instances: 4^M
> [org.apache.ojb.broker.accesslayer.ConnectionManager] INFO: Rollback was
> called, do rollback on current connection oracle.jdbc.driver.Oracle
> Connection@9a0203^M
> [org.apache.ojb.broker.ta.PersistenceBrokerFactoryDefaultImpl] INFO:
> Already created persistence broker instances: 5^M
> [org.apache.ojb.broker.accesslayer.JdbcAccess] ERROR: SQLException
> during the execution of the Update SQL query (for a
> org.apache.ojb.broker
> .Project): ORA-02292: integrity constraint (CAGRAWALOJB.TASK_FK_1)
> violated - child record found
> ^M
> ORA-02292: integrity constraint (CAGRAWALOJB.TASK_FK_1) violated - child
> record found
> ^M
> [org.apache.ojb.broker.accesslayer.JdbcAccess] ERROR: SQLException
> during the execution of the Update SQL query (for a
> org.apache.ojb.broker
> .Project): ORA-00001: unique constraint (CAGRAWALOJB.PERSON_PROJECT_PK)
> violated
> ^M
> ORA-00001: unique constraint (CAGRAWALOJB.PERSON_PROJECT_PK) violated
> ^M
> [org.apache.ojb.broker.accesslayer.JdbcAccess] ERROR: SQLException
> during the execution of the Update SQL query (for a
> org.apache.ojb.broker
> .Project): ORA-00001: unique constraint (CAGRAWALOJB.PERSON_PROJECT_PK)
> violated
> ^M
> ORA-00001: unique constraint (CAGRAWALOJB.PERSON_PROJECT_PK) violated
> ^M
> [org.apache.ojb.broker.accesslayer.JdbcAccess] ERROR: SQLException
> during the execution of the Update SQL query (for a
> org.apache.ojb.broker
> .Person): ORA-00001: unique constraint (CAGRAWALOJB.PERSON_PROJECT_PK)
> violated
> ^M
> ORA-00001: unique constraint (CAGRAWALOJB.PERSON_PROJECT_PK) violated
> ^M
> [org.apache.ojb.broker.accesslayer.JdbcAccess] ERROR: SQLException
> during the execution of the Update SQL query (for a
> org.apache.ojb.broker
> .Project): ORA-02292: integrity constraint (CAGRAWALOJB.TASK_FK_1)
> violated - child record found
> ^M
> ORA-02292: integrity constraint (CAGRAWALOJB.TASK_FK_1) violated - child
> record found
> ^M
> [org.apache.ojb.broker.accesslayer.JdbcAccess] ERROR: SQLException
> during the execution of the Update SQL query (for a
> org.apache.ojb.broker
> .Project): ORA-00001: unique constraint (CAGRAWALOJB.PERSON_PROJECT_PK)
> violated
> ^M
> ORA-00001: unique constraint (CAGRAWALOJB.PERSON_PROJECT_PK) violated
> ^M
> [org.apache.ojb.broker.accesslayer.JdbcAccess] ERROR: SQLException
> during the execution of the Update SQL query (for a
> org.apache.ojb.broker
> .Project): ORA-00001: unique constraint (CAGRAWALOJB.PERSON_PROJECT_PK)
> violated
> ^M
> ORA-00001: unique constraint (CAGRAWALOJB.PERSON_PROJECT_PK) violated
> ^M
> [org.apache.ojb.broker.accesslayer.JdbcAccess] ERROR: SQLException
> during the execution of the Update SQL query (for a
> org.apache.ojb.broker
> .Project): ORA-00001: unique constraint (CAGRAWALOJB.PERSON_PROJECT_PK)
> violated
> ^M
> ORA-00001: unique constraint (CAGRAWALOJB.PERSON_PROJECT_PK) violated
> ^M
> [org.apache.ojb.broker.accesslayer.JdbcAccess] ERROR: SQLException
> during the execution of the Update SQL query (for a
> org.apache.ojb.broker
> .Person): ORA-00001: unique constraint (CAGRAWALOJB.PERSON_PROJECT_PK)
> violated
> ^M
> ORA-00001: unique constraint (CAGRAWALOJB.PERSON_PROJECT_PK) violated
> ^M
> [org.apache.ojb.broker.ta.PersistenceBrokerFactoryDefaultImpl] INFO:
> Already created persistence broker instances: 6^M
> [org.apache.ojb.broker.ta.PersistenceBrokerFactoryDefaultImpl] INFO:
> Already created persistence broker instances: 7^M
> [org.apache.ojb.broker.accesslayer.JdbcAccess] ERROR: SQLException
> during the execution of the Update SQL query (for a
> org.apache.ojb.broker
> .Project): ORA-02292: integrity constraint (CAGRAWALOJB.TASK_FK_1)
> violated - child record found
> ^M
> ORA-02292: integrity constraint (CAGRAWALOJB.TASK_FK_1) violated - child
> record found
>
> -----Original Message-----
> From: Rajeev Kaul [mailto:Rajeev@;customercaresolutions.com]
> Sent: Wednesday, October 30, 2002 10:38 AM
> To: OJB Users List
> Subject: Re: Newbie: Running junit target on Oracle fails for OJB
> (0.9.7)
>
> You can find the answer in the archives.  Use the attached
> repository_internal.xml to fix your problem.
>
> ----- Original Message -----
> From: "CP Agrawal" <[EMAIL PROTECTED]>
> To: "'OJB Users List'" <[EMAIL PROTECTED]>
> Sent: Wednesday, October 30, 2002 8:12 AM
> Subject: Newbie: Running junit target on Oracle fails for OJB (0.9.7)
>
>
> > I am trying to run thru junit tests and tutorial examples, but ran
> into
> > few problems.
> > First problem was, prepare-testdb target had error when inserting
> > ojbcore-schema.sql. It fails in creating
> > CREATE TABLE OJB_DMAP_ENTRIES
> > (
> >     ID NUMBER NOT NULL,
> >     DMAP_ID NUMBER NOT NULL,
> >     KEY_OID LONG RAW,
> >     VALUE_OID LONG RAW
> > );
> > Because oracle allows only one column to be long raw per table. I
> > checked previous versions of OJB (0.9.6), same problem exists. Please
> > let me know what should be the fix.
> >
> > When I tried to ignore above problem and plow thru the unit tests, I
> get
> > bunch of transactions exceptions. I think I am not setting things
> > correctly.
> > To walk thru these examples I am not running any application server
> > (jboss or weblogic), is it a pre-requisite to run these examples?
> Please
> > find OJB.properties and test.xml files attached.
> >
> > Thanks
> > -- CP Agrawal
> >
>
>
> ------------------------------------------------------------------------
> ----
> ----
>
>
> > --
> > To unsubscribe, e-mail:
> <mailto:ojb-user-unsubscribe@;jakarta.apache.org>
> > For additional commands, e-mail:
> <mailto:ojb-user-help@;jakarta.apache.org>
>


----------------------------------------------------------------------------
----


> --
> To unsubscribe, e-mail:   <mailto:ojb-user-unsubscribe@;jakarta.apache.org>
> For additional commands, e-mail: <mailto:ojb-user-help@;jakarta.apache.org>


--
To unsubscribe, e-mail:   <mailto:ojb-user-unsubscribe@;jakarta.apache.org>
For additional commands, e-mail: <mailto:ojb-user-help@;jakarta.apache.org>

Reply via email to