Part 2

Part 2 - Lab Project Checklist:

 Please do not include part 1.

1.  SQL commands to ALTER a table, add a column, lengthen a column, shorten a column, change a data type for a column from NUMBER to CHAR and then CHAR to NUMBER.

2.  Commands to create another table like an existing one but without one column. Then load the data from the old to the new table. Then reestablish referential integrity. Then drop the old table and rename the new one.

 3.  Design for a test of restructuring existing objects for points 1 &2 above.

 4.  Scripts to capture static performance statistics.

5.  Design and Scripts for Performance testing.

6.  Scripts to capture dynamic performance statistics.

7.  A matrix with the results of the performance testing that was done as a DBA.

8.  A script to create a small table with 3 rows for recovery testing.

9.  Backup and recovery commands for Recovery testing using export/import and RMAN utilities.

10.  Design and backup/recovery commands for your test.

11.  Include explanations for what happened during the recovery when import vs. RMAN was used.

12.  Flashback recovery commands.

13.  Scripts that could be used to monitor the health of the database (status, space, invalid objects, and other statistics).

14.  Sample output from statistics queries.

15.  Sample output from invalid objects queries.

16.  Scripts used to create end-users. Including create, access, grant privileges.

17.  Scripts used to create synonyms.

18.  Scripts used to query all_objects views for reverse engineering exercise. Output from reverse engineering queries.

19.  DBA scripts to detect end-users and what they are running on your database.

Part 2 - Lab Project Checklist: Explanations

Please do not include part 1.

1.      SQL commands to ALTER a table, add a column, lengthen a column, shorten a column, change a data type for a column from NUMBER to CHAR and then CHAR to NUMBER.

2.      Commands to create another table like an existing one but without one column. Then load the data from the old to the new table. Then reestablish referential integrity. Then drop the old table and rename the new one.

3.      Design for a test of restructuring existing objects for points 1 &2 above .

       Use checklist 1,2,3 as one set

4.      Scripts to capture static performance statistics.

                    Use of  V$sysstat  See Lab10

5.      Design and Scripts for Performance testing.

Use checklist 4 ,5  as one set.--  See Lab10

 Check v$sysstat àGenerate read load à Check v$sysstat 

Flush shared pool.

 Check v$sysstat àGenerate write load à Check v$sysstat

6.      Scripts to capture dynamic performance statistics.

Use of addm reporting – See Lab11

7.      A matrix with the results of the performance testing that was done as a DBA.

         Just report the results and your findings from Steps 4 thru 6

8.      A script to create a small table with 3 rows for recovery testing.

9.      Backup and recovery commands for Recovery testing using export/import and RMAN utilities.

Use a test table to recover using various backup and recovery scenario commands and ( export/import or expdp/impdp)

For Rman use point in time recovery using scn or time.

10.  Design and backup/recovery commands for your test.

11.  Include explanations for what happened during the recovery when import vs. RMAN was used.

12.  Flashback recovery commands. Show examples scripts, output log

Use checklist 8,9,10,11,12  as one set

13.  Scripts that could be used to monitor the health of the database (status, space, invalid objects, and other statistics).

14.  Sample output from statistics queries.

15.  Sample output from invalid objects queries.

16.  Scripts used to create end-users. Including create, access, grant privileges.

17.  Scripts used to create synonyms.

18.  Scripts used to query all_objects views for reverse engineering exercise. Output from reverse engineering queries.

Required : Use of dbms_metadata to reverse engineer and extract scripts from the Database like table ,index,triggers ,sequence etc. Show how scripts are generated and output

19.  DBA scripts to detect end-users and what they are running on your database.