External tables in 9i and 10g provide a convenient, seamless way to move data in and out of the database, integrating SQL*Loader and Data Pump functionality with the power, scriptability and ease of SQL statements.
Post details about virtualization; Base OS name version, guest OS name version, and name version Virtual Machine s/w Show us what you did (if you tried it yourself) and how Oracle responded (copy paste your SQL*Plus session including errors and/or why the result is not.ISO Week 7 doesn't answer the second condition, either, since February 8, 2009 is the last day of ISO Week 6: SQL with date_wk as ( 2 select 'rrrr 'MM/DD/rrrr rownum - 4 dt 3 from dual 4 connect by level 366 5 6 wk_dt.Even if your question hasn't been answered here, chances are that on other websites someone already has posted an answer.It's harder to read and gives the impression you're shouting.Post results for Oracle rdbms by invoking following SQL select * from vversion By doing so, you'll avoid reactions using features you can't use.Home other suggestions Feedback oraFAQ Forum Guide ( ) 14 Votes, oraFAQ Forum Guide message #262537.In 9i, only read operations were permitted; in 10g, you can also write out data to an external table, although you can't write to an existing table.If you feel that a message is not admissible for some reason (offending language/opinions, personal attacks.SQL create table empl_info as 2 (select empl_id, last_name, first_name, ssn, get_bday_from_ssn (ssn) birth_dt 3* from xtern_empl_rpt) SQL / Table created.Choose a topic title that makes sense clearly states problem to be solved.We don't have all the information you have.
The log file - and the "bad" and "discard" files - will have been written to the directory you specified as the "default directory" in your create table statement, and the file names default to tablename_ospid : ls -l total 16 -rw-r-r- 1 oracle oinstall.
Commercial posts are admitted only in the Marketplace Forum.
External tables are largely used as a convenient way of moving data into and out of the database.
Let's look at both of them and see what differences they contain and how they can throw the listed assumptions 'out of the window'.
As a corollary, do not post a link to your site or blog unless it answers the question.
They ARE different in how they define Week number 1 and that can throw a 'monkey wrench' into any methodology one could implement to answer the above listed question.
How to ask smart questions Posting guidelines Posting guidelines Theory Have the courtesy to write in plain English; it is not the first language of most of the participants to this forum, but that is no excuse for poor or non-existent punctuation.While there are some behaviour differences and restrictions, you can think of external tables as a convenient, SQL-based way to use SQL*Loader and Data Pump functionality.The difference between the code blocks below is clear: First a block without proper tags, you'll notice that it is not that readable: declare cursor yourcursor IS select yourcolumn, another_column from yourtable where some_column betweennd some_other sysdate; begin FOR a_record IN yourcursor loop do_something_here;.A lot of people don't spend that much time on the forum and unclear posts will be skipped more often because they take a lot more time to decipher.The key difference is that you must specify the access driver, oracle_datapump, since the access driver defaults baby kön prognos far to oracle_loader.Now, that may seem obvious since this site is called Oracle FAQs, but we get quite a few questions about Access and MS SQL Server here - and SQL between databases is not always compatible - so please ask any non-Oracle questions elsewhere.Oracle uses SQL*Loader functionality, through the oracle_loader access driver to move data from the flat file into the database; it uses a Data Pump access driver to move data out of the db into a file in an Oracle-proprietary format, and back into the database.Selecting data from the table will still fail if the maximum number of rejects is exceeded, just as in SQL*Loader.