May 7 2009

Out of deep Woods- Thanking the Heavens!!

A few days back, I found a huge index on my main transaction table in primary production database(9i RAC Database), which I suspected was not being used by any query. So I decided to monitor its usage using oracle 9i Monitoring usage command. And after monitoring it for a week, I found out that it was not beingused by any query. I dropped it just before production hour began on Monday after weekly backup and other maintenance activities were finished. This table was then  replicated to three other databases using updateable materialized view setup.So this production database became the master site for replication.

To my surprise, I found out that even though 45 minutes of production time had  elapsed, no new records were appended to the main transaction table whose unused function based index was dropped.
In my database alert log, I got this very weird error in both my RAC instances
Errors in file d:\oracle\admin\ctdp\udump\ctdp1_ora_424.trc
:ORA-26500: error on caching “SALES”.”TRANSACT” “

search on metalink and Google suggested
DBMS_REPUTIL.MAKE_INTERNAL_PKG (’EDBMS’,'TEST’);
DBMS_REPUTIL.SYNC_UP_REP(’EDBMS’,'TEST’);
but it was riskier too as said links.

And then— I decided to regenerate replication support~

For which, I took following steps on repadmin user at master site:

begin
dbms_repcat.suspend_master_activity(gname=>’master_replication_group_name’);
end;/
begin
dbms_repcat.generate_replication_support( sname => ’schemanameofmastertable’,
oname => ‘tablenamewhichisrepliciated’,
type => ‘TABLE’,
min_communication => TRUE);
end;
/

begin
dbms_repcat.resume_master_activity(gname=>’master_replication_group_name’);
end;
/

Thank God! It worked!!

Now It was clear the culprit was poor documentation of Oracle as oracle says  that you only  need to regenerate replication support when you change the object. But I did not change the master table .I dropped its one index and that cannot change to master table.Thats only an indirect change; not a change to structure of DB .

TAGS:

LEAVE A COMMENT

Subscribe Form

Subscribe to Blog