Rendered PDF File Page 1 of 8

DOC0585277, Rev:3

Electronic Signature Information

Name

DOC0585277

Revision

Type

Controlled Document

Title

IT_TSG_STD_DOC0585277_Tera_SysMgmt_OpEx

Originator

212044609_sue_e._paulson

Release Date

06/27/2012 07:22:24 PM

Obsolete Date

Name

Reason For Change

IT_TSG_STD_DOC0585277_Tera_SysMgmt_OpEx.doc

172544

Route

Signer

R5043002

Function Status

Comments

200018486_jeffrey_a_weitschat

Approve Approved as QM

R5043002

212044609_sue_e._paulson

Author

R5043002

212069082_sudheer__darapureddy

Approve Approved

Approving as
author

Periodic Review
There are no signatures or routes related to this business object.

Obsolesence Approval
There are no signatures or routes related to this business object.

* Printed versions are For Reference Only *

+ Indicates a task was reassigned from an original assignee

Released

File Size (Bytes)

Completion Date
27 Jun 2012 14:30:13
GMT
27 Jun 2012 14:14:22
GMT
27 Jun 2012 16:44:36
GMT

Rendered PDF File Page 2 of 8

DOC0585277, Rev:3

GEHC ITPE Standard

Teradata System Maintenance and Operations

TABLE OF CONTENTS
1

PURPOSE ............................................................................................................................................................. 2

SCOPE.................................................................................................................................................................. 2

REFERENCES ........................................................................................................................................................ 2

PROCESS.............................................................................................................................................................. 3
4.1
4.2
4.3
4.4
4.5
4.6
4.7
4.8
4.9

SETUP DBA ACCOUNTS ON TERADATA NODES ............................................................................................................... 3

CREATING INCIDENTS AND WORKING WITH TERADATA SUPPORT ........................................................................................ 3
TERADATA HARDWARE ISSUES AND OUTAGES ............................................................................................................... 3
PACKDISK ............................................................................................................................................................ 3
CHECKTABLE AND SCANDISK ..................................................................................................................................... 3
CLEARING LEFT OVER SPOOL SPACE............................................................................................................................ 4
CPPT LOADING AND REPORTS .................................................................................................................................. 4
PERFORMANCE DATA COLLECTION AND REPORTING (PDCR)............................................................................................ 4
UPDATING SYSTEM AND DATABASE SOFTWARE .............................................................................................................. 5

DEFINITIONS........................................................................................................................................................ 6

RESPONSIBILITIES................................................................................................................................................. 6

OWNERSHIP, AUTHORIZATION, AND REVISION HISTORY ...................................................................................... 6

7.1
7.2
7.3

OWNER: TEAM LEAD, GLOBAL DBA OPERATIONS .......................................................................................................... 6

AUTHORIZATION .................................................................................................................................................... 6
REVISION HISTORY ................................................................................................................................................. 6

Released

Page 1 of 7

* Printed copies are uncontrolled unless otherwise identified *

Before using this document, consult MyWorkshop for the latest revision.

DOC0585277

Rendered PDF File Page 3 of 8

DOC0585277, Rev:3

GEHC ITPE Standard

Teradata System Maintenance and Operations

1 Purpose
This standard describes the process to be followed for GEHC Teradata systems management, upgrades, hardware
maintenance, and outages to meet enterprise goals for system availability and performance.

2 Scope
The Data Management DBA team uses this standard. The activities described in this standard generally require
coordination with Teradata field engineers, BI application support teams, and BI program development teams. System
changes and SRAs are executed in accordance with the GEHC Change Management process.

3 References
Reference ID and Title
[R1]

IT_TSG_STD_Tera_SetupNode_LocalAccount

DOC0757941

[R2]

IT_TSG_WIL3_DOC0637223_Teradata_Production_System_Incident_Mgmt

DOC0637223

[R3]

ITQ_WIL3_DOC0417505_Teradata_Hardware_Maint

DOC0417505

[R4]

IT_TSG_WIL3_DOC0370912_Tera_Packdisk

DOC0370912

[R5]

IT_TSG_WI_DOC0646060_Tera_Scandisk_CheckTables

DOC0646060

[R6]

IT_TSG_STD_DOC0868434_Tera_CPPT

DOC0868434

[R7]

PDCR Installation and Migration Guide

Teradata Performance and Workload Management COE

Version 12a.8
2009-06-17

[R8]

GEHC ITPE Full Cycle Change Control Process

DOC0254716

Page 2 of 7

Released

MyWorkshop
Document ID

* Printed copies are uncontrolled unless otherwise identified *

Before using this document, consult MyWorkshop for the latest revision.

DOC0585277

Rendered PDF File Page 4 of 8

DOC0585277, Rev:3

GEHC ITPE Standard

Teradata System Maintenance and Operations

4 Process
Teradata support and outage activities for TPOCW, TQAPW, and TPRDM systems are:

4.1

Setup DBA accounts on Teradata nodes

Creating incidents and working with Teradata support.
Teradata hardware maintenance and outages
Coordination of an emergency Teradata production outage
Packdisk
Checktable and Scandisk
Clear left over spool space
New User Creation
Drop Unused accounts
Password change
Performance Data Collection and Reporting (PDCR)

Setup DBA accounts on Teradata nodes

A named local account on each Teradata node is provisioned for each DBA and Teradata field engineer.
Additional references see: DOC0757941 [R1]

4.2

Creating Incidents and working with Teradata Support

The Teradata systems are supported by Teradata Global and Field Support. GEHC DBA team interacts with
Teradata Support teams for system maintenance, problems, and unplanned outages.
Additional references see: DOC0637223 [R2]

4.3

Teradata Hardware Issues and Outages

Routine Teradata system hardware component swaps and maintenance are supervised by the GEHC DBA team
and controlled using the GEHC Change Management process.
Additional references see: DOC0417505 [R3]

4.4

PackDisk
Each month the GEHC DBA team performs the PackDisk activity on all Teradata systems to recapture fragmented
space.
Additional references see: DOC0370912 [R4]

4.5

Checktable and Scandisk

Each month the GEHC DBA team performs CheckTable and ScanDisk activities on all Teradata systems to check
for any object or storage inconsistencies.
Additional references see: DOC0646060 [R5]

Released

Page 3 of 7

* Printed copies are uncontrolled unless otherwise identified *

Before using this document, consult MyWorkshop for the latest revision.

DOC0585277

Rendered PDF File Page 5 of 8

DOC0585277, Rev:3

GEHC ITPE Standard

Teradata System Maintenance and Operations
4.6

Clearing Left Over Spool Space

Spool space is the unused Perm Space in database and used to hold intermittent results of the query, it happens
that even though the account is not holding any spool space but database tables show it is, so using
UPDATESPACE utility we clear the spool every week using automated script placed on Teradata Node, please
find the script schedule below.

Script Schedule:

00 06 * * 0 /home/dba/bin/Clear_TPROD_Spool.sh > /dev/null 2> /dev/null

4.7

CPPT Loading and Reports

The GEHC DBA Team generates Teradata Capacity planning reports to understand current system usage and
estimate future capacity plan.
Additional references see: [R6]

4.8

Performance Data Collection and Reporting (PDCR)

The Performance Data Collection and Reporting (PDCR) database is a core database architecture designed to
collect data from various Teradata sources for the purpose of analysis and management of Teradata
Performance and Capacity Planning. The data collected for Performance Data Collection and Reporting is stored
primarily in a database called PDCRDATA. This database contains most of the supplemental tables that store
historical data and provide reference data that assists the reporting and analysis efforts. The PDCR databases
consist of tables, views, and macros. The macros are separated into two groups. The first group is for the
loading and purging of historical data. The second group is for generating reports.

Scripts Schedule:
0,10,20,30,40,50 * * * * /export/home/teraadmin/dba/Clear_Save_pdcr_tbls.sh PDCRCanary0M 2> /dev/null >
/dev/null
0,10,20,30,40,50 * * * * /export/home/teraadmin/dba/Clear_Save_pdcr_tbls.sh PDCRCanary1M 2> /dev/null >
/dev/null
0,10,20,30,40,50 * * * * /export/home/teraadmin/dba/Clear_Save_pdcr_tbls.sh Collect_SessionInfo_Data 2>
/dev/null > /dev/null
03 * * * * /export/home/teraadmin/dba/Clear_Save_pdcr_tbls_hrly.sh Acctg_Space_Test 2> /dev/null >
/dev/null
03 0 * * * /export/home/teraadmin/dba/Clear_Save_pdcr_tbls_Daily.sh Check_PDCRSTG_Data 2> /dev/null >
/dev/null
04 09 * * 0 /export/home/teraadmin/dba/Clear_Save_pdcr_tbls.sh Purge_Perf_Data_SP 2> /dev/null > /dev/null
08 09 * * 0 /export/home/teraadmin/dba/Clear_Save_pdcr_tbls.sh Collect_Stats_DBQL_Acctg_data 2> /dev/null
> /dev/null
20 09 * * 0 /export/home/teraadmin/dba/Clear_Save_pdcr_tbls.sh Collect_Stats_Perf_Data 2> /dev/null >
/dev/null
Additional references see: [R7]

Released

Page 4 of 7

* Printed copies are uncontrolled unless otherwise identified *

Before using this document, consult MyWorkshop for the latest revision.

DOC0585277

Rendered PDF File Page 6 of 8

DOC0585277, Rev:3

GEHC ITPE Standard

Teradata System Maintenance and Operations
4.9

Updating system and database software

Updating system software (i.e. OS or firmware) or program software (i.e. DBS, PDE, network gateway, portal, or
client) is done to stay at vendor supported patch levels to avoid potential problems or to resolve a specific
problem. It is not possible or practical to continually update software every time there is a new version. Instead,
the GEHC Teradata DBA Team Lead, in conjunction with the local Teradata CSR and BI Platform Owner, meet
twice monthly to review open incidents, Tech Alerts, and Field Retrofit Orders logged for GEHC systems on the
Teradata @ Your Service (http://www.teradata.com/t/at-your-service/) web portal. In addition, a Support
Review meeting is held quarterly to review past quarter results with regard to system availability and support or
vitality concerns. Selection and timing of a software update is primarily decided in these meetings.
The exception to this is for an unexpected and critical system problem. In this case, the implementation of a
patch is expedited. If a patch is not available to fix the problem, and there is no workaround, then Teradata
provides a software patch, referred to as an EFix, that is developed and tested to address the specific problem a
GEHC system is facing.
To implement the software update, an FCCC is opened, per the GEHC ITPE Full Cycle Change Control Process
[R8]. In the Develop phase, the patch is implemented and tested in a non-production environment. In some
cases, the non-production environment is declared to reside with Teradata; for example, OS and hardware
firmware updates. In the Pending Deployment phase, the update is implemented on the target production
system. The full description of the update, declaration of the change and outage windows, the implementation
plan details, the test plan and result details, backout/recovery plan, and all approvals are contained in the FCCC.

Released

Page 5 of 7

* Printed copies are uncontrolled unless otherwise identified *

Before using this document, consult MyWorkshop for the latest revision.

DOC0585277

Rendered PDF File Page 7 of 8

DOC0585277, Rev:3

GEHC ITPE Standard

Teradata System Maintenance and Operations

5 Definitions
Term

Definition

[D1]

BI

Business Intelligence

[D2]

CSR

Customer Service Representative

[D3]

DBS

Database System

[D4]

OS

Operating System

[D5]

PDE

Parallel Database Extension

[D6]

TPRDM

Primary Teradata Production environment

[D7]

TQAPW

Teradata QA and Tier 2 Production environment

[D8]

TPOCW

Teradata Development environment

[D9]

PDCR

Performance Data Collection and Reporting

6 Responsibilities
Personnel

Responsibilities

Teradata DBA

Follow the process to complete the task

Teradata DBA Team Leads

Ensure the procedure is followed, ensure anyone following this procedure is

trained accordingly

7 Ownership, Authorization, and Revision History

7.1

Owner: Team Lead, Global DBA Operations

7.2

Authorization
See MyWorkshop for approval signatures.

7.3

Revision History

Revision
Number

Released

Page 6 of 7

Date

Reason for Change / Change Control Number

* Printed copies are uncontrolled unless otherwise identified *

Before using this document, consult MyWorkshop for the latest revision.

Author

DOC0585277

Rendered PDF File Page 8 of 8

DOC0585277, Rev:3

GEHC ITPE Standard

Teradata System Maintenance and Operations

Revision
Number

Date

Reason for Change / Change Control Number

Author

01

25-Oct-2010

Initial version

Kishore Ramisetty

02

10-Mar-2011

FCCC #214423. Added details regarding PDCR.

Sharath Kumar
Dayyala

03

18-Jun-2012

Added section 4.9. Updated sections 3 and 5.

Sue Paulson

To satisfy SOX IT Control # DS13.1.0

Released

Page 7 of 7

* Printed copies are uncontrolled unless otherwise identified *

Before using this document, consult MyWorkshop for the latest revision.

DOC0585277