ERROR DURING TRIGGER EXECUTION

Question

Hello
I need help on this issue.
I've a table with a INDEXTYPE (INDEXTYPE IS CTXSYS.CONTEXT;) on one Column
Every Time I Update,Insert,Delete one record I need to rebuild this Index or I can't access this modified Record
SO I Thought to built a Trigger that Calls a Procedure to Rebuild the Index AFTER UPDATE,INSERT or DELETE
Now when I Update or insert or Delete a record in the Table I get the Error Message :
SYS@cfmt > update IWS.ALUMNI_SEARCH set FIRST_NAME = 'TEST' where INTEGRATION_ID = 1000026;
update IWS.ALUMNI_SEARCH set FIRST_NAME = 'TEST' where INTEGRATION_ID = 1000026
ERROR at line 1:
ORA-00054: resource busy and acquire with NOWAIT specified
ORA-06512: at "IWS.REBUILD_ALUMDATA", line 15
ORA-06512: at "IWS.TRG_REB_ALUM", line 5
ORA-04088: error during execution of trigger 'IWS.TRG_REB_ALUM'
Any ideas
TRIGGER SCRIPT :
CREATE OR REPLACE TRIGGER IWS.TRG_REB_ALUM
AFTER
     INSERT OR
     UPDATE OR
     DELETE ON
IWS.ALUMNI_SEARCH
FOR EACH ROW
DECLARE
BEGIN
IWS.REBUILD_ALUMDATA;
COMMIT;
END;
INDEX
CREATE INDEX ALUMNI_DATA ON ALUMNI_SEARCH
(ALUMNI_DATA)
INDEXTYPE IS CTXSYS.CONTEXT;

Answer 1

Ah. Since you are using a desupported version, neither resync on commit nor transactional Text indexes. Any chance you could upgrade to a more recent version of the database?
If you are stuck on 9.2, are you really certain that you need the newly added rows available for searching immediately? That's a pretty unusual requirement for doing full-text searching. Any chance you could just schedule a periodic refresh every few minutes?
If you absolutely need immediate refreshes and you're stuck in a desupported database version, you could potentially have your trigger submit a job via the DBMS_JOB package that did your index rebuild asynchronously after your transaction committed (which would mimic the ON COMMIT attribute introduced in 10g). Since you are trying to do an ALTER INDEX, which is DDL, you won't be able to do that directly in a trigger. You might be able to call CTX_DDL.Sync_Index instead of issuing the ALTER INDEX, but I would wager that this has the same problem of doing implicit commits, and is thus ineligible to be called from a trigger.
Justin
Edited by: Justin Cave on Dec 12, 2008 1:04 PM
Generally, it's a bad idea to be using the SYS account for anything other than the small handful of administrative tasks that actually require logging in as SYS. You would generally want to use the appropriate object owner account, or at least a separate account that you created and granted appropriate privileges. SYS is special, and there are frequently behaviors that are different for SYS than other users that cause all sorts of confusion. Additionally, it's a bad idea from a security perspective to have people accessing the most powerful account in the database for routine operations.