Loading the first set of triples goes well. But when I try to load the second set of triples, I get the exception below.

Some thoughts:
1) I dont think this is data problem because I uploaded all the data during an earlier test + when I upload the same data on an empty database it works fine.
2) I saw some earlier posts with similar error but none of the seem to be using the Jena adaptor..
3) The model also has a OWL Prime entailment in incremental mode.
4) I am not sure if this is relevant but... Before I ran the current test, I mistakenly launched multiple of java processes that bulk loaded the data. Ofcourse I killed all the processes and dropped the sem_models and the backing rdf tables they were uploading to.

EXCEPTION
java.sql.SQLException: ORA-06502: PL/SQL: numeric or value error: character string buffer too small
ORA-06512: at "MDSYS.SDO_RDF_INTERNAL", line 3164
ORA-06512: at "MDSYS.SDO_RDF_INTERNAL", line 4244
ORA-06512: at "MDSYS.SDO_RDF", line 276
ORA-06512: at "MDSYS.RDF_APIS", line 693
ORA-06512: at line 1

at oracle.jdbc.driver.SQLStateMapping.newSQLException(SQLStateMapping.java:70)
at oracle.jdbc.driver.DatabaseError.newSQLException(DatabaseError.java:131)
at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:204)
at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:455)
at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:413)
at oracle.jdbc.driver.T4C8Oall.receive(T4C8Oall.java:1034)
at oracle.jdbc.driver.T4CCallableStatement.doOall8(T4CCallableStatement.java:191)
at oracle.jdbc.driver.T4CCallableStatement.executeForRows(T4CCallableStatement.java:950)
at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1222)
at oracle.jdbc.driver.OraclePreparedStatement.executeInternal(OraclePreparedStatement.java:3387)
at oracle.jdbc.driver.OraclePreparedStatement.execute(OraclePreparedStatement.java:3488)
at oracle.jdbc.driver.OracleCallableStatement.execute(OracleCallableStatement.java:3840)
at oracle.jdbc.driver.OraclePreparedStatementWrapper.execute(OraclePreparedStatementWrapper.java:1086)
at oracle.spatial.rdf.client.jena.Oracle.executeCall(Oracle.java:689)
at oracle.spatial.rdf.client.jena.OracleBulkUpdateHandler.addInBulk(OracleBulkUpdateHandler.java:740)
at oracle.spatial.rdf.client.jena.OracleBulkUpdateHandler.addInBulk(OracleBulkUpdateHandler.java:463)
at oracleuploadtest.OracleUploader.loadModelToDatabase(OracleUploader.java:84)
at oracleuploadtest.RunOracleUploadTest.main(RunOracleUploadTest.java:81)

You have encountered a bug having to do with the length of the schema qualified name of the staging table. As a workaround, please shorten the name of the staging table so that the length(schema_name)+length(staging_table_name) <= 25.

Please note that Jena adapter automatically generates the staging table name using the RDF model name appended to a short prefix of length 5. So, for your testing, please use a shorter model name for now so that length(schema_name)+length(generated staging_table_name) <= 25.

We will fix this bug and make the fix available at the earliest opportunity.

I have got in a muddle this morning.
I thought I saw this bug in the behavior of my code yesterday, with a simple test failing with this error.
So I wrote work-around code that uses batch loader instead of bulk loader if the 25 condition is exceeded.

Then today, I started by writing a test that would fail if the oracle issue mentioned in this thread were resolved, to remind me to remove my work-around in the future.

However, that test failed, and I now cannot reproduce the issue described in this thread; I removed my work-around code and the tests that were failing yesterday are now succeeding!
Such is life, but it is confusing.

The addInBulk method needs to be called twice to trigger the bug. Here is a test case that passes only while the bug is present! (It is to remind me to remove the workaround code when the fix gets through to my code).

I think you're are right, I'm getting the following exception when I use a model name with 17 characters (table name 21 characters). But when I use a shorter name it works.
I'm using the recent Jena Adaptor 11.2.3 and this bug is still there:

java.sql.SQLException: ORA-06502: PL/SQL: numeric or value error: character string buffer too small
ORA-06512: at "MDSYS.SDO_RDF_INTERNAL", line 3164
ORA-06512: at "MDSYS.SDO_RDF_INTERNAL", line 4244
ORA-06512: at "MDSYS.SDO_RDF", line 276
ORA-06512: at "MDSYS.RDF_APIS", line 693
ORA-06512: at line 1