This content has been marked as final. Show 5 replies
Don't quite understand that, I thought CTXSYS.SYNCRN was the internal function which implemented CTX_DDL.SYNC_INDEX.
But you're saying that you're not running SYNCs at all?
Can you check the parameters used in creating the index? Are you sure you don't have SYNC(ON COMMIT) ?
As an aside, it's pretty dangerous to use the TRANSACTIONAL keyword without SYNC(ON COMMIT), or at least very regular syncs. The TRANSACTIONAL keyword requires queries to scan through all committed but not-yet-synced records as part of the query. If there are more than a few such records, it can make your queries run really slowly.
ctxsys.syncrn() is called during commit callback for $R maintenance during DML and is not related to ctx_ddl.sync_index.
Many thanks for your replies and apologies for not specifying the version number. It's 188.8.131.52, so it's probably not the bug described in Barbara's link.
I'm going to see if I can find some more information about $R maintenance; again, any tips on this are appreciated.
We are facing the same problem on a 10.2.0.5 database. Did you find the answer to the above problem?