You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jdo-dev@db.apache.org by "Michael Bouschen (JIRA)" <ji...@apache.org> on 2008/01/17 23:08:34 UTC

[jira] Created: (JDO-570) Problem with schema handling when running TCK with oracle

Problem with schema handling when running TCK with oracle 
----------------------------------------------------------

                 Key: JDO-570
                 URL: https://issues.apache.org/jira/browse/JDO-570
             Project: JDO
          Issue Type: Bug
          Components: tck2, tck2-legacy
    Affects Versions: JDO 2 maintenance release 1
            Reporter: Michael Bouschen
            Priority: Minor


Running the CompletenessTest against an Oracle database results in an exception:  
    [java] javax.jdo.JDODataStoreException: [JPOX-052208] Insert of object "org.apache.jdo.tck.pc.company.Company@c16b18
" using statement "INSERT INTO applicationidentity0.COMPANIES (ADDRID,CITY,COUNTRY,"STATE",STREET,ZIPCODE,"NAME",FOUNDED
DATE,ID,DISCRIMINATOR) VALUES (?,?,?,?,?,?,?,?,?,?)" failed : ORA-00942: Tabelle oder View nicht vorhanden
    [java]
    [java]      at org.jpox.jdo.JPOXJDOHelper.getJDOExceptionForJPOXException(JPOXJDOHelper.java:289)
    [java]      at org.jpox.jdo.AbstractPersistenceManager.jdoMakePersistent(AbstractPersistenceManager.java:646)
    [java]      at org.jpox.jdo.AbstractPersistenceManager.makePersistentAll(AbstractPersistenceManager.java:695)
    [java]      at org.apache.jdo.tck.mapping.CompletenessTest.localSetUp(CompletenessTest.java:79)
The table applicationidentity0.COMPANIES cannot be found. 

The table qualifier applicationidentity0 comes from the option javax.jdo.mapping.Schema. The maven goal doRuntck.jdori adds this option to the pmf properties. Oracle is able to find the table if the option is omitted from the pmf properties.

I also tried using applicationidentity0 as a table qualifier when creating the schema. But Oracle seems to interpret the qualifier as the user name. Loading the schema with sqlplus results in an exception saying there is no such user 'APPLICATIONIDDENTITY0': 
prefix 
CREATE TABLE applicationidentity0.companies (
*
FEHLER in Zeile 1:
ORA-01918: Benutzer 'APPLICATIONIDENTITY0' ist nicht vorhanden

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.