How do I narrow my search results?
After you submit your search query:
- On the Refine Search results page, select one or more categories of products or services from the left sidebar.
- Then for a category with search results, click Select to choose your product and release filters, and then click OK.
For search queries that contain multiple words, surround the query with quotes, and then resubmit your query. Example: "database cloud service"
How do I find the documentation for my product or service?
From the home page, click the technology categories for your products or services. If you do not know which category to pick, try the following features:
- Click the Find a product tab and search for your product or service.
- Click Browse All Products & Services at the bottom of the home page to view an alphabetical listing of products and services.
- Apple Safari: Version 6
- Google Chrome: Version 29 and later
- Mozilla Firefox: Version 24 and later
- Microsoft Internet Explorer: Version 9 and later
Discontinued Direct Path Loads → In a direct path load, the behavior of a discontinued load varies depending on the reason the load
Direct Path Loads → A direct path load parses the input records according to the field specifications, converts the … takes place. Direct path load is much faster than conventional path load, but entails several restrictions.
Load Discontinued Because Maximum Number of Errors Exceeded → If the maximum number of errors is exceeded, then SQL*Loader stops loading records into any table and the work done to that point is committed. This means that when you continue the load, the value you specify for the SKIP parameter may be different for different tables. SQL*Loader reports the value for the SKIP parameter only if it is the same for all tables.
Parallel Direct Path → A parallel direct path load allows multiple direct path load sessions to concurrently load the same … data segments (allows intrasegment parallelism). Parallel direct path is more restrictive than … direct path. See Also: \" Parallel Data Loading Models
Load Discontinued Because a Ctrl+C Was Issued → If SQL*Loader is in the middle of saving data when a Ctrl+C is issued, then it continues to do the save and then stops the load after the save completes. Otherwise, SQL*Loader stops the load without committing any work that was not committed already. This means that the value of the SKIP parameter will be the same for all tables.
Load Discontinued Because of Space Errors → multiple INTO TABLE statements in the control file, then SQL*Loader loads data already read from the data
Load Discontinued Because of Fatal Errors → If a fatal error is encountered, then the load is stopped and no data is saved unless ROWS was specified at the beginning of the load. In that case, all data that was previously committed is saved. SQL*Loader reports the value for the SKIP parameter only if it is the same for all tables.
Conventional Path Loads, Direct Path Loads, and External Table Loads → SQL*Loader provides the following methods to load data: Conventional Path Loads Direct Path Loads External Table Loads
12 Conventional and Direct Path Loads → Load Direct Path Load Using Direct Path Load Optimizing Performance of Direct Path Loads Optimizing … Direct Path Loads on Multiple-CPU Systems Avoiding Index Maintenance Direct Path Loads_
Instance Recovery and Direct Path Loads → Because SQL*Loader writes directly to the database files, all rows inserted up to the last data save will automatically be present in the database files if the instance is restarted. Changes do not need to be recorded in the redo log file to make instance recovery possible. If an instance failure occurs, then the indexes being built may be left in an Index Unusable state. Indexes that are Unusable
Restrictions on Parallel Direct Path Loads → The following restrictions are enforced on parallel direct path loads: Neither local nor global … disabled on parallel direct path loads. You do not have to take any action to disable them. SQL*Loader … is used If a parallel direct path load is being
Direct Path Loads, Integrity Constraints, and Triggers → section discusses the implications of using direct path loads with respect to these features. … with the direct path, SQL*Loader disables some integrity constraints and all database triggers. This … With the conventional path load method, arrays of rows are inserted with standard SQL
Parameters for Parallel Direct Path Loads → When you perform parallel direct path loads, there are options available for specifying attributes … and STORAGE parameters. These parameters are valid only for parallel loads.
Optimizing Performance of Direct Path Loads → You can control the time and temporary storage used during direct path loads. To minimize time … Set DB_UNRECOVERABLE_SCN_TRACKING=FALSE. Unrecoverable (nologging) direct writes are tracked in the … control file by periodically storing the SCN and Time of the last direct write. If these updates to
Data Recovery During Direct Path Loads → SQL*Loader provides full support for data recovery when using the direct path load method. There
Media Recovery and Direct Path Loads → loaded data when using the direct path, making media recovery possible. If redo log archiving is not … data loaded with the conventional path: Restore the most recent backup of the affected database file
Data Conversion During Direct Path Loads → During a direct path load, data conversion occurs on the client side rather than on the server side
Setting Up for Direct Path Loads → To prepare the database for direct path loads, you must run the setup script, catldr. sql, to … loads to. You can run this script during database installation if you know then that you will be doing direct loads. … create the necessary views. You need only run this script once for each
Restrictions on Using Direct Path Loads → … This is because in direct path loads there is no SQL being generated to fetch the next value since direct path does not generate INSERT statements. … The following conditions must be satisfied for you to use the direct path load method: Tables to be … perform
Using the FILE Parameter to Specify Temporary Segments → To allow for maximum I/O throughput, Oracle recommends that each concurrent direct path load