Hi ,
I want to pass parameters from a shell script to a sql script and use the parameter in the sql query ..and then I want to spool a particular select query on to my unix box... for 4 different locations by writing only one sql script
Right now no file is generated on the unix box...it is a... (2 Replies)
I have a script which connects to different database servers using sqlplus. Is there a way by which I can run a shell command on that host from sqlplus?
I know about 'host' command but it runs script on the local machine where the original script is running. Is there a way to run command on the... (9 Replies)
i'm having real problems retrieving the returncode of my sqlplus-call. I found a lot of informations on the net, but havn't been able to get it running so far, so now i ask for some help ;)
I do start the sqlplus out of my shell script with the parameters stored in the proc_clips.sql, which is... (6 Replies)
Can anybody help me out in sending parameters from sql*plus script to unix shell script without using flat files..
Initially in a shell script i will call sql*plus and after getting some value from some tables, i want that variable value in unix shell script. How can i do this?
Please tell me... (2 Replies)
Hi,
I am writing a script to test database connection. If the first try fails, it will wait for 1 minutes and then try again. The script is as following:
........
for i in $ORACLE_SID
do
$ORACLE_HOME/bin/sqlplus $username/$password@$i <<! >/dev/null
select * from tab;
exit
if ; then... (3 Replies)
Hi,
I need help urgently for following issue. Pls help me to resolve this issue.
I am calling sql script file(file1.sql) from UNIX Shell Script(script1.ksh) using sql plus and trying to create flat file that contains all records returned from SQL query in SQL script(file1.sql)
I given... (6 Replies)
Hi All,
How i will use sqlplus in shell script?
Can any one provide sample code which explain following:
1. Connect to oracle DB
2. Exceute select * from tablename
3. Release connection to the DB
4. Append output in file everytime when query executes.
Thanks in advance (1 Reply)
sql_rows=`sqlplus -s / <<EOF
set heading off
set pagesize 1000
set tab off
set linesize 120 wrap off
column "Path" format a15
--column "No_Of_files" format a10
select tablespace_name, substr(file_name,1,instr(file_name,'/',1,2)) as "Path" , count(*) as "No_Of_files" from dba_data_files
... (7 Replies)
Hi All,
Please let me know what i am missing in the following code (part of my script)
Schemas=(AWQM WFCONTROLLER PROVCO PRISM)
for s in "${Schemas}"
do
sch="${s}_$tol"
if || ;then
echo "This is AD or TD region"
sqlplus -s $sch/$tpwd@$ttns <<EOF... (7 Replies)
Discussion started by: pvmanikandan
7 Replies
LEARN ABOUT DEBIAN
osql
osql(1) FreeTDS Utilities osql(1)NAME
osql - utility to test FreeTDS connections and queries
SYNOPSIS
osql -S dsn -U username -P password [-I ini_dir]
DESCRIPTION
osql is a diagnostic tool provided as part of FreeTDS. It is a Bourne shell script that checks and reports on your configuration files. If
everything checks out OK, it invokes isql.
osql works only with the isql that comes with unixODBC.
OPTIONS -S dsn the Data Source Name to which to connect, as known to odbc.ini.
-U username
database login name.
-P password
database password.
-I ini_dir
override odbc.ini file location.
EXAMPLE
If you have an odbc.ini with a section like this:
[myDSN]
servername = myserver
TDS_Version = 5.0
You would invoke osql as:
osql -S myDSN [...]
NOTES
If you can connect with "osql -S servername -U user -P passwd", your FreeTDS ODBC installation is working.
osql guesses where unixODBC might look for its odbc.ini by examining the binary. This is not always an effective approach. If it doesn't
work, you'll receive a report of candidate strings. Kindly pass along the output to help improve the guessing.
If osql cannot intuit your odbc.ini directory, you can force the issue with the -I option. However, you're instructing osql what to test,
not where unixODBC will eventually look. Your override is therefore only as good as you are. Look carefully at the error output before
overriding.
If you have suggestions for ways to make osql more useful as a diagnostic tool, please post them to the FreeTDS mailing list.
HISTORY
osql first appeared in FreeTDS 0.65.
AUTHORS
The osql utility was written by James K. Lowden
doc 13 November 2011 osql(1)