Sponsored Content
Full Discussion: Unmatched <<
Top Forums Shell Programming and Scripting Unmatched << Post 302755061 by Don Cragun on Friday 11th of January 2013 05:22:36 PM
Old 01-11-2013
Quote:
Originally Posted by yoavbe
Hi,
I am running sinple ksh script .
From some reason it failed on the following error:
./ogg_status.sh[14]: syntax error at line 16 : `<<' unmatched

Please advise.
#!/usr/bin/ksh
export ORACLE_HOME=/software/oracle/DB10gR2
export LD_LIBRARY_PATH=/software/oracle/DB10gR2/lib:/usr/lib
infoall() {
/goldengate/ggsci<<EOF
info all
exit
EOF
}


$ ./gg_status.sh
+ export ORACLE_HOME=/software/oracle/DB10gR2
+ export LD_LIBRARY_PATH=/software/oracle/DB10gR2/lib:/usr/lib
./ogg_status.sh[14]: syntax error at line 16 : `<<' unmatched
You run a script named gg_status.sh and show us the first nine lines of an unnamed file. The error message from ksh is saying that there is a problem on line 14 or 16 in a file named ogg_status.sh.

Unless you show us the contents of of the file ogg_status.sh and the command line that invoked ogg_status.sh, there isn't much we can do to help you.

And PLEASE USE CODE tags. The position of the string that ends a here document can be very important when trying to diagnose a shell script. Leaving out the CODE tags hides information that can be crucial in diagnosing a problem like this.
 

10 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

else unmatched

I'm getting an else unmatched error on the script below.. For info : SYDB is the database name entered as a param on the command line. #Check the DB name HBDB=`sql $SYDB <<_END_ | grep '^|' | grep -v dbase | sed 's/|//g' | sed 's/ //g' set autocommit on; \p\g set lockmode... (7 Replies)
Discussion started by: b.hamilton
7 Replies

2. Shell Programming and Scripting

list of unmatched columns

Hi , I have two files want to compare and list of column values and postion which are not matched between two files,I can use diff but it will return rows from two files which are matched and unmatched columns.I wrote the below script but not working. f1=$1 f2=$2 for i in 1 do file1=`cat... (3 Replies)
Discussion started by: mohan705
3 Replies

3. Shell Programming and Scripting

input file unmatched

Hello guys, I am trying to run an installer through my script. Whatever yes/no or values required during the installation is provided by an answer file (answ.txt) ./install < /var/answ.txt Now, during the installation, it asks for: 1) press return to continue 2) press 3 and hit enter 3)... (1 Reply)
Discussion started by: solaix14
1 Replies

4. Shell Programming and Scripting

done' unexpected and do' unmatched

Good morning, I have been teaching myself shell scripting and seem to be stuck here. I am sure I am just blind and not seeing it so I thought maybe some fresh eyes would help. With the script below I keep getting.... "syntax error at line 248 : `done' unexpected" I am not seeing why this... (6 Replies)
Discussion started by: LRoberts
6 Replies

5. Shell Programming and Scripting

`for' unmatched

:b:Hi guys, I am getting this error in this piece of code, Any help will be appreciate rypidoc.shl: syntax error at line 79 : `for' unmatched ##Determine if there is a file to process ls 3526*.dat > /dev/null 2>&1 if then exit fi for i in 3526*.dat do # Capture just the file... (2 Replies)
Discussion started by: rechever
2 Replies

6. Shell Programming and Scripting

remove unmatched values

Below is my requirement : unmatched values should get deleted from file1 file1 A-1 B-1 C-1 D-2 E-3 F-4 file2 D C F output C-1 D-2 F-4 (2 Replies)
Discussion started by: lavnayas
2 Replies

7. Shell Programming and Scripting

Unknown error - ``' unmatched

Hi Guys, I get the error while running below commands. Earlier the command used to execute, but after enclosing them in a function, the error is occuring backupPath=`echo $folderName | sed -e 's,/vobs/dte/itgClient/client/RegressionTestLibPostOHS/,,'` check_event=`cat... (7 Replies)
Discussion started by: ajincoep
7 Replies

8. Shell Programming and Scripting

Find Unmatched name from given lists..

i have two lists, list1 => abc jones oracle smith ssm tty list2 => abc jones lmn smith ssm xyz now i want to print only those names which are present in list2 and want to remove names from list2 which presents in list1. so i want OUTPUT => lmn xyz because "abc jones smith ssm" from list2... (5 Replies)
Discussion started by: Killer420
5 Replies

9. Shell Programming and Scripting

If statement with unmatched condition

Hi Gurus, I'm facing some issues with multiple conditions in my if statement. if (!($InputLine=~/^Date/)) && (!($fields eq "VEN")) { Above is the line troughing some syntax errors. I am trying to avoid the below creteria lines to process in my logic. Records starting with... (4 Replies)
Discussion started by: hi.villinda
4 Replies

10. Shell Programming and Scripting

<< unmatched error

Hi all, I want to call a plsql package that does not return any value. I am using the following script to do so: sqlplus $UserNamePwd <<EOF set head off begin test_pkg.procedure('$DebugFlag'); end; exit EOF if then log_message "procedure failed." exit 1 fi exit $? I... (2 Replies)
Discussion started by: reshma15193
2 Replies
Pod::PlainText(3pm)					 Perl Programmers Reference Guide				       Pod::PlainText(3pm)

NAME
Pod::PlainText - Convert POD data to formatted ASCII text SYNOPSIS
use Pod::PlainText; my $parser = Pod::PlainText->new (sentence => 0, width => 78); # Read POD from STDIN and write to STDOUT. $parser->parse_from_filehandle; # Read POD from file.pod and write to file.txt. $parser->parse_from_file ('file.pod', 'file.txt'); DESCRIPTION
Pod::PlainText is a module that can convert documentation in the POD format (the preferred language for documenting Perl) into formatted ASCII. It uses no special formatting controls or codes whatsoever, and its output is therefore suitable for nearly any device. As a derived class from Pod::Parser, Pod::PlainText supports the same methods and interfaces. See Pod::Parser for all the details; briefly, one creates a new parser with "Pod::PlainText->new()" and then calls either parse_from_filehandle() or parse_from_file(). new() can take options, in the form of key/value pairs, that control the behavior of the parser. The currently recognized options are: alt If set to a true value, selects an alternate output format that, among other things, uses a different heading style and marks "=item" entries with a colon in the left margin. Defaults to false. indent The number of spaces to indent regular text, and the default indentation for "=over" blocks. Defaults to 4. loose If set to a true value, a blank line is printed after a "=head1" heading. If set to false (the default), no blank line is printed after "=head1", although one is still printed after "=head2". This is the default because it's the expected formatting for manual pages; if you're formatting arbitrary text documents, setting this to true may result in more pleasing output. sentence If set to a true value, Pod::PlainText will assume that each sentence ends in two spaces, and will try to preserve that spacing. If set to false, all consecutive whitespace in non-verbatim paragraphs is compressed into a single space. Defaults to true. width The column at which to wrap text on the right-hand side. Defaults to 76. The standard Pod::Parser method parse_from_filehandle() takes up to two arguments, the first being the file handle to read POD from and the second being the file handle to write the formatted output to. The first defaults to STDIN if not given, and the second defaults to STD- OUT. The method parse_from_file() is almost identical, except that its two arguments are the input and output disk files instead. See Pod::Parser for the specific details. DIAGNOSTICS
Bizarre space in item (W) Something has gone wrong in internal "=item" processing. This message indicates a bug in Pod::PlainText; you should never see it. Can't open %s for reading: %s (F) Pod::PlainText was invoked via the compatibility mode pod2text() interface and the input file it was given could not be opened. Unknown escape: %s (W) The POD source contained an "E<>" escape that Pod::PlainText didn't know about. Unknown sequence: %s (W) The POD source contained a non-standard internal sequence (something of the form "X<>") that Pod::PlainText didn't know about. Unmatched =back (W) Pod::PlainText encountered a "=back" command that didn't correspond to an "=over" command. RESTRICTIONS
Embedded Ctrl-As (octal 001) in the input will be mapped to spaces on output, due to an internal implementation detail. NOTES
This is a replacement for an earlier Pod::Text module written by Tom Christiansen. It has a revamped interface, since it now uses Pod::Parser, but an interface roughly compatible with the old Pod::Text::pod2text() function is still available. Please change to the new calling convention, though. The original Pod::Text contained code to do formatting via termcap sequences, although it wasn't turned on by default and it was problem- atic to get it to work at all. This rewrite doesn't even try to do that, but a subclass of it does. Look for Pod::Text::Termcap. SEE ALSO
Pod::Parser, Pod::Text::Termcap, pod2text(1) AUTHOR
Russ Allbery <rra@stanford.edu>, based very heavily on the original Pod::Text by Tom Christiansen <tchrist@mox.perl.com> and its conversion to Pod::Parser by Brad Appleton <bradapp@enteract.com>. perl v5.8.0 2002-06-01 Pod::PlainText(3pm)
All times are GMT -4. The time now is 05:01 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy