The only known bug, and it may have been fixed since my experiences, is that the clause can only be ~300 bytes in length. Anything after that is truncated.
The important thing is making sure the syntax is right when you add the ardb.conf entry. Use the SQL logs to view the 'create index' ddl that is used; if your entry is not shown, then it is probably a syntax issue where arserverd can not identify the appropriate entry to append to the create index statement. Seeing as the index was created, I would say this is the case. Axton Grams These statements represent my opinions and nothing more. On Mon, Jun 7, 2010 at 4:28 AM, Fatima <[email protected]> wrote: > ** > Hi Everyone, > I updated the ardb.conf to save any indexes created on this form to a > different Tablespace as follows: > Form:test <----- this is the name of the form > Index { > Clause:TABLESPACE INDX <--- this is the name of the tablespace to save the > indexes on > } > > After updating the ardb.conf and saving it, I created a new index from the > Admin tool, but it got created on the default tablespace. > What am I doing wrong? > > I tested to create an index on that same tablespace directly from Oracle > with the application username and it worked, I also tested to add a clause > to the CREATE TABLE statement as follows: > Form:test > Clause:TABLESPACE INDX > > and it worked it created the new table on this tablespace. > > We are running: > ARS 6.3 > Solaris 10 > Oracle 9.2.0.7 > > Is there any known bugs in dealing with ardb.conf with these ars and/or > Oracle versions? > > Appreciate your help. > > Regards, > Fatima Mahdi > _attend WWRUG10 www.wwrug.com ARSlist: "Where the Answers Are"_ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug10 www.wwrug.com ARSlist: "Where the Answers Are"
