Encrypting a Tablespace
To encrypt an entire database, the COMPATIBLE initialization parameter must be set to
11.1.0.0.0??”the default for Oracle Database 11g. If the database has been upgraded from
an earlier release, and you change the COMPATIBLE parameter to 11.1.0.0.0, the change
is irreversible.
An existing tablespace cannot be encrypted; to encrypt the contents of an existing tablespace,
you must create a new tablespace with the ENCRYPTION option and copy or move existing
objects to the new tablespace. Oracle Enterprise Manager makes it easy to create a new encrypted
tablespace. In Figure 9-12, you create a new tablespace called USERS_CRYPT with a size of
500MB, located in an ASM disk group.
Clicking the Encryption Options button, you see the status of the wallet you created earlier (it
must be open to create an encrypted tablespace), and you can select the encryption algorithm
you want to use for the tablespace. After you click Continue, as shown in Figure 9-13, you return
to the Create Tablespace page.
Clicking Show SQL, you can see the SQL command Oracle Enterprise Manager will use to
create the tablespace:
CREATE SMALLFILE TABLESPACE "USERS_CRYPT"
DATAFILE'+DATA' SIZE 500M LOGGING EXTENT MANAGEMENT LOCAL
SEGMENT SPACE MANAGEMENT AUTO NOCOMPRESS ENCRYPTION
USING 'AES256' DEFAULT STORAGE(ENCRYPT)
Click Return and then OK; Oracle Enterprise Manager creates the tablespace.
346 Oracle Database 11g DBA Handbook
FIGURE 9-12 Creating an encrypted tablespace
FIGURE 9-13 Specifying encrypted tablespace options
PART
III
High Availability
This page intentionally left blank
CHAPTER
10
Real Application Clusters
349
350 Oracle Database 11g DBA Handbook
n Chapter 4, we presented an overview of Automatic Storage Management (ASM)
and Oracle Managed Files (OMF) and how they can ease administration, enhance
performance, and improve availability.
Pages:
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564