Re: Financials: SQL*ReportWriter reports fail with signal 11
Date: 1996/07/24
Message-ID: <Dv1nu3.9ny_at_wildcat.daytonoh.ncr.com>#1/1
John,
Thanks for the reply. I seem to have gone down the same road
that you have already traveled. I was working with support also
and it took them 2 full days to realize that this was an known
problem. I upgraded to .27 and the reports worked. Support also
suggested that I upgrade to .28, which I did. Just to let you know
if you haven't already done so, I had to edit the .28 r20_patch.sh script
to include two rm -f before the second set of copies of rxinit.o
and rwfon.o.
If the rm -f isn't in there the patch install will fail. Just
another fine
Oracle product.
Thanks again,
Mike
==========John Allen, 7/19/96==========
I once had a client with this problem and upgrading from report 2.0.14 to 2.0.27 resolved the problem as well as other minor problems.
The problem made itself apparent after applying a mega-patch to
release 10.5.
No reports, except simple non-user-exit reports, ran and trying to
resolve the problem with Oracle Support was mostly a waste of
time, since
they never seemed to understand the essence of the problem.
John Allen
Criterion Consulting
Los Angeles
Mike Perkins (Mike.Perkins_at_daytonOH.ncr.com) wrote:
: Has anyone experienced any problem with Financials where
: the delivered SQL*ReportWriter reports fail with:
: APP-00969 Program was terminated by signal 11
:
: APP-01125 Concurrent Manager got error running SQL*ReportWriter
: for request
: This occurs on standard reports such as Active Users, Active
: Resp., etc...
: If I run the reports from the UNIX shell they complete successfully.
: Support's initial response was that I did not have a printer
configured.
: I have since done this and rebooted the concurrent manager without
: success. I have also recompiled the FND package along with ar20run
: and r20run.
: My environment is:
: NCR 3000 series
: 7.1.6 Oracle
: 10.6 Financials
: This is also an initial setup.
Received on Wed Jul 24 1996 - 00:00:00 CEST