Reviewing It |
1: | What is the purpose of SQL*Loader? |
A1: | SQL*loader can load data from specifically formatted files (files with data fields in fixed locations), files where the fields have some kind of field separator such as a ':', data that is in its own definition file, or it can even load data via the Unix pipe command |
2: | Why would someone use External Tables instead of SQL*Loader? |
A2: | External tables gives the user the ability to run full SQL against the data, performing data conversions with DECODE, concatenations, and so on |
3: | Why would you want SQL*Loader to skip records? |
A3: | Perhaps there is some header information in the data file that is not to be loaded or the user is creating some test data from the middle of a data file |
4: | What are Export/Import used for? |
A4: | Export and Import can be used to move data from one Oracle instance to another, to backup a particular users data, to create test environments, and to provide incremental backup and recovery. |
Checking It |
1: | Which of the following is proper SQL*Loader command line syntax:
|
A1: | d |
2: | Data will be inserted and any data in the table will remain with which mode:
|
A2: | b |
3: | The table is expected to be empty with which mode:
|
A3: | a |
4: | INTEGER EXTERNAL is used to define numbers with decimal points? True/False |
A4: | False |
5: | A converted SQL*Loader control file to an External file puts the CREATE TABLE in a separate file with a .SQL suffix. True/False |
A5: | False, it puts it in the log file |
6: | Which of the following is NOT valid EXPORT syntax:
|
A6: | c. |
Applying It |
Independent Exercise 1:
Independent Exercise 2:
Independent Exercise 3:
3.139.239.41