[ Pobierz całość w formacie PDF ]
.The following words must beenclosed in double quotation marks to be used as a name for a table or column:SQL*Loader Reserved Words A-1 AND FLOAT RECOVERABLEAPPEND FORMAT REENABLEBADFILE GENERATED REPLACEBADDN GRAPHIC RESUMEBEGINDATA INDDN SEQUENCEBLANKS INDEXES SINGLEROWBLOCKSIZE INFILE SKIPBY INSERT SMALLINTBYTEINT INTEGER SORTDEVTCHAR INTO SORTEDCHARACTERSET LAST SORTNUMCONCATENATE LOAD SQL/DSCONSTANT LOG STORAGECONTINUE_LOAD MAX STREAMCONTINUEIF MLSLABEL SYSDATECOUNT NEXT TABLEDATA NO TERMINATEDDATE NULLCOLS THISDECIMAL NULLIF TRAILINGDEFAULTIF OPTIONALLY TRUNCATEDELETE OPTIONS UNLOADDISABLED_CONSTRAINTS PARALLEL UNRECOVERABLEDISCARDDN PART USINGSDISCARDFILE PARTITION VARCHARDISCARDMAX PIECED VARGRAPHICDISCARDS POSITION VARIABLEDOUBLE PRESERVE WHENENCLOSED RAW WHITESPACEEXCEPTIONS READBUFFERS WORKDDNEXTERNAL RECLEN YESFIELDS RECNUM ZONEDFIXED RECORDA-2 Oracle8 Server Utilities A P P E N D I XB DB2/DXT User NotesThis appendix describes differences between SQL*Loader DDL syntax andDB2 Load Utility/DXT control file syntax.The topics discussed include:" SQL*Loader Extensions to the DB2 Load Utility" Using the DB2 RESUME Option" Inclusions for Compatibility" Restrictions" SQL*Loader Syntax with DB2-compatible StatementsDB2/DXT User Notes B-1 SQL*Loader Extensions to the DB2 Load UtilitySQL*Loader can use any DB2 Load Utility control file.SQL*Loader also offersnumerous extensions to the DB2 loader by supporting the following features:" The DATE datatype" The automatic generation of unique sequential keys" The ability to specify the record length explicitly" Loading data from multiple data files of different file types" Fixed-format, delimited-format, and variable-length records" The ability to treat a single physical record as multiplelogical records" The ability to combine multiple physical records into one logical recordvia CONCATENATE, CONTINUEIF NEXT, and CONTINUEIF THIS(IBM supports only CONTINUEIF THIS)" More thorough error reporting" Bad file (DB2 stops on first error)" Control over the number of records to skip, the number to load, and thenumber of errors to allow" ANDed WHEN clause" FIELDS clause for default field characteristics" Direct path loads" Parallel loadsB-2 Oracle8 Server Utilities Using the DB2 RESUME OptionYou can use the DB2 syntax for RESUME, but you may prefer to useSQL*Loader s equivalent keywords.See  Loading into Empty and Non-Empty Tables on page 5-27 for more details about the SQL*Loader optionssummarized below.Table A-1: DB2 Functions and Equivalent SQL*Loader OperationsDB2 SQL*Loader Options ResultRESUME NO or no INSERT Data loaded only if table is empty.RESUME clause Otherwise an error is returned.RESUME YES APPEND New data is appended to existingdata in the table, if any.RESUME NO REPLACE New data replaces existing tableREPLACE data, if any.A description of the DB2 syntax follows.If the tables you are loading alreadycontain data, you have three choices for the disposition of that data.Indicateyour choice using the RESUME clause.The argument to RESUME can beenclosed in parentheses.RESUME { YES | NO [ REPLACE ] }where:YES Appends the new rows to rows already in the table.NO Requires the table to be empty before loading.An errormessage results if the table contains rows and the run isterminated.This is the default.NO REPLACE Deletes any data in the table before loading new data.Thus, the new data will replace the old.This argumentrequires that the username invoking SQL*Loader haveDELETE privilege on the table.You cannot recover thedata that was in the table before the load, unless yousaved it using Export or something comparable.In SQL*Loader you can use one RESUME clause to apply to all loaded tablesby placing the RESUME clause before any INTO TABLE clauses.Alternatively, you can specify your RESUME options on a table-by-table basisby putting a RESUME clause after the INTO TABLE specification.TheRESUME option following a table name will override one placed earlier in thefile.The earlier RESUME applies to all tables that do not have their ownRESUME clause.DB2/DXT User Notes B-3 Inclusions for CompatibilityThe IBM DB2 Load Utility contains certain elements that SQL*Loader doesnot use.In DB2, sorted indexes are created using external files, andspecifications for these external files may be included in the load statement.For compatibility with the DB2 loader, SQL*Loader parses these options, butignores them if they have no meaning for Oracle.The syntactical elementsdescribed below are allowed, but ignored, by SQL*Loader.LOG StatementThis statement is included for compatibility with DB2.It is parsed butignored by SQL*Loader.(This LOG option has nothing to do with the log filethat SQL*Loader writes.) DB2 uses the log file for error recovery, and it mayor may not be written.SQL*Loader relies on Oracle s automatic logging, which may or may not beenabled as a warm start option.[ LOG { YES | NO } ]WORKDDN StatementThis statement is included for compatibility with DB2.It is parsed butignored by SQL*Loader.In DB2, this statement specifies a temporary file forsorting.[ WORKDDN filename ]SORTDEVT and SORTNUM StatementsSORTDEVT and SORTNUM are included for compatibility with DB2.Thesestatements are parsed but ignored by SQL*Loader.In DB2, these statementsspecify the number and type of temporary data sets for sorting.[ SORTDEVT device_type ][ SORTNUM n ]DISCARD SpecificationMultiple file handling requires that the DISCARD clauses (DISCARDDN andDISCARDS) be in a different place in the control file  next to the datafilespecification.However, when loading a single DB2 compatible file, theseclauses can be in their old position  between the RESUME and RECLENB-4 Oracle8 Server Utilities clauses [ Pobierz całość w formacie PDF ]

  • zanotowane.pl
  • doc.pisz.pl
  • pdf.pisz.pl
  • hanula1950.keep.pl

    		•