nerdexam
Oracle

1Z0-060 · Question #191

You are the DBA for an Oracle Database 11g Release 1 data warehouse database running on Oracle Linux with little endianness. You want to plug in a transportable tablespace with a 16K blocksize from…

The correct answer is B. Set ALTER SYSTEM SET DB_CACHE_SIZE=192M followed by ALTER SYSTEM SET. Plugging in a transportable tablespace with a non-default block size requires the DBA to explicitly set the matching block-size cache parameter, because neither AMM nor ASMM automatically sizes non-default block-size caches.

New Features for Storage

Question

You are the DBA for an Oracle Database 11g Release 1 data warehouse database running on Oracle Linux with little endianness. You want to plug in a transportable tablespace with a 16K blocksize from an Oracle Database database that is running on a SPARC-based Oracle Solaris system with big endianness. 10g The data warehouse database has the following parameters set: The following parameters are not explicitly set: What action must you perform on the data warehouse database to prepare it for the transportable tablespace plug in operation?

Options

  • ADo nothing, because Automatic Memory Management will size DB_16K_CACHE_SIZE
  • BSet ALTER SYSTEM SET DB_CACHE_SIZE=192M followed by ALTER SYSTEM SET
  • CDo nothing, because you cannot transport a tablespace between databases with different endian
  • DDo nothing, because Automatic Shared Memory Management will size DB_16K_CACHE_SIZE
  • ESet ALTER SYSTEM SET DB_16K_CACHE_SIZE=8M and leave other parameters set to their

How the community answered

(23 responses)
  • A
    9% (2)
  • B
    61% (14)
  • C
    4% (1)
  • D
    4% (1)
  • E
    22% (5)

Why each option

Plugging in a transportable tablespace with a non-default block size requires the DBA to explicitly set the matching block-size cache parameter, because neither AMM nor ASMM automatically sizes non-default block-size caches.

ADo nothing, because Automatic Memory Management will size DB_16K_CACHE_SIZE

Automatic Memory Management controls total SGA and PGA sizes but does not automatically allocate memory for non-default block-size caches like DB_16K_CACHE_SIZE.

BSet ALTER SYSTEM SET DB_CACHE_SIZE=192M followed by ALTER SYSTEM SETCorrect

Oracle never automatically allocates memory for non-default block-size caches such as DB_16K_CACHE_SIZE under either AMM or ASMM; the DBA must set this parameter explicitly before the 16K tablespace can be mounted. Setting DB_CACHE_SIZE alongside DB_16K_CACHE_SIZE is necessary when ASMM is managing the standard cache to ensure the total SGA allocation remains coherent.

CDo nothing, because you cannot transport a tablespace between databases with different endian

Transporting tablespaces between databases with different endianness is fully supported; RMAN's CONVERT TABLESPACE command performs the required byte-order conversion before the plug-in.

DDo nothing, because Automatic Shared Memory Management will size DB_16K_CACHE_SIZE

Automatic Shared Memory Management automatically sizes only standard SGA components such as the default buffer cache and shared pool; non-default block-size caches are explicitly excluded from its management.

ESet ALTER SYSTEM SET DB_16K_CACHE_SIZE=8M and leave other parameters set to their

Setting only DB_16K_CACHE_SIZE may be insufficient when ASMM is active, because the total SGA distribution may also require adjusting DB_CACHE_SIZE to free up memory for the new cache.

Concept tested: Non-default block size cache configuration for transportable tablespace plug-in

Source: https://docs.oracle.com/cd/B28359_01/server.111/b28310/transport.htm

Topics

#transportable tablespace#cross-platform#DB_16K_CACHE_SIZE#Automatic Shared Memory Management

Community Discussion

No community discussion yet for this question.

Sign up to join the discussion
Full 1Z0-060 Practice