tablespace point-in-time recovery is possible only with RMAN.（）

A .  restore the tablespace from the backup， and then perform an incomplete recovery B .  restore the tablespace from the backup， and then apply all the redo information C .  restore all the data files in the database， and then perform an incomplete recovery D .  restore the tablespace from the backu

A . YYYY-DD-MM:HH24:SS:MI  B . YYYY-DD-MM:HH24:SS:MM  C . YYYY-MM-DD:HH24:MI:SS  D . YYYY-DD-MM:SS:MI:HH24

A . The error log B . The backup log C . The general query log D . Binary logs E . The data backup F . Configuration file

A .  Change-based B .  Cancel-based C .  Time-based D .  Sequence number-based E .  Transaction number-based

A .  The SYSTEM tablespace. B .  The UNDO tablespace. C .  All tablespaces with tables. D .  All tablespaces with indexes. E .  No tablespaces are automatically restored.

A .  incomplete names B .  incomplete names with templates C .  alias with template names D .  numeric name

A . DBMS_STATS  B . DBMS_ALERT  C . DBMS_SPACE  D . DBMS_MONITOR  E . DBMS_SERVER_ALERT F . DBMS_SPACE_ADMIN

A . Data Pump B . SQL scripts C . SQL*Loader D . Flashback database E . Recovery Manager （RMAN） script

A . The tablespace has two data files. B . An error is reported and tablespace creation fails. C . Data files are created with names generated by the instance. D . The tablespace can be extended without specifying the data file. E . Data files belonging to the USERS tablespace cannot be renamed.

A .  The target database must be in NOARCHIVELOG mode. B .  No backup is required of the database before you perform a TSPITR. C .  You must have all archived redo logs generated since the last backup up to the point to which you want to restore the transport set. D .  If you rename a tablespace， you can not perform a TSPITR to any point in time before that rename operation occurred. E .  If you have tables in tablespace_1 that have associated constraints in tablespace_2，then you must transport both tablespaces.

A . New channels for restore and recovery tasks B . New name for the data files of the tablespace C . Auxiliary name for the data files of the tablespace D . Auxiliary destinations for an auxiliary set of data file

A .  until time B .  until change C .  until sequence D .  until SCN E .  until commit

A . The database automatically determines the extent-sizing policy for the tablespace. B . The segments are automatically shrunk when the contents are removed from them. C . The allocation of extents within the tablespace is managed through the dictionary tables. D . The space utilization description of the data blocks in segments is recorded inbitmapblocks. E . The space utilization description of the data blocks in segments is managed through free lists.MANUAL

A .  New channels for restore and recovery tasks B .  New name for the data files of the tablespace C .  Auxiliary name for the data files of the tablespace D .  Auxiliary destinations for an auxiliary set of data file

A .  The index tablespace contains bitmap indexes. B .  The index tablespace contains more than one data file. C .  The index tablespace supports only complete recovery. D .  The index tablespace is not a dictionary-managed tablespace. E .  There is a dependency relationship between a table and its indexes.

A .  Restore tablespace B .  Recover tablespace C .  Tablespace recover D .  Recover to time E .  recover datafile

A .  CREATE TABLESPACE DATA1 DATAFILE ’+grp1/abc（datafile）’； B .  CREATE TABLESPACE DATA1 DATAFILE ’+grp1’； C .  CREATE TABLESPACE DATA1 DATAFILE ’+data1（tempfile）’； D .  CREATE TABLESPACE DATA1 DATAFILE ’+grp1.256.34359’；

A .  SQL scripts B .  Recovery Manager （RMAN） script C .  Data Pump D .  SQL*Loader E .  Flashback database

A . The database automatically determines the extent-sizing policy for the tablespace. B . The segments are automatically shrunk when the contents are removed from them. C . The allocation of extents within the tablespace is managed through the dictionary tables. D . The space utilization description of the data blocks in segments is recorded in bitmap blocks. E . The space utilization description of the data blocks in segments is managed through free lists.

A . restore the tablespace from the backup; there is no need to apply the redo information  B . restore the full database to recover the data up to the point when you performed the backup  C . restore the tablespace from the backup， and then perform a recovery using the backup control file D . restore the tablespace from the backup， and then recover the tablespace; all the redo information from the point when the tablespace was made read/write is applied

A . None of the SYSAUX occupants can be relocated. B . The USERS tablespace is a bigfile tablespace （BFT）. C . The united Job Scheduler occupant cannot be relocated. D . The SYSAUX occupants can be relocated to the SYSTEM tablespace only.

A .  TEST_TBS is a small file tablespace. B .  TEST_TBS is a bigfile tablespace （BFT）. C .  TEST_TBS is the default temporary tablespace. D .  TEST_TBS is a dictionary-managed tablespace.

A . TEST_TBS is a small file tablespace. B . TEST_TBS is a bigfile tablespace (BFT). C . TEST_TBS is the default temporary tablespace. D . TEST_TBS is a dictionary-managed tablespace.

A .  You cannot perform the TSPITR with the constraints enabled. B .  You must perform the TSPITR recovery of both tablespaces for it to be successful. C .  You can perform TSPITR only on the USERS tablespace. D .  RMAN will determine if the INDEX_TBS tablespace must also be duplicated and will duplicate it automatically. E .  The TSPITR will only be successful if the constraint is enabled.