Hello? ... RIX101 error writing to repository, 'FS100: Record "*INDEXES" does not exist.' trying to rebuild system index. (OpenInsight Specific)
At 06 NOV 1997 04:59:49PM Alex Cruise Eloquent wrote:
I've modified my runtime window generator to write to the repository "manually" rather than making Repository( "NEW"… ) calls, and this works quite well in general.
Occasionally though, one of my windows will stop working–the write statement to the SysRepos table fails, and Get_Status returns "RIX101^AXX^~OIWINEXE<windowID" (^=@VM). "RIX" would seem to me to denote "Repository Index". I've tried rebuilding the system index–at the end of the process, after all seven indices are "built," I get the FS100 mentioned in this post's subject. I've gone over my repository in pretty fine detail, and can't find any obvious problems with it… Does anyone know what I'm missing? RTI folks: Am I doing something unsupportable here? If so, I'd appreciate some form of reply. TIA, Alex acruise@istar.ca </QUOTE> —- === At 07 NOV 1997 05:27AM Carl Pates Sprezzatura wrote: === <QUOTE>Alex, Before rebuilding your system index, delete ALL the rows from your SYSREPOSIX table (you'll have to use DELETE_ROW, as CLEAR_TABLE can't be used on 'system' tables.) If you still have this problem afterwards then you may be referencing an non-existant repository entity from another one. (The repository likes to create entries without checking if they entities they are referencing physically exist!) I had a similar problem when I called a Stored Procedure from a form's QuickEvent.. I used "SYSPROG*STPROCEXE*MYPROC" instead of "SYSPROG*STPROCEXEMYPROC".
I was missing an asterisk so the system completly screwed up the index for STPROCEXE's, as it tried to index a new class of "MYPROC", type "STPROCEXE" with no entity name, instead of a new entity with no ClassId and a type of "STPROCEXE".
This was not easy to track down!
cpates@sprezzatura.com
World Leaders in all things RevSoft (Except VIP)
At 10 NOV 1997 06:37PM Cameron Revelation wrote:
Alex,
Carl's comments are correct. You can, AFAIK, use Clear_Table on a System Table that is aliased, which is helpful for cleaning up system index tables. Also, we are planning to improve the I/O layer of the Repository to prevent problems like Carl described with bad entity references. (Probably 3.6.)
Cameron Purdy
info@revelation.com