Simpler Navigation coming for Servers and Operating Systems
Coming soon: a much simpler Servers and Operating Systems section of the Community. We will combine many of the older boards, and you won't have to click through so many levels to get at the information you need. If you are looking for an older board and do not find it, check the consolidated boards, as the posts are still there.
General
cancel
Showing results for 
Search instead for 
Did you mean: 

error starting concurrent managers

SOLVED
Go to solution
Dave Chamberlin
Trusted Contributor

error starting concurrent managers

I am running Oracle 7.3.4 with apps 10.7 on my shiny new N box. When starting the concurrent managers (startmgr) I get the error:
batchmgr[160]: /var/tmp/sh9809.2 cannot find or open the file.
Line 160 of batchmgr is:
nohup $shell << \end_logging >> $log 2>&1 &
The managers do not come up. If I run startmgr again, there is no error and all is fine. I'm afraid I don't fully understand what is line 160 doing. I know that the last part of the line is sending output to $log, redirecting errors to /dev/null, but what is the first part of the line doing? Does anyone know why this is failing the first time? Thanks.
6 REPLIES
harry d brown jr
Honored Contributor

Re: error starting concurrent managers


Shouldn't it be a forward slash, and not a backward slash?

nohup $shell << /end_logging >> $log 2>&1 &
Live Free or Die
Wodisch
Honored Contributor
Solution

Re: error starting concurrent managers

Hello Dave,

it should NOT be slash at all, perhaps it could be a dash...
The reason is the a statement like this:
sh <>output.log
echo this
echo that
ENDMARK

redirects the lines between the "<"ENDMARK" to the standard input of the command (sh
in this example). If it does have "-" after the "<<"
the white space at the begining of those lines is ignored.

HTH,
Wodisch
Sridhar Bhaskarla
Honored Contributor

Re: error starting concurrent managers

There is a syntax error on Line 160. It shouldn't be \. Morever it is trying to read from the from till this marker. You should give us little more of this script. Can you print in top 5 lines and bottom 10 lines after this line?.

Now, shell is somewhere defined in the script as a command and it is being executed as no hup taking arguments till the mark "end_logging". Take out "\" and see if it
works.

You should be having something like this

nohup $shell << end_logging >> $log 2>&1
....
some commands
....
end_logging

-Sri
You may be disappointed if you fail, but you are doomed if you don't try
Wodisch
Honored Contributor

Re: error starting concurrent managers

Hello Dave,

I am not quite certain on this, but if the "here document"
(that how the "<<" feature is called) uses a single-quote
quoted endmark, then not substitution happens on the
input lines, so that might be intended in your script...
If this is true, then change the endmark from
\mark
to
'mark'
and see wether it works now.

Just my ?0.02 (after a very long day),
Wodisch
Alexander M. Ermes
Honored Contributor

Re: error starting concurrent managers

Hi there.
Have you checked your directory /var/tmp for the correct rights or owner ?
Does this directory exist or is it a link to something else ?
Rgds
Alexander M. Ermes
.. and all these memories are going to vanish like tears in the rain! final words from Rutger Hauer in "Blade Runner"
Dave Chamberlin
Trusted Contributor

Re: error starting concurrent managers

Thanks for the help. I think I understand what is going on - except for the slash. The script was not working due to the logfile not being found, since I created new log files and that problem went away. On to the next one...