== COREDB - OPTIMIZING INDICES ...
java.sql.SQLException: ORA-00439: feature not enabled: Online Index Build
at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:125)
at oracle.jdbc.driver.T4CTTIoer.processError (T4CTTIoer.java:305)
at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:272)
at oracle.jdbc.driver.T4C8Oall.receive(T4C8Oall.java:626)
at oracle.jdbc.driver.T4CPreparedStatement.doOall8 (T4CPreparedStatement.java:182)
at oracle.jdbc.driver.T4CPreparedStatement.execute_for_rows(T4CPreparedStatement.java:630)
at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java :1081)
at oracle.jdbc.driver.OraclePreparedStatement.executeInternal(OraclePreparedStatement.java:2905)
at oracle.jdbc.driver.OraclePreparedStatement.execute(OraclePreparedStatement.java:2996)
at com.ontotext.kim.coredb.base.DBAdapter.executeDDL(DBAdapter.java:397)
at com.ontotext.kim.coredb.oracle.OracleDBAdapter.synchronize(OracleDBAdapter.java:292)
at com.ontotext.kim.coredb.util.PopulateCoreDb.populate (PopulateCoreDb.java:82)
at com.ontotext.kim.coredb.util.PopulateCoreDb.main(PopulateCoreDb.java:22)
java.sql.SQLException: ORA-00439: feature not enabled: Online Index Build
at oracle.jdbc.driver.DatabaseError.throwSqlException (DatabaseError.java:125)
at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:305)
at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:272)
at oracle.jdbc.driver.T4C8Oall.receive (T4C8Oall.java:626)
at oracle.jdbc.driver.T4CPreparedStatement.doOall8(T4CPreparedStatement.java:182)
at oracle.jdbc.driver.T4CPreparedStatement.execute_for_rows(T4CPreparedStatement.java:630)
at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1081)
at oracle.jdbc.driver.OraclePreparedStatement.executeInternal(OraclePreparedStatement.java:2905)
at oracle.jdbc.driver.OraclePreparedStatement.execute (OraclePreparedStatement.java:2996)
at com.ontotext.kim.coredb.base.DBAdapter.executeDDL(DBAdapter.java:397)
at com.ontotext.kim.coredb.oracle.OracleDBAdapter.optimize(OracleDBAdapter.java:318)
at com.ontotext.kim.coredb.util.PopulateCoreDb.populate(PopulateCoreDb.java:83)
at com.ontotext.kim.coredb.util.PopulateCoreDb.main(PopulateCoreDb.java:22)
== [time: 117ms]
=============================================================
On 9/25/06, Ilian Kitchukov <[EMAIL PROTECTED]
> wrote:
One more thing, if you insist on Derby after all, you have to manually
create a ./db subfolder in the kim_home_dir folder - it must exist before
KIM starts and there the Derby database files will be placed (sorry, it's
hardcoded, and this is what I mean crippled too). And there may still be
some other reason for crash, after all these ajustments and initialization
... when you do them it will show ...
Ilian
----- Original Message -----
From: "Ilian Kitchukov" <[EMAIL PROTECTED]>
To: "Jay Johnston" < [EMAIL PROTECTED]>; < [email protected]>
Sent: 25 September 2006, Monday 23:24
Subject: Re: [KIM-discussion] CoreDB
> Hi Jay,
>
> Besides that we've abandoned Derby implementation somwhere on the way to
> focus on the Oracle one, just changing the USE_CORE_DB flag will not do
> the
> work. Please, have a look at the page
> http://www.ontotext.com/kim/doc/sys-doc/kim-platform-administration/configure-core-module.html
> if your documentation is older and you don't have such.
>
> Read carefully what is written there (especially about the toolCoreDB) and
> bear in mind that switching on/off the CORE module when some documents
> have
> already been processed and stored will just lead to a big mess. So to
> summarize, 3 importatnt things:
> 1) turn CORE on/off only when you start from clear
> 2) use the toolCoreDB to create and init the tables in the database right
> after KIM starts (before trying to populate any docs)
> 3) bear in mind that Derby implementation was not updated for a long time
> and is crippled compared to Oracle one (also, the documentation page
> assumes
> Oracle implementation, there is no such thing as FTS in Derby)
>
> HTH,
> Ilian
>
> ----- Original Message -----
> From: "Jay Johnston" <[EMAIL PROTECTED]>
> To: < [email protected]>
> Sent: 25 September 2006, Monday 21:22
> Subject: [KIM-discussion] CoreDB
>
>
>> What is the procedure for getting CoreDB running with Derby in the
>> current
>> release? The current
>> documentation< http://www.ontotext.com/kim/doc/sys-doc/kim-platform-administration/configure-core-module.html>says
>> that oracle is the only supported database for CoreDB, but Derby is
>> uncommented in the CoreDB config file (while Oracle is commented out).
>> If
>> I
>> change the CoreDB option in install.properties to
>> com.ontotext.kim.KIMConstants.USE_CORE_DB = true
>> and run the populate tool, I receive the following error:
>>
>> Exception in thread "Thread-3"
>> java.lang.reflect.UndeclaredThrowableException
>> at $Proxy5.addDoc(Unknown Source)
>> at com.ontotext.kim.util.datastore.DatastoreProcess._$29835 (
>> DatastoreProcess.java:910)
>> at com.ontotext.kim.util.datastore.DatastoreProcess._$29816(
>> DatastoreProcess.java:481)
>> at com.ontotext.kim.util.datastore.DatastoreProcess.run (
>> DatastoreProcess.java:185)
>> Caused by: java.io.WriteAbortedException: writing aborted;
>> java.io.NotSerializableException:
>> org.apache.derby.impl.sql.compile.TableName
>> at java.io.ObjectInputStream.readObject0(ObjectInputStream.java
>> :1303)
>> ....etc.... (I can provide the rest of the Exception if it would help)
>>
>> Is there something I need to do to explicitly set up Derby?
>>
>> Thanks, Jay
>>
>>
>> __________ NOD32 1.1773 (20060925) Information __________
>>
>> This message was checked by NOD32 antivirus system.
>> http://www.eset.com
>>
>>
>
>
> --------------------------------------------------------------------------------
>
>
>> _______________________________________________
>> NOTE: Please REPLY TO ALL to ensure that your reply reaches all members
>> of
>> this mailing list.
>>
>> KIM-discussion mailing list
>> [email protected]
>> http://ontotext.com/mailman/listinfo/kim-discussion_ontotext.com
>>
>>
>> __________ NOD32 1.1773 (20060925) Information __________
>>
>> This message was checked by NOD32 antivirus system.
>> http://www.eset.com
>>
>>
>
>
> _______________________________________________
> NOTE: Please REPLY TO ALL to ensure that your reply reaches all members of
> this mailing list.
>
> KIM-discussion mailing list
> [email protected]
> http://ontotext.com/mailman/listinfo/kim-discussion_ontotext.com
>
>
> __________ NOD32 1.1773 (20060925) Information __________
>
> This message was checked by NOD32 antivirus system.
> http://www.eset.com
>
>
_______________________________________________ NOTE: Please REPLY TO ALL to ensure that your reply reaches all members of this mailing list.
KIM-discussion mailing list [email protected] http://ontotext.com/mailman/listinfo/kim-discussion_ontotext.com
