1. Write the connection string to a temp file. This would be your parameter file. The format is as below.
   userid=scott/tiger@
   As it is a parameter file, you can actually put all the other sqlldr parameters in there.
2. Call sqlldr with parfile parameter.
   Example : sqlldr parfile=paramfile.txt data=mydata.csv control=mytable.ctl log=mydata101.log
3. Delete the temp file

To be more clear, here’s the actual code I used.

umask 0077
PWDFILE=$(mktemp)
echo "userid=${SYS_JOB_BSS_ORACLE_UID}/${PASWD}@${SYS_JOB_BSS_ORACLE_SID}" > $PWDFILE
sqlldr parfile=$PWDFILE data=${data_file} control=${APP_CTL_FILE_NAME} log=${data_file}.log rows=100 errors=100
retCode=`echo $?`
rm $PWDFILE


I would like to explain it a bit but I realized that you won’t be here if you don’t understand what it does. If anything, the umask there just sets the permission of the temp file to be created as 077. The rest are pretty much self explanatory.

http://laurentschneider.com/wordpress/2009/05/hide-password-from-ps-output-sql-loader.html

SELECT * FROM ALL_DIRECTORIES;

The query above will display all the directories accessible to the current user. They are folders in the server where you can write your output files. For some reason, I forgot about this twice already and had to scour the web to find it. The problem is, I also forgot the keywords. So, I’m writing it now.

To register new directories, you can follow the example below.

Example
create or replace directory mydir as 'c:mydirectory';

To use, run the code below.

declare
f utl_file.file_type;
begin
f := utl_file.fopen('MYDIR', 'myfilename.txt', 'w');
utl_file.put_line(f, 'just another line text 1');
utl_file.put_line(f, 'just another line text 2');
utl_file.fclose(f);
end;

whereby
m is the base.
n is the exponent.

Example

power(36,5);

will return 1679616

Take note that this function returns NUMBER as the data type. That means the maximum value can only be 1.0 x 10^126. Later versions (10g onwards) can use binary_double as the base which makes the function output binary_double. I don’t know where you would need that large number, though. Also, if m is negative, then n must be an integer.

In case you are asking where I need it, there’s this code conversion whereby I needed to use the power function to get the value of a particular character. The exponent(n) is not fixed so I needed this function. To be specific, the function involves the pl/sql version of RowIdToRowIdNum of Siebel. I’ll post the code later.

References:

http://asktom.oracle.com/pls/asktom/f?p=100:11:0::::P11_QUESTION_ID:1594387900346571874

simple as below:

DELETE FROM my_table
WHERE mycolumn = 'mysearch';

v_rec_count := SQL%ROWCOUNT;


On this case, SQL%ROWCOUNT will return the number of affected records in the immediate preceding statement. It is the

equivalent command for @@rowcount in Sybase/SQL Server.

However in my friend’s case, the DELETE statement is part of the dynamic SQL. Obviously, we cannot use the approach

above as it is. Here’s how to capture the affected records in dynamic SQLs.


vSQL := 'DELETE FROM ' || v_SchemaName || '.' || v_TableName || ' WHERE ' || v_Conditions || ‘;’;
EXECUTE IMMEDIATE ‘BEGIN ’ || vSQL || ‘ :z := sql%rowcount; END; ’ USING OUT nRecCount ;


Basically, we have to capture the rowcount from within the dynamic sql. That means you have to pass the variable via “OUT” parameter to flow the value out of the execute immediate. You can’t just fire nRecCount := sql%rowcount after the execute immediate because with that, the last command that ran is the execute immediate. It will return 1 instead of the actual value from the dynamic sql.

Source :

https://asktom.oracle.com/pls/asktom/f?p=100:11:0::NO::P11_QUESTION_ID:497908700346519628

ALTER SEQUENCE MY_SEQUENCE_NAME
INCREMENT BY 1;


Explanation

The first SQL modifies increment number to 300. That means the next time I call the NEXTVAL, I’ll get the current number + 300. In that way, I can skip some numbers. And after achieving the purpose, I set back the increment to just 1.

This is a crudge workaround, actually. I needed to come up with a solution to a problem in production wherein the sequence number is no longer in-synch with the actual current max number in the table (due to manual insert/update).

To be clear, here’s the screenshot.


Source : http://forums.oracle.com/forums/thread.jspa?messageID=3594805


MERGE INTO tstg_idl_approach a
USING tmdb_idl_approach b
ON (a.approach_id = b.approach_id)
WHEN MATCHED THEN
UPDATE SET a.approach_code = b.approach_code ,
a.current_ind = b.current_ind
WHEN NOT MATCHED THEN
INSERT (approach_id ,
approach_code,
current_ind )
VALUES (b.approach_id ,
b.approach_code,
b.current_ind );

For further reading, I recommend visiting http://www.oracle-developer.net/display.php?id=203.

Below is the example.

SQL> DECLARE
2 x NUMBER := 0;
3 BEGIN
4 LOOP — After CONTINUE statement, control resumes here
5 DBMS_OUTPUT.PUT_LINE (‘Inside loop: x = ‘ || TO_CHAR(x));
6 x := x + 1;
7
8 IF x < 3 THEN
9 CONTINUE;
10 END IF;
11
12 DBMS_OUTPUT.PUT_LINE
13 ('Inside loop, after CONTINUE: x = ' || TO_CHAR(x));
14
15 EXIT WHEN x = 5;
16 END LOOP;
17
18 DBMS_OUTPUT.PUT_LINE (' After loop: x = ' || TO_CHAR(x));
19 END;
20 /

As our Siebel CRM here in the office still uses 10g, I have no choice but to use some other ways(i.e., logic change, big if-endif, etc.) There’s a lot of critics of this function with some saying it’s like using GOTO statement in BASIC. I find it handy, though. And I don’t think those critics ever encountered such kind of situations or have programmed a large pl/sql program in the real world.

The statement allows me to make my codes more readable and easily understandable. On top of that, it allows shorter program and easily traceable code. And so I’m happy that Oracle has added it their RDBMS starting from 11g.

Now, if the SQL script does not have exit at the end, you’ll have to do the following.

echo exit | sqlplus user/pass@connect @scriptname


This is another trivial thing that can be easily forgotten.

Dropping One Column
alter table
table_name
drop column col_name1;

Dropping Multiple Columns

alter table
table_name
drop (col_name1, col_name2);

Simple, eh?