Scribd
Upload
44 views3 pages

Purging of CM - PROV - TRXS Table: High. For The Health of The System, Purging of This Table Is Very Much Required

The document outlines a plan to purge data from the CM_PROV_TRXS table in the subscriber database to reduce its size of 46GB. It involves stopping relevant servers and schedulers, creating a new table and populating it with recent data from the old table, recreating indexes and materialized views, and verifying the process through analysis and application testing.

Uploaded by

Reddy sekhar
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
44 views3 pages

Purging of CM - PROV - TRXS Table: High. For The Health of The System, Purging of This Table Is Very Much Required

The document outlines a plan to purge data from the CM_PROV_TRXS table in the subscriber database to reduce its size of 46GB. It involves stopping relevant servers and schedulers, creating a new table and populating it with recent data from the old table, recreating indexes and materialized views, and verifying the process through analysis and application testing.

Uploaded by

Reddy sekhar
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 3

Purging of CM_PROV_TRXS Table

Business Justification: Currently CM_PROV_TRXS is using around 46 GB of Table Size and this is very
high. For the health of the System, purging of this table is very much required.

Affected Servers:

Provisioning Nodes:
Current State Before Activity Stop :

LPAR :10.87.128.12 /13 Servers To be Stopped (Responsibility VEL-MIDDLEWARE)


Servers To be Stopped (Responsibility VEL-MIDDLEWARE)
PROV_MP_SERVER1
PROV_ORI_SERVER1
Server1
Server3
PROV_MP_SERVER2
PROV_ORI_SERVER2

CM Nodes:
Current State Activity before Stop :
LPAR : 10.87.128.14/15
Stop All Schedulers (Responsibility OPERATIONS TEAM)
Stop the following Servers
CM_MP_SERVER1
CM_MP_SERVER2
CM_ORI_SERVER1
CM_ORI_SERVER2
server1
server2

Activity on the Subscriber DB


Subscriber DB: 10.87.132.15/10.87.132.16
(new CM_PROV_TRXS table creation/back up of data)
ODS DB: 10.87.132.43(MV drop and recreate on CM_PROV_TRXS)

Pre-Implementation Activities:

Stop all MDBs from MQ Node 10.87.128.12


Stop All CM Schedulers from 10.87.128.14/10.87.128.15
Take a snapshot of mview of CM_PROV_TRXS in UPSSODS. This should have create script with all
indexes and grants.

Implementation Activities:

Drop the mview of CM_PROV_TRXS in UPSSODS.


Drop mview log of CM_PROV_TRXS in UPSSSUBS.
Rename the table CM_PROV_TRXS to CM_PROV_TRXS_20AUG10 in UPSSSUBS.
Create a new table CM_PROV_TRXS exactly similar to CM_PROV_TRXS_20AUG10.
Script attached below. (including grants and any synonym, if there)
Populate newly created table CM_PROV_TRXS using the statement below.
insert into CM_PROV_TRXS select * from CM_PROV_TRXS_23MAY10 where
sys_creation_date> trunc(sysdate-7);
Create all required indexes and missing constraints on newly populated
table CM_PROV_TRXS.
Create mview log on newly created table CM_PROV_TRXS.
Create mview of this table in ODSUPSS using the script created in
step 1
Create required indexes (no constraints) on the mview.
Start the MDBs on MQ Node and CM Schedulers on CM Nodes

Verification Plan:

Analyse both tables and mview with cascade=>true and estimate_percent=>20.


Test from application that Provisioning requests are properly processed and getting inserted
into CM_PROV_TRXS table.

You might also like