Lab4 - Managing Database Storage Structures Using Enterprise Manager Database Express

Size: px

Start display at page:

Download "Lab4 - Managing Database Storage Structures Using Enterprise Manager Database Express"

Tobias Allison
6 years ago
Views:

1 Lab4 - Managing Database Storage Structures Using Enterprise Manager Database Express Contents Managing Database Storage Structures Using Enterprise Manager Database Express... 1 Overview... 2 Configuring the HTTP Port for CDB and PDB... 3 Accessing the Database Home Page at CDB level... 6 Managing Database Storage Structures at CDB level... 8 Explore the Tablespace Storage Information Page for PDB Disable EM Express for CDB and PDB Summary Copyright 2013, Oracle and/or its affiliates. All rights reserved. 1

2 Overview Purpose In this tutorial you will learn how to use Enterprise Manager Express to explore the structure of your database. In addition, you will learn how to make a number of changes to your database storage structure. Time to Complete Approximately 1 hour Introduction An Oracle database is made up of physical and logical structures. Physical structures are visible in the operating system. An example of a physical structure is an operating system file that stores data on a disk. Logical structures are defined and known to the Oracle Database server, but are not known to the operating system. An example of a logical structure is a tablespace. In this tutorial you will view logical structures in your database and understand how they relate to physical structures in the operating system. Copyright 2013, Oracle and/or its affiliates. All rights reserved. 2

Configuring the HTTP Port for CDB and PDB Open a terminal window by double clicking the terminal icon in the desktop.. Verify that the listener is started by executing the lsnrctl status command.

3 Configuring the HTTP Port for CDB and PDB Open a terminal window by double clicking the terminal icon in the desktop.. Verify that the listener is started by executing the lsnrctl status command. [oracle@db12c ~] lsnrctl status The EM express can be enabled in the CDB level. Log in to SQL*Plus as the SYSDBA user and verify that the DISPATCHERS parameter in the initialization parameter file includes the PROTOCOL=TCP attribute. [oracle@db12c ~] sqlplus / as sysdba SQL> show parameter dispatchers Copyright 2013, Oracle and/or its affiliates. All rights reserved. 3

4 Execute the DBMS_XDB.setHTTPPort procedure to set the HTTP port for Enterprise Manager Express. SQL> exec dbms_xdb.sethttpport(8080) SQL> exit Pluggable database can have its individual EM express instance. We can configure it almost the same as configure it in the CDB. Log in to PDB1 as sysdba and execute dbms_xdb.sethttpport procedure. Please note that we should use a difference port number other than the port number used by CDB. Also make sure PDB1 is opened before you run the procedure. [oracle@db12c ~] sqlplus sys/oracle@pdb1 as sysdba SQL> exec dbms_xdb.sethttpport(8081) Copyright 2013, Oracle and/or its affiliates. All rights reserved. 4

Accessing the Database Home Page at CDB level The Database Home page is the main database management page in Enterprise Manager Database Express.

(http://localhost:8080/em). Log in to Enterprise Manager Database Express with an authorized CDB user account such as SYS.

6 Accessing the Database Home Page at CDB level The Database Home page is the main database management page in Enterprise Manager Database Express. To access the Database Home page for CDB, double click the icon "EM Express for CDB" in the desktop, it will automatically open the EM login page ( Log in to Enterprise Manager Database Express with an authorized CDB user account such as SYS. Enter the username (sys) and password (oracle in this HOL) in the appropriate fields and select as sysdba checkbox. Click Login. The Database Home page for CDB is displayed. Copyright 2013, Oracle and/or its affiliates. All rights reserved. 6

Managing Database Storage Structures at CDB level In Oracle database 12c multitenant architecture, storage structure are managed by at CDB level and PDB level according to different storage

"control file", "redo log", "archived log" and "undo tablespace" are managed at CDB level, while "permanent tablespace(excluding undo tablespace" and "temp tablespace" are managed at PDB level.

8 Managing Database Storage Structures at CDB level In Oracle database 12c multitenant architecture, storage structure are managed by at CDB level and PDB level according to different storage structures type. "control file", "redo log", "archived log" and "undo tablespace" are managed at CDB level, while "permanent tablespace(excluding undo tablespace" and "temp tablespace" are managed at PDB level. To view storage structure information at CDB level, perform the following steps: Managing Control File Select Control Files in the Storage menu. The Control Files page is displayed. The Control File Information section provides information about the creation and most recent modification to the control file. In the List of Control Files section, the control file names are provided. More than one file name indicates that the control file is multiplexed. The Control File Sections section provides information about the data that is stored in the control file. Copyright 2013, Oracle and/or its affiliates. All rights reserved. 8

Click Backup to Trace to generate and trace file including the

The control file is successfully backed up to a trace file.

9 Click Backup to Trace to generate and trace file including the control file informations. Click Yes to accept the confirmation. The control file is successfully backed up to a trace file. We can view it from the terminal if need. Click OK to accept the confirmation. Managing Online Redo Log Select Redo Log Groups in the Storage menu. Copyright 2013, Oracle and/or its affiliates. All rights reserved. 9

The online redo log files contain entries that are used to recover transactions in the event of an instance failure and may also be used in recovery from media failure.

10 The Redo Log Groups page is displayed. This page lists the redo log groups that have been configured for your database. A value of Current in the Status column indicates the group that is currently being written to. If the redo log groups are multiplexed, more than one member is shown for the group. The online redo log files contain entries that are used to recover transactions in the event of an instance failure and may also be used in recovery from media failure. To ensure that redo entries are not lost in the event of a disk drive failure, redo log files should be multiplexed so that each group has multiple members. To multiplex the redo log file, perform the following steps: Select "Redo Log Group 1", and click "Add Member" Copyright 2013, Oracle and/or its affiliates. All rights reserved. 10

Enter the following directory name in the File Directory

File Directory : /u01/app/oracle/fast_recovery_area/orcl

The Redo Log Groups page shows the new member in Redo Log

11 Enter the following directory name in the File Directory field and a file name in the File Name field. Click OK. File Directory : /u01/app/oracle/fast_recovery_area/orcl File Name: redo01b.dbf Click OK on the Confirmation page. The Redo Log Groups page shows the new member in Redo Log Group 1. Copyright 2013, Oracle and/or its affiliates. All rights reserved. 11

Repeat steps from "Add Member" for redo group 2 and 3. Please note to use the same File Directory and different File Name (redo02b.dbf and redo03b.dbf).

Oracle Database automatically ensures that undo data that is in use by an active transaction is never overwritten until that transaction has been committed.

12 Repeat steps from "Add Member" for redo group 2 and 3. Please note to use the same File Directory and different File Name (redo02b.dbf and redo03b.dbf). Managing Undo Data Oracle Database uses undo data to roll back transactions, to provide read consistency, as part of database recovery, and to enable features such as Oracle Flashback Query. Oracle Database automatically ensures that undo data that is in use by an active transaction is never overwritten until that transaction has been committed. The database server maintains and automatically tunes an undo retention period to ensure the success of Oracle Flashback features and for read consistency for long-running queries. Auto-tuning of the undo retention period is enabled when you create your database. To view undo data information, perform the following steps: Copyright 2013, Oracle and/or its affiliates. All rights reserved. 12

13 Select Undo Management in the Storage menu. The Undo Management Details page is displayed. The "Low Undo Retention Threshold" setting shows the minimum undo retention as configured in the UNDO_RETENTION initialization parameter. A "Retention Guaranteed" setting of Yes indicates that the database server should not overwrite unexpired undo data even if current DML transactions must fail to accommodate this setting. A setting of Yes may be necessary to support Oracle Flashback Query. If you receive "Snapshot Too Old Errors" you may need to increase the value of UNDO_RETENTION or increase the size of the undo tablespace. Copyright 2013, Oracle and/or its affiliates. All rights reserved. 13

Scroll to the right to the view the Undo Advisor graph. The graph shows the minimum size requirement for the undo tablespace given a particular undo retention time.

14 Scroll to the right to the view the Undo Advisor graph. The graph shows the minimum size requirement for the undo tablespace given a particular undo retention time. You can change the undo tablespace to a fixed size if necessary. Changing to a fixed size may be required to support Oracle Flashback operations. Copyright 2013, Oracle and/or its affiliates. All rights reserved. 14

(http://localhost:8081/em). Log in to Enterprise Manager Database Express with an authorized PDB1 user account such as SYS.

16 Explore the Tablespace Storage Information Page for PDB Tablespace storage information are avalible at PDB level. To access the Database Home page for PDB1, click the icon "EM Express for PDB1" on the desktop, it will automatically open the EM login page ( Log in to Enterprise Manager Database Express with an authorized PDB1 user account such as SYS. Enter the username (sys) and password (oracle in this HOL) in the appropriate fields. Click Login. The Database Home page for PDB1 is displayed. Copyright 2013, Oracle and/or its affiliates. All rights reserved. 16

17 Click the Storage tab, and then select Tablespaces. You can check storage statistics for tablespaces such as Temp and Undo. These statistics are important for workload analysis. Copyright 2013, Oracle and/or its affiliates. All rights reserved. 17

18 Click View > Expand All to see all the tablespaces plus all of the datafiles in each tablespace. All tablespaces and their datafiles are now visible. Click View > Flatten. Copyright 2013, Oracle and/or its affiliates. All rights reserved. 18

You should now see only the datafiles and

20 Disable EM Express for CDB and PDB You can disable EM Express by setting the HTTP Port to 0. Disable EX Express for CDB: ~] sqlplus / as sysdba SQL> exec dbms_xdb.sethttpport(0) SQL> exit Disable EX Express for PDB1: [oracle@db12c ~] sqlplus sys/oracle@pdb1 as sysdba SQL> exec dbms_xdb.sethttpport(0) SQL> exit Copyright 2013, Oracle and/or its affiliates. All rights reserved. 20

22 Summary In this HOL, you have learned how to: o o o o Enable and Disable EM Database Express for PDB. Manage Initialization parameter at CDB level. Manage storage structure at CDB level. View storage structure at PDB level. Copyright 2013, Oracle and/or its affiliates. All rights reserved. 22

Oracle Database 12C: Advanced Administration - 1Z0-063

Oracle Database 12C: Advanced Administration - 1Z0-063 Backup and Recovery Explain Oracle backup and recovery solutions o Describe types of database failures o Describe the tools available for backup and