Oracle Database 12c: New Features for Administrators

Transcription

Unauthorized reproduction or distribution prohibitedฺ Copyright© 2013, Oracle and/or its affiliatesฺ
Global Information Technology
s
) ha
om ฺ
c
ฺ
Oracle Database 12c:
chNew
e
ide
t
i
u
l
Features for Administrators
ba ent G
o
l
g tud
Activity Guide
@
o
nf this S
i
(
ogy use
l
o
hn se to
c
e
T cen
n
o
li
ti
e
a
l
rm erab
o
f
In ansf
l
a
b
tr
Glo nonD77758GC10
Edition 1.0
June 2013
D80606
a
Copyright © 2013, Oracle and/or its affiliates. All rights reserved.
Disclaimer
This document contains proprietary information and is protected by copyright and other intellectual property laws. You may copy and
print this document solely for your own use in an Oracle training course. The document may not be modified or altered in any way.
Except where your use constitutes "fair use" under copyright law, you may not use, share, download, upload, copy, print, display,
perform, reproduce, publish, license, post, transmit, or distribute this document in whole or in part without the express authorization
of Oracle.
The information contained in this document is subject to change without notice. If you find any problems in the document, please
report them in writing to: Oracle University, 500 Oracle Parkway, Redwood Shores, California 94065 USA. This document is not
warranted to be error-free.
Restricted Rights Notice
If this documentation is delivered to the United States Government or anyone using the documentation on behalf of the United
States Government, the following notice is applicable:
U.S. GOVERNMENT RIGHTS
The U.S. Government’s rights to use, modify, reproduce, release, perform, display, or disclose these training materials are restricted
by the terms of the applicable Oracle license agreement and/or the applicable U.S. Government contract.
Trademark Notice
s
) ha
Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective
owners.
om ฺ
c
ฺ
ch ide
Authors
e
t
i
l- t Gu
a
Dominique Jeunot, Jean-François Verrier
b
lo den
g
@ Stu
Technical Contributors and Reviewers
o
f
isPeter Fusek, Dimpi Sarmah,
James Spiller, Donna Keesling, Maria Billings, Lachlan
(in Williams,
h
t
y
gJoel Goodman,
Branislav Valny, Christina Nayagam, Franklo
Fu,
Gerlinde Frenzen, Harald Van
se Malareddy
u
o
Breederode, Herbert Bradbury, Hermann
Baer,
Jim
Stenoish,
Goutam, Patricia
o
tMcguirk,
hn Robert
c
e
Mcelroy, Paul Needham, Puneet e
Sangar,
Sailaja
Pasupuleti,
Sean Kim,
s Vimala Jacob
n
T
Sharath Bhujani, Steven Wertheimer,
Uwe
Hesse,
e
n
o
lic
i
t
e
a
l
b Oracle Tutor
rm erusing:
a
o
This book was
published
f
In ansf
l
a
b
tr
Glo non-
a
Table of Contents
Practices for Lesson 1: Enterprise Manager Cloud Control and Other Tools ............................................1-1
Practices for Lesson 1: Overview ...................................................................................................................1-2
Practice 1-1: Accessing Enterprise Manager .................................................................................................1-3
Practice 1-2: Adding a Database Instance as a New Target Monitored by EM Cloud Control .......................1-6
Practice 1-3: Creating New Named Credentials .............................................................................................1-9
Practice 1-4: Testing the Named Credential ..................................................................................................1-11
Practices for Lesson 2: Basics of Multitenant Container Database and Pluggable Databases ................2-1
Practices for Lesson 2: Overview ...................................................................................................................2-2
Practice 2-1: Exploring CDB Architecture and Structures ..............................................................................2-3
Practices for Lesson 3: Creating a Multitenant Container Database and Pluggable Databases ..............3-1
Practices for Lesson 3....................................................................................................................................3-2
Practice 3-1: Creating a New CDB .................................................................................................................3-3
Practice 3-2: Exploring CDB and PDB Structures ..........................................................................................3-7
Practice 3-3: Creating a PDB from Seed ........................................................................................................3-19
Practice 3-4: Cloning PDB Within the Same CDB ..........................................................................................3-27
Practice 3-5: Plugging a Non-CDB into a CDB ..............................................................................................3-38
Practice 3-6: Merging All PDBs of CDBs into a Single CDB ..........................................................................3-45
Practice 3-7: Dropping a PDB (optional) ........................................................................................................3-50
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
u
Practices for Lesson 4: Managing a Multitenant Container Database and Pluggable
............4-1
l-Databases
G
a
t
b
lo den
g
Practice 4-1: Shutdown and Startup of the CDB ............................................................................................4-3
@ Stu
o
f
Practice 4-2: Closing and Opening a PDB .....................................................................................................4-8
n this
(i......................................................................4-14
Practice 4-3: Creating After Startup Trigger to Open All PDBs
y
og use
l
Practice 4-4: Changing PDBs' Open Mode ....................................................................................................4-16
o
n onePDBs
to (optional) ........................................................4-18
Practice 4-5: Instance Parameter Changes:
hImpact
c
e
s
T cenand Users in a CDB and PDBs........................................5-1
Practices for Lesson 5: Managing Tablespaces
n
o
li
ti
e
a
l
b .............................................................................................................5-3
Practice 5-1: Managing
rm Tablespaces
a
r
o
f
e
Practice 5-2:
Common
InManaging
sf and Local Users ........................................................................................5-11
l
n
a
a
Practice
5-3:
Managing
Local
and Common Roles ........................................................................................5-19
b n-tr
o
l
G Practicen5-4:
o Managing Local and Common Privileges ..................................................................................5-27
Practices for Lesson 6: Backup, Recovery, Flashback CDB and PDBs ......................................................6-1
Practice 6-1: Cold CDB Backup .....................................................................................................................6-3
Practice 6-2: RMAN Whole CDB Backup .......................................................................................................6-5
Practice 6-3: RMAN CDB / PDB Backup ........................................................................................................6-8
Practice 6-4: RMAN Recovery from SYSTEM PDB Data File Loss ...............................................................6-10
Practice 6-5: RMAN Recovery from Non-Essential PDB Data File Loss ........................................................6-14
Practice 6-6: SQL PDB Hot Backup (optional) ...............................................................................................6-18
Practice 6-7: SQL Control File Backup (optional) ...........................................................................................6-20
Practice 6-8: RMAN Recovery from Control File Loss (optional) ...................................................................6-21
Practice 6-9: RMAN Recovery from Redo Log File Member Loss (optional) .................................................6-26
Practice 6-10: RMAN Recovery from SYSTEM Root Data File Loss (optional) .............................................6-29
Practice 6-11: RMAN Recovery from Non-Essential Root Data File Loss (optional) ......................................6-33
Practice 6-12: PITR on PDB Tablespaces (optional) .....................................................................................6-35
Practice 6-13: Flashback from Common User Drop (optional) .......................................................................6-42
Oracle Database 12c: New Features for Administrators Table of Contents
i
a
Practices for Lesson 7: Heat Map, Automatic Data Optimization and Online Datafile Move.....................7-1
Practice 7-1: Enabling Heat Map....................................................................................................................7-3
Practice 7-2: Automatic Data Optimization – Creating a TIER Policy.............................................................7-5
Practice 7-3: Automatic Data Optimization – Creating a COMPRESS Policy ................................................7-14
Practice 7-4: Cleanup ADO Policies and Heat Map Statistics ........................................................................7-26
Practice 7-5: Moving Data File Online ............................................................................................................7-28
Practices for Lesson 8: In-Database Archiving and Temporal Validity .......................................................8-1
Practice 8-1: In-Database Archiving – Row-archival ......................................................................................8-3
Practice 8-2: Temporal Validity ......................................................................................................................8-8
Practice 8-3: Collecting User Context in FDA History Tables (optional) .........................................................8-18
Practice 8-4: Cleaning Up FDA ......................................................................................................................8-24
Practices for Lesson 9: Auditing ....................................................................................................................9-1
Practice 9-1: Enabling Unified Auditing ..........................................................................................................9-3
Practice 9-2: Auditing Data Pump Export .......................................................................................................9-9
Practice 9-3: Auditing RMAN Backups ...........................................................................................................9-13
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
b
lo den
g
@ Stu
o
f
(in this
y
og use
l
o
to
Practices for Lesson 11: Oracle Data Redaction
hn ...........................................................................................11-1
c
e
e
s
Practices for Lesson 11..................................................................................................................................11-2
T cen
n
o
Practice 11-1: Redacting Protected
li Values with FULL Redaction ....................................................11-3
i Column
t
e
a
l
Practice 11-2: Redacting
bColumn Values with PARTIAL Redaction (optional) ..............................11-7
rm UpProtected
a
r
o
f
e
Practice 11-3:
Cleaning
Redaction
Policies ..............................................................................................11-10
n nsf
I
l
Practices
ra12: Recovery Manager New Features and Temporal History Enhancements........12-1
bafor Lesson
t
o
l
n
G Practicesnofor Lesson 12..................................................................................................................................12-2
Practice 12-1: Using SYSBACKUP in RMAN .................................................................................................12-3
Practices for Lesson 10: Privileges ................................................................................................................10-1
Practice 10-1: Manage Password File with SYSBACKUP Entry ....................................................................10-3
Practice 10-2: Capturing Privileges ................................................................................................................10-8
Practice 10-3: Capture Privileges Used Through Roles (Optional) ................................................................10-17
Practice 10-4: Capture Privileges Used In Contexts (Optional) ......................................................................10-21
Practice 10-5: Use INHERIT PRIVILEGES Privilege .....................................................................................10-24
Practice 10-6: INHERIT PRIVILEGES Privilege and BEQUEATH Views .......................................................10-27
Practice 12-2: Recovering a Table by Using Table Recovery ........................................................................12-9
Practices for Lesson 13: Real-Time Database Operation Monitoring .........................................................13-1
Practices for Lesson 13: Overview .................................................................................................................13-2
Practice 13-1: Starting Enterprise Manager Database Express .....................................................................13-3
Practice 13-2: Identifying and Starting Database Operations .........................................................................13-7
Practice 13-3: Identifying and Starting Database Load Operations (Optional) ...............................................13-14
Practice 13-4: Cleaning Up ............................................................................................................................13-16
Practices for Lesson 14: Schema and Data Changes Management ............................................................14-1
Practice 14-1: Using Schema Change Plans .................................................................................................14-3
Practices for Lesson 15: SQL Tuning Enhancements ..................................................................................15-1
Practice 15-1: Using Dynamic Plans ..............................................................................................................15-3
ii
a
Practice 15-2: Using Re-optimization .............................................................................................................15-8
Practices for Lesson 16: Emergency Monitoring and Compare Period ADDM ..........................................16-1
Practice 16-1: Using Emergency Monitoring ..................................................................................................16-3
Practice 16-2: Cleaning Up ............................................................................................................................16-8
Practice 16-3: Using Compare Period ADDM (optional) ................................................................................16-9
Practices for Lesson 17: Resource Manager and Other Performance Enhancements..............................17-1
Practice 17-1: Using CDB Resource Manager Plans and Directives .............................................................17-3
Practice 17-2: Using Multi-Process Multi-Threaded Architecture ...................................................................17-14
Practices for Lesson 18: Tables, Indexes and Online Operations ...............................................................18-1
Practice 18-1: Using Invisible Table Columns ................................................................................................18-3
Practice 18-2: Advanced Row Compression ..................................................................................................18-7
Practices for Lesson 19: ADR and Network Enhancements ........................................................................19-1
Practice 19-1: Viewing ADR DDL Log File .....................................................................................................19-3
s
) ha
om ฺ
c
ฺ
ch ide
Practice 20-1: Creating a New non-CDB orcl3 ...........................................................................20-3
e
t
i
l- t Gu
Practice 20-2: Exporting/Importing Databases in FULL TRANSPORTABLE Mode .......................................20-5
a
b
Practice 20-3: Loading Data Using SQL*Loader Express Mode (Optional) ...................................................20-30
lo den
g
@ Stu
Practices for Lesson 21: Partitioning Enhancements ..................................................................................21-1
o
f
(in this
y
g uTables
Practice 21-1: Local and Global Partial Indexing ono
Partitioned
se .........................................................21-3
l
o
Practices for Lesson 22: SQL Enhancements
to Assistant for Unicode.................................22-1
hnand sMigration
c
e
e
n..........................................................................................22-3
T DatacType
e
n
Practice 22-1: Using 32K VARCHAR2
i
o
l
ti
lea SQL Row-Limiting Clause ...............................................................22-11
Practice 22-2: Quering aaTable Using
b
m
r
a
fo sfer
n
I
al -tran
b
o
Gl non
Practices for Lesson 20: Oracle Data Pump, SQL*Loader, and External Tables........................................20-1
iii
a
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
b
lo den
g
@ Stu
o
f
(in this
y
og use
l
o
hn se to
c
e
T cen
n
o
li
ti
e
a
l
rm erab
o
f
In ansf
l
a
b
tr
Glo non-
a
s
) ha
om ฺ
c
ฺ
Practices for Lesson
ch1: ide
e
t
i
u
l- Cloud
Enterprise Manager
G
a
t
b
n
eTools
gloOther
Control@
and
d
u
o is St
f
n
i
Chapter
( 1 th
y
g
se
o
l
u
o
hn se to
c
e
T cen
n
o
li
ti
e
a
l
rm erab
o
f
In ansf
l
a
b
tr
Glo non-
Practices for Lesson 1: Enterprise Manager Cloud Control and Other Tools
Chapter 1 - Page 1
a
Practices for Lesson 1: Overview
Practices Overview
Your system currently has Oracle Database 12c software installed, as well as three pre-created
database called orcl, orcl2 and cdb1.
You act as an Enterprise Manager administrator. You access Oracle Enterprise Manager Cloud
Control 12c as the sysman user with the Oracle123 password and select Summary as your
home page. You start exploring some of the Oracle Enterprise Manager Cloud Control 12c
functionalities through the different menus and options. And lastly, you will add the orcl
database as a monitored target.
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
b
lo den
g
@ Stu
o
f
(in this
y
og use
l
o
hn se to
c
e
T cen
n
o
li
ti
e
a
l
rm erab
o
f
In ansf
l
a
b
tr
Glo non-
Chapter 1 - Page 2
a
Practice 1-1: Accessing Enterprise Manager
Overview
In this practice, you access Oracle Enterprise Manager Cloud Control 12c as the sysman user
with the Oracle123 password and select Summary as your home page.
Assumptions
You reviewed the Oracle Enterprise Manager 12c: Console Overview and Customization
demonstration or have the equivalent navigation knowledge.
Tasks
1.
2.
Click the Firefox icon on the top panel (toolbar region) above the desktop to open a browser
to access the Enterprise Manager Cloud Control console.
Enter the URL for Cloud Control:
https://<em_server_hostname>.<domain>:7802/em. In the current setup, use
https://localhost:7802/em. If an error appears, you must first start the OMS, else proceed
directly with step 3.
a. Start the Enterprise Manager Repository Database em12rep if not started already.
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
b
lo den
g
@ Stu
o
f
(in this
y
og use
l
o
n e to
hinstance.
Connected to an idle
c
e
s
n
SQL> startup n T
e
lic
tio started.
ORACLE instance
e
a
l
rm erab
o
f
In System
sf Global Area 400846848 bytes
l
n
Total
a
a
b n-trSize
2271568 bytes
Glo nFixed
o
Variable Size
339740336 bytes
$ . oraenv
ORACLE_SID = [orcl] ? em12rep
The Oracle base for
ORACLE_HOME=/u01/app/oracle/product/12.1.0/dbhome_1 is
/u01/app/oracle
$ sqlplus / as sysdba
Database Buffers
Redo Buffers
Database mounted.
Database opened.
SQL> EXIT
$
b.
50331648 bytes
8503296 bytes
Restart the OMS.
$ export OMS_HOME=/u01/app/oracle/product/middleware/oms
$ $OMS_HOME/bin/emctl start oms
Oracle Enterprise Manager Cloud Control 12c Release 2
Chapter 1 - Page 3
a
Copyright (c) 1996, 2012 Oracle Corporation. All rights
reserved.
Starting Oracle Management Server...
Starting WebTier...
WebTier Successfully Started
Oracle Management Server Successfully Started
Oracle Management Server is Up
WARNING: Limit of open file descriptors is found to be 1024.
The OMS has been started but it may run out of descriptors under
heavy usage.
For proper functioning of OMS, please set "ulimit -n" to be at
least 4096.
$
3.
Most likely, you receive a Secure Connection Failed message and you need to add a
security exception. Click Or you can add an exception.
a. At the end of the alert box, click I Understand the Risks.
b. At the bottom of the page, click Add Exception.
c. In the Add Security Exception pop-up window, click Get Certificate.
d. Confirm that “Permanently store this exception” is selected in your training environment
and click Confirm Security Exception.
The Enterprise Manager Cloud Control console appears.
Enter sysman in the User Name field and Oracle123 in the Password field. Then click
Login.
The first time a new user logs in to Enterprise Manager, a page asks you to accept the
license agreement. You have to accept only once. Then each time you will log in to
Enterprise Manager, you will not get the license agreement page.
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
b
lo den
4.
g
@ Stu
o
5.
f
(in this
y
og use
l
6.
o
hn se to
c
e
T cen
n
o
li
ti
e
a
l
rm erab
o
f
In ansf
l
a
b
tr
Glo non-
Chapter 1 - Page 4
a
7. The “Select Enterprise Manager Home Page” page appears with choices, such as:
− Summary
− Databases
− Incidents
− SOA
− Middleware
− Composite Application
− Service Request
− Services
− Business Applications
− Compliance Dashboard
Each choice has a Preview and a Select As My Home button.
The page also has global menus with the following choices: Enterprise, Targets, Favorites,
History, and Search Target Name (next to the search entry field). Each of the menu items has
drop-down menus with further choices.
Preview any images that interest you.
8. Click the “Select As My Home” next to the Summary choice. After being successfully set, it
informs you how to change it.
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
b
lo den
g
@ Stu
o
f
(in this
y
9. Question: How can you change your home
selection
og useafter the initial setup?
l
o
Answer: SYSMAN > Select My Home…
n menu.
to
h
c
e
e
s
T cen
n
o
li
ti
e
a
l
rm erab
o
f
In ansf
l
a
b
tr
Glo non-
Chapter 1 - Page 5
a
Practice 1-2: Adding a Database Instance as a New Target Monitored
by EM Cloud Control
Overview
Assumptions
As a prerequisite task, you must log in to Enterprise Manager Cloud Control as the SYSMAN
user with Oracle123 as the password.
Tasks
First add the database instance orcl as a new target monitored by Oracle Enterprise Manager
Cloud Control.
1. Add the orcl Database Instance as a new target in Enterprise Manager Cloud Control.
a. In the Summary section, click the “Setup” > “Add Target” > “Add Targets Manually”.
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
b
lo den
g
@ Stu
o
f
(in this
y
og use
l
o
hn se to
c
e
T cen
n
o
li
ti
e
a
l
rm erab
o
f
In ansf
l
a
b
tr
Glo non-
Chapter 1 - Page 6
a
b.
In “Add Targets Manually”, choose “Add Non-Host Targets Using Guided Process
(Also Adds Related Targets)”. Then in “Target Types”, choose “Oracle Database,
Listener and Automatic Storage Management” for “Target Type”. Click “Add Using
Guided Discovery …” button.
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
b
lo den
g
@ Stu
o
f
(in this
y
og use
l
o
hn se to
c
e
nSpecify Host”, click the magnifying glass to find your
T target:
e
c. In “Add Database
Instance
n
c
i
o
l
ti host, then
host. Select a
your
le click “Continue”.
b
m
r
a
fo sfer
n
I
al -tran
b
o
Gl non
Chapter 1 - Page 7
a
d.
In the “Databases” list, deselect all databases except orcl. Deselect the listener.
1)
Unlock the DBSNMP user. This user is the monitoring user used to test the
connection once the target is being added. Open a terminal window.
$ . oraenv
ORACLE_SID = [oracle] ? orcl
The Oracle base for
/u01/app/oracle
Connected to:
Oracle Database 12c Enterprise Edition Release 12.1.0.0.2 64bit Production
With the Partitioning, OLAP, Advanced Analytics and Real
Application Testing options
has
SQL> alter user dbsnmp identified by oracle_4U account unlock;
)
om ฺ
c
ฺ
ch ide
User altered.
e
t
i
l- t Gu
a
b
lo den
SQL> EXIT
g
@ Stu
$
o
f
(in this
2) Enter oracle_4U for the “Monitor
Password”.
y
og use
l
o
hn se to
c
e
T cen
n
o
li
ti
e
a
l
rm erab
o
f
In ansf
l
a
b
tr
Glo none.
Click the “Test Connection” button. You should receive the following message:
f.
Click the “Finish” then “Save” buttons to complete the operation, and finally “OK”.
Chapter 1 - Page 8
a
Practice 1-3: Creating New Named Credentials
Overview
In this practice, you create the credorcl credential used for any connection as SYS user
sharable in the database instance orcl.
Assumptions
You completed the practice 1-2 to add the orcl database instance as a new target monitored
by Enterprise Manager Cloud Control.
Tasks
1.
2.
Navigate to Setup > Security > Named Credentials.
Click Create.
a. Enter the following values, then complete the Access Control section:
Field
Choice or Value
General Properties
s
) ha
om ฺ
c
ฺ
Credentials for Database ch
Credential description
te Guide
i
l
Database Instance a
Authenticating Target Type
b ent
o
l
g tud
Database Credentials
Credential type
@
o
nf this S
Target
i
Scope
(
gy usInstance
e
oDatabase
Target type
l
o
to(Click the magnifying glass
hn sorcl
Target Name
c
e
e
T cen to find orcl and select)
n
o
li
ti
e
a
l
rm erab
o
f
Credential
Properties
In ansf
l
a
b n-tr
SYS
Username
GloPassword
o
n
oracle_4U
Credential Name
credorcl
Confirm Password
oracle_4U
Role
SYSDBA
b.
•
•
Specify who can share, edit or even delete this shared credential using one of the three
privileges (Full, Edit, View).
SYS user with Full privilege will be able to use, edit and delete the credential.
SYSTEM user with Edit privilege will be able to use and edit the credential.
1) Click “Add Grant” then select the user SYS to be added in the Access Control list.
2) Repeat this operation to add the user SYSTEM.
By default, the selected users are granted the View privilege only.
3) To grant Full privilege to SYS, select the SYS user and click “Change Privilege”.
Choose Full and click OK.
Chapter 1 - Page 9
a
4)
3.
To grant Edit privilege to SYSTEM, select the SYSTEM user and click “Change
Privilege”. Choose Edit and click OK.
Test against the orcl database instance, click Test and Save until you get the following
message: Confirmation Credential Operation Successful. This means that the credential
was successful and saved.
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
b
lo den
g
@ Stu
o
f
(in this
y
og use
l
o
hn se to
c
e
T cen
n
o
li
ti
e
a
l
rm erab
o
f
In ansf
l
a
b
tr
Glo non-
Chapter 1 - Page 10
a
Practice 1-4: Testing the Named Credential
Overview
In this practice, you test the credorcl named credential to connect to orcl database.
Tasks
1.
2.
3.
4.
5.
Test if the named credential works when you connect to the orcl target.
Click Targets and then select Databases.
Choose orcl.
Click Administration, then Storage and then Tablespaces. The named credential
credorcl is displayed.
Click Login if you accept this named credential to log in the orcl database else choose
New to define new login username and password.
As soon as you click the Logout button, the following screenshot is displayed.
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
b
lo den
g
@ Stu
o
f
(in this
y
og use
l
o
hn se to
c
e
n and all targets” and click the Logout button.
T Manager
Choose “Logout of Enterprise
e
n
c
i
o
l
ti
a
le
b
m
r
a
fo sfer
n
I
al -tran
b
o
Gl non
Chapter 1 - Page 11
a
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
b
lo den
g
@ Stu
o
f
(in this
y
og use
l
o
hn se to
c
e
T cen
n
o
li
ti
e
a
l
rm erab
o
f
In ansf
l
a
b
tr
Glo non-
Chapter 1 - Page 12
a
s
) ha
om ฺ
c
ฺ
ch2: ide
e
t
i
l- t Gu
Basics of Multitenant
a
b
lo denand
g
Container
Database
@ Stu
o
f
Pluggable
n thiDatabases
s
i
(
y
ogChapterus2 e
l
o
hn se to
c
e
T cen
n
o
li
ti
e
a
l
rm erab
o
f
In ansf
l
a
b
tr
Glo non-
Practices for Lesson 2: Basics of Multitenant Container Database and Pluggable Databases
Chapter 2 - Page 1
a
Practices Overview
In previous Oracle Database versions, you used to create, configure, and manage non-CDBs.
In Oracle Database 12c, you need to know how to create, configure, and manage multitenant
container databases (CDBs) and pluggable databases (PDBs).
In this practice, you will explore new types of databases and get familiar with the architecture
and structures of multitenant container databases (CDBs) and pluggable databases (PDBs).
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
b
lo den
g
@ Stu
o
f
(in this
y
og use
l
o
hn se to
c
e
T cen
n
o
li
ti
e
a
l
rm erab
o
f
In ansf
l
a
b
tr
Glo non-
Chapter 2 - Page 2
a
Practice 2-1: Exploring CDB Architecture and Structures
Overview
In this practice, you will explore the architecture and structures of cdb1 and its pluggable
databases.
Tasks
1.
Explore the cdb1 instance, the background processes and the multitenant container
database.
a. Use the ps –ef|grep Unix command.
$ ps -ef|grep cdb1
oracle
378
375 0 18:05 ?
00:00:00 oraclecdb1
(DESCRIPTION=(LOCAL=YES)(ADDRESS=(PROTOCOL=beq)))
oracle
390
1 0 18:05 ?
00:00:00 ora_w001_cdb1
oracle
2711 2686 0 18:32 pts/2
00:00:00 grep cdb1
oracle
27530
1 0 13:24 ?
00:00:02 ora_pmon_cdb1
oracle
27534
1 0 13:24 ?
00:00:04 ora_psp0_cdb1
oracle
27538
1 1 13:24 ?
00:05:01 ora_vktm_cdb1
oracle
27544
1 0 13:24 ?
00:00:00 ora_gen0_cdb1
oracle
27548
1 0 13:24 ?
00:00:00 ora_mman_cdb1
oracle
27556
1 0 13:24 ?
00:00:00 ora_diag_cdb1
oracle
27560
1 0 13:24 ?
00:00:00 ora_ofsd_cdb1
oracle
27564
1 0 13:24 ?
00:00:00 ora_dbrm_cdb1
oracle
27568
1 0 13:24 ?
00:00:11 ora_dia0_cdb1
oracle
27572
1 0 13:24 ?
00:00:02 ora_dbw0_cdb1
oracle
27576
1 0 13:24 ?
00:00:01 ora_lgwr_cdb1
oracle
27580
1 0 13:24 ?
00:00:03 ora_ckpt_cdb1
oracle
27584
1 0 13:24 ?
00:00:00 ora_smon_cdb1
oracle
27588
1 0 13:24 ?
00:00:00 ora_reco_cdb1
oracle
27592
1 0 13:24 ?
00:00:00 ora_lreg_cdb1
oracle
27596
1 0 13:24 ?
00:00:15 ora_mmon_cdb1
oracle
27600
1 0 13:24 ?
00:00:06 ora_mmnl_cdb1
oracle
27604
1 0 13:24 ?
00:00:00 ora_d000_cdb1
oracle
27608
1 0 13:24 ?
00:00:00 ora_s000_cdb1
oracle
27630
1 0 13:25 ?
00:00:00 ora_tmon_cdb1
oracle
27634
1 0 13:25 ?
00:00:00 ora_tt00_cdb1
oracle
27638
1 0 13:25 ?
00:00:00 ora_fbda_cdb1
oracle
27642
1 0 13:25 ?
00:00:00 ora_aqpc_cdb1
oracle
27651
1 0 13:25 ?
00:00:00 ora_p000_cdb1
oracle
27659
1 0 13:25 ?
00:00:00 ora_p001_cdb1
oracle
27666
1 0 13:25 ?
00:00:00 ora_p002_cdb1
oracle
27670
1 0 13:25 ?
00:00:00 ora_p003_cdb1
oracle
27682
1 0 13:25 ?
00:00:09 ora_cjq0_cdb1
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
b
lo den
g
@ Stu
o
f
(in this
y
og use
l
o
hn se to
c
e
T cen
n
o
li
ti
e
a
l
rm erab
o
f
In ansf
l
a
b
tr
Glo non-
Chapter 2 - Page 3
a
oracle
oracle
oracle
oracle
oracle
$
b.
27734
27738
27742
27750
31695
1
1
1
1
1
0
0
0
0
0
13:25
13:25
13:25
13:25
17:05
?
?
?
?
?
00:00:00
00:00:00
00:00:00
00:00:00
00:00:00
ora_qm01_cdb1
ora_q001_cdb1
ora_q002_cdb1
ora_smco_cdb1
ora_w002_cdb1
Connect to the multitenant container database cdb1.
$ . oraenv
ORACLE_SID = [orcl] ? cdb1
The Oracle base remains unchanged with value /u01/app/oracle
Connected to:
With the Partitioning, OLAP, Data Mining, Real Application
Testing
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
b
SQL>
lo den
g
@ Stu
c. Check if the database is a multitenant container
database.
o
f
is
(in v$database;
h
SQL> select name, cdb, con_idyfrom
t
og use
l
o
hn se to
NAME
CDB
CON_ID
c
e
T cen
--------- --- n
---------o
li 0
ti
CDB1
YES
e
a
l
rm erab
o
f
In
sf
l
SQL> an
a
b n-tr
Glod. nCheck
o the instance name.
SQL> select INSTANCE_NAME, STATUS, CON_ID from v$instance;
INSTANCE_NAME
STATUS
CON_ID
---------------- ------------ ---------cdb1
OPEN
0
SQL> EXIT
$
2.
Explore the services.
a. Start the listener if not yet started.
$ lsnrctl status
Chapter 2 - Page 4
a
LSNRCTL for Linux: Version 12.1.0.0.2 - Production on 09-JUL2012 02:57:38
Copyright (c) 1991, 2012, Oracle.
All rights reserved.
Connecting to
(DESCRIPTION=(ADDRESS=(PROTOCOL=IPC)(KEY=EXTPROC1521)))
STATUS of the LISTENER
-----------------------Alias
LISTENER
Version
TNSLSNR for Linux: Version 12.1.0.0.2
- Production
Start Date
10-JUL-2012 00:15:19
Uptime
0 days 2 hr. 42 min. 19 sec
Trace Level
off
Security
ON: Local OS Authentication
SNMP
OFF
Listener Parameter File
/u01/app/oracle/product/12.1.0/dbhome_1/network/admin/listener.o
ra
Listener Log File
/u01/app/oracle/diag/tnslsnr/yourserver/listener/alert/log.xml
Listening Endpoints Summary...
(DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(KEY=EXTPROC1521)))
(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=yourserver)(PORT=1521)
))
(DESCRIPTION=(ADDRESS=(PROTOCOL=tcps)(HOST=yourserver)(PORT=5500
))(Security=(my_wallet_directory=/u01/app/oracle/admin/orcl/xdb_
wallet)) (Presentation=HTTP)(Session=RAW))
(DESCRIPTION=(ADDRESS=(PROTOCOL=tcps)(HOST=yourserver)(PORT=5502
))(Security=(my_wallet_directory=/u01/app/oracle/admin/cdb1/xdb_
wallet)) (Presentation=HTTP)(Session=RAW))
Services Summary...
Service "cdb1" has 1 instance(s).
Instance "cdb1", status READY, has 1 handler(s) for this
service...
Service "cdb1XDB" has 1 instance(s).
service...
Service "em12rep" has 1 instance(s).
Instance "em12rep", status READY, has 1 handler(s) for this
service...
Service "em12repXDB" has 1 instance(s).
service...
Service "orcl" has 1 instance(s).
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
b
lo den
g
@ Stu
o
f
(in this
y
og use
l
o
hn se to
c
e
T cen
n
o
li
ti
e
a
l
rm erab
o
f
In ansf
l
a
b
tr
Glo non-
Chapter 2 - Page 5
a
Instance "orcl", status READY, has 1 handler(s) for this
service...
Service "orcl2" has 1 instance(s).
Instance "orcl2", status READY, has 1 handler(s) for this
service...
Service "orcl2XDB" has 1 instance(s).
service...
Service "orclXDB" has 1 instance(s).
service...
Service "pdb1_1" has 1 instance(s).
service...
The command completed successfully
$
has
The listener is already started. If it were not started, you would use the following command
)
to start the listener:
om ฺ
c
ฺ
$ lsnrctl start
ch ide
e
t
i
l- t Gu
a
b
lo denon 09-JULLSNRCTL for Linux: Version 12.1.0.0.2 -gProduction
@ Stu
2012 03:08:50
o
f
(in this
y
g usAll
e rights reserved.
Copyright (c) 1991, 2012,lo
Oracle.
o
hn se to
c
e
Starting /u01/app/oracle/product/12.1.0/dbhome_1/bin/tnslsnr:
T cen
n
o
please wait...
li
ti
e
a
l
rm erab
o
f
TNSLSNR
In anfor
sf Linux: Version 12.1.0.0.2 - Production
l
a
b System
tr parameter file is
Glo n/u01/app/oracle/product/12.1.0/dbhome_1/network/admin/listener.o
onra
Log messages written to
Listening on:
Listening on:
))
Connecting to
-----------------------Alias
LISTENER
Chapter 2 - Page 6
a
Version
- Production
Start Date
09-OCT-2012 03:08:50
Uptime
Trace Level
off
Security
SNMP
OFF
ra
Listener Log File
s
) ha
))
The listener supports no services
$
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
b
b. Check services.
lo den
g
@ Stu
$ lsnrctl services
o
f
(in this
y
g use - Production on 06-SEPo12.1.0.0.2
LSNRCTL for Linux: Version
l
o
2012 23:29:20
hn se to
c
e
T cen
n
i
o
l2012,
Copyright (c)
Oracle. All rights reserved.
ti 1991,
e
a
l
b
m
r
ra
o
f
e
f
n
Connecting
to
I ans
l(DESCRIPTION=(ADDRESS=(PROTOCOL=IPC)(KEY=EXTPROC1521)))
a
b
tr
Glo nServices
on- Summary...
service...
Handler(s):
"DEDICATED" established:2 refused:0 state:ready
LOCAL SERVER
service...
Handler(s):
"D000" established:0 refused:0 current:0 max:1022
state:ready
DISPATCHER <machine: yourserver, pid: 27840>
Chapter 2 - Page 7
a
(ADDRESS=(PROTOCOL=tcp)(HOST=yourserver)(PORT=29863))
service...
Handler(s):
LOCAL SERVER
service...
Handler(s):
state:ready
service...
Handler(s):
LOCAL SERVER
Service "orcl2" has 1 instance(s).
service...
Handler(s):
LOCAL SERVER
Service "orcl2XDB" has 1 instance(s).
service...
Handler(s):
state:ready
service...
Handler(s):
state:ready
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
b
lo den
g
@ Stu
o
f
(in this
y
og use
l
o
hn se to
c
e
T cen
n
o
li
ti
e
a
l
rm erab
o
f
In ansf
l
a
b
tr
Glo non-
Chapter 2 - Page 8
a
service...
Handler(s):
LOCAL SERVER
$
c.
List the services automatically created for each container.
Connected to:
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
NAME
CON_ID
a
b
lo den
-------------------- ---------g
@ Stu
o
pdb1_1
3
f
in this
cdb1XDB
1(
y
og 1 use
l
cdb1
o
hn se to1
SYS$BACKGROUND
c
e
T cen 1
SYS$USERS
n
o
li
ti
e
a
l
b
SQL> orm
a
r
f
e
n the nPDB$SEED
Ithat
sf
Notice
service is not listed. No one should connect to this service
l
a
a
r
b
t
because
there
should
be
no
operations performed on this container. It is reserved as a
o
Gl template
nonto create other PDBs.
SQL> col name format A20
SQL> select name, con_id from v$services;
3.
Display the pluggable databases.
a. Use the new view V$PDBS.
SQL> select CON_ID, NAME, OPEN_MODE from v$pdbs;
CON_ID
---------2
3
NAME
-----------------------------PDB$SEED
PDB1_1
OPEN_MODE
---------READ ONLY
READ WRITE
SQL>
Notice that the seed PDB is in READ ONLY open mode.
Chapter 2 - Page 9
a
b.
Use the new command SHOW CON_NAME and CON_ID to know which container you
are connected to.
SQL> show con_name
CON_NAME
-----------------------------CDB$ROOT
SQL> show con_id
CON_ID
-----------------------------1
SQL>
has
You can also use SYS_CONTEXT function to view the CON_NAME and CON_ID attributes
)
of your session context.
om ฺ
c
ฺ
ch ide
SELECT sys_context('userenv','CON_NAME') from dual;
e
t
i
l- t Gu
SELECT sys_context('userenv','CON_ID') from dual;
a
b
lo den
g
4. View some of the new family of views CDB_xxx:
@ Stu
o
f
SQL> col PDB_NAME format a8
(in this
SQL> col CON_ID format 99 gy
seGUID, CON_ID
o DBID,
l
u
o
SQL> select PDB_ID, PDB_NAME,
hn se to
c
2 from cdb_pdbs;
e
T cen
n
o
li DBID GUID
ti
e
a
PDB_ID PDB_NAME
l
rm erab
CON_ID
o
f
In a-------sf ---------- -------------------------------- l
-----n
a
b -----tr
Glo non- 3 PDB1_1 3624951709 C39AE2177B2E530EE043160200C043C3
1
2 PDB$SEED 4029862422 C2CBF2921BD1161FE04388AAE80AB141
1
SQL>
5.
The PDB_ID number 2 is always assigned to the seed PDB because it is the second
container to be created after the root container (CON_ID 1).
Check all files of the CDB.
a. View the redo log files of the CDB.
SQL> col MEMBER format A40
SQL> select GROUP#, CON_ID, MEMBER from v$logfile;
Chapter 2 - Page 10
a
GROUP# CON_ID MEMBER
---------- ------ ---------------------------------------3
0 /u01/app/oracle/oradata/cdb1/redo03.log
2
1
SQL>
b.
View the control files of the CDB.
SQL> col NAME format A60
SQL> select NAME , CON_ID from v$controlfile;
NAME
CON_ID
------------------------------------------------------ -----/u01/app/oracle/oradata/cdb1/control01.ctl
0
/u01/app/oracle/fast_recovery_area/cdb1/control02.ctl
0
s
) ha
om ฺ
c
ฺ
ch ide
c. View all data files of the CDB, including those of the root and all iPDBs.
e
t
l- t Gu
a
1) With CDB_DATA_FILES view:
b
lo den
g
SQL> col file_name format A50
@ Stu
o
f
SQL> col tablespace_name format iA8
( n this
y
SQL> col file_id format 9999
og use
l
SQL> col con_id format
999
o
to
hnTABLESPACE_NAME,
SQL> select FILE_NAME,
FILE_ID, con_id
c
e
e
s
n
T
2 from
cdb_data_files
n
ce order by con_id ;
i
o
l
i
t
a
le
b
m
r
a
FILE_NAME
TABLESPA
r
o
f
e
f
n
I anCON_ID
s
lFILE_ID
a
r
b
t
--------------------------------------------------------- ---Glo n--on------SQL>
/u01/app/oracle/oradata/cdb1/users01.dbf
6
1
/u01/app/oracle/oradata/cdb1/undotbs01.dbf
4
1
/u01/app/oracle/oradata/cdb1/sysaux01.dbf
3
1
/u01/app/oracle/oradata/cdb1/system01.dbf
1
1
/u01/app/oracle/oradata/cdb1/pdbseed/system01.dbf
5
2
/u01/app/oracle/oradata/cdb1/pdbseed/sysaux01.dbf
7
2
/u01/app/oracle/oradata/cdb1/pdb1_1/system01.dbf
8
3
Chapter 2 - Page 11
USERS
UNDOTBS1
SYSAUX
SYSTEM
SYSTEM
SYSAUX
SYSTEM
a
/u01/app/oracle/oradata/cdb1/pdb1_1/sysaux01.dbf
SYSAUX
9
3
/u01/app/oracle/oradata/cdb1/pdb1_1/SAMPLE_SCHEMA_ USERS
10
3
users01.dbf
/u01/app/oracle/oradata/cdb1/pdb1_1/example01.dbf EXAMPLE
11
3
10 rows selected.
SQL>
2)
With ls Unix command:
SQL> !ls -l $ORACLE_BASE/oradata/cdb1
total 2575988
-rw-r----- 1 oracle oinstall 17874944
control01.ctl
drwxr-xr-x 2 oracle oinstall
4096
drwxr-x--- 2 oracle oinstall
4096
undotbs01.dbf
-rw-r----- 1 oracle oinstall
5251072
Sep
6 23:38
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
b
lo den
g
@ Stu
o
f
(in this
y
og use
l
o
hn se to
c
e
T cen
n
o
li
ti
e
a
l
Sep 6 22:29 users01.dbf
b
m
r
a
r
o
fe$ORACLE_BASE/oradata/cdb1/pdbseed
SQL>
nf !lsn-l
I
s
l
a
batotal
tr985064
o
l
n
G n-rw-r----o
1 oracle oinstall 88088576 Sep 5 10:50
pdbseed_temp01.dbf
Sep
Sep
Sep
Sep
Sep
Sep
Sep
Sep
Sep
-rw-r----- 1 oracle oinstall 671096832 Sep
-rw-r----- 1 oracle oinstall 262152192 Sep
SQL>
5
5
6
6
6
6
6
6
6
10:54
10:37
23:38
20:01
22:23
23:35
23:35
23:18
23:36
pdb1_1
pdbseed
redo01.log
redo02.log
redo03.log
sysaux01.dbf
system01.dbf
temp01.dbf
5 10:50 sysaux01.dbf
5 10:50 system01.dbf
There are only the SYSTEM and SYSAUX data files and a temp file for the seed
PDB.
d. Still connected to the root, now use DBA_DATA_FILES view.
SQL> select FILE_NAME, TABLESPACE_NAME, FILE_ID
2 from
dba_data_files;
FILE_NAME
TABLESPA FILE_ID
------------------------------------------ -------- --------Copyright © 2013, Oracle and/or its affiliates. All rights reserved.
Chapter 2 - Page 12
a
6
USERS
UNDOTBS1
SYSAUX
SYSTEM
4
3
1
SQL>
Notice that only the root data files are listed.
e. Now use V$TABLESPACE and V$DATAFILE view.
SQL>
SQL>
2
3
4
5
col NAME format A12
select FILE#, ts.name, ts.ts#, ts.con_id
from v$datafile d, v$tablespace ts
where d.ts#=ts.ts#
and
d.con_id=ts.con_id
order by 4,3;
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
b
lo den
g
@ Stu
o
f
(in this
y
og use
l
o
hn se to
c
e
T cen
n
o
li
ti
e
a
l
rm erab
o
f
In ansf
l
a
b
-tr
Glo n10onrows
selected.
FILE#
---------1
3
4
6
5
7
8
9
10
11
NAME
TS# CON_ID
------------ ---------- -----SYSTEM
0
1
SYSAUX
1
1
UNDOTBS1
2
1
USERS
4
1
SYSTEM
0
2
SYSAUX
1
2
SYSTEM
0
3
SYSAUX
1
3
USERS
3
3
EXAMPLE
4
3
SQL>
f.
List the temp files of the CDB.
2 from cdb_temp_files;
FILE_NAME
TABLESPA
FILE_ID
------------------------------------------------------- --------------
Chapter 2 - Page 13
a
/u01/app/oracle/oradata/cdb1/temp01.dbf
TEMP
1
/u01/app/oracle/oradata/cdb1/pdbseed/pdbseed_temp01.dbf TEMP
2
/u01/app/oracle/oradata/cdb1/pdb1_1/pdb1_1_temp01.dbf
TEMP
3
SQL>
6.
List all users created.
a. Verify that the SYSTEM user is created.
SQL> col username format A22
SQL> select username, common, con_id from cdb_users
2 where username ='SYSTEM';
USERNAME
---------------------SYSTEM
SYSTEM
SYSTEM
COM CON_ID
--- -----YES
1
YES
2
YES
3
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
b
lo den
g
SQL>
@ Stu
o
f
Notice that the user SYSTEM exists in all containers
is user.
(in as athcommon
y
b. List all common users of the CDB.log
se
u
o
n e tofrom cdb_users
SQL> select distinct h
username
c
e
2 where common
='YES';
T cens
n
tio le li
a
USERNAME
rm erab
o
f
-------------------In ansf
l
a
b DVFn-tr
Glo nMDSYS
o
XS$NULL
SYSKM
APEX_040100
DIP
SPATIAL_WFS_ADMIN_USR
FLOWS_FILES
SYSBACKUP
CTXSYS
OUTLN
SPATIAL_CSW_ADMIN_USR
GSMUSER
OLAPSYS
SYSTEM
Chapter 2 - Page 14
a
ORACLE_OCM
DVSYS
AUDSYS
ORDSYS
DBSNMP
OJVMSYS
GSMADMIN_INTERNAL
MDDATA
APEX_PUBLIC_USER
ORDPLUGINS
APPQOSSYS
GSMCATUSER
ORDDATA
SYSDG
XDB
SYS
WMSYS
LBACSYS
ANONYMOUS
SI_INFORMTN_SCHEMA
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
b
lo den
g
@ Stu
o
f
(in this
35 rows selected.
y
og use
l
o
SQL>
hn se to
c
e
T CDB.cen
c. List all local users n
of the
o
liusername, con_id from cdb_users
tidistinct
e
SQL> select
a
l
b ='NO';
rm common
a
2 fo
where
r
e
In ansf
l
a
b n-tr
CON_ID
Glo nUSERNAME
o
-------------------- -----SCOTT
BI
PM
IX
SH
OE
HR
PDBADMIN
3
3
3
3
3
3
3
3
8 rows selected.
SQL>
Chapter 2 - Page 15
a
d.
List local users in the root.
SQL> select username, con_id from cdb_users
2 where common ='NO';
USERNAME
CON_ID
-------------------- -----SCOTT
3
BI
3
PM
3
IX
3
SH
3
OE
3
HR
3
PDBADMIN
3
8 rows selected.
s
) ha
om ฺ
c
ฺ
SQL>
ch ide
e
t
i
- t Gtoucreate any
Notice that there is no local user in the root container because it a
is limpossible
b
local user in the root.
lo den
g
@ Stu
o
f
(in this
y
og use
l
o
hn se to
c
e
T cen
n
o
li
ti
e
a
l
rm erab
o
f
In ansf
l
a
b
tr
Glo non-
Chapter 2 - Page 16
a
7.
List all roles and privileges of the CDB.
a. List all roles of the CDB.
SQL> col role format A30
SQL> select role, common, con_id from cdb_roles;
ROLE
-----------------------------CONNECT
RESOURCE
DBA
AUDIT_ADMIN
AUDIT_VIEWER
SELECT_CATALOG_ROLE
EXECUTE_CATALOG_ROLE
DELETE_CATALOG_ROLE
PROF_ADMIN
EXP_FULL_DATABASE
IMP_FULL_DATABASE
CDB_DBA
…
DV_XSTREAM_ADMIN
DV_GOLDENGATE_REDO_ACCESS
DV_AUDIT_CLEANUP
DV_REALM_OWNER
PDB_DBA
…
DV_AUDIT_CLEANUP
DV_REALM_RESOURCE
DV_REALM_OWNER
PDB_DBA
COM CON_ID
--- -----YES
1
YES
1
YES
1
YES
1
YES
1
YES
1
YES
1
YES
1
YES
1
YES
1
YES
1
YES
1
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
b
lo den
g
YESfo@ 2 Stu
in thi2s
(YES
y
se 2
og YES
l
u
o
2
hn se toYES
c
e
n
T
YES
2
n
ce
i
o
l
i
t
a
le
b
m
YES
3
r
a
r
o
f
e
f
n
YES
3
I ans
l
a
b
tr
YES
3
Glo nonYES
3
252 rows selected.
SQL>
Notice that there is no local role in the root container because it is impossible to create any
local role in the root.
Chapter 2 - Page 17
a
b.
Check that the privileges are neither common nor local by nature.
SQL> desc sys.system_privilege_map
Name
Null?
----------------------------- -------PRIVILEGE
NOT NULL
NAME
NOT NULL
PROPERTY
NOT NULL
Type
---------------------NUMBER
VARCHAR2(40)
NUMBER
SQL> desc sys.table_privilege_map
Name
Null?
----------------------------- -------PRIVILEGE
NOT NULL
NAME
NOT NULL
Type
---------------------NUMBER
VARCHAR2(40)
SQL>
Notice that there is no COMMON column.
c. Verify that the privilege, when granted, becomes a common or local privilege.
s
) ha
om ฺ
c
ฺ
ch ide
SQL> desc CDB_SYS_PRIVS
e
t
i
l- t Gu
a
Name
Null?
Type
b
lo-------------------en
------------------------------- -------g
d
u
o@ is VARCHAR2(128)
St
GRANTEE
f
n
i
(
th VARCHAR2(40)
PRIVILEGE
y
g
e
lo o us
ADMIN_OPTION
VARCHAR2(3)
o
n
t
h
COMMON
VARCHAR2(3)
ec ense
T
CON_ID
NUMBER
n
ic
o
l
i
t
e
a
bl
m
r
a
r
o
SQL>f desc CDB_TAB_PRIVS
n nsfe
I
l
Name
Null?
Type
a -tra
b
o
-------- -------------------Gl n------------------------------on
GRANTEE
VARCHAR2(128)
OWNER
TABLE_NAME
GRANTOR
PRIVILEGE
GRANTABLE
HIERARCHY
COMMON
TYPE
CON_ID
VARCHAR2(128)
VARCHAR2(128)
VARCHAR2(128)
VARCHAR2(40)
VARCHAR2(3)
VARCHAR2(3)
VARCHAR2(3)
VARCHAR2(24)
NUMBER
SQL>
There is a COMMON column.
Chapter 2 - Page 18
a
d.
Notice that the role, though common or local depending on how the role was created is
also, like privileges, either granted commonly or locally.
SQL>
SQL>
SQL>
2
3
col grantee format A10
col granted_role format A28
select grantee, granted_role, common, con_id
from cdb_role_privs
where grantee='SYSTEM';
GRANTEE
---------SYSTEM
SYSTEM
SYSTEM
SYSTEM
SYSTEM
SYSTEM
GRANTED_ROLE
---------------------------DBA
AQ_ADMINISTRATOR_ROLE
DBA
DBA
COM CON_ID
--- -----YES
1
YES
1
YES
2
YES
2
YES
3
YES
3
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
b
lo den
g
@ Stu
o
f
(in this
y
og use
l
o
hn se to
c
e
T cen
n
o
li
ti
e
a
l
rm erab
o
f
In ansf
l
a
b
tr
Glo non6 rows selected.
SQL> EXIT
$
Chapter 2 - Page 19
a
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
b
lo den
g
@ Stu
o
f
(in this
y
og use
l
o
hn se to
c
e
T cen
n
o
li
ti
e
a
l
rm erab
o
f
In ansf
l
a
b
tr
Glo non-
Chapter 2 - Page 20
a
s
) ha
om ฺ
c
ฺ
ch3: ide
e
t
i
l- t Gu
Creating a Multitenant
a
b
lo denand
g
Container
Database
@ Stu
o
f
Pluggable
n thiDatabases
s
i
(
y
ogChapterus3 e
l
o
hn se to
c
e
T cen
n
o
li
ti
e
a
l
rm erab
o
f
In ansf
l
a
b
tr
Glo non-
Practices for Lesson 3: Creating a Multitenant Container Database and Pluggable Databases
Chapter 3 - Page 1
a
Practices for Lesson 3
Practices Overview
In this practice you will create a new CDB named cdb2 with DBCA with no PDB except the
seed.
After the CDB creation is completed, check the physical and logical structures of the new CDB.
Then, you will create several PDBs using different methods.
•
Create pdb2_1 from seed in cdb2.
•
Clone pdb2_2 in cdb2 from pdb2_1.
•
Plug the non-CDB orcl2 into the CDB cdb2 as pdb_orcl2.
•
Merge the two CDBs cdb1 and cdb2 into cdb2, and optionally drop the database
cdb1 (optional practice).
Finally, you drop the pdb2_3 using either DBCA or SQL Developer or SQL*Plus after the
creation of this PDB.
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
b
lo den
g
@ Stu
o
f
(in this
y
og use
l
o
hn se to
c
e
T cen
n
o
li
ti
e
a
l
rm erab
o
f
In ansf
l
a
b
tr
Glo non-
Chapter 3 - Page 2
a
Practice 3-1: Creating a New CDB
Overview
In this practice, you will create a new CDB named cdb2 with DBCA.
Assumptions
The created CDB cdb1 already exists.
Tasks
1.
Create a CDB named cdb2 using DBCA. First release resources held by other instances,
shutting down the orcl, orcl2 and cdb1 instances.
a.
Shut down orcl.
$ . oraenv
ORACLE_SID = [cdb1] ? orcl
s
) ha
om ฺ
c
ฺ
ch ide
e
Connected to:
t
i
u
l-12.1.0.0.2
G
a
Oracle Database 12c Enterprise Edition Release
t
b
n
o
l
e
64bit Production
tudApplication
@g Real
o
S
With the Partitioning, OLAP, DatanfMining,
is
(i
h
Testing
t
y
og use
l
o
hn se to
SQL> SHUTDOWN IMMEDIATE
c
e
T cen
Database closed.
n
o
li
ti
Database dismounted.
e
a
l
bshut down.
rm
a
r
ORACLE
instance
o
f
e
In EXIT
sf
l
SQL>
n
a
a
b
tr
Glo n$onb. Shut down orcl2.
$ . oraenv
ORACLE_SID = [orcl] ? orcl2
Connected to:
Testing
Chapter 3 - Page 3
a
Database closed.
ORACLE instance shut down.
SQL> EXIT
$
c.
Shut down cdb1.
$ . oraenv
ORACLE_SID = [orcl2] ? cdb1
Connected to:
Testing
s
) ha
a
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
b
lo den
g
@ Stu
Database closed.
o
f
(in this
y
og use
l
o
SQL> EXIT
hn se to
c
e
$
T cen
n
i
o
lfollowing
i
tperform
d. Start dbca and
the
steps.
e
a
l
b
m
r
a
$ dbca
fo sfer
n
I
n
al -traWindow/Page
Step
Description
Choices or Values
b
o
l
n
G a. no Step 1: Database Operation
Select “Create Database”.
Click Next.
b.
Step 2: Creation Mode
Select “Advanced Mode”.
Click Next.
c.
Step 3: Database Template
Select “General Purpose or Transaction
Processing”.
Click Next.
d.
Step 4: Database Identification
Enter
Global Database Name: cdb2
SID: cdb2
Select “Create As Container Database”
Select “Create An Empty Container Database”
Click Next.
Chapter 3 - Page 4
Step
Window/Page Description
Choices or Values
e.
Step 5: Management Options
Deselect “Configure Enterprise Manager (EM)
Database Express”.
Click Next.
f.
Step 6: Database Credentials
Select “Use same Administrative password…”
Enter:
Password: oracle_4U
Confirm password: oracle_4U
Click Next.
g.
Step 7: Network Configuration
Listener Selection: Click Next
h.
Step 8: Storage Locations
Confirm Storage type is “File System”.
Select “Use Common Location for All Database
Files”.
Click Next.
s
) ha
i.
Step 9: Database Options
Click Next.
j.
Step 10: Initialization Parameters
Select “Character Sets”.
Select “Use Unicode (AL32UTF8)”.
Click Next.
a
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
b
lo Database”.
en
g
d
k.
Step 11: Creation Option
Select
“Create
u
o@
St
f
n
s
Click
Next.
i
i
(
th
y
g
e
l.
Step 12: Pre Requisite Checks
s Next.
lo o uClick
o
n
t
m.
Step 13: Summary ch
e ense Click Finish.
T
n Page
n.
Step 14: Progress
On the Database Configuration Assistant page (for
ic
o
l
i
t
e
password management) click Exit.
a
l
b
m
r
a
Click Close.
fo sfer
n
I
al -tran
b
o
Gl non
Chapter 3 - Page 5
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
b
lo den
g
@ Stu
o
f
(in this
y
og use
l
o
hn se to
c
e
T cen
n
o
li
ti
e
a
l
rm erab
o
f
In ansf
l
a
b
tr
Glo non-
Chapter 3 - Page 6
a
Practice 3-2: Exploring CDB and PDB Structures
Overview
In this practice, you check the physical and logical structures of the new CDB cdb2 and its seed
PDB.
Tasks
1.
Connect to the multitenant container database cdb2.
$ . oraenv
ORACLE_SID = [cdb1] ? cdb2
Connected to:
With the Partitioning, OLAP, Data Mining and Real Application
Testing options
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
b
lo den
SQL>
g
@ Stu
o
f
a. Check if the database is a multitenant container
database.
is
(in v$database;
h
t
y
SQL> SELECT name, cdb, con_id
from
og use
l
o
hn se to
c
NAME
CDB
CON_ID
e
T cen
n
--------- -----------o
li
ti
e
a
l
CDB2
YES
0
b
m
r
a
r
o
nf nsfe
I
l
baSQL>
tra
o
l
n
G b. nCheck
o the instance name.
SQL> SELECT INSTANCE_NAME, STATUS, CON_ID from v$instance;
INSTANCE_NAME
STATUS
CON_ID
---------------- ------------ ---------cdb2
OPEN
0
SQL> EXIT
$
2.
Explore the services.
a. Check services.
$ lsnrctl status
Chapter 3 - Page 7
a
LSNRCTL for Linux: Version 12.1.0.0.2 - Production on 07-SEP2012 01:10:16
Connecting to
-----------------------Alias
LISTENER
Version
- Production
Start Date
14-SEP-2012 03:04:56
Uptime
Trace Level
off
Security
SNMP
OFF
ra
Listener Log File
))
)(Presentation=HTTP)(Session=RAW))
Services Summary...
service...
service...
service...
service...
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
b
lo den
g
@ Stu
o
f
(in this
y
og use
l
o
hn se to
c
e
T cen
n
o
li
ti
e
a
l
rm erab
o
f
In ansf
l
a
b
tr
Glo non-
Chapter 3 - Page 8
a
$
b.
List the services automatically created for each container.
Connected to:
SQL> SELECT name, con_id from v$services;
NAME
CON_ID
-------------------- ---------cdb2XDB
1
cdb2
1
SYS$BACKGROUND
1
SYS$USERS
1
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
b
lo den
g
SQL>
@ Stu
o
f
Notice that PDB$SEED service is not listed. No one
should
n thiconnect
s to this service because
i
(
there should be no operation performed on
se It is reserved as a template to
ogythis container.
l
create other PDBs.
u
o
n a new
toview V$PDBS.
hUse
3. Display the pluggable databases.
c
e
e
s
n OPEN_MODE from v$pdbs;
T NAME,
e
SQL> SELECT CON_ID,
n
c
i
o
l
ti
a
le
b
m
r
a
o sfNAME
fCON_ID
OPEN_MODE
er
n
I
l
n
---------ba---------tra 2 -----------------------------o
l
n
PDB$SEED
READ ONLY
G no
SQL>
4.
Notice that the seed PDB is in READ ONLY open mode.
View new family of views CDB_xxx:
SQL> connect / as sysdba
Connected.
SQL> col PDB_NAME format a8
SQL> col CON_ID format 999999
SQL> SELECT PDB_ID, PDB_NAME, DBID, GUID, CON_ID
2 from cdb_pdbs order by 1;
PDB_ID PDB_NAME
DBID GUID
CON_ID
------ -------- ---------- ---------------------------- -----Copyright © 2013, Oracle and/or its affiliates. All rights reserved.
Chapter 3 - Page 9
a
2 PDB$SEED 4012275228 203F5F3EDB7F0000000000000000
1
SQL>
5.
Check all files of the CDB.
a. View the redo log files of the CDB.
SQL> col MEMBER format A42
SQL> SELECT GROUP#, MEMBER, CON_ID from v$logfile;
GROUP# MEMBER
CON_ID
---------- ------------------------------------------ ------3 /u01/app/oracle/oradata/cdb2/redo03.log
0
0
0
s
) ha
SQL>
b.
View the control files of the CDB.
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
b
lo den
g
NAME
CON_ID
u
t
@
o
S
------------------------------------------------------------nf this
i
(
/u01/app/oracle/oradata/cdb2/control01.ctl
0
gy use
o
l
o
0
n e to
h
c
e ens
T
n
SQL>
tio le lic
a
b CDB, including those of the root and all PDBs, with
c. View all rdata
m files rofathe
o
f
e
CDB_DATA_FILES
view.
In ansf
l
a
r file_name format A65
b SQL>
tcol
Glo nSQL>
on- SELECT FILE_NAME, TABLESPACE_NAME, FILE_ID, con_id
2 from
cdb_data_files
SQL> SELECT name, con_id from v$controlfile;
3
order
by con_id ;
FILE_NAME
---------------------------------------------------------------TABLESPACE_NAME
FILE_ID CON_ID
------------------------------ ---------- ------/u01/app/oracle/oradata/cdb2/users01.dbf
USERS
6
1
UNDOTBS1
4
1
Chapter 3 - Page 10
a
SYSAUX
3
1
SYSTEM
1
1
SYSTEM
5
2
SYSAUX
7
2
6 rows selected.
SQL>
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
SQL> col tablespace_name format A10
a
b
lo den
SQL> SELECT FILE_NAME, TABLESPACE_NAME,gFILE_ID
@ Stu
2 from
dba_data_files;
o
f
(in this
y
og use
l
FILE_NAME
TABLESPACE FILE_ID
o
n
o
t
--------------------------------------------------- ------ch nse
e
T
USERS
6
e
n
c
i
o
l
i
t
UNDOTBS1
4
a
le
b
m
r
a
SYSAUX
3
fo sfer
n
I
SYSTEM
1
al/u01/app/oracle/oradata/cdb2/system01.dbf
an
r
b
t
o
Gl nSQL>
on EXIT
d.
Still connected to the root, now use DBA_DATA_FILES view.
$
Notice that only root data files are listed.
e. Start the cdb1 database.
$ . oraenv
Connected to an idle instance.
SQL> STARTUP
Chapter 3 - Page 11
a
ORACLE instance started.
Total System Global Area 400846848 bytes
Fixed Size
2271568 bytes
Variable Size
243271344 bytes
Database Buffers
146800640 bytes
Redo Buffers
8503296 bytes
Database mounted.
Database opened.
SQL> EXIT
$
1)
Use netca to add the PDB1_1 net service name for pdb1_1 pluggable database of
cdb1 in the tnsnames.ora file.
$ netca
s
) ha
2) On the Welcome page, select the “Local Net Service Name configuration” and
click Next.
On the Net Service Name Configuration page, accept Add and click Next.
om ฺ
c
ฺ
ch pdb1_1
4) On the Net Service Name Configuration, Service Name page,
enter
e
ide as
t
i
u
l
Service Name and click Next.
a nt G
b
o
l
5) On the Net Service Name Configuration, Select Protocols
g tupage,
de select TCP and
@
click Next.
fo is S
nTCP/IP
i
(
6) On the Net Service Name Configuration,
thProtocol page, enter your
y
g
e
complete host name, for example,
or localhost, accept
s
lo <yourservername>,
uand
o
n
o
“Use the standard port number
of
1521,”
click
Next.
t
ch Configuration,
eName
se
7) On the Net Service
Test page, select “No, do not test” (the
n
T
e
n
c
pluggable database
is
not
yet
opened)
and
click Next.
i
o
l
ti
e
a
l
b Name Configuration, Net Service Name page, accept pdb1_1
8) On r
the
mNet Service
a
r
o
f
e
as
Net
Service
Name
and click Next.
n nsf
I
l
a Net Service Name Configuration, Another Net Service Name page, select
On
ba9) nNo,
trthe
o
l
and
Next.
G no
10) On the Net Service Name Configuration Done page, click Next.
3)
f.
11) When you are back on the Welcome page, click Finish.
Open the pdb1_1 pluggable database in cdb1.
Connected to:
Testing
SQL> ALTER PLUGGABLE DATABASE pdb1_1 OPEN;
Chapter 3 - Page 12
a
Pluggable database altered.
SQL> EXIT
$
g.
Connect to the pdb1_1 of cdb1, and use DBA_DATA_FILES view.
$ sqlplus system/oracle_4U@pdb1_1
SQL*Plus: Release 12.1.0.0.2 Production on Fri Sep 7 01:28:32
2012
Last Successful login time: Wed Aug 22 2012 13:16:11 +00:00
Connected to:
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
b
lo den
g
SQL> SELECT FILE_NAME, TABLESPACE_NAME,
FILE_ID
@ Stu
o
f
2 from
dba_data_files;
(in this
y
og use
l
o
FILE_NAME
hn se to
c
---------------------------------------------------------------e
T cen
n
o
li
ti
e
a
l
TABLESPACE_NAME
FILE_ID
b
m
r
a
r
o
--------------------------------------nf nsfe
I
l
ba/u01/app/oracle/oradata/cdb1/pdb1_1/system01.dbf
tra
o
l
n
SYSTEM
8
G no
SYSAUX
9
/u01/app/oracle/oradata/cdb1/pdb1_1/SAMPLE_SCHEMA_users01.dbf
USERS
10
/u01/app/oracle/oradata/cdb1/pdb1_1/example01.dbf
EXAMPLE
11
SQL>
Notice that only pdb1_1 data files are listed.
Chapter 3 - Page 13
a
h.
Now use V$TABLESPACE and V$DATAFILE view.
SQL> col NAME format A12
SQL> SELECT FILE#, ts.name, ts.ts#, ts.con_id
2 from v$datafile d, v$tablespace ts
3 where d.ts#=ts.ts#
4 and
d.con_id=ts.con_id
5 order by 4;
FILE#
---------4
11
10
8
9
NAME
TS#
CON_ID
------------ ---------- ---------UNDOTBS1
2
0
EXAMPLE
4
3
USERS
3
3
SYSTEM
0
3
SYSAUX
1
3
s
) ha
SQL>
om ฺ
c
ฺ
ch ide
e
SQL> SELECT FILE_NAME, TABLESPACE_NAME from dba_temp_files;
t
i
l- t Gu
a
b
lo den
g
FILE_NAME
@ Stu
o
f
-------------------------------------------------------------(in this
y
TABLESPACE_NAME
og use
l
o
-----------------------------hn se to
c
/u01/app/oracle/oradata/cdb1/pdb1_1/pdb1_1_temp01.dbf
e
T cen
n
TEMP
o
li
ti
e
a
l
rm erab
o
f
SQL>
EXIT
In ansf
l
a
$
b n-tr
Gloj. nList
o the password file and SPFILE of both cdb1 and cdb2.
i.
List the temp files of the PDB.
$ cd $ORACLE_HOME/dbs
$ ls -l orapw* spfile*
7680
7680
7680
7680
7680
3584
3584
3584
3584
3584
Sep
Sep
Sep
Sep
Sep
Sep
Sep
Sep
Sep
Sep
5
7
5
5
5
7
7
6
6
7
10:43
00:48
07:23
10:02
10:19
01:23
01:08
18:13
10:00
00:35
orapwcdb1
orapwcdb2
orapwem12rep
orapworcl
orapworcl2
spfilecdb1.ora
spfilecdb2.ora
spfileem12rep.ora
spfileorcl2.ora
spfileorcl.ora
Chapter 3 - Page 14
a
$
k.
Check ADR files, directories, new DDL statement in alert.log.
$ cd $ORACLE_BASE/diag/rdbms/
$ ls
cdb1 cdb2 em12rep orcl orcl2
$ cd cdb2/cdb2/trace
$ vi alert_cdb2.log
…
Mon Feb 06 09:27:09 2012
Fri Sep 07 00:41:54 2012
create pluggable database PDB$SEED as clone using
'/u01/app/oracle/product/12.1.0/dbhome_1/assistants/dbca/templat
es//pdbseed.xml' source_file_name_convert =
('/ade/b/3895122769/oracle/oradata/seeddata/pdbseed/temp01.dbf',
'/u01/app/oracle/oradata/cdb2/pdbseed/pdbseed_temp01.dbf',
'/ade/b/3895122769/oracle/oradata/seeddata/pdbseed/system01.dbf'
,'/u01/app/oracle/oradata/cdb2/pdbseed/system01.dbf',
'/ade/b/3895122769/oracle/oradata/seeddata/pdbseed/sysaux01.dbf'
,'/u01/app/oracle/oradata/cdb2/pdbseed/sysaux01.dbf') NOCOPY
****************************************************************
Pluggable Database PDB$SEED with pdb id - 2 is created as
UNUSABLE.
If any errors are encountered before the pdb is marked as NEW,
then the pdb must be dropped
****************************************************************
…
Post plug operations are now complete.
Pluggable database PDB$SEED with pdb id - 2 is now marked as
NEW.
****************************************************************
Completed: create pluggable database PDB$SEED as clone using
'/u01/app/oracle/product/12.1.0/dbhome_1/assistants/dbca/templat
es//pdbseed.xml' source_file_name_convert =
('/ade/b/3895122769/oracle/oradata/seeddata/pdbseed/temp01.dbf',
'/u01/app/oracle/oradata/cdb2/pdbseed/pdbseed_temp01.dbf',
'/ade/b/3895122769/oracle/oradata/seeddata/pdbseed/system01.dbf'
,'/u01/app/oracle/oradata/cdb2/pdbseed/system01.dbf',
'/ade/b/3895122769/oracle/oradata/seeddata/pdbseed/sysaux01.dbf'
,'/u01/app/oracle/oradata/cdb2/pdbseed/sysaux01.dbf') NOCOPY
alter pluggable database PDB$SEED open restricted
Pluggable database PDB$SEED dictionary check beginning
Pluggable Database PDB$SEED Dictionary check complete
…
$
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
b
lo den
g
@ Stu
o
f
(in this
y
og use
l
o
hn se to
c
e
T cen
n
o
li
ti
e
a
l
rm erab
o
f
In ansf
l
a
b
tr
Glo non-
Chapter 3 - Page 15
a
6.
List all users created in the new CDB cdb2.
a.
Connect to cdb2 instance.
$ . oraenv
The Oracle base for
/u01/app/oracle
Connected to:
Testing options
SQL>
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
b
lo den
g
@ Stu
o
f
USERNAME
COM
CON_ID
in this
(--y
-----------------------------g us------e
o
l
o
SYSTEM
YES
1
n e to
h
c
SYSTEM
2
Te cens YES
n
tio le li
a
SQL>
rm erab
o
f
n the nuser
NoticeIthat
sf SYSTEM exists in all containers as a common user.
l
a
a
r
b Listnall-tcommon
c.
users in the CDB.
Glo nSQL>
o select distinct username from cdb_users
b.
Verify that the SYSTEM user is created.
SQL> select username, common, con_id from cdb_users
2 where username ='SYSTEM';
2
where common ='YES' order by 1;
USERNAME
-----------------------------ANONYMOUS
APEX_040200
APEX_PUBLIC_USER
APPQOSSYS
AUDSYS
CTXSYS
DBSNMP
DIP
DVF
Chapter 3 - Page 16
a
DVSYS
FLOWS_FILES
GSMADMIN_INTERNAL
GSMCATUSER
GSMUSER
LBACSYS
MDDATA
MDSYS
OJVMSYS
OLAPSYS
ORACLE_OCM
ORDDATA
ORDPLUGINS
ORDSYS
OUTLN
SI_INFORMTN_SCHEMA
SPATIAL_CSW_ADMIN_USR
SPATIAL_WFS_ADMIN_USR
SYS
SYSBACKUP
SYSDG
SYSKM
SYSTEM
WMSYS
XDB
XS$NULL
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
b
lo den
g
@ Stu
o
f
(in this
y
og use
l
o
hn se to
c
e
T cen
n
o
li
ti
e
a
l
rm erab
o
f
sf
35Inrows n
selected.
l
a
a
b n-tr
Glo nSQL>
o
d.
List all local users in the CDB.
SQL> select distinct username, CON_ID from cdb_users
no rows selected
SQL>
Chapter 3 - Page 17
a
e.
List local users in root.
SQL> select distinct username from dba_users
no rows selected
SQL>
7.
Notice that there is no local user in the root container because it is impossible to create any
local user in the root.
View distinct accesses by different containers to the single SGA.
SQL> select distinct status, con_id from v_$bh order by 2 ;
STATUS
CON_ID
---------- ---------cr
1
free
1
xcur
1
cr
2
xcur
2
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
b
SQL> EXIT
lo den
g
@ Stu
$
o
f
(in this
y
og use
l
o
hn se to
c
e
T cen
n
o
li
ti
e
a
l
rm erab
o
f
In ansf
l
a
b
tr
Glo non-
Chapter 3 - Page 18
a
Practice 3-3: Creating a PDB from Seed
Overview
In this practice, you will create a new PDB pdb2_1 in cdb2 from seed.
Assumptions
The creation of the CDB cdb2 is successful.
Tasks
Either use DBCA or SQL Developer or SQL commands.
The creation using SQL is described below.
1. Create a directory for the new data files of pdb2_1 of cdb2.
$ . oraenv
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
b
2. Run SQL*Plus and connect to the root with a user with CREATE
PLUGGABLE
o den DATABASE
l
g
privilege.
@ Stu
o
f
(in this
y
og use
l
o
Connected to:
hn se to
c
e
Oracle Database T
12c Enterprise
Edition Release 12.1.0.0.2 n
e
n
c
64bit Production
i
o
l
ti
a
le OLAP, Data Mining and Real Application
With the
Partitioning,
b
m
r
a
Testing
fo options
er
f
n
I
s
al -tran
b
o
PLUGGABLE DATABASE pdb2_1 ADMIN USER pdb2_1_admin
Gl nSQL>
o2n CREATE
IDENTIFIED BY oracle_4U ROLES=(CONNECT)
$ cd $ORACLE_BASE/oradata/cdb2
$ mkdir pdb2_1
$
3
4
FILE_NAME_CONVERT=('/u01/app/oracle/oradata/cdb2/pdbseed'
,'/u01/app/oracle/oradata/cdb2/pdb2_1');
Pluggable database created.
SQL>
3.
Check the open mode of pdb2_1.
SQL> col con_id format 999
SQL> select con_id, NAME, OPEN_MODE,DBID, CON_UID from V$PDBS;
CON_ID NAME
OPEN_MODE
DBID
Chapter 3 - Page 19
CON_UID
a
------ ---------------------- ---------- ---------- ---------2 PDB$SEED
READ ONLY 4029890286 4029890286
3 PDB2_1
MOUNTED
3071827262 3071827262
SQL>
4.
Open pdb2_1.
a. Open the PDB.
SQL> alter pluggable database pdb2_1 open;
SQL> EXIT
$
b.
Connect to pdb2_1 AS SYSDBA.
1)
s
) ha
om ฺ
c
ฺ
2) On the Welcome page, select the “Local Net Service Name configuration”
e
ch idand
e
t
click Next.
i
u
l
GNext.
a and nclick
t
bAdd
3) On the Net Service Name Configuration page, accept
o
l
gName tpage,
deenter pdb2_1 as
u
4) On the Net Service Name Configuration, Service
@
nfo this S
i
(
5) On the Net Service Name Configuration,
gy uSelect
se Protocols page, select TCP and
o
l
o
click Next.
to TCP/IP Protocol page, enter your
hnConfiguration,
c
e
6) On the Net Service e
Name
s
n <yourservername>, or localhost, accept
T example,
e
complete hostn
name, foric
o
l
ti
“Use theastandard
port
le number of 1521,” and click Next.
b
m
r
a
r Name Configuration, Test page, select “No, do not test” (the
7) On
fothe Net
eService
f
n
I
s
pluggable
database
is not yet opened) and click Next.
l
n
a
a
r
b
t
- the Net Service Name Configuration, Net Service Name page, accept pdb2_1
On
Glo n8)onas
Net Service Name and click Next.
$ netca
9)
On the Net Service Name Configuration, Another Net Service Name page, select
No, and Next.
$ sqlplus sys/oracle_4U@pdb2_1 AS SYSDBA
Connected to:
With the Partitioning, OLAP, Advanced Analytics, Real
Application Testing
SQL>
Chapter 3 - Page 20
a
5.
The service is now available and registered with the listener.
SQL> !lsnrctl status
Connecting to
-----------------------Alias
LISTENER
Version
- Production
Start Date
14-SEP-2012 03:04:56
Uptime
Trace Level
off
Security
SNMP
OFF
ra
Listener Log File
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
b
lo den
g
@ Stu
o
f
(in this
y
og use
l
o
hn se to
c
e
T cen
n
o
li
ti
e
a
l
rm erab
o
f
In ansf
l
a
b (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=yourserver)(PORT=1521)
tr
Glo n))on(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=yourserver)(PORT=5501)
Services Summary...
service...
service...
Chapter 3 - Page 21
a
service...
service...
service...
service...
service.
service.
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
SQL>
l- t Gu
a
b
6. Connect to pdb2_1 as sys user by using EasyConnect and
user.
lothen asdpdb2_1_admin
en
g
u
SQL> CONNECT sys/oracle_4U@localhost:1521/pdb2_1
o@ is St AS SYSDBA
f
n
i
(
Connected.
th
y
g
e
lo o us
SQL> connect pdb2_1_admin/oracle_4U@PDB2_1
o
n
h se t
Connected.
c
e
T cen
n
o
li
ti
SQL> show acon_name
e
l
rm erab
o
f
In ansf
l
CON_NAME
a
b n-tr
Glo n-----------------------------o
PDB2_1
SQL>
7.
List the data files created.
SQL> !ls -l $ORACLE_BASE/oradata/cdb2/pdb2_1/*
-rw-r----- 1 oracle oinstall 20979712 Sep 7 01:47
/u01/app/oracle/oradata/cdb2/pdb2_1/pdbseed_temp01.dbf
SQL>
Chapter 3 - Page 22
a
8.
Check the services, data files, and tablespaces using views.
SQL> connect system/oracle_4U@pdb2_1
Connected.
SQL> select name from v$services;
NAME
---------------------------pdb2_1
SQL>
SQL>
SQL>
SQL>
SQL>
2
3
col file_name format A50
col tablespace_name format A8
col file_id format 99
col con_id format 9
select FILE_NAME, TABLESPACE_NAME, FILE_ID, con_id
from
cdb_data_files
order by con_id ;
s
) ha
om ฺ
c
ฺ
h ide
cTABLESPA
FILE_NAME
e
t
i
l- t Gu
FILE_ID CON_ID
a
b
lo den-------- ----------------------------------------------------g
@ Stu
--- -----o
f
(in this
SYSAUX
y
g
e
9
3
lo o us
o
n
SYSTEM
h se t
c
e
8
3
T cen
n
o
li
i
t
e
a
l
SQL> select
TABLESPACE_NAME, FILE_ID
b
rm eFILE_NAME,
a
r
o
f
2
from
dba_data_files;
In ansf
l
a
b n-tr
TABLESPA
Glo nFILE_NAME
o
FILE_ID
-------------------------------------------------- -------- -----/u01/app/oracle/oradata/cdb2/pdb2_1/system01.dbf
SYSTEM
8
SYSAUX
9
FILE_NAME
FILE_ID
TABLESPA
Chapter 3 - Page 23
a
------------------------------------------------------ ------------/u01/app/oracle/oradata/cdb2/pdb2_1/pdbseed_temp01.dbf TEMP
3
2 from dba_temp_files;
FILE_NAME
TABLESPA
FILE_ID
------------------------------------------------------- -------------/u01/app/oracle/oradata/cdb2/pdb2_1/ pdbseed_temp01.dbf TEMP
3
s
) ha
SQL>
9.
To be able to view all objects of all containers in the CDB, connect to the root and use
CDB_xxx views.
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
Connected.
a
b
lo den
SQL> show con_id
g
@ Stu
o
f
(in this
CON_ID
y
og use
l
-----------------------------o
hn se to
1
c
e
T cen
SQL> show con_name
n
o
li
ti
e
a
l
rm erab
o
CON_NAME
f
In ansf
l
-----------------------------a
b n-tr
Glo nCDB$ROOT
o
SQL> select name from v$services;
NAME
-----------------------------pdb2_1
cdb2XDB
cdb2
SYS$BACKGROUND
SYS$USERS
SQL> select FILE_NAME, TABLESPACE_NAME, FILE_ID, con_id
2 from
cdb_data_files
3 order by con_id, file_id ;
Chapter 3 - Page 24
a
FILE_NAME
FILE_ID CON_ID
---------------------------------------------------- -----FILE_NAME
FILE_ID CON_ID
---------------------------------------------------- -----/u01/app/oracle/oradata/cdb2/system01.dbf
1
1
3
1
4
1
6
1
5
2
7
2
8
3
9
3
TABLESPA
-------------------------------------------------/u01/app/oracle/oradata/cdb2/users01.dbf
6
4
3
1
-------- ----
-------- ---TABLESPA
-------- ---SYSTEM
SYSAUX
UNDOTBS1
USERS
s
) ha
om ฺ
c
ฺ
h ide
cSYSAUX
e
t
i
l- t Gu
a
b
lo denSYSTEM
g
@ Stu
o
f
SYSAUX
(in this
y
og use
l
o
hn se to
8 rows selected.Tec
n
e
n
c
i
o
l
ti
a
le TABLESPACE_NAME, FILE_ID
b
SQL> select
FILE_NAME,
m
r
a
r
fofrom sfedba_data_files;
2
n
I
al -tran
b
o
Gl nFILE_NAME
on
TABLESPA
FILE_ID
Chapter 3 - Page 25
SYSTEM
USERS
UNDOTBS1
SYSAUX
SYSTEM
a
FILE_NAME
FILE_ID
------------------------------------------------------------/u01/app/oracle/oradata/cdb2/temp01.dbf
1
/u01/app/oracle/oradata/cdb2/pdbseed/pdbseed_temp01.dbf
2
/u01/app/oracle/oradata/cdb2/pdb2_1/pdbseed_temp01.dbf
3
TABLESPA
-------TEMP
TEMP
TEMP
2 from dba_temp_files;
s
) ha
FILE_NAME
TABLESPA
FILE_ID
------------------------------------------------------- -------------/u01/app/oracle/oradata/cdb2/temp01.dbf
TEMP
1
SQL> EXIT
$
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
b
lo den
g
@ Stu
o
f
(in this
y
og use
l
o
hn se to
c
e
T cen
n
o
li
ti
e
a
l
rm erab
o
f
In ansf
l
a
b
tr
Glo non-
Chapter 3 - Page 26
a
Practice 3-4: Cloning PDB Within the Same CDB
Overview
In this practice, you will create a new PDB with the cloning method, cloning pdb2_2 from
pdb2_1 within the same CDB cdb2.
Assumptions
The pdb2_1 creation has completed successfully in Practice 3-3.
Tasks
Either use the SQL commands OR SQL Developer.
Method with SQL*Plus.
$ . oraenv
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
$ mkdir pdb2_2
b
lo den
g
$
@ Stu
o
f
is CREATE PLUGGABLE
2. Run SQL*Plus and connect to the root as a user
(ingrantedthwith
y
DATABASE privilege.
og use
l
o
n mode
o cloning.
a. Set pdb2_1 in READ ONLY h
open
tbefore
c
e
e
s
T cen
n
o
li
ti
e
a
l
rm to:erab
Connected
o
f
In aDatabase
sf 12c Enterprise Edition Release 12.1.0.0.2 Oracle
l
n
a
b 64bit
trProduction
Glo nWith
on- the Partitioning, OLAP, Advanced Analytics and Real
SQL> alter pluggable database pdb2_1 close;
SQL> alter pluggable database pdb2_1 open read only;
SQL>
Chapter 3 - Page 27
a
b. Change OMF DB_CREATE_FILE_DEST parameter value to
'/u01/app/oracle/oradata/cdb2/pdb2_2'.
SQL> alter system set db_create_file_dest =
'/u01/app/oracle/oradata/cdb2/pdb2_2';
System altered.
SQL>
c.
Clone pdb2_2 from pdb2_1.
SQL> CREATE PLUGGABLE DATABASE pdb2_2 FROM pdb2_1;
SQL>
3.
SQL> select name, open_mode from v$pdbs;
s
) ha
om ฺ
c
ฺ
NAME
OPEN_MODE
ch ide
e
t
i
------------------------------ ---------l- t Gu
a
b
PDB$SEED
READ ONLY lo
en
g
d
u
PDB2_1
READoONLY
@ St
f
n
i
PDB2_2
(MOUNTEDthis
y
og use
l
SQL>
o
hnmodeseandtoopen PDB2_2.
c
4. Set PDB2_1 in READ WRITE
open
e
T cen
n
a. Open PDB2_1 tin
READ
WRITE
o
li mode.
i
e
a
l
b database PDB2_1 close;
SQL> alter
rm pluggable
a
r
o
f
e
In ansf
l
a
b Pluggable
tr database altered.
Glo nonSQL> alter pluggable database PDB2_1 open;
SQL>
b.
Open PDB2_2 in READ WRITE mode.
SQL> alter pluggable database PDB2_2 open;
SQL> EXIT
$
Chapter 3 - Page 28
a
c.
Connect to pdb2_2 AS SYSDBA.
1)
$ netca
3)
click Next.
4) On the Net Service Name Configuration, Service Name page, enter pdb2_2 as
5) On the Net Service Name Configuration, Select Protocols page, select TCP and
click Next.
6) On the Net Service Name Configuration, TCP/IP Protocol page, enter your
complete host name, for example, <yourservername>, or localhost, accept
“Use the standard port number of 1521,” and click Next.
7) On the Net Service Name Configuration, Test page, select “No, do not test” (the
pluggable database is not yet opened) and click Next.
8) On the Net Service Name Configuration, Net Service Name page, accept pdb2_2
as Net Service Name and click Next.
9) On the Net Service Name Configuration, Another Net Service Name page, select
No, and Next.
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
b
lo den
g
@ Stu
o
f
is
(ASin SYSDBA
h
$ sqlplus sys/oracle_4U@pdb2_2
t
y
og use
l
o
hn se to
Connected to:
c
e
n
T
e
Oracle Database
12c Enterprise
Edition Release 12.1.0.0.2 n
c
i
o
l
i
t
64bit Production
e
a
bl
rmPartitioning,
a
Withfo
the
OLAP, Advanced Analytics and Real
r
eTesting options
f
n
I
s
Application
al -tran
b
o
Gl nSQL>
on
d.
Check the open mode of the PDBs.
SQL> CONNECT / AS SYSDBA
Connected.
NAME
-----------------------------PDB$SEED
PDB2_1
PDB2_2
OPEN_MODE
---------READ ONLY
READ WRITE
READ WRITE
Chapter 3 - Page 29
a
SQL>
5.
Connect to PDB2_2 as the SYSTEM user.
SQL> connect system/oracle_4U@PDB2_2
Connected.
SQL> show con_name
PDB2_2
SQL> EXIT
$
6.
List the data files created.
$ cd $ORACLE_BASE/oradata/cdb2/pdb2_2
$ ls -l
total 4
drwxr-x--- 3 oracle oinstall 4096 Feb 6 13:46 CDB2
$ cd CDB2
$ ls -l
total 4
drwxr-x--- 3 oracle oinstall 4096 Jun 29 21:26
C3A419D23D3F1DE5E043160200C04142
$ cd C3A419D23D3F1DE5E043160200C04142
$ ls –l
total 4
drwxr-x--- 2 oracle oinstall 4096 Jun 29 21:26 datafile
$ cd datafile
$ ls -l
total 809836
-rw-r----- 1 oracle oinstall 566239232 Jun 29 21:27
o1_mf_sysaux_7yw7d38o_.dbf
o1_mf_system_7yw7d38h_.dbf
o1_mf_temp_7yw7dg92_.dbf
$
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
b
lo den
g
@ Stu
o
f
(in this
y
og use
l
o
hn se to
c
e
T cen
n
o
li
ti
e
a
l
rm erab
o
f
In ansf
l
a
b
tr
Glo non-
Method with SQL Developer:
1. If you already created pdb2_2 with SQL*Plus and would like to test the creation with SQL
Developer, you first have to drop pdb2_2 to recreate it.
a.
Drop the pluggable database pdb2_2.
$ sqlplus / AS SYSDBA
Connected to:
Chapter 3 - Page 30
a
SQL> ALTER PLUGGABLE DATABASE pdb2_2 CLOSE IMMEDIATE;
SQL> DROP PLUGGABLE DATABASE pdb2_2 INCLUDING DATAFILES;
Pluggable database dropped.
SQL> EXIT
$
b.
Remove the directory.
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
b
$ . oraenv
lo den
g
@ Stu
o
f
is /u01/app/oracle
(in withthvalue
The Oracle base remains unchanged
y
og use
l
o
hn se to
c
e
n
$ mkdir pdb2_2 T
e
n
c
i
o
l
ti
$
a
le
b
m
r
a
3. Run SQL*Plus
fo andsfconnect
er to the root to set OMF directory to the pdb2_2 directory.
n
I
al$ sqlplus
an / AS SYSDBA
r
b
t
o
Gl non
Connected to:
$ rm -r $ORACLE_BASE/oradata/cdb2/pdb2_2
$
SQL> alter system set db_create_file_dest =
'/u01/app/oracle/oradata/cdb2/pdb2_2' scope=both;
System altered.
SQL> EXIT
$
Chapter 3 - Page 31
a
4.
Launch SQL Developer.
$ cd $ORACLE_HOME/sqldeveloper
$ ./sqldeveloper.sh
$
5.
Create a connection as SYS in root cdb2.
6.
Open a connection as SYS in cdb2.
a. Choose the View option.
b. Click Connections.
c. Click + in the left Connections pane to add a new connection.
d. Fill the different fields as follows: be sure to change the host name and port number to
your assigned host name and port number.
Choices or Values
Connection Name
cdb2_root_SYS
Username
sys
Password
oracle_4U
Connection Type
TNS
s
) ha
om ฺ
c
ฺ
ch ide
e
t
SYSDBA
Role
i
l- t Gu
a
b
cdb2
Network Alias
lo den
g
@ Stu
o
f
(in this
y
og use
l
o
hn se to
c
e
T cen
n
o
li
ti
e
a
l
rm erab
o
f
In ansf
l
a
b
tr
Glo non-
e.
f.
g.
Click Test.
If the status is Success, click Save.
Click Connect.
Chapter 3 - Page 32
a
7.
To manage the CDB and its PDBs:
a. Choose the View option.
b. Click DBA.
c. Click + in the left Connections pane to view an existing connection.
d. From the list of existing connections, choose the one you just created.
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
b
lo den
g
@ Stu
o
f
(in this
y
og use
l
o
hn se to
c
e
T cen
n
o
li
ti
e
a
l
rm erab
o
f
In ansf
l
a
b
tr
Glo none.
f.
Click OK.
Click the sign + in front of the name of the cdb2_root_SYS connection to expand the
folder. Then click the sign + in front of “Container Database”. The list of containers in
the CDB appears.
Chapter 3 - Page 33
a
8.
Right-click the pluggable database pdb2_1 to show possible actions.
Choose Modify State to set it in READ ONLY open mode before cloning.
a. First close.
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
b
lo den
g
@ Stu
o
f
(in this
y
og use
l
b. Click Apply.
o
hn se to
c
c. Choose Modify State again.
e
n
T
e
d. Set the State Option
to READicONLY.
n
o
l
ti
a
le
b
m
r
a
fo sfer
n
I
al -tran
b
o
Gl non
Chapter 3 - Page 34
a
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
b
e. Click Apply then OK.
lo den
g
tu Database….
@CloneSPluggable
9. Right-click the pluggable database pdb2_1 and choose
o
f
(in this
a. Fill the different fields as follows.
y
og useChoices or Values
l
o
to
hn spdb2_2
c
e
Database Name
e
T cen
n
o
pdb2_1
li
Source PDB
ti
e
a
l
rm erab
None
File Name o
Conversions
f
f
n
l I Conversions
ns kept to None means that it uses the OMF target destination
File
Name
a
a
r
b
t
- DB_CREATE_FILE_DEST parameter.
in
Glodeclared
non
Chapter 3 - Page 35
a
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
b
glo tuden
b. You can view the SQL statement before applying.@
nfo this S
i
(
ogy use
l
o
hn se to
c
e
T cen
n
o
li
ti
e
a
l
rm erab
o
f
In ansf
l
a
b
tr
Glo non-
c.
Click Apply then OK. The new pdb2_2 appears in the list of PDBs in cdb2.
d.
Open pdb2_2.
Chapter 3 - Page 36
a
1)
Open pdb2_2 in READ WRITE mode. Right click pdb2_2 and click Modify State.
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
b
lo den
g
@ Stu
o
2) Click Apply, then OK.
f
is and click Modify State. Click
(inclick pdb2_1
h
t
e. Open pdb2_1 in READ WRITE mode.gRight
y
se
o
l
Apply , then OK.
u
o
hn se to
10. Leave SQL Developer.
c
e
T cen
a. Click File.
n
o
li
ti
e
b. Then click exit.
a
l
rm erab
o
f
In ansf
l
a
b
tr
Glo non-
Chapter 3 - Page 37
a
Practice 3-5: Plugging a Non-CDB into a CDB
Overview
In this practice, you will plug the non-CDB orcl2 into the CDB cdb2. You will not use
Export/Import DataPump, which can be a possible method, but the method with DBMS_PDB
package. This package executed in the non-CDB orcl2 generates an XML file describing the
tablespaces and data files of non-CDB orcl2. The XML file is then used when creating
pdb_orcl2 in cdb2.
Tasks
1.
Use DBMS_PDB.DESCRIBE to “unplug” non-CDB orcl2.
$ . oraenv
ORACLE_SID = [cdb2] ? orcl2
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
b
lo den
g
@ Stu
o
Fixed Size
2274000
bytes
f
is
(in bytes
h
t
Variable Size
973081904
y
g use
o687865856
l
Database Buffers
bytes
o
n
o
t
h
Redo Buffers
ec ense7000064 bytes
T
Database mounted.
n
o
lic
i
t
e
a
l
SQL>
b
rm database
a
r
o
SQL>
alter
open read only;
f
e
n nsf
I
l
baDatabase
tra altered.
o
l
n
G no
SQL> exec dbms_pdb.describe
SQL> startup mount
('/u01/app/oracle/oradata/orcl2/xmlorcl2.xml')
PL/SQL procedure successfully completed.
SQL> shutdown immediate
Database closed.
SQL> EXIT
$
Chapter 3 - Page 38
a
2.
Create a new PDB pdb_orcl2 to plug non-CDB orcl2 into cdb2 using the XML file
generated.
You will have to remove the temp file because the creation cannot complete until it is
removed to create it.
$ . oraenv
ORACLE_SID = [orcl2] ? cdb2
The Oracle base for
/u01/app/oracle
Connected to:
Testing options
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
b
lo den
g
@ Stu
o
f
(in this
y
og use
l
o
hn se to
c
e
T cen
n
o
li
ti
e
a
l
SQL>!rmm
/u01/app/oracle/oradata/orcl2/temp01.dbf
b
r
a
r
o
f
e
In ansf
l
a
SQL>
b n-tr
Glo nSQL>
o create pluggable database PDB_ORCL2 using
'/u01/app/oracle/oradata/orcl2/xmlorcl2.xml' NOCOPY;
SQL> create pluggable database PDB_ORCL2 using
'/u01/app/oracle/oradata/orcl2/xmlorcl2.xml' NOCOPY;
create pluggable database PDB_ORCL2 using 'xmlorcl2' NOCOPY
*
ERROR at line 1:
ORA-01119: error in creating database file
'/u01/app/oracle/oradata/orcl2/temp01.dbf'
ORA-27038: created file already exists
Additional information: 1
SQL> EXIT
$
Chapter 3 - Page 39
a
3.
To complete the operation, you have to convert the plugged non-CDB to a proper PDB by
deleting unnecessary metadata from PDB SYSTEM tablespace.
For this purpose, you execute the $ORACLE_HOME/rdbms/admin/noncdb_to_pdb.sql
script whilst connected to the PDB.
a. Connect to pdb2_2 as SYSDBA.
1)
Use netca to add the PDB_ORCL2 net service name for pdb_orcl2 pluggable
database of cdb2 in the tnsnames.ora file.
$ netca
3)
click Next.
4) On the Net Service Name Configuration, Service Name page, enter pdb_orcl2
as Service Name and click Next.
5) On the Net Service Name Configuration, Select Protocols page, select TCP and
click Next.
6) On the Net Service Name Configuration, TCP/IP Protocol page, enter your
complete host name, for example, <yourservername>, or localhost, accept
“Use the standard port number of 1521,” and click Next.
7) On the Net Service Name Configuration, Test page, select “No, do not test” (the
8) On the Net Service Name Configuration, Net Service Name page, accept
pdb_orcl2 as Net Service Name and click Next.
No, and Next.
Now connect to pdb_orcl2 using the net service name.
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
b
lo den
g
@ Stu
o
f
(in this
y
og use
l
o
hn se to
c
e
T cen
n
o
li
b.
ti
e
a
l
b
$ sqlplus
as sysdba
rm sys/oracle_4U@pdb_orcl2
a
r
o
f
e
f
n
l I rans
a
b
to:
n-t
Glo nConnected
o
SQL>
c.
Execute the script. Expect around 35 minutes to complete.
SQL>
SQL>
SQL>
SQL>
SQL>
SQL>
SQL>
@$ORACLE_HOME/rdbms/admin/noncdb_to_pdb.sql
SET SERVEROUTPUT ON
SET FEEDBACK 1
SET NUMWIDTH 10
SET LINESIZE 80
SET TRIMSPOOL ON
SET TAB OFF
Chapter 3 - Page 40
a
SQL> SET PAGESIZE 100
SQL>
SQL> WHENEVER SQLERROR EXIT;
SQL>
SQL> DOC
DOC>############################################################
###########
DOC>############################################################
###########
DOC>
The following statement will cause an "ORA-01722: invalid
number"
DOC>
error if we're not in a PDB.
DOC>############################################################
###########
DOC>############################################################
###########
DOC>#
SQL>
SQL> VARIABLE pdbname VARCHAR2(128)
SQL> BEGIN
2
SELECT sys_context('USERENV', 'CON_NAME')
3
INTO :pdbname
4
FROM dual
5
WHERE sys_context('USERENV', 'CON_NAME') <> 'CDB$ROOT';
6 END;
7 /
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
b
lo den
g
@ Stu
o
f
(in this
y
og use
l
o
hn se to
c
e
T cen
n
o
li
ti
e
a
l
bsuccessfully completed.
rm
a
PL/SQL
procedure
r
o
f
e
In ansf
l
a
b
tr
Glo n…on-
SQL>
SQL> Rem
================================================================
=
SQL> Rem Run component validation procedure
SQL> Rem
================================================================
=
SQL>
SQL> EXECUTE dbms_registry_sys.validate_components;
...Database user "SYS", database schema "APEX_040200", user#
"98" 10:21:02
Chapter 3 - Page 41
a
...Compiled 0 out of 2998 objects considered, 0 failed
compilation 10:21:03
...263 packages
...255 package bodies
...453 tables
...11 functions
...16 procedures
...3 sequences
...458 triggers
...1322 indexes
...207 views
...0 libraries
...6 types
...0 type bodies
...0 operators
...0 index types
...Begin key object existence check 10:21:03
...Completed key object existence check 10:21:03
...Setting DBMS Registry 10:21:03
...Setting DBMS Registry Complete 10:21:03
...Exiting validate 10:21:03
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
b
lo den
g
@ Stu
o
f
(in this
y
PL/SQL procedure successfully
se
og completed.
l
u
o
hn se to
c
e
SQL> SET serveroutput
n
T coff
e
n
i
o
l
SQL>
ti
a
le
b
m
SQL> Rem
r
a
fo sfer
================================================================
n
I
al= -tran
b
o
Gl nSQL>
on Rem END utlrp.sql
SQL> Rem
================================================================
=
SQL>
…
SQL> alter pluggable database "&pdbname" close;
SQL>
SQL> -- leave the PDB in the same state it was when we started
SQL> BEGIN
Chapter 3 - Page 42
a
2
3
4
5
6
7
8
9
10
11
execute immediate '&open_sql &restricted_state';
EXCEPTION
WHEN OTHERS THEN
BEGIN
IF (sqlcode <> -900) THEN
RAISE;
END IF;
END;
END;
/
SQL>
SQL> alter session set container="&pdbname";
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
SQL>
l- t Gu
a
b
SQL> WHENEVER SQLERROR CONTINUE;
lo den
g
@ Stu
SQL>
o
f
(in this
SQL>
y
og PDB.use
l
d. Quit the session after opening the
new
o
n e topdb_orcl2 open;
hdatabase
SQL> alter pluggable
c
e
T cens
n
li
Pluggable database
tio lealtered.
a
rm erab
o
f
In EXIT
sf
SQL>
l
n
a
a
b $ n-tr
G4.loConnect
no to PDB_ORCL2.
Session altered.
$ sqlplus sys/oracle_4U@localhost:1521/PDB_ORCL2 as SYSDBA
Connected to:
SQL>
Chapter 3 - Page 43
a
5.
Verify that the application data is in the PDB pdb_orcl2:
SQL> select count(empno) from scott.emp;
COUNT(EMPNO)
-----------14
SQL> EXIT
$
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
b
lo den
g
@ Stu
o
f
(in this
y
og use
l
o
hn se to
c
e
T cen
n
o
li
ti
e
a
l
rm erab
o
f
In ansf
l
a
b
tr
Glo non-
Chapter 3 - Page 44
a
Practice 3-6: Merging All PDBs of CDBs into a Single CDB
Overview
In this practice you merge all PDBs of cdb1 into a single CDB, cdb2.
1.
Merge all PDBs of cdb1 into cdb2.
2.
Drop cdb1.
Assumptions
The CDB cdb2 exists. The cdb2 creation has completed successfully in Practice 3-1.
Tasks
1.
Connect to the multitenant container database cdb1 to unplug all PDBs.
a.
Connect to cdb1 root as a common user with ALTER PLUGGABLE DATABASE
privilege to unplug pdb1_1. If the pdb1_1 is still in READ WRITE mode, close the
PDB.
s
) ha
$ . oraenv
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
b
lo den
g
@ Stu
o
f
Connected to:
in thRelease
is
(Edition
y
Oracle Database 12c Enterprise
12.1.0.0.2 og use
l
64bit Production
o
to Mining and Real Application
hnOLAP,
With the Partitioning,
Data
c
e
e
s
n
Testing options T
e
n
c
i
o
l
ti
a
le
b
m
r
a
SQL> o
select
name,
r open_mode from v$pdbs;
f
e
f
n
l I rans
a
b
OPEN_MODE
n-t
Glo nNAME
o
------------------------------ ---------PDB$SEED
PDB1_1
READ ONLY
READ WRITE
SQL> alter pluggable database PDB1_1 unplug into
'xmlfilePDB1_1.xml';
alter pluggable database PDB1_1 unplug into 'xmlfilePDB1_1'
*
ERROR at line 1:
ORA-65025: Pluggable database PDB1_1 is not closed on all
instances.
SQL> alter pluggable database PDB1_1 close immediate;
Chapter 3 - Page 45
a
SQL> alter pluggable database PDB1_1 unplug into
'xmlfilePDB1_1.xml';
SQL> col PDB_NAME format A20
SQL> select PDB_NAME, STATUS from CDB_PDBS
where PDB_NAME='PDB1_1';
PDB_NAME
STATUS
-------------------- ------------PDB1_1
UNPLUGGED
SQL> drop pluggable database PDB1_1 KEEP DATAFILES;
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
SQL> EXIT
b
lo den
g
$
@ Stu
o
f
b. Before plugging pdb1_1 into cdb2, you can
ischeck whether the unplugged
(inoptionally
h
t
y
pdb1_1 is compatible with cdb2 with
gDBMS_PDB.CHECK_PLUG_COMPATIBILITY
se with CREATE PLUGGABLE
laocommon
u
o
function. Connect to cdb2 rootnas
user
hpdb1_1.se to
c
DATABASE privilege to plug
e
Tcode: cen
n
Use the following PL/SQL
o
li
ti
e
l
DECLAREma
b
r BOOLEAN
a
r
o
f
e
compat
:= FALSE;
n nsf
I
l
ba BEGIN
tra
o
l
n
G nocompat := DBMS_PDB.CHECK_PLUG_COMPATIBILITY(
pdb_descr_file =>
'/u01/app/oracle/product/12.1.0/dbhome_1/dbs/xmlfilePDB1_1.xml',
pdb_name => 'pdb1_1');
if compat then
DBMS_OUTPUT.PUT_LINE('Is pluggable compatible? YES');
else DBMS_OUTPUT.PUT_LINE('Is pluggable compatible? NO');
end if;
end;
/
$ . oraenv
Chapter 3 - Page 46
a
Connected.
SQL> SET SERVEROUTPUT ON
SQL> DECLARE
2 compat BOOLEAN := FALSE;
3 BEGIN
4
compat := DBMS_PDB.CHECK_PLUG_COMPATIBILITY(
5 pdb_descr_file =>
'/u01/app/oracle/product/12.1.0/dbhome_1/dbs/xmlfilePDB1_1.xml',
pdb_name => 'pdb1_1');
6 if compat then
7
DBMS_OUTPUT.PUT_LINE('Is pluggable compatible? YES');
8 else DBMS_OUTPUT.PUT_LINE('Is pluggable compatible? NO');
9 end if;
10 end;
11 /
Is pluggable compatible? NO
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
PL/SQL procedure successfully completed. oba
l
en
g
d
u
o@ is St
f
SQL>
n
i
(
th with step d.
y
g
e
c. If the value returned is YES, you can
immediately
proceed
lothe PDB_PLUG_IN_VIOLATIONS
us
o
If the value returned is NO, examine
view to see why
n
o
t
h
c
e
it is not compatible.
e ens
T
n
c
SQL> select imessage,
from pdb_plug_in_violations
o le liaction
t
a
where
b
rm name='PDB1_1';
a
r
o
f
e
In ansf
l
a
MESSAGE
b n-tr
Glo n---------------------------------------------------------------o
ACTION
---------------------------------------------------------------Parameter sga_target mismatch: Previous value 503316480. CDB
value 5033164800
Change the parameter in PDB or the CDB
Parameter pga_aggregate_target mismatch: Previous value
167772160. CDB value 1677721600
Change the parameter in PDB or the CDB
SQL>
Chapter 3 - Page 47
a
The message refers to a parameter related to PGA. The parameter will not have any
impact if you create the PDB. You can proceed with the creation of the PDB.
d. Plug pdb1_1 into cdb2.
SQL> create pluggable database pdb1_1 using 'xmlfilePDB1_1.xml'
NOCOPY;
SQL>
Notice that you use the clause NOCOPY because the cdb2 pdb1_1 files are located in the
right place. Otherwise, you should have described the target destination to move the files
from the source to the new destination.
e. Open pdb1_1.
s
) ha
m
o
c
ฺ
SQL>
ch ideฺ
e
t
i
f. Check that the pdb1_1 is in the PDBs list in cdb2.
l- t Gu
a
b
lo den
g
@ Stu
o
f
in this
(OPEN_MODE
NAME
y
se
og --------------------------------------l
u
o
hn se toREAD ONLY
PDB$SEED
c
e
T cen
PDB2_1
READ WRITE
n
i
o
l
i
t
PDB2_2
READ WRITE
a
le
b
m
r
a
PDB_ORCL2
READ WRITE
fo sfer
n
I
PDB1_1
READ WRITE
l
n
a
a
r
b
t
Glo nSQL>
on- EXIT
$
2.
After all PDBs are unplugged from cdb1 (in case you had created other PDBs) and
plugged into cdb2, you can drop the multitenant container database cdb1 with DBCA or
SQL commands.
$ . oraenv
Connected.
Database closed.
Chapter 3 - Page 48
a
SQL> startup mount restrict
Total System Global Area
Fixed Size
Variable Size
Database Buffers
Redo Buffers
Database mounted.
722366464
2276928
213909952
503316480
2863104
bytes
bytes
bytes
bytes
bytes
SQL> DROP DATABASE;
Database dropped.
s
) ha
om ฺ
c
ฺ
SQL> EXIT
ch ide
e
t
i
$
l- t Gu
a
b
lo den
Remove archived logs and backups if necessary.
g
@ Stu
o
f
(in this
y
og use
l
o
hn se to
c
e
T cen
n
o
li
ti
e
a
l
rm erab
o
f
In ansf
l
a
b
tr
Glo non-
Chapter 3 - Page 49
a
Practice 3-7: Dropping a PDB (optional)
Overview
In this practice, you drop the PDB pdb2_3 of cdb2 that you quickly create from the seed.
Tasks
Either use DBCA or SQL Developer or SQL commands.
The creation using SQL is described below.
$ . oraenv
$ mkdir pdb2_3
$
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
b
lo den
g
@ Stu
Connected to:
o
f
in thRelease
is
Oracle Database 12c Enterprise (Edition
12.1.0.0.2 y
g
e
64bit Production
lo Data
usMining and Real Application
o
n
OLAP,
o
t
Testing options
ech ense
T
n
o
lic
i
t
e
a
l
SQL> CREATE
PLUGGABLE
DATABASE pdb2_3 ADMIN USER pdb2_3_admin
b
m
r
a
r
o
fe BY oracle_4U ROLES=(CONNECT)
nf IDENTIFIED
I
s
l
n
FILE_NAME_CONVERT=('/u01/app/oracle/oradata/cdb2/pdbseed'
ba n-tra
o
l
,'/u01/app/oracle/oradata/cdb2/pdb2_3');
G no
2.
Run SQL*Plus and connect to the root with a user with CREATE PLUGGABLE DATABASE
privilege.
SQL>
Chapter 3 - Page 50
a
3.
SQL> col con_id format 999
SQL> select NAME, OPEN_MODE from V$PDBS;
NAME
-----------------------------PDB$SEED
PDB2_1
PDB2_2
PDB_ORCL2
PDB1_1
PDB2_3
OPEN_MODE
---------READ ONLY
READ WRITE
READ WRITE
READ WRITE
READ WRITE
MOUNTED
SQL>
4.
Open pdb2_3.
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
b
lo den
g
@ Stu
SQL>
o
f
n tPLUGGABLE
is
(iALTER
h
5. Still connected to cdb2 as a common user with
DATABASE privilege,
y
e
s
og in MOUNTED
you close pdb2_3 if the PDB is not o
already
mode.
l
u
n
o
t
h
database
PDB2_3
close immediate;
ec ense
T
lic
tion lealtered.
Pluggable adatabase
rm erab
o
f
In
sf
l
SQL> an
a
b n-tr
G6.loYoundrop
o the PDB pdb2_3 and the data files.
SQL> drop pluggable database PDB2_3 INCLUDING DATAFILES;
SQL> EXIT
$
Chapter 3 - Page 51
a
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
b
lo den
g
@ Stu
o
f
(in this
y
og use
l
o
hn se to
c
e
T cen
n
o
li
ti
e
a
l
rm erab
o
f
In ansf
l
a
b
tr
Glo non-
Chapter 3 - Page 52
a
s
) ha
om ฺ
c
ฺ
ch4: ide
e
t
i
l- t Gu
Managing a Multitenant
a
b
lo denand
g
Container
Database
@ Stu
o
f
Pluggable
n thiDatabases
s
i
(
y
ogChapterus4 e
l
o
hn se to
c
e
T cen
n
o
li
ti
e
a
l
rm erab
o
f
In ansf
l
a
b
tr
Glo non-
Practices for Lesson 4: Managing a Multitenant Container Database and Pluggable Databases
Chapter 4 - Page 1
a
Practices Overview
In this practice, you will perform startup and shutdown operations on CDBs, open and close
operations on PDBs, and connections to PDBs to display current context.
Assumptions
cdb2 is successfully created after Practice 3-1.
pdb2_1 is successfully created in cdb2 after completion of Practice 3-3.
pdb2_2 is successfully created in cdb2 after completion of Practice 3-4.
It is not necessary at this step to have successfully created pdb1_1 and pdb_orcl2.
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
b
lo den
g
@ Stu
o
f
(in this
y
og use
l
o
hn se to
c
e
T cen
n
o
li
ti
e
a
l
rm erab
o
f
In ansf
l
a
b
tr
Glo non-
Chapter 4 - Page 2
a
Practice 4-1: Shutdown and Startup of the CDB
Overview
In this practice you shut down cdb2 and start up cdb2.
Tasks
1.
Connect to the multitenant container database cdb2 to shut it down.
a.
Connect to the CDB as a user with SYSDBA privilege.
$ . oraenv
Connected to:
Testing options
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
b
lo den
g
SQL> select name, cdb, con_id from v$database;
@ Stu
o
f
NAME
CDB
CON_ID
(in this
y
--------- --- ---------og use
l
o
CDB2
YES
0
hn se to
c
e
T cen
n
SQL>
o
li
ti
e
a
l
b
b. Shut down
rmthe CDB.
a
r
o
f
e
SQL>
In shutdown
sf immediate
l
n
a
a
b Database
tr closed.
Glo nDatabase
on- dismounted.
SQL> EXIT
$
c.
Explore the background processes.
$ ps -ef|grep cdb2
oracle
22991 2686
$
0 13:56 pts/2
00:00:00 grep cdb2
Chapter 4 - Page 3
a
2.
Connect to the multitenant container database cdb2 and start it up.
SQL> startup
Fixed Size
2248280 bytes
Variable Size
343933352 bytes
Database Buffers
717225984 bytes
Redo Buffers
5529600 bytes
Database mounted.
Database opened.
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
b
lo den
g
@ Stu
o
f
(in this
SQL> EXIT
y
og use
$
l
o
hn se to
3. Explore the background processes.
c
e
T cen
$ ps -ef|grep n
cdb2
o
li 0 03:11 ?
ti
e
a
l
oracle
26393
1
b
m
r
a
r
o
oracle
1 0 03:11 ?
00:00:00 ora_psp0_cdb2
fe
nf n26395
I
s
l
oracle
26397
1
0
03:11
?
00:00:00 ora_vktm_cdb2
a -tra
b
o
26403
1 0 03:11 ?
00:00:00 ora_gen0_cdb2
Gl noracle
on
oracle
26405
1 0 03:11 ?
00:00:00 ora_mman_cdb2
NAME
CDB
CON_ID
--------- --- ---------CDB2
YES
0
oracle
oracle
oracle
oracle
oracle
oracle
oracle
oracle
oracle
oracle
oracle
oracle
26409
26411
26413
26415
26417
26419
26421
26423
26425
26427
26429
26431
1
1
1
1
1
1
1
1
1
1
1
1
0
0
0
0
0
0
0
0
0
0
0
0
03:11
03:11
03:11
03:11
03:11
03:11
03:11
03:11
03:11
03:11
03:11
03:11
?
?
?
?
?
?
?
?
?
?
?
?
00:00:00
00:00:00
00:00:00
00:00:00
00:00:00
00:00:00
00:00:00
00:00:00
00:00:00
00:00:00
00:00:00
00:00:00
ora_diag_cdb2
ora_ofsd_cdb2
ora_dbrm_cdb2
ora_dia0_cdb2
ora_dbw0_cdb2
ora_lgwr_cdb2
ora_ckpt_cdb2
ora_lg00_cdb2
ora_lg01_cdb2
ora_smon_cdb2
ora_reco_cdb2
ora_lreg_cdb2
Chapter 4 - Page 4
a
oracle
oracle
oracle
oracle
oracle
oracle
oracle
oracle
oracle
oracle
oracle
oracle
oracle
oracle
oracle
oracle
oracle
oracle
oracle
oracle
oracle
oracle
oracle
$
26433
26435
26437
26439
26451
26453
26455
26457
26459
26461
26465
26467
26469
26471
26473
26475
26477
26479
26505
26507
26509
26513
26549
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
9398
1
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
1
0
03:11
03:11
03:11
03:11
03:11
03:11
03:11
03:11
03:11
03:11
03:12
03:12
03:12
03:12
03:12
03:12
03:12
03:12
03:12
03:12
03:12
03:12
03:12
?
?
?
?
?
?
?
?
?
?
?
?
?
?
?
?
?
?
?
?
?
?
pts/0
00:00:00
00:00:00
00:00:00
00:00:00
00:00:00
00:00:00
00:00:00
00:00:00
00:00:00
00:00:00
00:00:00
00:00:00
00:00:00
00:00:00
00:00:00
00:00:00
00:00:00
00:00:00
00:00:00
00:00:00
00:00:00
00:00:00
00:00:00
ora_mmon_cdb2
ora_mmnl_cdb2
ora_d000_cdb2
ora_s000_cdb2
ora_tmon_cdb2
ora_tt00_cdb2
ora_smco_cdb2
ora_fbda_cdb2
ora_aqpc_cdb2
ora_w000_cdb2
ora_p000_cdb2
ora_p001_cdb2
ora_p002_cdb2
ora_p003_cdb2
ora_p004_cdb2
ora_p005_cdb2
ora_p006_cdb2
ora_p007_cdb2
ora_qm02_cdb2
ora_q001_cdb2
ora_q002_cdb2
ora_cjq0_cdb2
grep cdb2
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
b
lo den
g
@ Stu
o
f
(in this
y
og use
l
o
hn se to
c
e
T cen
n
o
li
ti
e
a
l
rm erab
o
f
In ansf
l
a
b
tr
Glo non-
Chapter 4 - Page 5
a
4.
Explore the PDBs.
Connected to:
Testing options
CON_ID NAME
OPEN_MODE
---------- -------------------------------- ---------2 PDB$SEED
READ ONLY
3 PDB2_1
MOUNTED
4 PDB2_2
MOUNTED
5 PDB_ORCL2
MOUNTED
6 PDB1_1
MOUNTED
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
SQL>
l- t Gu
a
b
5. Open all PDBs.
lo den
g
@ Stu
SQL> alter pluggable database all fopen;
o
n this
Pluggable database altered. y (i
og use
l
o
to from v$pdbs;
hn sOPEN_MODE
SQL> select CON_ID,cNAME,
e
e
T cen
n
o
li
i
tNAME
CON_ID
OPEN_MODE
e
a
l
b
m
r
a
------------------fo sf-----------------------------er
n
I
2
PDB$SEED
READ ONLY
l
n
a
a
r
b
t
READ WRITE
Glo non- 34 PDB2_1
PDB2_2
READ WRITE
5 PDB_ORCL2
6 PDB1_1
READ WRITE
READ WRITE
SQL>
Chapter 4 - Page 6
a
6.
Connect to any of the PDBs in your cdb2, except PDB$SEED.
SQL> connect sys/oracle_4U@PDB2_1 AS SYSDBA
Connected.
CON_ID NAME
OPEN_MODE
---------- ------------------------------ ---------3 PDB2_1
READ WRITE
SQL>
7.
Display the context of the PDB you are connected to.
SQL> show con_name
CON_NAME
-----------------------------PDB2_1
s
) ha
om ฺ
c
ฺ
ch ide
e
SQL>
t
i
l- t Gu
a
b
8. Connect to another PDB left in your cdb2, except PDB$SEED.
lo den
g
SQL> connect sys/oracle_4U@PDB2_2 AS @
SYSDBA tu
o
f
n this S
i
Connected.
(
gy usefrom v$pdbs;
SQL> select CON_ID, NAME,lo
OPEN_MODE
o
hn se to
c
e
CON_ID NAME T
OPEN_MODE
n
e
n
c
i
o
l
i
---------- t--------------------------------------e
a
l
b
m
READ WRITE
r 4 PDB2_2
ra
o
f
e
f
n
l I rans
a
b
SQL>-t
G9.loDisplay
nonthe context of the PDB you are connected to.
SQL> show con_name
CON_NAME
-----------------------------PDB2_2
SQL> EXIT
$
Chapter 4 - Page 7
a
Practice 4-2: Closing and Opening a PDB
Overview
In this practice you close PDBs and open PDBs, and create triggers to automatically open PDBs
after CDB startup.
Tasks
1.
Connect to the multitenant container database cdb2 to shut it down.
a.
Connect to cdb2 as a user with SYSDBA privilege.
$ . oraenv
s
) ha
Connected to:
Testing options
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
b
lo den
g
@ Stu
o
f
SQL> select name, cdb, con_id from
v$database;
(in this
y
NAME
CDB
CON_ID
og use
l
o
--------- --- ---------hn0 se to
c
CDB2
YES
e
T cen
n
o
li
ti
e
a
l
SQL>
rm erab
o
f
b. Shut
cdb2.
In down
sf
l
n
a
a
r
b SQL>
immediate
tshutdown
Glo nDatabase
on- closed.
SQL>
c.
Start up cdb2.
SQL> startup
Fixed Size
2248280 bytes
Variable Size
343933352 bytes
Database Buffers
717225984 bytes
Redo Buffers
5529600 bytes
Chapter 4 - Page 8
a
Database mounted.
Database opened.
SQL>
d.
Notice that the PDBs are all in MOUNTED open mode.
CON_ID NAME
OPEN_MODE
---------- -------------------------------- ---------2 PDB$SEED
READ ONLY
3 PDB2_1
MOUNTED
4 PDB2_2
MOUNTED
5 PDB_ORCL2
MOUNTED
6 PDB1_1
MOUNTED
SQL>
s
) ha
om ฺ
c
ฺ
SQL> alter pluggable database all open;
ch ide
e
t
i
l- t Gu
a
b
lo den
g
@ Stu
o
f
SQL>
(in this
y
og use
3. Close PDB2_1.
l
o
to
hn ssession.
a. Start a DML transaction incanother
e
e
T cen
$ . oraenv
n
o
l?i cdb2
t=i [cdb2]
ORACLE_SID
e
a
l
bremains unchanged with value /u01/app/oracle
rm base
a
r
The fOracle
o
e
f
n nssys/oracle_4U@pdb2_1
l
$ Isqlplus
as sysdba
a
a
r
b
t
o
Gl nConnected
on
to:
2.
Open all PDBs manually.
Testing options
SQL> create table system.mytab (c number);
Table created.
SQL> insert into system.mytab values (1);
1 row created.
SQL> commit;
Chapter 4 - Page 9
a
Commit complete.
SQL> exit
$
b.
In the first session, close PDB2_1 in IMMEDIATE mode.
SQL> alter pluggable database pdb2_1 close immediate;
CON_ID NAME
OPEN_MODE
---------- ------------------------------ ---------2 PDB$SEED
READ ONLY
3 PDB2_1
MOUNTED
4 PDB2_2
READ WRITE
5 PDB_ORCL2
READ WRITE
6 PDB1_1
READ WRITE
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
SQL>
a
b
lo den
c. Try to connect as a user of PDB2_1.
g
@ Stu
o
f
SQL> connect system/oracle_4U@pdb2_1
(in this
y
ERROR:
og uorseshutdown in progress
l
o
ORA-01033: ORACLE initialization
hn se to
c
Process ID: 0
e
T cen 0
n
Session ID: 0
Seriallinumber:
o
ti
a
le
b
m
r
a
fo sfer
n
I
alWarning:
anYou are no longer connected to ORACLE.
r
b
t
o
Gl non
SQL>
4.
Open pdb2_1.
Connected.
SQL> alter pluggable database PDB2_1 open;
SQL>
Reconnect to pdb2_1 and select data from SYSTEM.MYTAB table.
SQL> connect system/oracle_4U@PDB2_1
Connected.
Chapter 4 - Page 10
a
SQL> select * from system.mytab;
C
---------1
SQL>
5.
Shut down the multitenant container database cdb2 to open and close PDBs with different
clauses.
Connected.
NAME
CDB
CON_ID
--------- --- ---------CDB2
YES
0
s
) ha
om ฺ
c
ฺ
ch ide
e
t
SQL>
i
l- t Gu
a
b
a. Shut down CDB2.
lo den
g
@ Stu
o
f
Database closed.
(in this
y
og use
l
o
n e to
ORACLE instance shut
hdown.
c
e
T cens
SQL>
n
i
lmode.
tinioNOMOUNT
b. Start up cdb2
e
a
l
b
rm enomount
a
r
SQL>fo
startup
In instance
sf started.
l
n
ORACLEra
a
b
t
Glo nonTotal System Global Area 1068937216 bytes
Fixed Size
Variable Size
Database Buffers
Redo Buffers
2248280
343933352
717225984
5529600
bytes
bytes
bytes
bytes
No rows selected.
SQL>
Chapter 4 - Page 11
a
c.
Mount cdb2.
SQL> alter database mount;
Database altered.
SQL>
CON_ID NAME
OPEN_MODE
---------- -------------------------------- ---------2 PDB$SEED
MOUNTED
3 PDB2_1
MOUNTED
4 PDB2_2
MOUNTED
5 PDB_ORCL2
MOUNTED
6 PDB1_1
MOUNTED
SQL>
s
) ha
om ฺ
c
ฺ
ch ide
SQL> alter database open;
e
t
i
l- t Gu
a
Database altered.
b
lo den
g
@ Stu
o
f
SQL> select CON_ID, NAME, OPEN_MODE
isv$pdbs;
(in from
h
t
y
og use
l
o
CON_ID NAME
OPEN_MODE
n e to
h
c
---------- ----------------------------------------Te cens
n
2 PDB$SEED
READ ONLY
tio le li
a
b
MOUNTED
rm3 PDB2_1
a
r
o
f
e
f
MOUNTED
In an4sPDB2_2
l
a
MOUNTED
b
tr 5 PDB_ORCL2
Glo non- 6 PDB1_1
MOUNTED
d.
Open cdb2.
SQL>
Chapter 4 - Page 12
a
e.
Open all PDBs except PDB2_2.
SQL> alter pluggable database all except pdb2_2 open;
CON_ID NAME
OPEN_MODE
---------- -------------------------------- ---------2 PDB$SEED
READ ONLY
3 PDB2_1
READ WRITE
4 PDB2_2
MOUNTED
5 PDB_ORCL2
READ WRITE
6 PDB1_1
READ WRITE
SQL>
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
b
lo den
g
@ Stu
o
f
(in this
y
og use
l
o
hn se to
c
e
T cen
n
o
li
ti
e
a
l
rm erab
o
f
In ansf
l
a
b
tr
Glo non-
Chapter 4 - Page 13
a
Practice 4-3: Creating After Startup Trigger to Open All PDBs
Overview
In this practice, you create AFTER STARTUP trigger to open all PDBs of a CDB.
Tasks
1.
Create a trigger in cdb2 to open all PDBs automatically after starting up cdb2.
a. Create the trigger.
CREATE TRIGGER open_all_PDBs
AFTER STARTUP ON DATABASE
begin
execute immediate 'alter pluggable database all open';
end open_all_PDBs;
/
SQL>
2
3
4
5
6
CREATE TRIGGER Open_All_PDBs
after startup on database
begin
execute immediate 'alter pluggable database ALL open';
end Open_All_PDBs;
/
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
b
lo den
g
@ Stu
o
f
Trigger created.
(in this
y
og use
l
o
SQL>
hn se to
c
e
T cen
b. Shut down cdb2.
n
o
li
ti immediate
SQL> shutdown
e
a
l
b
rmclosed.
a
r
Database
o
f
e
In andismounted.
sf
l
Database
a
b n-tr instance shut down.
Glo nORACLE
o
SQL>
c.
Start up cdb2.
SQL> startup
Fixed Size
2248280 bytes
Variable Size
343933352 bytes
Database Buffers
717225984 bytes
Redo Buffers
5529600 bytes
Database mounted.
Database opened.
SQL>
Chapter 4 - Page 14
a
d.
Notice that the PDBs are all in READ WRITE open mode. Then disconnect.
CON_ID NAME
OPEN_MODE
---------- -------------------------------- ---------2 PDB$SEED
READ ONLY
3 PDB2_1
READ WRITE
4 PDB2_2
READ WRITE
5 PDB_ORCL2
READ WRITE
6 PDB1_1
READ WRITE
SQL>
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
b
lo den
g
@ Stu
o
f
(in this
y
og use
l
o
hn se to
c
e
T cen
n
o
li
ti
e
a
l
rm erab
o
f
In ansf
l
a
b
tr
Glo non-
Chapter 4 - Page 15
a
Practice 4-4: Changing PDBs’ Open Mode
Overview
In this practice you will change the open mode of PDBs for specific operations.
Assumptions
If the trigger could not be created successfully, execute the following catchup script:
$ cd /home/oracle/recovery/catchup_04_03
$ ./cr_trig.sh
$
Tasks
Rename the global database name for pdb2_1 to pdb2 in cdb2. For this purpose, you must
open the PDB in RESTRICTED mode.
1.
Connect to pdb2_1.
s
) ha
SQL> CONNECT sys/oracle_4U@pdb2_1 as sysdba
Connected.
SQL>
om ฺ
c
ฺ
ch ide
e
t
i
2. Change the global database name for pdb2_1 to pdb2.
l- t Gu
a
b
SQL> alter pluggable database RENAME GLOBAL_NAME
lo deTOn pdb2;
g
tu pdb2
@ Sto
alter pluggable database RENAME global_name
o
f
(in this
*
y
g
e
ERROR at line 1:
lo o us
o
n
tnot in a restricted mode
ORA-65045: pluggable
hdatabase
c
e
e
s
T cen
n
o
li
ti
SQL>
e
a
l
rm erab
3. Close pdb2_1.
o
f
In ansfpluggable database close immediate;
l
SQL> alter
a
b
tr
Glo nonPluggable database altered.
SQL>
4.
Open pdb2_1 in restricted mode.
SQL> alter pluggable database open restricted;
SQL>
SQL> select CON_ID, NAME, OPEN_MODE, RESTRICTED from v$pdbs;
CON_ID NAME
OPEN_MODE
Chapter 4 - Page 16
RES
a
---------- ------------------------------ ---------- --3 PDB2_1
READ WRITE YES
SQL>
5.
Change the global database name for pdb2_1 to pdb2.
SQL> alter pluggable database RENAME GLOBAL_NAME TO pdb2;
SQL>
CON_ID NAME
OPEN_MODE RES
---------- ------------------------------ ---------- --3 PDB2
READ WRITE YES
s
) ha
om ฺ
c
ฺ
ch ide
e
t
SQL>
i
l- t Gu
a
b
6. Open PDB2.
lo den
g
@ Stu
SQL> alter pluggable database closeoimmediate;
f
(in this
y
og use
l
o
hn se to
c
e
n open;
T database
e
n
c
i
o
l
ti
a
lealtered.
b
m
r
Pluggable
database
a
fo sfer
n
I
alSQL>-tran
b
o
n
G7.l Check
noPDB2
is in READ WRITE mode.
CON_ID NAME
OPEN_MODE RES
---------- ------------------------------ ---------- --3 PDB2
READ WRITE NO
SQL>
Chapter 4 - Page 17
a
Practice 4-5: Instance Parameter Changes: Impact on PDBs (optional)
Overview
In this practice you will discover the impact of instance parameter changes on PDBs.
Tasks
1.
In this example, you will use in cdb2 the instance parameter
OPTIMIZER_USE_SQL_PLAN_BASELINES because it is ISPDB_MODIFIABLE in
V$PARAMETER.
Connected.
SQL> select ISPDB_MODIFIABLE from v$parameter
2 where name='optimizer_use_sql_plan_baselines';
ISPDB
----TRUE
s
) ha
om ฺ
c
ฺ
ch ide
e
SQL>
t
i
l- t Gu
a
b
2. Check the current value of instance parameter OPTIMIZER_USE_SQL_PLAN_BASELINES.
lo den
g
SQL> show parameter optimizer_use_sql_plan_baselines
@ Stu
o
f
NAME
VALUE
is
(in TYPE
h
t
y
-----------------------------------og use ----------- --------l
o
optimizer_use_sql_plan_baselines
boolean
TRUE
hn se to
c
e
T cen
n
o
li
SQL> EXIT ti
e
a
l
$
rm erab
o
f
Into pdb2
sinfcdb2 and check the current value of the same instance parameter
3. Connect
l
n
a
a
b
OPTIMIZER_USE_SQL_PLAN_BASELINES.
-tr
Glo n1)onUse
netca to add the PDB2 net service name for pdb2 pluggable database of
$ netca
3)
click Next.
4) On the Net Service Name Configuration, Service Name page, enter pdb2 as
5)
6)
On the Net Service Name Configuration, Select Protocols page, select TCP and
click Next.
On the Net Service Name Configuration, TCP/IP Protocol page, enter your
complete host name, for example, <yourservername>.us.oracle.com, or
localhost, accept “Use the standard port number of 1521,” and click Next.
Chapter 4 - Page 18
a
7)
On the Net Service Name Configuration, Test page, select “No, do not test” (the
8) On the Net Service Name Configuration, Net Service Name page, accept pdb2 as
Net Service Name and click Next.
No, and Next.
12) Reload the listener with the new configuration:
$ lsnrctl reload
a.
If this is not sufficient, then restart the instance.
Connect to pdb2 in cdb2.
$ sqlplus sys/oracle_4U@pdb2 AS SYSDBA
Connected to:
Testing
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
b
lo den
g
tu VALUE
@
o
S
f
NAME
TYPE
is
(in ----------h
t
y
-------------------------------------------g use
o
l
o
boolean
TRUE
n e to
h
c
e ens
T
n
SQL>
tio le lic
a
b value to FALSE in pdb2.
4. Change the instance
rm eparameter
a
r
o
f
In ALTER
sfSYSTEM SET optimizer_use_sql_plan_baselines= FALSE
SQL>
l
n
a
a
b SCOPE=BOTH;
tr
Glo nSystem
onaltered.
SQL>
NAME
TYPE
VALUE
------------------------------------ ----------- --------optimizer_use_sql_plan_baselines
boolean
FALSE
SQL>
5.
Check the instance parameter value in other PDBs of the same CDB.
SQL> CONNECT sys/oracle_4U@pdb2_2 AS SYSDBA
Connected.
NAME
TYPE
VALUE
------------------------------------ ----------- --------Copyright © 2013, Oracle and/or its affiliates. All rights reserved.
Chapter 4 - Page 19
a
boolean
TRUE
SQL>
6.
Close and open pdb2.
SQL> CONNECT sys/oracle_4U@pdb2 AS SYSDBA
Connected.
SQL> ALTER PLUGGABLE DATABASE CLOSE IMMEDIATE;
SQL> ALTER PLUGGABLE DATABASE OPEN;
NAME
TYPE
VALUE
------------------------------------ ----------- --------optimizer_use_sql_plan_baselines
boolean
FALSE
s
) ha
om ฺ
c
ฺ
ch ide
SQL>
e
t
i
u
l- root
Gand
a
7. Check the instance parameter value after CDB shutdown/startup
both inn
PDBs.
t
b
o
l
e
g tud
@
o
Connected.
nf this S
i
(
gy use
o
l
o
Database closed.
hn se to
c
e
n
T
e
n
c
ORACLE instance
shut
down.
i
o
l
ti
le
SQL> rma
b
a
fostartup
er
SQL>
f
n
I
s
n
alORACLE
ainstance
started.
r
b
t
o
l
n
G no
Fixed Size
2248280 bytes
Variable Size
377487784 bytes
Database Buffers
683671552 bytes
Redo Buffers
5529600 bytes
Database mounted.
Database opened.
SQL> col VALUE format a20
SQL> select CON_ID, VALUE from
V$SYSTEM_PARAMETER
2 where name ='optimizer_use_sql_plan_baselines';
CON_ID VALUE
---------- -------------------Copyright © 2013, Oracle and/or its affiliates. All rights reserved.
Chapter 4 - Page 20
a
0 TRUE
3 FALSE
SQL> EXIT
$
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
b
lo den
g
@ Stu
o
f
(in this
y
og use
l
o
hn se to
c
e
T cen
n
o
li
ti
e
a
l
rm erab
o
f
In ansf
l
a
b
tr
Glo non-
Chapter 4 - Page 21
a
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
b
lo den
g
@ Stu
o
f
(in this
y
og use
l
o
hn se to
c
e
T cen
n
o
li
ti
e
a
l
rm erab
o
f
In ansf
l
a
b
tr
Glo non-
Chapter 4 - Page 22
a
s
) ha
om ฺ
c
ฺ
ch5: ide
e
t
i
l- t Guand
Managing Tablespaces
a
b
lo and
enPDBs
g
Users in
a
CDB
d
u
o@ is St
f
n
i
Chapter
( 5 th
y
g
se
o
l
u
o
hn se to
c
e
T cen
n
o
li
ti
e
a
l
rm erab
o
f
In ansf
l
a
b
tr
Glo non-
Practices for Lesson 5: Managing Tablespaces and Users in a CDB and PDBs
Chapter 5 - Page 1
a
Practices Overview
In this practice, you will manage the tablespaces, users, privileges, and roles.
Assumptions
Practice 3-1 successfully created cdb2.
Practice 3-3 successfully created pdb2_1.
Practice 4-4 successfully renamed pdb2_1 to pdb2.
If the trigger could not be created successfully, execute the following catchup script:
$ cd /home/oracle/recovery/catchup_04_03
$ ./cr_trig.sh
$
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
b
lo den
g
@ Stu
o
f
(in this
y
og use
l
o
hn se to
c
e
T cen
n
o
li
ti
e
a
l
rm erab
o
f
In ansf
l
a
b
tr
Glo non-
Chapter 5 - Page 2
a
Practice 5-1: Managing Tablespaces
Overview
In this practice, you will manage the tablespaces in the CDB and PDBs.
Tasks
1.
View permanent and temporary tablespace properties in cdb2.
$ . oraenv
Connected to:
Testing options
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
SQL> col PROPERTY_NAME format a30
b
lo den
SQL> col PROPERTY_VALUE format a25
g
@ Stu
o
SQL> SELECT property_name, property_value
f
(in this
2 FROM database_properties
y
se
og 'DEFAULT_%TABLE%';
u
3 WHERE property_nameolLIKE
hn se to
c
e
T cen
PROPERTY_NAME
PROPERTY_VALUE
n
i
o
l
i
t
e
a
-----------------------------------------------------------bl
m
r
a
r
o
DEFAULT_TEMP_TABLESPACE
TEMP
nf nsfe
I
l
USERS
baDEFAULT_PERMANENT_TABLESPACE
tra
o
l
n
G no
SQL> SELECT tablespace_name, CON_ID from CDB_TABLESPACES;
TABLESPACE_NAME
CON_ID
------------------------------ ---------SYSTEM
1
SYSAUX
1
UNDOTBS1
1
TEMP
1
USERS
1
SYSTEM
2
SYSAUX
2
TEMP
2
SYSTEM
3
Chapter 5 - Page 3
a
SYSAUX
TEMP
SYSTEM
SYSAUX
TEMP
SYSTEM
SYSAUX
TEMP
USERS
EXAMPLE
SYSTEM
SYSAUX
TEMP
USERS
EXAMPLE
3
3
4
4
4
5
5
5
5
5
6
6
6
6
6
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
SQL> SELECT tablespace_name, CON_ID from CDB_TABLESPACES
al- nt Gu
2 WHERE TABLESPACE_NAME LIKE 'TEMP%'; lob
g tude
@
S
nfoCON_ID
s
i
TABLESPACE_NAME
i
(
h
t
gy ---------e
-----------------------------s
o
l
o to u
n
TEMP
1
h
c
e
e
s
TEMP
2
T cen
n
i
o
l
TEMP
3
ti
e
a
l
b
m
TEMP r
4
ra
o
f
e
f
n
TEMP
5
I ans
l
a
b TEMP tr
6
6 rows selected.
SQL>
The number of tablespaces may differ from your result and the one shown in the first
statement. It depends if PDBs are created with or without the EXAMPLE and the USERS
tablespaces.
Manage permanent tablespaces.
a. Create a permanent tablespace CDATA in the root container.
SQL> CREATE TABLESPACE CDATA
2 DATAFILE '/u01/app/oracle/oradata/cdb2/cdata_01.dbf'
3 SIZE 10M ;
Chapter 5 - Page 4
a
Tablespace created.
SQL> SELECT tablespace_name, CON_ID from CDB_TABLESPACES
2 WHERE TABLESPACE_NAME = 'CDATA';
TABLESPACE_NAME
CON_ID
------------------------------ ---------CDATA
1
SQL>
b.
Make the CDATA tablespace the default tablespace in the root container.
SQL> ALTER DATABASE DEFAULT TABLESPACE CDATA ;
Database altered.
2 FROM
database_properties
3 WHERE property_name LIKE 'DEFAULT_%TABLE%';
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
PROPERTY_NAME
PROPERTY_VALUE
b
lo den
------------------------------ ------------------------------g
@ Stu
o
DEFAULT_TEMP_TABLESPACE
TEMP
f
in
is
DEFAULT_PERMANENT_TABLESPACE y (CDATA th
og use
l
o
hn se to
c
SQL>
e
n in PDB2.
T ceLDATA
n
c. Create permanent
tablespace,
i
o
l
ti
a
le
b
SQL> connect
system/oracle_4U@PDB2
m
r
a
fo sfer
Connected.
n
I
al -tran
b
o
Gl nSQL>
on CREATE TABLESPACE ldata DATAFILE
2
3
'/u01/app/oracle/oradata/cdb2/pdb2_1/ldata_01.dbf'
SIZE 10M ;
Tablespace created.
SQL>
d.
Make the LDATA tablespace the default tablepace in the PDB2 container.
SQL> ALTER PLUGGABLE DATABASE DEFAULT TABLESPACE LDATA ;
Chapter 5 - Page 5
a
3
WHERE property_name LIKE 'DEFAULT_%TABLE%';
PROPERTY_NAME
-----------------------------DEFAULT_TEMP_TABLESPACE
DEFAULT_PERMANENT_TABLESPACE
PROPERTY_VALUE
------------------------------TEMP
LDATA
SQL>
3.
Manage temporary tablespaces (optional).
a. Create a temporary tablespace TEMP_ROOT in the root container.
SQL> connect system/oracle_4U
Connected.
SQL> CREATE TEMPORARY TABLESPACE TEMP_ROOT
2 TEMPFILE '/u01/app/oracle/oradata/cdb2/temproot_01.dbf'
3 SIZE 100M ;
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
SQL>
b
o root dcontainer.
lthe
en
g
b. Make TEMP_ROOT the default temporary tablespace in
u
o@TABLESPACE
St TEMP_ROOT ;
f
SQL> ALTER DATABASE DEFAULT TEMPORARY
n
s
i
i
(
th
y
g
e
lo o us
o
Database altered.
n
h se t
c
e
n T licen property_value
SQL> SELECTtiproperty_name,
o
adatabase_properties
le
b
2 FROM
m
r
a
foWHEREsfproperty_name
er
3
LIKE 'DEFAULT_%TABLE%';
n
I
l
n
a
a
b n-tr
Glo nPROPERTY_NAME
o
PROPERTY_VALUE
Tablespace created.
------------------------------ ------------------------------DEFAULT_TEMP_TABLESPACE
TEMP_ROOT
CDATA
SQL>
c.
Create a temporary tablepace TEMP_PDB2 in PDB2.
SQL> connect system/oracle_4U@PDB2
Connected.
SQL> CREATE TEMPORARY TABLESPACE TEMP_PDB2 TEMPFILE
2
'/u01/app/oracle/oradata/cdb2/pdb2_1/temppdb2_01.dbf'
3
SIZE 100M ;
Chapter 5 - Page 6
a
Tablespace created.
SQL>
d.
Make TEMP_PDB2 the default temporary tablespace in PDB2.
SQL> ALTER DATABASE DEFAULT TEMPORARY TABLESPACE TEMP_PDB2 ;
Database altered.
PROPERTY_NAME
PROPERTY_VALUE
------------------------------TEMP_PDB2
LDATA
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
SQL>
b
n
lo decommand.
Note that you could also use the ALTER PLUGGABLEgDATABASE
u
o@ is St
f
e.
Create a temporary tablespace MY_TEMP inin
PDB2.
(
th TEMPFILE
y
g
SQL> CREATE TEMPORARY TABLESPACE
MY_TEMP
e
lo o us
o
2 '/u01/app/oracle/oradata/cdb2/pdb2_1/my_temp_pdb2_01.dbf'
n
ch nse t
3 SIZE 10M; Te
n
ce
i
o
l
i
t
a created.
le
b
Tablespace
m
r
a
fo sfer
n
I
alSQL>-tran
b
o
Gl f. nDisplay
on default tablespaces of another PDB in cdb2.
SQL> connect system/oracle_4U@PDB_ORCL2
Connected.
PROPERTY_NAME
PROPERTY_VALUE
------------------------------TEMP
USERS
SQL>
Chapter 5 - Page 7
a
4.
Manage default permanent and temporary tablespaces of users.
a. Create a common user C##U.
Connected.
SQL> CREATE USER c##u IDENTIFIED BY x;
User created.
SQL>
b.
View the default tablespace and temporary tablespace assignment for user CU in all
containers.
SQL>
SQL>
SQL>
SQL>
SQL>
2
3
4
COLUMN username format A12
COLUMN default_tablespace format A18
COLUMN temporary_tablespace format A20
COLUMN con_id format 999
SELECT username, default_tablespace,
temporary_tablespace, con_id
FROM CDB_USERS
WHERE username = 'C##U';
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
b
lo den
g
@ Stu
o
f
n this
USERNAME
DEFAULT_TABLESPACE(iTEMPORARY_TABLESPACE
CON_ID
y
------------ ----------------------se
og ---------------------l
u
o
C##U
CDATA hn
1
to TEMP_ROOT
c
e
e
s
C##U
LDATA
TEMP_PDB2
3
T cen
n
C##U
TEMP
4
li
tioSYSTEM
e
a
l
b
C##U rm
USERS
TEMP
5
a
r
o
f
e
C##U
TEMP
6
In ansf USERS
l
a
b n-tr
Glo nSQL>
o
c.
Create a local user LU in PDB2.
Connected.
SQL> CREATE USER lu IDENTIFIED BY x;
User created.
SQL>
d.
View the default tablespace and temporary tablespace assignment for user LU.
SQL> SELECT username, default_tablespace, temporary_tablespace
2 FROM DBA_USERS
3 WHERE username = 'LU';
Chapter 5 - Page 8
a
USERNAME
DEFAULT_TABLESPACE TEMPORARY_TABLESPACE
------------ ------------------ -------------------LU
LDATA
TEMP_PDB2
SQL>
e.
Change the temporary tablespace assignment for user LU to MY_TEMP in PDB2.
SQL> ALTER USER LU TEMPORARY TABLESPACE MY_TEMP;
User altered.
SQL>
f.
View the default temporary tablespace assignment for user LU.
SQL> SELECT username, default_tablespace, temporary_tablespace
2 FROM DBA_USERS
3 WHERE username = 'LU';
s
) ha
om ฺ
c
ฺ
ch ide
USERNAME
DEFAULT_TABLESPACE TEMPORARY_TABLESPACE
e
t
i
l- t Gu
------------ ------------------ -------------------a
b
en
LU
LDATA
MY_TEMPglo
d
u
o@ is St
f
SQL>
n
i
(
th
y
g
e
5. Manage UNDO tablespaces (optional).
lo o us
o
n
a. Display the UNDO tablespace
used
t CDB.
h sinethe
c
e
T cen
n
o
li
Connected.
ti
e
a
l
b A12
rmNAMEeraformat
SQL> o
col
f
In select
sf FILE#, ts.name, ts.ts#, ts.con_id
SQL>
l
n
a
a
b
tr v$datafile d, v$tablespace ts
Glo no23n- from
where d.ts#=ts.ts#
4
5
and
and
d.con_id=ts.con_id
ts.name like 'UNDO%';
FILE# NAME
TS#
CON_ID
---------- ------------ ---------- ---------4 UNDOTBS1
2
1
SQL>
b.
Create an UNDO tablespace in a PDB and set it as the UNDO_TABLESPACE of the
CDB.
Connected.
SQL> CREATE UNDO TABLESPACE UNDO_PDB2 DATAFILE
Chapter 5 - Page 9
a
2 '/u01/app/oracle/oradata/cdb2/pdb2/undo_pdb2_01.dbf'
3 SIZE 10M;
Tablespace created.
SQL> alter system set undo_tablespace='UNDO_PDB2' scope=both;
alter system set undo_tablespace='UNDO_PDB2' scope=both
*
ERROR at line 1:
ORA-65040: operation not allowed from within a pluggable
database
SQL>
Notice that the statement fails because the UNDO tablespace can only be set at CDB level.
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
b
lo den
g
@ Stu
o
f
(in this
y
og use
l
o
hn se to
c
e
T cen
n
o
li
ti
e
a
l
rm erab
o
f
In ansf
l
a
b
tr
Glo non-
Chapter 5 - Page 10
a
Practice 5-2: Managing Common and Local Users
Overview
In this practice, you will manage common and local users in the CDB and PDBs.
Tasks
1.
View all common and local users in cdb2.
Connected.
SQL> col username format a20
SQL> select USERNAME,COMMON,CON_ID
USERNAME
-------------------SYS
SYSTEM
C##U
…
C##U
JONES
ADAMS
SCOTT
…
C##U
…
DVSYS
AUDSYS
SI_INFORMTN_SCHEMA
OLAPSYS
from cdb_users;
COM CON_ID
--- -----YES
1
YES
1
YES
1
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
YES
3
l- t Gu
a
b
NO
3
lo den
g
NO
3
@ Stu
o
f
NO
3(in
is
h
t
y
og use
l
o
n e to4
hYES
c
e
T cens
n
4
tio le liYES
a
b
m
YES
4
r
a
r
o
f
e
YES
4
In ansf
l
a
b
YES
4
tr
2 where username='SYSTEM';
USERNAME
-------------------SYSTEM
SYSTEM
SYSTEM
SYSTEM
SYSTEM
SYSTEM
from cdb_users
COM CON_ID
--- -----YES
1
YES
2
YES
3
YES
4
YES
5
YES
6
Chapter 5 - Page 11
a
6 rows selected.
SQL> select distinct username from cdb_users
2 where common='YES';
USERNAME
-------------------DVF
SYSKM
DIP
XS$NULL
OUTLN
SYSBACKUP
SYSTEM
ORACLE_OCM
DVSYS
AUDSYS
DBSNMP
…
C##U
XDB
APPQOSSYS
SYSDG
ANONYMOUS
SYS
SI_INFORMTN_SCHEMA
ANONYMOUS
LBACSYS
WMSYS
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
b
lo den
g
@ Stu
o
f
(in this
y
og use
l
o
hn se to
c
e
T cen
n
o
li
ti
e
a
l
rm erab
o
f
In ansf
l
a
b
tr
SQL> select username,con_id
2 where common='NO';
from cdb_users
USERNAME
CON_ID
-------------------- -----PDB2_1_ADMIN
3
LU
3
PDB2_1_ADMIN
4
SCOTT
5
Chapter 5 - Page 12
a
BI
PM
IX
SH
OE
HR
PDBADMIN
HR
OE
SH
IX
PM
BI
SCOTT
5
5
5
5
5
5
6
6
6
6
6
6
6
6
18 rows selected.
s
) ha
om ฺ
c
ฺ
SQL>
ch ide
e
t
i
l- t Gu
2. Create a common user C##_USER.
a
b
o den
SQL> create user C##_USER identified bygxl CONTAINER=ALL;
@ Stu
o
f
User created.
(in this
y
og use
l
o
SQL>
hn se to
c
e
n
T C##_USER.
3. View the new common user
e
n
c
i
o
l
tidistinct
SQL> select
a
le username from cdb_users
b
m
r
a
2 fo
where username='C##_USER';
er
f
n
I
s
al -tran
b
o
Gl nUSERNAME
on
-------------------C##_USER
SQL>
4.
Notice that the common user exists in each container.
Grant CREATE SESSION as a common privilege
SQL> GRANT CREATE SESSION TO c##_user CONTAINER=ALL;
Grant succeeded.
SQL>
Chapter 5 - Page 13
a
5.
Connect to root, PDB2, and PDB2_2 as c##_user user.
SQL> connect
Connected.
SQL> connect
Connected.
SQL> connect
Connected.
SQL>
6.
c##_user/x@pdb2
c##_user/x@pdb2_2
c##_user/x@cdb2
Create a local user LOCAL_USER in the root container.
Connected.
SQL> create user local_user identified by x
2 CONTAINER=CURRENT;
create user local_user identified by x
*
ERROR at line 1:
ORA-65049: creation of local user or role is not allowed in
CDB$ROOT
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
b
lo den
g
@ Stu
SQL>
o
f
(in this
Notice that no local user is authorized in the
root.
y
oingPDB2.use
l
7. Create a local user LOCAL_USER_PDB2
o
hn se to
a. View all users of PDB2. ec
T cen
SQL> connection
sys/oracle_4U@PDB2
as sysdba
li
t
e
a
l
Connected.
rm erab
o
f
In ansf
l
a
SQL>
r username format a25
b n-tcol
o
l
G nSQL>
o select USERNAME,COMMON,CON_ID from cdb_users;
USERNAME
COM
CON_ID
-------------------- --- ---------SYS
YES
3
SYSTEM
YES
3
OLAPSYS
YES
3
SI_INFORMTN_SCHEMA
YES
3
DVSYS
YES
3
AUDSYS
YES
3
GSMUSER
YES
3
ORDPLUGINS
YES
3
C##_USER
YES
3
SPATIAL_WFS_ADMIN_US YES
3
Chapter 5 - Page 14
a
R
SPATIAL_CSW_ADMIN_US YES
R
XDB
YES
APEX_PUBLIC_USER
YES
SYSDG
YES
DIP
YES
OUTLN
YES
ANONYMOUS
YES
CTXSYS
YES
ORDDATA
YES
SYSBACKUP
YES
MDDATA
YES
GSMCATUSER
YES
GSMADMIN_INTERNAL
YES
LBACSYS
YES
C##U
YES
SYSKM
YES
XS$NULL
YES
OJVMSYS
YES
APPQOSSYS
YES
ORACLE_OCM
YES
APEX_040200
YES
PDB2_1_ADMIN
NO
WMSYS
YES
DBSNMP
YES
ORDSYS
YES
MDSYS
YES
LU
NO
DVF
YES
FLOWS_FILES
YES
3
3
3
3
3
3
3
3
3
3
3
3
3
3
3
3
3
3
3
3
3
3
3
3
3
3
3
3
3
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
b
lo den
g
@ Stu
o
f
(in this
y
og use
l
o
hn se to
c
e
T cen
n
o
li
ti
e
a
l
rm erab
o
f
In ansf
l
a
b
tr
SQL>
Notice that you view all common and local users of the current PDB.
SQL> select USERNAME,COMMON from dba_users;
Notice that you view the same list.
b. Attempt to create a common user C##_USER_PDB2 in PDB2.
SQL> create user c##_user_pdb2 identified by x
2 CONTAINER=ALL;
create user c##_user_pdb2 identified by x CONTAINER=ALL
Chapter 5 - Page 15
a
*
ERROR at line 1:
ORA-65050: Common DDLs only allowed in CDB$ROOT
SQL>
Notice that no common user can be created except from the root.
c. Create the local user LOCAL_USER_PDB2 in PDB2.
SQL> create user local_user_pdb2 identified by x
User created.
2> order by username;
from cdb_users
USERNAME
COM
CON_ID
-------------------- --- ---------ANONYMOUS
YES
3
APEX_040200
YES
3
APEX_PUBLIC_USER
YES
3
APPQOSSYS
YES
3
AUDSYS
YES
3
C##U
YES
3
C##_USER
YES
3
CTXSYS
YES
3
DBSNMP
YES
3
DIP
YES
3
DVF
YES
3
DVSYS
YES
3
FLOWS_FILES
YES
3
GSMADMIN_INTERNAL
YES
3
GSMCATUSER
YES
3
GSMUSER
YES
3
LBACSYS
YES
3
LOCAL_USER_PDB2
NO
3
LU
NO
3
MDDATA
YES
3
MDSYS
YES
3
OJVMSYS
YES
3
OLAPSYS
YES
3
ORACLE_OCM
YES
3
ORDDATA
YES
3
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
b
lo den
g
@ Stu
o
f
(in this
y
og use
l
o
hn se to
c
e
T cen
n
o
li
ti
e
a
l
rm erab
o
f
In ansf
l
a
b
tr
Glo non-
Chapter 5 - Page 16
a
ORDPLUGINS
YES
ORDSYS
YES
OUTLN
YES
PDB2_1_ADMIN
NO
SI_INFORMTN_SCHEMA
YES
SPATIAL_CSW_ADMIN_US YES
R
SPATIAL_WFS_ADMIN_US YES
R
SYS
YES
SYSBACKUP
YES
SYSDG
YES
SYSKM
YES
SYSTEM
YES
WMSYS
YES
XDB
YES
XS$NULL
YES
3
3
3
3
3
3
3
3
3
3
3
3
3
3
3
s
) ha
om ฺ
c
ฺ
ch ide
e
40 rows selected.
t
i
l- t Gu
a
b
lo den
g
SQL> grant create session to local_user_pdb2;
@ Stu
o
f
(in this
y
Grant succeeded.
og use
l
o
SQL>
hn se to
c
e
T cen
d. Connect to PDB2 as
LOCAL_USER_PDB2.
n
o
li
ti local_user_pdb2/x@PDB2
e
SQL> connect
a
l
rm erab
o
Connected.
f
In
sf
l
SQL> ran
a
b n-t
Gloe. nConnect
o to PDB2_2 as LOCAL_USER_PDB2.
SQL> connect local_user_pdb2/x@PDB2_2
ERROR:
ORA-01017: invalid username/password; logon denied
Warning: You are no longer connected to ORACLE.
SQL>
Notice that it fails because LOCAL_USER_PDB2 does not exist in PDB2_2.
SQL> connect local_user_pdb2/x@cdb2
ERROR:
SQL>
Chapter 5 - Page 17
a
Notice that it fails because LOCAL_USER_PDB2 does not exist in root.
f. Overview of common and local users from a PDB.
SQL> connect sys/oracle_4U@PDB2_2 as sysdba
Connected.
SQL> col username format a20
SQL> select USERNAME, COMMON, CON_ID from cdb_users
2> order by username;
USERNAME
-------------------ANONYMOUS
APPQOSSYS
APPS
…
C##_USER
…
SYSTEM
…
XS$NULL
COM CON_ID
--- -----YES
4
YES
4
NO
4
APPS
…
C##_USER
…
SYSTEM
…
XS$NULL
NO
YES
4
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
YES
4
a
b
lo den
g
@ Stu
39 rows selected.
o
f
(in this
y
og use
SQL>
l
o
n localeusers
to of the current PDB.
hand
Notice that you view all common
c
e
s
n from dba_users order by username;
T cCOMMON
e
SQL> select USERNAME,
n
i
o
l
ti
a
le
b
m
r
a
USERNAME
COM
fo sfer
n
I
l
n
---------------------a -tra
b
o
YES
Gl nANONYMOUS
on
APPQOSSYS
YES
YES
4
YES
YES
YES
39 rows selected.
SQL>
Notice that you view the same list.
Chapter 5 - Page 18
a
Practice 5-3: Managing Local and Common Roles
Overview
In this practice, you will manage roles created as common or local, and granted as common
and/or local in CDB and PDBs.
Assumptions
C##_USER and LOCAL_USER_PDB2 are successfully created from the previous Practice 5-2 in
cdb2 PDB2.
Tasks
1.
Manage creation of roles in CDB and PDBs.
a. List all predefined roles in CDB.
Connected.
SQL> col role format a30
SQL> select ROLE, COMMON, CON_ID from cdb_roles order by role;
s
) ha
om ฺ
c
ฺ
ch ide
ROLE
COM CON_ID
e
t
i
l- t Gu
------------------------------ --- -----a
b
en
ADM_PARALLEL_EXECUTE_TASK
YES
2lo
g
d
u
YESfo@ 1 St
in thi3s
(YES
y
se 4
og YES
l
u
o
hn se toYES
5
c
e
n
T
YES
6
n
ce
i
o
l
i
t
a
le
b
m
r
a
…
fo sfer
n
I
YES
3
alDBA -tran
b
o
YES
1
Gl nDBA
on
DBA
YES
4
DBA
DBA
DBA
YES
YES
YES
2
5
6
…
PDB_DBA
PDB_DBA
PDB_DBA
YES
YES
YES
3
4
6
…
495 rows selected.
Chapter 5 - Page 19
a
SQL>
You can view all common and local roles of the root and PDBs.
b. List all predefined roles in root.
SQL> select ROLE, COMMON from dba_roles order by role;
ROLE
-----------------------------ADM_PARALLEL_EXECUTE_TASK
APEX_ADMINISTRATOR_ROLE
AQ_USER_ROLE
…
XS_CACHE_ADMIN
XS_NSATTR_ADMIN
XS_RESOURCE
XS_SESSION_ADMIN
COM
--YES
YES
YES
YES
YES
YES
YES
YES
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
82 rows selected.
a
b
lo den
g
@ Stu
o
SQL>
f
(incannotthbeisany local roles in the root.
y
Notice that all roles of the root are common:
there
log o use
c. Create a common C##_ROLE n
ino
root.
et
SQL> create roleTc##_role
ech enscontainer=ALL;
n
o
lic
i
t
e
a
l
Role created.
rm erab
o
f
In ansf
l
a
SQL>
b n-tr
Glod. nCreate
o a local LOCAL_ROLE in root.
SQL> create role local_role container=CURRENT;
create role local_role container=CURRENT
*
ERROR at line 1:
ORA-65049: creation of local user or role is not allowed in
CDB$ROOT
SQL>
You get an error message because no local role is authorized in the root.
e. List all predefined roles in PDB PDB2.
SQL> connect
Connected.
system/oracle_4U@PDB2
Chapter 5 - Page 20
a
SQL> col role format a30
SQL> select ROLE, COMMON, CON_ID from cdb_roles;
ROLE
COM CON_ID
------------------------------ --- -----CONNECT
YES
3
RESOURCE
YES
3
DBA
YES
3
AUDIT_ADMIN
YES
3
…
C##_ROLE
YES
3
DV_REALM_RESOURCE
YES
3
DV_REALM_OWNER
YES
3
PDB_DBA
YES
3
s
) ha
84 rows selected.
om ฺ
c
ฺ
ch ide
e
t
You can view all common and local roles of the PDB only.
i
l- t Gu
a
b
SQL> select ROLE,COMMON from dba_roles order
by
lo drole;
en
g
u
ROLE
COMfo@
St
n
s
i
i
(--- th
-----------------------------y
g
se
o YES
l
CONNECT
u
o
hn se toYES
RESOURCE
c
e
T cen
DBA
YES
n
i
o
l
i
t
AUDIT_ADMIN
YES
a
le
b
m
r
a
…
fo sfer
n
I
YES
alPDB_DBA
an
r
b
t
o
Gl n…on
XDB_WEBSERVICES
YES
SQL>
XDB_WEBSERVICES_OVER_HTTP
XDB_WEBSERVICES_WITH_PUBLIC
XS_CACHE_ADMIN
XS_NSATTR_ADMIN
XS_RESOURCE
XS_SESSION_ADMIN
YES
YES
YES
YES
YES
YES
84 rows selected.
SQL>
You view the same list.
f. Create a common role in PDB2.
Chapter 5 - Page 21
a
SQL> create role c##_role_PDB2 container=ALL;
create role c##_role_PDB2 container=ALL
*
ERROR at line 1:
SQL>
You get an error message because no common role can be created from a PDB.
g. Create a local role in PDB2.
SQL> create role local_role_PDB2 container=CURRENT;
Role created.
SQL> select ROLE,COMMON from dba_roles order by role;
ROLE
-----------------------------ADM_PARALLEL_EXECUTE_TASK
APEX_ADMINISTRATOR_ROLE
…
LOCAL_ROLE_PDB2
…
XS_NSATTR_ADMIN
XS_RESOURCE
XS_SESSION_ADMIN
COM
--YES
YES
YES
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
b
lo den
g
@ Stu
NOnfo
is
(i
h
t
y
se
og YES
l
u
o
hn se toYES
c
e
T cen
YES
n
i
o
l
i
t
e
a
bl
m
r
a
r
o
85 nrows
f selected.
fe
I
s
l
n
baSQL>
tra
o
l
n
G no
2. Grant common or local roles as common or local.
a.
Grant a common role to a common user from the root.
Connected.
SQL> grant c##_role to c##_user;
Grant succeeded.
SQL>
SQL>
SQL>
2
col grantee format A16
col GRANTED_ROLE format A16
select GRANTEE, GRANTED_ROLE, COMMON, CON_ID
from cdb_role_privs where grantee='C##_USER';
Chapter 5 - Page 22
a
GRANTEE
GRANTED_ROLE
COM CON_ID
---------------- ---------------- --- -----C##_USER
C##_ROLE
NO
1
SQL>
Note that the common role is granted locally to the common user. The granted role is only
applicable in the root.
SQL> connect c##_user/x
Connected.
SQL> select * from session_roles;
ROLE
-----------------------------C##_ROLE
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
SQL> connect c##_user/x@PDB2
a
b
lo den
Connected.
g
@ Stu
o
f
(in this
y
og use
no rows selected
l
o
hn se to
c
e
T cen
SQL>
n
o
li
i
tcommon
e
b. Now grant the
role to a common user from the root as common, to be
a
l
b
rmin all econtainers.
a
applicable
r
o
f
In connect
sf / as sysdba
l
SQL>
n
a
a
b n-tr
Glo nConnected.
o
SQL> grant c##_role to c##_user container=all;
SQL>
Grant succeeded.
SQL> select GRANTEE, GRANTED_ROLE, COMMON, CON_ID
2 from cdb_role_privs where grantee='C##_USER';
GRANTEE
---------------C##_USER
C##_USER
C##_USER
C##_USER
C##_USER
GRANTED_ROLE
---------------C##_ROLE
C##_ROLE
C##_ROLE
C##_ROLE
C##_ROLE
COM CON_ID
--- -----NO
1
YES
1
YES
3
YES
4
YES
5
Chapter 5 - Page 23
a
C##_USER
C##_ROLE
YES
6
SQL>
Connected.
ROLE
-----------------------------C##_ROLE
SQL>
Connected.
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
b
lo den
ROLE
g
@ Stu
-----------------------------o
f
(in this
C##_ROLE
y
og use
l
o
hn se to
SQL>
c
e
T fromcethencommon user so that the role cannot be used in any
c. Revoke the common
role
n
o
li
container. ati
e
l
rm e/raasb sysdba
SQL>fo
connect
In ansf
l
Connected.
a
b n-tr
Glo nSQL>
o revoke c##_role from c##_user container=all;
Revoke succeeded.
Connected.
ROLE
-----------------------------C##_ROLE
SQL>
Chapter 5 - Page 24
a
Connected.
no rows selected
SQL>
d.
Grant a common role to a local user from the root.
Connected.
SQL> grant c##_role to local_user_pdb2;
grant c##_role to local_user_pdb2
*
ERROR at line 1:
ORA-01917: user or role 'LOCAL_USER_PDB2' does not exist
s
) ha
om ฺ
c
ฺ
ch ide
e
Note that the user is unknown in root. It is a local user in PDB2.
t
i
l- t Gu
a
e. Grant a common role to a local user from PDB2.
b
lo den
SQL> connect system/oracle_4U@PDB2 @g
tu
o
S
f
Connected.
(in this
y
SQL> grant c##_role to local_user_PDB2;
og use
l
o
Grant succeeded.
hn se to
c
e
n T liGRANTED_ROLE,
cen
SQL> selecttiGRANTEE,
COMMON, CON_ID
o
e
a
l
b
2 from
where grantee='LOCAL_USER_PDB2';
rm cdb_role_privs
a
r
o
f
e
In ansf
l
a
GRANTED_ROLE
COM CON_ID
b GRANTEE
tr
Glo n---------------on---------------- --- -----SQL>
LOCAL_USER_PDB2
C##_ROLE
NO
3
SQL>
Note that the user is granted a common role locally (common column = NO) applicable only
in the PDB PDB2.
f. Test the connection as the local user.
SQL> connect
Connected.
local_user_pdb2/x@PDB2
ROLE
-----------------------------C##_ROLE
Chapter 5 - Page 25
a
SQL>
g.
Grant a common role to a local user from PDB2 applicable in all containers.
Connected.
SQL> grant c##_role to local_user_pdb2 container=all;
grant c##_role to local_user_pdb2 container=all
*
ERROR at line 1:
ORA-65030: one may not grant a Common Privilege to a Local User
or Role
SQL>
Notice that a common role cannot be granted globally from a PDB.
h. Grant a local role to a local user from PDB2.
SQL> grant local_role_pdb2 to local_user_pdb2;
Grant succeeded.
SQL> select GRANTEE, GRANTED_ROLE, COMMON, CON_ID
2 from cdb_role_privs where grantee='LOCAL_USER_PDB2';
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
GRANTEE
GRANTED_ROLE
COM CON_ID
b
lo den
g
---------------- ---------------- --- -----@ S3 tu
o
f
LOCAL_USER_PDB2 C##_ROLE
NO
(in NO this 3
y
LOCAL_USER_PDB2 LOCAL_ROLE_PDB2
og use
l
o
SQL>
hn se to
c
e
n
Tthe local
i. Test the connection
as
user.
e
n
c
i
o
l
ti local_user_pdb2/x@PDB2
SQL> connect
a
le
b
m
r
a
Connected.
fo sfer
n
I
alSQL>-tselect
an * from session_roles;
r
b
o
Gl nROLE
on
-----------------------------C##_ROLE
LOCAL_ROLE_PDB2
SQL>
Chapter 5 - Page 26
a
Practice 5-4: Managing Local and Common Privileges
Overview
In this practice, you will manage privileges granted as common and/or local in the CDB and
PDBs.
Assumptions
C##_USER and LOCAL_USER_PDB2 are successfully created from the previous Practice 5-2 in
cdb2 PDB2.
Tasks
1.
Check whether privileges are created as common or local.
Connected.
SQL> desc sys.system_privilege_map
Name
Null?
Type
------------------------------------ -------- ----------PRIVILEGE
NOT NULL NUMBER
NAME
NOT NULL VARCHAR2(40)
PROPERTY
NOT NULL NUMBER
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
b
lo den
g
@ Stu
SQL> desc sys.table_privilege_mapnfo
is
(i
h
t
Name
Null?
Type
y
g
e
s
o
l
-------------------------------------------- ----------o to u
n
h
PRIVILEGE
NOT NULL NUMBER
ec ense
T
NAME
NOT NULL VARCHAR2(40)
n
ic
o
l
i
t
e
a
bl
m
r
a
r
o
SQL>
nf nsfe
I
l
Notice
there
ra is no COMMON column. Privileges are not created as common or local, but
ba that
t
o
l
n
G theyncan
o be granted as common or local.
2. Check how the CREATE SESSION system privilege was granted to C##_USER and
LOCAL_USER_PDB2 users.
Connected.
SQL> col grantee format a18
SQL> col privilege format a14
SQL> select GRANTEE, PRIVILEGE, COMMON, CON_ID
2 from cdb_sys_privs
3 where grantee in ('C##_USER', 'LOCAL_USER_PDB2');
GRANTEE
PRIVILEGE
COM CON_ID
------------------ -------------- --- -----C##_USER
CREATE SESSION YES
1
Chapter 5 - Page 27
a
C##_USER
LOCAL_USER_PDB2
C##_USER
C##_USER
C##_USER
CREATE
CREATE
CREATE
CREATE
CREATE
SESSION
SESSION
SESSION
SESSION
SESSION
YES
NO
YES
YES
YES
3
3
4
5
6
6 rows selected.
SQL>
Connected.
SQL> select GRANTEE, PRIVILEGE, COMMON
2 from dba_sys_privs
3 where grantee in ('C##_USER', 'LOCAL_USER_PDB2');
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
b
lo den
g
@ Stu
o
f
(in this
SQL>
y
se
og anduUNLIMITED
l
o
3. Grant the system privileges CREATE
TABLE
to common
nany container.
to This will be aTABLESPACE
h
c
user C##_USER to be applicable
in
common
privilege.
e
Te cens
n
SQL> connectosystem/oracle_4U
li
ti
e
a
l
Connected.
b
rm CREATE
a
r
o
f
e
SQL>
grant
TABLE, UNLIMITED TABLESPACE to C##_USER
n nsf
I
l
ra
ba 2n-tCONTAINER=ALL;
o
l
G nGrant
o succeeded.
GRANTEE
-----------------LOCAL_USER_PDB2
C##_USER
PRIVILEGE
-------------CREATE SESSION
CREATE SESSION
COM
--NO
YES
SQL> col privilege format a30
3 where grantee = 'C##_USER';
GRANTEE
PRIVILEGE
COM CON_ID
------------ ------------------------------ --- -----C##_USER CREATE TABLE
YES
1
C##_USER CREATE SESSION
YES
1
C##_USER UNLIMITED TABLESPACE
YES
1
Chapter 5 - Page 28
a
C##_USER
C##_USER
C##_USER
C##_USER
C##_USER
C##_USER
C##_USER
C##_USER
C##_USER
C##_USER
C##_USER
C##_USER
CREATE TABLE
CREATE SESSION
UNLIMITED TABLESPACE
CREATE TABLE
CREATE SESSION
CREATE TABLE
CREATE SESSION
CREATE TABLE
CREATE SESSION
YES
YES
YES
YES
YES
YES
YES
YES
YES
YES
YES
YES
3
3
3
4
4
4
5
5
5
6
6
6
15 rows selected.
SQL>
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
b
lo den
Connected.
g
@ Stu
o
f
is
(in thCONTAINER=CURRENT;
SQL> grant CREATE SEQUENCE toyC##_USER
og use
l
Grant succeeded.
o
hn se to
c
e
n
T PRIVILEGE,
SQL> select GRANTEE,
COMMON, CON_ID
e
n
c
i
o
l
i
t
2 from acdb_sys_privs
le
b
m
r
a
3 fo
where grantee
= 'C##_USER';
er
f
n
I
s
al -tran
b
o
PRIVILEGE
COM CON_ID
Gl nGRANTEE
on
------------ ------------------------------ --- -----4.
Grant the system privilege CREATE SEQUENCE to common user C##_USER to be
applicable in root only. This will be a local privilege.
C##_USER
C##_USER
C##_USER
C##_USER
C##_USER
C##_USER
C##_USER
C##_USER
C##_USER
C##_USER
C##_USER
C##_USER
CREATE SEQUENCE
CREATE TABLE
CREATE SESSION
CREATE TABLE
CREATE SESSION
CREATE TABLE
CREATE SESSION
CREATE TABLE
CREATE SESSION
NO
YES
YES
YES
YES
YES
YES
YES
YES
YES
YES
YES
Chapter 5 - Page 29
1
1
1
1
3
3
3
4
4
4
5
5
a
C##_USER
C##_USER
C##_USER
C##_USER
CREATE TABLE
CREATE SESSION
YES
YES
YES
YES
5
6
6
6
16 rows selected.
SQL>
5.
Grant the system privilege CREATE SYNONYM to common user C##_USER to be applicable
in PDB2 only. This will be a local privilege.
Connected.
SQL> grant CREATE SYNONYM to C##_USER CONTAINER=CURRENT;
Grant succeeded.
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
2
from cdb_sys_privs
a
b
lo den
3
where grantee = 'C##_USER';
g
@ Stu
o
f
in this
GRANTEE
PRIVILEGE y (
COM CON_ID
g
e
s
o
l
------------------ -------------------------------- -----o to u
n
h
C##_USER
CREATE
SYNONYM
NO
3
c nse
e
T
C##_USER
YES
3
n CREATE
ceTABLE
i
o
l
i
t
C##_USER a
CREATE
YES
3
le SESSION
b
m
r
a
C##_USER
YES
3
fo sfer UNLIMITED TABLESPACE
n
I
al -tran
b
o
Gl nSQL>
on
6. Grant the system privilege CREATE VIEW to common user C##_USER to be applicable in
root only, but connected in PDB2.
SQL> grant CREATE VIEW to C##_USER CONTAINER=ALL;
grant CREATE VIEW to C##_USER CONTAINER=ALL
*
ERROR at line 1:
SQL>
7.
Note that you cannot grant a common privilege from a PDB.
Grant the system privilege CREATE ANY TABLE to local user LOCAL_USER_PDB2 to be
applicable in any container.
Chapter 5 - Page 30
a
Connected.
SQL> grant CREATE ANY TABLE to LOCAL_USER_PDB2 CONTAINER=ALL;
grant CREATE ANY TABLE to LOCAL_USER_PDB2 CONTAINER=ALL
*
ERROR at line 1:
SQL>
Notice that the user is unknown in root. It is a local user in PDB2.
8.
Grant the system privilege CREATE ANY SEQUENCE to local user LOCAL_USER_PDB2 to
be applicable in root only.
SQL> grant CREATE ANY SEQUENCE to LOCAL_USER_PDB2
grant CREATE ANY SEQUENCE to LOCAL_USER_PDB2
*
ERROR at line 1:
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
b
lo den
g
@ Stu
o
f
(in this
SQL>
y
e
suser
loIt gis aolocal
u
Notice that the user is unknown in n
root.
in PDB2.
o
t
h
e
9. Grant the system privilege UNLIMITED
to local user LOCAL_USER_PDB2 to
ec ensTABLESPACE
T
be applicable in PDB2oonly.
This iwill
be
a
local
privilege.
n
lc
ti system/oracle_4U@PDB2
e
a
l
SQL> connect
rm erab
o
f
Connected.
In ansf
l
a
b n-tr
Glo nSQL>
o col grantee format a18
SQL> grant UNLIMITED TABLESPACE to LOCAL_USER_PDB2;
Grant succeeded.
3 where grantee = 'LOCAL_USER_PDB2';
GRANTEE
-----------------LOCAL_USER_PDB2
LOCAL_USER_PDB2
PRIVILEGE
-----------------------------CREATE SESSION
SQL>
Chapter 5 - Page 31
COM CON_ID
--- -----NO
3
NO
3
a
10. Grant the system privilege DROP ANY VIEW to local user LOCAL_USER_PDB2 to be
applicable in root only but connected in PDB2.
SQL> grant DROP ANY VIEW to LOCAL_USER_PDB2 CONTAINER=ALL;
grant DROP ANY VIEW to LOCAL_USER_PDB2 CONTAINER=ALL
*
ERROR at line 1:
ORA-65030: one may not grant a Common Privilege to a Local User
or Role
SQL> EXIT
$
Notice that you cannot grant a local privilege that will be applicable in another container.
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
b
lo den
g
@ Stu
o
f
(in this
y
og use
l
o
hn se to
c
e
T cen
n
o
li
ti
e
a
l
rm erab
o
f
In ansf
l
a
b
tr
Glo non-
Chapter 5 - Page 32
a
s
) ha
om ฺ
c
ฺ
ch6: ide
e
t
i
u
l- Flashback
Backup, Recovery,
G
a
t
b
lo den
g
CDB and
PDBs
@ Stu
o
f
Chapter
(in 6 this
y
og use
l
o
hn se to
c
e
T cen
n
o
li
ti
e
a
l
rm erab
o
f
In ansf
l
a
b
tr
Glo non-
Practices for Lesson 6: Backup, Recovery, Flashback CDB and PDBs
Chapter 6 - Page 1
a
Practices Overview
In the next practices you will perform backup and recovery operations on the CDB and PDBs.
•
RMAN cdb2 backup
•
RMAN whole and partial pdb2 backup
•
Recovery from SYSTEM pdb2 data file loss
•
Recovery from non-essential pdb2 data file loss
Other optional scenarios are proposed for the attendees who still have time within the dedicated
hour and want to run some more practices.
•
SQL PDB hot backup
•
SQL control file backup
•
Recovery from all control files loss
•
Recovery from redo log member loss
•
Recovery from SYSTEM root data file loss
•
Recovery from a non-essential root data file loss
•
Point-in-time recovery on PDB tablespaces
•
CDB flashback from DROP common user
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
b
lo den
g
Assumptions
@ Stu
o
f
cdb2 is successfully created from previous Practice
n this
(i3-1.
y
pdb2_1 is successfully created from previous
e
ogPracticeus3-3.
l
o
pdb2_1 is successfully renamed to pdb2
previous
to Practice 4-4.
hn from
c
e
e
s
T cen
n
o
li could not be created successfully, execute the
If permanent and temporary
ti tablespaces
e
a
l
following catchuprscript:
m rab
o
f
fe
n /home/oracle/recovery/catchup_05_02
$ Icd
s
l
n
ba$ ./cr_TABLESPACES.sh
tra
o
l
n
G n$o
Chapter 6 - Page 2
a
Practice 6-1: Cold CDB Backup
Overview
In this practice, you will perform a CDB cold backup that you can use in case you lose all further
backups or you cannot recover from a difficult situation.
But before performing this task, make sure your database is in ARCHIVELOG mode.
Tasks
1.
Create the backup directory.
$ rm -Rf /home/oracle/Safe_Database_Files/cdb2
$ mkdir /home/oracle/Safe_Database_Files
$ mkdir /home/oracle/Safe_Database_Files/cdb2
$
2.
Shut down the cdb2 database before backing up all files.
$ . oraenv
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
b
Connected to:
lo den
g
tu 12.1.0.0.2 @Release
Oracle Database 12c Enterprise Edition
o
S
f
64bit Production
(in this
y
e and Real Application
With the Partitioning, OLAP,
og DatausMining
l
o
Testing options
hn se to
c
e
T from
en v$database;
n
c
SQL> select ilog_mode
i
o
l
t
a
le
b
m
r
a
fo sfer
LOG_MODE
n
I
al-----------an
r
b
t
o
Gl nNOARCHIVELOG
on
Database closed.
SQL> STARTUP MOUNT
Fixed Size
Variable Size
Database Buffers
655556608
2276288
188744768
461373440
bytes
bytes
bytes
bytes
Chapter 6 - Page 3
a
Redo Buffers
Database mounted.
3162112 bytes
SQL> ALTER DATABASE ARCHIVELOG;
Database altered.
SQL> ALTER DATABASE OPEN;
Database altered.
Database closed.
s
) ha
SQL> EXIT
$
om ฺ
c
ฺ
ch ide
$ tar -czf /home/oracle/Safe_Database_Files/cdb2/db.tar.gz
e
t
i
l- t Gu
/u01/app/oracle/oradata/cdb2
a
b
lo den
tar: Removing leading `/' from member names
g
@ Stu
$
o
f
in twith
isRMAN.
(backups
h
4. Start up the cdb2 database before performing
y
og use
$ sqlplus / AS SYSDBA nol
h se to
c
e
n
T
e
Connected tooan
idleliinstance.
n
c
ti
a
le
b
m
r
a
foSTARTUP
SQL>
er
f
n
I
s
n
started.
alORACLE
ainstance
r
b
t
o
l
n
G no
3.
Copy the files to the backup directory. The message is an informative message only.
Fixed Size
Variable Size
Database Buffers
Redo Buffers
Database mounted.
Database opened.
SQL> EXIT
$
2276288
188744768
461373440
3162112
bytes
bytes
bytes
bytes
Chapter 6 - Page 4
a
Practice 6-2: RMAN Whole CDB Backup
Overview
In this practice, you will perform a whole CDB backup of cdb2.
Assumptions
The PDB2 has been successfully created in cdb2 after Practices 3-3 and 4-4.
Tasks
1.
Run RMAN to connect to cdb2 with a user with SYSDBA or SYSBACKUP privilege.
$ export NLS_DATE_FORMAT='DD-MM-YYYY HH:MI:SS'
$ rman target /
connected to target database: cdb2 (DBID=534508813)
RMAN>
2.
s
) ha
As usual, backup all data files of the database (root and all PDBs), control files and
SPFILE, and archive log files, after setting the db_recovery_file_dest_size to 18
GB.
om ฺ
c
ฺ
ch ide
e
RMAN> CONFIGURE DEFAULT DEVICE TYPE TO disk;
t
i
- t Gucatalog
lrecovery
a
using target database control file instead b
of
lo den
g
new RMAN configuration parameters:
o@ is Stu
f
CONFIGURE DEFAULT DEVICE TYPE TOin
DISK;
( are tsuccessfully
h
y
new RMAN configuration parameters
stored
g
e
s
o
l
u
o
to
hn seAUTOBACKUP
c
RMAN> CONFIGURE CONTROLFILE
ON;
e
n
T
e
n
new RMAN configuration
io le lic parameters:
t
a
CONFIGURE
CONTROLFILE
AUTOBACKUP ON;
b
rmconfiguration
a
r
o
f
e
new
RMAN
parameters are successfully stored
n nsf
I
l
ba n-tra
o
l
G nRMAN>
o ALTER SYSTEM SET db_recovery_file_dest_size=18G
SCOPE=both;
Statement processed
RMAN> BACKUP DATABASE PLUS ARCHIVELOG;
Starting backup at 02-07-2012 02:53:38
current log archived
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=46 device type=DISK
channel ORA_DISK_1: starting archived log backup set
channel ORA_DISK_1: specifying archived log(s) in backup set
input archived log thread=1 sequence=10 RECID=1 STAMP=787589619
channel ORA_DISK_1: starting piece 1 at 02-07-2012 02:53:40
Chapter 6 - Page 5
a
channel ORA_DISK_1: finished piece 1 at 02-07-2012 02:53:41
piece
handle=/u01/app/oracle/fast_recovery_area/cdb2/backupset/2012_07
_02/o1_mf_annnn_TAG20120702T145339_7z3fhn5p_.bkp
tag=TAG20120702T145339 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:01
Finished backup at 02-07-2012 02:53:41
using channel ORA_DISK_1
channel ORA_DISK_1: starting full datafile backup set
channel ORA_DISK_1: specifying datafile(s) in backup set
input datafile file number=00001
name=/u01/app/oracle/oradata/cdb2/system01.dbf
name=/u01/app/oracle/oradata/cdb2/sysaux01.dbf
name=/u01/app/oracle/oradata/cdb2/pdbseed/sysaux01.dbf
name=/u01/app/oracle/oradata/cdb2/pdb2_1/sysaux01.dbf
name=/u01/app/oracle/oradata/cdb2/pdbseed/system01.dbf
name=/u01/app/oracle/oradata/cdb2/pdb2_1/system01.dbf
name=/u01/app/oracle/oradata/cdb2/undotbs01.dbf
name=/u01/app/oracle/oradata/cdb2/users01.dbf
name=/u01/app/oracle/oradata/cdb2/pdb2_1/pdb2_1_users01.dbf
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
b
lo den
g
@ Stu
o
f
(in this
y
og use
l
o
hn se to
c
e
T cen
n
o
li
ti
e
a
l
rm erab
o
f
In ansf
l
a
b
tr
Glo non-
piece
handle=/u01/app/oracle/fast_recovery_area/cdb2/backupset/2012_07
_02/o1_mf_annnn_TAG20120702T145426_7z3fk2qy_.bkp
Chapter 6 - Page 6
a
Starting Control File and SPFILE Autobackup at 02-07-2012
02:54:27
piece
handle=/u01/app/oracle/fast_recovery_area/cdb2/autobackup/2012_0
7_02/o1_mf_s_787589667_7z3fk46t_.bkp comment=NONE
Finished Control File and SPFILE Autobackup at 02-07-2012
02:54:28
RMAN>
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
b
lo den
g
@ Stu
o
f
(in this
y
og use
l
o
hn se to
c
e
T cen
n
o
li
ti
e
a
l
rm erab
o
f
In ansf
l
a
b
tr
Glo non-
Chapter 6 - Page 7
a
Practice 6-3: RMAN CDB / PDB Backup
Overview
In this practice, you will perform a whole and a partial PDB backup of PDB2.
Assumptions
The PDB2 has been successfully created in cdb2 after Practices 3-1, 3-3, and 4-4.
Tasks
1.
Perform a whole PDB backup.
a. A new RMAN command allows you to back up all data files of the pluggable database.
RMAN> BACKUP PLUGGABLE DATABASE pdb2;
name=/u01/app/oracle/oradata/cdb2/pdb2_1/sysaux01.dbf
name=/u01/app/oracle/oradata/cdb2/pdb2_1/system01.dbf
name=/u01/app/oracle/oradata/cdb2/pdb2_1/ldata_01.dbf
piece
handle=/u01/app/oracle/fast_recovery_area/CDB2/backupset/2012_09
_13/o1_mf_nnndf_TAG20120913T000925_85291pr4_.bkp
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
b
lo den
g
@ Stu
o
f
(in this
y
og use
l
o
hn se to
c
e
T cen
n
o
li
ti
e
a
l
rm erab
o
f
In ansf
l
a
b
tr
Glo non-
12:11:11
piece
handle=/u01/app/oracle/fast_recovery_area/CDB2/autobackup/2012_0
9_13/o1_mf_s_793843873_852957tb_.bkp comment=NONE
12:11:27
RMAN>
Chapter 6 - Page 8
a
2.
Perform a partial PDB backup of the tablespace ldata.
a.
A new RMAN command allows you to back up some data files of the pluggable
database.
RMAN> BACKUP TABLESPACE pdb2:ldata;
name=/u01/app/oracle/oradata/cdb2/pdb2_1/ldata_01.dbf
piece
_13/o1_mf_nnndf_TAG20120913T001139_85295w9g_.bkp
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
b
lo at d13-09-2012
en
Starting Control File and SPFILE Autobackup
g
u
12:11:43
o@ is St
f
n
i
(
piece
th
y
g
e
lo o us comment=NONE
o
9_13/o1_mf_s_793843903_852962yc_.bkp
n
h se t
c
e
Finished ControlTFile and
n SPFILE Autobackup at 13-09-2012
e
n
c
12:11:50
i
o
l
ti
a
le
b
m
r
a
foEXITsfer
RMAN>
n
I
al$ -tran
b
o
Gl non
Chapter 6 - Page 9
a
Practice 6-4: RMAN Recovery from SYSTEM PDB Data File Loss
Overview
In this practice, you will recover the PDB from an essential data file loss.
Tasks
1.
Remove the SYSTEM data file of PDB2.
$ sqlplus system/oracle_4U@PDB2
Connected to:
Testing options
SQL> select file_name from DBA_DATA_FILES
WHERE TABLESPACE_NAME='SYSTEM';
s
) ha
om ฺ
c
ฺ
ch ide
FILE_NAME
e
t
i
l- t Gu
a
-------------------------------------------------------------b
lo den
g
@ Stu
o
f
(in this
SQL> exit
y
og use
l
$
o
hn se to
c
e
T cen
n
$ rm /u01/app/oracle/oradata/cdb2/pdb2_1/system01.dbf
o
li
ti
e
a
l
bcdb2 with a user with SYSDBA or SYSBACKUP privilege.
2. Run RMAN to
connectrto
rm
a
o
f
e
n target
sf /
$ Irman
l
n
a
a
b n-tr
Glo nconnected
o
to target database: cdb2 (DBID=534631279)
RMAN>
3.
Proceed with the traditional procedure to restore the missing data file and recover the CDB
as it were a non-CDB.
RMAN> SHUTDOWN ABORT;
using target database control file instead of recovery catalog
Oracle instance shut down
RMAN> STARTUP MOUNT;
connected to target database (not started)
Oracle instance started
Chapter 6 - Page 10
a
database mounted
655556608 bytes
Fixed Size
Variable Size
Database Buffers
Redo Buffers
2276288
260047936
390070272
3162112
bytes
bytes
bytes
bytes
RMAN> RESTORE TABLESPACE pdb2:SYSTEM;
Starting restore at 13-SEP-12
s
) ha
channel ORA_DISK_1: starting datafile backup set restore
channel ORA_DISK_1: specifying datafile(s) to restore from
backup set
channel ORA_DISK_1: restoring datafile 00008 to
channel ORA_DISK_1: reading from backup piece
/u01/app/oracle/fast_recovery_area/CDB2/backupset/2012_09_13/o1_
mf_nnndf_TAG20120913T000925_85291pr4_.bkp
channel ORA_DISK_1: piece
tag=TAG20120913T000925
channel ORA_DISK_1: restored backup piece 1
channel ORA_DISK_1: restore complete, elapsed time: 00:00:15
Finished restore at 13-SEP-12
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
b
lo den
g
@ Stu
o
f
(in this
y
og use
l
o
hn se to
c
e
T cen
n
o
li
ti
e
a
l
rm erab
o
f
In ansf
l
a
b
tr
Glo nonRMAN> RECOVER TABLESPACE pdb2:SYSTEM;
Starting recover at 13-SEP-12
starting media recovery
media recovery complete, elapsed time: 00:00:01
Finished recover at 13-SEP-12
RMAN> ALTER DATABASE OPEN;
Statement processed
Chapter 6 - Page 11
a
RMAN> ALTER PLUGGABLE DATABASE ALL OPEN;
Statement processed
RMAN>
Or you could have used the new syntax to restore and recover a whole PDB, as follows:
RMAN> SHUTDOWN ABORT;
RMAN> startup mount;
database mounted
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
- t Gu
Fixed Size
2263616 bytes al
b
lo den
Variable Size
213910976 g
bytes
@bytesStu
o
Database Buffers
415236096
f
in thbytes
is
(3268608
Redo Buffers
y
og use
l
o
to pdb2;
hn database
RMAN> RESTORE pluggable
c
e
e
s
T cen
n
i
o
l13-SEP-12
ti
e
Starting restore
at
a
l
b ORA_DISK_1
rm channel:
a
r
o
allocated
f
e
In ORA_DISK_1:
sf
l
channelan
SID=21 device type=DISK
a
r
b
t
o
Gl non
634679296 bytes
backup set
tag=TAG20120913T000925
Chapter 6 - Page 12
a
backup set
/u01/app/oracle/oradata/cdb2/pdb2_1/ldata_01.dbf
mf_nnndf_TAG20120913T001139_85295w9g_.bkp
tag=TAG20120913T001139
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
b
lo den
g
@ Stu
o
f
(in this
y
media recovery complete, elapsed
se 00:00:02
og utime:
l
o
hn se to
ec13-SEP-12
Finished recoverTat
n
e
n
c
i
o
l
atiDATABASE
le OPEN;
RMAN> r
ALTER
b
m
a
fo sfer
n
I
alStatement
an processed
r
b
t
o
Gl non
RMAN> RECOVER pluggable database pdb2;
RMAN> select name, open_mode from v$pdbs;
NAME
-----------------------------PDB$SEED
PDB2
PDB2_2
PDB_ORCL2
PDB1_1
OPEN_MODE
---------READ ONLY
READ WRITE
READ WRITE
READ WRITE
READ WRITE
RMAN> exit
$
Chapter 6 - Page 13
a
Practice 6-5: RMAN Recovery from Non-Essential PDB Data File Loss
Overview
In this practice, you will recover from a non-essential PDB data file loss.
Assumptions
The LDATA tablespace has been successfully created in Practice 5-1.
Tasks
1.
Remove a data file of the LDATA tablespace of PDB2.
Connected to:
Testing options
s
) ha
om ฺ
c
ฺ
SQL> select file_name from dba_data_files
ch ide
e
t
i
l- t Gu
where tablespace_name='LDATA';
a
b
lo den
g
@ Stu
FILE_NAME
o
f
(in this
-------------------------------------------------------------y
og use
l
o
hn se to
c
e
T cen
SQL> exit
n
o
li
ti
$
e
a
l
rm erab
o
f
n nsf
Irm
l
$
a
ra
b n-t/u01/app/oracle/oradata/cdb2/pdb2_1/ldata_01.dbf
o
l
G no
Chapter 6 - Page 14
a
2.
Proceed with the traditional procedure to restore the missing data file and recover the
tablespace as if it were a non-CDB.
a. Put the tablespace in OFFLINE mode.
Connected to:
Testing options
SQL> ALTER TABLESPACE ldata OFFLINE IMMEDIATE;
Tablespace altered.
s
) ha
SQL> exit
$
om ฺ
c
ฺ
b. Run RMAN to connect to cdb2 with a user with SYSDBA or SYSBACKUP
ch privilege.
e
ide
t
i
u
$ rman target /
l
ba ent G
o
l
g tud
@
connected to target database: CDB2 o
(DBID=534631279)
nf this S
i
(
RMAN>
ogy use
l
c. Restore and recover the tablespace.
o
to
hn pdb2:LDATA;
RMAN> RESTORE TABLESPACE
c
e
e
s
T cen
n
i
o
l13-SEP-12
ti
e
Starting restore
at
a
l
b
m database
rtarget
a
r
o
using
control file instead of recovery catalog
f
e
f
n
I
s
alallocated
an channel: ORA_DISK_1
r
b
t
o
Gl nchannel
on ORA_DISK_1: SID=20 device type=DISK
backup set
tag=TAG20120913T001139
Chapter 6 - Page 15
a
RMAN> RECOVER TABLESPACE pdb2:LDATA;
Finished recover at 13-SEP-12
RMAN> exit
$
d.
Put the tablespace back ONLINE.
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
Connected to:
a
b
lo d12.1.0.0.2
en
Oracle Database 12c Enterprise Edition g
Release
u
t
@
64bit Production
o is S
(infMining
With the Partitioning, OLAP, y
Data
th and Real Application
g
e
Testing options
lo o us
o
n
t
hldataseONLINE;
c
e
SQL> ALTER TABLESPACE
T cen
n
Tablespace taltered.
o
li
i
e
a
l
rm erab
o
f
SQL>
In exit
sf
l
n
a
a
b $ n-tr
G3.loIf you
nodo not intend to perform any further practices on CDBs, shut down the cdb1 and
cdb2 instances if not dropped in Practice 3-6.
$ . oraenv
Connected to:
Testing options
SQL> shutdown immediate;
Chapter 6 - Page 16
a
Database closed.
SQL> exit
Disconnected from Oracle Database 12c Enterprise Edition Release
12.1.0.0.2 - 64bit Production
Testing options
$
$ . oraenv
The Oracle base remains unchanged with value /u01/app/oracle $
sqlplus / as sysdba
s
) ha
SQL*Plus: Release 12.1.0.0.2 Production on Thu Jul 5 09:15:29
2012
om ฺ
c
ฺ
ch ide
e
Copyright (c) 1982, 2012, Oracle. All rights reserved.
t
i
l- t Gu
a
b
lo den
g
@ Stu
o
f
Connected to:
in this
(Edition
y
og use Release 12.1.0.0.2 l
64bit Production
o
to
hnOLAP,
Data Mining and Real Application
c
e
e
s
T cen
Testing options
n
o
li
ti
e
a
l
b
rm eraimmediate;
SQL>fo
shutdown
In anclosed.
sf
Database
l
a
b n-tr dismounted.
Glo nDatabase
o
SQL> exit
$
Chapter 6 - Page 17
a
Practice 6-6: SQL PDB Hot Backup (optional)
Overview
In this practice, you will perform a hot backup of PDB2 in cdb2.
Assumptions
The PDB2 has been successfully created in cdb2 after Practices 3-1, 3-3, and 4-4.
Tasks
1.
List all data files belonging to PDB2 to be backed up.
Connected to:
Testing options
s
) ha
om ฺ
c
ฺ
ch ide
SQL> select file_name from dba_data_files;
e
t
i
l- t Gu
a
b
lo den
FILE_NAME
g
@ Stu
-------------------------------------------------------------o
f
(in this
y
og use
l
o
hn se to
c
e
T cen
n
o
li
ti
SQL>
e
a
l
b
rinmhot backup.
a
r
o
2. Set the n
PDB
f
e
I ALTER
sfPLUGGABLE DATABASE pdb2 BEGIN BACKUP;
l
n
a
SQL>
a
b
tr
Glo nonPluggable database altered.
SQL> exit
$
3.
Copy the data files of the pluggable database to a backup directory.
$ mkdir /home/oracle/backup
$ cp /u01/app/oracle/oradata/cdb2/pdb2_1/*.dbf
/home/oracle/backup
$
Chapter 6 - Page 18
a
4.
Deactivate the backup mode.
Connected to:
Testing options
SQL> ALTER PLUGGABLE DATABASE pdb2 END BACKUP;
SQL>
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
b
lo den
g
@ Stu
o
f
(in this
y
og use
l
o
hn se to
c
e
T cen
n
o
li
ti
e
a
l
rm erab
o
f
In ansf
l
a
b
tr
Glo non-
Chapter 6 - Page 19
a
Practice 6-7: SQL Control File Backup (optional)
Overview
In this practice, you will use the traditional SQL command to back up the cdb2 control file.
Tasks
1.
Connect to the cdb2 root.
SQL> CONNECT / as sysdba
Connected to:
Testing options
SQL>
s
) ha
m
o
c
ฺ
SQL> alter database backup controlfile to trace;
ch ideฺ
e
t
i
l- t Gu
a
b
Database altered.
lo den
g
@ Stu
o
f
SQL>
(in this
y
og use
l
o
hn se to
c
e
T cen
n
o
li
ti
e
a
l
rm erab
o
f
In ansf
l
a
b
tr
Glo non2.
Run the ALTER DATABASE command to back up the control file to a script.
Chapter 6 - Page 20
a
Practice 6-8: RMAN Recovery from Control File Loss (optional)
Overview
In this practice, you will recover the CDB from the control file loss.
Assumptions
Practice 6-2 successfully completed the whole CDB backup of cdb2.
Tasks
1.
Remove the control files of the CDB.
Connected to:
Testing options
s
) ha
om ฺ
c
ฺ
SQL> select name from v$controlfile;
ch ide
e
t
i
l- t Gu
a
b
lo den
NAME
g
@ Stu
-------------------------------------------------------------o
f
(in this
/u01/app/oracle/oradata/cdb2/control01.ctl
y
og use
l
o
hn se to
c
e
T cen
SQL> !rm /u01/app/oracle/oradata/cdb2/control01.ctl
n
o
li
ti
SQL>
e
a
l
b cdb2.
m instance
a
r
o
2. Shut down
/r
abort the
f
e
In shutdown
sf abort
l
n
SQL>
a
a
b n-tr
instance shut down.
Glo nORACLE
o
SQL> exit
$
3.
Proceed with the traditional procedure to restore the control files and recover the CDB as if
it were a non-CDB database.
$ rman target /
connected to target database (not started)
RMAN> startup nomount;
Fixed Size
634679296 bytes
2263616 bytes
Chapter 6 - Page 21
a
Variable Size
Database Buffers
Redo Buffers
226493888 bytes
402653184 bytes
3268608 bytes
RMAN> RESTORE CONTROLFILE FROM AUTOBACKUP;
Starting restore at 07-09-2012 08:40:42
recovery area destination: /u01/app/oracle/fast_recovery_area
database name (or database unique name) used for search: CDB2
channel ORA_DISK_1: AUTOBACKUP
/u01/app/oracle/fast_recovery_area/CDB2/autobackup/2012_09_07/o1
_mf_s_793355103_84mcv293_.bkp found in the recovery area
AUTOBACKUP search with format "%F" not attempted because DBID
was not set
channel ORA_DISK_1: restoring control file from AUTOBACKUP
_mf_s_793355103_84mcv293_.bkp
channel ORA_DISK_1: control file restore from AUTOBACKUP
complete
output file name=/u01/app/oracle/oradata/cdb2/control01.ctl
output file
name=/u01/app/oracle/fast_recovery_area/cdb2/control02.ctl
Finished restore at 07-09-2012 08:41:18
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
b
lo den
g
@ Stu
o
f
(in this
y
og use
l
o
hn se to
c
e
T cen
n
o
li
ti
e
a
l
rm erab
o
f
RMAN>
In ALTER
sf DATABASE MOUNT;
l
n
a
a
b n-tr
Glo nStatement
o
processed
released channel: ORA_DISK_1
RMAN> RECOVER DATABASE;
Starting recover at 07-09-2012 08:41:50
Starting implicit crosscheck backup at 07-09-2012 08:41:50
Crosschecked 6 objects
Finished implicit crosscheck backup at 07-09-2012 08:41:51
Starting implicit crosscheck copy at 07-09-2012 08:41:51
Chapter 6 - Page 22
a
Finished implicit crosscheck copy at 07-09-2012 08:41:51
searching for all files in the recovery area
cataloging files...
cataloging done
List of Cataloged Files
=======================
File Name:
_mf_s_793355103_84mcv293_.bkp
File Name:
/u01/app/oracle/fast_recovery_area/CDB2/archivelog/2012_09_07/o1
_mf_1_57_84md0zx0_.arc
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
- t Gonu disk as
lalready
archived log for thread 1 with sequence 57 is
a
b
file
lo den
g
@ Stu
o
f
_mf_1_57_84md0zx0_.arc
(in this
y
archived log for thread 1 with
g sequence
e 58 is already on disk as
s
o
l
u
o
file /u01/app/oracle/oradata/cdb2/redo01.log
hn se to
archived log file ec
T cen
name=/u01/app/oracle/fast_recovery_area/CDB2/archivelog/2012_09_
n
o
li
ti
07/o1_mf_1_57_84md0zx0_.arc
thread=1 sequence=57
e
a
l
b
m
r
a
archived
log
file
name=/u01/app/oracle/oradata/cdb2/redo01.log
fo sequence=58
er
f
n
I
s
thread=1
almedia-trrecovery
an
b
complete, elapsed time: 00:00:12
o
Gl nFinished
on
recover at 07-09-2012 08:42:08
RMAN> ALTER DATABASE OPEN RESETLOGS;
Statement processed
RMAN> select name, open_mode from v$pdbs;
NAME
-----------------------------PDB$SEED
PDB2
PDB2_2
OPEN_MODE
---------READ ONLY
READ WRITE
READ WRITE
Chapter 6 - Page 23
a
PDB_ORCL2
PDB1_1
READ WRITE
READ WRITE
RMAN>
4.
Back up the whole cdb2.
a.
Use the BACKUP command.
…
RMAN> exit
$
b.
If you encounter some space issues, like the following, reclaim some space and
increase the fast recovery area destination size:
RMAN-00571:
===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS
===============
RMAN-00571:
===========================================================
RMAN-03002: failure of backup plus archivelog command at
10/09/2012 03:46:44
ORA-19809: limit exceeded for recovery files
ORA-19804: cannot reclaim 67108864 bytes disk space from
10737418240 limit
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
b
lo den
g
@ Stu
o
f
(in this
y
g ubackups:
1) Reclaim some space deleting o
obsolete
se
l
o
RMAN> delete obsolete;
hn se to
c
e
RMAN retention policy
n be applied to the command
T cwill
e
n
i
o
l
RMAN retention
is set to redundancy 1
ti policy
e
a
l
b
m
using r
channel ra
ORA_DISK_1
o
f
e
f
n
Deleting
the
following
obsolete backups and copies:
I ans
l
a
b Type
tr
Key
Completion Time
Filename/Handle
Glo n-------------------on------ ------------------ ----------------Backup Set
44
13-SEP-12
Backup Piece
44
13-SEP-12
mf_nnndf_TAG20120913T000151_8528mvgr_.bkp
Backup Set
45
13-SEP-12
Backup Piece
45
13-SEP-12
mf_annnn_TAG20120913T000620_8528vwkw_.bkp
Backup Set
47
13-SEP-12
Backup Piece
47
13-SEP-12
Backup Set
49
13-SEP-12
Chapter 6 - Page 24
a
Backup Piece
49
13-SEP-12
Backup Set
51
13-SEP-12
Backup Piece
51
13-SEP-12
_mf_s_793845475_852bq621_.bkp
Do you really want to delete the above objects (enter YES or
NO)? Do you really want to delete the above objects (enter YES
or NO)? YES
deleted backup piece
backup piece
_13/o1_mf_nnndf_TAG20120913T000151_8528mvgr_.bkp RECID=44
STAMP=793843322
backup piece
_13/o1_mf_annnn_TAG20120913T000620_8528vwkw_.bkp RECID=45
STAMP=793843580
backup piece
_13/o1_mf_nnndf_TAG20120913T000925_85291pr4_.bkp RECID=47
STAMP=793843766
backup piece
_13/o1_mf_nnndf_TAG20120913T001139_85295w9g_.bkp RECID=49
STAMP=793843899
backup piece
9_13/o1_mf_s_793845475_852bq621_.bkp RECID=51 STAMP=793845477
Deleted 5 objects
RMAN>
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
b
lo den
g
@ Stu
o
f
(in this
y
og use
l
o
hn se to
c
e
T cen
n
o
li
ti
e
a
l
rm erab
o
f
In ansf
l
a
b
tr
Glo non-
2)
Increase the fast recovery area destination size to 20G.
RMAN> ALTER SYSTEM SET db_recovery_file_dest_size=20G
SCOPE=both;
Statement processed
RMAN> EXIT
$
Chapter 6 - Page 25
a
Practice 6-9: RMAN Recovery from Redo Log File Member Loss
(optional)
Overview
In this practice, you recover the cdb2 from a redo log file member loss.
Tasks
1.
Multiplex the redo log files if not already done.
$ sqlplus system/oracle_4U
Connected to:
Testing options
s
) ha
om ฺ
c
ฺ
ch ide
e
t
MEMBER
i
l- t Gu
a
-------------------------------------------------------------b
lo den
g
/u01/app/oracle/oradata/cdb2/redo03.log
@ Stu
o
f
(in this
y
og use
l
o
hn se to
c
SQL>
e
T cen
n
o
li
ti
e
a
l
b ADD LOGFILE MEMBER
SQL> ALTER
rm DATABASE
a
r
o
f
e
'/u01/app/oracle/oradata/cdb2/redo01_2.log'
In ansf
l
a
b TO GROUP
tr 1;
Glo nonSQL> select member from v$logfile;
Database altered.
SQL> ALTER DATABASE ADD LOGFILE MEMBER
TO GROUP 2;
Database altered.
TO GROUP 3;
Database altered.
Chapter 6 - Page 26
a
SQL>
SQL> alter system switch logfile;
System altered.
System altered.
System altered.
s
) ha
om ฺ
c
ฺ
ch ide
System altered.
e
t
i
l- t Gu
a
b
lo den
SQL> exit
g
@ Stu
o
$
f
(in this
y
2. Remove a redo log file member of the cdb2.
og use
l
o
$ rm /u01/app/oracle/oradata/cdb2/redo01.log
hn se to
c
$
e
T cen
n
o
li to regenerate the redo log file member. If you
3. Proceed with the traditional
procedure
i
t
e
a
l
encounter any
berror, execute the alter system switch logfile
rmORA-01609
a
r
o
f
e
command
until
the
redo
log
file is in INACTIVE status (view the STATUS in V$LOG view).
n nsf
I
l
ba$ sqlplus
tra system/oracle_4U
o
l
n
G no
Connected to:
Testing options
SQL> ALTER DATABASE DROP LOGFILE MEMBER
'/u01/app/oracle/oradata/cdb2/redo01.log';
Database altered.
'/u01/app/oracle/oradata/cdb2/redo01.log'
Chapter 6 - Page 27
a
TO GROUP 1;
Database altered.
SQL> exit
$
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
b
lo den
g
@ Stu
o
f
(in this
y
og use
l
o
hn se to
c
e
T cen
n
o
li
ti
e
a
l
rm erab
o
f
In ansf
l
a
b
tr
Glo non-
Chapter 6 - Page 28
a
Practice 6-10: RMAN Recovery from SYSTEM Root Data File Loss
(optional)
Overview
In this practice, you will recover from a root data file loss, particularly the SYSTEM data file.
Tasks
1.
Remove the SYSTEM data file from the root SYSTEM tablespace.
Connected to:
Testing options
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
FILE_NAME
b
lo den
g
---------------------------------------------------------@ Stu
o
f
(in this
y
og use
l
o
SQL> exit
hn se to
c
$
e
T cen
n
o
li
ti
e
a
l
$ rm /u01/app/oracle/oradata/cdb2/system01.dbf
rm erab
o
f
In ansf
l
a
b
tr
Glo nonSQL> select file_name from DBA_DATA_FILES
WHERE TABLESPACE_NAME='SYSTEM';
Chapter 6 - Page 29
a
2.
Run RMAN to connect to cdb2 with a user with SYSDBA or SYSBACKUP privilege.
$ rman target /
RMAN-00571: =================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS =====
RMAN-00571: =================================================
RMAN-00554: initialization of internal recovery manager package
failed
RMAN-04005: error from target database:
ORA-00604: error occurred at recursive SQL level 1
ORA-01116: error in opening database file 1
ORA-01110: data file 1:
'/u01/app/oracle/oradata/cdb2/system01.dbf'
ORA-27041: unable to open file
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3
$
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
b
lo den
g
@ Stu
Connected to:
o
f
in thRelease
is
Oracle Database 12c Enterprise (Edition
12.1.0.1.0 y
g
e
64bit Production
lo Advanced
us Analytics and Real
o
n
o
OLAP,
t
h se
Application Testing
ecoptions
n
T
e
n
c
i
o
l
ti
a
le
b
m
SQL> SHUTDOWN
ABORT
r
a
fo instance
er shut down.
f
n
ORACLE
I
s
alSQL>-tSTARTUP
an MOUNT
r
b
o
Gl nOracle
on instance started
3.
Proceed with the traditional procedure to restore the missing data file and recover the CDB
as it were a non-CDB.
Fixed Size
2298064 bytes
Variable Size
1040191280 bytes
Database Buffers
3959422976 bytes
Redo Buffers
8773632 bytes
Database mounted.
SQL> exit
$
$ rman target /
connected to target database: CDB2 (DBID=562519177, not open)
RMAN> RESTORE TABLESPACE SYSTEM;
Chapter 6 - Page 30
a
backup set
mf_nnndf_TAG20120907T085859_84mftokq_.bkp
_07/o1_mf_nnndf_TAG20120907T085859_84mftokq_.bkp
tag=TAG20120907T085859
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
b
lo den
g
@ Stu
o
f
(in this
y
og use
l
o
channel ORA_DISK_1: starting
backup set restore
to
hn se datafile
c
e
channel ORA_DISK_1:
datafile(s) to restore from
T specifying
cen
i
backup set tion
l
a
le restoring datafile 00001 to
b
channel
ORA_DISK_1:
m
r
a
fo sfer
n
I
alchannel
anORA_DISK_1: reading from backup piece
r
b
t
o
Gl n/u01/app/oracle/fast_recovery_area/CDB2/backupset/2012_09_07/o1_
on
mf_nnndf_TAG20120907T085859_84mftokq_.bkp
_07/o1_mf_nnndf_TAG20120907T085859_84mftokq_.bkp
tag=TAG20120907T085859
RMAN> RECOVER TABLESPACE SYSTEM;
Chapter 6 - Page 31
a
archived log for thread 1 with sequence 4 is already on disk as
file
_mf_1_4_84mg9v6y_.arc
file
_mf_1_5_84mgns9p_.arc
file
_mf_1_6_84mgntkz_.arc
file
_mf_1_7_84mgnyld_.arc
file
_mf_1_8_84mgnxtq_.arc
archived log file
07/o1_mf_1_4_84mg9v6y_.arc thread=1 sequence=4
archived log file
07/o1_mf_1_5_84mgns9p_.arc thread=1 sequence=5
archived log file
07/o1_mf_1_6_84mgntkz_.arc thread=1 sequence=6
Finished recover at 07-09-2012 09:25:04
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
b
lo den
g
@ Stu
o
f
(in this
y
og use
l
o
hn se to
c
e
T cen
n
o
li
ti
e
a
l
rm erab
o
f
In ansf
l
a
b
tr
Glo nonRMAN> ALTER DATABASE OPEN;
Statement processed
RMAN>
4.
Back up the CDB.
RMAN> BACKUP DATABASE PLUS ARCHIVELOG DELETE INPUT;
…
RMAN> exit
$
Chapter 6 - Page 32
a
Practice 6-11: RMAN Recovery from Non-Essential Root Data File
Loss (optional)
Overview
In this practice, you will recover from a non-essential root data file loss.
Tasks
1.
Remove a data file of the SYSAUX tablespace of the root of cdb2.
Connected to:
Testing options
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
FILE_NAME
b
lo den
g
------------------------------------------------------------@ Stu
o
f
(in this
y
og use
l
SQL> !rm /u01/app/oracle/oradata/cdb2/sysaux01.dbf
o
hn se to
c
SQL> EXIT
e
T cen
n
$
o
li
i
t
e
a
l
2. Run RMAN tom
to b
cdb2 with a user with SYSDBA or SYSBACKUP privilege.
r connect
a
r
o
f
e
$ Irman
n target
sf /
l
n
a
a
b n-tr
Glo nconnected
o
to target database: CDB2 (DBID=534631279)
SQL> select file_name from dba_data_files
where tablespace_name='SYSAUX';
RMAN>
3.
Proceed with the traditional procedure to restore the missing data file and recover the
tablespace as it were a non-CDB.
RMAN> ALTER TABLESPACE sysaux OFFLINE IMMEDIATE;
Statement processed
RMAN> RESTORE TABLESPACE sysaux;
Chapter 6 - Page 33
a
backup set
mf_nnndf_TAG20120907T093436_84mhxgdw_.bkp
_07/o1_mf_nnndf_TAG20120907T093436_84mhxgdw_.bkp
tag=TAG20120907T093436
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
b
lo den
g
@ Stu
o
f
(in this
y
media recovery complete, elapsed
se 00:00:02
og utime:
l
o
hn se to09:59:36
ec07-09-2012
Finished recoverTat
n
e
n
c
i
o
l
tiTABLESPACE
RMAN> ALTER
a
le sysaux ONLINE;
b
m
r
a
fo sfer
n
I
alStatement
an processed
r
b
t
o
Gl non
RMAN> exit
RMAN> RECOVER TABLESPACE sysaux;
$
Chapter 6 - Page 34
a
Practice 6-12: PITR on PDB Tablespaces (optional)
Overview
In this practice, you will perform a PITR on a non-essential PDB data file. Rows in a table in the
PDB2_2 pluggable database TEST_TBS tablespace have been incorrectly deleted. You have to
restore the situation to the time before the rows were deleted and committed.
Assumptions
The PDB pdb2_2 has been successfully created after completion of Practice 3-4.
Tasks
1.
Set the situation where deleted rows have been committed.
a. Create a TEST_TBS tablespace in PDB2_2, a local user LOCAL_TEST, and a table.
$ sqlplus sys/oracle_4U@PDB2_2 as sysdba
Connected.
SQL> create tablespace test_pdb datafile
'/u01/app/oracle/oradata/cdb2/pdb2_2/test_pdb1.f' size 3m;
s
) ha
om ฺ
c
ฺ
ch ide
Tablespace created.
e
t
i
l- t Gu
a
b
lo den
SQL>
g
@ Stu
o
f
(in thbyis p
y
SQL> create user local_test gidentified
se
o
l
u
o
default tablespace
test_pdb;
hn se to
c
e
T cen
n
User created.
o
li
ti
e
a
l
rm erab
o
f
SQL>
In ansf
l
a
b n-tr
Glo nSQL>
o grant create session, create table, unlimited tablespace
to local_test;
Grant succeeded.
SQL> EXIT
$
b.
Back up the new tablespace.
$ rman target /
connected to target database: CDB2 (DBID=540373866)
RMAN> backup pluggable database pdb2_2;
Chapter 6 - Page 35
a
name=/u01/app/oracle/oradata/cdb2/pdb2_2/CDB2/C3DCC6FF8EFD51EEE0
43160200C0E8F2/datafile/o1_mf_sysaux_7z3o334q_.dbf
43160200C0E8F2/datafile/o1_mf_system_7z3o333q_.dbf
43160200C0E8F2/datafile/o1_mf_ldata_7z3o3b4z_.dbf
43160200C0E8F2/datafile/o1_mf_users_7z3o3b2h_.dbf
name=/u01/app/oracle/oradata/cdb2/pdb2_2/test_pdb1.f
piece
_02/o1_mf_nnndf_TAG20120702T171416_7z3oq86v_.bkp
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
b
lo den
g
@ Stu
o
f
(in this
y
og use
l
o
hn se to
c
e
T cen
n
o
li
ti
e
a
l
bFile and SPFILE Autobackup at 02-07-2012
Starting
rmControl
a
r
o
f
e
05:14:31
In ansf
l
a
piece
b n-tr
Glo nhandle=/u01/app/oracle/fast_recovery_area/CDB2/autobackup/2012_0
o
7_02/o1_mf_s_787598071_7z3oqqbf_.bkp comment=NONE
05:14:32
RMAN> exit
$
c.
Create a table with 4 rows, check the SCN, delete 2 rows and recheck the SCN.
$ sqlplus sys/oracle_4U@PDB2_2 as sysdba
Connected to:
SQL> create table local_test.tab_test (c number);
Chapter 6 - Page 36
a
Table created.
SQL> insert into local_test.tab_test values (1);
1 row created.
1 row created.
1 row created.
s
) ha
om ฺ
c
ฺ
1 row created.
ch ide
e
t
i
l- t Gu
a
b
SQL> commit;
lo den
g
@ Stu
o
f
(in this
Commit complete.
y
og use
l
o
SQL> select timestamp_to_scn(sysdate)
from v$database;
hn se to
c
e
n
T
n
ce
i
o
l
i
t
TIMESTAMP_TO_SCN(SYSDATE)
a
le
b
m
r
a
-------------------------fo sfer
n
I
1861446
l
n
a
a
r
b
t
Glo nSQL>
on- delete from local_test.tab_test where rownum < 3;
2 rows deleted.
SQL> commit;
Commit complete.
SQL> select * from local_test.tab_test;
C
---------3
Chapter 6 - Page 37
a
4
SQL> exit
$
3.
Set the situation back when rows were all present in the table.
There are three solutions.
•
An incomplete CDB recovery. Start the CDB in mount state.
•
PDB tablespace Point-In-Time Recovery in PDB2_2: If you intend to perform a PDB
tablespace Point-In-Time Recovery, you must drop the OPEN_ALL_PDBS trigger before
proceeding.
•
PDB Point-In-Time Recovery.
The following steps show how to perform a PDB Point-In-Time Recovery.
a. Connect to cdb2 and close PDB2_2.
$ rman target /
s
) ha
om ฺ
c
ฺ
ch ide
RMAN> ALTER PLUGGABLE DATABASE pdb2_2 CLOSE;
e
t
i
l- t Gu
a
b
lo of recovery
en catalog
using target database control file instead
g
d
u
o@ is St
Statement processed
f
n
i
(
th
y
g
e
lo o us
RMAN>
o
n
t back to the SCN before the delete.
h sdatabase
c
e
b. Restore and recover theepluggable
T cen
RMAN> RUN { ion
li
t
e
a
l
SET UNTIL
SCN = b
1861446;
rmPLUGGABLE
a
r
o
f
e
RESTORE
DATABASE pdb2_2;
n nsf
I
l
baRECOVER
tra PLUGGABLE DATABASE pdb2_2 AUXILIARY
o
l
n
DESTINATION='/u01/app/oracle/oradata';
G no
ALTER PLUGGABLE DATABASE pdb2_2 OPEN RESETLOGS;
}
executing command: SET until clause
backup set
/u01/app/oracle/oradata/cdb2/pdb2_2/CDB2/DCBF06D282BC62C8E043652
3B98BA901/datafile/o1_mf_system_8s6p6w8q_.dbf
Chapter 6 - Page 38
a
/u01/app/oracle/oradata/cdb2/pdb2_2/CDB2/DCBF06D282BC62C8E043652
3B98BA901/datafile/o1_mf_sysaux_8s6p6w92_.dbf
/u01/app/oracle/oradata/cdb2/pdb2_2/test_pdb1.f
mf_nnndf_TAG20130516T085734_8s97vz9y_.bkp
_16/o1_mf_nnndf_TAG20130516T085734_8s97vz9y_.bkp
tag=TAG20130516T085734
s
) ha
RMAN-05026: WARNING: presuming following set of tablespaces
applies to specified Point-in-Time
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
b
lo den
g
tu
@
o
List of tablespaces expected to have
UNDO segments
S
f
(in this
Tablespace SYSTEM
y
og use
l
Tablespace UNDOTBS1
o
hn se to
c
e
n with SID='qgkd'
T instance,
e
Creating automatic
n
c
i
o
l
ti
a
le
b
m
r
a
initialization
fo sfer parameters used for automatic instance:
n
I
aldb_name=CDB2
an
r
b
t
o
Gl ndb_unique_name=qgkd_pitr_pdb2_2_CDB2
on
compatible=12.0.0.0.0
db_block_size=8192
db_files=200
sga_target=1G
processes=80
diagnostic_dest=/u01/app/oracle
db_create_file_dest=/u01/app/oracle/oradata
log_archive_dest_1='location=/u01/app/oracle/oradata'
enable_pluggable_database=true
_clone_one_pdb_recovery=true
#No auxiliary parameter file used
Chapter 6 - Page 39
a
starting up automatic instance CDB2
…
sql statement: alter database open read only
Removing automatic instance
Automatic instance removed
auxiliary instance file
/u01/app/oracle/oradata/CDB2/datafile/o1_mf_sysaux_8s98gkgd_.dbf
deleted
/u01/app/oracle/oradata/CDB2/controlfile/o1_mf_8s98g4tr_.ctl
deleted
s
) ha
om ฺ
c
ฺ
ch ide
Statement processed
e
t
i
l- t Gu
a
b
lo den
RMAN> exit
g
@ Stu
o
$
f
is
(in ttable.
h
y
c. Check the content of the local_test.tab_test
e
og asussysdba
l
o
$ sqlplus sys/oracle_4U@pdb2_2
hn se to
c
e
T cen
n
Connected to:
o
li
i
t
e
a
l
Oracle m
Database b
12c Enterprise Edition Release 12.1.0.0.2 rProduction
a
r
o
64bit
f
e
In anPartitioning,
sf
l
With the
OLAP, Data Mining and Real Application
a
b Testing
tr options
o
l
n
G no
SQL> select * from local_test.tab_test;
C
---------1
2
3
4
SQL> EXIT
$
Chapter 6 - Page 40
a
d.
Back up the CDB.
$ rman target /
RMAN> DELETE OBSOLETE;
RMAN retention policy will be applied to the command
RMAN retention policy is set to redundancy 1
Deleting the following obsolete backups and copies:
…
Do you really want to delete the above objects (enter YES or
NO)? yes
…
Deleted 5 objects
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
b
RMAN> BACKUP DATABASE PLUS ARCHIVELOG delete
all
n
lo deinput;
g
u
…
o@ is St
f
n
RMAN> exit
i
(
th
y
g
e
$
lo o us
o
n
h se t
c
e
T cen
n
o
li
ti
e
a
l
rm erab
o
f
In ansf
l
a
b
tr
Glo non-
Chapter 6 - Page 41
a
Practice 6-13: Flashback from Common User Drop (optional)
Overview
In this practice, you will flash back the CDB after a common user has been dropped.
Assumptions
The C##_USER common user exists in cdb2. This has been completed in practice 5-2.
Tasks
1.
Set the CDB cdb2 in FLASHBACK mode.
$ export NLS_DATE_FORMAT='DD-MM-YYYY HH:MI:SS'
Connected to:
Testing options
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
SQL> SELECT flashback_on from V$DATABASE;
a
b
lo den
g
@ Stu
FLASHBACK_ON
o
f
(in this
-----------------y
og use
NO
l
o
hn se to
c
e
T cen
SQL> SHUTDOWN n
IMMEDIATE
o
li
ti
Database closed.
e
a
l
b
rmdismounted.
a
Database
r
o
f
e
In ainstance
sf shut down.
l
ORACLE
n
a
b n-tr
Glo nSQL>
o STARTUP MOUNT
Fixed Size
2248280 bytes
Variable Size
281018792 bytes
Database Buffers
780140544 bytes
Redo Buffers
5529600 bytes
Database mounted.
SQL> ALTER SYSTEM SET
DB_FLASHBACK_RETENTION_TARGET=2880 SCOPE=BOTH;
Chapter 6 - Page 42
a
System altered.
SQL> ALTER DATABASE FLASHBACK ON;
Database altered.
Database altered.
SQL>
2.
Drop the common user C##_USER.
a.
Verify that C##_USER exists as a common user.
s
) ha
om ฺ
c
ฺ
ch ide
USERNAME
COM
CON_ID
e
t
i
l- t Gu
a
-------------------- --- ---------b
lo den
g
C##_USER
YES
1
@ Stu
o
f
C##_USER
YES
3
(in 4 this
y
C##_USER
YES
og us5 e
l
C##_USER
YES
o
n e to
hYES
c
C##_USER
6
e
s
n
T
e
n
o
lic
i
t
e
a
l
SQL> select
timestamp_to_scn(current_timestamp)
from v$database;
b
m
r
a
r
o
nf nsfe
I
l
ra
baTIMESTAMP_TO_SCN(CURRENT_TIMESTAMP)
t
o
l
n
G n-----------------------------------o
2455483
SQL>
b.
Drop the user.
SQL> DROP USER C##_USER CASCADE;
User dropped.
System altered.
Chapter 6 - Page 43
a
System altered.
System altered.
System altered.
SQL>
3.
Proceed with the flashback database operation.
Database closed.
s
) ha
om ฺ
c
ฺ
ch ide
SQL> STARTUP MOUNT
e
t
i
l- t Gu
a
b
lo den
g
@ Stu
o
Total System Global Area 1068937216
bytes
f
is
(in bytes
h
Fixed Size
2248280
t
y
g usebytes
o281018792
l
Variable Size
o
to bytes
hn s780140544
Database Buffers
c
e
e
n 5529600 bytes
e
Redo Buffers n T
c
i
o
l
ti
Database mounted.
a
le
b
m
r
a
fo sfer
n
I
DATABASE TO SCN 2455483;
alSQL>-tFLASHBACK
an
r
b
o
Gl non
Flashback complete.
SQL>
Chapter 6 - Page 44
a
4.
Open the database in READ ONLY mode to review changes before opening CDB with
RESETLOGS.
SQL> ALTER DATABASE OPEN READ ONLY;
Database altered.
USERNAME
COM
CON_ID
-------------------- --- ---------C##_USER
YES
1
SQL>
5.
Open PDBs in READ ONLY to review all changes.
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
b
locdb_users
en
g
SQL> select USERNAME, COMMON, CON_ID from
d
u
@ St
where username='C##_USER'; nfo
i
is
(
h
t
y
se
og CON_ID
l
u
USERNAME
COM
o
n e to
h--c
----------------------------e
s
n
T
e
n
C##_USER
YES
1
ic
o
l
i
t
e
a
C##_USER
3
bl YES
m
r
a
r
o
C##_USER
YES
4
nf nsfe
I
l
YES
5
ra
baC##_USER
t
o
l
n
YES
6
G nC##_USER
o
SQL> ALTER PLUGGABLE DATABASE ALL OPEN READ ONLY;
SQL>
6.
Open the CDB with RESETLOGS.
Database closed.
SQL> STARTUP MOUNT
Fixed Size
2248280 bytes
Chapter 6 - Page 45
a
Variable Size
Database Buffers
Redo Buffers
Database mounted.
281018792 bytes
780140544 bytes
5529600 bytes
SQL> FLASHBACK DATABASE TO SCN 2455483;
Flashback complete.
SQL> ALTER DATABASE OPEN RESETLOGS;
Database altered.
SQL>
7.
Check that the C##_USER can connect in each container.
SQL> connect C##_USER/x
Connected.
SQL> connect C##_USER/x@PDB2
Connected.
SQL> connect C##_USER/x@PDB2_2
Connected.
SQL> exit
$
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
b
lo den
g
@ Stu
o
f
8. Back up the CDB.
(in this
y
og use
$ rman target /
l
o
hn se to
c
e
n CDB2 (DBID=534631279)
T database:
connected to target
e
n
c
i
o
l
ti
a
le
b
m
a
RMAN>or
BACKUP DATABASE
PLUS ARCHIVELOG delete all input;
r
f
e
f
n
l… I rans
a
b
t
Glo nRMAN>
on- exit
$
Chapter 6 - Page 46
a
s
) ha
om ฺ
c
ฺ
ch7: Heat
e
ide
t
i
u
l
Map, Automatic
G
t
ba Data
n
o
l
g and
Optimization
deOnline
u
t
@
S
Datafile
nfo Move
s
i
i
(
h
y se t
gChapter
o
l
u7
o
n
o
t
ech ense
T
n
o
lic
i
t
e
a
l
rm erab
o
f
In ansf
l
a
b
tr
Glo non-
Practices for Lesson 7: Heat Map, Automatic Data Optimization and Online Datafile Move
Chapter 7 - Page 1
a
Practices Overview
In these practices, you will exercise yourself on new features of ILM and Online Move
operations.
In the first practices, you will exercise yourself on new features of ILM and more precisely on
Heat Map and Automatic Data Optimization (ADO).
In the last practice, you will exercise yourself on moving datafiles online.
Assumptions
The environment is prepared beforehand, namely installed an Oracle database 12c non-CDB
orcl. The ILM new features are not supported in a multitenant container database (CDB). Any
attempt to enable this feature will raise user exceptions.
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
b
lo den
g
@ Stu
o
f
(in this
y
og use
l
o
hn se to
c
e
T cen
n
o
li
ti
e
a
l
rm erab
o
f
In ansf
l
a
b
tr
Glo non-
Chapter 7 - Page 2
a
Practice 7-1: Enabling Heat Map
Overview
In this practice, you will enable activity tracking or heat map.
Tasks
1.
Perform several operations to cleanup any existing ADO policies and tablespaces.
a. Make sure you are in the ~/labs/ADO directory.
$ cd ~/labs/ADO
$
b.
Ensure your environment points to the orcl instance.
$ . oraenv
ORACLE_SID = [orcl] ? orcl
$
c.
Start the orcl instance up.
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
b
lo den
g
SQL> startup
@ Stu
o
f
(in this
y
g use
o400846848
l
o
n e to bytes
h
c
Fixed Size
bytes
e en2271568
s
T
n
Variable Size
io le lic 339740336 bytes
t
a
Database
50331648 bytes
b
rmBuffers
a
r
o
f
e
Redo
8503296 bytes
In Buffers
sf
l
n
a
a
Database
mounted.
b n-tr
Glo nDatabase
opened.
o
SQL> EXIT
$
d.
Run the ADO_cleanup.sh script to cleanup any existing ADO policy and tablespaces.
$ ./ADO_cleanup.sh
$
2.
Set the HEAT_MAP instance parameter to ON at the instance scope.
Chapter 7 - Page 3
a
Connected to:
Application Testing and Unified Auditing options
SQL> ALTER SYSTEM SET heat_map=on SCOPE=BOTH;
System altered.
SQL> EXIT
$
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
b
lo den
g
@ Stu
o
f
(in this
y
og use
l
o
hn se to
c
e
T cen
n
o
li
ti
e
a
l
rm erab
o
f
In ansf
l
a
b
tr
Glo non-
Chapter 7 - Page 4
a
Practice 7-2: Automatic Data Optimization – Creating a TIER Policy
Overview
ADO allows you to automate the movement of a segment to another tablespace under certain
circumstances. The default implicit condition under which the tiering policy would automatically
move a table to another tablespace is based on the fullness of the source tablespace where the
table resides in.
In this practice, you will create and enable an ADO tiering policy on the SCOTT.EMPLOYEE
table. The policy will move the table to the LOW_COST_STORAGE tablespace when the source
ILMTBS tablespace where the table resides on is less than 95% free.
Tasks
1.
Set up the environment before creating the tiering storage ADO policy on
SCOTT.EMPLOYEE table.
a.
Run the ADO_setup.sh script to ensure that the user SCOTT has the required
privileges to execute the various SELECT statements on dictionary views.
$ ./ADO_setup.sh
$
s
) ha
om ฺ
c
ฺ
b. Create the ADOTBS tablespace to store the SCOTT.EMPLOYEE and insert
e the
ch rowsidinto
e
t
i
SCOTT.EMPLOYEE table.
l- t Gu
a
b
lo den
g
@ Stu
o
f
Connected to:
(in this
y
se Release 12.1.0.0.2 og Edition
l
u
o
64bit Production
to
hnOLAP,
c
e
e
s
Advanced
Analytics, Real
n
T and
e
n
Application Testing
Unified
Auditing
options
ic
o
l
i
t
e
a
bl
m
r
a
r
o
SQL>
feTABLESPACE adotbs
nf CREATE
I
s
l
n
ba DATAFILE
tra '/u01/app/oracle/oradata/orcl/adotbs1.dbf'
o
l
n
G nosize 10m reuse autoextend off extent management local;
2
3
Tablespace created.
SQL>
c.
Create the tablespace LOW_COST_STORE where the SCOTT.EMPLOYEE table may be
moved to due to space pressure.
SQL> CREATE TABLESPACE low_cost_store
DATAFILE '/u01/app/oracle/oradata/orcl/lcs.dbf'
size 200M;
2
3
Tablespace created.
Chapter 7 - Page 5
a
SQL>
2.
Create and store the SCOTT.EMPLOYEE table on the ILMTBS tablespace and blow it up
with about 3500 rows. The rows inserted should raise the percentage of empty space in
ILMTBS tablespace to less than 95%. When the ILM policy will be created and evaluated,
this will trigger an ADO action to move the segment to the LOW_COST_STORE tablespace.
a.
Create and store the SCOTT.EMPLOYEE table on the ADOTBS tablespace and blow it
up with about 3500 rows.
SQL> CONNECT scott/oracle_4U
Connected.
SQL> drop table employee purge;
drop table employee purge
*
ERROR at line 1:
ORA-00942: table or view does not exist
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
b
lo den
g
@ Stu
o
f
(in this
y
og use
l
o
hn se to
c
e
T cen
n
o
li
ti
e
a
l
rm erab
o
f
10
11
In ansf
l
a
b
tr
Glo nonSQL> create table employee (
EMPNO
NUMBER(4) NOT NULL,
ENAME
VARCHAR2(10),
JOB
VARCHAR2(9),
MGR
NUMBER(4),
HIREDATE DATE,
SAL
NUMBER(7,2),
COMM
NUMBER(7,2),
DEPTNO
NUMBER(2)
)
tablespace adotbs;
2
3
4
5
6
7
8
9
Table created.
SQL> insert into employee (empno, ename, job, mgr, hiredate,
sal, comm, deptno)
select empno, ename, job, mgr, hiredate, sal, comm, deptno from
emp;
2
14 rows created.
SQL> declare
blowup PLS_INTEGER := 8;
sql_test clob;
begin
for i in 1..blowup loop
sql_test := 'insert /*+ append */ into employee
Chapter 7 - Page 6
a
select * from
execute immediate sql_test;
commit;
end loop;
end;
scott.employee';
/
2
3
4
5
6
7
8
9
10
11
SQL> SELECT count(*) FROM scott.employee;
COUNT(*)
---------3584
SQL>
s
) ha
om ฺ
c
ฺ
ch ide
SQL> alter session set nls_date_format='dd-mon-yy
hh:mi:ss';
e
t
i
l- t Gu
a
b
lo den
Session altered.
g
@ Stu
o
f
(in this
SQL> COL object_name FORMAT A12
y
ogA10 use
l
SQL> COL "Seg write" FORMAT
o
to
hn to_char(track_time,'DD-MON-YY
SQL> SELECT object_name,
c
e
e
s
n segment_write "Seg write", FULL_SCAN
T Time",
HH:MI:SS') "Tracking
e
n
c
i
o
l
"Full Scan",
"Lookup Scan"
ti lookup_scan
e
a
l
b
m
FROM DBA_HEAT_MAP_SEG_HISTOGRAM
r
ra
o
f
e
f
n
I object_name='EMPLOYEE';
lWHERE
ns
a
a
r
b
t
2
3
Glo nonb.
Verify that heat map statistics are already collected.
OBJECT_NAME Tracking Time
Seg write Ful Loo
------------ ------------------------ ---------- --- --EMPLOYEE
06-MAR-13 12:29:32
YES
YES NO
SQL> SELECT object_name, segment_write_time, FULL_SCAN,
lookup_scan
FROM dba_heat_map_segment
WHERE object_name='EMPLOYEE';
2
3
OBJECT_NAME SEGMENT_WRITE_TIME FULL_SCAN
LOOKUP_SCAN
------------ ------------------ ------------------ ----------EMPLOYEE
06-mar-13 12:53:07 06-mar-13 12:53:07
Chapter 7 - Page 7
a
SQL> COL "Seg_write" FORMAT A10
SQL> COL "Seg_read" FORMAT A10
SQL> SELECT OBJECT_NAME, TRACK_TIME, SEGMENT_WRITE "Seg_write",
SEGMENT_READ "Seg_read", FULL_SCAN, LOOKUP_SCAN
FROM v$heat_map_segment
2
3
4
OBJECT_NAME TRACK_TIME
Seg_write Seg_read
FUL LOO
------------ ------------------ ---------- ---------- --- --EMPLOYEE
06-mar-13 12:53:44 NO
NO
NO NO
SQL>
c.
Check the current free space in ADOTBS tablespace.
col tablespace format A16
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
b
lo den
g
@ Stu
o
f
(in this
y
og use
l
o
hn se to
c
e
T cen
n
o
li
ti
e
a
l
rm erab
o
f
In ansf
l
a
r tablespace format A16
b n-tcol
Glo nSQL>
o
SQL> SELECT /* + RULE */ df.tablespace_name "Tablespace",
SELECT /* + RULE */ df.tablespace_name "Tablespace",
df.bytes / (1024 * 1024) "Size (MB)",
SUM(fs.bytes) / (1024 * 1024) "Free (MB)",
Nvl(Round(SUM(fs.bytes) * 100 / df.bytes),1) "% Free",
Round((df.bytes - SUM(fs.bytes)) * 100 / df.bytes) "% Used"
FROM dba_free_space fs,
(SELECT tablespace_name,SUM(bytes) bytes
FROM dba_data_files
GROUP BY tablespace_name) df
WHERE fs.tablespace_name (+) = df.tablespace_name
GROUP BY df.tablespace_name,df.bytes
Order by 4;
df.bytes / (1024 * 1024) "Size (MB)",
FROM dba_data_files
Order by 4;
2
3
4
5
6
7
8
9
10
11
12
Chapter 7 - Page 8
a
Tablespace
Size (MB) Free (MB)
% Free
% Used
---------------- ---------- ---------- ---------- ---------SYSTEM
900
5
1
99
SYSAUX
7590
363.9375
5
95
USERS
8.75
.8125
9
91
EXAMPLE
358.125
33.6875
9
91
UNDOTBS1
165
139.6875
85
15
ADOTBS
10
8.6875
87
13
LOW_COST_STORE
200
199
100
1
7 rows selected.
SQL>
3.
Create a storage tiering policy on SCOTT.EMPLOYEE table.
SQL> ALTER TABLE scott.employee ILM ADD POLICY TIER TO
low_cost_store;
s
) ha
om ฺ
c
ฺ
Table altered.
ch ide
e
t
i
l- t Gu
a
b
lo den
SQL>
g
tu the following error
@
o
S
Note: If you had not enabled the heat map, you would
have received
f
(in this
message:
y
seADD POLICY TIER TO
og ILM
l
SQL> ALTER TABLE scott.employee
u
o
low_cost_store;
hn se to
c
e
T cen ILM ADD POLICY TIER TO low_cost_store
ALTER TABLE scott.employee
n
o
li
ti
*
e
a
l
ratmlineera1:b
ERROR
o
f
In ansfheat map not enabled
ORA-38342:
l
a
b n-tr
Glo nSQL>
o
4.
Verify that the policy is added.
SQL> COL policy_name format A12
SQL> COL TIER_TBS format A20
SQL> SELECT policy_name, action_type, scope,
tier_tablespace "TIER_TBS"
FROM user_ilmdatamovementpolicies
ORDER BY policy_name;
2
3
4
POLICY_NAME ACTION_TYPE SCOPE
TIER_TBS
------------ ----------- ------- -------------------P304
STORAGE
SEGMENT LOW_COST_STORE
Chapter 7 - Page 9
a
SQL> SELECT policy_name, object_name, inherited_from, enabled
FROM user_ilmobjects;
POLICY_NAME OBJECT_NAME INHERITED_FROM
ENA
------------ ------------ -------------------- --P304
EMPLOYEE
POLICY NOT INHERITED YES
SQL>
5.
The ADO decision to move segments also depends on the default thresholds defined at the
database level for all user-defined tablespaces. Set the TBS_PERCENT_FREE threshold to
95% and the TBS_PERCENT_USED threshold to 5%.
Connected.
SQL> COL name format A20
SQL> COL value format 9999
SQL> SELECT * FROM dba_ilmparameters;
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
NAME
VALUE
a
b
-------------------- ----lo den
g
@ Stu
ENABLED
1
o
f
(in this
JOB LIMIT
10
y
se
EXECUTION MODE
3log
u
o
EXECUTION INTERVAL chn 15 e to
e e85
s
n
TBS PERCENT USEDT
n
o le lic 25
tiFREE
TBS PERCENT
a
rm erab
o
f
n selected.
sf
6 Irows
l
n
a
a
b n-tr
Glo nSQL>
o EXEC
dbms_ilm_admin.customize_ilm(DBMS_ILM_ADMIN.TBS_PERCENT_FREE,95)
SQL> EXEC
dbms_ilm_admin.customize_ilm(DBMS_ILM_ADMIN.TBS_PERCENT_USED,5)
SQL> SELECT * FROM dba_ilmparameters;
NAME
VALUE
-------------------- ----Copyright © 2013, Oracle and/or its affiliates. All rights reserved.
Chapter 7 - Page 10
a
ENABLED
JOB LIMIT
EXECUTION MODE
EXECUTION INTERVAL
TBS PERCENT USED
TBS PERCENT FREE
1
10
3
15
5
95
6 rows selected.
SQL>
6.
Step 2-c showed that the 5% TBS_PERCENT_USED threshold is already reached on the
ADOTBS tablespace.
For the purpose of the demo, we will not wait for the maintenance window to open that will
trigger the ADO policies jobs. Instead, you are going to use the following PL/SQL block
connected as the ADO policy owner.
s
) ha
Connected.
SQL> declare
v_executionid number;
begin
dbms_ilm.execute_ILM (ILM_SCOPE => dbms_ilm.SCOPE_SCHEMA,
execution_mode => dbms_ilm.ilm_execution_offline,
task_id
=> v_executionid);
end;
/
2
3
4
5
6
7
8
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
b
lo den
g
@ Stu
o
f
(in this
y
og use
l
o
hn se to
c
e
T cen
n
o
li
ti
e
a
l
rm erab
o
f
In ansf
l
a
SQL>
b n-tr
G7.loCheck
nothe current free space in ADOTBS tablespace. The LOW_COST_STORE may show a
value for the column % Used, although the space used in ADOTBS may not have
decreased. If this is the case, a few seconds later, run the same statement and you will see
that the data dictionary has been updated to reflect the new situation.
COL tablespace format A16
SELECT /* + RULE */ df.tablespace_name "Tablespace",
df.bytes / (1024 * 1024) "Size (MB)",
FROM dba_data_files
Chapter 7 - Page 11
a
Order by 4;
SQL> COL tablespace format A16
SQL> SELECT /* + RULE */ df.tablespace_name "Tablespace",
df.bytes / (1024 * 1024) "Size (MB)",
FROM dba_data_files
Order by 4;
2
3
4
5
6
7
8
9
10
11
12
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
Tablespace
Size (MB) Free (MB)
%a
Free
l- t G% uUsed
b
---------------- ---------- ---------- ---------lo den---------g
tu 1
@
SYSTEM
900
5
99
o
S
f
n
s
i
i
(
SYSAUX
7600
362.8125
5
95
th
y
g
e
USERS
8.75
9
91
s
lo o u.8125
o
n
t
EXAMPLE
9
91
h se 33.6875
c358.125
e
n
T
UNDOTBS1
139.6875
85
15
n
ce165
i
o
l
i
ADOTBS
10
9
90
10
t
a
le
b
m
r
a
LOW_COST_STORE
200
198.75
99
1
r
o
f
e
f
n
l I rans
a
b
n-t selected.
Glo n7orows
SQL>
8.
Display the task that evaluated the ADO policy and the job executed.
SQL>
SQL>
SQL>
SQL>
COL job_name format A20
COL object_name format A8
COL task_id format 99999
SELECT task_id, state FROM user_ilmtasks;
TASK_ID STATE
------- --------1688 COMPLETED
SQL> SELECT TASK_ID, POLICY_NAME, OBJECT_NAME,
Chapter 7 - Page 12
a
SELECTED_FOR_EXECUTION, JOB_NAME
FROM user_ilmevaluationdetails;
TASK_ID POLICY_NAME OBJECT_N SELECTED_FOR_EXECUTION JOB_NAME
------- ------------ -------- ---------------------- --------1688 P304
EMPLOYEE SELECTED FOR EXECUTION ILMJOB1204
SQL> SELECT task_id, job_name, job_state FROM user_ilmresults;
TASK_ID JOB_NAME
JOB_STATE
------- -------------------- --------------------------------1688 ILMJOB1204
COMPLETED SUCCESSFULLY
SQL>
9.
s
) ha
Find the segment SCOTT.EMPLOYEE that has been moved to the LOW_COST_STORE
tablespace.
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
b
lo den
g
@ Stu
o
f
(in this
y
og use
l
o
hn se to
SQL> exit
c
e
T cen
$
n
o
li it ready for the next practice by running the following
ti
e
a
10. Clean up your environment
to
get
l
m rab
script. for
n nsfe
I
l
$
./ADO_cleanup.sh
ba$ n-tra
o
l
G no
SQL> SELECT table_name, tablespace_name FROM user_tables
WHERE table_name = 'EMPLOYEE';
2
3
4
TABLE_NAME
TABLESPACE_NAME
------------------------------ -------------------EMPLOYEE
LOW_COST_STORE
Chapter 7 - Page 13
a
Practice 7-3: Automatic Data Optimization – Creating a COMPRESS
Policy
Overview
In this practice, you will create and enable a Row Store compression policy on the
SCOTT.EMPLOYEE table so that rows get automatically compressed after 30 days of no
modification on the table.
ADO for compression can only work if statistics related to data accesses at segment level and
or data modifications at row and segment level are collected. Statistics are collected because
Heat Map is already enabled. Starting the collection causes DML and access of all segments to
be tracked in memory and then flushed to an on-disk statistics table, but only statistics post the
time you enabled heat map are valid and will be considered by ADO. You will simulate a
situation where statistics were collected dating one month before the heat map collection
started. Therefore you have to use a procedure that sets the heat map start time earlier.
Tasks
1.
s
) ha
Because you will introduce statistics dating a month, you have to set back the heat map
start time.
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
Connected to:
a
b
lo d12.1.0.0.2
en
Release
u
t
@
64bit Production
nfo tAnalytics,
sS
i
i
(
With the Partitioning, OLAP, Advanced
Real
h
y
g
e
Application Testing and Unified
Auditing
options
lo o us
o
n
h se t
c
e
SQL> exec dbms_ilm_admin.set_heat_map_start(sysdate-50)
T cen
n
o
li
ti
e
a
l
bsuccessfully completed.
PL/SQLrm
procedure
a
r
o
f
e
In ansf
l
a
b SQL>
-tr
n
G2.loCreate
o
n the procedure sys.print_compression_stats. This procedure uses the
dbms_compression.get_compression_type predefined function which returns the
compression type for a specified row of a table. You will use the procedure to verify that the
rows are compressed after ADO policy task execution.
SQL> create or replace procedure print_compression_stats
(owner varchar2,tabname varchar2) as
type r_cursor is REF CURSOR;
cmp_rec r_cursor;
type rec_ctype is record
(cmp_type
number(6));
rec_cmp rec_ctype;
stmt varchar2(200);
qot varchar2(1) := '''';
n_uncmp number :=0;
Chapter 7 - Page 14
a
n_advanced number :=0;
n_other number :=0;
begin
stmt
stmt
stmt
open
loop
:= 'select dbms_compression.get_compression_type(';
:= stmt||qot||owner||qot||','||qot||tabname||qot;
:= stmt||',rowid) from '||owner||'.'||tabname;
cmp_rec for stmt;
fetch cmp_rec into rec_cmp;
exit when cmp_rec%notfound;
case rec_cmp.cmp_type
when dbms_compression.COMP_NOCOMPRESS then
n_uncmp
:= n_uncmp + 1;
when dbms_compression.COMP_ADVANCED then
n_advanced := n_advanced + 1;
when dbms_compression.COMP_BASIC then
n_advanced := n_advanced + 1;
else
n_other := n_other + 1;
end case;
end loop;
close cmp_rec;
dbms_output.put_line('Compression Stats');
dbms_output.put_line('------------------');
dbms_output.put_line('Uncompressed
: ' || n_uncmp);
dbms_output.put_line('Adv/basic compressed : ' ||
n_advanced);
dbms_output.put_line('Others
: ' || n_other);
end;
/
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
Procedure created.
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
b
lo den
g
@ Stu
o
f
(in this
y
og use
l
o
hn se to
c
e
T cen
n
o
li
ti
e
a
l
rm erab
o
f
In ansf
l
a
b
tr
Glo non-
SQL> grant execute on print_compression_stats to public;
Grant succeeded.
SQL> create or replace public synonym print_compression_stats
for sys.print_compression_stats;
2
Synonym created.
Chapter 7 - Page 15
a
SQL>
3.
Create the SCOTT.EMPLOYEE table and insert rows.
Connected.
SQL> drop table employee purge;
drop table employee purge
*
ERROR at line 1:
ORA-00942: table or view does not exist
SQL> create table employee (
EMPNO
NUMBER(4) NOT NULL,
ENAME
VARCHAR2(10),
JOB
VARCHAR2(9),
MGR
NUMBER(4),
HIREDATE DATE,
SAL
NUMBER(7,2),
COMM
NUMBER(7,2),
DEPTNO
NUMBER(2)
) tablespace example;
2
3
4
5
6
7
8
9
Table created.
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
b
lo den
g
@ Stu
o
f
(in this10
y
og use
l
o
hn se to
c
e
n (empno, ename, job, mgr, hiredate,
Temployee
e
SQL> insert into
n
c
i
o
l
i
tdeptno)
sal, comm,
a
le
b
m
r
a
select
fo empno,
erename, job, mgr, hiredate, sal, comm, deptno from
f
n
I
s
emp;
al 2 -tran
b
o
Gl n14onrows created.
SQL> declare
blowup PLS_INTEGER := 8;
sql_test clob;
begin
for i in 1..blowup loop
sql_test := 'insert /*+ append */ into employee
select * from
scott.employee';
execute immediate sql_test;
commit;
end loop;
end;
Chapter 7 - Page 16
a
/
2 3 4 5 6 7 8 9 10 11 12
SQL> SELECT count(*) FROM scott.employee;
COUNT(*)
---------3584
SQL>
4.
Add a compression policy on SCOTT.EMPLOYEE table.
SET ECHO ON
SET NUMWIDTH 10
SET LINESIZE 300
SET TRIMSPOOL ON
SET TAB OFF
SET PAGESIZE 1000
COLUMN JOB_NAME FORMAT A15
COLUMN COMPRESSION_LEVEL FORMAT A17
COLUMN COMPLETION_TIME FORMAT A30
COLUMN COMMENTS FORMAT A10
COLUMN policy_name FORMAT A8
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
b
lo den
g
@ Stu
o
f
(in this
y
og use
l
o
n e to
SQL> SET ECHO ON ech
T 10 cens
SQL> SET NUMWIDTH
n
tio le300li
a
SQL> SET LINESIZE
rm erab ON
SQL>fo
SET TRIMSPOOL
In anTAB
sf OFF
l
SQL> SET
a
r
b n-tSET
PAGESIZE 1000
Glo nSQL>
o
SQL> COLUMN JOB_NAME FORMAT A15
SQL> COLUMN COMPRESSION_LEVEL FORMAT A17
SQL> COLUMN COMPLETION_TIME FORMAT A30
SQL> COLUMN COMMENTS FORMAT A10
SQL> COLUMN policy_name FORMAT A8
SQL> ALTER TABLE scott.employee ILM ADD POLICY ROW STORE
COMPRESS ADVANCED SEGMENT AFTER 30 DAYS OF NO MODIFICATION;
Table altered.
SQL>
Note: If you had not enabled heat map, you would have received the following error
message:
Chapter 7 - Page 17
a
SQL> ALTER TABLE scott.employee ILM ADD POLICY ROW STORE
COMPRESS ADVANCED SEGMENT AFTER 30 DAYS OF NO MODIFICATION;
ALTER TABLE scott.employee ILM ADD POLICY ROW STORE COMPRESS
ADVANCED SEGMENT AFTER 30 DAYS OF NO MODIFICATION
*
ERROR at line 1:
ORA-38342: heat map not enabled
SQL>
5.
Verify that the policy is added.
SQL> SELECT policy_name, action_type, scope, compression_level,
condition_type, condition_days
FROM
user_ilmdatamovementpolicies
ORDER BY policy_name;
2
3
4
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
b
lo den
g
@ Stu
o
f
(in this
y
og use
SQL>
l
o
to is disabled before ADO enables it.
hn of sthee table
6. Check if the COMPRESSION attribute
c
e
T cencompress_for
n
SQL> SELECT compression,
o
li
ti
e
a
l
FROM user_tables
WHERE
table_name = 'EMPLOYEE';
b
m
r
a
r
o
nf nsfe
I
l
ra COMPRESS_FOR
baCOMPRESS
t
o
l
n
-----------------------------G n-------o
DISABLED
POLICY_N ACTION_TYPE SCOPE
COMPRESSION_LEVEL CONDITION_TYPE
CONDITION_DAYS
-------- ----------- ------- ----------------- --------------------- -------------P324
COMPRESSION SEGMENT ADVANCED
LAST MODIFICATION
TIME
30
SQL>
Check that no blocks are compressed.
SQL> set serveroutput on
SQL> exec print_compression_stats('SCOTT','EMPLOYEE')
Compression Stats
-----------------Uncompressed
Adv/basic compressed
Others
: 3584
: 0
: 0
Chapter 7 - Page 18
a
SQL> ANALYZE TABLE scott.employee COMPUTE STATISTICS;
Table analyzed.
SQL> SELECT object_name, nrows_nc "Uncomp Rows", nrows_advanced
"Comp Rows", nrows_ehcc "HCC Comp Rows"
FROM
sys.compression_stat$ c, user_objects o
WHERE c.obj#=o.object_id
AND
o.object_name='EMPLOYEE';
2
3
4
no rows selected
SQL>
7.
Verify that heat map statistics are collected.
s
) ha
om ฺ
c
ฺ
ch ide
e
t
Session altered.
i
l- t Gu
a
b
lo den
g
SQL> COL object_name FORMAT A12
@ Stu
o
f
SQL> COL "Tracking Time" FORMAT(iA20
n this
y
SQL> COL "Seg_write" FORMAT
logA9o use
o
SQL> COL "Full" FORMATnA4
h seA8 t
c
e
SQL> COL "Seg_read"
FORMAT
T cen
n
SQL> COL "Lookup
Scan"
o
li FORMAT A12
ti
e
a
l
b
SQL> SELECT
object_name,
to_char(track_time,'DD-MON-YY
rm "Tracking
a
r
o
f
e
HH:MI:SS')
Time",
segment_write "Seg_write", FULL_SCAN
f
n nlookup_scan
I
s
l
"Full",
"Lookup
Scan"
a -tra
b
o
Gl nFROM
on DBA_HEAT_MAP_SEG_HISTOGRAM
SQL> alter session set nls_date_format='dd-mon-yy hh:mi:ss';
2
3
Seg_write Full Lookup Scan
------------ -------------------- --------- ---- -----------EMPLOYEE
06-MAR-13 01:19:57
YES
YES NO
SQL> SELECT object_name, segment_write_time, FULL_SCAN,
lookup_scan
FROM dba_heat_map_segment
2
3
OBJECT_NAME SEGMENT_WRITE_TIME FULL_SCAN
LOOKUP_SCAN
Chapter 7 - Page 19
a
------------ ------------------ ------------------ ----------EMPLOYEE
06-mar-13 01:20:19 06-mar-13 01:20:19
SQL> SELECT OBJECT_NAME, TRACK_TIME,
SEGMENT_WRITE "Seg_write",
SEGMENT_READ "Seg_read",
FULL_SCAN "Full", LOOKUP_SCAN "Look"
FROM v$heat_map_segment
2
3
4
5
6
Seg_write Seg_read Full Loo
------------ ------------------ --------- -------- ---- --EMPLOYEE
06-mar-13 01:24:08 YES
NO
YES NO
s
) ha
SQL>
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
b
lo den
g
@ Stu
o
f
(in this
y
og use
l
o
Connected.
to
hnnls_date_format='dd-mon-yy
c
e
SQL> alter sessioneset
hh:mi:ss';
s
T cen
n
io le li
t
a
Session
b
rmaltered.
a
r
o
f
e
In ansf
l
a
SQL>
r
b n-texec
o
l
G ndbms_ilm_admin.set_heat_map_table('SCOTT','EMPLOYEE',null,sysdat
o
e-31,2)
8.
Fake passage of time so that compression policy qualifies for ADO action. In real life
situation, this would happen naturally through ADO activity tracking.
a. Execute the procedure dbms_ilm_admin.set_heat_map_table. This procedure
simulates the passage of time in read access only so that the compression policy
qualifies for ADO action. In real life situation, this would happen naturally through a
normal activity on the table and a regular ADO policy evaluation.
SQL>
SQL>
SQL>
SQL>
SQL>
SQL>
SQL>
SQL>
SQL>
COL object_name FORMAT A12
COL "Tracking Time" FORMAT A20
COL "Seg_write" FORMAT A9
COL "Full" FORMAT A4
COL "Seg_read" FORMAT A8
COL "Write" FORMAT A6
COL "Full Scan" FORMAT A4
COL "Lookup Scan" FORMAT A12
select object_name,
Chapter 7 - Page 20
a
to_char(track_time,'DD-MON-YY HH:MI:SS') "Tracking Time",
segment_write "Write",
FULL_SCAN "Full Scan", lookup_scan "Lookup Scan"
from DBA_HEAT_MAP_SEG_HISTOGRAM
where object_name='EMPLOYEE'
and
owner='SCOTT';
2
3
4
5
6
7
Write Full Lookup Scan
------------ -------------------- ------ ---- -----------EMPLOYEE
06-MAR-13 01:31:33
YES YES NO
EMPLOYEE
03-FEB-13 01:27:48
NO
NO
NO
SQL>
There are two rows: one row relating recent write access and one row faking a
previous read access.
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
b
lo den
g
@ Stu
o
f
(in this
y
og use
l
o
hn se to
c
e
T cen
n
o
li
ti
e
a
l
b
SQL>form era
f
In only
sone
l
n
There is a
row relating recent write access.
a
r
b
t
o
Gl nSQL>
on select OBJECT_NAME, TRACK_TIME,
decode(SEGMENT_ACCESS,1, 'Write',2, 'Read',
SQL> select OBJECT_NAME, TRACK_TIME, SEGMENT_WRITE "Write",
SEGMENT_READ "Read", FULL_SCAN "Full Scan",
LOOKUP_SCAN "Lookup"
from v$heat_map_segment
where object_name='EMPLOYEE';
2
3
4
5
Write Rea Full Loo
------------ ------------------ ------ --- ---- --EMPLOYEE
06-mar-13 01:32:07 YES
NO YES
NO
'Other Acc') "Access"
from sys.heat_map_stat$ h, dba_objects o
where o.object_id=h.obj#
and
2
3
4
5
6
Access
------------ ------------------ --------EMPLOYEE
03-feb-13 01:27:48 Read
SQL>
There is only one row relating old read access.
Chapter 7 - Page 21
a
b.
Restart the instance to clear all statistics from memory, and mainly the statistics related
to recent write access.
Database closed.
SQL> startup
Fixed Size
2291280 bytes
Variable Size
285215152 bytes
Database Buffers
369098752 bytes
Redo Buffers
7303168 bytes
Database mounted.
Database opened.
SQL>
s
) ha
om ฺ
c
ฺ
c. Check that the statistics are cleared up.
ch ide
e
t
i
u
l- hh:mi:ss';
SQL> alter session set nls_date_format='dd-mon-yy
G
a
t
b
lo den
g
@ Stu
Session altered.
o
f
(in this
y
ogA12 use
SQL> COL object_name FORMAT
l
o
to A20
hn FORMAT
SQL> COL "Tracking Time"
c
e
e
s
n
TFORMAT
SQL> COL "Write"
A6
e
n
c
i
o
l
ti Scan"
SQL> COL "Full
a
le FORMAT A4
b
m
r
a
SQL>fo
COL "Lookup
r Scan" FORMAT A12
eobject_name,
f
n
I
s
SQL>
select
al -tran
b
o
HH:MI:SS') "Tracking Time",
Gl non to_char(track_time,'DD-MON-YY
segment_write "Seg_write",
FULL_SCAN "Full Scan", lookup_scan "Lookup Scan"
from DBA_HEAT_MAP_SEG_HISTOGRAM
where object_name='EMPLOYEE'
and
owner='SCOTT';
2
3
4
5
6
7
Seg_write Full Lookup Scan
------------ -------------------- --------- ---- -----------EMPLOYEE
03-FEB-13 01:27:48
NO
NO
NO
SQL>
There is now only one row: the one faking a previous read access.
Chapter 7 - Page 22
a
SQL> select OBJECT_NAME, TRACK_TIME, SEGMENT_WRITE "Write",
SEGMENT_READ "Read", FULL_SCAN "Full Scan",
LOOKUP_SCAN "Lookup"
from v$heat_map_segment
where object_name='EMPLOYEE';
2
3
4
5
no rows selected
SQL>
There are no more rows relating recent write access.
SQL> select OBJECT_NAME, TRACK_TIME,
decode(SEGMENT_ACCESS,1, 'Write',2, 'Read',
'Other Acc') "Access"
from sys.heat_map_stat$ h, dba_objects o
where o.object_id=h.obj#
and
2
3
4
5
6
Access
------------ ------------------ --------EMPLOYEE
03-feb-13 01:27:48 Read
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
b
lo den
g
@ Stu
SQL>
o
f
(in this
There is still one row relating old read access.
y
g useon SCOTT.EMPLOYEE table. For the
omodification
l
9. Now one month has passed without o
any
n untile the
tomaintenance window opens to execute the
hwait
purpose of the demo, you will not
c
e
s
npolicy evaluation and ADO task execution
T thecADO
ADO policies job. You launch
e
n
i
o
l
immediately.
ti
a
le
b
m
SQL> connect
scott/oracle_4U
r
a
fo sfer
n
I
Connected.
alSQL>-talter
an session set nls_date_format='dd-mon-yy hh:mi:ss';
r
b
o
Gl non
Session altered.
SQL> declare
v_executionid number;
begin
dbms_ilm.EXECUTE_ILM (
ILM_SCOPE
=> dbms_ilm.SCOPE_SCHEMA,
execution_mode => dbms_ilm.ilm_execution_offline,
task_id
=> v_executionid);
end;
/
Chapter 7 - Page 23
a
2
3
4
5
6
7
8
9
SQL>
10. Display the result of the executed task.
SQL>
SQL>
SQL>
SQL>
SQL>
SQL>
COL task_id format 99999
COL task_owner format A8
COL policy_name format A4
COL job_name format A10
COL SELECTED_FOR_EXECUTION format A22
select task_id, task_owner, state
from dba_ilmtasks where task_owner='SCOTT';
TASK_ID TASK_OWNER STATE
---------- ---------- ---------------1710 SCOTT
COMPLETED
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
SQL>
a
b
n SELECT
lo Rerun
ethe
11. If the STATE column displays ACTIVE, the task is still executing.
g
d
u
statement until STATE shows COMPLETED.
o@ is St
f
n
i
( object_name,
SQL> select task_id, policy_name,
th
y
g
e
selected_for_execution, job_name
lo o us
o
n
h se twhere object_name='EMPLOYEE';
FROM dba_ilmevaluationdetails
c
e
T cen
n
o
li
ti OBJECT_NAME
TASK_ID POLI
SELECTED_FOR_EXECUTION JOB_NAME
e
a
l
b
m
r
a
---------------------------- ---------r
fo ---e-----------f
n
I
s
1710
P324
EMPLOYEE
SELECTED FOR EXECUTION ILMJOB1284
l
n
a
a
r
b
t
Glo nSQL>
on-
It is possible that several rows are displayed with a SELECTED_FOR_EXECUTION
value of PRECONDITION NOT SATISFIED. The reason for the existence of these
rows is that the evaluation of the condition set in the ADO policy was not yet satisfied.
(there were still rows podified within the last month).
12. Verify the compression statistics for the SCOTT.EMPLOYEE segment. Use the
print_compression_stats procedure created in task 1.
SQL> exec print_compression_stats('SCOTT','EMPLOYEE')
Compression Stats
-----------------Uncompressed
: 0
Chapter 7 - Page 24
a
Adv/basic compressed : 3584
Others
: 0
SQL> SELECT compression, compress_for
FROM user_tables WHERE table_name = 'EMPLOYEE';
2
COMPRESS COMPRESS_FOR
-------- -----------------------------ENABLED ADVANCED
SQL> analyze table scott.employee compute statistics;
Table analyzed.
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
b
lo den
g
@ Stu
o
f
(in this
y
og use
l
o
hn se to
c
e
T cen
n
o
li
ti
e
a
l
2
3rm 4 ra5b
6
7
8
o
f
e
f
n
I anUncomp
s
Blocks Comp Rows Comp Blocks HCC Comp Blocks
lOBJECT_N
a
r
b
t
n- ------------- ---------- ----------- --------------Glo n-------o
EMPLOYEE
0
3584
6
0
SQL> COL object_name format A8
SQL> SELECT object_name,
nblk_nc "Uncomp Blocks",
nrows_advanced "Comp Rows",
nblk_advanced "Comp Blocks",
nblk_ehcc "HCC Comp Blocks"
FROM
sys.compression_stat$ c, user_objects o
WHERE c.obj#=o.object_id
AND
SQL>
Chapter 7 - Page 25
a
Practice 7-4: Cleanup ADO Policies and Heat Map Statistics
Overview
In this practice you delete all ADO policies on SCOTT.EMPLOYEE table, stop collecting heat map
statistics and clean up all heat map statistics.
Tasks
1.
Delete all ADO policies on SCOTT.EMPLOYEE table.
SQL> ALTER TABLE scott.employee ILM DELETE_ALL;
Table altered.
Connected.
SQL>
2.
Stop heat map statistics collection.
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
System altered.
l- t Gu
a
b
lo den
g
@ Stu
SQL>
o
f
(in this
3. Clean up all heat map statistics.
y
e sys.heat_map_stat$;
og usfrom
l
SQL> select OBJ#, TS#, TRACK_TIME
o
hn se to
c
e
n
T TS#cTRACK_TIM
OBJ#
e
n
i
o
l
i
t------------------a
le --------b
m
r
a
-1 06-MAR-13
o sfer
f-1
n
I
8 06-MAR-13
al -t30127
an
r
b
o
4 06-MAR-13
Gl non 26491
SQL> ALTER SYSTEM SET heat_map=off SCOPE=BOTH;
SQL> exec dbms_ilm_admin.clear_heat_map_all
SQL> select OBJ#, TS#, TRACK_TIME from sys.heat_map_stat$;
OBJ#
TS# TRACK_TIM
---------- ---------- ---------1
-1 06-MAR-13
SQL>
Chapter 7 - Page 26
a
You notice that the procedure deletes all rows in HEAT_MAP_STAT$ table except the
dummy row.
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
b
lo den
g
@ Stu
o
f
(in this
y
og use
l
o
hn se to
c
e
T cen
n
o
li
ti
e
a
l
rm erab
o
f
In ansf
l
a
b
tr
Glo non-
Chapter 7 - Page 27
a
Practice 7-5: Moving Data File Online
Overview
In this practice, you will move a data file to another location online.
Tasks
1.
Create a tablespace ONLINE_TBS and find the list of data files in the orcl database.
SQL> COL name FORMAT A60
SQL> create tablespace ONLINE_TBS
datafile '/u01/app/oracle/oradata/orcl/online_tbs01.dbf'
size 10m;
Tablespace created.
SQL> select name from v$datafile;
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
b
lo den
g
@ Stu
o
f
(in this
y
og use
l
o
hn se to
c
e
T cen
n
o
li
SQL>
ti
e
a
l
b
rm /u01/app/oracle/oradata/orcl/online_tbs01.dbf
a
2. Move the datafile
to
r
o
f
e
f
n
/u01/app/oracle/oradata/orcl/online
destination, online without taking it offline.
l I rans
a
b
t
n- the destination directory /u01/app/oracle/oradata/orcl/online.
Gloa. nCreate
o
SQL> !mkdir /u01/app/oracle/oradata/orcl/online
NAME
-------------------------------------------------------------/u01/app/oracle/oradata/orcl/system01.dbf
/u01/app/oracle/oradata/orcl/example01.dbf
/u01/app/oracle/oradata/orcl/sysaux01.dbf
/u01/app/oracle/oradata/orcl/undotbs01.dbf
/u01/app/oracle/oradata/orcl/users01.dbf
/u01/app/oracle/oradata/orcl/online_tbs01.dbf
SQL>
b.
Move the data file /u01/app/oracle/oradata/orcl/online_tbs01.dbf to
/u01/app/oracle/oradata/orcl/online destination, online.
SQL> ALTER DATABASE MOVE DATAFILE
2 '/u01/app/oracle/oradata/orcl/online_tbs01.dbf'
3 TO '/u01/app/oracle/oradata/orcl/online/online_tbs01.dbf';
Database altered.
SQL>
SQL> !ls -l /u01/app/oracle/oradata/orcl/online_tbs01.dbf
Chapter 7 - Page 28
a
ls: /u01/app/oracle/oradata/orcl/online_tbs01.dbf: No such file
or directory
SQL> !ls -l /u01/app/oracle/oradata/orcl/online
-rw-r----- 1 oracle oinstall 9183232 Dec 12 11:26
online_tbs01.dbf
SQL>
3.
Move the data file /u01/app/oracle/oradata/orcl/online/online_tbs01.dbf
online back to /u01/app/oracle/oradata/orcl destination and keep the original file.
SQL> ALTER DATABASE MOVE DATAFILE
'/u01/app/oracle/oradata/orcl/online/online_tbs01.dbf'
TO '/u01/app/oracle/oradata/orcl/online_tbs01.dbf' KEEP;
Database altered.
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
b
-rw-r----- 1 oracle oinstall 9183232 Dec l12
o 11:28
en
g
d
/u01/app/oracle/oradata/orcl/online_tbs01.dbf
u
o@ is St
f
n
i
(
th
y
SQL> !ls -l /u01/app/oracle/oradata/orcl/online/online*
g
e
lo 9183232
us Dec 12 11:28
o
n
o
t
/u01/app/oracle/oradata/orcl/online/online_tbs01.dbf
ech ense
T
n
o
lic
i
t
e
a
l
SQL>
rm erab
o
f
f
4. Move the
online
In dataafile
s/u01/app/oracle/oradata/orcl/online_tbs01.dbf
l
n
a
overwriting
the
file.
b n-tr
o
l
G nSQL>
o ALTER DATABASE MOVE DATAFILE
SQL>
'/u01/app/oracle/oradata/orcl/online_tbs01.dbf'
TO '/u01/app/oracle/oradata/orcl/online/online_tbs01.dbf'
REUSE;
Database altered.
SQL>
ls: cannot access /u01/app/oracle/oradata/orcl/online_tbs01.dbf:
No such file or directory
SQL> !ls -l /u01/app/oracle/oradata/orcl/online/online*
Chapter 7 - Page 29
a
-rw-r----- 1 oracle oinstall 9183232 Dec 12 11:30
SQL>
5.
Drop the tablespace ONLINE_TBS including the data files.
SQL> drop tablespace ONLINE_TBS including contents and
datafiles;
Tablespace dropped.
SQL> EXIT
$ ls –l /u01/app/oracle/oradata/orcl/online_tbs01.dbf
ls: cannot access /u01/app/oracle/oradata/orcl/online_tbs01.dbf:
No such file or directory
$ ls –l /u01/app/oracle/oradata/orcl/online/online_tbs01.dbf
ls: cannot access
/u01/app/oracle/oradata/orcl/online/online_tbs01.dbf: No such
file or directory
$
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
b
lo den
g
@ Stu
o
f
(in this
y
og use
l
o
hn se to
c
e
T cen
n
o
li
ti
e
a
l
rm erab
o
f
In ansf
l
a
b
tr
Glo non-
Chapter 7 - Page 30
a
s
) ha
om ฺ
c
ฺ
ch8: Ine
ide
t
i
u
l
Database Archiving
tG
ba enand
o
l
gValidity
Temporal
d
u
t
@
o
S
nf8 this
i
Chapter
(
ogy use
l
o
hn se to
c
e
T cen
n
o
li
ti
e
a
l
rm erab
o
f
In ansf
l
a
b
tr
Glo non-
Practices for Lesson 8: In-Database Archiving and Temporal Validity
Chapter 8 - Page 1
a
Practices Overview
In this practice, you will exercise yourself on new features like In-Database Archiving and
Temporal Validity.
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
b
lo den
g
@ Stu
o
f
(in this
y
og use
l
o
hn se to
c
e
T cen
n
o
li
ti
e
a
l
rm erab
o
f
In ansf
l
a
b
tr
Glo non-
Chapter 8 - Page 2
a
Practice 8-1: In-Database Archiving – Row-archival
Overview
In this practice, you will enable row-archival on HR.EMP_ARCH table in orcl database and
sometimes display active rows only and sometimes display active and non-active rows.
1. Connected under SYSTEM, create the table HR.EMP_ARCH with ROW ARCHIVAL attribute.
$ . oraenv
Connected to:
Testing options
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
b
lo den
g
@ Stu
o
f
(in this
y
og use
l
o
SQL> CREATE TABLE hr.emp_arch
to
hn se VARCHAR2(100),
c
(EMPNO NUMBER(7),
FULLNAME
e
n
T MGRceNUMBER(7))
n
JOB VARCHAR2(9),
i
o
l
ti
a
le
ROW ARCHIVAL;
b
m
r
a
fo 3 sfe4r
2
n
I
alTable-trcreated.
an
b
o
Gl non
SQL> DROP TABLE hr.emp_arch PURGE;
DROP TABLE hr.emp_arch PURGE
*
ERROR AT LINE 1:
ORA-00942: TABLE OR VIEW DOES NOT EXIST
SQL> DESC hr.emp_arch
Name
Null?
-------------------------------- -------EMPNO
FULLNAME
JOB
MGR
Type
------------------NUMBER(7)
VARCHAR2(100)
VARCHAR2(9)
NUMBER(7)
SQL>
2.
Insert new rows in the table and verify the value of the archival column.
SQL> INSERT INTO hr.emp_arch (EMPNO , FULLNAME , JOB)
VALUES (100, 'JEAN', 'MGR');
Chapter 8 - Page 3
a
2
1 row created.
SQL> INSERT INTO hr.emp_arch (EMPNO , FULLNAME , JOB , MGR)
VALUES (101, 'ADAM', 'CLERK' ,100);
2
1 row created.
VALUES (102, 'TOM', 'ADMIN' ,100);
2
1 row created.
VALUES (103, 'JIM', 'WRITER' ,100);
2
1 row created.
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
SQL> COMMIT;
l- t Gu
a
b
lo den
g
@ Stu
Commit complete.
o
f
(in this
y
SQL>
og use
l
o
n isedisplayed
to if explicitly required and that the default
hcolumn
3. Verify that the new row-archival
c
e
s
T cen
value is 0 for all active rows.
n
o
li A10
ti
SQL> COL fullname
FORMAT
e
a
l
b
rmORA_ARCHIVE_STATE
a
SQL>fo
COL
FORMAT A30
r
e
f
n
I
s
SQL>
SELECT
ORA_ARCHIVE_STATE,
fullname FROM hr.emp_arch;
l
n
a
a
r
b
t
Glo nORA_ARCHIVE_STATE
onFULLNAME
--------------------------0
0
0
0
---------JEAN
ADAM
TOM
JIM
SQL>
Chapter 8 - Page 4
a
4.
Performing a CTAS (create table as select) of a row-archival enabled table does
not propagate the row-archival state column to the new table.
SQL> CREATE TABLE hr.emp AS SELECT * FROM hr.emp_arch;
Table created.
SQL> SELECT ORA_ARCHIVE_STATE, fullname FROM hr.emp;
SELECT ORA_ARCHIVE_STATE, fullname FROM hr.emp
*
ERROR at line 1:
ORA-00904: "ORA_ARCHIVE_STATE": invalid identifier
SQL>
5.
Update ORA_ARCHIVE_STATE column to reflect a non-active state for employee numbers
101 and 102.
SQL> UPDATE hr.emp_arch
SET ORA_ARCHIVE_STATE=DBMS_ILM.ARCHIVESTATENAME(1)
WHERE empno IN (101,102);
2
3
2 rows updated.
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
b
lo den
g
@ Stu
o
f
(in this
SQL> COMMIT;
y
og use
l
o
hn se to
Commit complete.
c
e
T cen
n
o
li
ti
SQL>
e
a
l
b
rm estatement
a
r
6. Verify thatfo
a SELECT
displays only active rows by default.
f
n
I
s
alSQL>-tSELECT
an ORA_ARCHIVE_STATE, fullname FROM hr.emp_arch;
r
b
o
Gl non
ORA_ARCHIVE_STATE
FULLNAME
------------------------------ ---------0
JEAN
0
JIM
SQL>
7.
Display all rows of the tables, non-active and active rows.
SQL> ALTER SESSION SET ROW ARCHIVAL VISIBILITY = ALL;
Session altered.
SQL> SELECT ORA_ARCHIVE_STATE, fullname FROM hr.emp_arch;
Chapter 8 - Page 5
a
ORA_ARCHIVE_STATE
FULLNAME
------------------------------ ---------0
JEAN
1
ADAM
1
TOM
0
JIM
SQL>
8.
Verify that an INSERT AS SELECT where the source and target tables are row-archivalenabled does not populate the target table’s ORA_ARCHIVE_STATE column with the value
of the corresponding column from the source table’s. Instead, the default active rowarchival state will be set.
SQL> ALTER TABLE hr.emp ROW ARCHIVAL;
Table altered.
SQL> INSERT INTO hr.emp
SELECT EMPNO+100 , FULLNAME ||'_SENIOR'
FROM hr.emp_arch;
2
3
4 rows created.
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
b
lo den
g
@ Stu
o
f
s hr.emp_arch;
in thiFROM
SQL> SELECT ORA_ARCHIVE_STATE, (fullname
y
og use
l
o
n e to
ORA_ARCHIVE_STATE
hFULLNAME
c
e
s
-------------------n
T ---------e
n
ic
0
tio le lJEAN
a
1
rm erab ADAM
o
f
1 In
TOM
sf
l
n
a
a
b 0 tr
JIM
Glo non, JOB , MGR
SQL> COL fullname FORMAT A30
SQL> SELECT ORA_ARCHIVE_STATE, fullname FROM hr.emp;
ORA_ARCHIVE_STATE
FULLNAME
-------------------- -----------------------------0
JEAN
0
ADAM
0
TOM
0
JIM
0
JEAN_SENIOR
0
ADAM_SENIOR
0
TOM_SENIOR
0
JIM_SENIOR
Chapter 8 - Page 6
a
8 rows selected.
SQL>
9.
Disable the row-archival attribute on HR.ARCH_EMP table.
SQL> ALTER TABLE hr.emp_arch NO ROW ARCHIVAL;
Table altered.
SQL>
10. Verify that the row-archival column has been dropped.
SQL> SELECT ORA_ARCHIVE_STATE, fullname FROM hr.emp_arch;
SELECT ORA_ARCHIVE_STATE, fullname FROM hr.emp_arch
*
ERROR at line 1:
ORA-00904: "ORA_ARCHIVE_STATE": invalid identifier
s
) ha
om ฺ
c
ฺ
ch ide
e
SQL> EXIT
t
i
l- t Gu
a
$
b
lo den
g
@ Stu
o
f
(in this
y
og use
l
o
hn se to
c
e
T cen
n
o
li
ti
e
a
l
rm erab
o
f
In ansf
l
a
b
tr
Glo non-
Chapter 8 - Page 7
a
Practice 8-2: Temporal Validity
Overview
In this practice, you set a valid time dimension on HR.EMP table to define a period of validity for
each employee in the table.
Tasks
1.
Connected under SYSTEM, Set the valid-time dimension on a table using existing columns.
$ . oraenv
$
s
) ha
Connected to:
Testing options
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
b
lo den
g
@ Stu
o
f
SQL> DROP TABLE hr.emp PURGE;
(in this
y
og use
l
o
Table dropped.
hn se to
c
e
T HR.EMP
en
n
SQL> CREATE iTABLE
c
i
o
l
t
a
le
(EMPNObNUMBER,
SALARY NUMBER, DEPTID NUMBER,
m
r
a
r
o
e VARCHAR2(100),
nf nsfNAME
I
l
ba n-tra USER_TIME_START DATE,
o
l
USER_TIME_END
DATE,
G no
PERIOD FOR USER_TIME
2
3
4
Table created.
(USER_TIME_START, USER_TIME_END));
5
6
7
SQL>
Chapter 8 - Page 8
a
2.
Check the implicit constraint created with the valid-time dimension.
SQL> select constraint_name from dba_constraints
where table_name ='EMP' and OWNER='HR';
2
CONSTRAINT_NAME
-------------------------------------------------------------USER_TIME1ABD76
SQL>
3.
Insert rows with start and and valid time values.
SQL> INSERT INTO hr.emp (empno , salary , deptid , name ,
USER_TIME_START, USER_TIME_END)
VALUES (101,1900,90,'ADAM',
to_date('01-JAN-2000', 'dd-mon-yyyy') ,
to_date('31-DEC-2011', 'dd-mon-yyyy'));
2
3
4
5
1 row created.
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
SQL> commit;
b
lo den
g
@ Stu
o
f
Commit complete.
(in this
y
og use
l
o
SQL>
n e to
echtheencolumns
s of the USER TIME valid-time dimension
4. The DESCRIBE commandT
shows
n
because they were explicitly
lic in the table structure.
io ledefined
t
a
SQL> col
b A10
rmnameeraformat
o
f
SQL>
In select
sf NAME,
l
n
a
a
to_char(USER_time_start,'dd-mon-yyyy')
"Start",
b n-tr
o
l
G no
to_char(USER_time_end, 'dd-mon-yyyy') "End"
from hr.emp;
2
3
4
NAME
Start
End
---------- -------------------- -------------------ADAM
01-jan-2000
31-dec-2011
SQL>
SQL> DESC hr.emp
Name
Null?
Type
-------------------------- -------- ----------EMPNO
NUMBER
Chapter 8 - Page 9
a
SALARY
DEPTID
NAME
USER_TIME_START
USER_TIME_END
NUMBER
NUMBER
VARCHAR2(100)
DATE
DATE
SQL>
SQL> select TABLE_NAME, COLUMN_NAME
from dba_tab_cols where owner='HR' and table_name='EMP';
2
TABLE_NAME
COLUMN_NAME
--------------- -------------------EMP
USER_TIME
EMP
EMPNO
EMP
SALARY
EMP
DEPTID
EMP
NAME
EMP
USER_TIME_START
EMP
USER_TIME_END
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
b
lo den
g
@ Stu
o
f
(in this
7 rows selected.
y
og use
l
o
hn se to
SQL>
c
e
n of the valid-time dimension, drop the dimension,
Tthe columns
e
n
5. If you want to disassociate
c
i
o
l
i without
tone
and redefine a new
a
le explicitly naming the two columns. The implicit columns
b
m
r
a
created are
The DESCRIBE command does not show the
fodisassociated.
erand VALID_TIME_END
f
n
I
s
VALID_TIME_START
columns anymore as they are disassociated
l
n
a
a
r
b
t
and
were
not
explicitly
defined
at
the
table
creation.
n- still see the USER_START_TIME and USER_END_TIME columns in both
GloNote:
noYou
describes because they are part of the user's definition of the table.
SQL> ALTER TABLE hr.emp DROP (PERIOD FOR user_time);
Table altered.
SQL> ALTER TABLE hr.emp ADD (PERIOD FOR VALID_time);
Table altered.
SQL> desc hr.emp
Name
Null?
Type
Chapter 8 - Page 10
a
-------------------------- -------- ----------EMPNO
NUMBER
SALARY
NUMBER
DEPTID
NUMBER
NAME
VARCHAR2(100)
USER_TIME_START
DATE
USER_TIME_END
DATE
SQL>
SQL> select TABLE_NAME, COLUMN_NAME
from dba_tab_cols where owner='HR' and table_name='EMP';
2
TABLE_NAME
COLUMN_NAME
------------------- -------------------EMP
VALID_TIME_START
EMP
EMPNO
EMP
SALARY
EMP
DEPTID
EMP
NAME
EMP
USER_TIME_START
EMP
USER_TIME_END
EMP
VALID_TIME_END
EMP
VALID_TIME
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
b
lo den
g
@ Stu
o
f
(in this
y
og use
l
o
hn se to
c
e
T cen
n
o
li
ti
e
9 rows selected.
a
l
rm erab
o
f
In
sf
l
SQL> an
a
b n-tr
G6.loYouncan
o display them if you explicitly name them in the projection.
SQL> select NAME,
to_char(valid_time_start, 'dd-mon-yyyy'),
to_char(valid_time_end, 'dd-mon-yyyy')
from hr.emp;
2
3
4
NAME
TO_CHAR(VALID_TIME_S TO_CHAR(VALID_TIME_E
---------- -------------------- -------------------ADAM
SQL>
7.
Insert rows with different start and end dates of validity using the
/home/oracle/labs/VT/ins.sql script.
Chapter 8 - Page 11
a
SQL> DROP TABLE hr.emp PURGE;
Table dropped.
SQL> CREATE TABLE HR.EMP
(EMPNO NUMBER, SALARY NUMBER, DEPTID NUMBER,
NAME VARCHAR2(100),
PERIOD FOR VALID_TIME );
Table created.
SQL>
SQL> DESC hr.emp
Name
Null?
-------------------------- -------EMPNO
SALARY
DEPTID
NAME
Type
----------NUMBER
NUMBER
NUMBER
VARCHAR2(100)
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
b
lo den
g
@ Stu
o
f
(in this
y
SQL>
og use
l
o
hn se to
c
e
T cen
SQL> @/home/oracle/labs/VT/ins.sql
n
o
li
ti
e
a
l
m rab
1 rowor
created.
f
n nsfe
I
l
a
ba1 row
trcreated.
o
l
n
G no
1 row created.
1 row created.
1 row created.
1 row created.
1 row created.
1 row created.
Chapter 8 - Page 12
a
Commit complete.
SQL>
8.
View all rows. The disassociated columns don’t appear.
SQL>
SQL>
SQL>
SQL>
SQL>
COL NAME FORMAT A8
COL EMPNO FORMAT 999
COL VALID_TIME_START FORMAT A35
COL VALID_TIME_END FORMAT A35
select * from hr.emp;
EMPNO
SALARY
DEPTID NAME
---------- ---------- ---------- ---------101
1900
90 ADAM
102
1991
91 SCOTT
103
1992
92 JIM
104
1992
92 JEAN
105
1993
93 MARIA
106
1994
94 TOM
107
1996
92 KIM
108
1996
92 JAMES
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
b
lo den
g
@ Stu
o
f
(in this
y
8 rows selected.
og use
l
o
hn se to
c
e
T cen
SQL>
n
o
li
ti
e
a
l
bnamed valid-time columns.
rm
9. View all rows
with explicit
a
r
o
f
e
In select
sf NAME,
SQL>
l
n
a
a
b
tr
'dd-mon-yyyy') "Start",
Glo non- to_char(valid_time_start,
to_char(valid_time_end, 'dd-mon-yyyy') "End"
from hr.emp order BY 2;
NAME
--------ADAM
SCOTT
JIM
JEAN
MARIA
TOM
KIM
JAMES
Start
End
---------------------- -------------------01-jan-1990
31-dec-2010
01-jan-1991
31-dec-2011
01-jan-1992
31-dec-2013
01-jan-1992
31-dec-2012
01-jan-1993
31-dec-2011
01-jan-1994
01-jan-1994
30-jun-1994
31-dec-1992
31-dec-1994
Chapter 8 - Page 13
a
8 rows selected.
SQL>
10. View rows using Valid-time temporal flashback queries.
a. Using an AS OF query:
SQL> select NAME,
to_char(valid_time_start, 'dd-mon-yyyy') "Start",
from hr.emp AS OF PERIOD FOR valid_time
to_date('31-DEC-1992', 'dd-mon-yyyy') ;
2
3
4
5
NAME
Start
End
-------- -------------------- -------------------ADAM
01-jan-1990
31-dec-2010
SCOTT
01-jan-1991
31-dec-2011
JIM
01-jan-1992
31-dec-2013
JEAN
01-jan-1992
31-dec-2012
JAMES
31-dec-1992
31-dec-1994
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
b
lo den
g
@ Stu
o
f
(in this
SQL>
y
g validuatsethe date of '01-DEC-1992'.
ostill
l
Are displayed only employees who were
o
hn se to
b. Another example:
c
e
T cen
SQL> select NAME,
n
o
li
ti
e
a
l
to_char(valid_time_start,
'dd-mon-yyyy') "Start",
b
m
r
a
r
o
'dd-mon-yyyy') "End"
fe
nf nsto_char(valid_time_end,
I
l
from
hr.emp
order
BY
2;
ba n-tra
o
l
G no
NAME
Start
End
-------ADAM
SCOTT
JIM
JEAN
MARIA
TOM
KIM
JAMES
-------------------01-jan-1990
01-jan-1991
01-jan-1992
01-jan-1992
01-jan-1993
01-jan-1994
01-jan-1994
31-dec-1992
-------------------31-dec-2010
31-dec-2011
31-dec-2013
31-dec-2012
31-dec-2011
30-jun-1994
31-dec-1994
8 rows selected.
Chapter 8 - Page 14
a
SQL>
SQL> select NAME,
from hr.emp
AS OF PERIOD FOR valid_time to_date('01-JAN-2013');
NAME
-------JIM
TOM
Start
End
-------------------- -------------------01-jan-1992
31-dec-2013
01-jan-1994
SQL>
Are displayed only employees who were still valid at the date of '01-JAN-2013'.
c. Using the following new clause VERSIONS PERIOD FOR BETWEEN:
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
b
lo den
g
@ Stu
o
f
(in this
NAME
Start
End
y
se
og -------------------l
u
-------- -------------------o
hn se to31-dec-2010
c
ADAM
01-jan-1990
e
T cen 31-dec-2011
SCOTT
01-jan-1991
n
o
li
ti
e
a
l
JIM
01-jan-1992
31-dec-2013
b
m
r
a
r
o
JEAN
31-dec-2012
fe
nf n01-jan-1992
I
s
l
MARIA
01-jan-1993
31-dec-2011
a -tra
b
o
01-jan-1994
Gl nTOM
on
KIM
01-jan-1994
30-jun-1994
SQL> select NAME,
from hr.emp order BY 2;
JAMES
31-dec-1992
31-dec-1994
8 rows selected.
SQL>
SQL> select NAME,
to_char(VALID_TIME_START, 'dd-mon-yyyy') "Start",
to_char(VALID_TIME_END, 'dd-mon-yyyy') "End"
from hr.emp VERSIONS PERIOD FOR valid_time
BETWEEN to_date('31-DEC-1992', 'dd-mon-yyyy')
AND
to_date('31-DEC-1993', 'dd-mon-yyyy');
Chapter 8 - Page 15
a
NAME
-------ADAM
SCOTT
JIM
JEAN
MARIA
JAMES
Start
-------------------01-jan-1990
01-jan-1991
01-jan-1992
01-jan-1992
01-jan-1993
31-dec-1992
End
-------------------31-dec-2010
31-dec-2011
31-dec-2013
31-dec-2012
31-dec-2011
31-dec-1994
6 rows selected.
SQL>
The query displays all employees whose VALID_TIME_START is less than or equal to '31DEC-1992' and VALID_TIME_END greater than '31-DEC-1993'.
d. Another example:
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
b
lo den
g
@ Stu
o
f
(in this
y
og use
l
o
hn se to
c
e
n End
NAME
Startn T
e
c
i
o
l
ti
-------- --------------------------------------a
le
b
m
r
a
JIM fo
01-jan-1992
31-dec-2013
er
f
n
I
s
31-dec-2012
alJEAN-tran01-jan-1992
b
o
01-jan-1994
Gl nTOM
on
SQL> select NAME,
from hr.emp
VERSIONS PERIOD FOR valid_time
BETWEEN to_date('31-DEC-2011', 'dd-mon-yyyy')
AND
to_date('31-DEC-2012', 'dd-mon-yyyy');
SQL>
The query displays all employees whose VALID_TIME_START is less than or equal to '31DEC-2011' and VALID_TIME_END greater than '31-DEC-2012'.
Chapter 8 - Page 16
a
11. Use new procedures of DBMS_FLASHBACK_ARCHIVE package to set the time visibility.
Set the visibility of temporal data to currently valid data within the valid time period at the
session level.
SQL> exec DBMS_FLASHBACK_ARCHIVE.ENABLE_AT_VALID_TIME('CURRENT')
SQL> select NAME,
from hr.emp;
NAME
-------JIM
TOM
Start
End
-------------------- -------------------01-jan-1992
31-dec-2013
01-jan-1994
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
12. Set the visibility of temporal data to the full table.
l- t Gu
a
b
SQL> exec DBMS_FLASHBACK_ARCHIVE.ENABLE_AT_VALID_TIME('ALL')
lo den
g
@ Stu
o
f
(in this
y
og use
l
o
SQL> /
hn se to
c
e
T cen
n
o
li
NAME
Start
End
ti
e
a
l
b
m
r ---------------------------------------------ra
o
f
e
f
n
I an01-jan-1990
s
31-dec-2010
lADAM
a
r
b
t
31-dec-2011
n- 01-jan-1991
Glo nSCOTT
o
JIM
01-jan-1992
31-dec-2013
SQL>
JEAN
MARIA
TOM
KIM
JAMES
01-jan-1992
01-jan-1993
01-jan-1994
01-jan-1994
31-dec-1992
31-dec-2012
31-dec-2011
30-jun-1994
31-dec-1994
8 rows selected.
SQL> exit
$
Chapter 8 - Page 17
a
Practice 8-3: Collecting User Context in FDA History Tables (optional)
Overview
In this practice, you collect user context information in the history table of an FDA enabled table.
Tasks
1.
Create the tablespace for Temporal History tables and enable the HR.TEST_TABLE1 table
for FDA.
a. Make sure you are at the ~/labs/FDA directory and your environment points to the
orcl instance.
b.
$ cd ~/labs/FDA
$ . oraenv
$
Create the hr.test_table1 table.
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
Connected to:
l- t Gu
a
b
lo d12.1.0.0.2
en
g
u
64bit Production
o@Analytics,
St Real
f
n
s
i
i
( Auditing
th options
y
Application Testing and Unified
g
e
lo o us
o
n
h se t
c
SQL> CREATE TABLE e
hr.test_table1
n varchar2(25), NOW date ) ;
T NAME
e
n
c
(NUM number(8),
i
o
l
ti
a
le
2
b
m
r
a
focreated.
er
Table
f
n
I
s
al -tran
b
o
Gl nSQL>
on INSERT INTO hr.test_table1 VALUES (1,'First test
row',sysdate);
1 row created.
SQL> INSERT INTO hr.test_table1 VALUES (2,'Second test
row',sysdate);
1 row created.
SQL> INSERT INTO hr.test_table1 VALUES (3,'Third test
row',NULL);
1 row created.
Chapter 8 - Page 18
a
SQL> COMMIT;
Commit complete.
SQL>
c.
Execute the FDA_setup.sql script.
SQL> @FDA_setup.sql
ALTER TABLE hr.test_table1 NO FLASHBACK ARCHIVE
*
ERROR at line 1:
ORA-55602: The table "HR"."TEST_TABLE1" is not enabled for
Flashback Archive
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
b
lo den
g
@ Stu
o
f
(in this
y
e
og usCONTENTS
l
DROP TABLESPACE fda_tbs o
INCLUDING
AND DATAFILES
n
o
t
*
ch nse
e
T
ERROR at line n
1:
e
c
i
o
l
i
t
ORA-00959:
a tablespace
le 'FDA_TBS' does not exist
b
m
r
a
fo sfer
n
I
al -tran
b
o
created.
Gl nTablespace
on
DROP FLASHBACK ARCHIVE fla1
*
ERROR at line 1:
ORA-55605: Incorrect Flashback Archive is specified
Flashback archive created.
Table altered.
SQL>
Chapter 8 - Page 19
a
2.
Set the context-level collection to TYPICAL. You want to collect the username and module
name of the user performing UPDATE executions on HR.EMPLOYEES. This level is sufficient
to retrieve this information.
SQL> EXEC DBMS_FLASHBACK_ARCHIVE.SET_CONTEXT_LEVEL('TYPICAL')
SQL>
3.
Perform some changes to the HR.EMPLOYEES table rows.
a. Perform two UPDATE statements as HR user. If the user HR is locked, unlock the
account first.
SQL> ALTER USER hr IDENTIFIED BY oracle_4U ACCOUNT UNLOCK;
User altered.
SQL> CONNECT HR/oracle_4U
Connected.
SQL> UPDATE hr.test_table1 SET NAME='Premier test row'
WHERE num=1;
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
b
lo den
g
@ Stu
1 row updated.
o
f
(in this
y
SQL> COMMIT;
og use
l
o
hn se to
c
e
n
Commit complete.T
e
n
c
i
o
l
ti
a
le
b
m
r
a
SQL> o
UPDATE
hr.test_table1
SET NAME='Primero test row'
r
f
e
f
n
l I WHERE
ns num=1;
a
a
r
b
t
nGlo n1orow
updated.
SQL>
COMMIT;
Commit complete.
SQL>
Chapter 8 - Page 20
a
b.
Retrieve the name of the flashback table.
SQL> select * from DBA_FLASHBACK_ARCHIVE_TABLES;
TABLE_NAME
OWNER_NAME
------------ ---------ARCHIVE_TABLE_NAME
----------------------TEST_TABLE1 HR
SYS_FBA_HIST_92273
FLASHBACK_ARCHIVE_NAME
---------------------STATUS
-----------FLA1
ENABLED
SQL>
c.
Retrieve the transaction ID inserted into the flashback archive table. If the rows do not
yet appear, truncate the HR.TEST_TABLE1 table.
SQL> COL rid FORMAT A20
SQL> COL name FORMAT A20
SQL> truncate table hr.test_table1;
s
) ha
om ฺ
c
ฺ
ch ide
Table truncated.
e
t
i
l- t Gu
a
b
lo den
SQL> select * from hr.SYS_FBA_HIST_92273;
g
@ Stu
o
f
isXID
(inENDSCN
h
RID
STARTSCN
O
t
y
g --------e
s
o
l
-------------------- -----------------------u
o
n
o
t
NUM NAME ch
e NOW
e
s
n
T
------------ ------------------------e
n
c
i
o
l
i
t
AAAXI4AAGAAAAD9AAB
a
le 3550155
b
m
r
a
r
test row
10-SEP-12
fo sf2eSecond
n
I
al -tran
b
o
3550155
Gl nAAAXI4AAGAAAAD9AAC
on
3 Third test row
10-SEP-12
AAAXI4AAGAAAAD9AAA
3548223
1 First test row
10-SEP-12
AAAXI4AAGAAAAD9AAA
3548223
3548739 08001100030D0000 U
1 Premier test row 10-SEP-12
AAAXI4AAGAAAAD9AAA
3548739
1 Primero test row
3550155 0A000B0043090000 U
10-SEP-12
SQL>
Chapter 8 - Page 21
a
4.
Collect the usernames of users who performed the UPDATE operations.
Connected.
SQL> set pages 100
SQL> select DBMS_FLASHBACK_ARCHIVE.GET_SYS_CONTEXT
('08001100030D0000', 'USERENV','SESSION_USER') "User Name",
VERSIONS_XID,VERSIONS_STARTTIME,VERSIONS_ENDTIME,
num, name
FROM hr.test_table1 VERSIONS BETWEEN scn minvalue
AND maxvalue
WHERE num=1;
2
3
4
5
6
7
User Name
---------------------------------------------------------------VERSIONS_XID
---------------VERSIONS_STARTTIME
---------------------------------------------------------------VERSIONS_ENDTIME
---------------------------------------------------------------NUM NAME
----------- ------------------HR
0A000B0043090000
10-SEP-12 01.24.01.000000000 AM
10-SEP-12 01.24.14.000000000 AM
1 Primero test row
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
b
lo den
g
@ Stu
o
f
(in this
y
og use
l
o
hn se to
c
e
T cen
n
o
li
ti
e
a
l
rm erab
o
f
In ansf
l
a
b
tr
Glo nonHR
10-SEP-12 01.24.01.000000000 AM
1 First test row
HR
08001100030D0000
10-SEP-12 01.24.01.000000000 AM
10-SEP-12 01.24.14.000000000 AM
1 Premier test row
SQL>
Chapter 8 - Page 22
a
5.
Collect the module names of the users who performed the UPDATE operations.
SQL> select DBMS_FLASHBACK_ARCHIVE.GET_SYS_CONTEXT
('0A000B0043090000', 'USERENV','module') "Module Name",
num, name
FROM hr.test_table1 VERSIONS BETWEEN scn minvalue
AND maxvalue
WHERE num=1;
2
3
4
5
6
Module Name
---------------------------------------------------------------NUM NAME
---------- ------------------------SQL*Plus
1 Primero test row
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
b
SQL*Plus
lo den
g
1 Premier test row
@ Stu
o
f
(in this
y
SQL> EXIT
og use
l
o
$
hn se to
c
e
T cen
n
o
li
ti
e
a
l
rm erab
o
f
In ansf
l
a
b
tr
Glo nonSQL*Plus
1 First test row
Chapter 8 - Page 23
a
Practice 8-4: Cleaning Up FDA
Overview
In this practice, you clean up the FDA tablespace.
Assumptions
You created the tablespace during Practice 8-3.
Tasks
1.
Reconnect as SYSDBA to the de-active flashback archive on HR.TEST_TABLE1 table and
drop the FDA_TBS tablespace.
Connected to:
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
SQL>
a
b
lo ARCHIVE;
SQL> ALTER TABLE hr.test_table1 NO FLASHBACK
en
g
d
u
o@ is St
f
n
i
(
Table altered.
th
y
g
e
lo o us
o
n
t
h sefla1;
SQL> DROP FLASHBACKcARCHIVE
e
T cen
n
o
li
ti
Flashback aarchive
dropped.
e
l
rm erab
o
f
f
In DROP
sTABLESPACE
l
SQL>
fda_tbs INCLUDING CONTENTS AND DATAFILES;
n
a
a
r
b
t
o
Gl nTablespace
on
dropped.
SQL> EXIT
$
Chapter 8 - Page 24
a
s
) ha
om ฺ
c
ฺ
ch9: ide
e
t
i
l- t Gu
Auditing
a
b
glo tuden
Chapter 9 @
nfo this S
i
(
ogy use
l
o
hn se to
c
e
T cen
n
o
li
ti
e
a
l
rm erab
o
f
In ansf
l
a
b
tr
Glo non-
Practices for Lesson 9: Auditing
Chapter 9 - Page 1
a
Practices Overview
In the practices for this lesson, you enable unified audit, configure for Data Pump export
auditing, and audit export and RMAN operations. You then view the audited data in the
UNIFIED_AUDIT_TRAIL view.
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
b
lo den
g
@ Stu
o
f
(in this
y
og use
l
o
hn se to
c
e
T cen
n
o
li
ti
e
a
l
rm erab
o
f
In ansf
l
a
b
tr
Glo non-
Chapter 9 - Page 2
a
Practice 9-1: Enabling Unified Auditing
Overview
In this practice, you enable unified auditing.
Tasks
1.
Shut down all Oracle processes of all instances
a. Shut down the listener.
$ . oraenv
[ORACLE_SID = [orcl] ? orcl
$
$ lsnrctl stop
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
Copyright (c) 1991, 2012, Oracle. All rights lreserved.
- t Gu
a
b
lo den
g
Connecting to
@ Stu
o
f
(in this
y
og use
l
o
$
hn se to
c
e
b. Shut down all instances.
T cen
n
o
li
$ ps -ef | tgrep
i pmon
e
a
l
b 1 0 Sep07 ?
oraclerm 5111
00:00:31 ora_pmon_orcl
a
r
o
f
e
f
n
oracle
18211
1
0
Sep05
?
00:00:53 ora_pmon_em12rep
I ans
l
a
b oracle
tr 25014
1 0 Sep07 ?
Glo noracle
on- 30114 29015 0 23:38 pts/3 00:00:00 grep pmon
$
1)
Shut down the orcl instance.
Connected to:
Testing options
Database closed.
Chapter 9 - Page 3
a
SQL> EXIT
$
2)
Shut down the cdb2 instance.
$ . oraenv
[ORACLE_SID = [orcl] ? cdb2
$
Connected to:
Testing options
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
Database closed.
a
b
lo den
g
@ Stu
o
f
(in this
SQL> EXIT
y
og use
l
$
o
n e to
hinstance.
c
3) Shut down the em12rep
e
T cens
n
a) Stop theoOMS.
li
ti
e
a
l
$ cd /u01/app/oracle/product/middleware/oms
b
rmOMS_HOME=/u01/app/oracle/product/middleware/oms
a
r
o
f
e
$ Iexport
n nsf
l
a
b n-tra
o
l
G n$o$OMS_HOME/bin/emctl stop oms
reserved.
Stopping WebTier...
WebTier Successfully Stopped
Stopping Oracle Management Server...
Oracle Management Server Successfully Stopped
Oracle Management Server is Down
$
b)
Shut down the repository database instance em12rep.
$ . oraenv
[ORACLE_SID = [orcl] ? em12rep
Chapter 9 - Page 4
a
$
Connected to:
Testing options
Database closed.
SQL> EXIT
$
s
) ha
om ฺ
c
ฺ
$ ps -ef | grep pmon
ch ide
e
t
i
u
l- grept G
oracle
5165 13370 0 09:14 pts/0
00:00:00
pmon
a
b
lo den
$
g
@ Stu
o
2. Enable the Unified Audit option.
f
(in this
$ cd $ORACLE_HOME/rdbms/lib gy
se
o
l
$ make -f ins_rdbms.mk uniaud_on
ioracle
u
o
ORACLE_HOME=$ORACLE_HOME
hn se to
c
e
T cen
/usr/bin/ar d
n
o
li
/u01/app/oracle/product/12.1.0/dbhome_1/rdbms/lib/libknlopt.a
ti
e
a
l
kzanang.o
rm erab
o
f
/usr/bin/ar
In ansf cr
l
a
/u01/app/oracle/product/12.1.0/dbhome_1/rdbms/lib/libknlopt.a
b n-tr
Glo n/u01/app/oracle/product/12.1.0/dbhome_1/rdbms/lib/kzaiang.o
o
chmod 755 /u01/app/oracle/product/12.1.0/dbhome_1/bin
4)
Verify that all instances are down.
- Linking Oracle
rm -f /u01/app/oracle/product/12.1.0/dbhome_1/rdbms/lib/oracle
/u01/app/oracle/product/12.1.0/dbhome_1/bin/orald -o
/u01/app/oracle/product/12.1.0/dbhome_1/rdbms/lib/oracle -m64 -z
noexecstack -L/u01/app/oracle/product/12.1.0/dbhome_1/rdbms/lib/
-L/u01/app/oracle/product/12.1.0/dbhome_1/lib/ L/u01/app/oracle/product/12.1.0/dbhome_1/lib/stubs/
-Wl,-E
/u01/app/oracle/product/12.1.0/dbhome_1/rdbms/lib/opimai.o
/u01/app/oracle/product/12.1.0/dbhome_1/rdbms/lib/ssoraed.o
/u01/app/oracle/product/12.1.0/dbhome_1/rdbms/lib/ttcsoi.o -Wl,-whole-archive -lperfsrv12 -Wl,--no-whole-archive
/u01/app/oracle/product/12.1.0/dbhome_1/lib/nautab.o
/u01/app/oracle/product/12.1.0/dbhome_1/lib/naeet.o
Chapter 9 - Page 5
a
/u01/app/oracle/product/12.1.0/dbhome_1/lib/naect.o
/u01/app/oracle/product/12.1.0/dbhome_1/lib/naedhs.o
/u01/app/oracle/product/12.1.0/dbhome_1/rdbms/lib/config.o lserver12 -lodm12 -lcell12 -lnnet12 -lskgxp12 -lsnls12 -lnls12
-lcore12 -lsnls12 -lnls12 -lcore12 -lsnls12 -lnls12 -lxml12 lcore12 -lunls12 -lsnls12 -lnls12 -lcore12 -lnls12 -lclient12 lvsn12 -lcommon12 -lgeneric12 -lknlopt ìf /usr/bin/ar tv
/u01/app/oracle/product/12.1.0/dbhome_1/rdbms/lib/libknlopt.a |
grep xsyeolap.o > /dev/null 2>&1 ; then echo "-loraolap12" ; fi`
-lskjcx12 -lslax12 -lpls12 -lrt -lplp12 -lserver12 -lclient12
-lvsn12 -lcommon12 -lgeneric12 ìf [ -f
/u01/app/oracle/product/12.1.0/dbhome_1/lib/libavserver12.a ] ;
then echo "-lavserver12" ; else echo "-lavstub12"; fi` ìf [ -f
/u01/app/oracle/product/12.1.0/dbhome_1/lib/libavclient12.a ] ;
then echo "-lavclient12" ; fi` -lknlopt -lslax12 -lpls12 -lrt lplp12 -ljavavm12 -lserver12 -lwwg `cat
/u01/app/oracle/product/12.1.0/dbhome_1/lib/ldflags`
lncrypt12 -lnsgr12 -lnzjs12 -ln12 -lnl12 -lnro12 `cat
lncrypt12 -lnsgr12 -lnzjs12 -ln12 -lnl12 -lnnz12 -lzt12 -lztkg12
-lmm -lsnls12 -lnls12 -lcore12 -lsnls12 -lnls12 -lcore12 lsnls12 -lnls12 -lxml12 -lcore12 -lunls12 -lsnls12 -lnls12 lcore12 -lnls12 -lztkg12 `cat
lncrypt12 -lnsgr12 -lnzjs12 -ln12 -lnl12 -lnro12 `cat
lncrypt12 -lnsgr12 -lnzjs12 -ln12 -lnl12 -lnnz12 -lzt12 -lztkg12
-lsnls12 -lnls12 -lcore12 -lsnls12 -lnls12 -lcore12 -lsnls12 lnls12 -lxml12 -lcore12 -lunls12 -lsnls12 -lnls12 -lcore12 lnls12 ìf /usr/bin/ar tv
/u01/app/oracle/product/12.1.0/dbhome_1/rdbms/lib/libknlopt.a |
grep "kxmnsd.o" > /dev/null 2>&1 ; then echo " " ; else echo "lordsdo12"; fi` L/u01/app/oracle/product/12.1.0/dbhome_1/ctx/lib/ -lctxc12 lctx12 -lzx12 -lgx12 -lctx12 -lzx12 -lgx12 -lordimt12 -lclsra12
-ldbcfg12 -lhasgen12 -lskgxn2 -lnnz12 -lzt12 -lxml12 -locr12 locrb12 -locrutl12 -lhasgen12 -lskgxn2 -lnnz12 -lzt12 -lxml12 lgeneric12 -loraz -llzopro -lorabz2 -lipp_z -lipp_bz2 lippdcemerged -lippsemerged -lippdcmerged -lippsmerged lippcore -lippcpemerged -lippcpmerged -lsnls12 -lnls12 lcore12 -lsnls12 -lnls12 -lcore12 -lsnls12 -lnls12 -lxml12 lcore12 -lunls12 -lsnls12 -lnls12 -lcore12 -lnls12 -lsnls12 lunls12 -lsnls12 -lnls12 -lcore12 -lsnls12 -lnls12 -lcore12 lsnls12 -lnls12 -lxml12 -lcore12 -lunls12 -lsnls12 -lnls12 lcore12 -lnls12 -lasmclnt12 -lcommon12 -lcore12 -laio -lons
`cat /u01/app/oracle/product/12.1.0/dbhome_1/lib/sysliblist` Wl,-rpath,/u01/app/oracle/product/12.1.0/dbhome_1/lib -lm
`cat /u01/app/oracle/product/12.1.0/dbhome_1/lib/sysliblist` ldl -lm
-L/u01/app/oracle/product/12.1.0/dbhome_1/lib
test ! -f /u01/app/oracle/product/12.1.0/dbhome_1/bin/oracle ||\
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
b
lo den
g
@ Stu
o
f
(in this
y
og use
l
o
hn se to
c
e
T cen
n
o
li
ti
e
a
l
rm erab
o
f
In ansf
l
a
b
tr
Glo non-
Chapter 9 - Page 6
a
mv -f
/u01/app/oracle/product/12.1.0/dbhome_1/bin/oracle
/u01/app/oracle/product/12.1.0/dbhome_1/bin/oracleO
mv /u01/app/oracle/product/12.1.0/dbhome_1/rdbms/lib/oracle
/u01/app/oracle/product/12.1.0/dbhome_1/bin/oracle
chmod 6751 /u01/app/oracle/product/12.1.0/dbhome_1/bin/oracle
$
3.
Restart the processes.
a. Restart the database orcl only.
$ . oraenv
[ORACLE_SID = [cdb2] ? orcl
$
s
) ha
om ฺ
c
ฺ
ch ide
SQL> startup mount
e
t
i
l- t Gu
a
b
lo den
g
@ Stu
o
bytes
f
is
(in bytes
h
Fixed Size
2266072
t
y
g usebytes
o557845544
l
Variable Size
o
to bytes
hn s285212672
Database Buffers
c
e
e
n 2306048 bytes
e
Redo Buffers n T
c
i
o
l
ti
Database mounted.
a
le
b
m
r
a
fo sfer
n
I
alSQL>-tALTER
an DATABASE ARCHIVELOG;
r
b
o
Gl non
Database altered.
Database altered.
SQL> EXIT
$
You can see that the Unified Auditing option is enabled in the SQL*Plus banner.
b. Restart the listener.
$ lsnrctl start
Chapter 9 - Page 7
a
please wait...
TNSLSNR for Linux: Version 12.1.0.0.2 - Production
System parameter file is
ra
/u01/app/oracle/diag/tnslsnr/host01/listener/alert/log.xml
Listening on:
Listening on:
(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=host01.example.com)(PO
RT=1521)))
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
Connecting to
b
lo den
g
@ Stu
o
f
(in this
-----------------------y
g use
oLISTENER
l
Alias
o
to for Linux: Version 12.1.0.0.2
hn sTNSLSNR
Version
c
e
e
T cen
- Production
n
o
li
ti
Start Date
05-JUL-2012 09:37:38
e
a
l
b
m
r
a
Uptime
r
o
f
e
f
n
I Level
off
lTrace
ns
a
a
r
b
t
nGlo nSecurity
o
SNMP
OFF
ra
Listener Log File
RT=1521)))
$
Chapter 9 - Page 8
a
Practice 9-2: Auditing Data Pump Export
Overview
In this practice, you create an audit policy to audit Data Pump export operations. Then you will
view the audited data after the export is completed.
Assumptions
Practice 9-1 successfully enabled unified audit.
Tasks
1.
Create a DP_POLICY for the component Data Pump, and more specifically for export
operations.
Connected to:
Testing
and Unified Auditing options
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
b
lo den
g
SQL> create audit policy DP_POL actions
tu
@ COMPONENT=datapump
o
S
f
export;
(in this
y
og use
l
o
Audit policy created.hn
to
c
e
e
s
T cen
n
o
SQL>
li
ti
e
a
l
b
2. Enable theoaudit
rm policy.
a
r
f
e
In audit
sfpolicy DP_POL;
SQL>
l
n
a
a
b n-tr
Glo nAudit
o succeeded.
SQL>
3.
Verify that the policy exists.
SQL>
SQL>
SQL>
2
col user_name format A10
col policy_name format A10
SELECT * FROM
AUDIT_UNIFIED_ENABLED_POLICIES
where POLICY_NAME like '%DP%';
USER_NAME POLICY_NAM ENABLED_ SUC FAI
---------- ---------- -------- --- --ALL USERS DP_POL
BY
YES YES
Chapter 9 - Page 9
a
SQL> EXIT
$
4.
Perform an export operation. Before exporting, ensure that the dump file does not exist;
else, the export command will fail.
$ rm /u01/app/oracle/admin/orcl/dpdump/HR_tables.dmp
rm: cannot remove
`/u01/app/oracle/admin/orcl/dpdump/HR_tables.dmp': No such file
or directory
$ expdp system/oracle_4U dumpfile=HR_tables tables=HR.EMPLOYEES
Connected to: Oracle Database 12c Enterprise Edition Release
Testing
Starting "SYSTEM"."SYS_EXPORT_TABLE_01": system/********
dumpfile=HR_tables tables=HR.EMPLOYEES
Estimate in progress using BLOCKS method...
Processing object type TABLE_EXPORT/TABLE/TABLE_DATA
Total estimation using BLOCKS method: 64 KB
Processing object type TABLE_EXPORT/TABLE/TABLE
Processing object type
TABLE_EXPORT/TABLE/GRANT/OWNER_GRANT/OBJECT_GRANT
Processing object type TABLE_EXPORT/TABLE/COMMENT
Processing object type TABLE_EXPORT/TABLE/INDEX/INDEX
Processing object type TABLE_EXPORT/TABLE/CONSTRAINT/CONSTRAINT
TABLE_EXPORT/TABLE/INDEX/STATISTICS/INDEX_STATISTICS
TABLE_EXPORT/TABLE/CONSTRAINT/REF_CONSTRAINT
Processing object type TABLE_EXPORT/TABLE/TRIGGER
TABLE_EXPORT/TABLE/STATISTICS/TABLE_STATISTICS
Processing object type TABLE_EXPORT/TABLE/STATISTICS/MARKER
. . exported "HR"."EMPLOYEES"
17.06
KB
107 rows
Master table "SYSTEM"."SYS_EXPORT_TABLE_01" successfully
loaded/unloaded
**************************************************************
Dump file set for SYSTEM.SYS_EXPORT_TABLE_01 is:
/u01/app/oracle/admin/orcl/dpdump/HR_tables.dmp
Job "SYSTEM"."SYS_EXPORT_TABLE_01" successfully completed at Thu
Jul 5 10:08:37 2012 elapsed 0 00:00:23
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
b
lo den
g
@ Stu
o
f
(in this
y
og use
l
o
hn se to
c
e
T cen
n
o
li
ti
e
a
l
rm erab
o
f
In ansf
l
a
b
tr
Glo non-
Chapter 9 - Page 10
a
$
5. View the resulting audit data. If the result shows no rows, then proceed with step 6, else
you will get the result of step 7.
Connected to:
Testing and Unified Auditing options
SQL> select DBUSERNAME, DP_TEXT_PARAMETERS1,
2
DP_BOOLEAN_PARAMETERS1
3 from
UNIFIED_AUDIT_TRAIL
4 where DP_TEXT_PARAMETERS1 is not null;
s
) ha
om ฺ
c
ฺ
ch ide
e
t
SQL>
i
l- t Gu
a
b
6. If the audited data is still in memory, flush the data to disk. lo
en
g
d
u
SQL> EXEC SYS.DBMS_AUDIT_MGMT.FLUSH_UNIFIED_AUDIT_TRAIL
o@ is St
f
n
i
(
th
y
g
e
lo ocompleted.
us
o
n
t
ech ense
T
SQL>
tiondata.le lic
7. View the resultingaaudit
m rab
SQL>fo
/r
n nsfe
I
l
baDBUSERNAME
tra
o
l
n
G no
-----------------------------no rows selected
DP_TEXT_PARAMETERS1
-------------------------------------------------------------DP_BOOLEAN_PARAMETERS1
-------------------------------------------------------------SYSTEM
MASTER TABLE: "SYSTEM"."SYS_EXPORT_TABLE_01" , JOB_TYPE:
EXPORT, METADATA_JOB_M
ODE: TABLE_EXPORT, JOB VERSION: 12.0.0.0.0, ACCESS METHOD:
AUTOMATIC, DATA OPTIO
NS: 0, DUMPER DIRECTORY: NULL REMOTE LINK: NULL, TABLE EXISTS:
NULL, PARTITION
OPTIONS: NONE
Chapter 9 - Page 11
a
MASTER_ONLY: FALSE, DATA_ONLY: FALSE, METADATA_ONLY: FALSE,
DUMPFILE_PRESENT: TR
UE, JOB_RESTARTED: FALSE
SQL> exit
$
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
b
lo den
g
@ Stu
o
f
(in this
y
og use
l
o
hn se to
c
e
T cen
n
o
li
ti
e
a
l
rm erab
o
f
In ansf
l
a
b
tr
Glo non-
Chapter 9 - Page 12
a
Practice 9-3: Auditing RMAN Backups
In this practice, you perform RMAN backups. Then you will view the audited data after RMAN
backups are completed. You do not have to create any audit policy for RMAN operations.
RMAN is by default audited.
Assumptions
Practice 9-1 successfully enabled unified audit.
Tasks
1.
Perform a RMAN backup of the USERS tablespace.
$ rman target /
connected to target database: ORCL (DBID=1315477536)
RMAN> backup tablespace USERS;
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
b
lo den
g
@ Stu
o
f
(in this
y
og use
l
o
hn se to
c
e
n piece 1 at 05-JUL-12
T starting
channel ORA_DISK_1:
e
n
c
i
o
l
ti
channel ORA_DISK_1:
a
le finished piece 1 at 05-JUL-12
b
m
r
a
piece
fo sfer
n
handle=/u01/app/oracle/fast_recovery_area/ORCL/backupset/2012_07
I
al_05/o1_mf_nnndf_TAG20120705T102453_7zbtvp2x_.bkp
an
r
b
t
o
comment=NONE
Gl ntag=TAG20120705T102453
on
Starting backup at 05-JUL-12
name/u01/app/oracle/oradata/orcl/users01.dbf
Finished backup at 05-JUL-12
RMAN> exit;
Recovery Manager complete.
$
2.
Perform a restore and recover after removing the USERS tablespace file.
a.
Find the data file name of the USERS tablespace and remove the file.
Connected to:
Chapter 9 - Page 13
a
SQL> select name from v$datafile;
NAME
-------------------------------------------------------------/u01/app/oracle/oradata/orcl/system01.dbf
SQL> !rm /u01/app/oracle/oradata/orcl/users01.dbf
s
) ha
om ฺ
c
ฺ
h ide
c
e
t
i
b. Put the tablespace OFFLINE.
l- t Gu
a
b
SQL> alter tablespace users offline immediate;
lo den
g
@ Stu
o
f
Tablespace altered.
(in this
y
og use
l
o
SQL> exit
hn se to
c
e
$
T cen
n
o
li file.
ti theledata
c. Restore and a
recover
b
rm
a
r
$ rman
target
/
o
f
e
In ansf
l
a
b n-tr to target database: ORCL (DBID=1315477536)
Glo nconnected
o
SQL>
RMAN> restore tablespace USERS;
Starting restore at 05-JUL-12
backup set
Chapter 9 - Page 14
a
/u01/app/oracle/fast_recovery_area/ORCL/backupset/2012_07_05/o1_
mf_nnndf_TAG20120705T102453_7zbtvp2x_.bkp
_05/o1_mf_nnndf_TAG20120705T102453_7zbtvp2x_.bkp
tag=TAG20120705T102453
Finished restore at 05-JUL-12
RMAN> recover tablespace USERS;
Starting recover at 05-JUL-12
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
Finished recover at 05-JUL-12
l- t Gu
a
b
lo den
g
@ Stu
RMAN> exit;
o
f
(in this
$
y
og use
l
d. Put the tablespace USERS backoonline.
hn se to
c
e
T cen
n
o
li
ti
e
Connected ato:
l
b
rm
a
r
o
Oracle
Database
12c Enterprise Edition Release 12.1.0.0.2 f
e
f
n
I
s
al64bit-trProduction
anPartitioning, OLAP, Data Mining, Real Application
b
o
With
the
Gl nTesting
on and Unified Auditing options
SQL> alter tablespace USERS online;
Tablespace altered.
SQL>
Chapter 9 - Page 15
a
3.
View the resulting audit data. If the result shows no rows, then proceed with step 4, else
you will get the result of step 5.
SQL> select DBUSERNAME, RMAN_OPERATION
2 from
UNIFIED_AUDIT_TRAIL
3 where RMAN_OPERATION is not null;
no rows selected
SQL>
4.
If the audited data is still in memory, flush the data to disk. But it is possible that the audit
data is already flushed in the audit tables.
SQL> EXEC SYS.DBMS_AUDIT_MGMT.FLUSH_UNIFIED_AUDIT_TRAIL
5.
View the resulting audit data.
s
) ha
SQL> /
om ฺ
c
ฺ
ch ide
DBUSERNAME
RMAN_OPERATION
e
t
i
l- t Gu
------------------------ -------------------a
b
lo den
SYS
Recover
g
tu
SYS
Restore fo@
S
(in this
SYS
Backup
y
og use
l
o
hn se to
SQL> exit
c
e
T cen
$
n
o
li
ti
e
a
l
rm erab
o
f
In ansf
l
a
b
tr
Glo non-
Chapter 9 - Page 16
a
s
) ha
om ฺ
c
ฺ
ch10: ide
e
t
i
u
Privileges balG
t
glo tuden
Chapter 10 @
nfo this S
i
(
ogy use
l
o
hn se to
c
e
T cen
n
o
li
ti
e
a
l
rm erab
o
f
In ansf
l
a
b
tr
Glo non-
Practices for Lesson 10: Privileges
Chapter 10 - Page 1
a
Practices Overview
In the practices for this lesson, you use SYSBACKUP new administrative privilege and manage
the password file, configure privilege capture for revoking privileges, and use the new INHERIT
PRIVILEGES privilege.
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
b
lo den
g
@ Stu
o
f
(in this
y
og use
l
o
hn se to
c
e
T cen
n
o
li
ti
e
a
l
rm erab
o
f
In ansf
l
a
b
tr
Glo non-
Chapter 10 - Page 2
a
Practice 10-1: Manage Password File with SYSBACKUP Entry
Overview
In this practice, you manage the password file with the new 12 format dedicated to new
administrative privileges like SYSBACKUP.
Tasks
1.
Make sure you are in the ~/labs/Security directory and your environment points to the
orcl instance.
$ cd ~/labs/Security
$ . oraenv
$
2.
Run the SYSBACKUP_setup.sh script to recreate the password file.
$ ./SYSBACKUP_setup.sh
$
s
) ha
om ฺ
c
ฺ
h ide
3. Connect with OS authentication with AS SYSBACKUP and check the usercconnected.
e
t
i
l- t Gu
$ sqlplus / as sysbackup
a
b
lo den
g
@ Stu
Connected to:
o
f
in thRelease
is
(Edition
12.1.0.0.2 y
g use
64bit Production
o
l
o Data
n
to Mining, Real Application
OLAP,
h
c
e
e
s
Testing and Unified
n options
T Auditing
e
n
c
i
o
l
ti
a
le
b
m
SQL> show
user
r
a
fois "SYSBACKUP"
er
f
n
USER
I
s
al -tran
b
o
Gl nSQL>
on
4.
List the privileges granted to SYSBACKUP user. Only a few privileges are granted to
SYSBACKUP user. The SYSBACKUP privilege is granted to SYSBACKUP user.
SQL> select * from session_privs;
PRIVILEGE
---------------------------------------SYSBACKUP
SELECT ANY TRANSACTION
SELECT ANY DICTIONARY
RESUMABLE
CREATE ANY DIRECTORY
ALTER DATABASE
Chapter 10 - Page 3
a
AUDIT ANY
CREATE ANY CLUSTER
CREATE ANY TABLE
DROP TABLESPACE
ALTER TABLESPACE
ALTER SESSION
ALTER SYSTEM
14 rows selected.
SQL>
5.
Connect AS SYSDBA and list the privileges granted to SYS user. There are much more
privileges granted to SYS user.
Connected.
SQL> select * from session_privs;
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
PRIVILEGE
l- t Gu
a
b
---------------------------------------- lo
en
g
d
u
EXEMPT DDL REDACTION POLICY
o@ is St
f
n
i
EXEMPT DML REDACTION POLICY
(
th
y
g
e
LOGMINING
olo to us
CREATE ANY CREDENTIALhn
ec ense
CREATE CREDENTIAL
T
n
o
lic
i
SET CONTAINER
t
e
a
l
m rabDATABASE
CLONEor
PLUGGABLE
f
fe DATABASE
n PLUGGABLE
I
s
CREATE
l
n
baTRANSLATE
tra ANY SQL
o
l
n
G nINHERIT
o
ANY PRIVILEGES
EXEMPT REDACTION POLICY
FLASHBACK ARCHIVE ADMINISTER
PURGE DBA_RECYCLEBIN
EM EXPRESS CONNECT
KEEP SYSGUID
KEEP DATE TIME
ADMINISTER KEY MANAGEMENT
DROP ANY SQL TRANSLATION PROFILE
USE ANY SQL TRANSLATION PROFILE
ALTER ANY SQL TRANSLATION PROFILE
CREATE ANY SQL TRANSLATION PROFILE
CREATE SQL TRANSLATION PROFILE
Chapter 10 - Page 4
a
ALTER DATABASE LINK
ALTER PUBLIC DATABASE LINK
ADMINISTER SQL MANAGEMENT OBJECT
UPDATE ANY CUBE DIMENSION
UPDATE ANY CUBE BUILD PROCESS
DROP ANY CUBE BUILD PROCESS
CREATE ANY CUBE BUILD PROCESS
CREATE CUBE BUILD PROCESS
INSERT ANY MEASURE FOLDER
DROP ANY MEASURE FOLDER
DELETE ANY MEASURE FOLDER
CREATE ANY MEASURE FOLDER
CREATE MEASURE FOLDER
UPDATE ANY CUBE
SELECT ANY CUBE
DROP ANY CUBE
CREATE ANY CUBE
ALTER ANY CUBE
CREATE CUBE
SELECT ANY CUBE DIMENSION
INSERT ANY CUBE DIMENSION
…
AUDIT SYSTEM
ALTER SYSTEM
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
b
lo den
g
@ Stu
o
f
(in this
y
og use
l
o
hn se to
c
e
T cen
n
o
li
233 rows selected.
ti
e
a
l
rm erab
o
f
In ansf
SQL>
l
a
b nfrom
-tr the V$PWFILE_USERS view. SYS user is the only user defined in the
G6.loDisplay
o
n file with SYSDBA and SYSOPER privileges only. SYSBACKUP user is not registered
password
in the password file.
SQL> select * from v$pwfile_users;
USERNAME SYSDB SYSOP SYSAS SYSBA SYSDG SYSKM CON_ID
-------- ----- ----- ----- ----- ----- ----- -----SYS
TRUE TRUE FALSE FALSE FALSE FALSE
0
SQL>
Chapter 10 - Page 5
a
7.
Create a new user JOHN that will be granted the SYSBACKUP privilege in order to perform
backup, restore, and recover operations, hence act as the SYSBACKUP user.
SQL> CREATE USER john IDENTIFIED BY oracle_4U;
User created.
SQL> GRANT create session, sysbackup TO john;
GRANT create session, sysbackup TO john
*
ERROR at line 1:
ORA-28017: The password file is in the legacy format.
SQL> exit
$
has
8. Because the password file had been created in legacy format, not compatible with the
)
SYSBACKUP entry, it does not accept any SYSBACKUP entry.
om ฺ
c
ฺ
a. Recreate the file in 12 format, compatible with the SYSBACKUP entry.ch
e
ide
t
i
u
l
$ cd $ORACLE_HOME/dbs
a nt G
b
o
l
$ rm orapworcl
g tude
@
$ orapwd file=orapworcl password=oracle_4U
fo is Sentries=10 format=12
n
i
(
$
th
y
g
e
lo file.o us
b. Finally register JOHN in the password
o
n
h se t
c
e
T cen
n
o
li
ti
e
a
l
Connected
to:
b
rm
a
r
o
f
e
Oracle
Database
f 12c Enterprise Edition Release 12.1.0.0.2 n Production
I
s
l
n
64bit
ra Partitioning, OLAP, Data Mining, Real Application
baWith
tthe
o
l
n
G no
SQL> grant create session, SYSBACKUP to john;
Grant succeeded.
SQL> select * from v$pwfile_users;
USERNAME
-------------SYS
JOHN
SYSDB
----TRUE
FALSE
SYSOP
----TRUE
FALSE
SYSAS
----FALSE
FALSE
SYSBA
----FALSE
TRUE
SYSDG
----FALSE
FALSE
SQL>
Chapter 10 - Page 6
SYSKM
CON_ID
----- ---------FALSE
0
FALSE
0
a
c.
Attempt a remote connection in SQL*Plus.
SQL> connect john/oracle_4U@orcl as SYSBACKUP
Connected.
SQL> SHOW USER
USER is "SYSBACKUP"
SQL> exit
$
d.
Test the remote connection in RMAN.
$ rman target john/oracle_4U@orcl
Recovery Manager: Release 12.1.0.1.0 - Production on Mon Nov 26
06:28:43 2012
Copyright (c) 1982, 2012, Oracle and/or its affiliates.
rights reserved.
All
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
b
lo den
g
@ Stu
o
f
(in this
y
og use
l
o
hn se to
c
e
T cen
n
i
connected to
target
ORCL (DBID=1327161403)
o
ldatabase:
ti
e
a
l
rm erab
o
f
RMAN>
In select
sf user from dual;
l
n
a
a
b n-tr
Glo nusing
o target database control file instead of recovery catalog
RMAN-00571: ==================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS
RMAN-00571: ==================================================
RMAN-00554: initialization of internal recovery manager package
failed
RMAN-04005: error from target database:
ORA-01031: insufficient privileges
$ rman target '"john/oracle_4U@orcl AS SYSBACKUP"'
USER
-----------------------------SYSBACKUP
RMAN> exit
$
Chapter 10 - Page 7
a
Practice 10-2: Capturing Privileges
Overview
In this practice, you capture privileges used by users during a short period, generate the capture
results, compare between used and unused privileges to decide which privileges might need to
be revoked.
Tasks
1.
Make sure you are at the ~/labs/Security directory and your environment points to the
orcl instance.
$ . oraenv
$
2.
Run the priv_setup.sql script to create JIM and TOM users, HR_MGR and
SALES_CLERK roles.
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
Connected to:
b
lo d12.1.0.0.2
en
Release
u
t
@
o
S
64bit Production
is Real Application
(infMining,
h
t
With the Partitioning, OLAP, y
Data
se
og options
Testing and Unified Auditing
l
u
o
hn se to
c
e
T cen
SQL> @priv_setup.sql
n
o
li
ti
Connected.
e
a
l
b
rm jimeracascade
dropfo
user
In ans*f
l
a
b n-trat line 1:
Glo nERROR
o
ORA-01918: user 'JIM' does not exist
User created.
drop user tom cascade
*
ERROR at line 1:
ORA-01918: user 'TOM' does not exist
Chapter 10 - Page 8
a
User created.
Grant succeeded.
drop
role HR_MGR
*
ERROR at line 1:
ORA-01919: role 'HR_MGR' does not exist
drop role SALES_CLERK
*
ERROR at line 1:
ORA-01919: role 'SALES_CLERK' does not exist
s
) ha
om ฺ
c
ฺ
drop role HR_MGR_JUNIOR
ch ide
e
t
i
*
l- t Gu
a
b
ERROR at line 1:
lo den
g
tu
@
ORA-01919: role 'HR_MGR_JUNIOR' does
not exist
o
S
f
(in this
y
og use
l
o
hn se to
c
e
T cen
Role created.
n
o
li
ti
e
a
l
rm erab
o
f
In succeeded.
sf
Grant
l
n
a
a
b
tr
Glo nonGrant succeeded.
Role created.
Grant succeeded.
Grant succeeded.
revoke select any table from oe
Chapter 10 - Page 9
a
*
ERROR at line 1:
ORA-01952: system privileges not granted to 'OE'
drop user u1 cascade
*
ERROR at line 1:
ORA-01918: user 'U1' does not exist
drop user u2 cascade
*
ERROR at line 1:
ORA-01918: user 'U2' does not exist
s
) ha
om ฺ
c
ฺ
drop user kate
ch ide
e
t
i
*
l- t Gu
a
b
ERROR at line 1:
lo den
g
@ Stu
ORA-01918: user 'KATE' does not exist
o
f
(in this
y
og use
l
o
hn se to
c
e
T cen
User created.
n
o
li
ti
e
a
l
rm erab
o
f
In succeeded.
sf
Grant
l
n
a
a
b
tr
Glo nonRevoke succeeded.
User created.
Grant succeeded.
User created.
Chapter 10 - Page 10
a
Grant succeeded.
Table created.
1 row created.
Commit complete.
Grant succeeded.
SQL>
3.
s
) ha
Define a capture of privileges used by all users. Use the following procedure.
exec SYS.DBMS_PRIVILEGE_CAPTURE.CREATE_CAPTURE ( name
=>
'All_privs', description
=> 'All privs used', type
=>
dbms_privilege_capture.g_database)
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
b
lo den
g
@ Stu
o
SQL> exec SYS.DBMS_PRIVILEGE_CAPTURE.CREATE_CAPTURE
( f
n
s
i
i
(
h
name
=>
'All_privs',
y se t g
o
l
description=> o 'All privs
u used', n
o
t
h
type
e
ec =>ensdbms_privilege_capture.g_database)
T
> > >
n
o
lic
i
t
e
PL/SQL procedure
successfully
completed.
a
l
b
m
r
a
fo sfer
n
I
alSQL>-tran
b
o
Gl non
a
4.
Start capturing the privileges while users are performing their daily work using privileges.
a. Start the capture.
SQL> exec SYS.DBMS_PRIVILEGE_CAPTURE.ENABLE_CAPTURE (name =>
'All_privs')
SQL>
b.
Run the priv_used_by_users.sql script. The script connects as JIM who deletes
rows from HR.EMPLOYEES table and TOM who selects rows from SH.SALES table.
SQL> @priv_used_by_users.sql
Connected.
s
) ha
24 rows deleted.
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
Connected.
a
b
lo den
g
tuQUANTITY_SOLD
@
o
S
PROD_ID CUST_ID TIME_ID
CHANNEL_ID
PROMO_ID
f
(in this
AMOUNT_SOLD
y
g use -------- ------------- ---o---------------- ------- --------l
o
-----------hn se to
c
e
120
6452 T
29-SEP-00
2
999
1
n
e
n
c
i
o
l
6.4ti
a 6452 b29-SEP-00
le
m
120
4
999
1
r
a
r
o
f
e
f
n
s
l I ran6.4
a
b
t
Glo nSQL>
onCommit complete.
5.
Stop the capture.
Connected.
SQL> exec SYS.DBMS_PRIVILEGE_CAPTURE.DISABLE_CAPTURE (name
=> 'All_privs')
SQL>
a
6.
Generate the capture results. It may take a few minutes.
SQL> exec SYS.DBMS_PRIVILEGE_CAPTURE.GENERATE_RESULT (name =>
'All_privs')
SQL>
7.
Display the object privileges used during the capture period.
SQL>
SQL>
SQL>
SQL>
SQL>
COL username FORMAT A10
COL object_owner FORMAT A12
COL object_name FORMAT A30
COL obj_priv FORMAT A25
SELECT username, object_owner, object_name, obj_priv
FROM dba_used_objprivs
WHERE username IN ('JIM', 'TOM');
2
3
USERNAME
OBJECT_OWNER OBJECT_NAME
OBJ_PRIV
---------- ------------ ------------------------------ ------JIM
SYS
DUAL
SELECT
JIM
SYSTEM
PRODUCT_PRIVS
SELECT
TOM
SYS
ORA$BASE
USE
TOM
SYSTEM
PRODUCT_PRIVS
SELECT
JIM
SYS
DBMS_APPLICATION_INFO
EXECUTE
JIM
SYS
ORA$BASE
USE
TOM
SYS
DUAL
SELECT
TOM
SH
SALES
SELECT
JIM
HR
EMPLOYEES
DELETE
TOM
SYS
DBMS_APPLICATION_INFO
EXECUTE
JIM
SYS
DUAL
SELECT
TOM
SYS
DUAL
SELECT
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
b
lo den
g
@ Stu
o
f
(in this
y
og use
l
o
hn se to
c
e
T cen
n
o
li
ti
e
a
l
rm erab
o
f
In ansf
l
a
b
tr
SQL>
8.
Display the system privileges used.
SQL> SELECT username, sys_priv FROM dba_used_sysprivs
WHERE username IN ('JIM', 'TOM');
2
USERNAME
SYS_PRIV
---------- ---------------------------------------TOM
CREATE SESSION
JIM
CREATE SESSION
a
SQL>
9.
Display the path of the privileges used if the privileges were granted to roles, and roles to
users.
SQL>
SQL>
SQL>
SQL>
COL object FORMAT A12
COL path FORMAT A32
SELECT username, obj_priv, object_name, path
FROM
dba_used_objprivs_path
WHERE username IN ('TOM','JIM')
AND object_name IN ('SALES','EMPLOYEES');
2
3
4
USERNAME
OBJ_PRIV
OBJECT
PATH
---------- ---------- ------------ --------------------------TOM
SELECT
SALES
GRANT_PATH('TOM',
'SALES_CLERK')
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
SQL>
l- t Gu
a
b
lo den table through
10. JIM is granted select, update, delete, insert privileges on g
HR.EMPLOYEES
@
HR_MGR role. He used only the DELETE privilege until
now. Stu
o
f
is
The unused privileges are visible in DBA_UNUSED_PRIVS
(in thview.
y
SQL> SELECT username, sys_priv,
object_name, path
se
og obj_priv,
l
u
o
n
o
t
FROM
dba_unused_privs
ech ense
T
WHERE username='JIM';
n
lic
2
3 atio
e
l
b
rm SYS_PRIV
a
USERNAME
OBJ_PRIV
OBJECT
PATH
r
o
f
e
f
n
I ans ---------- ---------- ------------ -----------------l---------a
b
-----------tr
Glo nJIM
onSELECT
EMPLOYEES
GRANT_PATH('JIM',
JIM
DELETE
'HR_MGR')
JIM
'HR_MGR')
JIM
'HR_MGR')
EMPLOYEES
GRANT_PATH('JIM', 'HR_MGR')
INSERT
EMPLOYEES
GRANT_PATH('JIM',
UPDATE
EMPLOYEES
GRANT_PATH('JIM',
SQL>
a
11. Compare used and unused privileges. Finally you decide to revoke the INSERT privilege
from JIM, but not impact other users who benefit from the HR_MGR role.
a.
You will first create a new role without the INSERT privilege and finally revoke the
HR_MGR role from JIM.
SQL> create role HR_MGR_JUNIOR;
Role created.
SQL> GRANT select, update, delete ON hr.employees
2 TO hr_mgr_junior;
Grant succeeded.
SQL>
b.
Grant the new role to JIM.
SQL> grant HR_MGR_JUNIOR to JIM;
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
b
SQL>
lo den
g
tu
@from JIM.
c. Finally revoke the powerful privileged role HR_MGR
o
S
f
(in this
SQL> revoke HR_MGR from JIM;
y
og use
l
o
Revoke succeeded.
hn se to
c
e
T cen
n
SQL>
o
li
ti
e
a
l
12. Display the definition
rm eofratheb capture. The ENABLED column that the All_privs capture
o
f
has been
In stopped.
sf
l
n
a
a
r name FORMAT A12
b SQL>
tCOL
Glo nSQL>
on- COL type FORMAT A12
Grant succeeded.
SQL>
SQL>
SQL>
2
COL enabled FORMAT A2
COL roles FORMAT A26
SELECT name, type, enabled,roles, context
FROM dba_priv_captures;
NAME
TYPE
EN ROLES
------------ ------------ -- -------------------------CONTEXT
-------------------------------------------------------------All_privs
DATABASE
N
SQL>
a
13. Delete the capture so as to remove all previous captured information from the views.
a. Execute the procedure.
SQL> exec SYS.DBMS_PRIVILEGE_CAPTURE.DROP_CAPTURE (name=>
'All_privs')
SQL>
b.
Verify that there is no data left of the All_privs capture.
SQL> SELECT username, sys_priv, obj_priv, object_name, path
2 FROM
dba_unused_privs
3 WHERE username='JIM';
no rows selected
s
) ha
SQL>
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
b
lo den
g
@ Stu
o
f
(in this
y
og use
l
o
hn se to
c
e
T cen
n
o
li
ti
e
a
l
rm erab
o
f
In ansf
l
a
b
tr
Glo non-
a
Practice 10-3: Capture Privileges Used Through Roles (Optional)
Overview
In this practice, you capture the privileges used by roles during a short period, generate the
capture results, compare between used and unused privileges to decide which privileges might
need to be revoked.
Tasks
1.
Define a capture of privileges used by roles HR_MGR_JUNIOR and SALES_CLERK. Use the
following procedure.
=> 'Role_privs', description
=> 'Privs used by HR_MGR_JUNIOR, SALES_CLERK', type
=> dbms_privilege_capture.g_role, roles
=> role_name_list('HR_MGR_JUNIOR', 'SALES_CLERK'))
s
) ha
SQL> exec SYS.DBMS_PRIVILEGE_CAPTURE.CREATE_CAPTURE ( name
=> 'Role_privs', description => 'Privs used by HR_MGR_JUNIOR, SALES_CLERK', type
=> dbms_privilege_capture.g_role, roles => role_name_list('HR_MGR_JUNIOR', 'SALES_CLERK'))
> > > >
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
b
lo den
g
@ Stu
o
f
(in this
y
og use
l
o
hn se to
SQL>
c
e
n perform their daily work.
T whileceusers
n
2. Start capturing the privileges
i
o
l
ti
a
le
a. Start the capture.
b
m
r
a
foexec sSYS.DBMS_PRIVILEGE_CAPTURE.ENABLE_CAPTURE
er
SQL>
(name =>
f
n
I
l
n
'Role_privs')
ba n-tra
o
l
G no
SQL>
b.
Connected.
0 rows deleted.
Commit complete.
Connected.
a
PROD_ID CUST_ID
AMOUNT_SOLD
------- -----------------120
6452
6.4
120
6452
6.4
TIME_ID
CHANNEL_ID PROMO_ID QUANTITY_SOLD
--------- ---------- -------- ------------- ---29-SEP-00
2
999
1
29-SEP-00
4
999
1
SQL>
3.
Stop the capture.
Connected.
=> 'Role_privs')
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
b
SQL>
lo den
g
4. Generate the capture results.
@ Stu
o
f
SQL> exec SYS.DBMS_PRIVILEGE_CAPTURE.GENERATE_RESULT
(name =>
(in this
y
g
e
'Role_privs')
lo o us
o
n
h se t
c
e
PL/SQL procedureTsuccessfully
n completed.
e
n
c
i
o
l
ati ble
SQL> rm
ra
o
f
e
f
n
5. Display
l I the robject
nsprivileges used by the roles HR_MGR_JUNIOR and SALES_CLERK during
a
a
b
t
the
capture
period.
Glo nSQL>
on- COL username FORMAT A10
SQL> COL owner FORMAT A8
SQL> COL object FORMAT A16
SQL> COL obj_priv FORMAT A10
SQL> COL used_role FORMAT A14
SQL> SELECT username, object_owner, object_name, obj_priv,
used_role
WHERE used_role IN ('HR_MGR_JUNIOR', 'SALES_CLERK');
2
3
USERNAME
OWNER
OBJECT
OBJ_PRIV
USED_ROLE
---------- -------- ---------------- ---------- -------------JIM
HR
EMPLOYEES
DELETE
HR_MGR_JUNIOR
TOM
SH
SALES
SELECT
SALES_CLERK
a
SQL>
6.
Display the system privileges used by the roles HR_MGR_JUNIOR and SALES_CLERK.
SQL> SELECT username, sys_priv, used_role
FROM dba_used_sysprivs
WHERE used_role IN ('HR_MGR_JUNIOR', 'SALES_CLERK');
2
3
no rows selected
SQL>
7.
HR_MGR_JUNIOR is granted select, update, delete on HR.EMPLOYEES table. The role used
by JIM during the capture period used the DELETE privilege until now.
The unused privileges are visible in DBA_UNUSED_PRIVS view.
SQL>
SQL>
SQL>
SQL>
SQL>
SQL>
COL username FORMAT A12
COL path FORMAT A32
COL object FORMAT A10
COL sys_priv FORMAT A10
SELECT sys_priv, obj_priv, object_name, path
FROM
dba_unused_privs
WHERE rolename IN ('HR_MGR_JUNIOR', 'SALES_CLERK');
2
3
SYS_PRIV
OBJ_PRIV
OBJECT
PATH
---------- ---------- ---------- ---------------------------SELECT
EMPLOYEES GRANT_PATH('HR_MGR_JUNIOR')
UPDATE
EMPLOYEES GRANT_PATH('HR_MGR_JUNIOR')
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
b
lo den
g
@ Stu
o
f
(in this
y
og use
l
o
hn se to
c
e
T cen
n
o
li
ti
e
a
l
rm erab
o
f
In ansf
l
a
SQL>
b
-trof unused privileges: this list helps you decide whether to revoke or not the
GloViewnothenlist
UPDATE and SELECT privileges granted through the HR_MGR_JUNIOR role.
8.
Display the definition of the capture. The ENABLED column shows that the Role_privs
capture has been stopped.
SQL>
SQL>
SQL>
SQL>
SQL>
COL name FORMAT A12
COL type FORMAT A12
COL enabled FORMAT A2
COL roles FORMAT A26
SELECT name, type, enabled,roles, context
FROM dba_priv_captures;
2
NAME
TYPE
EN ROLES
------------ ------------ -- -------------------------CONTEXT
a
-------------------------------------------------------------Role_privs
ROLE
N ROLE_ID_LIST(119, 115)
SQL>
9.
Delete the capture so as to remove all previous captured information from the views.
a. Execute the procedure.
SQL> exec SYS.DBMS_PRIVILEGE_CAPTURE.DROP_CAPTURE (name=>
'Role_privs')
SQL>
b.
Verify that there is no data left of the Role_privs capture.
SQL> SELECT sys_priv, obj_priv, object_name, path
FROM
dba_unused_privs
WHERE rolename IN ('HR_MGR_JUNIOR', 'SALES_CLERK');
2
3
no rows selected
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
b
lo den
SQL>
g
@ Stu
o
f
(in this
y
og use
l
o
hn se to
c
e
T cen
n
o
li
ti
e
a
l
rm erab
o
f
In ansf
l
a
b
tr
Glo non-
a
Practice 10-4: Capture Privileges Used In Contexts (Optional)
Overview
In this practice, you capture privileges used by the user TOM or by the specific role
SALES_CLERK during a short period, generate the capture results, compare between used and
unused privileges to decide which privileges might need to be revoked.
Tasks
1.
Define a capture of privileges used by the user TOM or by the specific role SALES_CLERK.
Use the following procedure.
=> 'Special_capt', description => 'Special', type
=> dbms_privilege_capture.g_role_and_context, roles
=>
role_name_list('SALES_CLERK'), condition =>
'SYS_CONTEXT(''USERENV'',''SESSION_USER'')=''TOM''')
s
) ha
om ฺ
c
ฺ
ch( - ide
SQL> exec SYS.DBMS_PRIVILEGE_CAPTURE.CREATE_CAPTURE
e
t
i
l- t Gu
name
=> 'Special_capt', a
b
lo den
description => 'Special', g
@ Stu
type
=> dbms_privilege_capture.g_role_and_context,
o
f
n
s
i
i
(
h
roles
=> role_name_list('SALES_CLERK'),
gy use t
o
l
condition =>
o to
n
'SYS_CONTEXT(''USERENV'',''SESSION_USER'')=''TOM''')
h
ec ense
T
> > > > >
n successfully
o
lic
i
PL/SQL procedure
completed.
t
e
a
l
b
m
r
ra
o
f
e
f
n
I ans
lSQL>
a
b
n-tr privileges while users perform their daily work using the privileges.
G2.loa.StartnStart
ocapturing
the capture.
SQL> exec SYS.DBMS_PRIVILEGE_CAPTURE.ENABLE_CAPTURE (name =>
'Special_capt')
SQL>
b.
Connected.
0 rows deleted.
a
Commit complete.
Connected.
PROD_ID CUST_ID
AMOUNT_SOLD
------- -----------------120
6452
6.4
120
6452
6.4
TIME_ID
CHANNEL_ID PROMO_ID QUANTITY_SOLD
--------- ---------- -------- ------------- ---29-SEP-00
2
999
1
29-SEP-00
4
999
1
SQL>
3.
Stop the capture.
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
b
lo den
g
@ Stu
o
f
(in this
y
SQL>
og use
l
o
4. Generate the capture results. It may
to minutes.
hn takesea few
c
e
SQL> exec SYS.DBMS_PRIVILEGE_CAPTURE.GENERATE_RESULT
(name =>
T cen
n
i
'Special_capt')
o
l
ti
a
le
b
m
r
a
fo procedure
er successfully completed.
f
n
PL/SQL
I
s
al -tran
b
o
Gl nSQL>
on
Connected.
=> 'Special_capt')
5.
Display the object privileges used.
SQL> COL username FORMAT A10
SQL> COL owner FORMAT A8
SQL> COL object FORMAT A16
SQL> COL obj_priv FORMAT A10
SQL> COL used_role FORMAT A14
SQL> SELECT username, object_owner, object_name, obj_priv,
used_role
WHERE username ='TOM' OR used_role='SALES_CLERK';
2
3
USERNAME
OWNER
OBJECT
OBJ_PRIV
USED_ROLE
---------- -------- ---------------- ---------- -------------Copyright © 2013, Oracle and/or its affiliates. All rights reserved.
a
TOM
SH
SALES
SELECT
SALES_CLERK
SQL>
6.
Display the system privileges used.
SQL> SELECT username, sys_priv FROM dba_used_sysprivs;
no rows selected
SQL>
7.
TOM is granted the select privilege on the SH.SALES table through SALES_CLERK role. He
used the privilege.
The unused privs are visible in DBA_UNUSED_PRIVS view.
There are not any unused privileges. So there is no privilege that has been unnecessarily
granted.
SQL> SELECT username, sys_priv, obj_priv, object_name, path
FROM
dba_unused_privs
WHERE username='TOM' OR rolename='SALES_CLERK';
2
3
no rows selected
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
b
lo den
g
@ Stu
SQL>
o
f
n thinformation
is
(icaptured
8. Delete the capture so as to remove all previous
from the views.
y
g
e
lo o us
SQL> exec SYS.DBMS_PRIVILEGE_CAPTURE.DROP_CAPTURE
(name=>
o
n
t
'Special_capt')
h
ec ense
T
n successfully
o
lic
i
t
PL/SQL procedure
completed.
e
a
l
b
m
r
ra
o
f
e
f
n
I ans
lSQL>
a
b
tr
Glo non-
a
Practice 10-5: Use INHERIT PRIVILEGES Privilege
Overview
In this practice you will use the new INHERIT PRIVILEGES privilege when creating invoker’s
rights procedures.
Assumptions
The priv_setup.sql script has been successfully executed at the beginning of Practice 10-1.
Tasks
1.
The developer U1 creates an invoker’s rights procedure that selects rows from U2.T1 table.
The user U1 is granted the SELECT privilege on U2.T1 table
a.
Connect as user U1.
SQL> connect u1/u1
Connected.
SQL>
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
b
lo den
g
@ Stu
o
f
(in this
y
END PROC2;
og use
l
o
/
hn se to
c
e
SQL> CREATE OR REPLACE
u1.proc2 (CODE in varchar2)
n
T cePROCEDURE
n
i
o
AUTHID CURRENT_USER
AS
l
ati ble
v_coderm
number;
ra
o
f
e
f
n
BEGIN
l I rans
a
b
SELECT
t code INTO v_code FROM u2.t1;
Glo ndbms_output.put_line('Code
onis: '||v_code);
b.
Create the U1.PROC2 procedure.
CREATE OR REPLACE PROCEDURE u1.proc2 (CODE in varchar2)
AUTHID CURRENT_USER AS
v_code number;
BEGIN
SELECT code INTO v_code FROM u2.t1;
dbms_output.put_line('Code is: '||v_code);
END PROC2;
/
2
3
4
5
Procedure created.
6
7
8
SQL>
c.
Execute the procedure to test that it works successfully.
SQL> exec U1.PROC2('Code')
Code is: 1
a
SQL>
d.
The developer U1 grants the EXECUTE privilege to the KATE user.
SQL> grant execute on U1.PROC2 to KATE;
Grant succeeded.
SQL>
2.
KATE wants to test the procedure.
a.
KATE has no privilege on U2.T1 table. KATE connects and executes the procedure.
SQL> CONNECT kate/kate
Connected.
SQL> BEGIN U1.PROC2('Code'); END;
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
b
lo den
g
@ Stu
o
f
(in this
y
og use
l
o
SQL>
hn se to
c
e
n
b. KATE grants the INHERIT
on user KATE to procedure owner U1 thus
T PRIVILEGES
e
n
c
i
o
l
allowing U1 to tinherit
i herleprivileges during the execution of the procedure
a
b PRIVILEGES ON USER kate TO U1;
m
r INHERIT
SQL> o
grant
a
r
f
e
In ansf
l
a
b n-trsucceeded.
Glo nGrant
o
*
ERROR at line 1:
ORA-06598: insufficient INHERIT PRIVILEGES privilege
ORA-06512: at "U1.PROC2", line 1
ORA-06512: at line 1
SQL>
c.
KATE re-executes the procedure.
Code is: 1
SQL>
3.
Display the users being granted the INHERIT PRIVILEGES privilege. There is a new
object type ‘USER’ and the table name is the user name controlling who can access his
privileges when he runs an invoker’s rights procedure.
a
Connected.
SQL>
SQL>
SQL>
SQL>
SQL>
2
COL privilege FORMAT A20
COL type FORMAT A6
COL table_name FORMAT A10
COL grantee FORMAT A8
select PRIVILEGE, TYPE, TABLE_NAME, GRANTEE
from DBA_TAB_PRIVS where grantee='U1';
PRIVILEGE
-------------------SELECT
INHERIT PRIVILEGES
TYPE
-----TABLE
USER
TABLE_NAME
---------T1
KATE
GRANTEE
-------U1
U1
s
) ha
SQL>
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
b
lo den
g
tu
@newuser;
SQL> CREATE USER newuser IDENTIFIED
BY
o
S
f
(in this
y
og use
User created.
l
o
hn se to
c
e
T cen
SQL>
n
o
li to NEWUSER.
ti granted
e
b. Check the privileges
a
l
b
rm ePRIVILEGE,
a
r
o
SQL>
select
TYPE, TABLE_NAME, GRANTEE
f
n nsf
I
l
from
DBA_TAB_PRIVS
ra
ba n-twhere
o
l
type='USER'
G no
and
table_name='NEWUSER';
4.
Be aware that newly created users are granted the INHERIT PRIVILEGES privilege
because the INHERIT PRIVILEGES privilege is granted to PUBLIC. The user KATE was
revoked the INHERIT PRIVILEGES privilege at the beginning of the practice.
a. Create a new user.
2
3
4
PRIVILEGE
TYPE
TABLE_NAME GRANTEE
-------------------- ------ ---------- -------INHERIT PRIVILEGES
USER
NEWUSER
PUBLIC
SQL> EXIT
$
a
Practice 10-6: INHERIT PRIVILEGES Privilege and BEQUEATH Views
Overview
In this practice you understand the different types of BEQUEATH views: the CURRENT_USER and
the DEFINER views.
Assumptions
The bequeath_setup.sql script is successfully completed.
Tasks
1.
Make sure you are at the ~/labs/Security directory and your environment points to the
orcl instance. Connect under SYSTEM user.
$ . oraenv
$
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
$ sqlplus SYSTEM/oracle_4U
b
lo den
g
@ Stu
o
f
Connected to:
(in this
y
l
u
64bit Production
o
to
hnOLAP,
c
e
Advanced Analytics, Real
e
s
n
T and
Application Testing
Unified
Auditing options
e
n
c
i
o
l
i
t
a
le
b
m
r
a
SQL>fo
er
f
n
I
s
alSQL>-t@bequeath_setup.sql
an
r
b
o
Gl nConnected.
on
REVOKE select any table from OE
2.
Execute the bequeath_setup.sql script. The script creates users and grants
appropriate privileges to the developer U1 and the end user KATE.
*
ERROR at line 1:
ORA-01952: system privileges not granted to 'OE'
User dropped.
User dropped.
User dropped.
User created.
a
Grant succeeded.
Revoke succeeded.
User created.
Grant succeeded.
SQL>
3.
The developer U1 creates a BEQUEATH CURRENT_USER view. The view displays the
current user connected.
a. The user U1 connects and creates the view V_WHOAMI.
SQL> CONNECT u1/u1
Connected.
SQL> CREATE OR REPLACE VIEW u1.v_whoami
BEQUEATH CURRENT_USER
AS SELECT ORA_INVOKING_USER "WHOAMI" FROM DUAL;
2
3
View created.
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
b
lo den
g
@ Stu
o
SQL>
f
s
isuccessfully.
(in works
h
t
b. The developer checks that the view V_WHOAMI
y
og use
l
o
SQL> select * from U1.V_WHOAMI;
hn se to
c
e
T cen
n
WHOAMI
o
li
ti
e
a
l
--------------------------------------------------------rm erab
U1Info
sf
l
n
a
a
b n-tr
Glo nSQL>
o
4.
The same developer U1 creates an BEQUEATH DEFINER view. The view displays the
current user connected.
a. The user U1 connects and creates the view V_WHOAMI_DEF.
SQL> CREATE OR REPLACE VIEW u1.v_whoami_def
BEQUEATH DEFINER
AS SELECT ORA_INVOKING_USER "WHOAMI" FROM DUAL;
2
3
View created.
SQL>
a
b.
The developer checks that the view V_WHOAMI_DEF works successfully.
SQL> select * from U1.V_WHOAMI_DEF;
WHOAMI
--------------------------------------------------------U1
SQL>
5.
The developer U1 grants the SELECT privilege to KATE on both views.
SQL> grant SELECT
on U1.V_WHOAMI to KATE;
Grant succeeded.
SQL> grant SELECT
on U1.V_WHOAMI_DEF to KATE;
s
) ha
om ฺ
c
ฺ
ch ide
SQL>
e
t
i
l- t Gu
a
6. KATE connects and selects data from the BEQUEATH DEFINER
view.
b
lo den
g
SQL> CONNECT kate/kate
@ Stu
o
f
Connected.
(in this
y
SQL> select * from U1.V_WHOAMI_DEF;
og use
l
o
hn se to
c
e
WHOAMI
T cen
n
o
-------------------------------------------------------li
ti
e
a
l
b
KATE rm
a
r
o
f
e
In ansf
l
a
b SQL>
-tr
n
G7.loKATE
o
n selects data from the BEQUEATH CURRENT_USER view.
Grant succeeded.
SQL> SELECT * FROM U1.V_WHOAMI;
select * from U1.V_WHOAMI
*
ERROR at line 1:
ORA-06598: insufficient INHERIT PRIVILEGES privilege
SQL>
a
8.
KATE grants the INHERIT PRIVILEGES ON USER KATE to the view owner U1, allowing
U1 to use her privileges during the view execution.
SQL> grant INHERIT PRIVILEGES ON USER kate TO U1;
Grant succeeded.
SQL>
9.
KATE attempts the statement on the BEQUEATH CURRENT_USER view.
SQL> select * from U1.V_WHOAMI;
WHOAMI
---------------------------------------------------------KATE
s
) ha
SQL> EXIT
$
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
b
lo den
g
@ Stu
o
f
(in this
y
og use
l
o
hn se to
c
e
T cen
n
o
li
ti
e
a
l
rm erab
o
f
In ansf
l
a
b
tr
Glo non-
a
s
) ha
om ฺ
c
ฺ
ch11: ide
e
t
i
l- t Gu
Oracle Data Redaction
a
b
glo tuden
Chapter 11 @
nfo this S
i
(
ogy use
l
o
hn se to
c
e
T cen
n
o
li
ti
e
a
l
rm erab
o
f
In ansf
l
a
b
tr
Glo non-
Chapter 11 - Page 1
a
Practices Overview
In the practice for this lesson, you use Oracle Data Redaction to redact values of shielded
columns of the HR.EMPLOYEES table.
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
b
lo den
g
@ Stu
o
f
(in this
y
og use
l
o
hn se to
c
e
T cen
n
o
li
ti
e
a
l
rm erab
o
f
In ansf
l
a
b
tr
Glo non-
Chapter 11 - Page 2
a
Practice 11-1: Redacting Protected Column Values with FULL
Redaction
Overview
In this practice you use FULL data redaction to display the SALARY column values from the
HR.EMPLOYEES as 0 instead of the real values.
Tasks
1.
Display the current values from the HR.EMPLOYEES table before redaction.
$ . oraenv
The Oracle base for
/u01/app/oracle
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
b
lo den
g
@ Stu
o
f
is
(in salary
SQL> SELECT employee_id, last_name,
h
t
y
og use
FROM hr.employees
l
o
to
WHERE department_id
hn =se100;
c
e
T cen
2
3
n
o
li
tiLAST_NAME
EMPLOYEE_ID
SALARY
e
a
l
b
m
r
a
-------------------------------------------fo sfer
n
I
12008
l
n108 Greenberg
a
a
r
b
t
Faviet
9000
Glo non- 109
110 Chen
8200
Connected to:
111 Sciarra
112 Urman
113 Popp
7700
7800
6900
6 rows selected.
SQL>
2.
Define a masking policy for the HR.EMPLOYEES table specifying full masking for the
SALARY column. SALARY is defined as NUMBER(8,2). In this example, by setting
EXPRESSION to 1=1, redaction is always performed because the expression always
evaluates to true.
The policy is enabled by default.
BEGIN
Chapter 11 - Page 3
a
DBMS_REDACT.ADD_POLICY
(object_schema => 'HR',
object_name
=> 'EMPLOYEES',
policy_name
=> 'EMPSAL_POLICY',
column_name
=> 'SALARY',
function_type => DBMS_REDACT.FULL,
expression => '1=1');
END;
/
SQL> BEGIN
DBMS_REDACT.ADD_POLICY
object_name
=> 'EMPLOYEES',
policy_name
=> 'EMPSAL_POLICY',
column_name
=> 'SALARY',
function_type => DBMS_REDACT.FULL,
END;
2
3
4
5
6
7
8
9
11 /
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
u
10 alG
t
b
lo den
g
@ Stu
o
f
(in this
y
og use
l
o
SQL>
hn se to
c
e
n that the policy has been created and is enabled.
T tocverify
3. Query REDACTION_POLICIES
e
n
i
o
l
ti underlwhat
This view also shows
e condition the redaction will be performed as shown in the
a
b
m
EXPRESSION
column.
r
a
foCOL object_owner
er
f
n
I
s
SQL>
FORMAT A12
l
n
a
a
r
b
t
n- COL object_name FORMAT A12
Glo nSQL>
o
SQL> COL policy_name FORMAT A14
SQL>
SQL>
SQL>
SQL>
COL expression FORMAT A12
COL enable FORMAT A6
COL policy_description FORMAT A10
SELECT * FROM redaction_policies;
OBJECT_OWNER OBJECT_NAME POLICY_NAME
EXPRESSION
ENABLE
------------ ------------ -------------- ------------ -----POLICY_DES
---------HR
EMPLOYEES
EMPSAL_POLICY 1=1
YES
Chapter 11 - Page 4
a
SQL>
4.
Display which columns will be redacted and what type of redaction will take place.
SQL>
SQL>
SQL>
SQL>
COL column_name FORMAT A10
COL function_typ FORMAT A14
COL function_parameters FORMAT A20
SELECT object_owner, object_name, column_name,
function_type, function_parameters
FROM redaction_columns;
2
3
OBJECT_OWNER OBJECT_NAME
COLUMN_NAM FUNCTION_TYPE
------------ ---------------- ---------- --------------------FUNCTION_PARAMETERS
-------------------HR
EMPLOYEES
SALARY
FULL REDACTION
s
) ha
SQL>
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
a. First grant the SELECT privilege to SH.
b
lo den
g
SQL> GRANT select ON hr.employees TO sh;
@ Stu
o
f
(in this
y
Grant succeeded.
og use
l
o
hn se to
c
SQL>
e
n
n isTlocked,
ceunlock
i
l
b. Connect as SH.tiIfoSH
the account.
e
a
l
bsh IDENTIFIED BY oracle_4U ACCOUNT UNLOCK;
SQL> ALTER
rm USER
a
r
o
f
e
In ansf
l
a
r
b User taltered.
Glo non5.
Now query the HR.EMPLOYEES table again and note that the value of the SALARY column
is 0 for all displayed rows.
SQL> CONNECT sh/oracle_4U
Connected.
SQL>
c.
Run the same select as in task 1.
SQL> SELECT employee_id, last_name, salary
FROM hr.employees
WHERE department_id = 100;
2
3
EMPLOYEE_ID LAST_NAME
SALARY
----------- ------------------------- ---------108 Greenberg
0
109 Faviet
0
Chapter 11 - Page 5
a
110
111
112
113
Chen
Sciarra
Urman
Popp
0
0
0
0
6 rows selected.
SQL>
6.
If you query as SYSDBA, the “real” value is displayed, not the redacted value as shown in
this example. Any user who is granted the EXEMPT REDACTION POLICY privilege
bypasses any redaction policy.
a. Connect as SYSDBA.
Connected.
SQL>
b.
Run the same select as in task 1.
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
SALARY
b
lo den
g
----------- ------------------------- ---------tu
@ S12008
o
f
108 Greenberg
(in this 9000
109 Faviet
y
og use
l
110 Chen
8200
o
n
o
t
h
111 Sciarra
7700
ec ense
T
112 Urman
7800
n
ic
o
l
i
t
e
a Poppbl
113
6900
m
r
a
r
o
nf nsfe
I
l
ba6 rows
traselected.
o
l
n
G no
SQL>
SQL> /
Chapter 11 - Page 6
a
Practice 11-2: Redacting Protected Column Values with PARTIAL
Redaction (optional)
Overview
In this practice, you use PARTIAL data redaction to display the HIRE_DATE column values from
the HR.EMPLOYEES as a partially redacted value instead of the real values.
Tasks
1.
Query the HR.EMPLOYEES table again and display the HIRE_DATE column.
SQL> SELECT employee_id, last_name, hire_date
FROM hr.employees
WHERE department_id = 100;
2
3
HIRE_DATE
----------- ------------------------- --------108 Greenberg
17-AUG-02
109 Faviet
16-AUG-02
110 Chen
28-SEP-05
111 Sciarra
30-SEP-05
112 Urman
07-MAR-06
113 Popp
07-DEC-07
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
b
lo den
g
@ Stu
o
f
(in this
y
6 rows selected.
og use
l
o
hn se to
c
e
SQL>
T cen
n
o
li the HIRE_DATE column. In this example, partial redaction
ti to redact
2. Alter the maskingapolicy
e
l
byear of hire.
is used to mask
rmthe eactual
a
r
o
f
In ansf
BEGIN
l
a
b DBMS_REDACT.ALTER_POLICY
n-tr
Glo no(object_schema
=> 'HR',
object_name
=> 'EMPLOYEES',
policy_name
=> 'EMPSAL_POLICY',
action
=> DBMS_REDACT.ADD_COLUMN,
column_name
=> 'HIRE_DATE',
function_type => DBMS_REDACT.PARTIAL,
function_parameters=> 'MDy2012',
END;
/
SQL> BEGIN
DBMS_REDACT.ALTER_POLICY
Chapter 11 - Page 7
a
object_name
=> 'EMPLOYEES',
policy_name
=> 'EMPSAL_POLICY',
action
=> DBMS_REDACT.ADD_COLUMN,
column_name
=> 'HIRE_DATE',
function_type => DBMS_REDACT.PARTIAL,
function_parameters=> 'MDy2012',
END;
/
2 3 4 5 6 7 8 9 10 11 12
SQL>
3.
Query REDACTION_POLICIES to verify that the policy has been created and is enabled.
This view also shows under what condition the redaction will be performed as shown in the
EXPRESSION column.
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t GuENABLE
OBJECT_OWNER OBJECT_NAME POLICY_NAME
EXPRESSION
a
b
------------ ------------ ----------------lo ---------en -----g
d
u
POLICY_DES
o@ is St
f
n
i
(
---------th
y
g
e
HR
EMPLOYEES
1=1
YES
loEMPSAL_POLICY
us
o
n
o
t
ch nse
e
T
SQL>
n
ce
i
o
l
i
t
e shows both masking functions defined on the
4. The REDACTION_COLUMNS
a
lview
b
m
r
a
HR.EMPLOYEES
fo table.
er
f
n
I
s
alSQL>-tSELECT
an object_owner, object_name, column_name,
r
b
o
Gl non function_type, function_parameters
FROM redaction_columns;
SQL> select * from redaction_policies;
2
3
OBJECT_OWNER OBJECT_NAME COLUMN_NAM FUNCTION_TYPE
------------ ------------ ---------- -----------------FUNCTION_PARAMETERS
-------------------HR
EMPLOYEES
SALARY
FULL REDACTION
HR
MDy2012
EMPLOYEES
HIRE_DATE
PARTIAL REDACTION
SQL>
Chapter 11 - Page 8
a
5.
Query HR.EMPLOYEES again as the SH user. ’12’ is displayed as the hire year for all the
rows selected.
Connected.
SQL> select employee_id, last_name, hire_date
from hr.employees
where department_id = 100;
2
3
HIRE_DATE
----------- ------------------------- --------108 Greenberg
17-AUG-12
109 Faviet
16-AUG-12
110 Chen
28-SEP-12
111 Sciarra
30-SEP-12
112 Urman
07-MAR-12
113 Popp
07-DEC-12
s
) ha
om ฺ
c
ฺ
ch ide
6 rows selected.
e
t
i
l- t Gu
a
b
lo den
SQL>
g
@ Stu
o
f
(in this
y
og use
l
o
hn se to
c
e
T cen
n
o
li
ti
e
a
l
rm erab
o
f
In ansf
l
a
b
tr
Glo non-
Chapter 11 - Page 9
a
Practice 11-3: Cleaning Up Redaction Policies
Overview
In this practice you clean up the redaction policy applied on the HR.EMPLOYEES table.
1.
Drop the redaction policy as SYSTEM user.
BEGIN
DBMS_REDACT.DROP_POLICY
object_name
=> 'EMPLOYEES',
policy_name
=> 'EMPSAL_POLICY');
END;
/
SQL> CONNECT system/oracle_4U
Connected.
SQL> BEGIN
DBMS_REDACT.DROP_POLICY
object_name
=> 'EMPLOYEES',
policy_name
=> 'EMPSAL_POLICY');
END;
/
2 3 4 5 6 7
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
b
lo den
g
@ Stu
o
f
(in this
y
og use
l
o
hn se to
c
e
T cen
SQL>
n
o
li
ti
e
a
l
rm erab
o
f
In ansf
l
a
b
tr
Glo non-
a
2.
Check that the values for the SALARY and HIRE_DATE columns are displayed without
redaction.
SQL> select employee_id, last_name, salary, hire_date
from hr.employees
where department_id = 100;
2
3
SALARY HIRE_DATE
----------- ------------------------- ---------- --------108 Greenberg
12008 17-AUG-02
109 Faviet
9000 16-AUG-02
110 Chen
8200 28-SEP-05
111 Sciarra
7700 30-SEP-05
112 Urman
7800 07-MAR-06
113 Popp
6900 07-DEC-07
s
) ha
6 rows selected.
om ฺ
c
ฺ
SQL> EXIT
ch ide
e
t
i
$
l- t Gu
a
b
lo den
g
@ Stu
o
f
(in this
y
og use
l
o
hn se to
c
e
T cen
n
o
li
ti
e
a
l
rm erab
o
f
In ansf
l
a
b
tr
Glo non-
a
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
b
lo den
g
@ Stu
o
f
(in this
y
og use
l
o
hn se to
c
e
T cen
n
o
li
ti
e
a
l
rm erab
o
f
In ansf
l
a
b
tr
Glo non-
a
s
) ha
om ฺ
c
ฺ
ch12: ide
e
t
i
u
l- New
Recovery Manager
G
a
t
b
lo Temporal
en
g
Features
and
d
u
o@
St
f
History
Enhancements
n
s
i
i
(
th
y
g
e
lo Chapter
us12
o
n
o
t
ech ense
T
n
o
lic
i
t
e
a
l
rm erab
o
f
In ansf
l
a
b
tr
Glo non-
Practices for Lesson 12: Recovery Manager New Features and Temporal History Enhancements
Chapter 12 - Page 1
a
Practices Overview
In the practice for this lesson, you use SYSBACKUP connection to RMAN and perform RMAN
commands. You use table recovery to recover the HR.EMPLOYEES table instead of using
Tablespace Point-In-Time Recovery (TSPITR) of the EXAMPLE tablespace or flashing back the
table.
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
b
lo den
g
@ Stu
o
f
(in this
y
og use
l
o
hn se to
c
e
T cen
n
o
li
ti
e
a
l
rm erab
o
f
In ansf
l
a
b
tr
Glo non-
Chapter 12 - Page 2
a
Practice 12-1: Using SYSBACKUP in RMAN
Overview
In this practice, you connect to RMAN and execute several SQL and SQL*Plus commands. You
will find out that some commands are not allowed to SYSBACKUP due to restricted privileges.
Tasks
1.
Connect to RMAN.
$ . oraenv
[ORACLE_SID = [orcl] ? orcl
$ rman TARGET '"/ AS SYSBACKUP"'
Recovery Manager: Release 12.1.0.0.2 - Production on Mon Jul 9
14:34:13 2012
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
b
lo den
g
@ Stu
o
RMAN> select user from dual;
f
(in this
y
e
sinstead
og file
l
using target database control
of recovery catalog
u
o
n
o
t
h
USER
ec ense
T
-----------------------------ion le lic
SYSBACKUP at
rm erab
o
f
In
sf
l
RMAN> an
a
b n-tr
G2.loExecute
o a backup command to back up the whole database and the archive logs.
nRMAN>
CONFIGURE CONTROLFILE AUTOBACKUP ON;
rights reserved.
All
Chapter 12 - Page 3
a
piece
_10/o1_mf_annnn_TAG20120910T010639_84th903m_.bkp
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
b
lo den
g
@ Stu
o
f
(in this
y
og use
l
o
hn se to
c
e
T cen
n
o
li
ti
e
a
l
rm erab
o
f
In ansf
l
a
b
tr
Glo non-
Chapter 12 - Page 4
a
name=/u01/app/oracle/oradata/orcl/sysaux01.dbf
name=/u01/app/oracle/oradata/orcl/system01.dbf
name=/u01/app/oracle/oradata/orcl/example01.dbf
name=/u01/app/oracle/oradata/orcl/undotbs01.dbf
name=/u01/app/oracle/oradata/orcl/users01.dbf
piece
_10/o1_mf_nnndf_TAG20120910T010735_84thbr78_.bkp
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
b
lo den
g
@ Stu
o
f
(in this
y
using channel ORA_DISK_1 log
se
u
o
to
channel ORA_DISK_1: starting
log backup set
hn se archived
c
e
channel ORA_DISK_1:
archived log(s) in backup set
n
T specifying
e
n
c
i
o
l
input archived
ti loglethread=1 sequence=60 RECID=38 STAMP=793588111
a
b starting piece 1 at 10-09-2012 01:08:31
m
channel
r ORA_DISK_1:
a
r
o
f
e
In anORA_DISK_1:
sf
channel
finished piece 1 at 10-09-2012 01:08:32
l
a
r
b
t
Glo npiece
onhandle=/u01/app/oracle/fast_recovery_area/ORCL/backupset/2012_09
_10/o1_mf_annnn_TAG20120910T010831_84thdhnl_.bkp
01:08:32
piece
handle=/u01/app/oracle/fast_recovery_area/ORCL/autobackup/2012_0
9_10/o1_mf_s_793588112_84thdkwt_.bkp comment=NONE
01:08:35
RMAN>
Chapter 12 - Page 5
a
3.
Execute the REPORT SCHEMA command.
RMAN> REPORT SCHEMA;
Report of database schema for database with db_unique_name ORCL
List of Permanent Datafiles
===========================
File Size(MB) Tablespace
RB segs Datafile Name
---- -------- -------------------- ------- --------------------1
800
SYSTEM
***
/u01/app/oracle/oradata/orcl/system01.dbf
2
500
EXAMPLE
***
3
970
SYSAUX
***
4
385
UNDOTBS1
***
6
5
USERS
***
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
b
lo den
g
List of Temporary Files
@ Stu
o
f
=======================
(in this
y
e
File Size(MB) Tablespace log
Tempfile Name
sMaxsize(MB)
u
o
---- -------- -------------------hn se to ----------- ----------------c
e
T cen
n
1
198
TEMP
32767
o
li
ti
e
a
l
/u01/app/oracle/oradata/orcl/temp01.dbf
rm erab
o
f
In ansf
l
a
RMAN>
b n-tr
G4.loExecute
no a SELECT command on an application table. The SYSBACKUP user is not granted
any object privilege on any application object, or the SELECT ANY TABLE system privilege.
RMAN> SELECT * FROM hr.employees;
RMAN-00571: ==================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ======
RMAN-00571: ==================================================
RMAN-03002: failure of sql statement command at 07/09/2012
14:40:31
RMAN>
Chapter 12 - Page 6
a
5.
Execute a SELECT command on a dictionary table. The SYSBACKUP user is granted the
system privilege SELECT ANY DICTIONARY.
a.
Select from DBA_TABLES.
RMAN> SELECT owner
FROM DBA_TABLES WHERE table_name='JOBS';
OWNER
------------------------------------------------------------HR
RMAN>
b.
Select from V$DATABASE.
RMAN> SELECT log_mode FROM v$database;
LOG_MODE
-----------ARCHIVELOG
s
) ha
om ฺ
c
ฺ
RMAN>
ch ide
e
t
i
l- t Gu
6.
Execute the DESCRIBE SQL*Plus command.
a
b
lo den
RMAN> DESC v$database
g
@ Stu
o
f
Name
(in thisNull? Type
y
--------------------------------------g use ------- ----------o
l
o
DBID
NUMBER
n e to
h
c
NAME
VARCHAR2(9)
Te cens
n
CREATED
DATE
tio le li
a
RESETLOGS_CHANGE#
NUMBER
rm erab
o
f
RESETLOGS_TIME
DATE
In ansf
l
a
NUMBER
b PRIOR_RESETLOGS_CHANGE#
n-tr
Glo noPRIOR_RESETLOGS_TIME
DATE
LOG_MODE
CHECKPOINT_CHANGE#
ARCHIVE_CHANGE#
CONTROLFILE_TYPE
CONTROLFILE_CREATED
CONTROLFILE_SEQUENCE#
CONTROLFILE_CHANGE#
CONTROLFILE_TIME
OPEN_RESETLOGS
VARCHAR2(12)
NUMBER
NUMBER
VARCHAR2(7)
DATE
NUMBER
NUMBER
DATE
VARCHAR2(11)
VERSION_TIME
OPEN_MODE
PROTECTION_MODE
DATE
VARCHAR2(20)
VARCHAR2(20)
Chapter 12 - Page 7
a
PROTECTION_LEVEL
REMOTE_ARCHIVE
ACTIVATION#
SWITCHOVER#
DATABASE_ROLE
ARCHIVELOG_CHANGE#
ARCHIVELOG_COMPRESSION
SWITCHOVER_STATUS
DATAGUARD_BROKER
GUARD_STATUS
SUPPLEMENTAL_LOG_DATA_MIN
SUPPLEMENTAL_LOG_DATA_PK
SUPPLEMENTAL_LOG_DATA_UI
FORCE_LOGGING
PLATFORM_ID
PLATFORM_NAME
RECOVERY_TARGET_INCARNATION#
LAST_OPEN_INCARNATION#
CURRENT_SCN
FLASHBACK_ON
SUPPLEMENTAL_LOG_DATA_FK
SUPPLEMENTAL_LOG_DATA_ALL
DB_UNIQUE_NAME
STANDBY_BECAME_PRIMARY_SCN
FS_FAILOVER_STATUS
FS_FAILOVER_CURRENT_TARGET
FS_FAILOVER_THRESHOLD
FS_FAILOVER_OBSERVER_PRESENT
FS_FAILOVER_OBSERVER_HOST
CONTROLFILE_CONVERTED
PRIMARY_DB_UNIQUE_NAME
SUPPLEMENTAL_LOG_DATA_PL
MIN_REQUIRED_CAPTURE_CHANGE#
CDB
CON_ID
PENDING_ROLE_CHANGE_TASKS
CON_DBID
VARCHAR2(20)
VARCHAR2(8)
NUMBER
NUMBER
VARCHAR2(16)
NUMBER
VARCHAR2(8)
VARCHAR2(20)
VARCHAR2(8)
VARCHAR2(7)
VARCHAR2(8)
VARCHAR2(3)
VARCHAR2(3)
VARCHAR2(39)
NUMBER
VARCHAR2(101)
NUMBER
NUMBER
NUMBER
VARCHAR2(18)
VARCHAR2(3)
VARCHAR2(3)
VARCHAR2(30)
NUMBER
VARCHAR2(22)
VARCHAR2(30)
NUMBER
VARCHAR2(7)
VARCHAR2(512)
VARCHAR2(3)
VARCHAR2(30)
VARCHAR2(3)
NUMBER
VARCHAR2(3)
NUMBER
VARCHAR2(512)
NUMBER
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
b
lo den
g
@ Stu
o
f
(in this
y
og use
l
o
hn se to
c
e
T cen
n
o
li
ti
e
a
l
rm erab
o
f
In ansf
l
a
b
tr
Glo non-
RMAN> EXIT
Recovery Manager complete.
$
Chapter 12 - Page 8
a
Practice 12-2: Recovering a Table by Using Table Recovery
In this practice, you perform a table recovery of HR.TEST_TABLE1 after having inadvertently
purged the table.
Assumption
The whole database backup has been successfully completed in the previous practice in task 2.
Tasks
1.
Create a new HR.TEST table and insert a few rows.
Connected to:
s
) ha
om ฺ
c
ฺ
ch; ide
e
date
)
t
i
l- t Gu
a
b
lo den
g
@ Stu
o
f
n this
(iVALUES
y
SQL> INSERT INTO hr.test_table1
og use (1,'First test
l
row',sysdate);
o
hn se to
c
e
n
e
1 row created.n T
c
i
o
l
ti
a
le
b
m
r
a
r hr.test_table1 VALUES (2,'Second test
SQL>fo
INSERTfe
INTO
n
I
s
row',sysdate);
al -tran
b
o
n
Gl n1orow
created.
SQL> CREATE TABLE hr.test_table1
(NUM number(8), NAME varchar2(25), NOW
2
Table created.
SQL> INSERT INTO hr.test_table1 VALUES (3,'Third test
row',NULL);
1 row created.
SQL> COMMIT;
Commit complete.
SQL> EXIT
$
Chapter 12 - Page 9
a
2.
Back up the tablespace where the table is stored.
$ rman TARGET /
RMAN> backup tablespace users;
name=/u01/app/oracle/oradata/orcl/users01.dbf
piece
_10/o1_mf_nnndf_TAG20120910T011327_84thoqyr_.bkp
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
b
lo den
g
@ Stu
o
f
(in this
y
og use
l
o
to Autobackup at 10-09-2012
hnand sSPFILE
Starting Control File
c
e
e
T cen
01:13:28
n
o
li
ti
piece
e
a
l
rm erab
o
f
9_10/o1_mf_s_793588409_84thospn_.bkp
comment=NONE
In ansf
l
a
b Finished
tr Control File and SPFILE Autobackup at 10-09-2012
Glo n01:13:31
onRMAN> exit
$
3.
You inadvertently purge the table.
a. Select the current sysdate. This date will help you recover the table back to the time
when the table was purged.
Connected to:
a
SQL> select timestamp_to_scn(current_timestamp)
2 from v$database;
TIMESTAMP_TO_SCN(CURRENT_TIMESTAMP)
----------------------------------2634118
SQL>
b.
Purge the table.
SQL> DROP TABLE hr.test_table1 PURGE;
Table dropped.
SQL> exit
$
4.
s
) ha
Perform the table recovery as the SYS user using /tmp/backup_test as the auxiliary
destination using your own SCN number retrieved in step 3.a.
om ฺ
c
ฺ
ch ide
$ mkdir /u01/app/oracle/backup_test
e
t
i
l- t Gu
a
$ rman TARGET /
b
lo den
g
@ Stu
o
f
connected to target database: ORCL
(DBID=1315953682)
(in this
y
e
og usUNTIL
l
RMAN> RECOVER TABLE hr.test_table1
SCN 2634118 AUXILIARY
o
n
o
t
h
DESTINATION '/u01/app/oracle/backup_test';
ec ense
T
n
o
lic
i
t
e
a
l
bat 10-09-2012 01:14:51
rmrecover
a
r
Starting
o
f
e
In ansf database control file instead of recovery catalog
l
using target
a
b n-tr log archived
Glo ncurrent
o
RMAN-05026: WARNING: presuming following set of tablespaces
applies to specified Point-in-Time
List of tablespaces expected to have UNDO segments
Tablespace SYSTEM
Tablespace UNDOTBS1
Creating automatic instance, with SID='zrik'
initialization parameters used for automatic instance:
db_name=ORCL
a
db_unique_name=zrik_pitr_ORCL
compatible=12.0.0.0.0
db_block_size=8192
db_files=200
sga_target=1G
processes=80
db_create_file_dest=/u01/app/oracle/backup_test
log_archive_dest_1='location=/u01/app/oracle/backup_test'
#No auxiliary parameter file used
starting up automatic instance ORCL
1068937216 bytes
s
) ha
om ฺ
c
ฺ
Fixed Size
2279272 bytes
ch ide
e
t
i
u
Variable Size
281020568 bytes alG
t
b
Database Buffers
780140544 bytes
lo den
g
@bytesStu
Redo Buffers
5496832
o
f
(in this
Automatic instance created
y
og use
l
o
contents of Memory Script:
hn se to
c
e
T cen
{
n
o
li in time
ti point
# set requested
e
a
l
b
rm scn
a
set until
2634118;
r
o
f
e
f controlfile
n nsthe
# Irestore
l
a
a
b n-tr clone controlfile;
Glo nrestore
o
# mount the controlfile
sql clone 'alter database mount clone database';
# archive current online log
sql 'alter system archive log current';
}
executing Memory Script
allocated channel: ORA_AUX_DISK_1
channel ORA_AUX_DISK_1: SID=72 device type=DISK
a
channel ORA_AUX_DISK_1: starting datafile backup set restore
channel ORA_AUX_DISK_1: restoring control file
channel ORA_AUX_DISK_1: reading from backup piece
/u01/app/oracle/fast_recovery_area/ORCL/autobackup/2012_09_10/o1
_mf_s_793588409_84thospn_.bkp
channel ORA_AUX_DISK_1: piece
9_10/o1_mf_s_793588409_84thospn_.bkp tag=TAG20120910T011328
channel ORA_AUX_DISK_1: restored backup piece 1
channel ORA_AUX_DISK_1: restore complete, elapsed time: 00:00:01
output file
name=/u01/app/oracle/backup_test/ORCL/controlfile/o1_mf_84tht7co
_.ctl
sql statement: alter database mount clone database
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
b
{
lo den
g
# set requested point in time
@ Stu
o
f
set until scn 2634118;
(in this
y
# set destinations for recovery
seand auxiliary set datafiles
og set
l
u
o
set newname for clonehn
datafileto 1 to new;
c
e
se 4 to new;
set newname for T
clone datafile
n
e
n clonelicdatafile 3 to new;
o
set newnametifor
a for bclone
le tempfile 1 to new;
m
set newname
r
a
r
fo all
etempfiles
f
n
#
switch
I
s
n
alswitch
aclone
r
b
t
tempfile all;
o
n
Gl n#orestore
the tablespaces in the recovery set and the auxiliary
sql statement: alter system archive log current
set
restore clone datafile 1, 4, 3;
switch clone datafile all;
}
executing command: SET NEWNAME
a
renamed tempfile 1 to
/u01/app/oracle/backup_test/ORCL/datafile/o1_mf_temp_%u_.tmp in
control file
using channel ORA_AUX_DISK_1
channel ORA_AUX_DISK_1: starting datafile backup set restore
channel ORA_AUX_DISK_1: specifying datafile(s) to restore from
backup set
channel ORA_AUX_DISK_1: restoring datafile 00001 to
/u01/app/oracle/backup_test/ORCL/datafile/o1_mf_system_%u_.dbf
/u01/app/oracle/backup_test/ORCL/datafile/o1_mf_undotbs1_%u_.dbf
/u01/app/oracle/backup_test/ORCL/datafile/o1_mf_sysaux_%u_.dbf
mf_nnndf_TAG20120910T010735_84thbr78_.bkp
_10/o1_mf_nnndf_TAG20120910T010735_84thbr78_.bkp
tag=TAG20120910T010735
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
b
lo den
g
@ Stu
o
f
(in this
y
og use
l
o
hn se to
c
e
T cen
n
o
li
ti
e
a
l
rm erab
o
f
In ansf
l
a
b datafile
tr 1 switched to datafile copy
Glo ninput
on- datafile copy RECID=4 STAMP=793588605 file
name=/u01/app/oracle/backup_test/ORCL/datafile/o1_mf_system_84th
th32_.dbf
datafile 4 switched to datafile copy
input datafile copy RECID=5 STAMP=793588605 file
name=/u01/app/oracle/backup_test/ORCL/datafile/o1_mf_undotbs1_84
thth4f_.dbf
name=/u01/app/oracle/backup_test/ORCL/datafile/o1_mf_sysaux_84th
th08_.dbf
{
a
# online the datafiles restored or switched
sql clone "alter database datafile 1 online";
# recover and open database read only
recover clone database tablespace "SYSTEM", "UNDOTBS1",
"SYSAUX";
sql clone 'alter database open read only';
}
sql statement: alter database datafile
1 online
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
sql statement: alter database datafile 3 online
l- t Gu
a
b
lo den
g
@ Stu
o
f
using channel ORA_AUX_DISK_1
(in this
y
og use
l
o
hn se to
c
e
T cen
n
o
li 1 with sequence 60 is already on disk as
archived log
i for thread
t
e
a
l
file rm
b
a
r
o
f
/u01/app/oracle/fast_recovery_area/ORCL/archivelog/2012_09_10/o1
e
In ansf
l
_mf_1_60_84thdh45_.arc
a
b n-tr log for thread 1 with sequence 61 is already on disk as
Glo narchived
o
file
sql statement: alter database datafile
4 online
_mf_1_61_84thrcth_.arc
archived log file
name=/u01/app/oracle/fast_recovery_area/ORCL/archivelog/2012_09_
10/o1_mf_1_60_84thdh45_.arc thread=1 sequence=60
archived log file
10/o1_mf_1_61_84thrcth_.arc thread=1 sequence=61
sql statement: alter database open read only
a
{
sql clone "create spfile from memory";
shutdown clone immediate;
startup clone nomount;
sql clone "alter system set control_files =
''/u01/app/oracle/backup_test/ORCL/controlfile/o1_mf_84tht7co_.c
tl'' comment=
''RMAN set'' scope=spfile";
shutdown clone immediate;
startup clone nomount;
# mount database
sql clone 'alter database mount clone database';
}
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
database closed
b
lo den
g
database dismounted
@ Stu
o
f
(in this
y
se started)
log o (not
u
o
connected to auxiliaryndatabase
t
Oracle instance T
started
ech ense
n
o
lic
i
t
e
a
l
Total r
System
b Area 1068937216 bytes
m Global
a
r
o
f
e
In ansf
l
a
Fixed
2279272 bytes
b n-trSize
o
l
G nVariable
o
Size
285214872 bytes
sql statement: create spfile from memory
Database Buffers
Redo Buffers
775946240 bytes
5496832 bytes
sql statement: alter system set control_files =
''/u01/app/oracle/backup_test/ORCL/controlfile/o1_mf_84tht7co_.c
tl'' comment= ''RMAN set'' scope=spfile
connected to auxiliary database (not started)
1068937216 bytes
a
Fixed Size
Variable Size
Database Buffers
Redo Buffers
2279272
285214872
775946240
5496832
bytes
bytes
bytes
bytes
sql statement: alter database mount clone database
{
# set destinations for recovery set and auxiliary set datafiles
set newname for datafile 6 to new;
# restore the tablespaces in the recovery set and the auxiliary
set
restore clone datafile 6;
switch clone datafile all;
}
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
b
lo den
g
@ Stu
o
f
(in this
y
og use
l
o
executing command: SET
to
hnNEWNAME
c
e
e
s
T cen
n
i
o
Starting restore
at l10-09-2012
01:17:26
ti
e
a
l
b
m
allocated
r channel:
ra ORA_AUX_DISK_1
o
f
e
f
n
channel
ORA_AUX_DISK_1:
SID=83 device type=DISK
I ans
l
a
b n-tr
Glo nchannel
o
ORA_AUX_DISK_1: starting datafile backup set restore
channel ORA_AUX_DISK_1: specifying datafile(s) to restore from
backup set
/u01/app/oracle/backup_test/ZRIK_PITR_ORCL/datafile/o1_mf_users_
%u_.dbf
mf_nnndf_TAG20120910T011327_84thoqyr_.bkp
_10/o1_mf_nnndf_TAG20120910T011327_84thoqyr_.bkp
tag=TAG20120910T011327
a
name=/u01/app/oracle/backup_test/ZRIK_PITR_ORCL/datafile/o1_mf_u
sers_84thx7b9_.dbf
{
# online the datafiles restored or switched
# recover and open resetlogs
recover clone database tablespace "USERS", "SYSTEM",
"UNDOTBS1", "SYSAUX" delete archivelog;
alter clone database open resetlogs;
}
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
b
lo den
g
@ Stu
o
f
(in thi6s online
y
sql statement: alter database
datafile
og use
l
o
hn se to01:17:28
c
Starting recover at
10-09-2012
e
T cen
n
using channel
ORA_AUX_DISK_1
o
li
ti
e
a
l
b
rmmedia
a
r
o
f
starting
recovery
e
In ansf
l
a
b n-tr
log for thread 1 with sequence 61 is already on disk
Glo narchived
o
file
as
_mf_1_61_84thrcth_.arc
archived log file
10/o1_mf_1_61_84thrcth_.arc thread=1 sequence=61
database opened
{
# create directory for datapump import
a
sql "create or replace directory TSPITR_DIROBJ_DPDIR as ''
/u01/app/oracle/backup_test''";
# create directory for datapump export
sql clone "create or replace directory TSPITR_DIROBJ_DPDIR as ''
/u01/app/oracle/backup_test''";
}
sql statement: create or replace directory TSPITR_DIROBJ_DPDIR
as ''/u01/app/oracle/backup_test''
sql statement: create or replace directory TSPITR_DIROBJ_DPDIR
as ''/u01/app/oracle/backup_test''
Performing export of tables...
EXPDP> Starting "SYS"."TSPITR_EXP_zrik_pgCo":
EXPDP> Estimate in progress using BLOCKS method...
EXPDP> Processing object type TABLE_EXPORT/TABLE/TABLE_DATA
EXPDP> Total estimation using BLOCKS method: 64 KB
EXPDP> Processing object type TABLE_EXPORT/TABLE/TABLE
EXPDP> Processing object type
TABLE_EXPORT/TABLE/STATISTICS/TABLE_STATISTICS
EXPDP> Processing object type
TABLE_EXPORT/TABLE/STATISTICS/MARKER
EXPDP> ORA-39127: unexpected error from call to export_string
:=SYS.DBMS_TRANSFORM_EXIMP.INSTANCE_INFO_EXP('AQ$_ORDERS_QUEUETA
BLE_S','IX',1,1,'12.00.00.00.00',newblock)
ORA-00376: file 2 cannot be read at this time
'/u01/app/oracle/oradata/orcl/example01.dbf'
ORA-06512: at "SYS.DBMS_TRANSFORM_EXIMP", line 197
ORA-06512: at "SYS.DBMS_METADATA", line 9796
ORA-39127: unexpected error from call to export_string
:=SYS.DBMS_TRANSFORM_EXIMP.INSTANCE_INFO_EXP('AQ$_STREAMS_QUEUE_
TABLE_S','IX',1,1,'12.00.00.00.00',newblock)
ORA-00376: file 2 cannot be read at this time
'/u01/app/oracle/oradata/orcl/example01.dbf'
ORA-06512: at "SYS.DBMS_TRANSFORM_EXIMP", line 197
ORA-06512: at "SYS.DBMS_METADATA", line 9796
EXPDP> . . exported "HR"."TEST_TABLE1"
5.992 KB
3 rows
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
b
lo den
g
@ Stu
o
f
(in this
y
og use
l
o
hn se to
c
e
T cen
n
o
li
ti
e
a
l
rm erab
o
f
In ansf
l
a
b
tr
Glo non-
a
EXPDP> Master table "SYS"."TSPITR_EXP_zrik_pgCo" successfully
loaded/unloaded
EXPDP>
****************************************************************
*
EXPDP> Dump file set for SYS.TSPITR_EXP_zrik_pgCo is:
EXPDP>
/u01/app/oracle/backup_test/tspitr_zrik_42203.dmp
EXPDP> Job "SYS"."TSPITR_EXP_zrik_pgCo" completed with 2
error(s) at Mon Sep 10 01:18:13 2012 elapsed 0 00:00:25
Export completed
{
# shutdown clone before import
shutdown clone abort
}
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
b
lo den
g
@ Stu
o
Performing import of tables...
f
(in this
IMPDP> Master table "SYS"."TSPITR_IMP_zrik_fmvv"
successfully
y
g use
o
loaded/unloaded
l
o to
n
IMPDP> Starting "SYS"."TSPITR_IMP_zrik_fmvv":
h
ec object
setype TABLE_EXPORT/TABLE/TABLE
n
T
IMPDP> Processing
e
c
tion le liobject
IMPDP> aProcessing
type TABLE_EXPORT/TABLE/TABLE_DATA
b
m
r
a
IMPDP>
.
.
imported
"HR"."TEST_TABLE1"
foKB sfer 3 rows
n
5.992
I
al IMPDP>
an Processing object type
r
b
t
o
Gl nTABLE_EXPORT/TABLE/STATISTICS/TABLE_STATISTICS
on
IMPDP> Processing object type
TABLE_EXPORT/TABLE/STATISTICS/MARKER
IMPDP> Job "SYS"."TSPITR_IMP_zrik_fmvv" successfully
completed at Mon Sep 10 01:18:26 2012 elapsed 0 00:00:04
Import completed
Removing automatic instance
Automatic instance removed
/u01/app/oracle/backup_test/ORCL/datafile/o1_mf_temp_84thw2c6_.t
mp deleted
a
/u01/app/oracle/backup_test/ZRIK_PITR_ORCL/onlinelog/o1_mf_3_84t
hxdfy_.log deleted
hxcdy_.log deleted
hxb7j_.log deleted
/u01/app/oracle/backup_test/ZRIK_PITR_ORCL/datafile/o1_mf_users_
84thx7b9_.dbf deleted
/u01/app/oracle/backup_test/ORCL/datafile/o1_mf_sysaux_84thth08_
.dbf deleted
/u01/app/oracle/backup_test/ORCL/datafile/o1_mf_undotbs1_84thth4
f_.dbf deleted
/u01/app/oracle/backup_test/ORCL/datafile/o1_mf_system_84thth32_
.dbf deleted
/u01/app/oracle/backup_test/ORCL/controlfile/o1_mf_84tht7co_.ctl
deleted
auxiliary instance file tspitr_zrik_42203.dmp deleted
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
b
lo den
g
@ Stu
o
f
(in this
y
og use
l
o
hn se to
c
e
RMAN>
T cen
n
o
li
tiis fully lrecovered.
5. Check that the table
e
a
b hr.test_table1;
m *rafrom
rselect
RMAN>
o
f
e
In ansf
l
a
b n-tr NUM NAME
NOW
Glo n---------o
------------------------- --------1 First test row
2 Second test row
3 Third test row
10-SEP-12
10-SEP-12
RMAN> exit
$
a
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
b
lo den
g
@ Stu
o
f
(in this
y
og use
l
o
hn se to
c
e
T cen
n
o
li
ti
e
a
l
rm erab
o
f
In ansf
l
a
b
tr
Glo non-
a
s
) ha
om ฺ
c
ฺ
ch13: ide
e
t
i
l- t Gu
Real-Time Database
a
b
lo den
g
Operation
Monitoring
@ Stu
o
f
Chapter
(in 13 this
y
og use
l
o
hn se to
c
e
T cen
n
o
li
ti
e
a
l
rm erab
o
f
In ansf
l
a
b
tr
Glo non-
Practices for Lesson 13: Real-Time Database Operation Monitoring
Chapter 13 - Page 1
a
Practices Overview
In the practices for this lesson, you monitor database operations in the orcl database. You will
use DBMS_SQL_MONITOR new functions to identify and start operations and Enterprise
Manager Database Express to monitor database operations execution.
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
b
lo den
g
@ Stu
o
f
(in this
y
og use
l
o
hn se to
c
e
T cen
n
o
li
ti
e
a
l
rm erab
o
f
In ansf
l
a
b
tr
Glo non-
Chapter 13 - Page 2
a
Practice 13-1: Starting Enterprise Manager Database Express
Overview
In this practice, you will use Enterprise Manager Database Express or Enterprise Manager
Cloud Control to monitor the various database operations started in the orcl database.
Tasks
1.
Check if Enterprise Manager Database Express is started.
a. Verify that the value of the DISPATCHERS instance parameter is set to
(PROTOCOL=TCP)(SERVICE=orclXDB).
Connected to:
s
) ha
om ฺ
c
ฺ
SQL> SHOW PARAMETER dispatchers
ch ide
e
t
i
NAME
TYPE
VALUE
l- t Gu
a
b
------------------- ---------- ------------lo den
g
@ Stu
dispatchers
string
(PROTOCOL=TCP)(SERVICE=orclXDB)
o
f
max_dispatchers
integer
(in this
y
og use
l
o
SQL>
hn se to
c
e
n
Tused cforeEnterprise
b. Select the port number
Manager Database Express.
n
i
o
l
tidbms_xdb_config.gethttpport
SQL> SELECT
FROM DUAL;
a
le
b
m
r
a
fo sfer
n
I
GETHTTPPORT
al-----------an
r
b
t
o
Gl non 5500
SQL> EXIT
$
c.
Verify that the listener is running and listens to the localhost (yourserver) using TCP
protocol, the port 5500, the http presentation with RAW session data.
$ lsnrctl status
Connecting to
-----------------------Alias
LISTENER
Chapter 13 - Page 3
a
Version
- Production
Start Date
14-AUG-2012 09:05:04
Uptime
Trace Level
off
Security
SNMP
OFF
ra
Listener Log File
/u01/app/oracle/diag/tnslsnr/youserver/listener/alert/log.xml
(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=<Your
hostname>)(PORT=1521)))
(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=<Your
hostname>)(PORT=5500))(Presentation=HTTP)(Session=RAW))
Services Summary...
service...
service...
$
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
b
lo den
g
@ Stu
o
f
(in this
y
og use
l
o
hn se to
c
e
T cen
n
o
li
i
t
e
a
l
d. Launch r
am
browser and
buse the following URL http://localhost:5500/em.
a
r
o
f
e
e. Log
SYS
Inin with
sf and oracle_4U password as SYSDBA.
l
n
a
a
2. IfbEM Database
-tr Express is not started, proceed with the following steps; else, go to the next
n
Glopractice.
o
n
a.
Set the value of the DISPATCHERS instance parameter to
(PROTOCOL=TCP)(SERVICE=orclXDB).
Connected to:
SQL> ALTER SYSTEM SET dispatchers =
'(PROTOCOL=TCP)(SERVICE=orclXDB)' scope=both;
Chapter 13 - Page 4
a
System altered.
SQL>
b.
Set the HTTP port.
SQL> EXEC DBMS_XDB_CONFIG.setHTTPSPort(5500)
SQL> EXIT
$
c.
Restart or start the listener.
$ lsnrctl stop
Connecting to
$
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
$ lsnrctl start
b
lo den
g
@ Stu
o
f
(in this
y
please wait...
og use
l
o
to
hn se12.1.0.0.2
c
TNSLSNR for Linux:eVersion
- Production
n
T
e
n filelicis
System parameter
o
i
t
a
le
b
a
ra form
r
ewritten
f
n
I
s
Log
messages
to
l
n
a
a
r
b
t
Glo nListening
onon:
Listening on:
(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=youserver)(PORT=1521))
)
Connecting to
-----------------------Alias
LISTENER
Version
- Production
Start Date
14-AUG-2012 15:25:04
Chapter 13 - Page 5
a
Uptime
Trace Level
off
Security
SNMP
OFF
ra
Listener Log File
(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=youserver)(PORT=1521))
)
$
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
b
lo den
g
@ Stu
o
f
(in this
y
og use
l
o
hn se to
c
e
T cen
n
o
li
ti
e
a
l
rm erab
o
f
In ansf
l
a
b
tr
Glo nond.
Launch a browser and use the following URL https://localhost:5500/em.
Chapter 13 - Page 6
a
Practice 13-2: Identifying and Starting Database Operations
Overview
In this practice, you use the DBMS_SQL_MONITOR.BEGIN_OPERATION function to identify and
start several database operations.
Tasks
1.
Make sure you are at the ~/labs/DBOps directory and your environment points to the
orcl instance.
$ cd ~/labs/DBOps
$ . oraenv
$
2.
Run the DBOps_setup.sh script to ensure that the users SH and HR can connect and get
the SELECT ANY DICTIONARY privilege for the purpose of this practice.
s
) ha
om ฺ
c
ฺ
h ide
tec10G01:38:52
i
SQL*Plus: Release 12.1.0.0.2 Production on Monl-Sep
u
a
t
2012
b
lo den
g
tureserved.
@rights
o
S
f
All
(in this
y
se10 2012 01:38:09 +00:00
logMono Sep
u
o
Last Successful login n
time:
h se t
c
e
T cen
n
Connected to:
o
li
i
t
e
a
l
Oracle m
Database b
12c Enterprise Edition Release 12.1.0.0.2 rProduction
a
r
o
64bit
f
e
In anPartitioning,
sf
l
With the
OLAP, Advanced Analytics, Real
a
b Application
tr
o
l
n
G no
$ ./DBOps_setup.sh
User altered.
User altered.
Grant succeeded.
Database altered.
Disconnected from Oracle Database 12c Enterprise Edition Release
Application Testing
Chapter 13 - Page 7
a
$
3.
Start a first database operation. Name the database operation ORA.HR.select. The
database operation performs several SELECT statements as HR user. The database
operation is started and completed with the DBMS_MONITOR.BEGIN_OPERATION and
DBMS_MONITOR.END_OPERATION procedures. Move on to the next step while the
statement is running, to monitor the database operation with EM Database Express.
If you want to have time to view the database operation ORA.HR.select in EM Database
Express or EM Cloud Control, do not execute EXEC
DBMS_SQL_MONITOR.END_OPERATION right after the third SELECT statement.
VAR dbop_eid NUMBER;
EXEC :dbop_eid := DBMS_SQL_MONITOR.BEGIN_OPERATION
('ORA.HR.select', forced_tracking => 'Y')
select a.employee_id, b.employee_id from hr.employees a,
hr.employees b;
select * from hr.departments;
select a.table_name , b.table_name FROM dict a, dict b;
EXEC DBMS_SQL_MONITOR.END_OPERATION('ORA.HR.select', :dbop_eid)
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
Connected to:
a
b
Release
lo d12.1.0.0.2
en
u
64bit Production
o@ is Real
St Application
f
n
i
With the Partitioning, OLAP, Data
Mining,
(
th
y
Testing
g
e
lo o us
o
n
h se t
c
e
T cen
n
SQL> VAR dbop_eid
NUMBER;
o
li
ti
e
a
l
SQL> EXEC
b := DBMS_SQL_MONITOR.BEGIN_OPERATION
rm :dbop_eid
a
r
o
f
e
('ORA.HR.select',
forced_tracking => 'Y')
n nsf
I
l
baPL/SQL
traprocedure successfully completed.
o
l
n
G no
$ sqlplus hr/oracle_4U
SQL> SELECT a.employee_id, b.employee_id FROM hr.employees a,
hr.employees b;
…
6889 rows selected.
SQL> SELECT * FROM hr.departments;
…
27 rows selected.
SQL> SELECT a.table_name , b.table_name FROM dict a, dict b;
…
SQL> EXEC DBMS_SQL_MONITOR.END_OPERATION('ORA.HR.select',
:dbop_eid)
Chapter 13 - Page 8
a
SQL>
4.
View the database operation currently executing using Enterprise Manager Database
Express. From Enterprise Manager Database Express, click the “Performance” menu, then
the “Performance Hub” option, then the “Monitored SQL” tab. The list of database
operations appears.
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
$ . oraenv
a
b
lo den
g
@ Stu
The Oracle base for
o
f
ORACLE_HOME=/u01/app/oracle/product/12.1.0/dbhome_1
is
(in this
y
g
e
/u01/app/oracle
lo o us
$ sqlplus / as sysdbahno
t
c
e
e
s
T cen
n
o
liinstance.
Connected to
ti an idle
e
a
l
SQL> startup
rm erab
o
f
ORACLE
In ainstance
sf started.
l
n
a
b n-tr
Glo nTotal
o System Global Area 400846848 bytes
Note: You could also use Enterprise Manager Cloud Control.
1) Restart the Enterprise Manager Repository Database em12rep.
Fixed Size
Variable Size
Database Buffers
Redo Buffers
Database mounted.
Database opened.
SQL> EXIT
$
2)
2271568
339740336
50331648
8503296
bytes
bytes
bytes
bytes
Restart the OMS.
$ export OMS_HOME=/u01/app/oracle/product/middleware/oms
$ $OMS_HOME/bin/emctl start oms
Chapter 13 - Page 9
a
reserved.
Starting WebTier...
heavy usage.
least 4096.
$
3)
Use https://localhost:7802/em to get the Enterprise Manager Cloud
Control console appear, enter sysman in the User Name field and Oracle123 in
the Password field. Then click Login.
The status of the orcl database agent might be in unreachable state because the
oms was stopped in practice 9. However this has no incidence on other practices.
From the “Targets” menu, click “Databases” and select orcl. Log in as SYS with
oracle_4U password as SYSDBA. From the “Performance” menu, click the “SQL
“Monitoring” option. You will see the same list as the one from Enterprise Manager
Database Express.
From another session connected to orcl, start a second database operation. Name the
database operation ORA.SYSTEM.select. The database operation performs several
SELECT statements as SYSTEM user using the DBMS_MONITOR.BEGIN_OPERATION
procedure to monitor.
('ORA.SYSTEM.select', forced_tracking => 'Y')
SELECT a.table_name , b.table_name FROM dict a, dict b;
SELECT c.cust_id, c.cust_last_name, c.cust_first_name,
s.prod_id, p.prod_name, s.time_id
FROM
sh.sales s, sh.customers c, sh.products p
WHERE s.cust_id = c.cust_id
AND
s.prod_id = p.prod_id
ORDER BY c.cust_id, s.time_id;
EXEC DBMS_SQL_MONITOR.END_OPERATION('ORA.SYSTEM.select',
:dbop_eid)
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
b
lo den
g
@ Stu
o
f
5.
(in this
y
og use
l
o
hn se to
c
e
T cen
n
o
li
ti
e
a
l
rm erab
o
f
In ansf
l
a
b
tr
Glo non-
$ . oraenv
ORACLE_SID = [em12rep] ? orcl
The Oracle base for
/u01/app/oracle
a
Connected to:
SQL> VAR dbop_eid NUMBER;
SQL> EXEC :dbop_eid := DBMS_SQL_MONITOR.BEGIN_OPERATION
('ORA.SYSTEM.select', forced_tracking => 'Y')
SQL> SELECT a.table_name , b.table_name FROM dict a, dict b;
…
s
) ha
SQL> SELECT c.cust_id, c.cust_last_name, c.cust_first_name,
FROM
AND
…
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
b
lo den
g
@ Stu
o
f
(in this
y
SQL> EXEC DBMS_SQL_MONITOR.END_OPERATION('ORA.SYSTEM.select',
og use
l
o
:dbop_eid)
hn se to
c
e
T cen
n
o
li
PL/SQL procedure
successfully
completed.
ti
e
a
l
b
m
r
ra
o
f
e
f
n
I ans
lSQL>
a
b
-tr database operation currently executing using Enterprise Manager Database
View the
new
n
G6.loExpress.
o
n From Enterprise Manager Database Express, refresh the list of database
operations. From Enterprise Manager Cloud Control, you will view the same list of
monitored database operations.
7.
Start a third database operation in another session. Name the database operation
ORA.SH.select2. The database operation performs several SELECT statements as SH
user using the DBMS_MONITOR.BEGIN_OPERATION procedure to monitor.
a
('ORA.SH.select2', forced_tracking => 'Y')
SELECT c.cust_id, c.cust_last_name, c.cust_first_name,
FROM
AND
EXEC DBMS_SQL_MONITOR.END_OPERATION('ORA.SH.select2', :dbop_eid)
$ . oraenv
ORACLE_SID = [em12rep] ? orcl
The Oracle base for
/u01/app/oracle
$ sqlplus sh/oracle_4U
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
b
lo den
g
@ Stu
o
f
(in this
y
se
SQL> VAR dbop_eid NUMBER;log
u
o
to
SQL> EXEC :dbop_eidc:=
hnDBMS_SQL_MONITOR.BEGIN_OPERATION
e
e
s
('ORA.SH.select2',
=> 'Y')
n
T forced_tracking
e
n
c
i
o
l
ati bsuccessfully
le
PL/SQLrm
procedure
completed.
a
r
o
f
e
In SELECT
sf c.cust_id, c.cust_last_name, c.cust_first_name,
l
n
a
SQL>
a
b n-tr
p.prod_name, s.time_id
Glo ns.prod_id,
o
FROM
Connected to:
AND
…
SQL> EXEC DBMS_SQL_MONITOR.END_OPERATION('ORA.SH.select2',
:dbop_eid)
SQL> EXIT
$
a
8.
View the new database operation using Enterprise Manager Database Express or
Enterprise Manager Cloud Control.
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
b
lo den
g
@ Stu
o
f
(in this
y
og use
l
o
hn se to
c
e
T cen
n
o
li
ti
e
a
l
rm erab
o
f
In ansf
l
a
b
tr
Glo non-
a
Practice 13-3: Identifying and Starting Database Load Operations
(Optional)
Overview
In this practice, you will use Enterprise Manager Database Express to monitor the various
database load operations started in the orcl database.
Tasks
1.
Start a new database operation. Name the database operation ORA.SYSTEM.load. The
database operation performs several bulk-load statements as the SYSTEM user using the
DBMS_MONITOR.BEGIN_OPERATION procedure to monitor.
('ORA.SYSTEM.load', forced_tracking => 'Y')
INSERT /*+ append */ INTO sh.sales NOLOGGING SELECT * from
sh.sales WHERE ROWNUM < 1000;
INSERT /*+ append */ INTO sh.sales NOLOGGING SELECT * from
sh.sales;
EXEC DBMS_SQL_MONITOR.END_OPERATION('ORA.SYSTEM.load',
:dbop_eid)
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
b
lo den
g
@ Stu
o
f
Connected to:
(in this
y
l
u
o
64bit Production
to
hnOLAP,
c
e
Data Mining, Real Application
e
s
n options
T Auditing
e
Testing and Unified
n
c
i
o
l
ti
a
le
b
m
r
a
SQL>fo
VAR dbop_eid
er NUMBER;
f
n
I
s
DBMS_SQL_MONITOR.BEGIN_OPERATION
alSQL>-tEXEC
an :dbop_eid :=
r
b
o
('ORA.SYSTEM.load',
forced_tracking
=> 'Y')
Gl non
SQL> INSERT /*+ append */ INTO sh.sales NOLOGGING SELECT * from
sh.sales WHERE ROWNUM<1000;
999 rows created.
SQL> INSERT /*+ append */ INTO sh.sales NOLOGGING SELECT * from
sh.sales;
919842 rows created.
SQL> EXEC DBMS_SQL_MONITOR.END_OPERATION('ORA.SYSTEM.load',
:dbop_eid)
a
SQL>
2.
View the new database operation currently executing using Enterprise Manager Database
Express. From Enterprise Manager Database Express, refresh the list of database
operations.
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
b
lo den
g
@ Stu
o
f
(in this
y
og use
l
o
hn se to
c
e
T cen
n
o
li
ti
e
a
l
rm erab
o
f
In ansf
l
a
b
tr
Glo non-
a
Practice 13-4: Cleaning Up
Overview
In this practice, you revoke the SELECT ANY DICTIONARY privilege granted to HR and SH
users for the purpose of these practices.
1. Revoke the SELECT ANY DICTIONARY privilege granted to HR and SH users.
Connected to:
Testing options
SQL> REVOKE SELECT ANY DICTIONARY FROM hr, sh;
Revoke succeeded.
SQL> EXIT
$
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
b
lo den
g
@ Stu
o
f
(in this
y
og use
l
o
hn se to
c
e
T cen
n
o
li
ti
e
a
l
rm erab
o
f
In ansf
l
a
b
tr
Glo non-
a
s
) ha
om ฺ
c
ฺ
ch14: ide
e
t
i
u
l- Changes
Schema and b
Data
G
a
t
lo den
g
Management
@ Stu
o
f
Chapter
(in 14 this
y
og use
l
o
hn se to
c
e
T cen
n
o
li
ti
e
a
l
rm erab
o
f
In ansf
l
a
b
tr
Glo non-
Practices for Lesson 14: Schema and Data Changes Management
Chapter 14 - Page 1
a
Practices Overview
In the practice for this lesson, you will use the Schema Change Plans demo to understand and
view the steps required during schema change plan usage between two databases to
synchronize two databases together.
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
b
lo den
g
@ Stu
o
f
(in this
y
og use
l
o
hn se to
c
e
T cen
n
o
li
ti
e
a
l
rm erab
o
f
In ansf
l
a
b
tr
Glo non-
Chapter 14 - Page 2
a
Practice 14-1: Using Schema Change Plans
Overview
In this practice you use a browser to execute the Schema Change Plans demonstration.
Tasks
1.
Launch a browser and enter:
file:////home/oracle/demos/Schema_Change_Plans/Schema_change_plan.html.
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
b
lo den
g
@ Stu
o
f
(in this
y
og use
l
o
hn se to
c
e
T cen
n
o
li
ti
e
a
l
rm erab
o
f
In ansf
l
a
b
tr
Glo non-
Chapter 14 - Page 3
a
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
b
lo den
g
@ Stu
o
f
(in this
y
og use
l
o
hn se to
c
e
T cen
n
o
li
ti
e
a
l
rm erab
o
f
In ansf
l
a
b
tr
Glo non-
Chapter 14 - Page 4
a
s
) ha
om ฺ
c
ฺ
ch15: iSQL
de
e
t
i
u
l
Tuning Enhancements
ba ent G
o
l
g tud
Chapter 15 @
o
nf this S
i
(
ogy use
l
o
hn se to
c
e
T cen
n
o
li
ti
e
a
l
rm erab
o
f
In ansf
l
a
b
tr
Glo non-
Practices for Lesson 15: SQL Tuning Enhancements
Chapter 15 - Page 1
a
Practices Overview
This practice covers the dynamic plans part of the Adaptive Execution Plans feature in Oracle
Database 12c.
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
b
lo den
g
@ Stu
o
f
(in this
y
og use
l
o
hn se to
c
e
T cen
n
o
li
ti
e
a
l
rm erab
o
f
In ansf
l
a
b
tr
Glo non-
Chapter 15 - Page 2
a
Practice 15-1: Using Dynamic Plans
Overview
In this practice, you will use the dynamic plans part of the Adaptive Execution Plans feature.
Tasks
1. Unlock the OE account in ORCL database and then grant SELECT ANY DICTIONARY
privilege to OE.
$ . oraenv
Connected to:
s
) ha
om ฺ
c
ฺ
ch ide
e
SQL> grant select any dictionary to oe;
t
i
l- t Gu
a
b
lo den
g
Grant succeeded.
@ Stu
o
f
(in this
y
SQL> alter user oe account unlock;
og use
l
o
User altered.
hn se to
c
e
n by oracle_4U;
T
e
n
c
SQL> alter user
oe
identified
i
o
l
ti
a
le
b
m
r
a
foaltered.
er
f
User
n
I
s
al -tran
b
o
Gl nSQL>
on
2.
From the same SQL*Plus session, connect as user OE and show the execution plan of the
following query without executing it:
select /*+ monitor*/ product_name
from order_items o, product_information p
where o.unit_price = 15
and quantity > 1
and p.product_id = o.product_id;
SQL> connect oe/oracle_4U
Connected.
SQL>
SQL> explain plan for
select /*+ monitor*/ product_name
Chapter 15 - Page 3
a
from order_items o, product_information p
and quantity > 1
and p.product_id = o.product_id;
2
3
4
5
6
Explained.
SQL> set lines 300
SQL> select * from table(dbms_xplan.display());
PLAN_TABLE_OUTPUT
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------Plan hash value: 1255158658
-----------------------------------------------------------------------------------------------------| Id
|
| Operation
| Name
| Rows
s
) ha
| Bytes | Cost (%CPU)| Time
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
b
lo den
g
@ Stu
o
f
(in this
y
og use
l
o
hn se to
c
e
T cen
n
o
li
ti
e
a
l
rm erab
o
f
In ansf
l
a
b
tr
Glo non-
-----------------------------------------------------------------------------------------------------|
|
0 | SELECT STATEMENT
|
|
4 |
128 |
|
|
1 |
|
|
|
|
|
|
2 |
|
|
4 |
128 |
7
(0)| 00:00:01
|*
|
3 |
TABLE ACCESS FULL
| ORDER_ITEMS
|
4 |
48 |
3
(0)| 00:00:01
|*
|
4 |
INDEX UNIQUE SCAN
| PRODUCT_INFORMATION_PK |
1 |
|
0
(0)| 00:00:01
|
|
5 |
1 |
20 |
1
(0)| 00:00:01
NESTED LOOPS
NESTED LOOPS
TABLE ACCESS BY INDEX ROWID| PRODUCT_INFORMATION
|
7
(0)| 00:00:01
|
PLAN_TABLE_OUTPUT
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------Predicate Information (identified by operation id):
--------------------------------------------------3 - filter("O"."UNIT_PRICE"=15 AND "QUANTITY">1)
4 - access("P"."PRODUCT_ID"="O"."PRODUCT_ID")
18 rows selected.
SQL>
3.
4.
What do you observe?
The plan is using a simple NESTED LOOP join.
Now, execute the same query:
SQL> select /*+ monitor*/ product_name
from
order_items o, product_information p
Chapter 15 - Page 4
a
and
quantity > 1
and
p.product_id = o.product_id;
2
3
4
5
PRODUCT_NAME
-------------------------------------------------Screws <B.28.S>
Screws <B.28.S>
Screws <B.28.S>
Screws <B.28.S>
…
Screws <B.28.S>
Screws <B.28.S>
13 rows selected.
s
) ha
SQL>
om ฺ
c
ฺ
ch ide
SQL> select * from table(dbms_xplan.display_cursor());
e
t
i
l- t Gu
a
b
lo den
g
@ Stu
o
f
(in this
y
og use
l
o
hn se to
c
e
T cen
n
o
li
ti
e
a
l
rm erab
o
f
In ansf
l
a
b
tr
Glo non5.
Show the resulting execution plan:
PLAN_TABLE_OUTPUT
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------SQL_ID
439uv1rqa5svb, child number 1
-------------------------------------
select /*+ monitor*/ product_name from order_items o,
product_information p where o.unit_price = 15
and quantity > 1
and
p.product_id = o.product_id
Plan hash value: 1553478007
----------------------------------------------------------------------------------------| Id
|
| Operation
| Name
| Rows
| Bytes | Cost (%CPU)| Time
-----------------------------------------------------------------------------------------
|
|
|
|
|
|
|*
|
1 |
|
|
13 |
416 |
8
(0)| 00:00:01
|*
|
2 |
TABLE ACCESS FULL| ORDER_ITEMS
|
13 |
156 |
3
(0)| 00:00:01
|
|
3 |
TABLE ACCESS FULL| PRODUCT_INFORMATION |
288 |
5760 |
5
(0)| 00:00:01
HASH JOIN
8 (100)|
-----------------------------------------------------------------------------------------
Chapter 15 - Page 5
a
Predicate Information (identified by operation id):
--------------------------------------------------1 - access("P"."PRODUCT_ID"="O"."PRODUCT_ID")
2 - filter(("O"."UNIT_PRICE"=15 AND "QUANTITY">1))
Note
----- cardinality feedback used for this statement
27 rows selected.
SQL>
6.
What do you observe and conclude?
The actual plan used at execution was a HASH_JOIN.
Why did the plan change?
The plan changed because the optimizer realized during the execution that the number of
rows actually returned from the order_items table was much larger than expected.
Multiple single-column predicates on the order_items table caused the initial cardinality
estimate to be incorrect. The misestimation can't be corrected by extended statistics
because one of the predicates is a non-equality predicate.
How would you confirm the plan change was caused by dynamic plans?
By looking in V$SQL and checking the value of the new column
IS_RESOLVED_ADAPTIVE_PLAN.
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
7.
l- t Gu
a
b
lo den
g
@ Stu
SQL> column sql_text format a30 info
is
(
h
t
y
SQL> select sql_id, sql_text,
is_resolved_adaptive_plan
og use
l
o
from
v$sql
n e to
hlike
c
where sql_text
e
s'select /*+ monitor*/ product_name%';
n
T
e
n
2
3
tio le lic
a
b
rm eraSQL_TEXT
SQL_ID
I
o
f
f
n
I
s
-----------------------------------------l
n
a
a
r
b
t
select /*+ monitor*/ product_n Y
Glo n439uv1rqa5svb
oname from order_items o, produc
t_information p where o.unit_p
rice = 15
and quantity > 1
and p.product_id = o.product_
id
SQL>
8.
The information learnt via dynamic plans is persisted as a SQL directive. Check the SQL
directives created for the previous execution.
SQL> connect /
Connected.
SQL> set pages
SQL> set lines
SQL> col state
as sysdba
9999
300
format a5
Chapter 15 - Page 6
a
SQL>
SQL>
SQL>
SQL>
col subobject_name format a11
col col_name format a11
col object_name format a13
select d.directive_id, o.object_type, o.object_name,
o.subobject_name col_name, d.type, d.state, d.reason
from
dba_sql_plan_directives d, dba_sql_plan_dir_objects
o
where d.DIRECTIVE_ID=o.DIRECTIVE_ID
and
o.object_name in ('ORDER_ITEMS')
order by d.directive_id;
no rows selected
SQL> /
no rows selected
s
) ha
om ฺ
c
ฺ
SQL>
ch ide
e
t
i
9. -- You have to wait for a while before it is persisted. MMON is
responsible
l- t Gufor the
a
b
flush.
lo denflush has been
g
-- In Database 12c DML monitoring and column_usage
information
@ Stu
o
f
transferred to MMON instead of SMON.
(in this o.object_name,
y
SQL> select d.directive_id, go.object_type,
se d.type, d.state, d.reason
o col_name,
l
u
o
o.subobject_name
hn se to d, dba_sql_plan_dir_objects
c
from
dba_sql_plan_directives
e
T cen
o
n
o
li
tid.DIRECTIVE_ID=o.DIRECTIVE_ID
e
a
where
l
b
rm o.object_name
a
r
o
and
in
f
e
f
n
I
s
al('ORDER_ITEMS','PRODUCT_INFORMATION')
an
r
b
t
o
order
by d.directive_id;
Gl non
DIRECTIVE_ID OBJECT OBJECT_NAME
COL_NAME
TYPE
STATE
REASON
------------ ------ ------------- ----------- ---------------- ------------------ -----------------------------------1.3208E+19 COLUMN ORDER_ITEMS
UNIT_PRICE DYNAMIC_SAMPLING
MISSING STATS
SINGLE TABLE CARDINALITY MISESTIMATE
1.3208E+19 TABLE ORDER_ITEMS
DYNAMIC_SAMPLING
MISSING STATS
1.3208E+19 COLUMN ORDER_ITEMS
QUANTITY
DYNAMIC_SAMPLING
MISSING STATS
SQL>
Chapter 15 - Page 7
a
Practice 15-2: Using Re-optimization
Overview
In this practice, you discover how the re-optimization (Cardinality Feedback) part of the Adaptive
Execution Plans feature in Oracle Database 12c works.
Tasks
1.
Unlock the SH account in ORCL database and then grant SELECT ANYDICTONARY privilege
to SH.
SQL> grant select any dictionary to sh;
Grant succeeded.
SQL> alter user sh identified by oracle_4U account unlock;
s
) ha
User altered.
om ฺ
c
ฺ
ch ide
e
t
i
uto display
2. Execute the following query. Note the gather_plan_statistics
l- hint ist used
G
a
b
the actual number of rows returned from each operation in the
plan.
This
will
allow
you to
lo returned.
en
d
compare the optimizer’s estimates with the actual numbergof rowsu
t
o@ i*/
Sc.cust_first_name,
f
select /*+ gather_plan_statistics
HINT1
n
s
i
(
th
c.cust_last_name, sum(s.amount_sold)
y
g
e
from customers c, salesolso
us
n
o
t
where c.cust_id=s.cust_id
ech enAngeles'
se
and
c.cust_city='Los
T
n
and
c.cust_state_province='CA'
o
lic
i
t
e
a
l
and
c.country_id=52790
b
rms.time_id='09-NOV-00'
a
r
and
o
f
e
In by
sf
group
c.cust_first_name,
c.cust_last_name;
l
n
a
a
r
b
t
n- connect sh/oracle_4U
Glo nSQL>
o
Connected.
SQL>
SQL>
SQL>
SQL>
SQL>
set pages 9999
set lines 300
COL sql_text format a30
select /*+ gather_plan_statistics HINT1 */
c.cust_first_name, c.cust_last_name,
sum(s.amount_sold)
from customers c, sales s
and
c.cust_city='Los Angeles'
and
and
c.country_id=52790
and
s.time_id='09-NOV-00'
Chapter 15 - Page 8
a
group by c.cust_first_name, c.cust_last_name;
no rows selected
SQL>
3.
Display the associated execution plan. What do you observe?
There is a large difference between the estimated (E-Rows) and the actual number of rows
returned (A-Rows). This statement looks like a candidate for re-optimization.
SQL> select * from
table(dbms_xplan.display_cursor(FORMAT=>'ALLSTATS LAST'));
PLAN_TABLE_OUTPUT
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------SQL_ID
1s4x3nv00bub2, child number 0
------------------------------------select /*+ gather_plan_statistics HINT1 */ c.cust_first_name, c.cust_last_name,
sum(s.amount_sold) from
and
c.country_id=52790 and
s
) ha
customers c, sales s where c.cust_id=s.cust_id
c.cust_city='Los Angeles' and
c.cust_state_province='CA' and
s.time_id='09-NOV-00' group by
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
b
lo den
g
@ Stu
o
f
(in this
y
og use
l
o
hn se to
c
e
T cen
n
o
li
ti
e
a
l
rm erab
o
f
In ansf
l
a
b
tr
Glo nonc.cust_first_name, c.cust_last_name
------------------------------------------------------------------------------------------------------------------------------------------------------------| Id | Operation
1Mem | Used-Mem |
| Name
| Starts | E-Rows | A-Rows |
A-Time
| Buffers | Reads
|
OMem |
------------------------------------------------------------------------------------------------------------------------------------------------------------|
|
|
|
1 |
909K|
|
|
2 |
|*
|
3 |
|
|
4 |
HASH GROUP BY
|
MERGE JOIN
|
TABLE ACCESS BY INDEX ROWID
|
INDEX FULL SCAN
|
|
1 |
|
0 |00:00:00.33 |
35069 |
1282 |
|
|
|
1 |
1 |
0 |00:00:00.33 |
35069 |
1282 |
909K|
|
|
1 |
1 |
0 |00:00:00.33 |
35069 |
1282 |
|
| CUSTOMERS
|
1 |
1 |
482 |00:00:00.07 |
34981 |
1198 |
|
|
| CUSTOMERS_PK
|
1 |
55500 |
35610 |00:00:00.05 |
74 |
70 |
|* 5 |
SORT JOIN
95232 |83968 (0)|
|
|
482 |
2152 |
0 |00:00:00.22 |
88 |
84 | 95232 |
|
|
6 |
|
|
1 |
2152 |
2152 |00:00:00.12 |
88 |
84 |
|
|
|
7 |
|
1 |
2152 |
2152 |00:00:00.11 |
88 |
84 |
|
|
|
8 |
|
1 |
|
2152 |00:00:00.09 |
2 |
2 |
|
|*
|
9 |
| SALES_TIME_BIX |
1 |
|
1 |00:00:00.02 |
2 |
2 |
|
|
PARTITION RANGE SINGLE
|
TABLE ACCESS BY LOCAL INDEX ROWID BATCHED| SALES
|
BITMAP CONVERSION TO ROWIDS
|
|
BITMAP INDEX SINGLE VALUE
|
-------------------------------------------------------------------------------------------------------------------------------------------------------------
Predicate Information (identified by operation id):
---------------------------------------------------
3 - filter(("C"."CUST_CITY"='Los Angeles' AND "C"."CUST_STATE_PROVINCE"='CA' AND "C"."COUNTRY_ID"=52790))
5 - access("C"."CUST_ID"="S"."CUST_ID")
filter("C"."CUST_ID"="S"."CUST_ID")
9 - access("S"."TIME_ID"='09-NOV-00')
33 rows selected.
SQL>
Chapter 15 - Page 9
a
4.
How would you confirm this statement will be re-optimized?
You can confirm that by checking the value of the is_reoptimizable column in v$sql.
This column indicates that this statement will be re-parsed on the next execution and
information learnt on the first execution about the actual number of rows returned will be
used to generate a better plan.
SQL> select sql_id, child_number, sql_text, is_reoptimizable
from
v$sql
where sql_text like '%+ gather_plan_statistics HINT1%';
2
3
SQL_ID
CHILD_NUMBER SQL_TEXT
I
------------- ------------ ------------------------------ 6wdhzmv5882s2
0 select sql_id, child_number, s N
ql_text, is_reoptimizable from
v$sql where sql_text like
'%gather_plan_statistics HINT1
%'
s
) ha
om ฺ
c
ฺ
ch ideY
e
c81f6n14144kd
0 select /*+ gather_plan_statisti
t
i
l- t Gu
a
cs HINT1 */ c.cust_first_name,
b
lo sum(s.amount
en
g
d
c.cust_last_name,
u
t
o@
Scustomers
f
_sold)
from
c, s
n
s
i
i
(
h
t
y s se where c.cust_id=s.cu
ogales
l
u and c.cust_city='L
o
st_id
n
o
t
h
ec enseos Angeles' and c.cust_s
T
n
tate_province='CA'
and c
o
lic
i
t
e
a
l
.country_id=52790
and
s.
b
m
r
a
r
o
time_id='09-NOV-00'
group b
nf nsfe
I
l
y c.cust_first_name, c.cust_la
ba n-tra
o
l
st_name
G no
SQL>
5.
Confirm your guess is correct:
SQL> select /*+ gather_plan_statistics HINT1 */
c.cust_first_name, c.cust_last_name,
sum(s.amount_sold)
from customers c, sales s
and
c.cust_city='Los Angeles'
and
and
c.country_id=52790
and
s.time_id='09-NOV-00'
group by c.cust_first_name, c.cust_last_name;
a
no rows selected
SQL> select * from
table(dbms_xplan.display_cursor(FORMAT=>'ALLSTATS LAST'));
PLAN_TABLE_OUTPUT
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------SQL_ID
1s4x3nv00bub2, child number 1
------------------------------------select /*+ gather_plan_statistics HINT1 */ c.cust_first_name, c.cust_last_name,
sum(s.amount_sold) from
and
customers c, sales s where c.cust_id=s.cust_id
c.cust_city='Los Angeles' and
c.country_id=52790 and
c.cust_state_province='CA' and
s.time_id='09-NOV-00' group by
c.cust_first_name, c.cust_last_name
s
) ha
---------------------------------------------------------------------------------------------------------------------------------------------------| Id | Operation
Buffers | OMem |
| Name
| Starts | E-Rows | A-Rows |
A-Time
|
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
b
lo den
g
@ Stu
o
f
(in this
y
og use
l
o
hn se to
c
e
T cen
n
o
li
ti
e
a
l
rm erab
o
f
In ansf
l
a
b
tr
Glo non1Mem | Used-Mem |
---------------------------------------------------------------------------------------------------------------------------------------------------|
35065 |
|
|
|
|
1 |
35065 |
|
|
2 |
35065 |
HASH GROUP BY
909K|
909K|
MERGE JOIN
|
|
TABLE ACCESS BY INDEX ROWID
|
|
|
|
4 |
74 |
|
INDEX FULL SCAN
|
|
6 |
84 |
|
|
7 |
84 |
|
|
1 |
|
0 |00:00:00.04 |
|
|
1 |
1 |
0 |00:00:00.04 |
|
|
1 |
767 |
0 |00:00:00.04 |
| CUSTOMERS
|
1 |
482 |
482 |00:00:00.06 |
| CUSTOMERS_PK
|
1 |
35610 |
35610 |00:00:00.04 |
|
|
482 |
2152 |
0 |00:00:00.01 |
|
|
1 |
2152 |
2152 |00:00:00.01 |
|
1 |
2152 |
2152 |00:00:00.01 |
|
1 |
|
2152 |00:00:00.01 |
| SALES_TIME_BIX |
1 |
|
1 |00:00:00.01 |
|
|* 3 |
34981 |
|* 5 |
SORT JOIN
84 | 99328 | 99328 |88064
|
|
(0)|
|
|
TABLE ACCESS BY LOCAL INDEX ROWID BATCHED| SALES
|
|
|
8 |
2 |
|
BITMAP CONVERSION TO ROWIDS
|
|
|* 9 |
2 |
|
BITMAP INDEX SINGLE VALUE
|
|
|
---------------------------------------------------------------------------------------------------------------------------------------------------Predicate Information (identified by operation id):
--------------------------------------------------3 - filter(("C"."CUST_CITY"='Los Angeles' AND "C"."CUST_STATE_PROVINCE"='CA' AND "C"."COUNTRY_ID"=52790))
5 - access("C"."CUST_ID"="S"."CUST_ID")
filter("C"."CUST_ID"="S"."CUST_ID")
9 - access("S"."TIME_ID"='09-NOV-00')
Note
----- cardinality feedback used for this statement
37 rows selected.
SQL>
a
6.
Check that a new child cursor was created:
SQL> select sql_id, child_number, sql_text, is_reoptimizable
from
v$sql
where sql_text like '%gather_plan_statistics HINT1%';
2
3
SQL_ID
CHILD_NUMBER SQL_TEXT
I
------------- ------------ ------------------------------ 6wdhzmv5882s2
%'
c81f6n14144kd
s
) ha
0 select /*+ gather_plan_statisti N
c.cust_last_name, sum(s.amount
_sold)
from customers c, s
ales s
where c.cust_id=s.cu
st_id
and
c.cust_city='L
os Angeles' and c.cust_s
tate_province='CA'
and c
.country_id=52790
and
s.
time_id='09-NOV-00'
group b
st_name
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
b
lo den
g
@ Stu
o
f
(in this
y
og use
l
o
hn se to
c
e
T cen
n
o
li
ti
e
a
l
rm erab
o
f
In ansf
l
c81f6n14144kd
1 select /*+ gather_plan_statisti Y
a
r
b
t
o
Gl non
c.cust_last_name, sum(s.amount
_sold)
from customers c, s
ales s
where c.cust_id=s.cu
st_id
and
c.cust_city='L
os Angeles' and c.cust_s
tate_province='CA'
and c
.country_id=52790
and
s.
time_id='09-NOV-00'
group b
st_name
987h8zk1zax24
a
%'
SQL>
SQL>
select CHILD_NUMBER, USE_FEEDBACK_STATS
from
v$sql_shared_cursor where SQL_ID='c81f6n14144kd';
CHILD_NUMBER
-----------0
1
USE_FEEDBACK_STATS
-----------------------------N
Y
s
) ha
SQL>
7.
Force the SQL plan directive to be flushed and check to see it was persisted into the data
dictionary:
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
Connected.
b
lo den
SQL> col state format a5
g
@ Stu
o
SQL> col subobject_name format a11
f
in this
SQL> col col_name format a11 y (
oga13 use
l
SQL> col object_name format
o
hna23se to
c
SQL> col dir_id format
e
n
T
e
SQL> col ownernformatica5
o
l
ti format
a
SQL> col state
le A20
b
m
r
a
fo sfer
n
I
alSQL>-tset
anecho on
r
b
o
Gl nSQL>
on
SQL> exec dbms_spd.flush_sql_plan_directive
SQL> select to_char(d.directive_id) dir_id, o.owner,
o.object_name, o.subobject_name col_name,
o.object_type,
d.type, d.state, d.reason
from
dba_sql_plan_directives d, dba_sql_plan_dir_objects
o
where d.DIRECTIVE_ID=o.DIRECTIVE_ID
and
o.owner in ('SH')
order by 1,2,3,4,5;
a
DIR_ID
OWNER OBJECT_NAME
COL_NAME
OBJECT
TYPE
STATE
REASON
----------------------- ----- ------------- ----------- ------ --------------- ------------ -------------------------------11713533193494921230
SH
CUSTOMERS
TABLE
DYNAMIC_SAMPLING NEW JOIN CARDINALITY MISESTIMATE
11713533193494921230
SH
SALES
TABLE
DYNAMIC_SAMPLING NEW JOIN CARDINALITY MISESTIMATE
SQL> EXIT
$
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
b
lo den
g
@ Stu
o
f
(in this
y
og use
l
o
hn se to
c
e
T cen
n
o
li
ti
e
a
l
rm erab
o
f
In ansf
l
a
b
tr
Glo non-
a
s
) ha
om ฺ
c
ฺ
ch16: ide
e
t
i
u
l- t Gand
Emergency Monitoring
a
b
lo dADDM
en
g
Compare
Period
u
o@ is St
f
n
i
Chapter
( 16 th
y
g
se
o
l
u
o
hn se to
c
e
T cen
n
o
li
ti
e
a
l
rm erab
o
f
In ansf
l
a
b
tr
Glo non-
Practices for Lesson 16: Emergency Monitoring and Compare Period ADDM
Chapter 16 - Page 1
a
Practices Overview
In these practices, you will use Emergency Monitoring to troubleshoot a hanging situation
discovered in orcl database instance.
Then you can optionally run the Compare Period ADDM demonstration to know how to use this
new feature.
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
b
lo den
g
@ Stu
o
f
(in this
y
og use
l
o
hn se to
c
e
T cen
n
o
li
ti
e
a
l
rm erab
o
f
In ansf
l
a
b
tr
Glo non-
Chapter 16 - Page 2
a
Practice 16-1: Using Emergency Monitoring
Assumption
You are managing the target orcl database and are already connected to Enterprise Manager
Cloud Control in the target orcl database. Make sure you restart Enterprise Manager Cloud
Control (you stopped it in Practice 9-1 to enable Unified Auditing).
1. Restart the Enterprise Manager Repository Database em12rep.
$ . oraenv
The Oracle base for
/u01/app/oracle
SQL> startup
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
Fixed Size
2271568 bytes
b
lo den
Variable Size
339740336 bytes g
o@ is Stu
f
Database Buffers
50331648in
bytes
( bytesth
y
Redo Buffers
8503296
g
se
o
l
u
o
Database mounted.
hn se to
Database opened. ec
T cen
n
SQL> EXIT
o
li
ti
e
a
l
$
rm erab
o
f
2. RestartIn
the OMS.sf
l
a
anOMS_HOME=/u01/app/oracle/product/middleware/oms
r
b
$ export
t
o
n
Gl n$o$OMS_HOME/bin/emctl
start oms
reserved.
Starting WebTier...
heavy usage.
least 4096.
Chapter 16 - Page 3
a
$
3.
Use https://localhost:7802/em to get the Enterprise Manager Cloud Control
Console appear, enter sysman in the User Name field and Oracle123 in the Password
field. Then click Login.
The status of the orcl database agent might be in unreachable state because the oms
was stopped in practice 9. However this has no incidence on other practices.
Overview
In this practice you will troubleshoot a hanging situation after users told you they could not
connect to the orcl instance anymore.
You can use Emergency Monitoring only from Enterprise Manager Cloud Control.
Tasks
1.
Make sure you are already connected to Enterprise Manager Cloud Control in the target
orcl database with SYSDBA credentials.
a.
b.
Connect to Enterprise Manager Cloud Control as sysman with Oracle123 password.
After being connected, click “Targets” and then “Databases”.
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
b
lo den
g
@ Stu
o
f
(in this
y
og use
l
o
hn se to
c
e
T cen
n
o
li
ti
e
a
l
rm erab
o
f
In ansf
l
a
b
tr
Glo nonc.
2.
From the right pane, click the orcl database instance. You are still not connected to
orcl.
d. Therefore, go to any of the menus and try to execute any DBA operation, “Create a
tablespace” or “Create a new user” for example.
e. Because you created a named credential in Practice 1-3, the named credential is
proposed to make a connection as SYSDBA to the instance. You can use it or create a
new credential to log in. Log in.
In a terminal window, make sure you are at the ~/labs/Emergency directory and your
environment points to the orcl instance.
$ cd ~/labs/Emergency
$ . oraenv
Chapter 16 - Page 4
a
$
3.
Execute the Emergency_setup.sh shell script.
$ ./Emergency_setup.sh
DROP TRIGGER trig_after_logon
*
ERROR at line 1:
ORA-04080: trigger 'TRIG_AFTER_LOGON' does not exist
Leave the Emergency_setup.sh shell script pending.
4.
Meanwhile you create a new user. From another terminal window, connect to the orcl
database as SYSTEM with oracle_4U password.
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
b
lo den
Copyright (c) 1982, 2012, Oracle. All g
rights ureserved.
o@ is St
f
n
i
(
th
y
g
e
lo o us
o
But the session is pending.
n
h stoethet orcl database AS SYSDBA with oracle_4U
c
e
5. From another terminal window,
connect
T cen
n
password.
o
li
i
t
e
a
l
$ sqlplus
b
rm / eASraSYSDBA
o
f
In ansf
l
a
SQL*Plus:
b n-tr Release 12.1.0.0.2 Production on Thu Sep 6 15:41:45
o
l
G n2012
o
SQL*Plus: Release 12.1.0.0.2 Production on Thu Sep 6 15:41:45
2012
But the session is pending.
Chapter 16 - Page 5
a
6.
You will use Emergency Monitoring to quickly solve the hanging situation. Click
Performance from the menu, then Emergency Monitoring from the list of options.
has
In DB Host Credentials, choose New and enter oracle for both the UserName and the
)
Password. Then click Submit.
om ฺ
c
ฺ
7. The Hanging Analysis page is displayed. It shows the blockers and blocked
To
chsessions.
e
ideAnd
t
i
u
release the blocked sessions, kill the blocking session. Click the Killl-SessionG
button.
bathatethentsession has
click YES to approve the operation. A message appears to inform
o
l
g tud
been killed. Click OK.
@
o
nf this S
i
(
ogy use
l
o
hn se to
c
e
T cen
n
o
li
ti
e
a
l
rm erab
o
f
In ansf
l
a
b
tr
Glo non-
Chapter 16 - Page 6
a
8.
Check that the sessions that were hanging are now released.
2012
SQL> exit
$
From the other terminal window, the connection is also released.
2012
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
SQL> exit
l- t Gu
a
b
$
lo den
g
@ Stu
o
f
(in this
y
og use
l
o
hn se to
c
e
T cen
n
o
li
ti
e
a
l
rm erab
o
f
In ansf
l
a
b
tr
Glo nonCopyright (c) 1982, 2012, Oracle.
Chapter 16 - Page 7
a
Practice 16-2: Cleaning Up
Overview
In this practice you clean up the environment of the orcl database.
Tasks
1.
From the session where you launched the Emergency_setup.sh shell script, clean up
the orcl database. If the Emergency_setup.sh shell script does not end up (because of
the 1800 seconds sleep), interrupt it with a CTRL C.
$ ./Emergency_setup.sh
DROP TRIGGER trig_after_logon
*
ERROR at line 1:
ORA-04080: trigger 'TRIG_AFTER_LOGON' does not exist
s
) ha
CTRL C
$
m
o
c
ฺ
2. From one of the released SQL*Plus session, drop the trigger.
ch ideฺ
e
t
i
SQL> ALTER SYSTEM SET "_system_trig_enabled"=FALSE;
l- t Gu
a
b
lo den
g
System altered.
@ Stu
o
f
(in this
y
SQL> DROP TRIGGER trig_after_logon;
og use
l
o
hn se to
c
e
Trigger dropped.T
n
e
n
c
i
o
l
ti
a
le
b
m
SQL> r
a
fo sfer
n
I
3. Shut
down
orcl
l the
n instance to release resources for the next practices.
a
a
r
b
t
SQL>
IMMEDIATE
Glo nDatabase
on- SHUTDOWN
closed.
SQL> EXIT
$
Chapter 16 - Page 8
a
Practice 16-3: Using Compare Period ADDM (optional)
Overview
In this demonstration, you will see how to use the Compare Period ADDM with Enterprise
Manager Cloud Control. You discover that during the current period of time, the performance is
decreasing. You need to understand why the performance changed, and the root causes of this
change, so as to perform appropriate actions to solve the issue.
In this practice, you use a browser to execute the Compare Period ADDM demonstration.
Tasks
1.
Launch a browser and enter in the
file:////home/oracle/demos/Compare_Period_ADDM/Compare_Period_ADDM.html
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
b
lo den
g
@ Stu
o
f
(in this
y
og use
l
o
hn se to
c
e
T cen
n
o
li
ti
e
a
l
rm erab
o
f
In ansf
l
a
b
tr
Glo non-
Chapter 16 - Page 9
a
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
b
lo den
g
@ Stu
o
f
(in this
y
og use
l
o
hn se to
c
e
T cen
n
o
li
ti
e
a
l
rm erab
o
f
In ansf
l
a
b
tr
Glo non-
a
s
) ha
om ฺ
c
ฺ
ch17: ide
e
t
i
uOther
l- and
Resource Manager
G
a
t
b
lo Enhancements
en
g
Performance
d
u
o@ is St
f
n
i
Chapter
( 17 th
y
g
se
o
l
u
o
hn se to
c
e
T cen
n
o
li
ti
e
a
l
rm erab
o
f
In ansf
l
a
b
tr
Glo non-
Practices for Lesson 17: Resource Manager and Other Performance Enhancements
Chapter 17 - Page 1
a
Practices Overview
In this practice, you create two CDB Resource Manager plans and associated directives to limit
CPU resources used by two PDBs.
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
b
lo den
g
@ Stu
o
f
(in this
y
og use
l
o
hn se to
c
e
T cen
n
o
li
ti
e
a
l
rm erab
o
f
In ansf
l
a
b
tr
Glo non-
Chapter 17 - Page 2
a
Practice 17-1: Using CDB Resource Manager Plans and Directives
Overview
In this practice, you create two CDB Resource Manager plans and associated directives to limit
CPU resources used by two PDBs.
Tasks
1.
Connect to the root of cdb2 as SYSDBA and cleanup your environment by executing the
rsrc_cleanup.sql script. The script will close all PDBs except PDB1_1 and PDB2_2.
a.
Make sure you are in the ~/labs/RM directory and your environment points to the
cdb2 instance.
$ cd ~/labs/RM
$ . oraenv
$
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
b
lo den
g
@ Stu
o
f
(in this
y
SQL> STARTUP
og use
l
o
hn se to
c
e
T cen
n
o
li
ti
e
a
l
rm erab
o
f
In ansf
l
a
b
tr
Glo nonb.
Execute the rsrc_cleanup.sql script.
1) Start up the multitenant container database instance if not already done.
Chapter 17 - Page 3
a
Fixed Size
2274024 bytes
Variable Size
1090522392 bytes
Database Buffers
1342177280 bytes
Redo Buffers
20254720 bytes
Database mounted.
Database opened.
SQL> @rsrc_cleanup.sql
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
b
lo den
NAME
CON_ID OPEN_MODE
g
tu
@ --------------------------------------- ---------o
S
f
is
(2inREADthONLY
PDB$SEED
y
se WRITE
og 6uREAD
l
PDB1_1
o
hn se to 3 MOUNTED
PDB2
c
e
T cen
PDB2_2
4 READ WRITE
n
i
o
l
i
t
PDB_ORCL2 a
5 MOUNTED
le
b
m
r
a
fo sfer
n
I
al -tran
b
o
Gl nSystem
on altered.
NAME
-------------------------------ORA$INTERNAL_CDB_PLAN
System altered.
Chapter 17 - Page 4
a
BEGIN
DBMS_Resource_Manager.Delete_CDB_Plan_Directive('fairplan',
'pdb1_1'); END;
*
ERROR at line 1:
ORA-29358: resource plan FAIRPLAN does not exist
ORA-06512: at "SYS.DBMS_RMIN_SYS", line 3168
ORA-06512: at "SYS.DBMS_RESOURCE_MANAGER", line 1605
BEGIN
DBMS_Resource_Manager.Delete_CDB_Plan_Directive('fairplan',
'pdb2_2'); END;
s
) ha
om ฺ
c
ฺ
ch ide
*
e
t
i
l- t Gu
ERROR at line 1:
a
b
lo existden
ORA-29358: resource plan FAIRPLAN does g
not
@ 3168Stu
ORA-06512: at "SYS.DBMS_RMIN_SYS",fo
line
(in this line 1605
ORA-06512: at "SYS.DBMS_RESOURCE_MANAGER",
y
og use
l
o
hn se to
c
e
T cen
n
o
li
ti
e
BEGIN DBMS_Resource_Manager.Delete_CDB_Plan('fairplan');
END;
a
l
b
m
r
a
fo sfer
n
I
al* -tran
b
o
n at line 1:
Gl nERROR
o
ORA-29358: resource plan FAIRPLAN does not exist
BEGIN
DBMS_Resource_Manager.Delete_CDB_Plan_Directive('unfairplan',
'pdb1_1'); END;
*
ERROR at line 1:
ORA-29358: resource plan UNFAIRPLAN does not exist
Chapter 17 - Page 5
a
BEGIN
DBMS_Resource_Manager.Delete_CDB_Plan_Directive('unfairplan',
'pdb2_2'); END;
*
ERROR at line 1:
ORA-29358: resource plan UNFAIRPLAN does not exist
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
*
b
lo den
g
ERROR at line 1:
@ Stu
o
f
ORA-29358: resource plan UNFAIRPLAN
does
n thisnot exist
i
(
ORA-06512: at "SYS.DBMS_RMIN_SYS",
gy usline
e 2863
o
l
o
ORA-06512: at "SYS.DBMS_RESOURCE_MANAGER",
line 1451
n e to
h
c
ORA-06512: at line
Te1 cens
n
tio le li
a
rm erab
o
f
In ansf
l
a
PL/SQL
b n-tr procedure successfully completed.
o
l
G no
BEGIN DBMS_Resource_Manager.Delete_CDB_Plan('unfairplan'); END;
SQL> exit
$
Chapter 17 - Page 6
a
2.
Open a terminal window (it will be referred to as window1) to connect to pdb1_1 in cdb2
and create a PL/SQL procedure that burns CPU in PDB1_1 as the SYSTEM user. You can
use the create_burn_cpu.sql script to create the procedure after connecting to
PDB1_1.
$ cd ~/labs/RM
$ . oraenv
$
$ sqlplus system/oracle_4U@localhost/pdb1_1
Connected to:
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
Procedure created.
b
lo den
g
@ Stu
o
SQL>
f
is
(in to asthwindow2)
y
3. Open a second terminal window (it will begreferred
connect to pdb2_2 in
se in PDB2_2 asto the
o burnsuCPU
l
cdb2 and create a PL/SQL procedure
that
SYSTEM user. You
o
n
o
t
h
can use the create_burn_cpu.sql
ec enscript
se to create the procedure after connecting to
T
PDB2_2.
n
o
lic
i
t
e
$ cd ~/labs/RM
a
l
rm erab
o
$ . foraenv
In ansf= [cdb1] ? cdb2
l
ORACLE_SID
a
b n-Oracle
tr
base remains unchanged with value /u01/app/oracle
Glo nThe
o
$
SQL> @create_burn_cpu.sql
$ sqlplus system/oracle_4U@localhost/pdb2_2
Connected to:
SQL> @create_burn_cpu.sql
Procedure created.
Chapter 17 - Page 7
a
SQL>
4.
From window1, create two new CDB plans called FAIRPLAN and UNFAIRPLAN.
FAIRPLAN should give one share to both PDB1_1 and PDB2_2, and UNFAIRPLAN should
give one share to PDB1_1 and five shares to PDB2_2.
SQL> alter session set container = CDB$Root;
Session altered.
SQL> EXEC DBMS_Resource_Manager.Clear_Pending_Area();
SQL> EXEC DBMS_Resource_Manager.Create_Pending_Area();
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
b
PL/SQL procedure successfully completed. lo
en
g
d
u
o@ is St
f
n
i
SQL> EXEC
(
th
y
DBMS_Resource_Manager.Create_CDB_Plan_Directive('fairplan',
g
e
lo o us
o
'pdb1_1', shares => 1);
n
h se t
c
e
n completed.
Tsuccessfully
e
n
PL/SQL procedure
c
i
o
l
ti
a
le
b
m
r
a
foEXEC sfer
SQL>
n
I
alDBMS_Resource_Manager.Create_CDB_Plan_Directive('fairplan',
an shares => 1);
r
b
t
o
'pdb2_2',
Gl non
SQL> EXEC DBMS_Resource_Manager.Create_CDB_Plan('fairplan', 'One
share each');
SQL> EXEC DBMS_Resource_Manager.Create_CDB_Plan('unfairplan',
'one share to pdb1_1 and five to pdb2_2');
SQL> EXEC
DBMS_Resource_Manager.Create_CDB_Plan_Directive('unfairplan',
'pdb1_1', shares => 1);
Chapter 17 - Page 8
a
SQL> EXEC
DBMS_Resource_Manager.Create_CDB_Plan_Directive('unfairplan',
'pdb2_2', shares => 5);
SQL> EXEC DBMS_Resource_Manager.Validate_Pending_Area();
SQL> EXEC DBMS_Resource_Manager.Submit_Pending_Area();
SQL>
5.
s
) ha
Still from window1, make sure both plans and associated directives were created correctly.
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
b
lo den
g
@ Stu
o
f
(in this
y
og use
l
o
hn se to
c
e
T cen
n
o
li
SQL> selecttiPlan, Pluggable_Database,
Shares
e
a
l
b
m
from
CDB_CDB_Rsrc_Plan_Directives
r
ra
o
f
e
f
n
l I where
ns Con_ID = 1
a
a
r
b
t
and
Plan in ('FAIRPLAN', 'UNFAIRPLAN')
Glo non- and Pluggable_Database in ('PDB1_1', 'PDB2_2')
SQL> SELECT Plan from CDB_CDB_Rsrc_Plans
WHERE Con_ID = 1 AND Plan IN ('FAIRPLAN', 'UNFAIRPLAN')
ORDER BY 1;
2
3
PLAN
--------------------------------------------------------------FAIRPLAN
UNFAIRPLAN
order by 1, 2;
3
4
5
2
6
PLAN
------------------------------------------------------------------------------PLUGGABLE_DATABASE
------------------------------------------------------------------------------SHARES
---------FAIRPLAN
PDB1_1
1
Chapter 17 - Page 9
a
FAIRPLAN
PDB2_2
1
UNFAIRPLAN
PDB1_1
1
UNFAIRPLAN
PDB2_2
s
) ha
5
om ฺ
c
ฺ
SQL>
ch ide
e
t
i
l- t Gu
6. From window1, activate the CDB plan FAIRPLAN.
a
b
lo den
g
@ Stu
o
Connected.
f
(in this = fairplan;
SQL> alter system set resource_manager_plan
y
og use
l
o
hn se to
c
System altered.
e
T cen
n
o
li v$Rsrc_Plan where Con_ID = 1;
tiName from
e
a
SQL> select
l
rm erab
o
f
In
sf
l
NAME ran
a
b n-t
Glo n-------------------------------o
FAIRPLAN
SQL>
7.
From window1, connect as the SYSTEM user in PDB1_1 and set SERVEROUPUT variable to
ON.
SQL> CONNECT System/oracle_4U@localhost/pdb1_1
Connected.
SQL>
a
8.
From window2, connect as the SYSTEM user in PDB2_2 and set SERVEROUPUT variable to
ON.
Connected.
SQL>
9.
DO NOT WAIT AND GO TO STEP 10 RIGHT AFTER: From window1, execute the CPU
burner procedure you created at step 2.
SQL> EXEC Burn_CPU_For_RM_Demo();
CPU:
139.9 Wall:
882.1 k: 2000000000
SQL>
10. From window2, execute the CPU burner procedure you created at step 3.
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
CPU:
140.9 Wall: 886.7 k: 2000000000
a
b
lo den
g
@ Stu
o
f
(in this
y
og use
l
SQL>
o
hn se to
c
11. What do you observe?
e
nalmost at the same time, and have both consumed
Texecution
e
Both procedures finish n
their
c
i
o
l
ti and wall-clock
almost the same a
CPU
during their execution.
le PDB istime
b
m
r
This is expected
because
each
receiving
one share of CPU.
a
r
o
f
e
f
n
I anconnect
s as user SYS in the root, and change the Resource Manager plan to
12. Froml window1,
a
r
b
t
UNFAIRPLAN.
Glo nSQL>
on- CONNECT / AS SYSDBA
SQL> EXEC Burn_CPU_For_RM_Demo();
Connected.
SQL>
SQL> alter system set resource_manager_plan = unfairplan;
System altered.
SQL> select Name from v$Rsrc_Plan where Con_ID = 1;
NAME
-------------------------------UNFAIRPLAN
SQL>
a
13. DO NOT WAIT AND GO TO STEP 14 RIGHT AFTER: From window1, connect as user
SYSTEM in PDB1_1 and execute the CPU burner procedure you created at step 2.
Connected.
SQL>
SQL>
SQL> execute Burn_CPU_For_RM_Demo();
CPU:
150.5 Wall: 333.9 k: 2000000000
SQL>
14. From window2 execute the CPU burner procedure you created at step 3.
SQL> execute Burn_CPU_For_RM_Demo();
CPU:
154.2 Wall: 205.6 k: 2000000000
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
b
lo den
SQL> EXIT
g
@ Stu
$
o
f
(in this
y
e longer to execute in PDB1_1 than
smuch
og takes
l
Now, execution of the CPU burner procedure
u
o
hn se to
in PDB2_2.
c
e
nassigned five shares while PDB1_1 only one.
This is expected because T
PDB2_2 is
e
n
c
i
o
l
However, the difference
five times slower simply because once the procedure
ti is not
ecycles
a
l
b
executed in PDB2_2,
all
CPU
goes to PDB1_1.
m
r
a
r
o
f
e
In ansf
l
a
b
tr
Glo non-
a
16. Make sure you set the CDB plan back to its default and open PDB2_2.
Connected to:
SQL> alter system set resource_manager_plan = '';
System altered.
SQL> select Name from v$Rsrc_Plan where Con_ID = 1;
NAME
-------------------------------ORA$INTERNAL_CDB_PLAN
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
SQL> alter pluggable database all open; oba
l
en
g
d
u
o@ is St
f
n
i
(
th
y
g
e
lo o us
o
SQL> exit
n
h se t
c
e
$
T cen
n
o
li
ti
e
a
l
rm erab
o
f
In ansf
l
a
b
tr
Glo non-
a
Practice 17-2: Using Multi-Process Multi-Threaded Architecture
Overview
In this practice, you switch cdb2 to use the multi-process multi-threaded architecture.
1.
From a terminal window, connected as the oracle user, list all processes and threads
used to run your cdb2 instance.
$ ps -eLo "pid tid comm args" |grep cdb2
25075 25075 ora_pmon_cdb2
ora_pmon_cdb2
25077 25077 ora_psp0_cdb2
ora_psp0_cdb2
25089 25089 ora_vktm_cdb2
ora_vktm_cdb2
25095 25095 ora_gen0_cdb2
ora_gen0_cdb2
25097 25097 ora_mman_cdb2
ora_mman_cdb2
25101 25101 ora_diag_cdb2
ora_diag_cdb2
25103 25103 ora_ofsd_cdb2
ora_ofsd_cdb2
25105 25105 ora_dbrm_cdb2
ora_dbrm_cdb2
25107 25107 ora_dia0_cdb2
ora_dia0_cdb2
25109 25109 ora_dbw0_cdb2
ora_dbw0_cdb2
25111 25111 ora_lgwr_cdb2
ora_lgwr_cdb2
25113 25113 ora_ckpt_cdb2
ora_ckpt_cdb2
25115 25115 ora_smon_cdb2
ora_smon_cdb2
25117 25117 ora_reco_cdb2
ora_reco_cdb2
25119 25119 ora_lreg_cdb2
ora_lreg_cdb2
25121 25121 ora_mmon_cdb2
ora_mmon_cdb2
25123 25123 ora_mmnl_cdb2
ora_mmnl_cdb2
25125 25125 ora_d000_cdb2
ora_d000_cdb2
25127 25127 ora_s000_cdb2
ora_s000_cdb2
25152 25152 ora_rvwr_cdb2
ora_rvwr_cdb2
25153 25153 oracle_25153_cd oraclecdb2
(DESCRIPTION=(LOCAL=YES)(ADDRESS=(PROTOCOL=beq)))
25156 25156 ora_tmon_cdb2
ora_tmon_cdb2
25158 25158 ora_arc0_cdb2
ora_arc0_cdb2
25160 25160 ora_arc1_cdb2
ora_arc1_cdb2
25162 25162 ora_arc2_cdb2
ora_arc2_cdb2
25164 25164 ora_arc3_cdb2
ora_arc3_cdb2
25166 25166 ora_tt00_cdb2
ora_tt00_cdb2
25169 25169 ora_smco_cdb2
ora_smco_cdb2
25172 25172 ora_fbda_cdb2
ora_fbda_cdb2
25178 25178 ora_w000_cdb2
ora_w000_cdb2
25360 25360 ora_aqpc_cdb2
ora_aqpc_cdb2
25372 25372 ora_p000_cdb2
ora_p000_cdb2
25374 25374 ora_p001_cdb2
ora_p001_cdb2
25376 25376 ora_p002_cdb2
ora_p002_cdb2
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
b
lo den
g
@ Stu
o
f
(in this
y
og use
l
o
hn se to
c
e
T cen
n
o
li
ti
e
a
l
rm erab
o
f
In ansf
l
a
b
tr
Glo non-
a
25378
25415
25417
25419
25487
26061
26612
26822
26824
26871
26880
$
2.
3.
25378
25415
25417
25419
25487
26061
26612
26822
26824
26871
26880
ora_p003_cdb2
ora_qm02_cdb2
ora_q001_cdb2
ora_q002_cdb2
ora_cjq0_cdb2
ora_w001_cdb2
oracle_26612_cd
ora_j000_cdb2
ora_j001_cdb2
ora_j002_cdb2
grep
ora_p003_cdb2
ora_qm02_cdb2
ora_q001_cdb2
ora_q002_cdb2
ora_cjq0_cdb2
ora_w001_cdb2
oraclecdb2 (LOCAL=NO)
ora_j000_cdb2
ora_j001_cdb2
ora_j002_cdb2
grep cdb2
What do you observe?
Each Oracle process is running into a different OS process.
Do the same as in step 1, but using Oracle Database dictionary views.
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
Connected to:
l- t Gu
a
b
lo d12.1.0.0.2
en
g
64bit Production
u
o@Analytics
St and Real
f
n
s
i
i
(
th
Application Testing options gy
e
lo o us
o
n
h se t
c
SQL> set linesize e
300
n
T
n
SQL> set pages
100 lice
o
ti
a
lefor a10
SQL> col
username
b
m
r
a
fo sfer
n
I
alSQL>-tselect
an p.spid, p.stid,p.pname,s.username,s.program
r
b
o
Gl nfrom
on v$process p, v$session s
where s.paddr = p.addr
order by 1;
2
3
4
SPID
STID
PNAME USERNAME
PROGRAM
------------------------ ------------------------ ----- --------- -----------------------------------------------25075
25075
PMON
oracle@YOURSERVER (PMON)
25077
25077
PSP0
oracle@YOURSERVER (PSP0)
25089
25089
VKTM
oracle@YOURSERVER (VKTM)
a
25095
25095
oracle@YOURSERVER (GEN0)
25097
25097
oracle@YOURSERVER (MMAN)
25101
25101
oracle@YOURSERVER (DIAG)
25103
25103
oracle@YOURSERVER (OFSD)
25105
25105
oracle@YOURSERVER (DBRM)
25107
25107
oracle@YOURSERVER (DIA0)
25109
25109
oracle@YOURSERVER (DBW0)
25111
25111
oracle@YOURSERVER (LGWR)
25113
25113
oracle@YOURSERVER (CKPT)
25115
25115
oracle@YOURSERVER (SMON)
25117
25117
oracle@YOURSERVER (RECO)
25119
25119
oracle@YOURSERVER (LREG)
25121
25121
oracle@YOURSERVER (MMON)
25123
25123
oracle@YOURSERVER (MMNL)
25152
25152
oracle@YOURSERVER (RVWR)
25153
25153
sqlplus@YOURSERVER (TNS V1-V3)
25156
25156
oracle@YOURSERVER (TMON)
25158
25158
oracle@YOURSERVER (ARC0)
25160
25160
25162
25162
25164
25164
25166
25166
oracle@YOURSERVER (TT00)
25169
25169
oracle@YOURSERVER (SMCO)
GEN0
MMAN
DIAG
OFSD
DBRM
DIA0
DBW0
LGWR
CKPT
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
RECO
a
b
lo den
g
u
@ StLREG
o
f
(in this
y
MMON
og use
l
o
hn se to
c
MMNL
e
T cen
n
tio le li
RVWR
a
b
m
r
a
fo sfer
n
I
SYS
l
n
a
a
r
b
t
Glo nonTMON
SMON
ARC0
ARC1
ARC2
ARC3
TT00
SMCO
a
25172
25172
oracle@YOURSERVER (FBDA)
25178
25178
oracle@YOURSERVER (W000)
25360
25360
oracle@YOURSERVER (AQPC)
25415
25415
oracle@YOURSERVER (QM02)
25417
25417
oracle@YOURSERVER (Q001)
25419
25419
25487
25487
oracle@YOURSERVER (CJQ0)
26061
26061
26612
26612
26952
26952
27028
27028
oracle@YOURSERVER (M000)
FBDA
W000
AQPC
QM02
Q001
Q002
CJQ0
W001
SYSTEM
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
M000
a
b
lo den
g
@ Stu
o
f
37 rows selected.
(in this
y
og use
l
o
SQL>
hn se to
c
e
n architecture.
T forceMPMT
4. Modify your SPFILE ton
prepare
i
o
l
i
tsystem
SQL> alter
a
leset threaded_execution=true scope=spfile;
b
m
r
a
fo sfer
n
I
n
alSystem
aaltered.
r
b
t
o
Gl nSQL>
on
5.
SYS
Still connected from the same session, shut down your cdb2 instance, and restart it again.
Database closed.
SQL>
SQL> startup
SQL>
6. Why are you getting the " ORA-01017: invalid username/password; logon denied" error?
This is because when using MPMT architecture, you have to use password authentication for
SYSDBA operations.
a
7.
Start up your cdb2 instance.
Connected.
SQL> startup
ORA-01081: cannot start already-running ORACLE - shut it down
first
SQL> alter database mount;
Database altered.
SQL> alter database open;
Database altered.
s
) ha
SQL>
om ฺ
c
ฺ
ch ide
e
t
i
SQL> ! ps -eLo "pid tid comm args" |grep cdb2
l- t Gu
a
b
27375 27375 ora_pmon_cdb2
ora_pmon_cdb2
lo den
g
@ Stu
27377 27377 ora_psp0_cdb2
ora_psp0_cdb2
o
f
(in this
27379 27379 ora_vktm_cdb2
ora_vktm_cdb2
y
se
27385 27385 ora_scmn_cdb2logora_u004_cdb2
u
o
to
27385 27386 oracle chn
ora_u004_cdb2
e
e
s
T cen ora_u004_cdb2
27385 27387 ora_gen0_cdb2
n
o
li
tiora_mman_cdb2
27385 27388
ora_u004_cdb2
e
a
l
b
m
r
a
27385
27398
ora_dbrm_cdb2
ora_u004_cdb2
r
o
f
e
f
n
I 27402
l27385
ns ora_lgwr_cdb2 ora_u004_cdb2
a
a
r
b
t
n- 27403 ora_ckpt_cdb2 ora_u004_cdb2
Glo n27385
o
27385 27404 ora_smon_cdb2
ora_u004_cdb2
8.
Still connected from your SQL*Plus session, list the OS processes and OS threads used to
run your cdb2 instance using OS commands.
27385
27385
27391
27391
27391
27391
27391
27391
27391
27391
27391
27391
27406
27588
27391
27392
27393
27399
27405
27407
27408
27409
27410
27411
ora_lreg_cdb2
ora_rvwr_cdb2
ora_scmn_cdb2
oracle
ora_diag_cdb2
ora_dia0_cdb2
ora_reco_cdb2
ora_mmon_cdb2
ora_mmnl_cdb2
ora_d000_cdb2
ora_s000_cdb2
ora_n000_cdb2
ora_u004_cdb2
ora_u004_cdb2
ora_u005_cdb2
ora_u005_cdb2
ora_u005_cdb2
ora_u005_cdb2
ora_u005_cdb2
ora_u005_cdb2
ora_u005_cdb2
ora_u005_cdb2
ora_u005_cdb2
ora_u005_cdb2
a
27391
27391
27391
27391
27391
27391
27391
27391
27391
27391
27391
27391
27391
27391
27391
27391
27391
27391
27391
27391
27391
27391
27391
27391
27391
27391
27391
27391
27391
27391
27391
27395
27395
27395
27401
27855
27918
args"
27920
27575
27589
27590
27591
27592
27593
27594
27595
27596
27597
27598
27610
27611
27612
27613
27620
27621
27622
27655
27669
27899
27900
27901
27902
27903
27904
27905
27906
27910
27911
27912
27395
27396
27397
27401
27855
27918
|grep
27920
oracle_27575_cd
ora_tmon_cdb2
ora_arc0_cdb2
ora_arc1_cdb2
ora_arc2_cdb2
ora_arc3_cdb2
ora_tt00_cdb2
ora_smco_cdb2
ora_fbda_cdb2
ora_w000_cdb2
ora_aqpc_cdb2
ora_p000_cdb2
ora_p001_cdb2
ora_p002_cdb2
ora_p003_cdb2
ora_qm02_cdb2
ora_q001_cdb2
ora_q002_cdb2
ora_q003_cdb2
ora_cjq0_cdb2
ora_j001_cdb2
ora_j002_cdb2
ora_j003_cdb2
ora_j004_cdb2
ora_j005_cdb2
ora_j006_cdb2
ora_j007_cdb2
ora_j008_cdb2
ora_j009_cdb2
ora_j010_cdb2
ora_j011_cdb2
ora_scmn_cdb2
oracle
ora_ofsd_cdb2
ora_dbw0_cdb2
vim
bash
cdb2
grep
ora_u005_cdb2
ora_u005_cdb2
ora_u005_cdb2
ora_u005_cdb2
ora_u005_cdb2
ora_u005_cdb2
ora_u005_cdb2
ora_u005_cdb2
ora_u005_cdb2
ora_u005_cdb2
ora_u005_cdb2
ora_u005_cdb2
ora_u005_cdb2
ora_u005_cdb2
ora_u005_cdb2
ora_u005_cdb2
ora_u005_cdb2
ora_u005_cdb2
ora_u005_cdb2
ora_u005_cdb2
ora_u005_cdb2
ora_u005_cdb2
ora_u005_cdb2
ora_u005_cdb2
ora_u005_cdb2
ora_u005_cdb2
ora_u005_cdb2
ora_u005_cdb2
ora_u005_cdb2
ora_u005_cdb2
ora_u005_cdb2
ora_u006_cdb2
ora_u006_cdb2
ora_u006_cdb2
ora_dbw0_cdb2
vim alert_cdb2.log
/bin/bash -c ps -eLo "pid tid comm
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
b
lo den
g
@ Stu
o
f
(in this
y
og use
l
o
hn se to
c
e
T cen
n
o
li
ti
e
a
l
rm erab
o
f
In ansf
l
a
b
tr
Glo non-
grep cdb2
SQL>
a
SQL> ! ps -ef | grep cdb2
oracle
27375
1 0 05:03
oracle
27377
1 0 05:03
oracle
27379
1 0 05:03
oracle
27385
1 1 05:03
oracle
27391
1 11 05:03
oracle
27395
1 0 05:03
oracle
27401
1 0 05:03
oracle
27855 31546 0 05:06
alert_cdb2.log
oracle
27955 26951 0 05:07
-ef | grep cdb2
oracle
27957 27955 0 05:07
?
?
?
?
?
?
?
pts/6
00:00:00
00:00:00
00:00:01
00:00:02
00:00:25
00:00:00
00:00:00
00:00:00
ora_pmon_cdb2
ora_psp0_cdb2
ora_vktm_cdb2
ora_u004_cdb2
ora_u005_cdb2
ora_u006_cdb2
ora_dbw0_cdb2
vim
pts/5
00:00:00 /bin/bash -c
pts/5
00:00:00 grep cdb2
SQL>
9.
Do the same using SQL commands.
ps
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
b
lo den
g
@ Stu
o
f
(in this
y
og use
l
o
hn se to
c
e
SPID
PNAME USERNAME
PROGRAM
TSTID cen
n
i
o
l
----------------------------------------------- ----- -------ti
e
a
l
b
-- -----------------------------------------------m
r
ra
o
f
e
f
27375
27375
PMON
n
I ans
l
a
oracle@YOURSERVER
(PMON)
b n-tr
27377
PSP0
Glo n27377
o
SQL> set linesize 300
SQL> col username for a10
SQL> select p.spid, p.stid,p.pname,s.username,s.program
from
v$process p, v$session s
order by 1;
2
3
4
27379
oracle@YOURSERVER
27385
oracle@YOURSERVER
27385
oracle@YOURSERVER
27385
oracle@YOURSERVER
27385
oracle@YOURSERVER
27385
oracle@YOURSERVER
27379
(VKTM)
27388
(MMAN)
27385
(SCMN)
27387
(GEN0)
27406
(LREG)
27588
(RVWR)
VKTM
MMAN
SCMN
GEN0
LREG
RVWR
a
27385
27404
27385
27403
27385
27402
27385
27398
27391
27399
27391
27591
27391
27393
27391
27391
oracle@YOURSERVER (SCMN)
27391
27620
oracle@YOURSERVER (QM02)
27391
27621
27391
27622
27391
27405
27391
27669
27391
27407
27391
27408
oracle@YOURSERVER (MMNL)
27391
27655
27391
27589
oracle@YOURSERVER (TMON)
27391
27590
27391
27575
27391
27592
27391
27593
27391
27594
27391
27595
SMON
CKPT
LGWR
DBRM
DIA0
ARC1
DIAG
SCMN
QM02
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
Q002
a
b
lo den
g
u
@ StRECO
o
f
(in this
y
CJQ0
og use
l
o
hn se to
c
MMON
e
T cen
n
tio le li
MMNL
a
b
m
r
a
fo sfer
n
I
Q003
l
n
a
a
r
b
t
Glo nonTMON
Q001
ARC0
SYS
ARC2
ARC3
TT00
SMCO
a
27391
oracle@YOURSERVER
27391
oracle@YOURSERVER
27391
oracle@YOURSERVER
27395
oracle@YOURSERVER
27395
oracle@YOURSERVER
27401
oracle@YOURSERVER
27596
(FBDA)
27597
(W000)
27598
(AQPC)
27397
(OFSD)
27395
(SCMN)
27401
(DBW0)
FBDA
W000
AQPC
OFSD
SCMN
DBW0
37 rows selected.
SQL>
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
b
lo den
g
SQL> connect sys/oracle_4U@cdb2 as sysdba
@ Stu
o
f
Connected.
(in this
y
SQL> set linesize 300
log o use
o
SQL> col username for n
a10
h se t
c
SQL> select p.spid,
p.stid,p.pname,s.username,s.program
e
T cp,env$session s
n
from iv$process
o
li
t s.paddr
e
a
l
where
b = p.addr
m
r
a
r
o
fbye 1;
nf order
I
s
l
n
ba2 n-t3ra 4
o
l
G no
Now, many Oracle processes run as threads inside a small amount of OS processes.
11. Establish a remote connection to your cdb2 instance using SQL*Plus, and list again OS
processes and threads used to run all Oracle processes.
SPID
STID
PNAME USERNAME
PROGRAM
------------------------ ------------------------ ----- --------- -----------------------------------------------27375
27375
PMON
27377
27377
PSP0
27379
27379
VKTM
27385
27388
MMAN
27385
27385
SCMN
a
27385
oracle@YOURSERVER
27385
oracle@YOURSERVER
27385
oracle@YOURSERVER
27385
oracle@YOURSERVER
27385
oracle@YOURSERVER
27385
oracle@YOURSERVER
27385
oracle@YOURSERVER
27391
oracle@YOURSERVER
27391
oracle@YOURSERVER
27391
oracle@YOURSERVER
27391
oracle@YOURSERVER
27391
oracle@YOURSERVER
27391
oracle@YOURSERVER
27391
oracle@YOURSERVER
27391
oracle@YOURSERVER
27391
oracle@YOURSERVER
27391
oracle@YOURSERVER
27391
oracle@YOURSERVER
27391
oracle@YOURSERVER
27391
oracle@YOURSERVER
27391
oracle@YOURSERVER
27391
oracle@YOURSERVER
27391
oracle@YOURSERVER
27387
(GEN0)
27406
(LREG)
27588
(RVWR)
27404
(SMON)
27403
(CKPT)
27402
(LGWR)
27398
(DBRM)
27399
(DIA0)
27591
(ARC1)
27393
(DIAG)
27391
(SCMN)
27598
(AQPC)
27620
(QM02)
27621
(Q001)
27622
(Q002)
27405
(RECO)
27669
(CJQ0)
27407
(MMON)
27408
(MMNL)
27655
(Q003)
27589
(TMON)
27590
(ARC0)
27592
(ARC2)
GEN0
LREG
RVWR
SMON
CKPT
LGWR
DBRM
DIA0
ARC1
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
SCMN
a
b
lo den
g
u
@ StAQPC
o
f
(in this
y
QM02
og use
l
o
hn se to
c
Q001
e
T cen
n
tio le li
Q002
a
b
m
r
a
fo sfer
n
I
RECO
l
n
a
a
r
b
t
Glo nonCJQ0
DIAG
MMON
MMNL
Q003
TMON
ARC0
ARC2
a
27391
27593
27391
27594
27391
27595
27391
27596
oracle@YOURSERVER (FBDA)
27391
27597
27395
27397
oracle@YOURSERVER (OFSD)
27395
27395
27401
27401
oracle@YOURSERVER (DBW0)
28009
28009
ARC3
TT00
SMCO
FBDA
W000
OFSD
SCMN
DBW0
SYS
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
SQL>
a
b
lo den
g
@ Stu
o
f
is is using one OS process, and
Your foreground process that runs your SQL*Plus
(inconnection
h
t
y
not threads.
og use
l
o
13. How would you make sure foreground
to are using threads?
hn processes
c
e
e
s
SQL> exit
T cen
n
o
li
$
ti
e
a
l
b file content.
rm
a
a. Viewfthe
tnsnames.ora
r
o
e
In ansf
l
$ cat $ORACLE_HOME/network/admin/tnsnames.ora
a
b tnsnames.ora
tr
Network Configuration File:
Glo n#/u01/app/oracle/product/12.1.0/dbhome_1/network/admin/tnsnames.o
on37 rows selected.
ra
# Generated by Oracle configuration tools.
PDB_ORCL2 =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = host01.example.com)(PORT
= 1521))
(CONNECT_DATA =
(SERVER = DEDICATED)
(SERVICE_NAME = pdb_orcl2)
)
)
a
PDB2_2 =
(DESCRIPTION =
= 1521))
(CONNECT_DATA =
(SERVICE_NAME = pdb2_2)
)
)
PDB2_1 =
(DESCRIPTION =
= 1521))
(CONNECT_DATA =
)
)
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
b
lo den
g
CDB2 =
@ Stu
o
f
(DESCRIPTION =
is
(in =thhost01.example.com)(PORT
y
(ADDRESS = (PROTOCOL = TCP)(HOST
og use
l
= 1521))
o
hn se to
(CONNECT_DATA e
=c
T cen
n
(SERVER
= DEDICATED)
o
li
ti
e
a
l
(SERVICE_NAME
b = cdb2)
m
r
a
r
o
nf) nsfe
I
l
ba )n-tra
o
l
G no
CDB1 =
(DESCRIPTION =
= 1521))
(CONNECT_DATA =
(SERVICE_NAME = cdb1)
)
)
ORCL2 =
(DESCRIPTION =
a
= 1521))
(CONNECT_DATA =
(SERVICE_NAME = orcl2)
)
)
PDB1_1 =
(DESCRIPTION =
= 1521))
(CONNECT_DATA =
)
)
s
) ha
om ฺ
c
ฺ
ORCL =
ch ide
e
t
i
(DESCRIPTION =
l- t Gu
a
b
lo den
g
= 1521))
@ Stu
o
f
(CONNECT_DATA =
(in this
(SERVER = DEDICATED) gy
se
o
l
u
(SERVICE_NAME = orcl)
o
hn se to
)
c
e
T cen
)
n
o
li
ti
$
e
a
l
m rab file content.
rlistener.ora
o
b. View the
f
n nsfe
I
l
a
ba$ cat
tr$ORACLE_HOME/network/admin/listener.ora
o
l
n
G n#olistener.ora Network Configuration File:
ra
LISTENER =
(DESCRIPTION_LIST =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC1521))
(ADDRESS = (PROTOCOL = TCP)(HOST =
host01.example.com)(PORT = 1521))
)
)
a
ADR_BASE_LISTENER = /u01/app/oracle
$
c.
Keep a copy of the listener.ora file.
$ cp $ORACLE_HOME/network/admin/listener.ora
$ORACLE_HOME/network/admin/listener.ora.bak
$
d.
Add the following parameter in the listener.ora file.
$ echo DEDICATED_THROUGH_BROKER_LISTENER=on >>
$ORACLE_HOME/network/admin/listener.ora
$
e.
Check that the listener.ora file is adequately modified.
$ cat $ORACLE_HOME/network/admin/listener.ora
# listener.ora Network Configuration File:
ra
s
) ha
om ฺ
c
ฺ
ch ide
LISTENER =
e
t
i
l- t Gu
(DESCRIPTION_LIST =
a
b
lo den
(DESCRIPTION =
g
tu
@= EXTPROC1521))
o
(ADDRESS = (PROTOCOL = IPC)(KEY
S
f
(in th=is
(ADDRESS = (PROTOCOL = y
TCP)(HOST
g use
host01.example.com)(PORT l=o1521))
o
)
hn se to
c
e
T cen
)
n
o
li
ti
e
a
l
rm erab = /u01/app/oracle
ADR_BASE_LISTENER
o
f
In ansf
l
a
b n-tr
Glo nDEDICATED_THROUGH_BROKER_LISTENER=on
o
$
f.
Restart the listener.
$ lsnrctl stop
Connecting to
$
a
$ lsnrctl start
please wait...
TNSLSNR for Linux: Version 12.1.0.0.2 - Production
System parameter file is
ra
Listening on:
Listening on:
RT=1521)))
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
b
lo den
g
@ Stu
o
f
Connecting to
(in this
y
g use
STATUS of the LISTENER olo
hn se to
-----------------------c
e
T cen LISTENER
Alias
n
o
li
i
e
Version at
l
b
m
r
a
- Production
fo sfer
n
I
Start
Date
04-SEP-2012 13:01:29
l
n
a
a
r
b
t
nGlo nUptime
o
Trace Level
off
Security
SNMP
OFF
ra
Listener Log File
RT=1521)))
a
$
g.
Set the LOCAL_LISTENER parameter to cdb2.
$ sqlplus sys/oracle_4U@cdb2 as sysdba
Connected to:
SQL> show parameter local_listener
NAME
TYPE
VALUE
------------------------------------ ----------- -------------local_listener
string
LISTENER_CDB2
s
) ha
om ฺ
c
ฺ
SQL> alter system set local_listener=cdb2 scope=both;
ch ide
e
t
i
l- t Gu
a
b
System altered.
lo den
g
@ Stu
o
f
SQL> show parameter local_listener
(in this
y
og use
l
o
NAME
TYPE
VALUE
hn se to
c
e
---------------------------------------------- -------------T cen
n
i
o
l
local_listener
string
CDB2
ti
e
a
l
b
m
r
ra
o
f
e
f
n
I ans
lSQL>
a
r you did is working.
b
-twhat
Check that
n
G14.loTip:
o
nLooking at the sqlplus program, it should be run as a thread in an existing OS
process.
SQL> connect sys/oracle_4U@cdb2 as sysdba
Connected.
SQL>
SQL>
SQL>
SQL>
2
set linesize 300
set pages 100
col username for a10
select p.spid, p.stid,p.pname,s.username,s.program
from
v$process p, v$session s
order by 1;
3
4
a
SPID
STID
PNAME USERNAME
PROGRAM
------------------------ ------------------------ ----- --------- -----------------------------------------------27375
27375
PMON
27377
27377
PSP0
27379
27379
VKTM
27385
27387
GEN0
oracle@YOURSERVER (GEN0)
27385
27385
SCMN
27385
27398
DBRM
27385
27588
RVWR
oracle@YOURSERVER (RVWR)
27385
27406
LREG
oracle@YOURSERVER (LREG)
27385
27404
SMON
27385
27402
LGWR
27385
27403
CKPT
27385
27388
MMAN
27391
27399
DIA0
27391
27391
SCMN
27391
27393
DIAG
27391
28582
SYS
27391
27405
RECO
27391
27622
Q002
27391
27621
Q001
27391
27669
CJQ0
27391
27407
MMON
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
b
lo den
g
@ Stu
o
f
(in this
y
og use
l
o
hn se to
c
e
T cen
n
o
li
ti
e
a
l
rm erab
o
f
In ansf
l
a
b
tr
Glo non-
a
27391
oracle@YOURSERVER
27391
oracle@YOURSERVER
27391
oracle@YOURSERVER
27391
oracle@YOURSERVER
27391
oracle@YOURSERVER
27391
oracle@YOURSERVER
27391
oracle@YOURSERVER
27391
oracle@YOURSERVER
27391
oracle@YOURSERVER
27391
oracle@YOURSERVER
27391
oracle@YOURSERVER
27391
oracle@YOURSERVER
27395
oracle@YOURSERVER
27395
oracle@YOURSERVER
27401
oracle@YOURSERVER
27408
(MMNL)
27589
(TMON)
27590
(ARC0)
27591
(ARC1)
27592
(ARC2)
27593
(ARC3)
27594
(TT00)
27595
(SMCO)
27596
(FBDA)
27597
(W000)
27598
(AQPC)
27620
(QM02)
27395
(SCMN)
27397
(OFSD)
27401
(DBW0)
MMNL
TMON
ARC0
ARC1
ARC2
ARC3
TT00
SMCO
FBDA
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
AQPC
a
b
lo den
g
u
@ StQM02
o
f
(in this
y
SCMN
og use
l
o
hn se to
c
OFSD
e
T cen
n
tio le li
DBW0
a
b
m
r
a
fo sfer
n
I
al -tran
b
o
Gl n36onrows selected.
W000
SQL>
15. Revert to the non-MPMT architecture. Keep the cdb2 database closed for the moment so
as to preserve resources on the machine.
SQL> alter system set threaded_execution=false scope=spfile;
System altered.
Database closed.
a
SQL> exit
$
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
b
lo den
g
@ Stu
o
f
(in this
y
og use
l
o
hn se to
c
e
T cen
n
o
li
ti
e
a
l
rm erab
o
f
In ansf
l
a
b
tr
Glo non-
a
s
) ha
om ฺ
c
ฺ
ch18: ide
e
t
i
u
l-and tOnline
Tables, Indexes
G
a
b
lo den
g
Operations
@ Stu
o
f
Chapter
(in 18 this
y
og use
l
o
hn se to
c
e
T cen
n
o
li
ti
e
a
l
rm erab
o
f
In ansf
l
a
b
tr
Glo non-
Practices for Lesson 18: Tables, Indexes and Online Operations
Chapter 18 - Page 1
a
Practices Overview
In the practice for this lesson, you will use the invisible/visible table columns and the Advanced
Row compression.
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
b
lo den
g
@ Stu
o
f
(in this
y
og use
l
o
hn se to
c
e
T cen
n
o
li
ti
e
a
l
rm erab
o
f
In ansf
l
a
b
tr
Glo non-
Chapter 18 - Page 2
a
Practice 18-1: Using Invisible Table Columns
Overview
In this practice, you will create a table with invisible columns. These columns are not necessarily
useful for the current application but might become useful in a later application release.
Tasks
1.
Make sure you are in the ~/labs/Tables directory and your environment points to the
orcl instance.
$ cd ~/labs/Tables
$ . oraenv
$
2.
First start the instance up.
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
b
lo den
g
@ Stu
o
f
is
(in bytes
h
t
y
Fixed Size
2271568
se
og ubytes
l
o
Variable Size
to bytes
hn339740336
c
e
e
s
Database BuffersT
50331648
bytes
n
e
n
c
i
o
Redo Buffers
8503296
bytes
l
ti
e
a
l
b
Database
rmmounted.
a
r
o
f
e
Database
In anopened.
sf
l
a
b SQL>
-tr
G3.loRunnthe
oninvisible_setup.sql
script to create a new user STATS
SQL> startup
SQL> @invisible_setup.sql
Connected.
DROP USER stats CASCADE
*
ERROR at line 1:
ORA-01918: user 'STATS' does not exist
User created.
Grant succeeded.
SQL>
Chapter 18 - Page 3
a
4.
The STATS user creates a new table CENSUS. The table structure contains three columns,
GENDER, COUNTRY, NUMBER and an invisible column REGION. The REGION column is not
used by the application yet, but might become useful in a future application release.
SQL> CREATE TABLE stats.census (gender VARCHAR2(10), country
CHAR(2), nb NUMBER, region VARCHAR2(20) INVISIBLE );
Table created.
SQL>
5.
Describe the structure of the CENSUS table.
a. You see that the invisible column does not appear.
SQL> DESC stats.census
Name
Null?
-------------------------- -------GENDER
COUNTRY
NB
Type
-------------------------VARCHAR2(10)
CHAR(2)
NUMBER
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
SQL>
l- t Gu
a
b
lo column
b. Describe the structure of the CENSUS table so that theginvisible
en appears.
d
u
o@ is St
SQL> SET COLINVISIBLE ON
f
n
i
(
SQL> DESC stats.census
th
y
g
e
lo Null?
Name
us Type
o
n
o
t
-------------------------ch nse-------- -------------------------e
T
GENDER
VARCHAR2(10)
n
ce
i
o
l
i
t
e
COUNTRY a
CHAR(2)
l
b
m
r
a
NB fo
NUMBER
er
f
n
I
s
VARCHAR2(20)
al REGION
an(INVISIBLE)
r
b
t
o
Gl non
SQL>
6.
Insert rows into the CENSUS table.
a. You cannot insert a value for the invisible column unless you define it in the projection
list.
SQL> INSERT INTO stats.census VALUES ('BOY','BR', 10000,
'BAHIA');
INSERT INTO stats.census VALUES ('BOY','BR', 10000, 'BAHIA')
*
ERROR at line 1:
ORA-00913: too many values
SQL>
Chapter 18 - Page 4
a
b.
Insert a row with values for the three visible columns.
SQL> INSERT INTO stats.census VALUES ('BOY','BR',100000);
1 row created.
SQL> COMMIT;
Commit complete.
SQL> SELECT * FROM stats.census;
GENDER
CO
NB
---------- -- ---------BOY
BR
100000
SQL>
s
) ha
om ฺ
c
ฺ
chregion)
SQL> INSERT INTO stats.census (gender, country, tnb,
de
e
i
i
u
l
VALUES ('BOY','BR', 35000,'BAHIA');
ba ent G
o
l
g tud
@
1 row created.
o
nf this S
i
(
ogy use
SQL> COMMIT;
l
o
hn se to
c
e
T cen
Commit complete.
n
o
li
ti
e
a
l
b country, nb, region FROM stats.census;
rm egender,
a
SQL>fo
SELECT
r
In ansf
l
a
b n-tr
CO
NB REGION
Glo nGENDER
o
---------- -- ---------- -------------------c.
Insert a row with a value for the invisible column.
BOY
BOY
BR
BR
100000
35000 BAHIA
SQL>
7.
Make the invisible column visible.
SQL> ALTER TABLE stats.census MODIFY (region VISIBLE);
Table altered.
SQL> SELECT * FROM stats.census;
GENDER
CO
NB REGION
Chapter 18 - Page 5
a
---------- -- ---------- -------------------BOY
BR
100000
BOY
BR
35000 BAHIA
SQL> EXIT
$
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
b
lo den
g
@ Stu
o
f
(in this
y
og use
l
o
hn se to
c
e
T cen
n
o
li
ti
e
a
l
rm erab
o
f
In ansf
l
a
b
tr
Glo non-
Chapter 18 - Page 6
a
Practice 18-2: Advanced Row Compression
Overview
In this practice, you will use the row store advanced compression. You will compare the storage
requirements between a compressed table and an uncompressed table and verify the
compression ratio between different tables with the same number of rows.
Tasks
1.
Connect as SH. You first create two copies of the SH.SALES table, the first being
compressed and the second being uncompressed.
Connected.
SQL> drop table sales_nocompress purge;
Table dropped.
SQL> drop table sales_advcompress purge;
s
) ha
om ฺ
c
ฺ
ch ide
Table dropped.
e
t
i
l- t Gu
a
b
lo den
SQL> set echo on
g
@ Stu
SQL> set timing on
o
f
is * FROM sales;
(in AS tSELECT
h
SQL> CREATE TABLE sales_nocompress
y
og use
l
o
hn se to
Table created.
c
e
T cen
n
o
li
ti
e
Elapsed: 00:00:02.13
a
l
b sales_advcompress ROW STORE COMPRESS ADVANCED
rm eTABLE
a
r
SQL>fo
CREATE
s*f FROM sales where 1=0;
ASInSELECT
l
n
a
a
b n-tr
Glo nTable
o created.
Elapsed: 00:00:00.05
SQL>
SQL> SELECT count(*) FROM sales_nocompress;
COUNT(*)
---------918843
Elapsed: 00:00:00.44
SQL> SELECT count(*) FROM sales_advcompress;
Chapter 18 - Page 7
a
COUNT(*)
---------0
Elapsed: 00:00:00.00
SQL>
2.
Load the SALES_ADVCOMPRESS table using the following PL/SQL block.
SQL> declare
commit_after integer := 0 ;
loop_variable integer ;
cursor c_sales is
select prod_id, cust_id, time_id, channel_id, promo_id,
quantity_sold, amount_sold
from sales ;
begin
for r_sales in c_sales
loop
if commit_after = 0
then
loop_variable := 0 ;
commit_after := round(dbms_random.value(1,1)) ;
end if ;
insert into sales_advcompress
(prod_id, cust_id, time_id, channel_id, promo_id,
quantity_sold, amount_sold)
values
(r_sales.prod_id, r_sales.cust_id, r_sales.time_id,
r_sales.channel_id,
r_sales.promo_id, r_sales.quantity_sold, r_sales.amount_sold)
;
if loop_variable = commit_after
then
commit ;
commit_after := 0 ;
end if ;
loop_variable := loop_variable + 1 ;
end loop ;
end ;
/
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
b
lo den
g
@ Stu
o
f
(in this
y
og use
l
o
hn se to
c
e
T cen
n
o
li
ti
e
a
l
rm erab
o
f
In ansf
l
a
b
tr
Glo non-
Chapter 18 - Page 8
a
2
15
28
3
16
4
17
5
18
6
19
7
20
8
21
9
22
10
23
11
24
12
25
13
26
14
27
Elapsed: 00:01:37.67
SQL>
3.
Verify the number of rows in the two tables.
SQL> SELECT count(*) FROM sales_nocompress;
COUNT(*)
---------918843
Elapsed: 00:00:00.02
SQL> SELECT count(*) FROM sales_advcompress;
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
COUNT(*)
l- t Gu
a
b
---------lo den
g
918843
@ Stu
o
f
(in this
y
Elapsed: 00:00:00.31
og use
l
o
SQL>
hn se to
c
e
n
4. Now you can compare n
theT
storage e
requirements
between the two tables you just created.
c
i
o
l
i
t
SQL> COL segment_name
a
le FORMAT A30
b
m
r
a
r
SQL>fo
select e
segment_name,
sum(bytes)/1024/1024 mb
f
n
I
s
alfrom-tdba_segments
an
r
b
o
where
owner
= 'SH' and segment_name in
Gl n('SALES_NOCOMPRESS','SALES_ADVCOMPRESS')
on
group by segment_name order by segment_name;
2
3
4
SEGMENT_NAME
MB
----------------------- ---------SALES_ADVCOMPRESS
14
SALES_NOCOMPRESS
36
Elapsed: 00:00:00.46
SQL>
Chapter 18 - Page 9
a
5.
Use the DBMS_COMPRESSION package to get the compression ratio of the
SALES_ADVCOMPRESS table.
SQL> DECLARE
blkcnt_cmp pls_integer;
blkcnt_uncmp pls_integer;
row_cmp pls_integer;
row_uncmp pls_integer;
cmp_ratio pls_integer;
comptype_str varchar2(100);
BEGIN
DBMS_COMPRESSION.GET_COMPRESSION_RATIO (
'USERS', 'SH', 'SALES_ADVCOMPRESS', NULL,
DBMS_COMPRESSION.COMP_ADVANCED,
blkcnt_cmp, blkcnt_uncmp, row_cmp, row_uncmp, cmp_ratio,
comptype_str,1000,1);
DBMS_OUTPUT.PUT_LINE('Table = SH.SALES_ADVCOMPRESS');
DBMS_OUTPUT.PUT_LINE('Block count compressed = ' ||
blkcnt_cmp);
DBMS_OUTPUT.PUT_LINE('Block count uncompressed = ' ||
blkcnt_uncmp);
DBMS_OUTPUT.PUT_LINE('Row count per block compressed = ' ||
row_cmp);
DBMS_OUTPUT.PUT_LINE('Row count per block uncompressed = ' ||
row_uncmp);
DBMS_OUTPUT.PUT_LINE('Compression type = ' || comptype_str);
DBMS_OUTPUT.PUT_LINE('Compression ratio =
'||blkcnt_uncmp/blkcnt_cmp||' to 1');
DBMS_OUTPUT.PUT_LINE('Compression ratio org= '||cmp_ratio);
END;
/
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
Table = SH.SALES_ADVCOMPRESS
Block count compressed = 1628
Block count uncompressed = 4379
Row count per block compressed = 558
Row count per block uncompressed = 207
Compression type = "Compress Advanced"
Compression ratio = 2.68980343980343980343980343980343980344 to
1
Compression ratio org= 3
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
b
lo den
g
@ Stu
o
f
(in this
y
og use
l
o
hn se to
c
e
T cen
n
o
li
ti
e
a
l
rm erab
o
f
In ansf
l
a
b
tr
Glo non-
a
Elapsed: 00:00:13.19
SQL>
6.
Analyze the tables and note the number of rows compressed in the compressed table and
compare the ratio of compression with the non compressed table.
SQL> ANALYZE TABLE sh.sales_nocompress COMPUTE STATISTICS;
Table analyzed.
Elapsed: 00:00:05.30
SQL> ANALYZE TABLE sh.sales_advcompress COMPUTE STATISTICS;
Table analyzed.
s
) ha
Elapsed: 00:00:05.76
SQL>
om ฺ
c
ฺ
ch ide
SQL> COL object_name format A20
e
t
i
l- t Gu
a
b
lo den
Connected.
g
tu
@ AVGROWSIZE_C,
o
S
SQL> SELECT object_name , AVGROWSIZE_NC,
NBLK_NC,
f
n this
i
(
NBLK_ADVANCED, NROWS_NC, NROWS_ADVANCED
se
ocgy, DBA_OBJECTS
l
FROM sys.compression_stat$
o
u
o
n
o
t
WHERE c.obj# = o.object_id;
ch nse
e
T
2
3
n
ce
i
o
l
i
t
a
le
b
m
r
a
OBJECT_NAME
AVGROWSIZE_NC AVGROWSIZE_C
NBLK_NC
fo sfer
n
I
------------- ------------ ---------al-------------------an
r
b
t
o
NROWS_NC NROWS_ADVANCED
Gl nNBLK_ADVANCED
on
------------- ---------- -------------SALES_ADVCOMPRESS
1732
35010
32.8
883833
10.43
Elapsed: 00:00:00.27
SQL> SELECT avg_row_len, num_rows FROM dba_tables WHERE
table_name='SALES_NOCOMPRESS';
AVG_ROW_LEN
NUM_ROWS
----------- ---------33
918843
8
a
SQL>
7.
The non compressed table contains 918843 uncompressed rows whereas the compressed
table contains 883833 compressed rows and only 35010 uncompressed rows with an
average row size 3 times smaller.
Cleanup the tables.
SQL> DROP TABLE sh.sales_nocompress PURGE;
Table dropped.
Elapsed: 00:00:00.62
SQL> DROP TABLE sh.sales_advcompress PURGE;
Table dropped.
Elapsed: 00:00:00.13
s
) ha
om ฺ
c
ฺ
SQL> EXIT
ch ide
e
t
i
$
l- t Gu
a
b
lo den
g
@ Stu
o
f
(in this
y
og use
l
o
hn se to
c
e
T cen
n
o
li
ti
e
a
l
rm erab
o
f
In ansf
l
a
b
tr
Glo non-
a
s
) ha
om ฺ
c
ฺ
ch19: iADR
de
e
t
i
u
l
and Network bEnhancements
a nt G
o
l
g tude
Chapter 19 @
nfo this S
i
(
ogy use
l
o
hn se to
c
e
T cen
n
o
li
ti
e
a
l
rm erab
o
f
In ansf
l
a
b
tr
Glo non-
Practices for Lesson 19: ADR and Network Enhancements
Chapter 19 - Page 1
a
Practices Overview
In this practice, you will familiarize yourself with viewing an ADR DDL log file and content.
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
b
lo den
g
@ Stu
o
f
(in this
y
og use
l
o
hn se to
c
e
T cen
n
o
li
ti
e
a
l
rm erab
o
f
In ansf
l
a
b
tr
Glo non-
Chapter 19 - Page 2
a
Practice 19-1: Viewing ADR DDL Log File
Overview
In this practice, you will find and view the ADR DDL log file.
Tasks
1.
Set the ENABLE_DDL_LOGGING instance parameter to TRUE to activate the DDL logging.
$ . oraenv
Connected to:
Testing options
s
) ha
om ฺ
c
ฺ
ch ide
SQL> ALTER SYSTEM SET enable_ddl_logging=TRUE SCOPE=both;
e
t
i
l- t Gu
a
b
lo den
g
System altered.
@ Stu
o
f
(in this
SQL> EXIT
y
og use
l
$
o
hn e to
c
2. The administrator is performing
varioussadministration
tasks requiring DDL statements.
e
T cen
n
tio le li
a
rm erab
o
f
f
Connected
In ansto:
l
a
b Oracle
tr Database 12c Enterprise Edition Release 12.1.0.0.2 Glo n64bit
on- Production
Testing options
SQL*Plus: Release 12.1.0.0.2 Production on Fri Aug 24 11:09:58
2012
SQL> CREATE TABLE scott.test1 (c NUMBER);
Table created.
SQL> CREATE TABLE scott.test2 (c VARCHAR2(10));
Chapter 19 - Page 3
a
Table created.
SQL> CREATE USER new_u1 IDENTIFIED BY oracle_4U;
User created.
SQL> DROP USER new_u1 CASCADE;
User dropped.
SQL> DROP TABLE scott.test2;
Table dropped.
SQL> DROP TABLE scott.test1;
s
) ha
om ฺ
c
ฺ
Table dropped.
ch ide
e
t
i
SQL> EXIT
l- t Gu
a
b
$
lo den
g
@ Stu
3. Check the existence of the DDL log file in the ADRfdirectory.
o
(in this
$ cd /u01/app/oracle/diag/rdbms/orcl/orcl/log/ddl
y
og use
l
$ ls -ltr
o
hn se to
total 4
c
e
n 1257 Sep 10 05:19 log.xml
T oinstall
e
-rw-r----- 1 oracle
n
c
i
o
l
ti
$
a
le
b
m
r
a
r the content of the DLL log file.
foutilitystofeview
4. Use ADRCI
n
I
alLaunch
anadrci utility and execute the SHOW LOG command.
a.
the
r
b
t
o
n
Gl n$oadrci
ADRCI: Release 12.1.0.0.2 - Production on Fri Aug 24 11:50:36
2012
rights reserved.
ADR base = "/u01/app/oracle"
adrci> SHOW LOG
b.
A vi editor page is displayed.
2012-09-10 05:18:58.322000 +00:00
CREATE TABLE scott.test1 (c NUMBER)
2012-09-10 05:19:02.625000 +00:00
CREATE TABLE scott.test2 (c VARCHAR2(10))
Chapter 19 - Page 4
All
a
2012-09-10 05:19:36.456000 +00:00
DROP USER new_u1 CASCADE
2012-09-10 05:19:38.594000 +00:00
DROP TABLE scott.test2
2012-09-10 05:19:41.920000 +00:00
DROP TABLE scott.test1
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
"/tmp/utsout_22394_14071_1.ado" 20L, 675C
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
b
lo den
g
@ Stu
o
f
(in this
y
og use
l
o
hn se to
c
e
T cen
n
o
li
ti
e
a
l
rm erab
o
f
In ansf
l
a
b
tr
Gloc. nToonquit- the editor, use the :q vi command.
:q
ADR Home = /u01/app/oracle/diag/rdbms/orcl/orcl:
****************************************************************
*********
Output the results to file: /tmp/utsout_22424_13977_2.ado
adrci> EXIT
$
Chapter 19 - Page 5
a
5.
View the content of the DDL log file with a UNIX command.
$ more /u01/app/oracle/diag/rdbms/orcl/orcl/log/ddl/log.xml
<msg time='2012-09-10T05:18:58.322+00:00' org_id='oracle'
comp_id='rdbms'
msg_id='opiexe:4142:2946163730' type='UNKNOWN' group='diag_adl'
level='16' host_id='EDRSR7P1' host_addr='139.185.35.107'
version='1'>
<txt>CREATE TABLE scott.test1 (c NUMBER)
</txt>
</msg>
comp_id='rdbms'
level='16' host_id='EDRSR7P1' host_addr='139.185.35.107'>
<txt>CREATE TABLE scott.test2 (c VARCHAR2(10))
</txt>
</msg>
comp_id='rdbms'
<txt>DROP USER new_u1 CASCADE
</txt>
</msg>
comp_id='rdbms'
<txt>DROP TABLE scott.test2
</txt>
</msg>
comp_id='rdbms'
<txt>DROP TABLE scott.test1
</txt>
</msg>
$
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
b
lo den
g
@ Stu
o
f
(in this
y
og use
l
o
hn se to
c
e
T cen
n
o
li
ti
e
a
l
rm erab
o
f
In ansf
l
a
b
tr
Glo non-
Chapter 19 - Page 6
a
s
) ha
om ฺ
c
ฺ
ch20: ide
e
t
i
l- t Gu
Oracle Data Pump,
a
b
n
lo anddeExternal
g
SQL*Loader,
u
o@ is St
f
Tables
n
i
(
th
y
g
e
lo Chapter
us20
o
n
o
t
ech ense
T
n
o
lic
i
t
e
a
l
rm erab
o
f
In ansf
l
a
b
tr
Glo non-
Practices for Lesson 20: Oracle Data Pump, SQL*Loader, and External Tables
Chapter 20 - Page 1
a
Practices Overview
In these practices, you will create a new non-CDB named orcl3 with DBCA. After the non-CDB
orcl3 creation is completed, you will perform a FULL TRANSPORTABLE from the non-CDB
orcl into the non-CDB orcl3.
You will also perform a data load by using SQL*Loader Express Mode.
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
b
lo den
g
@ Stu
o
f
(in this
y
og use
l
o
hn se to
c
e
T cen
n
o
li
ti
e
a
l
rm erab
o
f
In ansf
l
a
b
tr
Glo non-
Chapter 20 - Page 2
a
Practice 20-1: Creating a New non-CDB orcl3
Overview
In this practice, you will create a new non-CDB named orcl3 with DBCA.
Assumptions
The created non-CDB orcl already exists.
Tasks
1.
Create a non-CDB named orcl3 using DBCA following the steps below. Be sure to select
Unicode (AL32UTF8) as the character set.
$ export ORACLE_HOME=/u01/app/oracle/product/12.1.0/dbhome_1
$ dbca
Step
a.
Step 1: Database Operation
Choices or Values
Select “Create Database”.
Click Next.
s
) ha
a
om ฺ
c
ฺ
ch ide
e
t
i
u
l- t orGTransaction
a
c.
Step 3: Database Template
Select “General
Purpose
b
lo den
g
Processing”.
tu
@
o
S
f
Click
Next.
(in this
d.
Step 4: Database Identification gy
Enter
se
o
l
u
o
n e to Global Database Name: orcl3
h
c
SID: orcl3
Te cens
n
i
o
l
DON’T SELECT “Create as Container Database.
ti
e
a
l
b
m
Click Next.
r
ra
o
f
e
f
n
e.al I Step n
5: s
Management Options
ConfigureEnterprise Manager (EM) Database
a
r
b
t
Express
Glo nonClick Next
b.
Step 2: Creation Mode
Select “Advanced Mode”.
Click Next.
f.
Step 6: Database Credentials
Select “Use same Administrative password…”
Enter:
Password: oracle_4U
Confirm password: oracle_4U
Click Next.
g.
Step 7: Network Configuration
Click Next.
h.
Step 8: Storage Locations
Confirm Storage type is “File System.”
Select “Use Common Location for All Database
Files”.
Click Next.
i.
Step 9: Database Options
DON’T SELECT “Sample Schemas” Click Next.
Chapter 20 - Page 3
Step
2.
Choices or Values
j.
Step 10: Initialization Parameters
Select “Character Sets”.
Select “Use Unicode (AL32UTF8)”.
Click Next.
k.
Step 11: Creation Options
Select “Create Database” .
Click Next.
l.
Step 12: Pre Requisite Checks
Click Next.
m.
Step 13: Summary
Click Finish.
n.
Step 14: Progress Page
On the Database Configuration Assistant page (for
password management) click Exit.
Click Close.
While the creation of the new orcl3 database is processing, you can start preparing the
source orcl database for FULL TRANSPORTABLE exportation. Move to Practice 20-2.
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
b
lo den
g
@ Stu
o
f
(in this
y
og use
l
o
hn se to
c
e
T cen
n
o
li
ti
e
a
l
rm erab
o
f
In ansf
l
a
b
tr
Glo non-
Chapter 20 - Page 4
a
Practice 20-2: Exporting/Importing Databases in FULL
TRANSPORTABLE Mode
Overview
In this practice, you export the orcl database and import into the orcl3 database using the
Oracle Data Pump FULL TRANSPORTABLE feature.
Tasks
1.
Connect to the source database orcl.
$ . oraenv
s
) ha
Connected to:
Testing options
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
b
lo den
g
@ Stu
o
SQL>
f
in this
(database
y
2. Put the user-defined tablespaces in the source
g use orcl in read-only mode.
o
l
o
a. Create new tablespace to be transported
n e towith other tablespaces into orcl3 database.
h
c
SQL> CREATE TABLESPACE
ns DATAFILE
Te cetest
n
'/u01/app/oracle/oradata/orcl/test01.dbf'
size 5M;
i
o
l
i
t
e
a
bl
m
r
a
r
o
e
Tablespace
nf nsfcreated.
I
l
ba n-tra
o
l
G nSQL>
o
b.
Create a table HR.TESTTAB in the TEST tablespace, insert rows, and commit. You will
check at the end of the FULL TRANSPORTABLE operation from orcl to orcl3
database if the HR.TESTTAB has been transported in a TEST tablespace in the
orcl3 database.
SQL> CREATE TABLE hr.testtab ( id NUMBER, label VARCHAR2(10))
TABLESPACE test;
Table created.
SQL> INSERT INTO hr.testtab VALUES (10,'Skirt');
1 row created.
Chapter 20 - Page 5
a
SQL> INSERT INTO hr.testtab VALUES (20,'Trousers');
1 row created.
SQL> COMMIT;
Commit complete.
SQL>
c.
Find the list of user-defined tablespaces to be put in read-only mode.
SQL> SELECT tablespace_name FROM dba_tablespaces ORDER BY 1;
TABLESPACE_NAME
-----------------------------EXAMPLE
SYSAUX
SYSTEM
TEMP
TEST
UNDOTBS1
USERS
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
b
lo den
g
@ Stu
o
f
(in this
y
og use
l
7 rows selected.
o
hn se to
c
e
T cen
SQL>
n
o
li
tidifferentlefrom
a
d. The list may
be
yours according to the tablespaces created during the
b
m
r
a
r
o
training
session.
Make
all
tablespaces
except SYSTEM, SYSAUX, TEMP, and UNDOTBS1
f
e
f
n
I
s
alread-only.
an
r
b
t
o
Gl nSQL>
on ALTER TABLESPACE example READ ONLY;
Tablespace altered.
SQL> ALTER TABLESPACE test READ ONLY;
Tablespace altered.
SQL> ALTER TABLESPACE users
READ ONLY;
Tablespace altered.
SQL>
Chapter 20 - Page 6
a
e.
Find the list of data files associated to the read-only tablespaces that need to be
transported.
SQL> SELECT file_name FROM dba_data_files
2 WHERE tablespace_name IN ('EXAMPLE',
'FDA_TBS','TEST','USERS');
FILE_NAME
--------------------------------------------------------------/u01/app/oracle/oradata/orcl/users01.dbf
/u01/app/oracle/oradata/orcl/test01.dbf
SQL> EXIT
$
3.
Export the orcl database in full transportable mode.
$ rm /u01/app/oracle/admin/orcl/dpdump/expfull.dmp
$ expdp system/oracle_4U DUMPFILE=expfull.dmp FULL=Y
TRANSPORTABLE=ALWAYS LOGFILE=exp.log
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
b
Connected to: Oracle Database 12c Enterprise
Edition
lo den Release
g
@ Stu
o
f
Real
n tAnalytics,
s
i
i
(
h
Application Testing
ogy use
l
o
hn se to
c
Starting "SYSTEM"."SYS_EXPORT_FULL_01":
system/********
e
n
T
DUMPFILE=expfull.dmp
FULL=Y
TRANSPORTABLE=ALWAYS
LOGFILE=exp.log
e
n
c
i
o
l
i
t
Estimate in
a progress
le using BLOCKS method...
b
m
r
a
Processing
fo sfobject
er type
n
I
DATABASE_EXPORT/PLUGTS_FULL/FULL/PLUGTS_TABLESPACE
alProcessing
an object type DATABASE_EXPORT/PLUGTS_FULL/PLUGTS_BLK
r
b
t
o
Gl nProcessing
on
object type
DATABASE_EXPORT/EARLY_OPTIONS/VIEWS_AS_TABLES/TABLE_DATA
Processing object type DATABASE_EXPORT/NORMAL_OPTIONS/TABLE_DATA
DATABASE_EXPORT/NORMAL_OPTIONS/VIEWS_AS_TABLES/TABLE_DATA
Processing object type DATABASE_EXPORT/SCHEMA/TABLE/TABLE_DATA
Total estimation using BLOCKS method: 2.703 MB
DATABASE_EXPORT/PRE_SYSTEM_IMPCALLOUT/MARKER
DATABASE_EXPORT/PRE_INSTANCE_IMPCALLOUT/MARKER
Processing object type DATABASE_EXPORT/TABLESPACE
Processing object type DATABASE_EXPORT/PROFILE
Processing object type DATABASE_EXPORT/SYS_USER/USER
Chapter 20 - Page 7
a
Processing object type DATABASE_EXPORT/SCHEMA/USER
Processing object type DATABASE_EXPORT/ROLE
Processing object type DATABASE_EXPORT/RADM_FPTM
DATABASE_EXPORT/GRANT/SYSTEM_GRANT/PROC_SYSTEM_GRANT
Processing object type DATABASE_EXPORT/SCHEMA/GRANT/SYSTEM_GRANT
Processing object type DATABASE_EXPORT/SCHEMA/ROLE_GRANT
Processing object type DATABASE_EXPORT/SCHEMA/DEFAULT_ROLE
Processing object type DATABASE_EXPORT/SCHEMA/ON_USER_GRANT
Processing object type DATABASE_EXPORT/SCHEMA/TABLESPACE_QUOTA
Processing object type DATABASE_EXPORT/RESOURCE_COST
Processing object type DATABASE_EXPORT/TRUSTED_DB_LINK
Processing object type DATABASE_EXPORT/SCHEMA/SEQUENCE/SEQUENCE
Processing object type DATABASE_EXPORT/DIRECTORY/DIRECTORY
DATABASE_EXPORT/DIRECTORY/GRANT/OWNER_GRANT/OBJECT_GRANT
Processing object type DATABASE_EXPORT/SCHEMA/SYNONYM
Processing object type DATABASE_EXPORT/SCHEMA/TYPE/INC_TYPE
Processing object type DATABASE_EXPORT/SCHEMA/TYPE/TYPE_SPEC
DATABASE_EXPORT/SCHEMA/TYPE/GRANT/OWNER_GRANT/OBJECT_GRANT
DATABASE_EXPORT/SYSTEM_PROCOBJACT/PRE_SYSTEM_ACTIONS/PROCACT_SYS
TEM
Processing object type DATABASE_EXPORT/SYSTEM_PROCOBJACT/PROCOBJ
DATABASE_EXPORT/SYSTEM_PROCOBJACT/POST_SYSTEM_ACTIONS/PROCACT_SY
STEM
Processing object type DATABASE_EXPORT/SCHEMA/PROCACT_SCHEMA
DATABASE_EXPORT/EARLY_OPTIONS/VIEWS_AS_TABLES/TABLE
DATABASE_EXPORT/EARLY_POST_INSTANCE_IMPCALLOUT/MARKER
DATABASE_EXPORT/SCHEMA/XMLSCHEMA/XMLSCHEMA
Processing object type DATABASE_EXPORT/NORMAL_OPTIONS/TABLE
DATABASE_EXPORT/NORMAL_OPTIONS/VIEWS_AS_TABLES/TABLE
Processing object type DATABASE_EXPORT/NORMAL_OPTIONS/PROCEDURE
DATABASE_EXPORT/NORMAL_OPTIONS/OPTION_PACKAGE/PACKAGE_SPEC
DATABASE_EXPORT/NORMAL_OPTIONS/OPTION_PACKAGE/PACKAGE_BODY
DATABASE_EXPORT/NORMAL_POST_INSTANCE_IMPCALLOU/MARKER
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
b
lo den
g
@ Stu
o
f
(in this
y
og use
l
o
hn se to
c
e
T cen
n
o
li
ti
e
a
l
rm erab
o
f
In ansf
l
a
b
tr
Glo non-
Chapter 20 - Page 8
a
Processing object type DATABASE_EXPORT/SCHEMA/TABLE/TABLE
DATABASE_EXPORT/SCHEMA/TABLE/GRANT/OWNER_GRANT/OBJECT_GRANT
Processing object type DATABASE_EXPORT/SCHEMA/TABLE/COMMENT
DATABASE_EXPORT/XS_SECURITY/SCHEMA/XS_SECURITY_CLASS
Processing object type DATABASE_EXPORT/SCHEMA/FUNCTION/FUNCTION
DATABASE_EXPORT/SCHEMA/PROCEDURE/PROCEDURE
DATABASE_EXPORT/SCHEMA/FUNCTION/ALTER_FUNCTION
DATABASE_EXPORT/SCHEMA/PROCEDURE/ALTER_PROCEDURE
Processing object type DATABASE_EXPORT/SCHEMA/TABLE/INDEX/INDEX
DATABASE_EXPORT/SCHEMA/TABLE/INDEX/FUNCTIONAL_INDEX/INDEX
DATABASE_EXPORT/SCHEMA/TABLE/CONSTRAINT/CONSTRAINT
DATABASE_EXPORT/SCHEMA/TABLE/INDEX/STATISTICS/INDEX_STATISTICS
DATABASE_EXPORT/SCHEMA/TABLE/INDEX/STATISTICS/FUNCTIONAL_INDEX/I
NDEX_STATISTICS
Processing object type DATABASE_EXPORT/SCHEMA/VIEW/VIEW
DATABASE_EXPORT/SCHEMA/VIEW/GRANT/OWNER_GRANT/OBJECT_GRANT
Processing object type DATABASE_EXPORT/SCHEMA/VIEW/COMMENT
Processing object type DATABASE_EXPORT/SCHEMA/TYPE/TYPE_BODY
DATABASE_EXPORT/SCHEMA/TABLE/CONSTRAINT/REF_CONSTRAINT
DATABASE_EXPORT/SCHEMA/TABLE/INDEX/BITMAP_INDEX/INDEX
DATABASE_EXPORT/SCHEMA/TABLE/INDEX/STATISTICS/BITMAP_INDEX/INDEX
_STATISTICS
DATABASE_EXPORT/SCHEMA/TABLE/STATISTICS/TABLE_STATISTICS
Processing object type DATABASE_EXPORT/STATISTICS/MARKER
DATABASE_EXPORT/SCHEMA/TABLE/INDEX/DOMAIN_INDEX/INDEX
Processing object type DATABASE_EXPORT/SCHEMA/TABLE/TRIGGER
Processing object type DATABASE_EXPORT/SCHEMA/VIEW/TRIGGER
Processing object type DATABASE_EXPORT/SCHEMA/MATERIALIZED_VIEW
Processing object type DATABASE_EXPORT/SCHEMA/DIMENSION
Processing object type DATABASE_EXPORT/END_PLUGTS_BLK
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
b
lo den
g
@ Stu
o
f
(in this
y
og use
l
o
hn se to
c
e
T cen
n
o
li
ti
e
a
l
rm erab
o
f
In ansf
l
a
b
tr
Glo non-
Chapter 20 - Page 9
a
DATABASE_EXPORT/FINAL_POST_INSTANCE_IMPCALLOUT/MARKER
DATABASE_EXPORT/SCHEMA/TABLE/POST_INSTANCE/PROCACT_INSTANCE
DATABASE_EXPORT/SCHEMA/TABLE/POST_INSTANCE/PROCDEPOBJ
DATABASE_EXPORT/SCHEMA/POST_SCHEMA/PROCOBJ
DATABASE_EXPORT/SCHEMA/POST_SCHEMA/PROCACT_SCHEMA
DATABASE_EXPORT/AUDIT_UNIFIED/AUDIT_POLICY
DATABASE_EXPORT/AUDIT_UNIFIED/AUDIT_POLICY_ENABLE
Processing object type DATABASE_EXPORT/AUDIT
DATABASE_EXPORT/POST_SYSTEM_IMPCALLOUT/MARKER
. . exported "SYS"."KU$_USER_MAPPING_VIEW"
6.218
KB
50 rows
. . exported "ORDDATA"."ORDDCM_DOCS"
252.9
KB
9 rows
. . exported "SYS"."AUD$"
25.18
KB
24 rows
. . exported "LBACSYS"."OLS$AUDIT_ACTIONS"
5.734
KB
8 rows
. . exported "LBACSYS"."OLS$DIP_EVENTS"
5.515
KB
2 rows
. . exported "LBACSYS"."OLS$INSTALLATIONS"
6.937
KB
2 rows
. . exported "LBACSYS"."OLS$PROPS"
6.210
KB
5 rows
. . exported "SYS"."DAM_CONFIG_PARAM$"
6.507
KB
14 rows
. . exported "SYS"."TSDP_PARAMETER$"
5.929
KB
1 rows
. . exported "SYS"."TSDP_POLICY$"
5.898
KB
1 rows
. . exported "SYS"."TSDP_SUBPOL$"
6.304
KB
1 rows
. . exported "SYSTEM"."REDO_DB"
23
KB
1 rows
. . exported "WMSYS"."WM$ENV_VARS$"
6.054
KB
5 rows
. . exported "WMSYS"."WM$EVENTS_INFO$"
5.789
KB
12 rows
. . exported "WMSYS"."WM$HINT_TABLE$"
9.429
KB
75 rows
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
b
lo den
g
@ Stu
o
f
(in this
y
og use
l
o
hn se to
c
e
T cen
n
o
li
ti
e
a
l
rm erab
o
f
In ansf
l
a
b
tr
Glo non-
a
. .
KB
. .
KB
. .
KB
. .
KB
. .
KB
. .
KB
. .
KB
. .
KB
. .
KB
. .
KB
. .
KB
. .
KB
. .
KB
. .
KB
. .
KB
. .
KB
. .
KB
. .
KB
. .
KB
. .
KB
. .
KB
. .
KB
. .
KB
exported "WMSYS"."WM$NEXTVER_TABLE$"
1 rows
exported "WMSYS"."WM$VERSION_HIERARCHY_TABLE$"
1 rows
exported "WMSYS"."WM$WORKSPACES_TABLE$"
1 rows
exported "WMSYS"."WM$WORKSPACE_PRIV_TABLE$"
8 rows
exported "LBACSYS"."OLS$AUDIT"
0 rows
exported "LBACSYS"."OLS$COMPARTMENTS"
0 rows
exported "LBACSYS"."OLS$DIP_DEBUG"
0 rows
exported "LBACSYS"."OLS$GROUPS"
0 rows
exported "LBACSYS"."OLS$LAB"
0 rows
exported "LBACSYS"."OLS$LEVELS"
0 rows
exported "LBACSYS"."OLS$POL"
0 rows
exported "LBACSYS"."OLS$POLICY_ADMIN"
0 rows
exported "LBACSYS"."OLS$POLS"
0 rows
exported "LBACSYS"."OLS$POLT"
0 rows
exported "LBACSYS"."OLS$PROFILE"
0 rows
exported "LBACSYS"."OLS$PROFILES"
0 rows
exported "LBACSYS"."OLS$PROG"
0 rows
exported "LBACSYS"."OLS$SESSINFO"
0 rows
exported "LBACSYS"."OLS$USER"
0 rows
exported "LBACSYS"."OLS$USER_COMPARTMENTS"
0 rows
exported "LBACSYS"."OLS$USER_GROUPS"
0 rows
exported "LBACSYS"."OLS$USER_LEVELS"
0 rows
exported "SYS"."DAM_CLEANUP_EVENTS$"
0 rows
6.351
5.960
12.08
6.539
0
0
0
0
s
) ha
0
om ฺ 0
c
ฺ
ch ide
e
t
i
l- t Gu
0
a
b
n
o
l
g tude
0
@
o is S
f
n
i
(
th
y
0
g
e
s
o
l
u
o
hn se to
c
0
e
T cen
n
tio le li
0
a
b
m
r
a
fo sfer
n
I
0
l
n
a
a
r
b
t
Glo non0
0
0
0
0
0
0
a
. .
KB
. .
KB
. .
KB
. .
KB
. .
KB
. .
KB
. .
KB
. .
KB
. .
KB
. .
KB
. .
KB
. .
KB
. .
KB
. .
KB
. .
KB
. .
KB
. .
KB
. .
KB
. .
KB
. .
KB
. .
KB
. .
KB
. .
KB
exported "SYS"."DAM_CLEANUP_JOBS$"
0 rows
exported "SYS"."TSDP_ASSOCIATION$"
0 rows
exported "SYS"."TSDP_CONDITION$"
0 rows
exported "SYS"."TSDP_FEATURE_POLICY$"
0 rows
exported "SYS"."TSDP_PROTECTION$"
0 rows
exported "SYS"."TSDP_SENSITIVE_DATA$"
0 rows
exported "SYS"."TSDP_SENSITIVE_TYPE$"
0 rows
exported "SYS"."TSDP_SOURCE$"
0 rows
exported "SYSTEM"."REDO_LOG"
0 rows
exported "WMSYS"."WM$BATCH_COMPRESSIBLE_TABLES$"
0 rows
exported "WMSYS"."WM$CONSTRAINTS_TABLE$"
0 rows
exported "WMSYS"."WM$CONS_COLUMNS$"
0 rows
exported "WMSYS"."WM$LOCKROWS_INFO$"
0 rows
exported "WMSYS"."WM$MODIFIED_TABLES$"
0 rows
exported "WMSYS"."WM$MP_GRAPH_WORKSPACES_TABLE$"
0 rows
exported "WMSYS"."WM$MP_PARENT_WORKSPACES_TABLE$"
0 rows
exported "WMSYS"."WM$NESTED_COLUMNS_TABLE$"
0 rows
exported "WMSYS"."WM$REMOVED_WORKSPACES_TABLE$"
0 rows
exported "WMSYS"."WM$RESOLVE_WORKSPACES_TABLE$"
0 rows
exported "WMSYS"."WM$RIC_LOCKING_TABLE$"
0 rows
exported "WMSYS"."WM$RIC_TABLE$"
0 rows
exported "WMSYS"."WM$RIC_TRIGGERS_TABLE$"
0 rows
exported "WMSYS"."WM$UDTRIG_DISPATCH_PROCS$"
0 rows
0
0
0
0
0
0
0
0
s
) ha
0
om ฺ 0
c
ฺ
ch ide
e
t
i
l- t Gu
0
a
b
n
o
l
g tude
0
@
o is S
f
n
i
(
th
y
0
g
e
s
o
l
u
o
hn se to
c
0
e
T cen
n
tio le li
0
a
b
m
r
a
fo sfer
n
I
0
l
n
a
a
r
b
t
Glo non0
0
0
0
0
0
0
a
. . exported "WMSYS"."WM$UDTRIG_INFO$"
0
KB
0 rows
. . exported "WMSYS"."WM$VERSION_TABLE$"
0
KB
0 rows
. . exported "WMSYS"."WM$VT_ERRORS_TABLE$"
0
KB
0 rows
. . exported "WMSYS"."WM$WORKSPACE_SAVEPOINTS_TABLE$"
0
KB
0 rows
. . exported "SYSTEM"."SCHEDULER_PROGRAM_ARGS"
9.484
KB
12 rows
. . exported "SYS"."AUDTAB$TBS$FOR_EXPORT"
5.929
KB
2 rows
. . exported "WMSYS"."WM$EXP_MAP"
7.695
KB
3 rows
. . exported "SYS"."DBA_SENSITIVE_DATA"
0
KB
0 rows
. . exported "SYS"."DBA_TSDP_POLICY_PROTECTION"
0
KB
0 rows
. . exported "SYS"."FGA_LOG$FOR_EXPORT"
0
KB
0 rows
. . exported "SYS"."NACL$_HOST_EXP"
0
KB
0 rows
. . exported "SYS"."NACL$_WALLET_EXP"
0
KB
0 rows
. . exported "SYSTEM"."SCHEDULER_JOB_ARGS"
0
KB
0 rows
Master table "SYSTEM"."SYS_EXPORT_FULL_01" successfully
loaded/unloaded
****************************************************************
*
Dump file set for SYSTEM.SYS_EXPORT_FULL_01 is:
/u01/app/oracle/admin/orcl/dpdump/expfull.dmp
****************************************************************
*
Datafiles required for transportable tablespace EXAMPLE:
Datafiles required for transportable tablespace TEST:
Datafiles required for transportable tablespace USERS:
Job "SYSTEM"."SYS_EXPORT_FULL_01" successfully completed at Mon
Sep 10 05:40:45 2012 elapsed 0 00:09:40
$
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
b
lo den
g
@ Stu
o
f
(in this
y
og use
l
o
hn se to
c
e
T cen
n
o
li
ti
e
a
l
rm erab
o
f
In ansf
l
a
b
tr
Glo non-
4.
View the log file exp.log to get the list of data files to be transported before the full
transportable import.
a. Find the exp.log file.
a
$ cd /u01/app/oracle/admin/orcl/dpdump
$ ls –ltr exp*
-rw-r--r-- 1 oracle oinstall
1624 Sep 9 23:52 export.log
-rw-r----- 1 oracle oinstall 6012928 Sep 10 05:40 expfull.dmp
-rw-r--r-- 1 oracle oinstall
12605 Sep 10 05:40 exp.log
$
b.
View the last lines of the exp.log file.
$ tail -20 exp.log
. . exported "SYS"."DBA_SENSITIVE_DATA"
0
KB
0 rows
. . exported "SYS"."DBA_TSDP_POLICY_PROTECTION"
0
KB
0 rows
. . exported "SYS"."FGA_LOG$FOR_EXPORT"
0
KB
0 rows
. . exported "SYS"."NACL$_HOST_EXP"
0
KB
0 rows
. . exported "SYS"."NACL$_WALLET_EXP"
0
KB
0 rows
. . exported "SYSTEM"."SCHEDULER_JOB_ARGS"
0
KB
0 rows
Master table "SYSTEM"."SYS_EXPORT_FULL_01" successfully
loaded/unloaded
****************************************************************
*
Dump file set for SYSTEM.SYS_EXPORT_FULL_01 is:
/u01/app/oracle/admin/orcl/dpdump/expfull.dmp
****************************************************************
*
Datafiles required for transportable tablespace EXAMPLE:
Datafiles required for transportable tablespace TEST:
Datafiles required for transportable tablespace USERS:
Job "SYSTEM"."SYS_EXPORT_FULL_01" successfully completed at Mon
Sep 10 05:40:45 2012 elapsed 0 00:09:40
$
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
b
lo den
g
@ Stu
o
f
(in this
y
og use
l
o
hn se to
c
e
T cen
n
o
li
ti
e
a
l
rm erab
o
f
In ansf
l
a
b
tr
Glo non-
5.
After the orcl3 database is created, you can copy the data files to the target locations
/u01/app/oracle/oradata/orcl3 and the export dump file to
/u01/app/oracle/admin/orcl3/dpdump. Before proceeding, check that there are not
any tablespaces in the target orcl3 database having the same names as the tablespaces
in the source orcl database.
a.
Set your environment to the target database orcl3.
$ . oraenv
a
ORACLE_SID = [cdb2] ? orcl3
Connected to:
Testing options
SQL>
b.
Select the tablespace names.
SQL> SELECT tablespace_name FROM dba_tablespaces;
TABLESPACE_NAME
-----------------------------SYSTEM
SYSAUX
UNDOTBS1
TEMP
USERS
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
b
lo den
g
@ Stu
o
f
(in this
y
og use
l
o
SQL>
hn se to
c
e
T cetonUSERS_NEW and the data file
c. Rename the USERS
tablespace
n
o
li
/u01/app/oracle/oradata/orcl3/users01.dbf
to
ti
e
a
l
b
m
/u01/app/oracle/oradata/orcl3/users_new01.dbf.
r
ra
o
f
e
f
n
I ALTER
lSQL>
ns TABLESPACE users RENAME TO users_new;
a
a
r
b
t
Glo nTablespace
onaltered.
SQL> ALTER TABLESPACE users_new OFFLINE;
Tablespace altered.
SQL> EXIT
$
$ mv /u01/app/oracle/oradata/orcl3/users01.dbf
/u01/app/oracle/oradata/orcl3/users_new01.dbf
$
Connected to:
a
Testing options
SQL> ALTER DATABASE RENAME FILE
'/u01/app/oracle/oradata/orcl3/users01.dbf' TO
'/u01/app/oracle/oradata/orcl3/users_new01.dbf';
Database altered.
SQL> ALTER TABLESPACE users_new ONLINE;
Tablespace altered.
s
) ha
SQL> SELECT tablespace_name FROM dba_tablespaces ORDER BY 1;
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
b
lo den
g
@ Stu
o
f
(in this
y
og use
l
o
hn se to
c
e
T cen
SQL> EXIT
n
o
li
ti
e
$
a
l
b
rm
a
r
o
f
d. Now
you
can
copy
the
data files to the target locations
e
n nsf
I
l
/u01/app/oracle/oradata/orcl3
and the export dump file to
a -tra
b
o
/u01/app/oracle/admin/orcl3/dpdump.
Gl non
$ cp /u01/app/oracle/oradata/orcl/test01.dbf
TABLESPACE_NAME
-----------------------------SYSAUX
SYSTEM
TEMP
UNDOTBS1
USERS_NEW
/u01/app/oracle/oradata/orcl3
$ cp /u01/app/oracle/admin/orcl/dpdump/expfull.dmp
/u01/app/oracle/admin/orcl3/dpdump/expfull.dmp
$
6.
Import the orcl database into the orcl3 database in full transportable mode. There are
many errors due to existing objects in the target orcl3 database. These errors can be
ignored.
$ rm /u01/app/oracle/admin/orcl3/dpdump/import.log
$ impdp system/oracle_4U FULL=Y dumpfile=expfull.dmp
TRANSPORT_DATAFILES='/u01/app/oracle/oradata/orcl3/test01.dbf','
a
/u01/app/oracle/oradata/orcl3/users01.dbf','/u01/app/oracle/orad
ata/orcl3/example01.dbf' logfile=import.log
Connected to: Oracle Database 12c Enterprise Edition Release
Testing options
Master table "SYSTEM"."SYS_IMPORT_FULL_01" successfully
loaded/unloaded
Starting "SYSTEM"."SYS_IMPORT_FULL_01": system/******** FULL=Y
dumpfile=expfull.dmp
TRANSPORT_DATAFILES=/u01/app/oracle/oradata/orcl3/test01.dbf,/u0
1/app/oracle/oradata/orcl3/users01.dbf,/u01/app/oracle/oradata/o
rcl3/example01.dbf logfile=import.log
DATABASE_EXPORT/PRE_SYSTEM_IMPCALLOUT/MARKER
DATABASE_EXPORT/PRE_INSTANCE_IMPCALLOUT/MARKER
Processing object type DATABASE_EXPORT/PLUGTS_FULL/PLUGTS_BLK
Processing object type DATABASE_EXPORT/TABLESPACE
ORA-31684: Object type TABLESPACE:"UNDOTBS1" already exists
ORA-31684: Object type TABLESPACE:"TEMP" already exists
Processing object type DATABASE_EXPORT/PROFILE
ORA-31684: Object type PROFILE:"MONITORING_PROFILE" already
exists
Processing object type DATABASE_EXPORT/SYS_USER/USER
Processing object type DATABASE_EXPORT/SCHEMA/USER
ORA-31684: Object type USER:"OUTLN" already exists
ORA-31684: Object type USER:"OLAPSYS" already exists
ORA-31684: Object type USER:"MDDATA" already exists
ORA-31684: Object type USER:"SPATIAL_WFS_ADMIN_USR" already
exists
ORA-31684: Object type USER:"SPATIAL_CSW_ADMIN_USR" already
exists
ORA-31684: Object type USER:"FLOWS_FILES" already exists
ORA-31684: Object type USER:"APEX_PUBLIC_USER" already exists
ORA-31684: Object type USER:"APEX_040100" already exists
ORA-31684: Object type USER:"SCOTT" already exists
Processing object type DATABASE_EXPORT/ROLE
ORA-31684: Object type ROLE:"SELECT_CATALOG_ROLE" already exists
ORA-31684: Object type ROLE:"EXECUTE_CATALOG_ROLE" already
exists
ORA-31684: Object type ROLE:"DELETE_CATALOG_ROLE" already exists
ORA-31684: Object type ROLE:"CAPTURE_ADMIN" already exists
ORA-31684: Object type ROLE:"CDB_DBA" already exists
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
b
lo den
g
@ Stu
o
f
(in this
y
og use
l
o
hn se to
c
e
T cen
n
o
li
ti
e
a
l
rm erab
o
f
In ansf
l
a
b
tr
Glo non-
a
ORA-31684: Object
ORA-31684: Object
exists
ORA-31684: Object
ORA-31684: Object
exists
ORA-31684: Object
ORA-31684: Object
ORA-31684: Object
ORA-31684: Object
ORA-31684: Object
ORA-31684: Object
ORA-31684: Object
exists
ORA-31684: Object
exists
ORA-31684: Object
exists
ORA-31684: Object
ORA-31684: Object
ORA-31684: Object
ORA-31684: Object
exists
ORA-31684: Object
exists
ORA-31684: Object
ORA-31684: Object
ORA-31684: Object
ORA-31684: Object
ORA-31684: Object
ORA-31684: Object
ORA-31684: Object
ORA-31684: Object
ORA-31684: Object
already exists
ORA-31684: Object
exists
ORA-31684: Object
ORA-31684: Object
ORA-31684: Object
ORA-31684: Object
ORA-31684: Object
ORA-31684: Object
ORA-31684: Object
type ROLE:"DBFS_ROLE" already exists
type ROLE:"AQ_ADMINISTRATOR_ROLE" already
type ROLE:"AQ_USER_ROLE" already exists
type ROLE:"ADM_PARALLEL_EXECUTE_TASK" already
type
type
type
type
type
type
type
ROLE:"PROVISIONER" already exists
ROLE:"XS_RESOURCE" already exists
ROLE:"XS_SESSION_ADMIN" already exists
ROLE:"XS_NSATTR_ADMIN" already exists
ROLE:"XS_CACHE_ADMIN" already exists
ROLE:"GSMUSER_ROLE" already exists
ROLE:"GATHER_SYSTEM_STATISTICS" already
type ROLE:"OPTIMIZER_PROCESSING_RATE" already
has
type ROLE:"RECOVERY_CATALOG_OWNER" already
)
om ฺ
c
ฺ
type ROLE:"EM_EXPRESS_BASIC" already
e
ch exists
e
t
i
uid
- tG
type ROLE:"EM_EXPRESS_ALL" aalready
exists
l
type ROLE:"SCHEDULER_ADMIN"
lob already
en exists
g
d
u
type ROLE:"HS_ADMIN_SELECT_ROLE"
already
o@ is St
f
n
i
(
th
y
g
e
type ROLE:"HS_ADMIN_EXECUTE_ROLE"
already
s
o
l
u
o
to
hnROLE:"HS_ADMIN_ROLE"
c
e
e
type
already exists
s
T cen
n
li ROLE:"GLOBAL_AQ_USER_ROLE" already exists
tio letype
a
rm erab type ROLE:"OEM_ADVISOR" already exists
o
f
type ROLE:"OEM_MONITOR" already exists
In ansf
l
a
type ROLE:"XDBADMIN" already exists
b
tr
Glo nontype ROLE:"XDB_SET_INVOKER" already exists
type ROLE:"AUTHENTICATEDUSER" already exists
type ROLE:"XDB_WEBSERVICES" already exists
type ROLE:"XDB_WEBSERVICES_WITH_PUBLIC"
type ROLE:"XDB_WEBSERVICES_OVER_HTTP" already
type
type
type
type
type
type
type
ROLE:"WM_ADMIN_ROLE" already exists
ROLE:"JAVAUSERPRIV" already exists
ROLE:"JAVAIDPRIV" already exists
ROLE:"JAVASYSPRIV" already exists
ROLE:"JAVADEBUGPRIV" already exists
ROLE:"EJBCLIENT" already exists
ROLE:"JMXSERVER" already exists
a
ORA-31684: Object type ROLE:"JAVA_ADMIN" already exists
ORA-31684: Object type ROLE:"JAVA_DEPLOY" already exists
ORA-31684: Object type ROLE:"CTXAPP" already exists
ORA-31684: Object type ROLE:"ORDADMIN" already exists
ORA-31684: Object type ROLE:"OLAP_XS_ADMIN" already exists
ORA-31684: Object type ROLE:"OLAP_DBA" already exists
ORA-31684: Object type ROLE:"CWM_USER" already exists
ORA-31684: Object type ROLE:"OLAP_USER" already exists
ORA-31684: Object type ROLE:"SPATIAL_WFS_ADMIN" already exists
ORA-31684: Object type ROLE:"WFS_USR_ROLE" already exists
ORA-31684: Object type ROLE:"SPATIAL_CSW_ADMIN" already exists
ORA-31684: Object type ROLE:"CSW_USR_ROLE" already exists
ORA-31684: Object type ROLE:"LBAC_DBA" already exists
ORA-31684: Object type ROLE:"APEX_ADMINISTRATOR_ROLE" already
exists
ORA-31684: Object type ROLE:"APEX_GRANTS_FOR_NEW_USERS_ROLE"
already exists
ORA-31684: Object type ROLE:"DV_REALM_RESOURCE" already exists
ORA-31684: Object type ROLE:"DV_REALM_OWNER" already exists
ORA-31684: Object type ROLE:"DV_ACCTMGR" already exists
ORA-31684: Object type ROLE:"DV_OWNER" already exists
ORA-31684: Object type ROLE:"DV_ADMIN" already exists
ORA-31684: Object type ROLE:"DV_SECANALYST" already exists
ORA-31684: Object type ROLE:"DV_PUBLIC" already exists
ORA-31684: Object type ROLE:"DV_PATCH_ADMIN" already exists
ORA-31684: Object type ROLE:"DV_MONITOR" already exists
ORA-31684: Object type ROLE:"DV_STREAMS_ADMIN" already exists
ORA-31684: Object type ROLE:"DV_GOLDENGATE_ADMIN" already exists
ORA-31684: Object type ROLE:"DV_XSTREAM_ADMIN" already exists
ORA-31684: Object type ROLE:"DV_GOLDENGATE_REDO_ACCESS" already
exists
ORA-31684: Object type ROLE:"DV_AUDIT_CLEANUP" already exists
Processing object type DATABASE_EXPORT/RADM_FPTM
DATABASE_EXPORT/GRANT/SYSTEM_GRANT/PROC_SYSTEM_GRANT
Processing object type DATABASE_EXPORT/SCHEMA/GRANT/SYSTEM_GRANT
Processing object type DATABASE_EXPORT/SCHEMA/ROLE_GRANT
Processing object type DATABASE_EXPORT/SCHEMA/DEFAULT_ROLE
Processing object type DATABASE_EXPORT/SCHEMA/ON_USER_GRANT
Processing object type DATABASE_EXPORT/SCHEMA/TABLESPACE_QUOTA
Processing object type DATABASE_EXPORT/RESOURCE_COST
Processing object type DATABASE_EXPORT/TRUSTED_DB_LINK
Processing object type DATABASE_EXPORT/SCHEMA/SEQUENCE/SEQUENCE
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
b
lo den
g
@ Stu
o
f
(in this
y
og use
l
o
hn se to
c
e
T cen
n
o
li
ti
e
a
l
rm erab
o
f
In ansf
l
a
b
tr
Glo non-
a
Processing object type DATABASE_EXPORT/DIRECTORY/DIRECTORY
DATABASE_EXPORT/DIRECTORY/GRANT/OWNER_GRANT/OBJECT_GRANT
Processing object type DATABASE_EXPORT/SCHEMA/SYNONYM
Processing object type DATABASE_EXPORT/SCHEMA/TYPE/INC_TYPE
Processing object type DATABASE_EXPORT/SCHEMA/TYPE/TYPE_SPEC
DATABASE_EXPORT/SCHEMA/TYPE/GRANT/OWNER_GRANT/OBJECT_GRANT
DATABASE_EXPORT/SYSTEM_PROCOBJACT/PRE_SYSTEM_ACTIONS/PROCACT_SYS
TEM
Processing object type DATABASE_EXPORT/SYSTEM_PROCOBJACT/PROCOBJ
DATABASE_EXPORT/SYSTEM_PROCOBJACT/POST_SYSTEM_ACTIONS/PROCACT_SY
STEM
Processing object type DATABASE_EXPORT/SCHEMA/PROCACT_SCHEMA
DATABASE_EXPORT/EARLY_OPTIONS/VIEWS_AS_TABLES/TABLE
DATABASE_EXPORT/EARLY_OPTIONS/VIEWS_AS_TABLES/TABLE_DATA
. . imported "SYS"."KU$_EXPORT_USER_MAP"
6.132
KB
43 rows
DATABASE_EXPORT/EARLY_POST_INSTANCE_IMPCALLOUT/MARKER
DATABASE_EXPORT/SCHEMA/XMLSCHEMA/XMLSCHEMA
Processing object type DATABASE_EXPORT/NORMAL_OPTIONS/TABLE
Processing object type DATABASE_EXPORT/NORMAL_OPTIONS/TABLE_DATA
. . imported "ORDDATA"."ORDDCM_DOCS_TRANSIENT"
252.9
KB
9 rows
. . imported "SYS"."AMGT$DP$DAM_CONFIG_PARAM$"
6.507
KB
14 rows
. . imported "SYS"."DP$TSDP_PARAMETER$"
5.929
KB
1 rows
. . imported "SYS"."DP$TSDP_POLICY$"
5.898
KB
1 rows
. . imported "SYS"."DP$TSDP_SUBPOL$"
6.304
KB
1 rows
. . imported "SYSTEM"."REDO_DB_TMP"
22.57
KB
1 rows
. . imported "WMSYS"."E$ENV_VARS$"
6.054
KB
5 rows
. . imported "WMSYS"."E$EVENTS_INFO$"
5.789
KB
12 rows
. . imported "WMSYS"."E$HINT_TABLE$"
9.460
KB
76 rows
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
b
lo den
g
@ Stu
o
f
(in this
y
og use
l
o
hn se to
c
e
T cen
n
o
li
ti
e
a
l
rm erab
o
f
In ansf
l
a
b
tr
Glo non-
a
. .
KB
. .
KB
. .
KB
. .
KB
. .
KB
. .
KB
. .
KB
. .
KB
. .
KB
. .
KB
. .
KB
. .
KB
. .
KB
. .
KB
. .
KB
. .
KB
. .
KB
. .
KB
. .
KB
. .
KB
. .
KB
. .
KB
. .
KB
imported "WMSYS"."E$NEXTVER_TABLE$"
1 rows
imported "WMSYS"."E$VERSION_HIERARCHY_TABLE$"
1 rows
imported "WMSYS"."E$WORKSPACES_TABLE$"
1 rows
imported "WMSYS"."E$WORKSPACE_PRIV_TABLE$"
8 rows
imported "LBACSYS"."OLS_DP$OLS$AUDIT"
0 rows
imported "LBACSYS"."OLS_DP$OLS$COMPARTMENTS"
0 rows
imported "LBACSYS"."OLS_DP$OLS$GROUPS"
0 rows
imported "LBACSYS"."OLS_DP$OLS$LAB"
0 rows
imported "LBACSYS"."OLS_DP$OLS$LEVELS"
0 rows
imported "LBACSYS"."OLS_DP$OLS$POL"
0 rows
imported "LBACSYS"."OLS_DP$OLS$POLS"
0 rows
imported "LBACSYS"."OLS_DP$OLS$POLT"
0 rows
imported "LBACSYS"."OLS_DP$OLS$PROFILE"
0 rows
imported "LBACSYS"."OLS_DP$OLS$PROG"
0 rows
imported "LBACSYS"."OLS_DP$OLS$USER"
0 rows
imported "SYS"."AMGT$DP$AUD$"
0 rows
imported "SYS"."AMGT$DP$DAM_CLEANUP_EVENTS$"
0 rows
imported "SYS"."AMGT$DP$DAM_CLEANUP_JOBS$"
0 rows
imported "SYS"."AMGT$DP$FGA_LOG$"
0 rows
imported "SYS"."DP$TSDP_ASSOCIATION$"
0 rows
imported "SYS"."DP$TSDP_CONDITION$"
0 rows
imported "SYS"."DP$TSDP_FEATURE_POLICY$"
0 rows
imported "SYS"."DP$TSDP_PROTECTION$"
0 rows
6.351
5.960
12.08
6.539
0
0
0
0
s
) ha
0
om ฺ 0
c
ฺ
ch ide
e
t
i
l- t Gu
0
a
b
n
o
l
g tude
0
@
o is S
f
n
i
(
th
y
0
g
e
s
o
l
u
o
hn se to
c
0
e
T cen
n
tio le li
0
a
b
m
r
a
fo sfer
n
I
0
l
n
a
a
r
b
t
Glo non0
0
0
0
0
0
0
a
. . imported "SYS"."DP$TSDP_SENSITIVE_DATA$"
KB
0 rows
. . imported "SYS"."DP$TSDP_SENSITIVE_TYPE$"
KB
0 rows
. . imported "SYS"."DP$TSDP_SOURCE$"
KB
0 rows
. . imported "SYSTEM"."REDO_LOG_TMP"
KB
0 rows
. . imported "WMSYS"."E$BATCH_COMPRESSIBLE_TABLES$"
KB
0 rows
. . imported "WMSYS"."E$CONSTRAINTS_TABLE$"
KB
0 rows
. . imported "WMSYS"."E$CONS_COLUMNS$"
KB
0 rows
. . imported "WMSYS"."E$LOCKROWS_INFO$"
KB
0 rows
. . imported "WMSYS"."E$MODIFIED_TABLES$"
KB
0 rows
. . imported "WMSYS"."E$MP_GRAPH_WORKSPACES_TABLE$"
KB
0 rows
. . imported "WMSYS"."E$MP_PARENT_WORKSPACES_TABLE$"
KB
0 rows
. . imported "WMSYS"."E$NESTED_COLUMNS_TABLE$"
KB
0 rows
. . imported "WMSYS"."E$REMOVED_WORKSPACES_TABLE$"
KB
0 rows
. . imported "WMSYS"."E$RESOLVE_WORKSPACES_TABLE$"
KB
0 rows
. . imported "WMSYS"."E$RIC_LOCKING_TABLE$"
KB
0 rows
. . imported "WMSYS"."E$RIC_TABLE$"
KB
0 rows
. . imported "WMSYS"."E$RIC_TRIGGERS_TABLE$"
KB
0 rows
. . imported "WMSYS"."E$UDTRIG_DISPATCH_PROCS$"
KB
0 rows
. . imported "WMSYS"."E$UDTRIG_INFO$"
KB
0 rows
. . imported "WMSYS"."E$VERSION_TABLE$"
KB
0 rows
. . imported "WMSYS"."E$VT_ERRORS_TABLE$"
KB
0 rows
. . imported "WMSYS"."E$WORKSPACE_SAVEPOINTS_TABLE$"
KB
0 rows
DATABASE_EXPORT/NORMAL_OPTIONS/VIEWS_AS_TABLES/TABLE
0
0
0
0
0
0
0
0
s
) ha
0
om ฺ 0
c
ฺ
ch ide
e
t
i
l- t Gu
0
a
b
n
o
l
g tude
0
@
o is S
f
n
i
(
th
y
0
g
e
s
o
l
u
o
hn se to
c
0
e
T cen
n
tio le li
0
a
b
m
r
a
fo sfer
n
I
0
l
n
a
a
r
b
t
Glo non0
0
0
0
0
0
a
DATABASE_EXPORT/NORMAL_OPTIONS/VIEWS_AS_TABLES/TABLE_DATA
. . imported "SYSTEM"."SCHEDULER_PROGRAM_ARGS_TMP"
9.484
KB
12 rows
. . imported "WMSYS"."E$EXP_MAP"
7.695
KB
3 rows
. . imported "SYS"."DP$DBA_SENSITIVE_DATA"
0
KB
0 rows
. . imported "SYS"."DP$DBA_TSDP_POLICY_PROTECTION"
0
KB
0 rows
. . imported "SYS"."NACL$_HOST_IMP"
0
KB
0 rows
. . imported "SYS"."NACL$_NAME_MAP_IMP"
0
KB
0 rows
. . imported "SYS"."NACL$_WALLET_IMP"
0
KB
0 rows
. . imported "SYSTEM"."SCHEDULER_JOB_ARGS_TMP"
0
KB
0 rows
Processing object type DATABASE_EXPORT/NORMAL_OPTIONS/PROCEDURE
ORA-39342: Internal error - failed to import internal objects
tagged with APEX due to ORA-00955: name is already used by an
existing object.
ORA-31684: Object type PROCEDURE:"SYS"."VALIDATE_APEX" already
exists
DATABASE_EXPORT/NORMAL_OPTIONS/OPTION_PACKAGE/PACKAGE_BODY
ORA-31684: Object type PACKAGE_BODY:"SYS"."WWV_DBMS_SQL" already
exists
DATABASE_EXPORT/NORMAL_POST_INSTANCE_IMPCALLOU/MARKER
Processing object type DATABASE_EXPORT/SCHEMA/TABLE/TABLE
ORA-39151: Table "SCOTT"."DEPT" exists. All dependent metadata
and data will be skipped due to table_exists_action of skip
ORA-39151: Table "SCOTT"."EMP" exists. All dependent metadata
ORA-39151: Table "SCOTT"."BONUS" exists. All dependent metadata
ORA-39151: Table "SCOTT"."SALGRADE" exists. All dependent
metadata and data will be skipped due to table_exists_action of
skip
ORA-39083: Object type TABLE:"OE"."PURCHASEORDER" failed to
create with error:
ORA-31061: XDB error: DBMS_XDBZ.ENABLE_HIERARCHY
ORA-06512: at "XDB.DBMS_XDBZ0", line 131
ORA-06512: at "XDB.DBMS_XDBZ0", line 598
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
b
lo den
g
@ Stu
o
f
(in this
y
og use
l
o
hn se to
c
e
T cen
n
o
li
ti
e
a
l
rm erab
o
f
In ansf
l
a
b
tr
Glo non-
a
Failing sql is:
BEGIN DBMS_XDBZ.ENABLE_HIERARCHY('"OE"','"PURCHASEORDER"'); END;
DATABASE_EXPORT/SCHEMA/TABLE/GRANT/OWNER_GRANT/OBJECT_GRANT
Processing object type DATABASE_EXPORT/SCHEMA/TABLE/COMMENT
DATABASE_EXPORT/XS_SECURITY/SCHEMA/XS_SECURITY_CLASS
ORA-39083: Object type XS_SECURITY_CLASS:"SYS" failed to create
with error:
ORA-06550: line 11, column 27:
PLS-00103: Encountered the symbol ";" when expecting one of the
following:
. ( ) , * % & = - + < / > at in is mod remainder not rem =>
<an exponent (**)> <> or != or ~= >= <= <> and or like like2
like4 likec as between from using || multiset member
submultiset
The symbol ")" was substituted for ";" to continue.
Failing sql is:
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
b
lo den
DECLARE
g
@ Stu
o
priv_list
XS$PRIVILEGE_LIST;
f
(in this
BEGIN
y
og use
l
o
hn se to
priv_lis
c
e
n
T typeceDATABASE_EXPORT/SCHEMA/FUNCTION/FUNCTION
Processing object
n
i
o
l
i
tobject
Processing
a
letype
b
m
r
a
DATABASE_EXPORT/SCHEMA/PROCEDURE/PROCEDURE
fo sfobject
er type
n
I
Processing
alDATABASE_EXPORT/SCHEMA/FUNCTION/ALTER_FUNCTION
an
r
b
t
o
Gl nProcessing
on
object type
DATABASE_EXPORT/SCHEMA/PROCEDURE/ALTER_PROCEDURE
Processing object type DATABASE_EXPORT/SCHEMA/TABLE/INDEX/INDEX
DATABASE_EXPORT/SCHEMA/TABLE/INDEX/FUNCTIONAL_INDEX/INDEX
DATABASE_EXPORT/SCHEMA/TABLE/CONSTRAINT/CONSTRAINT
DATABASE_EXPORT/SCHEMA/TABLE/INDEX/STATISTICS/INDEX_STATISTICS
DATABASE_EXPORT/SCHEMA/TABLE/INDEX/STATISTICS/FUNCTIONAL_INDEX/I
NDEX_STATISTICS
Processing object type DATABASE_EXPORT/SCHEMA/VIEW/VIEW
DATABASE_EXPORT/SCHEMA/VIEW/GRANT/OWNER_GRANT/OBJECT_GRANT
a
Processing object type DATABASE_EXPORT/SCHEMA/TYPE/TYPE_BODY
DATABASE_EXPORT/SCHEMA/TABLE/CONSTRAINT/REF_CONSTRAINT
DATABASE_EXPORT/SCHEMA/TABLE/INDEX/BITMAP_INDEX/INDEX
DATABASE_EXPORT/SCHEMA/TABLE/INDEX/STATISTICS/BITMAP_INDEX/INDEX
_STATISTICS
DATABASE_EXPORT/SCHEMA/TABLE/STATISTICS/TABLE_STATISTICS
Processing object type DATABASE_EXPORT/STATISTICS/MARKER
OE.ACTION_TABLE_MEMBERS : sqlerrm = ORA-20000: Unable to set
values for index ACTION_TABLE_MEMBERS: does not exist or
insufficient privileges
OE.LINEITEM_TABLE_MEMBERS : sqlerrm = ORA-20000: Unable to set
values for index LINEITEM_TABLE_MEMBERS: does not exist or
insufficient privileges
Importing statistics failed for 2 object(s);
DATABASE_EXPORT/SCHEMA/TABLE/INDEX/DOMAIN_INDEX/INDEX
Processing object type DATABASE_EXPORT/SCHEMA/TABLE/TRIGGER
Processing object type DATABASE_EXPORT/SCHEMA/VIEW/TRIGGER
Processing object type DATABASE_EXPORT/SCHEMA/MATERIALIZED_VIEW
Processing object type DATABASE_EXPORT/SCHEMA/DIMENSION
Processing object type DATABASE_EXPORT/END_PLUGTS_BLK
DATABASE_EXPORT/FINAL_POST_INSTANCE_IMPCALLOUT/MARKER
DATABASE_EXPORT/SCHEMA/TABLE/POST_INSTANCE/PROCACT_INSTANCE
DATABASE_EXPORT/SCHEMA/TABLE/POST_INSTANCE/PROCDEPOBJ
DATABASE_EXPORT/SCHEMA/POST_SCHEMA/PROCOBJ
ORA-39083: Object type
PROCOBJ:"APEX_040100"."ORACLE_APEX_PURGE_SESSIONS" failed to
create with error:
ORA-27477: "APEX_040100"."ORACLE_APEX_PURGE_SESSIONS" already
exists
Failing sql is:
BEGIN
dbms_scheduler.create_job('"ORACLE_APEX_PURGE_SESSIONS"',
job_type=>'STORED_PROCEDURE', job_action=>
'WWV_FLOW_CACHE.PURGE_SESSIONS'
, number_of_arguments=>0,
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
b
lo den
g
@ Stu
o
f
(in this
y
og use
l
o
hn se to
c
e
T cen
n
o
li
ti
e
a
l
rm erab
o
f
In ansf
l
a
b
tr
Glo non-
a
start_date=>TO_TIMESTAMP_TZ('04-JUL-2012 11.31.16.846009000 PM 07:00','DD-MON-RRRR HH.MI.SSXFF AM
TZR','NLS_DATE_LANGUAGE=english'), repeat_interval=>
'FREQ
PROCOBJ:"APEX_040100"."ORACLE_APEX_MAIL_QUEUE" failed to create
with error:
ORA-27477: "APEX_040100"."ORACLE_APEX_MAIL_QUEUE" already exists
Failing sql is:
BEGIN
dbms_scheduler.create_job('"ORACLE_APEX_MAIL_QUEUE"',
'WWV_FLOW_MAIL.PUSH_QUEUE_IMMEDIATE'
TZR','NLS_DATE_LANGUAGE=english'), repeat_interval=>
'FREQ=MINUTE
PROCOBJ:"APEX_040100"."ORACLE_APEX_WS_NOTIFICATIONS" failed to
create with error:
ORA-27477: "APEX_040100"."ORACLE_APEX_WS_NOTIFICATIONS" already
exists
Failing sql is:
BEGIN
dbms_scheduler.create_job('"ORACLE_APEX_WS_NOTIFICATIONS"',
'WWV_FLOW_WORKSHEET_API.DO_NOTIFY'
TZR','NLS_DATE_LANGUAGE=english'), repeat_interval
PROCOBJ:"APEX_040100"."ORACLE_APEX_DAILY_MAINTENANCE" failed to
create with error:
ORA-27477: "APEX_040100"."ORACLE_APEX_DAILY_MAINTENANCE" already
exists
Failing sql is:
BEGIN
dbms_scheduler.create_job('"ORACLE_APEX_DAILY_MAINTENANCE"',
'WWV_FLOW_MAINT.DAILY_MAINTENANCE'
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
b
lo den
g
@ Stu
o
f
(in this
y
og use
l
o
hn se to
c
e
T cen
n
o
li
ti
e
a
l
rm erab
o
f
In ansf
l
a
b
tr
Glo non-
a
TZR','NLS_DATE_LANGUAGE=english'), repeat_inter
DATABASE_EXPORT/SCHEMA/POST_SCHEMA/PROCACT_SCHEMA
DATABASE_EXPORT/AUDIT_UNIFIED/AUDIT_POLICY_ENABLE
Processing object type DATABASE_EXPORT/AUDIT
DATABASE_EXPORT/POST_SYSTEM_IMPCALLOUT/MARKER
Job "SYSTEM"."SYS_IMPORT_FULL_01" completed with 97 error(s) at
Tue Aug 21 09:59:05 2012 elapsed 0 00:04:44
$
7.
Check in the target orcl3 database that the tablespaces TEST, EXAMPLE, and USERS
have been plugged and that the HR.TESTTAB table contains two rows as in the source
orcl database.
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
Connected to:
l- t Gu
a
b
lo d12.1.0.0.2
en
g
64bit Production
u
o@ isandStReal Application
f
n
Mining
i
(
th
y
Testing options
g
e
lo o us
o
n
t dba_tablespaces;
h seFROM
c
SQL> SELECT tablespace_name
e
T cen
n
o
li
ti
e
a
l
TABLESPACE_NAME
rm erab
o
f
-----------------------------In ansf
l
a
SYSTEM
b n-tr
Glo nSYSAUX
o
UNDOTBS1
TEMP
USERS_NEW
EXAMPLE
TEST
USERS
8 rows selected.
SQL> SELECT name FROM v$datafile;
NAME
--------------------------------------------------------------Copyright © 2013, Oracle and/or its affiliates. All rights reserved.
a
/u01/app/oracle/oradata/orcl3/system01.dbf
/u01/app/oracle/oradata/orcl3/example01.dbf
/u01/app/oracle/oradata/orcl3/sysaux01.dbf
/u01/app/oracle/oradata/orcl3/undotbs01.dbf
/u01/app/oracle/oradata/orcl3/test01.dbf
/u01/app/oracle/oradata/orcl3/users_new01.dbf
/u01/app/oracle/oradata/orcl3/users01.dbf
7 rows selected.
SQL> SELECT * FROM hr.testtab;
ID
---------10
20
LABEL
---------Skirt
Trousers
s
) ha
om ฺ
c
ฺ
SQL> EXIT
ch ide
e
t
i
$
l- t Gu
a
b
n
lo backdineread-write
8. Put the user-defined tablespaces in the source database orcl
mode in
g
u
t
@
order to let users work.
nfo this S
i
(
$ . oraenv
ogy use
l
o
to with value /u01/app/oracle
hn unchanged
The Oracle base remains
c
e
e
s
T cen
n
o
li
$ sqlplus a/tias sysdba
e
l
rm erab
o
f
f
In ansto:
l
Connected
a
b n-tr Database 12c Enterprise Edition Release 12.1.0.0.2 Glo nOracle
o
64bit Production
Testing options
SQL> ALTER TABLESPACE example READ WRITE;
Tablespace altered.
SQL> ALTER TABLESPACE test READ WRITE;
Tablespace altered.
SQL> ALTER TABLESPACE users
READ WRITE;
a
Tablespace altered.
SQL> EXIT
$
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
b
lo den
g
@ Stu
o
f
(in this
y
og use
l
o
hn se to
c
e
T cen
n
o
li
ti
e
a
l
rm erab
o
f
In ansf
l
a
b
tr
Glo non-
a
Practice 20-3: Loading Data Using SQL*Loader Express Mode
(Optional)
Overview
In this practice, you will load records from an emp.dat file into the HR.TAB1 table using
SQL*Loader in Express Mode.
Tasks
1.
Make sure you are in the ~/labs/Load directory and your environment points to the orcl
instance.
$ cd ~/labs/Load
$ . oraenv
$
2.
Create an HR.EMP table as follows.
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
Connected to:
a
b
Release
lo d12.1.0.0.2
en
u
64bit Production
o@ isandStReal Application
f
n
i
Mining
(
th
y
Testing options
g
e
lo o us
o
n
t
e
ech ePURGE;
SQL> DROP TABLE T
hr.tab1
s
n
n
c
i
DROP TABLE thr.tab1
PURGE
o
l
i
e
a
* bl
m
r
a
foat line
er1:
f
ERROR
n
I
s
alORA-00942:
an table or view does not exist
r
b
t
o
Gl non
SQL> CREATE TABLE hr.tab1 (id NUMBER, prod_name VARCHAR2(10));
Table created.
SQL> INSERT INTO hr.tab1 VALUES (10, 'Skirt');
1 row created.
SQL> INSERT INTO hr.tab1 VALUES (20, 'Trousers');
1 row created.
SQL> COMMIT;
a
Commit complete.
SQL> EXIT
$
3.
Display the $HOME/labs/Load/tab1.dat file. It contains 5 records.
$ more tab1.dat
30, Shirt
40, Socks
50, Cap
60, Gloves
70, Tie
$
4.
Load the five records into the HR.TAB1 table using SQL*Loader in Express Mode.
$ sqlldr system/oracle_4U TABLE=hr.tab1
SQL*Loader: Release 12.1.0.0.2 - Production on Wed Aug 22
08:31:01 2012
s
) ha
om ฺ
c
ฺ
ch idAlle
e
t
i
l- t Gu
rights reserved.
a
b
lo den
g
tu
Express Mode Load, Table: HR.TAB1 fo@
S
n this
(iDEGREE_OF_PARALLELISM=AUTO
Path used:
External Table,
y
og use
l
o
hn se to
Table HR.TAB1:
c
e
n
T cloaded.
e
5 Rows successfully
n
i
o
l
ti
a
le
b
m
r
a
Check
fothe slog
erfiles:
f
n
I
al hr.log
an
r
b
t
o
n
Gl nohr_%p.log_xt
for more information about the load.
$
5.
Verify the existence of the log files.
$ ls -l hr*
-rw-r--r-- 1 oracle oinstall 1036 Aug 22 08:31 hr_782.log_xt
-rw-r--r-- 1 oracle oinstall 2241 Aug 22 08:31 hr.log
$
6.
View the hr.log file.
$ more hr.log
SQL*Loader: Release 12.1.0.0.2 - Production on Wed Aug 22
08:31:01 2012
a
rights reserved.
All
Express Mode Load, Table: HR.TAB1
Data File:
tab1.dat
Bad File:
tab1.bad
Discard File: none specified
(Allow all discards)
Number to load:
Number to skip:
Errors allowed:
Continuation:
Path used:
ALL
0
50
none specified
External Table
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
u
al- nt G
Column Name
Position lob
Len Term
Encl
g tude
Datatype
@
S ---- ---- ----------------------------------- ---------nfo this ----i
(
--------------ogy useFIRST
l
ID
*
,
o
n
o
t
h
CHARACTER
ec ense
T
PROD_NAME
NEXT
*
,
n
c
i
o
l
i
t
CHARACTER a
le
b
m
r
a
fo scontrol
er file for possible reuse:
f
n
I
Generated
alOPTIONS(EXTERNAL_TABLE=EXECUTE,
an
r
b
t
TRIM=LRTRIM)
o
Gl nLOAD
on DATA
Table HR.TAB1, loaded from every logical record.
Insert option in effect for this table: APPEND
INFILE '(null)'
APPEND
INTO TABLE HR.TAB1
FIELDS TERMINATED BY ","
(
ID,
PROD_NAME
)
End of generated control file for possible reuse.
created temporary directory object SYS_SQLLDR_XT_TMPDIR_00000
for path /home/oracle/labs/Load
a
enable parallel DML: ALTER SESSION ENABLE PARALLEL DML
creating external table "SYS_SQLLDR_X_EXT_TAB1"
CREATE TABLE "SYS_SQLLDR_X_EXT_TAB1"
(
"ID" NUMBER,
"PROD_NAME" VARCHAR2(10)
)
ORGANIZATION external
(
TYPE oracle_loader
DEFAULT DIRECTORY SYS_SQLLDR_XT_TMPDIR_00000
ACCESS PARAMETERS
(
RECORDS DELIMITED BY NEWLINE CHARACTERSET US7ASCII
BADFILE 'SYS_SQLLDR_XT_TMPDIR_00000':'tab1.bad'
LOGFILE 'hr_%p.log_xt'
READSIZE 1048576
FIELDS TERMINATED BY "," LRTRIM
REJECT ROWS WITH ALL NULL FIELDS
(
"ID" CHAR(255),
"PROD_NAME" CHAR(255)
)
)
location
(
'tab1.dat'
)
)REJECT LIMIT UNLIMITED
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
b
lo den
g
@ Stu
o
f
(in this
y
og use
l
o
hn se to
c
e
T cen
n
o
li
ti
e
a
l
rm erab
o
f
In ansf
l
a
b
tr
Glo non-
executing INSERT statement to load database table HR.TAB1
INSERT /*+ append parallel(auto) */ INTO HR.TAB1
(
ID,
PROD_NAME
)
SELECT
"ID",
a
"PROD_NAME"
FROM "SYS_SQLLDR_X_EXT_TAB1"
dropping external table "SYS_SQLLDR_X_EXT_TAB1"
Table HR.TAB1:
5 Rows successfully loaded.
Run began on Wed Aug 22 08:31:01 2012
Run ended on Wed Aug 22 08:31:02 2012
Elapsed time was:
CPU time was:
$
7.
00:00:00.58
00:00:00.01
View the hr_782.log_xt file.
$ more hr_782.log_xt
s
) ha
om ฺ
c
ฺ
ch ide
LOG file opened at 08/22/12 08:31:01
e
t
i
l- t Gu
a
b
lo den
Field Definitions for table SYS_SQLLDR_X_EXT_TAB1
g
@ Stu
o
Record format DELIMITED BY NEWLINE
f
is platform
(in as tthe
h
Data in file has same endianness
y
se
ogfields
l
u
Reject rows with all null
o
hn se to
c
e
n
TSource:
e
Fields in Data
n
c
i
o
l
ti
a
le
b
m
r
a
o sfer
CHAR (255)
fID
n
I
l
n
Terminated
by
","
a
ba n-trTrim
o
l
whitespace from left and right
G no
PROD_NAME
CHAR (255)
Terminated by ","
Trim whitespace from left and right
LOG file opened at 08/22/12 08:31:01
KUP-05004:
Warning: Intra source concurrency disabled because
parallel select was not request
ed.
Field Definitions for table SYS_SQLLDR_X_EXT_TAB1
Record format DELIMITED BY NEWLINE
a
Data in file has same endianness as the platform
Reject rows with all null fields
Fields in Data Source:
ID
CHAR (255)
Terminated by ","
PROD_NAME
CHAR (255)
Terminated by ","
$
8.
Verify that the records have been inserted into the HR.TAB1 table.
s
) ha
Connected to:
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
b
lo den
g
@ Stu
o
f
SQL> SELECT * FROM hr.tab1;
(in this
y
og use
l
o
to
ID PROD_NAME hn
c
e
e
s
---------- ---------T cen
n
o
li
i
10
tSkirt
e
a
l
b
rm20 Trousers
a
r
o
f
e
In an30sf Shirt
l
a
b
tr
Socks
Glo non- 40
50 Cap
60
70
Gloves
Tie
SQL>
9.
Drop the HR.TAB1 table.
SQL> DROP TABLE hr.tab1 PURGE;
Table dropped.
SQL> EXIT
$
a
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
b
lo den
g
@ Stu
o
f
(in this
y
og use
l
o
hn se to
c
e
T cen
n
o
li
ti
e
a
l
rm erab
o
f
In ansf
l
a
b
tr
Glo non-
a
s
) ha
om ฺ
c
ฺ
ch21: ide
e
t
i
l- t Gu
Partitioning Enhancements
a
b
glo tuden
Chapter 21 @
nfo this S
i
(
ogy use
l
o
hn se to
c
e
T cen
n
o
li
ti
e
a
l
rm erab
o
f
In ansf
l
a
b
tr
Glo non-
Practices for Lesson 21: Partitioning Enhancements
Chapter 21 - Page 1
a
Practices Overview
In this practice, you will familiarize yourself with using partial local and global indexes.
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
b
lo den
g
@ Stu
o
f
(in this
y
og use
l
o
hn se to
c
e
T cen
n
o
li
ti
e
a
l
rm erab
o
f
In ansf
l
a
b
tr
Glo non-
Chapter 21 - Page 2
a
Practice 21-1: Local and Global Partial Indexing on Partitioned Tables
Overview
In this practice, you will create a partitioned table with five partitions: A local partitioned index
indexing only two partitions of the table and therefore composed of three index partitions, and a
global index indexing the rows of only two partitions of the table.
Tasks
1.
Create the partitioned table HR.TAB_PART1 with five partitions and only three local index
partitions.
a. Connect to the source database orcl.
$ . oraenv
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
b
lo den
g
@ Stu
o
f
(in this
y
SQL>
og use
l
o
to and indexes are created without
hntables,
b. To be sure that the segments,
partitions
c
e
e
s
inserting rows, set theT
deferred_segment_creation
parameter to FALSE.
n
e
n
c
i
o
l
i
tSYSTEM
SQL> ALTER
a
leSET deferred_segment_creation=FALSE;
b
m
r
a
fo sfer
n
I
System
altered.
l
n
a
a
r
b
t
o
Gl nSQL>
on
Connected to:
Testing options
c.
Execute the CREATE TABLE statement as follows.
CREATE TABLE hr.tab_part1
(
order_id NUMBER(12),
order_date DATE CONSTRAINT order_date_nn NOT NULL,
order_mode VARCHAR2(8),
customer_id NUMBER(6) CONSTRAINT order_cust_id_nn NOT NULL,
order_status NUMBER(2),
order_total NUMBER(8,2),
sales_rep_id NUMBER(6),
promotion_id NUMBER(6),
Chapter 21 - Page 3
a
CONSTRAINT order_mode_lov CHECK (order_mode in
('direct','online')),
CONSTRAINT order_total_min CHECK (order_total >= 0)
)
INDEXING OFF
PARTITION BY RANGE (ORDER_DATE)
(PARTITION ord_p1 VALUES LESS THAN (TO_DATE('01-MAR-1999','DDMON-YYYY')) INDEXING ON,
PARTITION ord_p2 VALUES LESS THAN (TO_DATE('01-JUL-1999','DDMON-YYYY')) INDEXING OFF,
PARTITION ord_p3 VALUES LESS THAN (TO_DATE('01-OCT-1999','DDMON-YYYY')) INDEXING ON,
PARTITION ord_p4 VALUES LESS THAN (TO_DATE('01-MAR-2000','DDMON-YYYY')),
PARTITION ord_p5 VALUES LESS THAN (TO_DATE('01-MAR-2010','DDMON-YYYY')))
/
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
DROP TABLE hr.tab_part1 PURGE
l- t Gu
a
b
*
lo den
g
ERROR at line 1:
@ Stu
o
f
is
ORA-00942: table or view does not
(in exist
h
t
y
og use
l
o
SQL> CREATE TABLE hr.tab_part1
hn se to
c
e
(
T cen
n
o
li
order_id NUMBER(12),
ti
e
a
l
bCONSTRAINT order_date_nn NOT NULL,
order_date
rm eDATE
a
r
o
f
order_mode
In ansf VARCHAR2(8),
l
a
b customer_id
NUMBER(6) CONSTRAINT order_cust_id_nn NOT NULL,
n-tr
Glo noorder_status
NUMBER(2),
SQL> DROP TABLE hr.tab_part1 PURGE;
order_total NUMBER(8,2),
sales_rep_id NUMBER(6),
promotion_id NUMBER(6),
CONSTRAINT order_mode_lov CHECK (order_mode in
('direct','online')),
CONSTRAINT order_total_min CHECK (order_total >= 0)
)
INDEXING OFF
PARTITION BY RANGE (ORDER_DATE)
(PARTITION ord_p1 VALUES LESS THAN (TO_DATE('01-MAR-1999','DDMON-YYYY')) INDEXING ON,
PARTITION ord_p2 VALUES LESS THAN (TO_DATE('01-JUL-1999','DDMON-YYYY')) INDEXING OFF,
Chapter 21 - Page 4
a
PARTITION ord_p3 VALUES LESS THAN (TO_DATE('01-OCT-1999','DDMON-YYYY')) INDEXING ON,
PARTITION ord_p4 VALUES LESS THAN (TO_DATE('01-MAR-2000','DDMON-YYYY')),
PARTITION ord_p5 VALUES LESS THAN (TO_DATE('01-MAR-2010','DDMON-YYYY')))
/
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
Table created.
SQL>
2.
Check the default indexing value of the table created.
SQL> SELECT def_indexing FROM dba_part_tables
2 WHERE table_name='TAB_PART1';
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
b
lo den
g
SQL>
@ Stu
o
f
3. Create a partial global index as follows.
(in this
y
SQL> CREATE INDEX hr.tab_part1_gidx_ordermode
og use
l
o
ON hr.tab_part1
to
hn se (order_mode)
c
e
GLOBAL
INDEXING
PARTIAL;
T cen
n
o
2
3
li
ti
e
a
l
Index r
created.
m rab
o
f
n nsfe
I
l
SQL>
ba n-tra
o
l
G4. Create
oa partial local partitioned index as follows.
nSQL>
CREATE INDEX hr.tab_part1_lidx_orderdate
DEF
--OFF
ON hr.tab_part1 (order_date)
LOCAL INDEXING PARTIAL;
2
3
Index created.
SQL>
5.
Check the indexing type and status of the indexes.
SQL> col INDEX_NAME format a26
SQL> SELECT indexing, index_name, status
FROM
dba_indexes
WHERE index_name like 'TAB_PART1%';
2
3
Chapter 21 - Page 5
a
INDEXING
-------PARTIAL
PARTIAL
INDEX_NAME
-------------------------TAB_PART1_LIDX_ORDERDATE
TAB_PART1_GIDX_ORDERMODE
STATUS
-------N/A
VALID
SQL>
6.
Check the status of the index partitions of the partial local index.
SQL> col PARTITION_NAME format a20
SQL> SELECT index_name, partition_name, status
FROM dba_ind_partitions
WHERE INDEX_NAME like 'TAB_PART1%';
2
3
INDEX_NAME
PARTITION_NAME
-------------------------- -------------------TAB_PART1_LIDX_ORDERDATE
ORD_P5
TAB_PART1_LIDX_ORDERDATE
ORD_P4
ORD_P3
ORD_P2
TAB_PART1_LIDX_ORDERDATE ORD_P1
STATUS
-------UNUSABLE
UNUSABLE
USABLE
UNUSABLE
USABLE
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
b
lo den
g
@ Stu
o
SQL>
f
(in this
y
7. Insert rows into the table.
og use
l
o
SQL> INSERT INTO hr.tab_part1
hn se to
c
VALUES (10, TO_DATE('01-FEB-1999','DD-MON-YYYY'),
e
T cen
'direct',200,0,20,201,222);
n
o
li
ti
e
a
l
1 row created.
rm erab
o
f
In ansf INTO hr.tab_part1
l
SQL> INSERT
a
b n-tr (11, TO_DATE('01-MAY-1999','DD-MON-YYYY'),
Glo nVALUES
o
'online',300,0,30,301,333);
1 row created.
VALUES (12, TO_DATE('01-SEP-1999','DD-MON-YYYY'),
'direct',400,0,40,401,444);
1 row created.
VALUES (13, TO_DATE('01-FEB-2000','DD-MON-YYYY'),
'direct',500,0,50,501,555);
Chapter 21 - Page 6
a
1 row created.
SQL> COMMIT;
Commit complete.
SQL>
8.
Check that the partial global index TAB_PART1_GIDX_ORDERMODE is used while
performing queries on the highly selective column ORDER_MODE to access a single value
such as direct. The optimizer has to rely on a full scan of the non-indexed partitions for
the value such as online stored in rows in partitions that are not indexed.
a. Collect statistics for the table.
SQL> EXEC dbms_stats.gather_table_stats ('HR','TAB_PART1')
s
) ha
om ฺ
c
ฺ
ch idinethe
b. Generate a plan for a query accessing the value direct of the ORDER_MODE
e
t
i
l- t Gu
table where there are few rows.
a
b
lo den
SQL> EXPLAIN PLAN FOR
g
tu
@
2 SELECT order_mode, order_status
FROM hr.tab_part1
o
S
f
(in this
3 WHERE order_mode='direct';
y
og use
l
o
hn se to
Explained.
c
e
T cen
n
o
li
ti* fromletable(dbms_xplan.display)
SQL> select
;
a
b
m
r
a
fo sfer
n
I
alPLAN_TABLE_OUTPUT
an
r
b
t
o
n
Gl n----------------------------------------------------------------o
SQL>
-----------------------------------------------------------------------------------------------------------------------| Id | Operation
| Rows | Bytes | Cost (%CPU)| Time
| Name
| Pstart| Pstop |
--------------------------------------------------------------------------------------------------------------------------------------Copyright © 2013, Oracle and/or its affiliates. All rights reserved.
Chapter 21 - Page 7
a
|
|
2 |
18 |
30
|
|
1 | VIEW
3 |
57 |
|
|
2 |
|*
|
3 |
1 |
UNION-ALL
|
|
30
|
(0)| 00:00:01 |
(0)| 00:00:01 |
|
|
|
| VW_TE_2
|
|
|
|
|
|
TABLE ACCESS BY GLOBAL INDEX ROWID BATCHED| TAB_PART1
17 |
3
(0)| 00:00:01 | ROWID | ROWID |
|* 4 |
INDEX RANGE SCAN
TAB_PART1_GIDX_ORDERMODE
|
2 |
|
1
(0)| 00:00:01 |
|
|
|
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
b
|* 6 |
TABLE ACCESS FULL
lo den | TAB_PART1
g
|
2 |
34 |
27
(0)| 00:00:01
tu
@ |KEY(OR)|KEY(OR)|
o
S
f
(in this
y
---------------------------------------------------------------og use
l
o
---------------hn se to
c
--------------------------------------------------------e
T cen
n
o
li
ti
e
a
l
rm erab
o
f
f
Predicate
(identified by operation id):
In ansInformation
l
a
--------------------------------------------------b
tr
Glo non|
|
5 |
2 |
PARTITION RANGE OR
|
34 |
27
(0)| 00:00:01 |KEY(OR)|KEY(OR)|
3 - filter("TAB_PART1"."ORDER_DATE"<TO_DATE(' 1999-10-01
00:00:00', 'syyyy-mm-dd hh24:mi:ss') AND
"TAB_PART1"."ORDER_DATE">=TO_DATE(' 1999-07-01
00:00:00', 'syyyy-mm-dd hh24:mi:ss') OR
"TAB_PART1"."ORDER_DATE"<TO_DATE('
1999-03-01 00:00:00', 'syyyy-mm-dd hh24:mi:ss'))
4 - access("ORDER_MODE"='direct')
6 - filter("ORDER_MODE"='direct' AND
("TAB_PART1"."ORDER_DATE">=TO_DATE(' 1999-10-01 00:00:00',
'syyyy-mm-dd hh24:mi:ss') AND
"TAB_PART1"."ORDER_DATE"<TO_DATE(' 2010-03-01
Chapter 21 - Page 8
a
1999-07-01 00:00:00', 'syyyy-mm-dd hh24:mi:ss')
AND "TAB_PART1"."ORDER_DATE">=TO_DATE(' 1999-03-01 00:00:00',
'syyyy-mm-ddhh24:mi:ss')))
25 rows selected.
SQL>
The partial global index is used to access the two partitions of the table where the rows
containing the direct value in the ORDER_MODE column are stored.
9.
Load the ord_p1 partition. This partition is indexed. So both the partial global and local
indexes will be updated.
SQL> INSERT INTO hr.tab_part1 PARTITION (ord_p1)
2 SELECT * FROM hr.tab_part1 PARTITION (ord_p1);
1 row created.
SQL> /
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
b
lo den
g
4 rows created.
@ Stu
o
f
SQL> /
(in this
y
og use
l
o
8 rows created.
hn se to
c
e
SQL> /
T cen
n
o
li
ti
e
a
l
b
16 rows
rmcreated.
a
r
o
f
e
In ansf
l
a
b SQL> t/r
Glo non2 rows created.
SQL> /
32 rows created.
SQL> /
64 rows created.
SQL> /
128 rows created.
SQL> /
256 rows created.
Chapter 21 - Page 9
a
SQL> /
512 rows created.
SQL> /
1024 rows created.
SQL> COMMIT;
Commit complete.
SQL>
10. Generate the plan for a query by using the key of the partial global index.
SQL> EXEC dbms_stats.gather_table_stats ('HR','TAB_PART1')
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
SQL>
a
b
lo den
g
@ Stu
o
f
is hr.tab_part1 WHERE
(in FROM
h
t
2 SELECT order_mode, order_status
y
og use
order_mode='direct';
l
o
hn se to
c
e
T cen
Explained.
n
o
li
ti
e
a
l
b
a
SQL> orm
r
f
e
Inthat athenpartial
sf local index is used to access the ord_p3 partition.
l
11. You
see
a
r
b n-tselect
* from table(dbms_xplan.display) ;
Glo nSQL>
o
PLAN_TABLE_OUTPUT
---------------------------------------------------------------Plan hash value: 1639651856
---------------------------------------------------------------| Id | Operation
| Name
| Pstart| Pstop |
---------------------------------------------------------------|
|
| 2050 | 18450 |
43
(0)| 00:00:01 |
|
|
a
|
1 | VIEW
| VW_TE_2
| 3600 | 68400 |
43
(0)| 00:00:01 |
|
|
|
2 |
UNION-ALL
|
|
|
|
|
|
|
|
|
3 |
CONCATENATION
|
|
|
|
|
|
|
|
|
4 |
|
| 2048 | 34816 |
14
(0)| 00:00:01 |
1 |
1 |
|* 5 |
TABLE ACCESS FULL
|
TAB_PART1
| 2048 | 34816 |
14
(0)| 00:00:01
|
1 |
1 |
|
6 |
|
|
1 |
17 |
2
(0)| 00:00:01 |
3 |
3 |
|* 7 |
TABLE ACCESS BY LOCAL INDEX ROWID BATCHED|
TAB_PART1
|
1 |
17 |
2
(0)| 00:00:01
|
3 |
3 |
|* 8 |
INDEX RANGE SCAN
|
TAB_PART1_LIDX_ORDERDATE |
1 |
|
1
(0)| 00:00:01
|
3 |
3 |
|
9 |
PARTITION RANGE OR
|
| 1551 | 26367 |
27
(0)| 00:00:01 |KEY(OR)|KEY(OR)|
|* 10 |
TABLE ACCESS FULL
|
TAB_PART1
| 1551 | 26367 |
27
(0)| 00:00:01
|KEY(OR)|KEY(OR)|
----------------------------------------------------------------
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
b
lo den
g
@ Stu
o
f
(in this
y
og use
l
o
hn se to
c
e
n
T c(identified
Predicate Information
by operation id):
e
n
i
o
l
i
t
--------------------------------------------------a
le
b
m
r
a
fo sfer
n
I
5
AND
l -rafilter("ORDER_MODE"='direct'
n
a
b
t
1999-03-01 00:00:00', 'syyyyGlo nmm-dd
on- hh24:mi:ss'))
7 - filter("ORDER_MODE"='direct')
8 - access("TAB_PART1"."ORDER_DATE">=TO_DATE(' 1999-07-01
00:00:00', 'syyyy-mm-dd hh24:mi:ss'))
filter(LNNVL("TAB_PART1"."ORDER_DATE"<TO_DATE(' 1999-0301 00:00:00', 'syyyy-mm-dd hh24:mi:ss')))
10 - filter(("TAB_PART1"."ORDER_DATE">=TO_DATE(' 1999-10-01
a
'syyyy-mm-dd
hh24:mi:ss')) AND "ORDER_MODE"='direct')
30 rows selected.
SQL>
12. Generate the plan for a query on the non-indexed partition ord_p2. A table access full is
performed on the partition.
SELECT order_mode, order_status FROM hr.tab_part1
WHERE order_date >=TO_DATE('1999-03-01 00:00:00','syyyy-mmdd hh24:mi:ss')
AND
order_date <TO_DATE('1999-07-01 00:00:00','syyyy-mmdd hh24:mi:ss');
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
- t Gu
a
SQL> select * from table(dbms_xplan.display)
;l
b
lo den
g
@ Stu
o
PLAN_TABLE_OUTPUT
f
(in this
---------------------------------------------------------------y
og use
l
o
hn se to
c
e
T cen
n
o
li
ti
---------------------------------------------------------------e
a
l
b
a
-| Idorm
| Operation
| Name
| Rows | Bytes |
r
f
e
f
n
Cost
(%CPU)|
Time
|
Pstart|
Pstop
|
l I rans
a
b
---------------------------------------------------------------t
Glo n-|on- 0 | SELECT STATEMENT
|
|
1 |
17 |
14
(0)| 00:00:01 |
|
|
Explained.
|
1 | PARTITION RANGE SINGLE|
|
1 |
17 |
14
(0)| 00:00:01 |
2 |
2 |
|
2 |
TABLE ACCESS FULL
| TAB_PART1 |
1 |
17 |
14
(0)| 00:00:01 |
2 |
2 |
---------------------------------------------------------------9 rows selected.
SQL>
a
13. Generate the plan for a query on the indexed partition ord_p1 and ord_p3. A full scan is
performed on the large partition ord_p1 and the partial local index is used to access the
ord_p3 partition rows.
2 SELECT order_mode, order_status FROM hr.tab_part1
3 WHERE order_date <TO_DATE('1999-03-01 00:00:00','syyyy-mmdd hh24:mi:ss')
4
OR (order_date between TO_DATE('1999-07-01
00:00:00','syyyy-mm-dd hh24:mi:ss') AND TO_DATE('1999-10-01
00:00:00', 'syyyy-mm-dd hh24:mi:ss'));
Explained.
SQL> select * from table(dbms_xplan.display) ;
s
) ha
PLAN_TABLE_OUTPUT
---------------------------------------------------------------Plan hash value: 2109685904
---------------------------------------------------------------| Id | Operation
| Name
| Pstart| Pstop |
---------------------------------------------------------------|
|
| 3337 | 56729 |
30
(0)| 00:00:01 |
|
|
|
1 | VIEW
| VW_TE_2
| 6621 |
122K|
30
(0)| 00:00:01 |
|
|
|
2 |
UNION-ALL
|
|
|
|
|
|
|
|
|
3 |
CONCATENATION
|
|
|
|
|
|
|
|
|
4 |
|
|
1 |
17 |
2
(0)| 00:00:01 |
3 |
3 |
|
5 |
TABLE ACCESS BY LOCAL INDEX ROWID BATCHED|
TAB_PART1
|
1 |
17 |
2
(0)| 00:00:01
|
3 |
3 |
|* 6 |
INDEX RANGE SCAN
|
TAB_PART1_LIDX_ORDERDATE |
1 |
|
1
(0)| 00:00:01
|
3 |
3 |
|
7 |
|
| 4095 | 69615 |
14
(0)| 00:00:01 |
1 |
1 |
|* 8 |
TABLE ACCESS FULL
|
TAB_PART1
| 4095 | 69615 |
14
(0)| 00:00:01
|
1 |
1 |
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
b
lo den
g
@ Stu
o
f
(in this
y
og use
l
o
hn se to
c
e
T cen
n
o
li
ti
e
a
l
rm erab
o
f
In ansf
l
a
b
tr
Glo non-
a
|
9 |
PARTITION RANGE OR
|
| 2525 | 42925 |
14
(0)| 00:00:01 |KEY(OR)|KEY(OR)|
|* 10 |
TABLE ACCESS FULL
|
TAB_PART1
| 2525 | 42925 |
14
(0)| 00:00:01
|KEY(OR)|KEY(OR)|
---------------------------------------------------------------Predicate Information (identified by operation id):
--------------------------------------------------6 - access("TAB_PART1"."ORDER_DATE">=TO_DATE(' 1999-07-01
00:00:00', 'syyyy-mm-dd hh24:mi:ss'))
filter("ORDER_DATE"<TO_DATE(' 1999-03-01 00:00:00',
'syyyy-mm-dd hh24:mi:ss') OR "ORDER_DATE">=TO_DATE(' 1999-07-01
"ORDER_DATE"<=TO_DATE(' 1999-10-01 00:00:00', 'syyyy-mm-dd
hh24:mi:ss'))
8 - filter("TAB_PART1"."ORDER_DATE"<TO_DATE(' 1999-03-01
00:00:00', 'syyyy-mm-dd hh24:mi:ss') AND ("ORDER_DATE"<TO_DATE('
1999-03-01 00:00:00', 'syyyy-mm-dd hh24:mi:ss') OR
"ORDER_DATE">=TO_DATE(' 1999-07-01 00:00:00', 'syyyy-mm-dd
hh24:mi:ss') AND
"ORDER_DATE"<=TO_DATE(' 1999-10-01 00:00:00',
'syyyy-mm-dd hh24:mi:ss')) AND
(LNNVL("TAB_PART1"."ORDER_DATE">=TO_DATE('
1999-07-01 00:00:00', 'syyyy-mm-dd hh24:mi:ss'))
OR LNNVL("TAB_PART1"."ORDER_DATE"<TO_DATE(' 1999-10-01
00:00:00', 'syyyy-mm-dd
hh24:mi:ss'))))
10 - filter(("TAB_PART1"."ORDER_DATE">=TO_DATE(' 1999-10-01
'syyyy-mm-dd
hh24:mi:ss')) AND ("ORDER_DATE">=TO_DATE(' 199907-01 00:00:00', 'syyyy-mm-dd hh24:mi:ss') AND
"ORDER_DATE"<=TO_DATE(' 1999-10-01
"ORDER_DATE"<TO_DATE(' 1999-03-01 00:00:00', 'syyyy-mm-dd
hh24:mi:ss')))
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
b
lo den
g
@ Stu
o
f
(in this
y
og use
l
o
hn se to
c
e
T cen
n
o
li
ti
e
a
l
rm erab
o
f
In ansf
l
a
b
tr
Glo non-
35 rows selected.
a
SQL> EXIT
$
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
b
lo den
g
@ Stu
o
f
(in this
y
og use
l
o
hn se to
c
e
T cen
n
o
li
ti
e
a
l
rm erab
o
f
In ansf
l
a
b
tr
Glo non-
a
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
b
lo den
g
@ Stu
o
f
(in this
y
og use
l
o
hn se to
c
e
T cen
n
o
li
ti
e
a
l
rm erab
o
f
In ansf
l
a
b
tr
Glo non-
a
s
) ha
om ฺ
c
ฺ
ch22: iSQL
de
e
t
i
u
l
Enhancements
Migration
G
t
ba and
n
o
l
gfor Unicode
Assistant
de
u
t
@
nf22o this S
i
Chapter
(
ogy use
l
o
hn se to
c
e
T cen
n
o
li
ti
e
a
l
rm erab
o
f
In ansf
l
a
b
tr
Glo non-
Practices for Lesson 22: SQL Enhancements and Migration Assistant for Unicode
Chapter 22 - Page 1
a
Practices Overview
In the practice for this lesson, you use the extended data type column to create columns of
32767 bytes long and the row-limiting clause to limit the rows resulting from queries.
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
b
lo den
g
@ Stu
o
f
(in this
y
og use
l
o
hn se to
c
e
T cen
n
o
li
ti
e
a
l
rm erab
o
f
In ansf
l
a
b
tr
Glo non-
Chapter 22 - Page 2
a
Practice 22-1: Using 32K VARCHAR2 Data Type
Overview
In this practice, you create a new table with a column of data type VARCHAR2(32767).
Tasks
1.
Connect to the source database orcl.
$ . oraenv
Connected to:
Testing options
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
SQL>
b
lo den
g
2. Create a table LONG_VARCHAR with a column VARCHAR2(32767).
@ Stu
o
f
is VARCHAR2(32767));
SQL> CREATE TABLE long_varchar(id
(in NUMBER,vc
h
t
y
CREATE TABLE long_varchar(id
se VARCHAR2(32767))
og NUMBER,vc
l
u
o
*
hn se to
c
e
ERROR at line 1:T
n
e
n
c
i
o
l
i
ORA-00910: tspecified
e length too long for its datatype
a
l
b
m
r
ra
o
f
e
f
n
I ans
lSQL>
a
b
-tr parameter MAX_STRING_SIZE to EXTENDED.
ninstance
G3.loSetnthe
o
SQL> alter system set MAX_STRING_SIZE =EXTENDED;
alter system set MAX_STRING_SIZE =EXTENDED
*
ERROR at line 1:
ORA-02097: parameter cannot be modified because specified value
is invalid
ORA-14694: database must in UPGRADE mode to begin
MAX_STRING_SIZE migration
SQL>
Chapter 22 - Page 3
a
4.
Configure the database to be compatible with extended data type columns.
a. Restart the database instance.
Database closed.
SQL>
.
SQL> startup upgrade
Fixed Size
2261160 bytes
Variable Size
989859672 bytes
Database Buffers
687865856 bytes
Redo Buffers
6938624 bytes
Database mounted.
Database opened.
SQL>
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
b
n
o devalue.
lEXTENDED
g
b. Set the instance parameter MAX_STRING_SIZE to the
u
o@= iEXTENDED;
St
f
SQL> ALTER SYSTEM SET MAX_STRING_SIZE
n
s
i
(
th
y
g
e
lo o us
o
System altered.
n
h se t
c
e
T cen
n
SQL>
o
li
ti
e
a
l
b
m $ORACLE_HOME/rdbms/admin/utl32k.sql
c. Executerthe
script as SYSDBA. Be
a
r
o
f
e
f
aware
that
the
script
may
last
very
long
(around
one
hour).
Although,
at the very last
n
I ans
l
a
step
when
the
function
is
being
dropped
and
the
script
stuck,
you
can
start another
b session
tras SYSDBA and perform task 5 to check if the creation of the table
o
l
n
is possible
G no
with a VARCHAR2(32767) data type column.
SQL> @$ORACLE_HOME/rdbms/admin/utl32k.sql
Session altered.
DOC>############################################################
###########
DOC>############################################################
###########
DOC>
number"
DOC>
error if the database has not been opened for UPGRADE.
DOC>
DOC>
Perform a "SHUTDOWN ABORT" and
Chapter 22 - Page 4
a
DOC>
restart using UPGRADE.
DOC>############################################################
###########
DOC>############################################################
###########
DOC>#
no rows selected
DOC>############################################################
###########
DOC>############################################################
###########
DOC>
number"
DOC>
error if the database does not have compatible >= 12.0.0
DOC>
DOC>
Set compatible >= 12.0.0 and retry.
DOC>############################################################
###########
DOC>############################################################
###########
DOC>#
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
b
lo den
g
@ Stu
o
f
(in this
y
se
og completed.
l
u
o
hn se to
c
e
T cen
n
Session altered.
o
li
ti
e
a
l
rm erab
o
f
0 Irows
n updated.
sf
l
n
a
a
b n-tr
Glo nCommit
o
complete.
1671 rows updated.
Commit complete.
System altered.
Commit complete.
System altered.
Chapter 22 - Page 5
a
Session altered.
No errors.
Session altered.
Package altered.
TIMESTAMP
------------------------------------------------------------------------------COMP_TIMESTAMP UTLRP_BGN 2012-07-11 08:29:59
s
) ha
DOC>
The following PL/SQL block invokes UTL_RECOMP to
recompile invalid
DOC>
objects in the database. Recompilation time is
proportional to the
DOC>
number of invalid objects in the database, so this
command may take
DOC>
a long time to execute on a database with a large number
of invalid
DOC>
objects.
DOC>
DOC>
Use the following queries to track recompilation
progress:
DOC>
DOC>
1. Query returning the number of invalid objects
remaining. This
DOC>
number should decrease with time.
DOC>
SELECT COUNT(*) FROM obj$ WHERE status IN (4, 5,
6);
DOC>
DOC>
2. Query returning the number of objects compiled so far.
This number
DOC>
should increase with time.
DOC>
SELECT COUNT(*) FROM UTL_RECOMP_COMPILED;
DOC>
DOC>
This script automatically chooses serial or parallel
recompilation
DOC>
based on the number of CPUs available (parameter
cpu_count) multiplied
DOC>
by the number of threads per CPU (parameter
parallel_threads_per_cpu).
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
b
lo den
g
@ Stu
o
f
(in this
y
og use
l
o
hn se to
c
e
T cen
n
o
li
ti
e
a
l
rm erab
o
f
In ansf
l
a
b
tr
Glo non-
Chapter 22 - Page 6
a
DOC>
On RAC, this number is added across all RAC nodes.
DOC>
DOC>
UTL_RECOMP uses DBMS_SCHEDULER to create jobs for
parallel
DOC>
recompilation. Jobs are created without instance affinity
so that they
DOC>
can migrate across RAC nodes. Use the following queries
to verify
DOC>
whether UTL_RECOMP jobs are being created and run
correctly:
DOC>
DOC>
1. Query showing jobs created by UTL_RECOMP
DOC>
SELECT job_name FROM dba_scheduler_jobs
DOC>
WHERE job_name like 'UTL_RECOMP_SLAVE_%';
DOC>
DOC>
2. Query showing UTL_RECOMP jobs that are running
DOC>
SELECT job_name FROM dba_scheduler_running_jobs
DOC>
WHERE job_name like 'UTL_RECOMP_SLAVE_%';
DOC>#
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
b
lo den
g
@ Stu
o
f
(in this
TIMESTAMP
y
og use
l
---------------------------------------------------------------o
---------------hn se to
c
e
T cen 2012-07-11 08:32:14
COMP_TIMESTAMP UTLRP_END
n
o
li
ti
e
a
l
b query reports the number of objects that have
rmfollowing
a
DOC> o
The
r
f
e
compiled
In ansf
l
a
r errors.
b DOC>
twith
Glo nDOC>
onDOC> If the number is higher than expected, please examine the
error
DOC> messages reported with each object (using SHOW ERRORS) to
see if they
DOC> point to system misconfiguration or resource constraints
that must be
DOC> fixed before attempting to recompile these objects.
DOC>#
OBJECTS WITH ERRORS
------------------4
Chapter 22 - Page 7
a
DOC> The following query reports the number of errors caught
during
DOC> recompilation. If this number is non-zero, please query the
error
DOC> messages in the table UTL_RECOMP_ERRORS to see if any of
these errors
DOC> are due to misconfiguration or resource constraints that
must be
DOC> fixed before objects can compile successfully.
DOC>#
ERRORS DURING RECOMPILATION
--------------------------4
Function created.
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
Function dropped.
a
b
lo den
g
tu
@ "APEX_040200",
o
...Database user "SYS", database schema
user#
S
f
n this
i
(
"98" 06:52:09
gy usconsidered,
e
...Compiled 0 out of 2992lo
objects
0 failed
o
o
compilation 06:52:09 hn
t
c nse
...263 packages Te
nbodieslice
o
...255 package
i
t
a
le
...453rm
tables rab
fofunctions
fe
n
...11
I
s
l
n
a
ba...16
trprocedures
o
l
n
G n...3
o sequences
...458 triggers
...1316 indexes
...207 views
...0 libraries
...6 types
...0 type bodies
...0 operators
...0 index types
...Begin key object existence check 06:52:09
...Completed key object existence check 06:52:10
...Setting DBMS Registry 06:52:10
...Setting DBMS Registry Complete 06:52:10
Chapter 22 - Page 8
a
...Exiting validate 06:52:10
0 rows updated.
Commit complete.
SQL>
d.
Restart the database in normal mode.
Database closed.
SQL> startup
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
b
lo den
Fixed Size
2261160 bytes
g
@ Stu
o
Variable Size
989859672
bytes
f
is
(in bytes
h
Database Buffers
687865856
t
y
sebytes
og6938624
l
Redo Buffers
u
o
n e to
Database mounted. ch
e
T cens
Database opened.
n
tio le li
SQL>
a
b
rmthe MAX_STRING_SIZE
a
r
o
f
e
e. Verify
that
is set to EXTENDED.
n nsf
I
l
ra parameter MAX_STRING_SIZE
baSQL>
tshow
o
l
n
G no
NAME
TYPE
VALUE
------------------------------------ ----------- -------------max_string_size
string
EXTENDED
SQL>
Chapter 22 - Page 9
a
5.
Create a table with an extended data type column of 32767 bytes.
SQL> CREATE TABLE long_varchar(id NUMBER,vc VARCHAR2(32767));
Table created.
SQL> DESC long_varchar
Name
Null?
------------------------------- -------ID
VC
Type
-------------------NUMBER
VARCHAR2(32767)
SQL>
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
b
lo den
g
@ Stu
o
f
(in this
y
og use
l
o
hn se to
c
e
T cen
n
o
li
ti
e
a
l
rm erab
o
f
In ansf
l
a
b
tr
Glo non-
a
Practice 22-2: Quering a Table Using a SQL Row-Limiting Clause
Overview
In this practice, you limit the number or rows returned by a query that orders data.
Tasks
1.
Count the number of rows in the HR.EMPLOYEES table.
SQL> select count(*) from hr.employees;
COUNT(*)
---------83
SQL>
2.
Select the EMPLOYEE_ID and LAST_NAME of the first 10 employees ordered by their last
name.
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
b
lo den
g
@ Stu
o
f
----------- ------------------------(in this
y
174
Abel
og use
l
o
166
Ande
hn se to
c
e
105
Austin
T cen
n
o
204
tiBaer le li
a
b
167
rm eBanda
a
r
o
f
In 172ansf Bates
l
a
b
tr
192
Bell
Glo non-151 Bernstein
SQL> SELECT employee_id, last_name FROM hr.employees
2 ORDER BY last_name
3 FETCH FIRST 10 ROWS ONLY;
129
169
Bissot
Bloom
10 rows selected.
SQL>
You see the first 10 employees ordered by their last name. The first of them has a name
starting with letter A.
a
3.
Select the EMPLOYEE_ID, LAST_NAME and HIRE_DATE of the first 10 employees ordered
by their hire date.
SQL> SELECT employee_id,last_name, hire_date FROM hr.employees
2 ORDER BY hire_date
3 FETCH FIRST 10 ROWS ONLY;
EMPLOYEE_ID
----------102
203
206
205
204
109
108
114
122
115
LAST_NAME
------------------------De Haan
Mavris
Gietz
Higgins
Baer
Faviet
Greenberg
Raphaely
Kaufling
Khoo
HIRE_DATE
--------13-JAN-01
07-JUN-02
07-JUN-02
07-JUN-02
07-JUN-02
16-AUG-02
17-AUG-02
07-DEC-02
01-MAY-03
18-MAY-03
EMPLOYEE_ID
----------100
137
200
141
184
LAST_NAME
------------------------King
Ladwig
Whalen
Rajs
Sarchand
HIRE_DATE
--------17-JUN-03
14-JUL-03
17-SEP-03
17-OCT-03
27-JAN-04
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
b
10 rows selected.
lo den
g
@ Stu
o
f
SQL>
(in this
y
g usedate. The first hired one was the
You see the first 10 employees orderedlo
by their hire
o
employee De Haan.
hn se to
c
e
4. Select the EMPLOYEE_ID,T
LAST_NAME
n and HIRE_DATE of the next 5 employees ordered
e
n
c
i
o
l
by their hire date coming
the previous ones.
ti after
e
a
l
b
m
SQL> SELECT
employee_id,last_name,
hire_date FROM hr.employees
r
ra
o
f
e
f
n
l I2 ORDER
ns BY hire_date
a
a
r
b
t
3
OFFSET
10 ROWS FETCH NEXT 5 ROWS ONLY;
Glo non-
SQL>
a
5.
Select the EMPLOYEE_ID and LAST_NAME of the first 8% of the employees ordered by their
employee identifier.
SQL> SELECT employee_id, last_name FROM hr.employees
2 ORDER BY employee_id
3 FETCH FIRST 8 PERCENT ROWS ONLY;
EMPLOYEE_ID
----------100
101
102
103
104
105
106
LAST_NAME
------------------------King
Kochhar
De Haan
Hunold
Ernst
Austin
Pataballa
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
SQL> EXIT
a
b
lo den
$
g
tu The first one is the
@ identifier.
You see the first seven employees ordered by theirfo
employee
S
(in this7 rows.
employee 100. 8 % of 83 rows correspond to
approximately
y
og use
l
o
hn se to
c
e
T cen
n
o
li
ti
e
a
l
rm erab
o
f
In ansf
l
a
b
tr
a
s
) ha
om ฺ
c
ฺ
ch ide
e
t
i
l- t Gu
a
b
lo den
g
@ Stu
o
f
(in this
y
og use
l
o
hn se to
c
e
T cen
n
o
li
ti
e
a
l
rm erab
o
f
In ansf
l
a
b
tr
Glo non-
a

Oracle Database 12c: New Features for Administrators

Transcription

Similar documents

Elogix – Oracle Practice - Elogix Software Pvt Ltd

Providing comPrehensive, Personalised solutions for high net worth

Oracle 10g release 2

Five Techniques for Loading Flat File Data into Oracle Tables

WHAT DOES PSTC Employees Federal Gredit DO WITH YOUR

1072 Integrating Multiple EBS Instances with one OTM

Privacy Policy - SnoCope Credit Union

ta news corner

Building and Deploying Web-Scale Social Networking Applications

Capabilities Overview