cdawes
VIP Member
Anyone who solves this desires a million bucks. Here's the situation.
Before our first go-live with JDE OneWorld we rolled out 200+ replacement
desktops. We were at Oracle 8.1.5 but since Oracle was desupporting this on
January 1st 2001 AND JDE had certified OneWorld on Oracle 8.1.6 we migrated
all our database servers to Oracle 8.1.6 and installed Oracle 8.1.6 clients
and MDAC 2.1 SP2 on all our clients.
The problem we are experiencing is that when we run Financial columnar
reports such as the R14113 certain sections get dropped from the report.
This is a consistent problem in our environment that JDE-Denver has not been
able to duplicate. They have indicated (as usual) that it must be something
with our technical set-up. Here's why I believe that it is not our set-uo
but a JDE OneWorld 'bug'. Here's what I've tried to fix it.
1. Install SP13 - Still not working
2. Run the cross references on R14113 and transfer all objects relating to
this report from Pristine to CRP. - Still not working
3. Install OneWorld on a NT server to see if the problem was at the OS
level. - Still not working.
4. Install a Pristine package on the workstation. - Still not working.
5. Roll back to SP 11.1 and use jdbco81.dll instead of jdbco80.dll. - Still
not working.
The only place that this report did run correctly was on the Deployment
server. So I tried the following:
1. Copy all directories from the Deployment server pathcode to a
Workstation. - Still not working
2. Build a new Pristine package and test on the Deployment Server (worked).
Deploy package to workstation. - Still not working.
To prove that this was not a database problem with Oracle here's what I did:
1. Turn on all logging and capture the SQL select statements generated by
OneWorld.
2. Run the captured SQL statements against the Oracle Database
3. All the right information was returned, thus there was no problem with
Oracle.
Now I could rule out that this was not an OS problem, not a database problem
and really not a OneWorld application problem since I had copied the entire
pathcode from the Deployment Server (working) to a Workstation
(not-working). This left only one possibility - JDE database middleware.
The reason I suspect the middleware is that I took an Oracle 8.1.6 client,
rolled it back to Oracle 8.1.5 and guess what? - Perfect report. Myself, our
senior level DBA's, the 3 report writer's who were doing reports, 2 CNC
consultant who came in and most of Denver is stumped by this. What we had to
do was roll back 45 client who went live on Budget on October 10th. We have
200 more users going live on full A/R, GA and A/P on January 1st, 2001. We
do not want to have to downgrade our Oracle clients on either our
workstations or our servers. We have tried just about everything with
JDE-Denver. You're my only hope!
Thanks
Colin
Now here's what I did to
Colin Dawes, MSc
Business Systems Analyst
The City of Guelph
Before our first go-live with JDE OneWorld we rolled out 200+ replacement
desktops. We were at Oracle 8.1.5 but since Oracle was desupporting this on
January 1st 2001 AND JDE had certified OneWorld on Oracle 8.1.6 we migrated
all our database servers to Oracle 8.1.6 and installed Oracle 8.1.6 clients
and MDAC 2.1 SP2 on all our clients.
The problem we are experiencing is that when we run Financial columnar
reports such as the R14113 certain sections get dropped from the report.
This is a consistent problem in our environment that JDE-Denver has not been
able to duplicate. They have indicated (as usual) that it must be something
with our technical set-up. Here's why I believe that it is not our set-uo
but a JDE OneWorld 'bug'. Here's what I've tried to fix it.
1. Install SP13 - Still not working
2. Run the cross references on R14113 and transfer all objects relating to
this report from Pristine to CRP. - Still not working
3. Install OneWorld on a NT server to see if the problem was at the OS
level. - Still not working.
4. Install a Pristine package on the workstation. - Still not working.
5. Roll back to SP 11.1 and use jdbco81.dll instead of jdbco80.dll. - Still
not working.
The only place that this report did run correctly was on the Deployment
server. So I tried the following:
1. Copy all directories from the Deployment server pathcode to a
Workstation. - Still not working
2. Build a new Pristine package and test on the Deployment Server (worked).
Deploy package to workstation. - Still not working.
To prove that this was not a database problem with Oracle here's what I did:
1. Turn on all logging and capture the SQL select statements generated by
OneWorld.
2. Run the captured SQL statements against the Oracle Database
3. All the right information was returned, thus there was no problem with
Oracle.
Now I could rule out that this was not an OS problem, not a database problem
and really not a OneWorld application problem since I had copied the entire
pathcode from the Deployment Server (working) to a Workstation
(not-working). This left only one possibility - JDE database middleware.
The reason I suspect the middleware is that I took an Oracle 8.1.6 client,
rolled it back to Oracle 8.1.5 and guess what? - Perfect report. Myself, our
senior level DBA's, the 3 report writer's who were doing reports, 2 CNC
consultant who came in and most of Denver is stumped by this. What we had to
do was roll back 45 client who went live on Budget on October 10th. We have
200 more users going live on full A/R, GA and A/P on January 1st, 2001. We
do not want to have to downgrade our Oracle clients on either our
workstations or our servers. We have tried just about everything with
JDE-Denver. You're my only hope!
Thanks
Colin
Now here's what I did to
Colin Dawes, MSc
Business Systems Analyst
The City of Guelph