Create Database   «Prev  Next»

Create Permanent and Temporary Tablespaces in a PDB - Exercise

Objective: Design separate permanent and temporary storage for a lab application PDB.

Use an existing, open read/write application PDB named COINPDB with OMF configured and sufficient free storage. Confirm the current container, DB_CREATE_FILE_DEST, and that the three exercise names are unused. Use an account with CREATE TABLESPACE and the necessary dictionary-view access. A newly created CDB root/seed alone does not satisfy this prerequisite.

The COIN_ prefix avoids assuming USERS or TEMP is absent. This exercise does not replace existing defaults, move objects, or create a manual rollback-segment tablespace. Submit a script and verification plan; execution is optional in an authorized lab.

Instructions

  1. Create permanent COIN_USERS and COIN_TOOLS using locally managed extents and automatic segment space management.
  2. Create temporary COIN_TEMP using a tempfile. For all three use a 100M initial size, 10M growth increment and 1G maximum; these are lab examples only.
  3. Provide checks of container, existing names, tablespace type and permanent/temporary file allocation. Explain why this exercise does not create RBS or individual rollback segments.
  4. Submit the SQL and expected/observed verification summary, labeling any unexecuted steps.

Self-assessment: 20 points

Compare your response with the model solution. This page does not automatically grade free-text answers.

  1. PDB, OMF, privileges, free-space and name checks (5 points).
  2. Two correct permanent tablespace statements (5 points).
  3. Temporary tablespace and all growth limits (5 points).
  4. Dictionary/file verification and undo distinction (5 points).