READ Free Dumps For Oracle- 1z0-023
| Question ID 8724 | Which export option will generate code to create an initial extent that is equal to the sum of the sizes of all the extents currently allocated to an object?
|
| Option A | FULL
|
| Option B | DIRECT
|
| Option C | COMPACT
|
| Option D | COMPRESS
|
| Correct Answer | D |
Explanation Explanation/Reference: Explanation: Answer D is correct because parameter COMPRESS=Y indicates whether EXPORT will place all rows of the table into one initial extent in the export file. This is useful for reducing fragmentation, but you may allocate too much space if your table has a lots of deleted rows. It is important to note here that Oracle does not actually reduce space use; it merely recalculates the existing data so that it fits into one big initial segment, which can still cause space problems later. Incorrect Answers: A: Parameter FULL=Y indicates whether EXPORT should export the entire database. B. Parameter DIRECT=Y allows user to run faster exports using the direct path. This is similar in function to direct-path loading in SQL*Loader. C: Parameter COMPACT does not exist. Oracle 8, DBA Certification Exam Guide, Jason S. Couchman, p. 534-536 Chapter 1: Selecting Data from Oracle
| Question ID 8725 | What are two reasons for changing user quotas on a tablespace? (Choose two)
|
| Option A | A datafile becomes full.
|
| Option B | A user encounters slow response time from the application.
|
| Option C | Tables owned by a user exhibit rapid and anticipated growth.
|
| Option D | Database objects are reorganized and placed in different tablespace.
|
| Correct Answer | CD |
Explanation Explanation/Reference: Explanation: Answers A and C are correct because a quota is a limit on the amount of space the user's database objects can occupy within the tablespace. If a user attempts to create a database object that exceeds that user's quota for that tablespace, then the object creation script will fail. A quota clause should be issued separately for every tablespace other than the temporary tablespace on which the user will have access to create database objects. Users need quotas on tablespaces to create database objects only. They do not need a quota on a tablespace to UPDATE, INSERT, or DELETE data in an existing object in the tablespace, so long as they do have the appropriate privilege on the object for data being inserted, updated or deleted. Incorrect Answers: A: User quota on a tablespace have nothing to do with a datafile which becomes full, because tablespace is a logical object, but datafile is physical object and you can not control datafile growth with tablespace quota. B: Slow response time from the application is not related with user quotas on a tablespace, it depends on performance problems. Oracle 8, DBA Certification Exam Guide, Jason S. Couchman, p. 466 Chapter 10: Managing Database Use