1.

when we r doing interface/conversion which things u will

take care to improve the perfrmonce?(except bulk collect)
1.Need to check execution plan for the sql statement, need to check for full
scan or not.
If the cost is more need to reduce it based on your approach.
eg:Hints can be used, check for the join conditions.Check for the Indexes if
not create it.
-----------------------------------------------------------------------------------
----------------------
2. In conversion,u r loading the data using sql*loader,I dnt
want to use sql*loader,& i have millions of records,Id der
any way to load the data withing fraction of time
considering best performance.

We can use the external tables for bulk loading.

https://oracle-base.com/articles/9i/external-tables-9i

1.Create directory
CREATE OR REPLACE DIRECTORY ext_tab_data AS '/data';
2.Provide the permissions to the library.
3.Create the external table using below
CREATE TABLE countries_ext (
country_code VARCHAR2(5),
country_name VARCHAR2(50),
country_language VARCHAR2(50)
)
ORGANIZATION EXTERNAL (
TYPE ORACLE_LOADER
DEFAULT DIRECTORY ext_tab_data
ACCESS PARAMETERS (
RECORDS DELIMITED BY NEWLINE
FIELDS TERMINATED BY ','
MISSING FIELD VALUES ARE NULL
(
country_code CHAR(5),
country_name CHAR(50),
country_language CHAR(50)
)
)
LOCATION ('Countries1.txt','Countries2.txt')
)
PARALLEL 5
REJECT LIMIT UNLIMITED;

3. When u r doing conversion,that using sql*loader u r

loading data into staging table,u r writing control file bt
I dnt want to use sql*loader,when u r creating con prog that
time can we pass all values from flat file using
paramere,valuset?how?

4. In flat file u got 50 records,out of 50 ,30 records are

proceesed & inserted into base table,after taht clien
understood that 1 item having wrong name e.g insted of ABC
he given DCE, so can we delete?hw?(client permission is der)

i have lot of wrong item name randomly spreaded,can we

delete it?hw?
5.after doing validation hw u will follow approach to error
out records?if i want to send all the error out records to
client daily,whats ur approach?

6. In outbound interface is der any way to load the

data(large data-millions of records) except UTL_FILE package?

7. what is parsing?

8. In technical doc.s which section will mention?except code?

9. Do u have any idea about code depository tool?

10.whats is performance tunning,DB link?

11, How u will do RMA?

12.UTL File:
This easy writing to the alert log is accomplished by using Oracle's utl_file
package. The Oracle utl_file package allows Oracle SQL and PL/SQL to read and write
directly from flat files on the server.

Writing custom messages to the Oracle alert log requires the following steps:

1 - Locate the background dump directory (the location of the alert log).
2 - Set the utl_file_dir initialization parameter.
3 - Execute utl_file.fopen to open the file for write access.
4 - Use dbms_output.put_line to write the custom message to the alert log.
5 - Execute utl_file.fclose to close the file
-- ******************************************************
-- Gather the location of the alert log directory
-- ******************************************************

select
name into :alert_loc
from
v$parameter
where
name = 'background_dump_destination';
-- ******************************************************
alter system set utl_file_dir = ':alert_log');

-- ******************************************************
-- Open the alert log file for write access
-- ******************************************************
utl_file.fopen(':alert_log','alertprod.log','W');

-- ******************************************************
-- Write the custom message to the alert log file
-- ******************************************************
dbms_output.put_line('invalid_application_error');

-- ******************************************************
-- Close the alert log file
-- ******************************************************
utl_file.fclose(':alert_loc');

Oracle lets a database program write to flat files using the utl_file utility
FILE SYSTEM 3