Shell script executed from Informatica ETL tool is spawning 2 processes for one script
Hi,
I am having a shell script which has a while loop as shown below.
I am executing this script from Informatica ETL tool command task from where we can execute UNIX commands/scripts. When i do that, i am seeing 2 processes getting started for one script execution.
When i execute the same script through unix command line, i can see only one process created.
Anybody has any idea on why 2 processes are getting created for one script execution through Informatica ETL tool ?
thanks
Last edited by Scott; 05-20-2013 at 05:18 PM..
Reason: Code tags
Hi there,
I have a shell script which I need to run it from two different places on the same server, are there any specific rules I need to apply? What is the best practice to achieve this task.
Regards (5 Replies)
Hi all,
I am not sure whether this is the right place to ask this question...:)
I am working in Informatica PowerCenter 8.1.1 tool and my server is on UNIX. I have got a shell script to copy files from one folder to another.
When I run the script directly from UNIX prompt it is taking 60... (0 Replies)
Request Any one of your to provide me a script which does the following in a single unix script.
Basically Users will load data in SHARED LINK everyday, should write a UNIX SCRIPT which will ........
1) Unix script should Open the LINK (FTP)
2) Each DIRECTORY in the link contains many... (0 Replies)
Hello
I am very new to Unix scripting,
I am using informatica etl,which is schedule by tidal enterprise.
I have a scenario where assume that Tidal only knows how to run jobs at a given time and does not know how to retry.
So i want to know weather can i write a shell script such that... (1 Reply)
I made a shell script to execute a server in screen mode.
# start server
screen -d -m -S Test ./application
echo "Program Started Successfully"
than I'm executing it from php by
echo shell_exec('/home/script.sh');
and it is giving me this error.
"cannot make directory... (1 Reply)
Hi,
Script to check the ETL standards in an informatica mapping ( xml file ).
Example:
To check the naming standard of mapping .
To check the transformation naming convention.
To check the datatypes.
To the session name , it should start with s.
To check the workflow name , it should... (0 Replies)
Hi,
This is regarding a issue we are facing in informatica post session. We place a shell script in informatica job.
The shell script will need to upload a dummy file to another server.The shell script is running fine.However in informatica job not completing and throwing error
It's... (1 Reply)
Hi,
I am having a shell script on Solaris 10 which has a while loop as shown below.
#!/usr/bin/ksh
#
while
do
sleep 60
done
Name of the shell script is coldcentric.sh. I executed script /DATAWAREHOUSE/LOAD/Scripts/coldcentric.sh from a command task in Informatica worklow as... (3 Replies)
Hi
As per my requirement when I run . ./file.sh am getting the following error
-bash:ELF: command not found
when i execute as ./file.sh it is getting executed.How to resolve this.
Thanks in advance. (3 Replies)
I have bash shell script which is internally calling python script.I would like to know how long python is taking to execute.I am not allowed to do changes in python script.Please note i need to know execution time of python script which is getting executed inside shell .I need to store execution... (2 Replies)
Discussion started by: Adfire
2 Replies
LEARN ABOUT NETBSD
sleep
SLEEP(1) BSD General Commands Manual SLEEP(1)NAME
sleep -- suspend execution for an interval of time
SYNOPSIS
sleep seconds
DESCRIPTION
The sleep utility suspends execution for a minimum of seconds. It is usually used to schedule the execution of other commands (see EXAMPLES
below).
Note: The NetBSD sleep command will accept and honor a non-integer number of specified seconds. This is a non-portable extension, and its
use will nearly guarantee that a shell script will not execute properly on another system.
When the SIGINFO signal is received, the estimate of the amount of seconds left to sleep is printed on the standard output.
EXIT STATUS
The sleep utility exits with one of the following values:
0 On successful completion, or if the signal SIGALRM was received.
>0 An error occurred.
EXAMPLES
To schedule the execution of a command for 1800 seconds later:
(sleep 1800; sh command_file >& errors)&
This incantation would wait half an hour before running the script command_file. (See the at(1) utility.)
To reiteratively run a command (with csh(1)):
while (1)
if (! -r zzz.rawdata) then
sleep 300
else
foreach i (*.rawdata)
sleep 70
awk -f collapse_data $i >> results
end
break
endif
end
The scenario for a script such as this might be: a program currently running is taking longer than expected to process a series of files, and
it would be nice to have another program start processing the files created by the first program as soon as it is finished (when zzz.rawdata
is created). The script checks every five minutes for the file zzz.rawdata, when the file is found, then another portion processing is done
courteously by sleeping for 70 seconds in between each awk job.
SEE ALSO at(1), nanosleep(2), sleep(3)STANDARDS
The sleep command is expected to be IEEE Std 1003.2 (``POSIX.2'') compatible.
BSD August 13, 2011 BSD