Yep...as near as I can tell...all the proper pieces are in the proper place. According to the System Admin folks, we are caught up on cume tapes, etc.
And yes...i understand that...the error is being generated while creating the index, not when accessing it...haven't been able to get that far yet. Also, the table that I am creating the index upon is populated.
The issue is that the create does not recognize the schema as existing, even though it does.
steve
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of DeLong, Eric
Sent: Friday, September 10, 2010 5:22 PM
To: Midrange Systems Technical Discussion
Subject: RE: OmniFind product question
Have you confirmed that all the prerequisites are configured?
Also, did you see this?
" Note: This stored procedure only defines the text search index. The text search index does not contain any data until after the first invocation of the SYSPROC.SYSTS_UPDATE stored procedure for the new text search index. You create the text search index after the table is initially populated. By creating the text search index after the table is initially populated, you avoid the firing of change triggers before an initial index update. "
http://publib.boulder.ibm.com/infocenter/iseries/v7r1m0/index.jsp?topic=/rzash/srchz_sps_systs_create.htm
-Eric
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Needles,Stephen J
Sent: Friday, September 10, 2010 12:49 PM
To: midrange-l@xxxxxxxxxxxx
Subject: RE: OmniFind product question
I apologize if this is not the correct place to post a question such as this...but I found nothing else that I considered an alternative.
I am trying to evaluate the OmniFind product from IBM and I am encountering a problem when creating an index.
The product has a generic SQ20427 error message that seems to be a catchall for whenever "An error occurred during a text search administrative procedure" occurs. The rest of the message supposedly spells out the "real" problem...which is...
The reason code is 339. The text returned is: THE SCHEMA 'THELIB' IS NOT EXISTDB2 ERROR: 462 Procedure or user-defined function
OBJECT_STATISTICS in QSYS2 returned a warning SQLSTATE.õà+. FILE
/QSYS.LIB/QTEMP.LIB/TEMPFILE.FILE/DSXDBCAT.MBR:1720..
However, THELIB does exist on this machine.
This is what I am running:
CALL SYSPROC/SYSTS_CREATE ('THELIB', 'txtindex', 'THELIB.testfile(wbxxml)', 'FORMAT INSO')
Anyone got any insights? I found nothing useful via Google.
Thanks!
steve
==============================================================================
This communication, including attachments, is confidential, may be subject to legal privileges, and is intended for the sole use of the addressee. Any use, duplication, disclosure or dissemination of this communication, other than by the addressee, is prohibited. If you have received this communication in error, please notify the sender immediately and delete or destroy this communication and all copies.
midrange.com
