Reactivate a deactivated package?

(OneWorld 7332, ES RS6000/AIX, DS Windows 2000, Oracle)

My client accidentally deactivated a full package which previously had built successfully. Now its Assembly Status is "Assembly Definition in Progress", and its Build Status is "In Definition".

Is there a way, perhaps doing an update to a table, to "Reactivate" this package without having to resubmit the build?

Thanks in advance.

A very good friend just told me how this is done. Our package is back to Assembly Status=Assembly Definition Complete and Build Status=Build Completed Successfully.

Here's how we reactivated the deactivated package:

All this takes place within SQL*Plus for Oracle, though I imagine it would be much similar in SQL Server or other:

1) Fix the status in the F9603 Software Package Header
SQL> update sysb733.f9603 set phpcksts = 20 where phpkgname = 'PRODB733FI';

2) Fix the status in the Software Package Build Header
SQL> update sysb733.f96021 set bhbldsts=50 where bhpkgname = 'PRODB733FI';

That fixes it-- we were fortunate, because the folders for the package were still in place.

Whew.

Tim,

We have the same configuration as you including being on OW 7332. Have you
given any thought as to upgrading to version XE or higher? We have to make
a decision soon as to what we are going to do because we heard JDE will stop
supporting b7332 at the end of June of this year. Please let me know what
your thoughts are.

Thanks,
Patrick Pierce
Programmer/Analyst
Zen-Noh Grain Corp.

(OneWorld 7332, Enterprise Server RS/6000 AIX, DS & TS Windows 2000, Oracle
8.1.6.



Patrick Pierce
Programmer/Analyst
Zen-Noh Grain Corp.

OneWorld ver. 73.3.2
Terminal Servers - Windows 2000 w/Terminal Server 2000
Deployment Server - Windows 2000

Re: RE: Reactivate a deactivated package?

Hi Patrick,
Yeah, my client wants to upgrade to Xe this summer (when no one works in Spain-- except us technicians). The installation was done by some fairly non-experienced folks from IBM who had the CDs to install Xe, but had never done an Xe installation, so they installed 7332. Neat, huh?

We had not heard about JDE not supporting 7332. They want to upgrade because Xe will be so much faster, powerful, and more generally wonderful than 7332. Since I get to do the upgrade, I'm all for it.