UNIX for Beginners Questions & Answers

If you're running the script in post#3, you should receive a message like

Code:

bash: warning: here-document at line 1 delimited by end-of-file (wanted `$EMP_DETAILS.txt')

You should
- add the here document delimiter
- define the EMP_DETAILS variable
IF IT IS THAT what you want: mail the contents of the here document. If not, reconsider your construct. Right now, it is eating away the second mail command, which, BTW, would not send the resulting text file.

Assuming that you have made some changes to the code in post #3 in this thread (based on the comments you have received so far), please show us your current code (in CODE tags). It is hard to guess at what might be wrong if we don't know exactly what your code is doing.

please find below code which am running and Error message and advise.

Code:

FILE="scripts/EMP_FILE.txt"
#FILE="EMP_FILE.$(date +%F_%R).txt"
#touch $FILE

echo $ORACLE_HOME/bin/sqlplus
echo "======== START ============="
 
#$ORACLE_HOME/bin/sqlplus -s scott/tiger@XE  <<EOF
RESULT=`$ORACLE_HOME/bin/sqlplus -silent ${DB_USER}/${DB_DECRYPTED_PASSWORD}@${DB_CONNECTION_STRING} <<ENDA

set pagesize 0 feedback off verify off heading off echo off
column last_business_date format date
SELECT * FROM EMP WHERE DEPTNO IN(10,20);
exit;
ENDA`

echo "$RESULT" > $FILE
#sed -i 's/#^/\n/g' $FILE
sed '/#^/G' $FILE
echo "======== END ============="


## READ AND WRITE THE FILE AND TOOK THE BACKUP
#
FILE1="EMP_FILE.$(date +%F_%R).txt"
{
 while IFS= read -r line
 do
    shnfix "$line"
  done < "$FILE"
} > "emp.backup.$(date +%F_%R).txt"

##this will fetch the number of lines in the file
if [ $(wc -l < "$FILE") -gt 0 ]; then
uuencode EMP_FILE.txt EMP_FILE.txt|mailx -s  "EMPLOYEE DATA FOR DEPT 10 AND 20" "ROBIN@GMAIL.COM" 
fi

Code:

 shnfix: not found [No such file or directory]
 uuencode: not found
 mailx: not found [No such file or directory]

We would hope that you understand how to set the PATH environment variable so that your script can find the mailx, shnfix, and uuencode utilities on your system. I have never heard of shnfix, but the other two should be available on most UNIX and UNIX-like systems. The directories in which they are located, however, varies from system to system.

If is strange that you define a variable named FILE1 but never use it. It is strange that you create a file with a name similar (but sometimes not identical to the pathname assigned to FILE1), but never reference that file after it is created.

We have no idea when you should be using $FILE and when you should be using $FILE1 since we have no idea what shnfix does nor what you want to do with the contents of either of those files in the remainder of your script.

If we knew what operating system and shell you were using, we knew what shnfix does, we knew what you were trying to accomplish with your script, and we knew where the utilities that your script can't find were located; then we might be able to help you fix your script. Without all of this information, we have a MUCH lower chance of being able to fix your script than you do. We presume that you know what the utilities you are invoking are intended to do and that you know what your script is trying to do. Since we don't know those things, how do you expect us to advise you on the proper changes that would make your script do what you want it to do?

As the the query is going to run for every 15 mins, I would like to create a backup file and would like to name it as "EMP_FILE_bkp.txt"

For this it has to read the data from "EMP_FILE.txt" and Write it into "EMP_FILE_bkp.txt".

For this I was trying to write a Loop. I am not sure the command

Code:

SHNFIX

Can you help me to resove Read and write process and mail sending process.

Thanks

---------- Post updated at 03:12 PM ---------- Previous update was at 02:29 PM ----------

Don,

Please ignore my script and suggest me a new code for the below

Below is my requirement.

1.Send in email every 15 minutes from 12 to 3:30 PM. E-mail should only be sent ONLY when below Query have data return ELSE DISPLAY A MESSGAGE NO DATA EXISTED.

2. Email format:

Code:

To: xyz 
 From: abc
 Email Subject: 
 Email content: <data return from below query>

Code:

Query :  SELECT * from EMP where DEPT = 87;

I'd propose you get your act together and present a concise and consistent picture of your problem, answering the questions raised by the various contributors, and make your comments fit the code. How about stripping down your code to the essential steps and test each one independently for errors?
- there's no file called EMP_FILE_bkp.txt in your code
- the "emp.backup.$(date +%F_%R).txt" is written but never used.
- as case IS relevant in *nix code, SHNFIX in not shnfix. Please be careful when quoting.
- What is the purpose of that sed command? Take it out for testing.

You are right, that was a typo on my part. Thanks for the correction.

uuencode and mailx are both standard UNIX utilities. They should reside in /bin or /usr/bin on most systems (btw.: care to tell us on which OS you are?) If you have /bin in your PATH (which you should have anyways) that means they are not installed. Get them installed in this case.

In general "executable: not found" can have three reasons and you will have to investigate them yourself because we can't look onto your system:

1) the executable is installed but not in the PATH:
If you have some program /foo/bar/program and you call it with

Code:

program

(that is: without the full path) you need to its respective path included in the PATH statement (actually this is what PATH is for), like this:

Code:

PATH="${PATH}:/foo/bar"

2) the executable is not installed at all
You obviously need to install it, in this case. To find out if it is installed you can run the following command (note that it might run for some while)

Code:

find / -type f -name "your_executable" -print 2>/dev/null

3) the executable is installed but filemodes are wrong
The operating system identifies (potentially) executable files by the filemode, i.e.:

Code:

# ls -l /bin/mailx
-rwxr-xr-x    3 bin      mail         159650 Jan 22 2016  /bin/mailx

The first "x" means that the owner of the file (bin) may execute it. The second "x" means that every member of the group "mail" is allowed to execute it. The third "x" means that every other user is also allowed to execute it.

What you see here for mailx is the default, but some security aficionados tamper with these filemodes and set it to

Code:

# ls -l /bin/mailx
----------    3 bin      mail         159650 Jan 22 2016  /bin/mailx

That means nobody is allowed to do anything (read, write or execute) with this file, not even its owner. It might be that someone deemed mailx or uuecode so dangerous that the only way to deal with this threat was to flag it that way. I have seen such things.

To make it work again you simply need (as root) to reinstate its original filemodes:

Code:

# chmod 755 /bin/mailx
# ls -l /bin/mailx
-rwxr-xr-x    3 bin      mail         159650 Jan 22 2016  /bin/mailx

I hope this helps.

bakunin