Programming

Hello,

Can anyone tell me that,
How can I assign variable to shell script variable, which i need to use in INSERT INTO statement?

my shell script variables are,

Code:

 
EMPNAME=`regular expression`
EMPID=`regular expression`
EMPBDATE=`regular expression`

Now through ksh script I am connecting to database and want to use above variable values in my INSERT INTO statement.

Code:

 
INS_REC=$(sqlplus $USERID/$PASSWORD@$DATABASE << EOF 
set serveroutput on
declare
v_cnt NUMBER:=0;
name VARCHAR(6):=$EMPNAME;
id      NUMBER(6):=$EMPID;
date  NUMBER(14):=$EMPBDATE;
begin
select count (*) into v_cnt from TBL1;
dbms_output.put_line(v_cnt);
if v_cnt >= 0 then
INSERT INTO TBL1( EMP_NAME,
    EMP_ID,
    BIRTH_DATE
    )
    VALUES (
    name,
    id,
    TO_DATE (date , 'YYYYMMDDHH24MISS')
    );
end if;
EXCEPTION
     WHEN OTHERS THEN
     NULL;
end;
/
EOF)

but I am getting errors as,

Code:

ORA-06550: line 3, column 21:
PLS-00201: identifier "EMPNAME" must be declared
ORA-06550: line 3, column 9:
PL/SQL: Item ignored
ORA-06550: line 4, column 21:
PLS-00201: identifier "EMPID" must be declared
ORA-06550: line 4, column 9:
PL/SQL: Item ignored
ORA-06550: line 4, column 21:
PLS-00201: identifier "EMPBDATE" must be declared
ORA-06550: line 4, column 9:
PL/SQL: Item ignored
ORA-06550: line 18, column 25:
PL/SQL: ORA-00984: column not allowed here
ORA-06550: line 11, column 1:
PL/SQL: SQL Statement ignored

Please help me out.

IMO, you are better off to use a scripting language with built-in database support, like PERL or PHP.

I do a lot of database programming (MySQL) and use PHP (and never use KSH or other shell scripts for SQL DB support).

My whole project is in ksh script with Oracle database. I have no choice to use any other scripting as well as DB programming languages.
Please provide any solution for above problem.

Here's a very short testcase that demonstrates a technique of passing shell variables to Oracle SQL -

Code:

$
$
$ # display the content of the shell script "f36"
$ cat -n f36
    1  #!/usr/bin/bash
    2  EMPNAME="Napoleon Bonaparte"
    3  EMPID="1"
    4  EMPBDATE="15-Aug-1769"
    5  sqlplus -s test/test <<EOF
    6    INSERT INTO TBL1 (EMP_NAME, EMP_ID, BIRTH_DATE)
    7    VALUES ('$EMPNAME', $EMPID, TO_DATE ('$EMPBDATE','DD-Mon-YYYY'));
    8  EOF
$
$
$ # execute the shell script
$ ./f36
 
1 row created.
 
$
$
$ # verify that the record was inserted
$ echo "select emp_name, emp_id, to_char(birth_date, 'dd-Mon-yyyy') bdate from tbl1;" | sqlplus -s test/test
 
EMP_NAME                 EMP_ID BDATE
-------------------- ---------- -----------
Napoleon Bonaparte            1 15-Aug-1769
 
1 row selected.
 
$
$

I'll let you figure out the details of tailoring it for your scripts.

A few observations about your script:

(a) The Oracle documentation recommends the use VARCHAR2 datatype instead of VARCHAR. Check the Concepts Guide or the SQL Reference guide in the documentation set.

(b) Your "if" condition is redundant. The record count of a table is always 0 or something greater than 0. It can *never* be negative. So your "if" condition will always be true. In fact, I am not sure why you'd want to run a count(*) query before inserting a record into a table!!

(c) The exception handler "when others then null;" is a classic logical bug. That's because "when others" is a catch-all for all exceptions that you either don't know about or don't care about.

These exceptions could be something completely unrelated to your code; serious things like:

ORA-01000: maximum open cursors exceeded due to cursor leakage that could bring your Oracle database to a grinding halt,

or

ORA-1652: unable to extend temp segment by 1024 in tablespace <blah>
which means your temp tablespace is full and requires DBA intervention

or

the dreaded ORA-00600 internal kernel errors that might require you to contact Oracle support

etc. You don't want to "swallow" such exceptions (NULL; statement does exactly that). You want to raise such exceptions to your client program as soon as possible so you or your DBA could do something about it.

Instead of a NULL; there should be a RAISE; statement in "when others then" exception handler. Or better yet, leave it out altogether, and Oracle will do the escalation for you.

It's something like this - if you are on a vacation, and your house catches fire, you'd want to know that as soon as possible! You'd want to let go of your vacation and get back as soon as possible. The NULL statement gives you the impression that everything is fine and dandy, whereas you'd come back to a charred house!

Finally, Neo's suggestion is noteworthy. Small Oracle projects (such as yours apparently) that deal mainly with strings or "string-like" data may be fine with Unix shells. But as the project increases in scope and volume, and as you keep on adding more and more complex datatypes - LOBs, XML, timestamps, Collections - nested tables, varrays etc. the use of a wrapper API like Perl DBI or PHP or JDBC will make your life easier. They are very robust, well tested and bind quite tightly with complex Oracle types.

tyler_durden

Thanks for the information and your time.

still I am facing error from below code,

Code:

INSERT INTO BIOS_TRANSCODING ( EMPNAME,EMPID,EMPBDATE)
VALUES('$EMPNAME','$EMPID',TO_DATE('$EMPBDATE','YYYY-MM-DD'));

error is,

Code:

 TO_DATE("$EMPBDATE","YYYY-MM-DD")
                                                   *
ERROR at line 14:
ORA-06550: line 14, column 24:
PL/SQL: ORA-00984: column not allowed here
ORA-06550: line 7, column 1:
PL/SQL: SQL Statement ignored

For point (b), I want to check the table is exists in database or not, If it exists then only do for INSERT INTO statement, So i used if condition with select count(*) statement.
For point (c), I'll try to use raise statement instead of NULL.

Please help me out.

Post the contents of your entire script over here.

Do you have a reason to believe that someone/something will drop that table ?
If you do, then there's something seriously wrong with either your application or its security.

tyler_durden

You are better off with "echo 'junk' | sqlplus . . ." than "<<", especially with tricky shell constructs like this. Also get off "`", as $() is so much prettier, and nests! You can tinker with the echo until you like the final generated code, and then know "|" will not touch it, unlike the "<<" that expands and removes metadata.

If this simple form gets too busy:

Code:

echo '...'"$( whatever )"'...'| sqlplus . . .

then go subshell:

Code:

(
echo 'this'  # single quotes allow least change, use whenever possible
that # command output
echo "$the_other"  #double quotes allow most expansions but not globbing or removal of single quote: '
) | sqlplus . . .

---------- Post updated at 10:02 AM ---------- Previous update was at 10:00 AM ----------

Its a mind-set problem. You are not "putting $whatever into your Oracle", you are generating a hunk of text to send to an app, which happens to the the Oracle Command line client.