In addition to the "" issue, there is a ";;" missing in the case statement for option 4.
I've remove all excess trailing semi-colon characters to make it easier to read and put the ;; on a separate line. This is unix shell not Oracle and it is never necessary to end a line in a single semi-colon.
Hi friends,
I am using Sun Solaris 5.9. I want to take backup of 3 folders which are 50 GB in size totally using tar command on tapes. I am having DAT 72 tape. After initiating tar command (tar -cvf /dev/rmt/0n /tmp/dir1/ /tmp/dir2/ /tmp/dir3/), tarring is stopped after 10 hrs (approx) and i am... (7 Replies)
I am taring to disk and get this message:
tar: write error: unexpected EOF
This message is normally associated with tape devices, not disk.
Here is the syntax:
tar -cf <tarfilename> /dir
Have you seen this message on disk tars? (4 Replies)
Hi,
I am newbie and am just trying to connect to oracle from shell script ,,,but I am getting the following error
./prog.sh: line 20: syntax error: unexpected end of file
The scripts is :
#!/bin/bash
O=$IFS; IFS=",";
while read a b c d
do
echo $c
... (6 Replies)
I need archive data from some tar files. I use the command "tar xvf
filename". For about half of the files I get the error message
"tar:read error: unexpected EOF".
The number of bytes extracted comes very close to the size of the
tar file.
An example:
972434779 Jan 10 01:01... (4 Replies)
I have a script which throws an error: "here document `EOF' unclosed"
The script is:
...
main()
{
RETVAL=`sqlplus -s $ConnectDetails << EOF
SET SERVEROUTPUT ON
DECLARE
errnum NUMBER;
errmsg VARCHAR2(1000);
BEGIN
My_Procedure( errbuf => errmsg, errcode... (2 Replies)
I am trying to check the return status of a command thats encapsulated
in an <<EOF
#!/bin/ksh
set -x
xxx()
{
set -x
ls -lt /tmp/jdlkewjdlkewjdlkewjdlewjdlew<<EOT
ret=$?
EOT
echo "ret=$ret"
} >>$LOG 2>&1
LOG=/tmp/t2.out
rm -rf $LOG
echo "Starting process `date... (2 Replies)
tar: write error: unexpected EOF
I usually encounter this when I'm doing backup to Dat72 tape. Here's the command
gzip all files in a directory then tar cvfp /dev/rmt/0n files. Not all files are copied. Any things I should look at? Directory size?
---------- Post updated at 05:20 PM... (1 Reply)
Below is a test script I'm writing in the process of learning to write script. When I try to run it I get an unexpected end of file error on line 56. Thoughts?
SCRIPT:
#!/bin/bash
# system_page - A script to produce a system information HTML file
##### Constants
TITLE="My System... (1 Reply)
Hi all
I am inserting record in oracle database using shell script. When the sql part is directly written in the shell script the record is getting inserted. But when the same piece of code is added into a function, I am getting an error while execution "line 45: syntax error: unexpected end of... (6 Replies)
Hi,
can someone kindly look into my copy script and figure out why am i getting a "unexpected EOF while looking for matching `"' error message
#!/bin/ksh -x
cd /home/goldenga/test/flag37
if ; then
rm copied.ok
cd /home/goldenga/test
Upper=`ls -t|grep 'qw*'|cut -d "w" -f 2|head... (4 Replies)
Discussion started by: NDalal007
4 Replies
LEARN ABOUT OPENSOLARIS
echo
echo(1B) SunOS/BSD Compatibility Package Commands echo(1B)NAME
echo - echo arguments to standard output
SYNOPSIS
/usr/ucb/echo [-n] [argument]
DESCRIPTION
echo writes its arguments, separated by BLANKs and terminated by a NEWLINE, to the standard output.
echo is useful for producing diagnostics in command files and for sending known data into a pipe, and for displaying the contents of envi-
ronment variables.
For example, you can use echo to determine how many subdirectories below the root directory (/) is your current directory, as follows:
o echo your current-working-directory's full pathname
o pipe the output through tr to translate the path's embedded slash-characters into space-characters
o pipe that output through wc -w for a count of the names in your path.
example% /usr/bin/echo "echo $PWD | tr '/' ' ' | wc -w"
See tr(1) and wc(1) for their functionality.
The shells csh(1), ksh(1), and sh(1), each have an echo built-in command, which, by default, will have precedence, and will be invoked if
the user calls echo without a full pathname. /usr/ucb/echo and csh's echo() have an -n option, but do not understand back-slashed escape
characters. sh's echo(), ksh's echo(), and /usr/bin/echo, on the other hand, understand the black-slashed escape characters, and ksh's
echo() also understands a as the audible bell character; however, these commands do not have an -n option.
OPTIONS -n Do not add the NEWLINE to the output.
ATTRIBUTES
See attributes(5) for descriptions of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Availability |SUNWscpu |
+-----------------------------+-----------------------------+
SEE ALSO csh(1), echo(1), ksh(1), sh(1), tr(1), wc(1), attributes(5)NOTES
The -n option is a transition aid for BSD applications, and may not be supported in future releases.
SunOS 5.11 3 Aug 1994 echo(1B)