Examine the list of possible steps to transport a tablespace across platforms that have the same compatibility level, character sets, and endian format: 1. Make the tablespace read-only at the…

Question

Options

• A2, 4, and 3
• B2, 4, 3, and 5
• C1, 5, 2, 4, 3, and 6
• D1, 2, 4, 3, and 6

• A
  5% (1)
• B
  9% (2)
• D
  86% (19)

Explanation

Step 1 (1) : To copy tablespaces from one database to another using transportable tablespace, the source tablespaces are first kept in READ-ONLY mode (to ensure data consistency). Once the tablespaces are in READ-ONLY mode, the actual datafiles belonging to the source tablespaces are copied from source database to target database (using any available methods like scp, sftp, rcp, etc). Step 2 (2): Once the tablespace is kept in READ-ONLY mode, we need to generate the metadata export of the tablespaces that needs to transported using the DataPump export utility. Step 3 (4): Once the metadata export is generated on the source database for all the tablespaces that needs to be transported, we need to copy the Export Dump file as well as all the datafiles belonging to the tablespaces to be transported to the target database server.

No community discussion yet for this question.