12-15-2005
Shell script call from a DB trigger
Has anybody been able to execute a shell script call from a database trigger?
If so what are the steps to execute it? Do we have any specific packages in Oracle?
Reards,
Rahul.
10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
Hello all,
I'm new to shell programming and need some help. I would like to set up a step within a shell script to trigger another shell script to run, based on the highest return code generated in the current script. For example, if the highes return code value in the current script is less... (1 Reply)
Discussion started by: mmignot
1 Replies
2. UNIX for Dummies Questions & Answers
Hi,
My program A updates a log called logA.
I have a shell script S that is responsible to send emails reading from the log.
I want to trigger execution of the script whenever there is an update to the log.
Thanks in advance. (8 Replies)
Discussion started by: cv_pan
8 Replies
3. Shell Programming and Scripting
I am new to siebel workflow manager.
Can anyone help me regarding the shell script which will trigger siebel workflow manager.
I want a sample shell script to trigger workflow manager.
Thanks in advance. (2 Replies)
Discussion started by: siri_886
2 Replies
4. Shell Programming and Scripting
Hi,
I have been assigned a job which requires me to send mails from unix(Mailx) upon on certain actions triggered in the database.
On insert/update of a certain field into one of the database tables the shell script present in Unix box responsible to send mail though mailx needs to be triggered... (7 Replies)
Discussion started by: hemant.bs11
7 Replies
5. Shell Programming and Scripting
Hi,
I basically have 2 shell scripts.
One is a shell script will get the variable value from the user. The variable is nothing but the IP of the remote system.
Another shell script is a script that does the job of connecting to the remote system using ssh. This uses a expect utility in turn.
... (2 Replies)
Discussion started by: sunrexstar
2 Replies
6. Red Hat
please help me in this script
shell script :1
***********
>cat file1.sh
#!/bin/bash
echo "this is first file"
function var()
{
a=10
b=11
}
function var_1()
{
c=12
d=13 (2 Replies)
Discussion started by: ponmuthu
2 Replies
7. UNIX for Dummies Questions & Answers
Folks,
how to trigger a shell script eg " B " from shell script eg "A" and parse different arguments to the child shell script "B" - like 0 the first time the shell script "B" is triggered and 1 the next time.
Shell script A -----------> launch shell script B with an args 0... (6 Replies)
Discussion started by: venu
6 Replies
8. Shell Programming and Scripting
Hi
I have created a shell program, which takes a series of parameters as shown in the below code. Its working good from terminal.
My program
restorejob.sh -g <NAME> -p <Path-to-search> -r <Path-to-restore>
Its working fine from bash shell.
I want to extend this functionality like... (1 Reply)
Discussion started by: rakeshkumar
1 Replies
9. Shell Programming and Scripting
Hello All,
I need immediate help in creating shell script to call archivebkup.ksh script when archive file system capacity reaches threshold value or 60%
Need to identify the unique file system that reaches threshold value.
ex:
capacity
... (4 Replies)
Discussion started by: sasikanthdba
4 Replies
10. UNIX for Beginners Questions & Answers
I'm trying to create a shell script that takes a awk script that I wrote and a filename as an argument. I was able to get that done but I'm having trouble figuring out how to keep the header of the output at the top but sort the rest of the rows alphabetically. This is what I have now but it is... (1 Reply)
Discussion started by: Eric7giants
1 Replies
LEARN ABOUT OSX
deb-triggers
deb-triggers(5) dpkg suite deb-triggers(5)
NAME
deb-triggers - package triggers
SYNOPSIS
triggers
DESCRIPTION
A package declares its relationship to some trigger(s) by including a triggers file in its control archive (i.e. DEBIAN/triggers during
package creation).
This file contains directives, one per line. Leading and trailing whitespace and everything after the first # on any line will be trimmed,
and empty lines will be ignored.
The trigger control directives currently supported are:
interest trigger-name
interest-await trigger-name
interest-noawait trigger-name
Specifies that the package is interested in the named trigger. All triggers in which a package is interested must be listed using
this directive in the triggers control file. The "noawait" variant does not put the triggering packages in triggers-awaited state.
This should be used when the functionality provided by the trigger is not crucial.
activate trigger-name
activate-await trigger-name
activate-noawait trigger-name
Arranges that changes to this package's state will activate the specified trigger. The trigger will be activated at the start of the
following operations: unpack, configure, remove (including for the benefit of a conflicting package), purge and deconfigure. The
"noawait" variant does not put the triggering packages in triggers-awaited state. This should be used when the functionality
provided by the trigger is not crucial.
If this package disappears during the unpacking of another package the trigger will be activated when the disappearance is noted
towards the end of the unpack. Trigger processing, and transition from triggers-awaited to installed, does not cause activations.
In the case of unpack, triggers mentioned in both the old and new versions of the package will be activated.
Unknown directives are an error which will prevent installation of the package.
The "-noawait" variants should always be favored when possible since triggering packages are not put in triggers-awaited state and can thus
be immediately configured without requiring the processing of the trigger. If the triggering packages are dependencies of other upgraded
packages, it will avoid an early trigger processing run and make it possible to run the trigger only once as one of the last steps of the
upgrade.
The "-noawait" variants are supported since dpkg 1.16.1, and will lead to errors if used with an older dpkg.
The "-await" alias variants are supported since dpkg 1.17.21, and will lead to errors if used with an older dpkg.
SEE ALSO
dpkg-trigger(1), dpkg(1), /usr/share/doc/dpkg-dev/triggers.txt.gz.
1.19.0.5 2018-04-16 deb-triggers(5)