| < Day Day Up > |
|
This is shown in Table A4.2.
Note | The work plan assumes usage of raw devices if file systems are used. Tasks 2, 3, 4 and 8 need to be replaced appropriately. |
# | Tasks | Who | Status |
---|---|---|---|
1 | Define business requirements, including capacity requirements based on anticipated growth. | ||
2 | Determine the size of raw partitions | ||
3 | Create a raw partition matrix | ||
4 | Create raw partitions | ||
5 | Define logical volumes and volume groups | ||
6 | Create shared file systems for Oracle | ||
7 | Create shared file systems for archive logs | ||
8 | Verify raw partitions | ||
9 | Install Oracle | ||
10 | Verify Oracle install | ||
11 | Determine tablespace requirements, including sizes and the partitions they are to reside on, for the database | ||
12 | Map data files to partitions. Usage of locally managed tablespaces should be preferred; this would avoid all the additional management that would normally be required in the case of dictionary-managed table spaces, including FREELISTS and FREELIST GROUPS | ||
13 | Map tablespaces to data files | ||
14 | Create crdbRAC1.sql script and initRAC1.ora (Samples of these scripts are shown in Appendix 2) | ||
15 | Configure all external cluster-related processes including GSD, SRVCTL, and SRVCONFIG | ||
16 | Create RAC1 instance and PRODDB database | ||
17 | Create crdbRAC2.sql script and initRAC2.ora (Samples of these scripts are shown in Appendix 2) | ||
18 | Full export of the database | ||
19 | Configure Oracle Net Support | ||
20 | Bounce both instances to ensure that all the setup completed to this point is OK | ||
21 | Database verification | ||
22 | Create tablespaces | ||
23 | Assign tables and indexes to mapped partitions | ||
24 | Create database objects; this should be from the current production system (if one exists) or from the development system (if this is a new system). This will give a true picture of the performance characteristics | ||
25 | Set up STATSPACK | ||
26 | Set up OEM | ||
27 | Load data from legacy configuration | ||
28 | QA sanity check | ||
29 | Load testing and tuning RAC1 and monitor using STATSPACK and OEM | ||
30 | Tune parameters | ||
31 | Verify testing results against the requirements | ||
32 | Load testing and tuning RAC1 and RAC2 and monitor using STATSPACK and OEM | ||
33 | Tune parameters | ||
34 | Verify testing results against the requirements | ||
35 | Setup DBMS_STATS package to collect stats | ||
36 | Test load balancing of database cluster | ||
37 | Test failover of database cluster using TAF | ||
38 | Tune failover parameters | ||
39 | Day in a life—test 1: to verify functioning of the cluster in a regular full day production-like simulation. Create backup and recovery strategy based on business requirements, including recovery criteria and procure management approval | ||
40 | Set up RMAN | ||
41 | Start up backup processes | ||
42 | Verify backup strategy | ||
43 | Update startup/shutdown utilities | ||
44 | Day in a life—Test 2: to verify functioning of the cluster in a regular full day production-like simulation with backup scripts running in the background at regular intervals and real user activity | ||
45 | 7-day burn down test—running a 24-hour, 7-day load test will simulate worst case user behavior for a week. This test will also test database and hardware anomalies, if any | ||
46 | Verify testing results against the requirements | ||
47 | Prepare and review report on testing and accomplishments | ||
48 | Prepare and review configuration documentation |
| < Day Day Up > |
|