Sponsored Content
Full Discussion: SQL and shell scripts
Top Forums UNIX for Dummies Questions & Answers SQL and shell scripts Post 302086422 by Amruta Pitkar on Wednesday 23rd of August 2006 10:14:28 PM
Old 08-23-2006
SQL and shell scripts

Initial code is modified...Can u help me with the next post.....

Last edited by Amruta Pitkar; 08-24-2006 at 03:53 AM.. Reason: I have modified the code ..no help is needed now on this issue
 

10 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

Help with GDL to SQL scripts

Hi to everyone, i want ask if someone knows about a script/program to convert the .gdl (Interbase) to .sql scripts. I wrote a little script to make it but it's very very simple, and the triggers and some code from .gdl are so difficult to me. If somebody could help me, I would very thankful. ... (0 Replies)
Discussion started by: ch4r1e5
0 Replies

2. Shell Programming and Scripting

Calling SQL scripts through Shell Script

Oracle and Scripting gurus, I need some help with this script... I am trying to add the query SELECT * FROM ALL_SYNONYMS WHERE SYNONYM_NAME = 'METADATA' in the current script.... Read the result set and look for the TABLE_NAME field. If the field is pointing to one table eg.... (18 Replies)
Discussion started by: madhunk
18 Replies

3. Shell Programming and Scripting

Running SQL Scripts from Shell script - Need insight!

I've a script that fetches various values from the database as below: #! /bin/ksh $conn="user/pwd@service_name" `sqlplus -s << $conn EOF1 @xyz.sql @pqr.sql @abc.sql EOF1` The output of the script should generate txt files containing the results from queries which are further... (6 Replies)
Discussion started by: manthasirisha
6 Replies

4. Shell Programming and Scripting

Calling SQL LDR and SQL plus scripts in a shell script

Hi- I am trying to achieve the following in a script so I can schedule it on a cron job. I am fairly new to the unix environment... I have written a shell script that reads a flat file and loads the data into an Oracle table (Table1) via SQLLDR. This Works fine. Then, I run a nested insert... (5 Replies)
Discussion started by: rajagavini
5 Replies

5. Shell Programming and Scripting

any possible solution on sql calling scripts

hi all, i have a function which will take i/p as a ddl sctipt as i/p and execute it, let function execute_sql { db_var="$1" v_cnt=`sqlplus -s XXXXX/XXXXX@aXXX << ENDSQL | sed -e "s/Connected\.//" -e "/^$/d" set pagesize 0 feedback off verify off heading off echo off serveroutput on size... (4 Replies)
Discussion started by: manas_ranjan
4 Replies

6. Shell Programming and Scripting

Not able to execute many SQL scripts within a shell script

I am using HP-UX: I have written a ksh script where I need to connect to sqlplus and execute few sql scripts. Part of this code is - sqlplus user/temp1234 <<! set serverout on set feedback off set pages 1000 set colsep , set echo off spool /home/supp1/pks/output.csv... (8 Replies)
Discussion started by: Sriranga
8 Replies

7. Shell Programming and Scripting

Execute multiple SQL scripts from single SQL Plus connection

Hi! I would like to do a single connection to sqlplus and execute some querys. Actually I do for every query one connection to database i.e echo 'select STATUS from v$instance; exit' > $SQL_FILE sqlplus user/pass@sid @$SQL_FILE > $SELECT_RESULT echo 'select VERSION from v$instance;... (6 Replies)
Discussion started by: guif
6 Replies

8. UNIX for Advanced & Expert Users

Call parallel sql scripts from shell and return status when both sql are done

Hi Experts: I have a shell script that's kicked off by cron. Inside this shell script, I need to kick off two or more oracle sql scripts to process different groups of tables. And when both sql scripts are done, I will continue in the shell script to do other things like checking processing... (3 Replies)
Discussion started by: huasheng8
3 Replies

9. UNIX and Linux Applications

how to execute multiple .sql scripts from within a shell script using sqlplus

using sqlplus I want to execute a .sql script that has dbms_output statments in rhe script. I want to write the dbms_output statements from .sql file to a log file. is this possible. thanks any help would be appreciated :wall: (1 Reply)
Discussion started by: TRS80
1 Replies

10. Shell Programming and Scripting

Issue in SQL Loader scripts

Hi, I'm planning to load the data from FLAT files into tables. Source file: more input.txt LRNO|Bale|Horsepower|NumberOfBarges|BollardPull|NumberOfCars|GasCapacity|GrainCapacity|IndicatedHorsepower|LiquidCapacity|... (6 Replies)
Discussion started by: shyamu544
6 Replies
Hook::LexWrap(3)					User Contributed Perl Documentation					  Hook::LexWrap(3)

NAME
Hook::LexWrap - Lexically scoped subroutine wrappers VERSION
This document describes version 0.23 of Hook::LexWrap. SYNOPSIS
use Hook::LexWrap; sub doit { print "[doit:", caller, "]"; return {my=>"data"} } SCOPED: { wrap doit, pre => sub { print "[pre1: @_] " }, post => sub { print "[post1:@_] "; $_[1]=9; }; my $temporarily = wrap doit, post => sub { print "[post2:@_] " }, pre => sub { print "[pre2: @_] "}; @args = (1,2,3); doit(@args); # pre2->pre1->doit->post1->post2 } @args = (4,5,6); doit(@args); # pre1->doit->post1 DESCRIPTION
Hook::LexWrap allows you to install a pre- or post-wrapper (or both) around an existing subroutine. Unlike other modules that provide this capacity (e.g. Hook::PreAndPost and Hook::WrapSub), Hook::LexWrap implements wrappers in such a way that the standard "caller" function works correctly within the wrapped subroutine. To install a prewrappers, you write: use Hook::LexWrap; wrap 'subroutine_name', pre => &some_other_sub; #or: wrap *subroutine_name, pre => &some_other_sub; The first argument to "wrap" is a string containing the name of the subroutine to be wrapped (or the typeglob containing it, or a reference to it). The subroutine name may be qualified, and the subroutine must already be defined. The second argument indicates the type of wrapper being applied and must be either 'pre' or 'post'. The third argument must be a reference to a subroutine that implements the wrapper. To install a post-wrapper, you write: wrap 'subroutine_name', post => &yet_another_sub; #or: wrap *subroutine_name, post => &yet_another_sub; To install both at once: wrap 'subroutine_name', pre => &some_other_sub, post => &yet_another_sub; or: wrap *subroutine_name, post => &yet_another_sub, # order in which wrappers are pre => &some_other_sub; # specified doesn't matter Once they are installed, the pre- and post-wrappers will be called before and after the subroutine itself, and will be passed the same argument list. The pre- and post-wrappers and the original subroutine also all see the same (correct!) values from "caller" and "wantarray". Short-circuiting and long-circuiting return values The pre- and post-wrappers both receive an extra argument in their @_ arrays. That extra argument is appended to the original argument list (i.e. is can always be accessed as $_[-1]) and acts as a place-holder for the original subroutine's return value. In a pre-wrapper, $_[-1] is -- for obvious reasons -- "undef". However, $_[-1] may be assigned to in a pre-wrapper, in which case Hook::LexWrap assumes that the original subroutine has been "pre-empted", and that neither it, nor the corresponding post-wrapper, nor any wrappers that were applied before the pre-empting pre-wrapper was installed, need be run. Note that any post-wrappers that were installed after the pre-empting pre-wrapper was installed will still be called before the original subroutine call returns. In a post-wrapper, $_[-1] contains the return value produced by the wrapped subroutine. In a scalar return context, this value is the scalar return value. In an list return context, this value is a reference to the array of return values. $_[-1] may be assigned to in a post-wrapper, and this changes the return value accordingly. Access to the arguments and return value is useful for implementing techniques such as memoization: my %cache; wrap fibonacci, pre => sub { $_[-1] = $cache{$_[0]} if $cache{$_[0]} }, post => sub { $cache{$_[0]} = $_[-1] }; or for converting arguments and return values in a consistent manner: # set_temp expects and returns degrees Fahrenheit, # but we want to use Celsius wrap set_temp, pre => sub { splice @_, 0, 1, $_[0] * 1.8 + 32 }, post => sub { $_[-1] = ($_[0] - 32) / 1.8 }; Lexically scoped wrappers Normally, any wrappers installed by "wrap" remain attached to the subroutine until it is undefined. However, it is possible to make specific wrappers lexically bound, so that they operate only until the end of the scope in which they're created (or until some other specific point in the code). If "wrap" is called in a non-void context: my $lexical = wrap 'sub_name', pre => &wrapper; it returns a special object corresponding to the particular wrapper being placed around the original subroutine. When that object is destroyed -- when its container variable goes out of scope, or when its reference count otherwise falls to zero (e.g. "undef $lexical"), or when it is explicitly destroyed ("$lexical->DESTROY") -- the corresponding wrapper is removed from around the original subroutine. Note, however, that all other wrappers around the subroutine are preserved. Anonymous wrappers If the subroutine to be wrapped is passed as a reference (rather than by name or by typeglob), "wrap" does not install the wrappers around the original subroutine. Instead it generates a new subroutine which acts as if it were the original with those wrappers around it. It then returns a reference to that new subroutine. Only calls to the original through that wrapped reference invoke the wrappers. Direct by- name calls to the original, or calls through another reference, do not. If the original is subsequently wrapped by name, the anonymously wrapped subroutine reference does not see those wrappers. In other words, wrappers installed via a subroutine reference are completely independent of those installed via the subroutine's name (or typeglob). For example: sub original { print "ray" } # Wrap anonymously... my $anon_wrapped = wrap &original, pre => sub { print "do..." }; # Show effects... original(); # prints "ray" $anon_wrapped->(); # prints "do..ray" # Wrap nonymously... wrap *original, pre => sub { print "fa.." }, post => sub { print "..mi" }; # Show effects... original(); # now prints "fa..ray..mi" $anon_wrapped->(); # still prints "do...ray" DIAGNOSTICS
"Can't wrap non-existent subroutine %s" An attempt was made to wrap a subroutine that was not defined at the point of wrapping. "'pre' value is not a subroutine reference" The value passed to "wrap" after the 'pre' flag was not a subroutine reference. Typically, someone forgot the "sub" on the anonymous subroutine: wrap 'subname', pre => { your_code_here() }; and Perl interpreted the last argument as a hash constructor. "'post' value is not a subroutine reference" The value passed to "wrap" after the 'post' flag was not a subroutine reference. "Uselessly wrapped subroutine reference in void context" (warning only) When the subroutine to be wrapped is passed as a subroutine reference, "wrap" does not install the wrapper around the original, but instead returns a reference to a subroutine which wraps the original (see "Anonymous wrappers"). However, there's no point in doing this if you don't catch the resulting subroutine reference. AUTHOR
Damian Conway (damian@conway.org) BLAME
Schwern made me do this (by implying it wasn't possible ;-) BUGS
There are undoubtedly serious bugs lurking somewhere in code this funky :-) Bug reports and other feedback are most welcome. SEE ALSO
Sub::Prepend COPYRIGHT
Copyright (c) 2001, Damian Conway. All Rights Reserved. This module is free software. It may be used, redistributed and/or modified under the same terms as Perl itself. perl v5.16.2 2013-08-25 Hook::LexWrap(3)
All times are GMT -4. The time now is 08:03 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy