PD Refresh

Heres the scenario: We applied update 4 to DV7333, applied custom code & such. I built a C/S full pkg. I refreshed PD with DV, but not the Edwards way, too long. I used AS400 cpylib, etc.... I'm having no problems except attempting a full build in PD. The gbrspec.ddb is taking a long time, been running 24 hrs, approx 1/2 done(rec count).

I'm not sure if it's a performance issue w/AS400, or what. Update pkgs are building w/no problems.

Any suggestions ??, I would appreciate the input.

When you did this, did you copy/replace the Object Librarian record from the
Development pathcode to the Production pathcode? I will experience problems
if you don't do this.

Andy



Consultant with clients
at B7331 - Xe
Various Deployment Servers, Citrix and JAS

Good thing you saved all that time by not using recommended methods huh?

Check your LF's on prod CO tables, esp the F98741.
Check your Central Objects - PD7333 ODBC is set correctly on the build
machine. The compression tab.

Why did you not include copying the full DV package in your refresh to PD?

You're right, the JDEdwards way is far too long and painful to go through.



I'm not sure if it's a performance issue w/AS400, or what. Update pkgs are
building w/no problems.

Any suggestions ??, I would appreciate the input.

What does the SvrBuild.log say? At what point in the server build is it? I had a problem where OW thought the server was still building, but a backup had occurred and locked files during the package build and it wasn't doing anything. I had to restart the build.

The problem has been resolved. Rich hit it right. ODBC setting for compression on CO somehow (?) was turned off.

Jim-

Check the odbcdatasource.inf on the deployment server for the compression
setting on that (and other) datasource. JDE uses that file for the settings
when it configures ODBC.

Regards,
David

Brightpoint NA
Sun/Oracle 8.1.6 / Citrix Xe base Sp15.1 live
Update 4 / SP18.1 sandbox