Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 9 Next »

Monday 10-08-2007

Sunday 10-07-2007

  • 07:00 (Patrick) I've rebuilt the TA tables with current data and the synonyms now point there. The job completed at 7am.
  • 12:20 (Prabhu) I disable monitor when tables dropped and enable when new ones created as below. 
    • ---Enable monitoring
SQL> alter index sakai_external.CM_INST_TA_PERSON_IDX monitoring usage;
Index altered.
SQL> alter index sakai_external.CM_SECTION_TA_EID_IDX monitoring usage;
Index altered.
SQL> select index_name, table_name, monitoring, used, end_monitoring from v$object_usage;
no rows selected

---Disable monitoring
alter index sakai_external.CM_INST_TB_PERSON_IDX nomonitoring usage;
alter index sakai_external.CM_SECTION_TB_EID_IDX nomonitoring usage;

Saturday 10-06-2007

  • 06:58 (Patrick) I switched to the recreated TB tables. The job started at 6:58am and completed at 7:06.
    • I checked the problem query on both the TA and TB tables and it looks like the indexes are still being used.
    • I noticed that there are 151 pairs of duplicate EID's in the SECTION table. Have we considered changing the view to weed those out?
  • 24:00 (Oracle) run stats

Friday 10-05-2007

  • 22:00 (Oracle) run stats
  • 14:49 (Patrick) 
    • Thanks, Brian. I created the indexes and added these statements to the
script that recreates the tables for the synonym switch. There are
currently no outstanding queries in the poor performance category.
  • 11:43 (Brian) 
    • Oh, I see, I didn't put an index on it because it was all null.  Okay,
here are indexes for the courseset_eid and courseoffering_eid columns,
both of which are all null.

CREATE INDEX CM_MEMBERSHIP_TA_CS_IDX ON COURSEMANAGEMENT_MEMBERSHIP_TA
(COURSESET_EID) STORAGE(INITIAL 50M NEXT 10M);
CREATE INDEX CM_MEMBERSHIP_TB_CS_IDX ON COURSEMANAGEMENT_MEMBERSHIP_TB
(COURSESET_EID) STORAGE(INITIAL 50M NEXT 10M);

CREATE INDEX CM_MEMBERSHIP_TA_CO_IDX ON COURSEMANAGEMENT_MEMBERSHIP_TA
(COURSEOFFERING_EID) STORAGE(INITIAL 50M NEXT 10M);
CREATE INDEX CM_MEMBERSHIP_TB_CO_IDX ON COURSEMANAGEMENT_MEMBERSHIP_TB
(COURSEOFFERING_EID) STORAGE(INITIAL 50M NEXT 10M);

That will create the indexes on both tables.

Thursday 10-04-2007

  • 15:20 (Patrick) Run coursemanagement_merge_procs.sql
    • coursemanagement_merge_procs.sql
    • Script run fine for:
      • coursemanagement_section
      • coursemanagement_offering
    • coursemanagement_enrollment
    • Script hung during the delete records process for:
      • coursemanagement_instructors
      • coursemanagement_membership

Wednesday 10-03-2007

  • ... ?

Tuesday 10-02-2007

  • ... ?

Monday 10-01-2007

  • ... ?

Sunday 09-30-2007

  • ... ?

Saturday 09-29-2007

  • ... ?
  • No labels