Cisco®
Oracle
CompTIA
Checkpoint
ISC
EC-Council
EXIN
Fortinet
ITIL®
Juniper
Microsoft
VMware
Avaya
SAP
Google
Salesforce
Amazon
Palo Alto Networks
All Vendors
  2. Home
  3. Exams
  4. Oracle
  5. 1Z0-062

Free Oracle 1Z0-062 Exam Questions (page: 5)

Page 5 of 87
PDF with 419 Questions

Examine the contents of SQL loader control file:

Which three statements are true regarding the SQL* Loader operation performed using the control file? (Choose three.)

  1. An EMP table is created if a table does not exist. Otherwise, if the EMP table is appended with the loaded data.
  2. The SQL* Loader data file myfile1.dat has the column names for the EMP table.
  3. The SQL* Loader operation fails because no record terminators are specified.
  4. Field names should be the first line in the both the SQL* Loader data files.
  5. The SQL* Loader operation assumes that the file must be a stream record format file with the normal carriage return string as the record terminator.

Answer(s): A,B,E

Explanation:

A: The APPEND keyword tells SQL*Loader to preserve any preexisting data in the table. Other options allow you to delete preexisting data, or to fail with an error if the table is not empty to begin with.
B (not D):
Note:
* SQL*Loader-00210: first data file is empty, cannot process the FIELD NAMES record Cause: The data file listed in the next message was empty. Therefore, the FIELD NAMES FIRST FILE directive could not be processed.
Action: Check the listed data file and fix it. Then retry the operation
E: * A comma-separated values (CSV) (also sometimes called character-separated values, because the separator character does not have to be a comma) file stores tabular data (numbers and text) in plain-text form. Plain text means that the file is a sequence of characters, with no data that has to be interpreted instead, as binary numbers. A CSV file consists of any number of records, separated by line breaks of some kind; each record consists of fields, separated by some other character or string, most commonly a literal comma or tab. Usually, all records have an identical sequence of fields.
* Fields with embedded commas must be quoted.
Example:
1997, Ford, E350, "Super, luxurious truck"
Note:
* SQL*Loader is a bulk loader utility used for moving data from external files into the Oracle database.



Which two are true concerning a multitenant container database with three pluggable database? (Choose two.)

  1. All administration tasks must be done to a specific pluggable database.
  2. The pluggable databases increase patching time.
  3. The pluggable databases reduce administration effort.
  4. The pluggable databases are patched together.
  5. Pluggable databases are only used for database consolidation.

Answer(s): C,D



Examine the following command:
CREATE TABLE (prod_id number(4),
Prod_name varchar2 (20),
Category_id number(30),
Quantity_on_hand number (3) INVISIBLE);
Which three statements are true about using an invisible column in the PRODUCTS table? (Choose three.)

  1. The %ROWTYPE attribute declarations in PL/SQL to access a row will not display the invisible column in the output.
  2. The DESCRIBE commands in SQL *Plus will not display the invisible column in the output.
  3. Referential integrity constraint cannot be set on the invisible column.
  4. The invisible column cannot be made visible and can only be marked as unused.
  5. A primary key constraint can be added on the invisible column.

Answer(s): A,B,E

Explanation:

AB: You can make individual table columns invisible. Any generic access of a table does not show the invisible columns in the table. For example, the following operations do not display invisible columns in the output:
* SELECT * FROM statements in SQL
* DESCRIBE commands in SQL*Plus
* %ROWTYPE attribute declarations in PL/SQL
* Describes in Oracle Call Interface (OCI)
Incorrect:
Not D: You can make invisible columns visible.
You can make a column invisible during table creation or when you add a column to a table, and you can later alter the table to make the same column visible.



You are about to plug a multi-terabyte non-CDB into an existing multitenant container database (CDB).
The characteristics of the non-CDB are as follows:
­ Version: Oracle Database 11g Release 2 (11.2.0.2.0) 64-bit
­ Character set: AL32UTF8
­ National character set: AL16UTF16
­ O/S: Oracle Linux 6 64-bit
The characteristics of the CDB are as follows:
­ Version: Oracle Database 12c Release 1 64-bit
­ Character Set: AL32UTF8
­ National character set: AL16UTF16
­ O/S: Oracle Linux 6 64-bit
Which technique should you use to minimize down time while plugging this non-CDB into the CDB?

  1. Transportable database
  2. Transportable tablespace
  3. Data Pump full export/import
  4. The DBMS_PDB package
  5. RMAN

Answer(s): B

Explanation:

* Overview, example:
- Log into ncdb12c as sys
- Get the database in a consistent state by shutting it down cleanly.
- Open the database in read only mode
- Run DBMS_PDB.DESCRIBE to create an XML file describing the database.
- Shut down ncdb12c
- Connect to target CDB (CDB2)
- Check whether non-cdb (NCDB12c) can be plugged into CDB(CDB2)
- Plug-in Non-CDB (NCDB12c) as PDB(NCDB12c) into target CDB(CDB2).
- Access the PDB and run the noncdb_to_pdb.sql script.
- Open the new PDB in read/write mode.
* You can easily plug an Oracle Database 12c non-CDB into a CD
B. Just create a PDB manifest file for the non-CDB, and then use the manifest file to create a cloned PDB in the CDB.
* Note that to plug in a non-CDB database into a CDB, the non-CDB database needs to be of version 12c as well. So existing 11g databases will need to be upgraded to 12c before they can be part of a 12c CDB.



Viewing page 5 of 87



Post your Comments and Discuss Oracle 1Z0-062 exam prep with other Community members:

1Z0-062 Exam Discussions & Posts