TELECOM Proposal for DRAGON Change Request for SERVER LOADER 6.3.2 Upgrade TO DATALOADING 6.7 Prepared by: Date Prepared: 25 Dec 2015 V1.0 Telecom DRAGON Change datafiles management Document Information Project Name: Telecom Dragon Change datafiles managements Project Manager: Document Version No: Opportunity Roadmap Phase: Document Version Date: Quality Review Method: Prepared By: Preparation Date: Reviewed By: Review Date: Distribution List From To Action* Date Phone/Fax Due Date Phone/Fax * Action Types: Approve, Review, Inform, File, Action Required, Attend Meeting, Other (please specify) Version History Ver. No. Ver. Date HPE Global Method PJM2350T (Version 0/22-Feb-2016) Project_Document_Id Revised By Description Filename Page 2 of 8 Last changed: 27 April 2016 at 17:49 V1.0 Telecom DRAGON Change datafiles management Proprietary Notice The information contained in all sheets of this document, proposal, or quotation constitutes trade secrets and/or information that is commercial or financial and is deemed confidential or privileged. It is furnished to TELECOM in confidence with the understanding that TELECOM will not, without the permission of Hewlett Packard (from now on called HPE or Hewlett Packard Enterprise), use or disclose for other than evaluation purposes the information contained herein which is solely confidential and proprietary to Hewlett Packard Enterprise ("Confidential Information"). In the event a contract is awarded on the basis of this document, proposal, or quotation, TELECOM shall have the right to use and disclose Hewlett Packard Enterprise Confidential Information to the extent provided in the contract. The restriction does not limit TELECOM right to use or disclose such information if obtained from another source without restriction. HPE Global Method PJM2350T (Version 0/22-Feb-2016) Project_Document_Id Page 3 of 8 Last changed: 27 April 2016 at 17:49 V1.0 Telecom DRAGON Change datafiles management Table of Contents Proprietary Notice ...................................................................................................................................................... 3 1. Introduction ........................................................................................................................................................ 5 1.1. Audience ..................................................................................................................................................................................... 5 1.2. References .................................................................................................................................................................................. 5 2. Management Summary ..................................................................................................................................... 5 3. Purpose and Scope ............................................................................................................................................. 5 4. Implementation Scope....................................................................................................................................... 6 4.1. 5. Implementation Approach ................................................................................................................................................... 6 Project Implementation ..................................................................................................................................... 8 5.1. Organization .............................................................................................................................................................................. 8 5.2. Project Delivery Restrictions ................................................................................................................................................ 8 5.3. Customer Responsibilities .................................................................................................................................................... 8 5.3.1. Acceptance .................................................................................................................................................................................. 8 5.3.2. Acceptance Testing .................................................................................................................................................................. 8 5.3.3. Data Migration .......................................................................................................................................................................... 8 5.3.4. Remote Connection ................................................................................................................................................................. 8 5.3.5. Data Sanitation ......................................................................................................................................................................... 8 5.3.6. Functional Specification Approval ...................................................................................................................................... 8 5.3.7. Change Request Management ............................................................................................................................................ 8 5.3.8. Test Environment Availability .............................................................................................................................................. 8 6. Hardware ............................................................................................................................................................. 8 7. Appendix .............................................................................................................................................................. 8 HPE Global Method PJM2350T (Version 0/22-Feb-2016) Project_Document_Id Page 4 of 8 Last changed: 27 April 2016 at 17:49 V1.0 Telecom DRAGON Change datafiles management 1. Introduction This document covers CR Implementation for TELECOM DRAGON to change datafiles managements, scope of CR is remove dba privilegies to application db user (drguser), so it is no longer possible CREATE and DROP TABLESPACE and MANAGE DATAFILES. It is necessary to define a list of datafiles, with the FS distribution also, and create just one time in the upgrade project. 1.1. Audience 1.2. References 2. Management Summary The Telecom DBA team suggests to change DRAGON application to not use any oracle users with DBA privileges, in particular DRAGON application should not create or drop oracle tabplespace. HPE is delighted to offer to TELECOM, the Implementation for TELECOM DRAGON to load data without manage the oracle datafiles, using DATALOADING version 6.7. TELECOM DRAGON Administration teams would like to migrate the data to the old tablespaces to the new approach. This would shorten the backup of the DRAGON DB, as there will be less data in the DRAGON DB. This proposal is for upgrading the existing TELECOM DRAGON Server Loader (version 6.3.2) to version Dataloaging 6.7.x and modifying the tablespaces and filesystems used. The following modules, for all flow, are impacted by CR: NORMALIZER LOADER DBSTORE PURGER 3. Purpose and Scope This proposal covers CR Implementation for TELECOM DRAGON to change datafiles managements using version 6.7.x of Dataloading. HPE Global Method PJM2350T (Version 0/22-Feb-2016) Project_Document_Id Page 5 of 8 Last changed: 27 April 2016 at 17:49 V1.0 Telecom DRAGON Change datafiles management 4. Implementation Scope HPE offers TELECOM to implement the following: 4.1. DRAGON Server Loader upgrade to Dataloading version 6.7.x. All custom configuration flow currently implemented in TELECOM environment will be migrated to the new Dataloading component. The old Server Loader component (NORMALIZER, LOADER;DBSTORE and PURGER) for all flow will be completely dismissed. The actual fs management will be changed, Dataloading does not handle the file system, it will not check if there is space before proceeding with loading data. The data will be purged only logical but not fiscally, using DROP TABLE TABLE_NAME PURGE condition Dragon Dataloading will use a pre – created tablespace to load data. Implementation Approach Upgrade will be carried on the DRAGON Test System first at TELECOM and it will be carried to the production system upon completion of the testing. The file system management will be delegated to Telecom DBA team, they will guarantee that there is enough space to load data in each tablespaces defined at startup of the system. The new DRAGON DataLoading component assumes that tablespaces will be already present, there isn’t any check from this component used to verify the space left on each tablespace. In case of error during loading task caused by missing space, the DRAGON component will stop to load and it will report the issue clearly on the log file, after that the DBA team will be responsible to manage properly the space missing adding new one. The new DRAGON DataLoading component will offer the capability to configure the tablespace name, in total it will be possible to define four different tablespaces for each stream, assigned as described below, based in this highlights: Split the tablespaces for each flow (7 in total) Keep DATA and INDEX in separate tablespaces Also split for ONLINE DATA and COMPRESSED one (just for the flow that have compressed, not all). HPE Global Method PJM2350T (Version 0/22-Feb-2016) Project_Document_Id Page 6 of 8 Last changed: 27 April 2016 at 17:49 V1.0 Flow Telecom DRAGON Change datafiles management Tablespace Name Note WVOICE TS_WVOICE_DATA_ONLINE Used to host DATA for ONLINE for flow WVOICE WVOICE TS_WVOICE_INDEX_ONLINE Used to host INDEX for ONLINE for flow WVOICE WVOICE TS_WVOICE_DATA_COMPRESSED Used to host data for COMPRESSED DB for flow WVOICE WVOICE TS_WVOICE_INDEX_COMPRESSED Used to host INDEX for COMPRESSED DB for flow WVOICE WSMS TS_WSMS_DATA_ONLINE Used to host DATA for ONLINE for flow WSMS WSMS TS_WSMS_INDEX_ONLINE Used to host INDEX for ONLINE for flow WSMS WSMS TS_WSMS_DATA_COMPRESSED Used to host data for COMPRESSED DB for flow WSMS WSMS TS_WSMS_INDEX_COMPRESSED Used to host INDEX for COMPRESSED DB for flow WSMS WGPRS TS_WGPRS_DATA_ONLINE Used to host DATA for ONLINE for flow WGPRS WGPRS TS_WGPRS_INDEX_ONLINE Used to host INDEX for ONLINE for flow WGPRS WGPRS TS_WGPRS_DATA_COMPRESSED Used to host data for COMPRESSED DB for flow WGPRS WGPRS TS_WGPRS_INDEX_COMPRESSED Used to host INDEX for COMPRESSED DB for flow WGPRS FVOICE TS_FVOICE_DATA_ONLINE Used to host DATA for ONLINE for flow FVOICE FVOICE TS_FVOICE_INDEX_ONLINE Used to host INDEX for ONLINE for flow FVOICE FVOICE TS_FVOICE_DATA_COMPRESSED Used to host data for COMPRESSED DB for flow FVOICE FVOICE TS_FVOICE_INDEX_COMPRESSED Used to host INDEX for COMPRESSED DB for flow FVOICE FSMS TS_FSMS_INDEX_ONLINE Used to host DATA for ONLINE for flow FSMS * NOT COMPRESSED REQUIRED FOR THIS FLOW FSMS TS_FSMS_INDEX_ONLINE Used to host INDEX for ONLINE for flow FSMS * NOT COMPRESSED REQUIRED FOR THIS FLOW FVOD TS_FVOD_DATA_ONLINE Used to host DATA for ONLINE for flow FVOD * NOT COMPRESSED REQUIRED FOR THIS FLOW FVOD TS_FVOD_INDEX_ONLINE Used to host INDEX for ONLINE for flow FVOD * NOT COMPRESSED REQUIRED FOR THIS FLOW ENT TS_ENT_DATA_ONLINE Used to host DATA for ONLINE for flow ENT * NOT COMPRESSED REQUIRED FOR THIS FLOW ENT TS_ENT_INDEX_ONLINE Used to host INDEX for ONLINE for flow ENT * NOT COMPRESSED REQUIRED FOR THIS FLOW Tablespace used for each stream The DRAOGN PURGER that is fully integrated in the new DataLoading component will not drop tablespace as before but it will simply executes a drop table with purge condition. Without the actual functionality of drop and create tablespaces, the DBA privileges of the dragon oracle users, will not be more necessary, as Telecom requested. HPE Global Method PJM2350T (Version 0/22-Feb-2016) Project_Document_Id Page 7 of 8 Last changed: 27 April 2016 at 17:49 V1.0 Telecom DRAGON Change datafiles management 5. Project Implementation 5.1. Organization 5.2. Project Delivery Restrictions 5.3. Customer Responsibilities 5.3.1. Acceptance 5.3.2. Acceptance Testing 5.3.3. Data Migration Data Migration that consist to migrate data from current tabplespace to the new one defined by Telecom Personal is not part of this CR. HPE will be glad to support TP in case of doubts during the migration project. 5.3.4. Remote Connection 5.3.5. Data Sanitation N/A. 5.3.6. Functional Specification Approval 5.3.7. Change Request Management 5.3.8. Test Environment Availability 6. Hardware No hardware is included in this proposal. 7. Appendix HPE Global Method PJM2350T (Version 0/22-Feb-2016) Project_Document_Id Page 8 of 8 Last changed: 27 April 2016 at 17:49
