R09801

[libbi_fletcher]

Does anyone have any ideas of how to speed up the post program? It is
taking several hours to run a post with 7000 transactions in it to a F0911
with 2.5 million records. Any suggestions would be appreciated.

AS400 ES B733.2 11.3 NT 4.0

Libbi Fletcher
HoMedics, Inc.
M.I.S. Department
248-863-3001 ext. 1281
[email protected]

 

[Carl_Fisher]

Sounds like database tuning issue to me. Shouldn't take anywhere near that
long. Try getting your DBA to check out your Indexing etc.



OW733.3 Xe SP 14.2
Enterprise Server - Intel NT + Oracle 8.0.6
Client - Citrix TSE + 4 NT PC's for development

 

[david_mallory]

Libbi,

We had a similar problem with R09801 post, and database tuning was the
solution. We are running Oracle.

Dave Mallory

 

[Christian Audet]

Libbi,

A couple of moths ago I was at a client site with big performance issues regarging every report that was touching the f0911, f0901,f0902. This client have 4 millions records in f0911.

This client was under B733.2 SP 11 just like you are. The JDEdwards solution was to go to SP16.1 (it's always there answer !!) but that time that was true ! Some report went from 5 hours to 5 minutes with SP16.1 but we also have some report that didn't change at all !

So I think that SP16.1 can be a solution to some of your performance problem but probably not all.

Christian Audet




Implementing B7333 (Xe) SP16.1, SQL
(Support B732, B7331 and B7332)

 

[libbi_fletcher]

Thank you, Christian. We are planning on going up to XE in the next couple
of months, so maybe we will just limp along until that time.

Libbi Fletcher
HoMedics, Inc.
M.I.S. Department
248-863-3001 ext. 1281
[email protected]

 

[pianosynth]

I agree with Carl. We had some reports that were taking up to an hour with only 80K records in the dB. We used the Oracle dB analysis tools to identify the problem and created an index on the key fields of the dB accessed by the report. The run time went from around an hour to around 20-30 seconds. I would start with dB analysis and see if you can't tweak performance before tackling the job of installing and testing a major SP upgrade.

B733.2, SP 15, Oracle 8.1.6, HP 9000
Win2K, Citrix 1.8, NFuse

 

[Richard_Wheeler]

We have had some performance issues on certain reports. Mostly on ones that
hit on the F0911, F0902, and F0901 as well. Big thing that helped us since
we are an AS400 shop is moving to SP17.1. We have had no problems so far
(almost a week of testing) besides the MTRs on Fat Clients (Running WIN98).
Another thing is to make sure you have the right indexes on those files,
That is a big one. We use the SQL optimizer on the AS400 to find the best
index for the reports and create it if we have to. We have 14 million
records in our F0911 and this has helped us A LOT! Some reports were
running for 20 minutes are now running in under 2 minutes.

Richard Wheeler
OneWorld Developer
503-370-7071 X7261
www.holidaytouch.com

AS400, COEXISTENT, XE/CUM12, UPD1 SP15 (SP17.1 in DEV), CO on AS400, WIN2000
WS

 

[libbi_fletcher]

Christian
Do you mean 16.1 on XE? We are planning to upgrade to XE in the next few
months, so are you saying that perhaps that will take care of it?

Libbi Fletcher
HoMedics, Inc.
M.I.S. Department
248-863-3001 ext. 1281
[email protected]

 

[Christian Audet]

Charles,

You are right, the reason why I was talking about SP 16.1 is that I know there is a huge glitch before SP 16.1 and this is about linking to F0911 table.

I was able to discover that when OneWorld is accessing f0911 from report sometimes there is no WHERE clause in the SELECT to the f0911 wich can select in the case of my client 4 MILLIONS records instead of 2000!!

With SP16.1 most of thoses error are fixed. If you don't have millions of record in your file it's sometimes difficult to reproduce the error i'm talking about since it's already going fast.

So conclusion is Carl and Charles are right but if it still failed try SP16.1 it as worked for us.

Christian Audet

Implementing B7333 (Xe) SP16.1, SQL
(Support B732, B7331 and B7332)

 

[ShaneM]

Libbi:

We attempted to upgrade to 16.1 to fix this problem as well. It hasn't
worked for any of our custom reports, but some of the core reports have
better performance.

Shane McConnell
Metroplex, Inc.
NT, XE, Update 2 SP 16.1

 

[Christian Audet]

Re: RE: R09801

Libbi,

Yes i'm talking about the SP16.1 of B733.2

Christian

Implementing B7333 (Xe) SP16.1, SQL
(Support B732, B7331 and B7332)