![]() ![]() An example of the flow of a SQL*Loader session is shown in Figure 6-1. The output of SQL*Loader is an Oracle database (where the data is loaded), a log file, a bad file, and potentially, a discard file. ![]() See Chapter 11.Ī typical SQL*Loader session takes as input a control file, which controls the behavior of SQL*Loader, and one or more datafiles. While conventional path loading is very flexible, direct path loading provides superior loading performance. Use either conventional or direct path loading. Use secondary datafiles for loading LOBs and collections. Load arbitrarily complex object-relational data. Generate sophisticated error reports, which greatly aid troubleshooting. Load data from disk, tape, or named pipe. Use the operating system's file system to access the datafiles. Generate unique sequential key values in specified columns. Manipulate the data before loading it, using SQL functions. Selectively load data (you can load records based on the records' values). ![]() Load data into multiple tables during the same load session. Load data from multiple datafiles during the same load session. This means that you can run the SQL*Loader client on a different system from the one that is running the SQL*Loader server. You can use SQL*Loader to do the following: It has a powerful data parsing engine that puts little limitation on the format of the data in the datafile. SQL*Loader loads data from external files into tables of an Oracle database. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |