11-13-2006
I checked the syntax of the shell script and it's OK.
I agree with mona that you have problem with the sql statements.
Try to remove the commas from the sql statements:
select max(ctrl_perd) from prod where code=123;
select max(ctrl_perd) from geo where code=456;
Execute the statements first in sqlplus and see if they run successfully.
Send us the output you get.
Nir
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
i All
I have scripting question.
I have a file "out.txt"
which is generated by another script
the file contains the following
my_identifier8859574
logout
The number is generated in the script and I have put the my_identifier bit in front of it as a unique identifier
I now have... (7 Replies)
Discussion started by: grahambo2005
7 Replies
2. Shell Programming and Scripting
Hi,
Can anyone tell me how to get all ORA errors between two particular times in an alertlog file using shell script.
Thanks (3 Replies)
Discussion started by: suman_dba1
3 Replies
3. Shell Programming and Scripting
Hi all
im having trouble starting with a shell script, i hope someone here can help me
i have 2 files
file1:
404905.jpg 516167
404906.jpg 516168
404917.psd 516183
404947.pdf 516250
file2:
516250 /tmp/RecyclePoster18241.pdf
516167 /tmp/ReunionCardFINAL.jpg
516168... (7 Replies)
Discussion started by: kenray
7 Replies
4. Shell Programming and Scripting
Hi,
I have a shell script and inside that shell script it calls a local .env file to set the environment for the shell script ,but the thing is that i got a error while running the script like
./myscript.sh it gives DB_NAME=dvcl021: is not an identifier
that DB_Name is accessed from my .env... (6 Replies)
Discussion started by: malickhat
6 Replies
5. Solaris
Hi all,
Am intermittently getting the following errors on one of my databases.
Errors in file /oracle/HRD/saptrace/background/hrd_psp0_13943.trc:
ORA-27300: OS system dependent operation:fork failed with status: 12
ORA-27301: OS failure message: Not enough space
ORA-27302:... (1 Reply)
Discussion started by: newbie_01
1 Replies
6. Shell Programming and Scripting
Hi,
as the title says, I am after a simple script, which will open the Alert log from
an 11.2.0.1 Linux environment and mail the error message and description to a recipient email address.
I can then schedule this job via cron and let it run every 15 minutes.
I have searched online... (16 Replies)
Discussion started by: jnrpeardba
16 Replies
7. Shell Programming and Scripting
Here is the question...
Create a new script, sub2, taking three parameters...
1.) the string to be replaced
2.) the string with which to replace it
3.) the name of the file in which to make the substitution
...that treats the string to be replaced as plain text instead of as a regular... (1 Reply)
Discussion started by: johnhisenburg
1 Replies
8. Shell Programming and Scripting
I have a shell script which select total count from a table and use its value in a if condition like below
connect_string="username/password@tnsname"
tot=`sqlplus -s $connect_string << EOF
set echo off
set feedback off
set head off
select count(*) from test_table;
EOF
`
if
then
echo... (2 Replies)
Discussion started by: vel4ever
2 Replies
9. UNIX for Dummies Questions & Answers
Hello
I am trying to use the following inside a shell script :
S_TAB=$(sqlplus -s / as sysdba <<EOF
set feedback off linesize 132 pages 0 echo off verify off heading off
select created
from v\$database;
select 'hurrah' from dual;
EOF)
Spews out lots of rubbish... (2 Replies)
Discussion started by: d_b
2 Replies
10. UNIX for Dummies Questions & Answers
I've been trying to debug this for 3 hours now. TAB is a table where it contains all the table names. If I try to run it without the filter 'where' it runs fine and outputs the number of rows. But when I put a filter it shows that error. I want to be able to know if the table exists, if it doesn't,... (2 Replies)
Discussion started by: gmatcat
2 Replies
LEARN ABOUT CENTOS
error::pass1
ERROR::PASS1(7stap) ERROR::PASS1(7stap)
NAME
error::pass1 - systemtap pass-1 errors
DESCRIPTION
Errors that occur during pass 1 (parsing) usually mean a basic syntax error of some sort occurred in the systemtap script. There are sev-
eral classes of problems possible:
plain syntax error
The systemtap script parser detects a large variety of errors, such as missing operands, bad punctuation. It tries to list what
kinds of tokens it was expecting to see, and will show the region of the source code with the problem. Please review the stap(1)
man page and/or the tutorial, to correct the script's syntax.
grammar ambiguities
There is at least one known ambiguity in the systemtap grammar. It relates to the optionality of ; (semicolon) separators between
statements, and the ++ and -- increment/decrement operators. If the parser indicates an error, consider adding some explicit ; sep-
arators between nearby statements and try again.
missing command line arguments
A systemtap script that uses the $N and @N constructs for substituting in command-line options may fail if not enough options were
given on the stap command line.
compatibility changes
Some versions of systemtap have changed the language incompatibly, for example by adding the try/catch keywords for exception han-
dling. In such cases, rerun systemtap with the --compatibility=VERSION option, substituting the last systemtap version where your
script was known to work. You may also check the release-history NEWS file for compatibility changes.
GATHERING MORE INFORMATION
Increasing the verbosity of pass-1 with an option such as --vp 1 can help pinpoint the problem.
SEE ALSO
stap(1),
error::reporting(7stap)
ERROR::PASS1(7stap)