@Chubler_XL,
Whenever i am executing this script through informatica command task, issue of 2 process creation for one script execution is occurring. If i execute the script at command line, one process will get created. This is irrespective of shell thats being used.
I am seeing one more process for the script execution getting created. Please see below.
I executed script /DATAWAREHOUSE/LOAD/Scripts/coldcentric.sh from a command task in Informatica worklow as shown below.
When i abort command task or workflow, i am seeing only first process among above 2 process getting killed and second process would be alive and will not get killed. It becomes orphan and kernel process id gets tagged to this process. It remains by utilizing CPU.
After aborting worklow, below still remains.
I am using a while loop in my script as shown below.
I am executing other scripts in my other ETLs and i am not facing this issue. There is no while loop like above in those scripts. Is this creating a problem ?
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 SUNOS
goto
exit(1) User Commands exit(1)NAME
exit, return, goto - shell built-in functions to enable the execution of the shell to advance beyond its sequence of steps
SYNOPSIS
sh
exit [n]
return [n]
csh
exit [ ( expr )]
goto label
ksh
*exit [n]
*return [n]
DESCRIPTION
sh
exit will cause the calling shell or shell script to exit with the exit status specified by n. If n is omitted the exit status is that of
the last command executed (an EOF will also cause the shell to exit.)
return causes a function to exit with the return value specified by n. If n is omitted, the return status is that of the last command exe-
cuted.
csh
exit will cause the calling shell or shell script to exit, either with the value of the status variable or with the value specified by the
expression expr.
The goto built-in uses a specified label as a search string amongst commands. The shell rewinds its input as much as possible and searches
for a line of the form label: possibly preceded by space or tab characters. Execution continues after the indicated line. It is an error to
jump to a label that occurs between a while or for built-in command and its corresponding end.
ksh
exit will cause the calling shell or shell script to exit with the exit status specified by n. The value will be the least significant 8
bits of the specified status. If n is omitted then the exit status is that of the last command executed. When exit occurs when executing
a trap, the last command refers to the command that executed before the trap was invoked. An end-of-file will also cause the shell to exit
except for a shell which has the ignoreeof option (See set below) turned on.
return causes a shell function or '.' script to return to the invoking script with the return status specified by n. The value will be the
least significant 8 bits of the specified status. If n is omitted then the return status is that of the last command executed. If return
is invoked while not in a function or a '.' script, then it is the same as an exit.
On this man page, ksh(1) commands that are preceded by one or two * (asterisks) are treated specially in the following ways:
1. Variable assignment lists preceding the command remain in effect when the command completes.
2. I/O redirections are processed after variable assignments.
3. Errors cause a script that contains them to abort.
4. Words, following a command preceded by ** that are in the format of a variable assignment, are expanded with the same rules as a vari-
able assignment. This means that tilde substitution is performed after the = sign and word splitting and file name generation are not
performed.
ATTRIBUTES
See attributes(5) for descriptions of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
|Availability |SUNWcsu |
+-----------------------------+-----------------------------+
SEE ALSO break(1), csh(1), ksh(1), sh(1), attributes(5)SunOS 5.10 15 Apr 1994 exit(1)