Hi, in your code there are some errors: this code mybe useful for you.
First create a bash
in the sql file:
then execute the bash, passing as first parameter the file: hope I helped you.
If this works try also the bipinajith solution, that result more fast, but not applicable if the list is very long.
Hi
Does any one have any idea on uploading the data using Unix Shell script from text file to Oracle database.
Requirement:-
1. Need to connect to Oracle database from Unix Shell script.
2. Need to pick Text file from some location on Unix Box.
3. Need to upload the data from text file to... (6 Replies)
Hi all,
I have a data like,
0,R001,2,D
this wants to be loaded into a oracle database table.
Pl let me know how this has to be done.
Thanks in advance (2 Replies)
Hi All,
I have a linux centos instance which has a dump file. I need to import the dump file to the oracle server which is located at some remote location. I have installed the oracle client on my machine and I am able to connect to the remote oracle server.
Now how to import the dump to the... (3 Replies)
Hi All,
I am facing one problem related to importing Oracle Dump file.
We have two different version of AIX boxes with oracle (version 10.2.0.4.0) installed.
On one AIX box (version 6.1) we are creating oracle dump file (*.dmp) using oracle exp utility and importing it onto another AIX box... (1 Reply)
Hi,
Is it possible to pass oracle connection information from a configuration file and use that to connect to oracle database in my unix shell scripts. Following is the scenario:
(1) I would like to save oracle connection string details in a configuration file (ex., dbconfig.txt)
(2) from my... (6 Replies)
1. The problem statement, all variables and given/known data:
are the oracle dump files compatible to direct import into db2?
I already tried many times but it always truncated results.
anyone can help/ advice or suggest?
2. Relevant commands, code, scripts, algorithms:
exp... (3 Replies)
I am facing issue related to performance of one customized application running on RHEL 5.9. The application stalls for some unknown reason that I need to track. For that I require some tool or shell scripts that can monitor the CPU usage statistics (what we get in TOP or in more detail by other... (6 Replies)
Dear Team,
please help me to solve this problem using Linux command. I want to dump this data into an excel sheet,
Suppose I have a string like:
ABC
PQR
XYZ
ASD
then I expect output as a
ABC XYZ
PQR ASD (3 Replies)
Discussion started by: Shubham1182
3 Replies
LEARN ABOUT DEBIAN
dh_installinit
DH_INSTALLINIT(1) Debhelper DH_INSTALLINIT(1)NAME
dh_installinit - install init scripts and/or upstart jobs into package build directories
SYNOPSIS
dh_installinit [debhelperoptions] [--name=name] [-n] [-R] [-r] [-d] [--params]
DESCRIPTION
dh_installinit is a debhelper program that is responsible for installing init scripts with associated defaults files, as well as upstart
job files into package build directories.
It also automatically generates the postinst and postrm and prerm commands needed to set up the symlinks in /etc/rc*.d/ to start and stop
the init scripts.
FILES
debian/package.init
If this exists, it is installed into etc/init.d/package in the package build directory.
debian/package.default
If this exists, it is installed into etc/default/package in the package build directory.
debian/package.upstart
If this exists, it is installed into etc/init/package.conf in the package build directory.
OPTIONS -n, --noscripts
Do not modify postinst/postrm/prerm scripts.
-o, --onlyscripts
Only modify postinst/postrm/prerm scripts, do not actually install any init script, default files, or upstart job. May be useful if the
init script or upstart job is shipped and/or installed by upstream in a way that doesn't make it easy to let dh_installinit find it.
-R, --restart-after-upgrade
Do not stop the init script until after the package upgrade has been completed. This is different than the default behavior, which
stops the script in the prerm, and starts it again in the postinst.
This can be useful for daemons that should not have a possibly long downtime during upgrade. But you should make sure that the daemon
will not get confused by the package being upgraded while it's running before using this option.
-r, --no-restart-on-upgrade
Do not stop init script on upgrade.
--no-start
Do not start the init script on install or upgrade, or stop it on removal. Only call update-rc.d. Useful for rcS scripts.
-d, --remove-d
Remove trailing d from the name of the package, and use the result for the filename the upstart job file is installed as in etc/init/ ,
and for the filename the init script is installed as in etc/init.d and the default file is installed as in etc/default/ . This may be
useful for daemons with names ending in d. (Note: this takes precedence over the --init-script parameter described below.)
-uparams --update-rcd-params=params
-- params
Pass params to update-rc.d(8). If not specified, defaults will be passed to update-rc.d(8).
--name=name
Install the init script (and default file) as well as upstart job file using the filename name instead of the default filename, which
is the package name. When this parameter is used, dh_installinit looks for and installs files named debian/package.name.init,
debian/package.name.default and debian/package.name.upstart instead of the usual debian/package.init, debian/package.default and
debian/package.upstart.
--init-script=scriptname
Use scriptname as the filename the init script is installed as in etc/init.d/ (and also use it as the filename for the defaults file,
if it is installed). If you use this parameter, dh_installinit will look to see if a file in the debian/ directory exists that looks
like package.scriptname and if so will install it as the init script in preference to the files it normally installs.
This parameter is deprecated, use the --name parameter instead. This parameter is incompatible with the use of upstart jobs.
--error-handler=function
Call the named shell function if running the init script fails. The function should be provided in the prerm and postinst scripts,
before the #DEBHELPER# token.
NOTES
Note that this command is not idempotent. dh_prep(1) should be called between invocations of this command. Otherwise, it may cause multiple
instances of the same text to be added to maintainer scripts.
SEE ALSO debhelper(7)
This program is a part of debhelper.
AUTHORS
Joey Hess <joeyh@debian.org>
Steve Langasek <steve.langasek@canonical.com>
9.20120909 2012-04-10 DH_INSTALLINIT(1)