Yes, the first link to the Oracle forum was the source of my original
question as it appears I may need another patch.  It appears that
there are patches for 11g itself and patches for the Jena adaptor,
which I believe are separate.  It might be helpful to post these
patches on the TBC forum in the future.  I will try to locate.
Thanks.

On Nov 19, 4:35 pm, Scott Henninger <[EMAIL PROTECTED]>
wrote:
> Paul;  It doesn't matter which serialization format you use
> (i.e .owl, .n3, etc.).  Oracle will store the data in their native
> format and the Composer/Oracle interface takes care of translation.
> RDF/XML-ABBREV, N3, N-TRIPLE, etc. are text serializations of and RDF
> data store.
>
> My question was more on the origins of the ontology and everything is
> good along that line. (and sorry for my typos! gads!)
>
> The basic error you have "component <xyz> must be declared" is an
> Oracle error resulting from a stored procedure not being defined.  The
> issue may be that your patches have not been installed properly,
> including the stored procedure 'ANALYZE_MODEL'.  There is a slight
> chance that the problem is with user permissions, but between the fact
> that the model was created in Composer and the specific name of the
> stored procedure, I rather doubt that.
>
> It is much more likely that the patch is the cause of the problem.
> This is a link to an Oracle forum to a TBC user with a similar problem
> on 10g:
>  http://forums.oracle.com/forums/thread.jspa?threadID=664928&tstart=30
>
> There is also a nice writeup on Oracle titled "Oracle Semantic
> Technologies Inference Best Practices with RDFS/OWL"
>  http://www.oracle.com/technology/tech/semantic_technologies/pdf/seman...
>
> This was a nice find for me, so maybe it can help if you didn't know
> about it.
> -- Scott
>
> On Nov 19, 5:51 pm, Paul <[EMAIL PROTECTED]> wrote:
>
>
>
> > I created it from scratch as an OWL file using TBC and I am using the
> > native export option to load into Oracle directly.  It is in RDF/XML-
> > ABBREV format.  Now that you mention this, I thought I did read that
> > 11g requires models in N3 format.  Is this accurate and if so, would
> > there be any loss to current functionality in TBC if I switch it to
> > a .N3 format?  I would be interested in also understanding best
> > practices around which format to use in general.  For
> > example....keeping it in .N3 format allows me to leverage any of the
> > current triples stores on the market, etc...
>
> > Thanks.
>
> > On Nov 19, 2:35 pm, Scott Henninger <[EMAIL PROTECTED]>
> > wrote:
>
> > > Payl;  Hoe did you create the model (.owl/.n3 file) and what is the
> > > query you are trying to run?  Some of those forums are about Jena SDB
> > > and I didn't get the impression you were using that.
> > > -- Scott
>
> > > On Nov 19, 4:08 pm, Paul <[EMAIL PROTECTED]> wrote:
>
> > > > No error messages in the log and I did verify that I have the latest
> > > > patch for 11g.  I can successfully query via SQL and the Oracle
> > > > console, so no worries there.  However, I do get a message in the
> > > > error log when I try to export an owl file to my Oracle instance using
> > > > TBC.  I have already performed all of the necessary steps to RDF
> > > > enable 11g and can add triples via the SQL console.  TBC fails with
> > > > the message below:
>
> > > > java.sql.SQLException: ORA-06550: line 1, column 21:
> > > > PLS-00302: component 'ANALYZE_MODEL' must be declared
> > > > ORA-06550: line 1, column 7:
> > > > PL/SQL: Statement ignored
>
> > > > at oracle.jdbc.driver.SQLStateMapping.newSQLException
> > > > (SQLStateMapping.java:70)
> > > > at oracle.jdbc.driver.DatabaseError.newSQLException(DatabaseError.java:
> > > > 110)
> > > > at oracle.jdbc.driver.DatabaseError.throwSqlException
> > > > (DatabaseError.java:171)
> > > > 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:1030)
> > > > at oracle.jdbc.driver.T4CCallableStatement.doOall8
> > > > (T4CCallableStatement.java:191)
> > > > at oracle.jdbc.driver.T4CCallableStatement.executeForRows
> > > > (T4CCallableStatement.java:944)
> > > > at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout
> > > > (OracleStatement.java:1222)
> > > > at oracle.jdbc.driver.OraclePreparedStatement.executeInternal
> > > > (OraclePreparedStatement.java:3381)
> > > > at oracle.jdbc.driver.OraclePreparedStatement.execute
> > > > (OraclePreparedStatement.java:3482)
> > > > at oracle.jdbc.driver.OracleCallableStatement.execute
> > > > (OracleCallableStatement.java:3839)
> > > > at oracle.jdbc.driver.OraclePreparedStatementWrapper.execute
> > > > (OraclePreparedStatementWrapper.java:1085)
> > > > at oracle.spatial.rdf.client.jena.GraphOracleSem.analyze
> > > > (GraphOracleSem.java:2863)
> > > > at
> > > > org.topbraidcomposer.oracle.wizards.export.OracleExportWizardPlugin.perform­­Finish
> > > > (OracleExportWizardPlugin.java:83)
> > > > at org.topbraidcomposer.wizards.export.ExportWizard$1.run
> > > > (ExportWizard.java:117)
> > > > at org.eclipse.jface.operation.ModalContext$ModalContextThread.run
> > > > (ModalContext.java:121)
>
> > > > In searching the web, Oracle forums note this as an issue in the Jena
> > > > adapter, requiring a patch.  Before I pursue this option, I would like
> > > > to understand whether TBC already has the latest patches for Jena and
> > > > if not, where can I locate the latest.  Thanks in advance.
>
> > > > On Nov 19, 11:10 am, Holger Knublauch <[EMAIL PROTECTED]> wrote:
>
> > > > > Are there any more details in the error log (Window > Show View).  
> > > > > Also, do you have all relevant patches for Oracle 11g's RDF support  
> > > > > installed?
>
> > > > > Holger
>
> > > > > On Nov 19, 2008, at 11:02 AM, Paul wrote:
>
> > > > > > I was sucessful in creating a connection to Oracle 11g and when I
> > > > > > click the .oracle file in my TBC project, it appears that it
> > > > > > automatically connects.  Upon connection, I get the same message
> > > > > > repeating in the console.
>
> > > > > > Could not perform query
>
> > > > > > Has anyone encountered this and should I be concerned?  I can
> > > > > > successfully execute SQL using the Oracle console, so that appears 
> > > > > > to
> > > > > > be working.  Thanks in advance.- Hide quoted text -
>
> > > > > - Show quoted text -- Hide quoted text -
>
> > > - Show quoted text -- Hide quoted text -
>
> - Show quoted text -
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"TopBraid Composer Users" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/topbraid-composer-users?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to