Thanks for your help Ben.

Oracle Version Info:
Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - 64bit Production
PL/SQL Release 11.2.0.1.0 - Production
CORE    11.2.0.1.0      Production
TNS for Linux: Version 11.2.0.1.0 - Production
NLSRTL Version 11.2.0.1.0 - Production

The surefire reports show 3 failures and 47 errors.

Maybe something is wrong with my setup.  But a lot works in spite of these 
failures.

Focusing on just the first error for now...

Test class: 
Test being executed: OracleDataStoreAPIOnlineTest
Test in error: testGetFeaturesWriterAdd
Exception message: ROAD is read only
Thrown by: ContentDataStore
    protected final ContentFeatureStore ensureFeatureStore(String typeName, 
Transaction tx) 
        throws IOException {
        
        ContentFeatureSource featureSource = getFeatureSource(typeName,tx);
        if ( !( featureSource instanceof ContentFeatureStore)) {
            throw new IOException(typeName + " is read only" );
        }

        return (ContentFeatureStore) featureSource;
    }

This is the script that created my test schema in Oracle:
DEF SA_SCHEMA_NAME=FDOTGEOTOOLS
DEF SA_SCHEMA_PASSWORD=FDOTGEOTOOLS
DEF SA_SCHEMA_DATAFILE=/u03/oradata/NWDEV/FDOTGEOTOOLS.dbf
DEF SA_SCHEMA_DATAFILE_SIZE=64M
DEF SA_SCHEMA_AUTOEXTEND_SIZE=64M
DEF SA_SCHEMA_MAXSIZE=UNLIMITED
CREATE TABLESPACE "&&SA_SCHEMA_NAME" DATAFILE '&SA_SCHEMA_DATAFILE' 
                  SIZE &SA_SCHEMA_DATAFILE_SIZE AUTOEXTEND ON NEXT 
&SA_SCHEMA_AUTOEXTEND_SIZE MAXSIZE &SA_SCHEMA_MAXSIZE
                   EXTENT MANAGEMENT LOCAL AUTOALLOCATE;
CREATE USER "&&SA_SCHEMA_NAME" PROFILE "DEFAULT"
IDENTIFIED BY "&&SA_SCHEMA_PASSWORD" DEFAULT TABLESPACE "&&SA_SCHEMA_NAME"
ACCOUNT UNLOCK;
COMMIT;
GRANT "CONNECT" TO "&&SA_SCHEMA_NAME";
GRANT ALTER SESSION TO "&&SA_SCHEMA_NAME";
GRANT ALTER TABLESPACE TO "&&SA_SCHEMA_NAME";
GRANT CREATE PROCEDURE TO "&&SA_SCHEMA_NAME";
GRANT CREATE SEQUENCE TO "&&SA_SCHEMA_NAME";
GRANT CREATE SESSION TO "&&SA_SCHEMA_NAME";
GRANT CREATE SYNONYM TO "&&SA_SCHEMA_NAME";
GRANT CREATE TABLE TO "&&SA_SCHEMA_NAME";
GRANT CREATE TRIGGER TO "&&SA_SCHEMA_NAME";
GRANT CREATE TYPE TO "&&SA_SCHEMA_NAME";
GRANT CREATE VIEW TO "&&SA_SCHEMA_NAME";
GRANT EXECUTE ANY PROCEDURE TO "&&SA_SCHEMA_NAME";
GRANT EXECUTE ANY TYPE TO "&&SA_SCHEMA_NAME";
GRANT DBA TO "&&SA_SCHEMA_NAME";
GRANT SELECT ANY DICTIONARY TO "&&SA_SCHEMA_NAME";
GRANT CREATE DATABASE LINK TO "&&SA_SCHEMA_NAME"; 
COMMIT;
ALTER USER "&&SA_SCHEMA_NAME" QUOTA UNLIMITED ON "&&SA_SCHEMA_NAME";
COMMIT;

Before this error the console shows: INFO No primary key or unique index found 
for ROAD.

In case it's meaningful in terms of what works vs. not here is a list of the 
tables in my schema after running the tests.  Note that I've selectively run 
some individual tests since I did the full run.
exec dbms_stats.gather_schema_stats('FDOTGEOTOOLS');
select table_name,num_rows from user_tables order by table_name;
TABLE_NAME      NUM_ROWS
COLA_MARKETS_CS 1
CURVES  10
DATES   3
EMPTY   0
FT1     3
FTJOIN  4
FTJOIN2 4
FTNTABLE        0
GTMETA  1
GT_PK_METADATA  4
LAKE    1
LAKES   1
LINE3D  2
MDRT_5DCA1$     
MDRT_5DCAF$     
MDRT_5DE2E$     
MDRT_5E69B$     
MDRT_5EDE5$     
MDRT_5EDF1$     
MDRT_5EDFE$     
MDRT_5EFDC$     
MDRT_5F037$     
MDRT_5F1BD$     
MDRT_5F484$     
MDRT_5F820$     
MDRT_5FBAA$     
MDRT_5FBB8$     
MDRT_5FBC6$     
MULTI   3
NEIGHBORS       25
NOKEY   3
NONFIRST        3
NONINC  3
PERSON  2
PLAINTABLE      3
POINT3D 2
RIVER   2
ROAD    3
SEQ     3
SEQTABLE        3
SKIPCOLUMN      1
TESTLOB 1
TESTLOBCREATE   0
TMULTIPOINT     0
UNIQ    3
ZIPCODE 0

-----Original Message-----
From: Ben Caradoc-Davies [mailto:b...@transient.nz] 
Sent: Thursday, October 08, 2015 6:05 PM
To: Walter Stovall; geotools-devel@lists.sourceforge.net
Subject: Re: [Geotools-devel] I would like to make a bug fix and need help on 
the process

On 09/10/15 02:55, Walter Stovall wrote:
> What's the difference between a "failure" and an "error"?

A failure is when a JUnit assertion fails (an AssertionFailedError is thrown 
and caught in the enclosing JUnit TestRunner) and errors are when other 
exceptions are thrown. In practice they are all just failures from our point of 
view and the distinction can be ignored.

>    OracleDataStoreAPIOnlineTest
[...]
>    OracleSpatialFiltersOnlineTest
[...]
> Being as new to the tool as I am and with limited time to invest, I'm not 
> very prepared to dive into debugging those tests.  Are they perhaps somehow 
> obsolete or would you more suspect something about my environment?

Tests are run by maven-surefire-plugin and full stack traces for these failures 
can be found in its reports. For these tests:

jdbc-oracle/target/surefire-reports/org.geotools.data.oracle.OracleDataStoreAPIOnlineTest.txt
jdbc-oracle/target/surefire-reports/org.geotools.data.oracle.OracleSpatialFiltersOnlineTest.txt

The full stack trace can be very revealing.

What is your Oracle version? Vanilla or Enterprise? Locator or Spatial? 
Are you using XE? How much memory and disk? Do you see any errors in the Oracle 
logs?

Kind regards,

--
Ben Caradoc-Davies <b...@transient.nz>
Director
Transient Software Limited <http://transient.nz/> New Zealand

------------------------------------------------------------------------------
_______________________________________________
GeoTools-Devel mailing list
GeoTools-Devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geotools-devel

Reply via email to