07-29-2019
what happens is that I have this call to the procedure, and this one returned me a code, that code when closing the connection to the bbdd I need to rescue it and use that code in the shell
10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
Hi,
I am trying to pass some of the variables in my shell scripts to the sqlplus call and use them as parameters.
For example, I would like to replace the 'SAS', and '20050612' with $var1 and $var2, respectively, how can I do that?
--------------------------------------------------------... (1 Reply)
Discussion started by: Jtrinh
1 Replies
2. Shell Programming and Scripting
Hi,
I am writing a ksh script which will use sqlplus to run a sql and pass 2 variables as the SQL request. In the ksh script, I have 2 variables which are $min_snap and $max_snap holding 2 different numbers.
Inside the same script, I am using SQLPLUS to run an Oracle SQL script,... (6 Replies)
Discussion started by: rwunwla
6 Replies
3. UNIX for Advanced & Expert Users
hi fellows,
can any body tell me how to pass unix variables to oracle
code is...
#! /bin/ksh
echo ENTER DATE VALUE's
read START_DATE END_DATE
sqlplus xyx/abc@oracle
select * from table1 where coloumn1 between $START_DATE and $END_DATE;
is this is correct way...........
Thanks in... (1 Reply)
Discussion started by: chiru
1 Replies
4. Shell Programming and Scripting
Hi,
Currently i have a .sql file 1.sql.
I need to pass that as a parameter through a shell script to the sqlplus inside the same shell script.
How I should I do.can anyone help me pls.
I have an req where I need to send the .sql file and the place where the script has to create a .csv... (9 Replies)
Discussion started by: Hemamalini
9 Replies
5. Shell Programming and Scripting
if
then
# mail -s "Import failed file does not exist" sanjay.jaiswal@xyz.com
echo "FILE does not exist"
exit 1
fi
echo "FILE EXIST"
size=-1
set $(du /export/home/oracle/nas/scott21.dmp.gz)
while
do
echo "Inside the loop"
size=$1
set $(du... (1 Reply)
Discussion started by: sanora600
1 Replies
6. Shell Programming and Scripting
I have a script that "runs" a script. For example:
./runscript.ksh pcnmc01.ksh
runscript puts pcnmc01.ksh into the background with log output going to the logfile.
After executing the command, I get this output:
Running script in the background: pcnmc01.ksh
Logfile:... (2 Replies)
Discussion started by: Eben Yong
2 Replies
7. Shell Programming and Scripting
Gurus,
The issue I'm having is that my Shell won't accept SQL parameters properly......
Here's they way I'm running it....
applmgr@ga006hds
=> sh CW_MigrationDeployScript.sh apps <appspwd> <SID> '01-JAN' '31-MAR'
The process just hangs not submitting the SQL job...
... (3 Replies)
Discussion started by: WhoDatWhoDer
3 Replies
8. Shell Programming and Scripting
echo "set echo off"; echo "set feedback off"; echo "set linesize 4000"; echo " set pagesize 0"; echo " set sqlprompt ''"; echo " set trimspool on";
Select statement is mentioned below
echo "select res.ti_book_no from disney_ticket_history res where res.ti_status =${STATUS} and... (7 Replies)
Discussion started by: aroragaurav.84
7 Replies
9. Programming
i have file in which i have employee id are there and every time number of employee id are different in file means number of count of employee id in file are every time different.
343535435
365765767
343534543
343543543
i want to pass this file to sqlplus
and sql command is
... (7 Replies)
Discussion started by: pallvi_mahajan
7 Replies
10. Shell Programming and Scripting
Hi Team,
I am trying to run a sqlplus script against several databases via a FOR/LOOP and also passing the loop variable to a sqlplus script I am calling, as follows:
#!/bin/bash
export ORACLE_SID=plgc1
export ORACLE_HOME=/opt/oracle/product/11.2.0.2/db_1
export... (1 Reply)
Discussion started by: jonnyd
1 Replies
LEARN ABOUT FREEBSD
rescue
RESCUE(8) BSD System Manager's Manual RESCUE(8)
NAME
rescue -- rescue utilities in /rescue
DESCRIPTION
The /rescue directory contains a collection of common utilities intended for use in recovering a badly damaged system. With the transition
to a dynamically-linked root beginning with FreeBSD 5.2, there is a real possibility that the standard tools in /bin and /sbin may become
non-functional due to a failed upgrade or a disk error. The tools in /rescue are statically linked and should therefore be more resistant to
damage. However, being statically linked, the tools in /rescue are also less functional than the standard utilities. In particular, they do
not have full use of the locale, pam(3), and nsswitch libraries.
If your system fails to boot, and it shows a prompt similar to:
Enter full pathname of shell or RETURN for /bin/sh:
the first thing to try running is the standard shell, /bin/sh. If that fails, try running /rescue/sh, which is the rescue shell. To repair
the system, the root partition must first be remounted read-write. This can be done with the following mount(8) command:
/rescue/mount -uw /
The next step is to double-check the contents of /bin, /sbin, and /usr/lib, possibly mounting a FreeBSD rescue or ``live file system'' CD-ROM
(e.g., disc2 of the officially released FreeBSD ISO images) and copying files from there. Once it is possible to successfully run /bin/sh,
/bin/ls, and other standard utilities, try rebooting back into the standard system.
The /rescue tools are compiled using crunchgen(1), which makes them considerably more compact than the standard utilities. To build a
FreeBSD system where space is critical, /rescue can be used as a replacement for the standard /bin and /sbin directories; simply change /bin
and /sbin to be symbolic links pointing to /rescue. Since /rescue is statically linked, it should also be possible to dispense with much of
/usr/lib in such an environment.
In contrast to its predecessor /stand, /rescue is updated during normal FreeBSD source and binary upgrades.
FILES
/rescue Root of the rescue hierarchy.
SEE ALSO
crunchgen(1), crash(8)
HISTORY
The rescue utilities first appeared in FreeBSD 5.2.
AUTHORS
The rescue system was written by Tim Kientzle <kientzle@FreeBSD.org>, based on ideas taken from NetBSD. This manual page was written by
Simon L. Nielsen <simon@FreeBSD.org>, based on text by Tim Kientzle <kientzle@FreeBSD.org>.
BUGS
Most of the rescue tools work even in a fairly crippled system. The most egregious exception is the rescue version of vi(1), which currently
requires that /usr be mounted so that it can access the termcap(5) files. Hopefully, a failsafe termcap(3) entry will eventually be added
into the ncurses(3) library, so that /rescue/vi can be used even in a system where /usr cannot immediately be mounted. In the meantime, the
rescue version of the ed(1) editor can be used from /rescue/ed if you need to edit files, but cannot mount /usr.
BSD
July 23, 2003 BSD