26 Deinstalling the Software

This chapter includes these tasks:

26.1 Understanding the Deinstallation

The installation and upgrade processes do not automatically remove any JD Edwards EnterpriseOne databases. You should have a database administrator (DBA) for your relational database management system (RDMS) manually remove any unused databases according to the list of databases and associated components, which are provided in this document.

The deinstallation program restricts you from deinstalling a mandatory component without also removing all associated optional components that were previously installed. The relationship between the mandatory and optional components is shown in this table:

Server Mandatory Component Optional Components
Deployment Server JD Edwards EnterpriseOne Files Production Environment

Prototype Environment

Development Environment

Pristine Environment

Enterprise Server JD Edwards EnterpriseOne Foundation ES Production

ES Prototype

ES Development

ES Pristine


26.2 Deinstalling the Software from the Workstations

You can remove previous JD Edwards EnterpriseOne installations from workstations by running the deinstallation program as described in the JD Edwards EnterpriseOne Development Client Installation Guide.

26.3 Deinstalling the Local OEE from the Deployment Server

Note:

Oracle products use the term "deinstall" to refer to removing an Oracle product.

To deinstall the local Oracle database:

  1. Either export the local database tablespaces or deinstall JD Edwards EnterpriseOne using Start > Programs > Oracle - <Home_Name> > Oracle Installation Products > Universal Installer where <Home_Name> is the name that you gave the installation of EnterpriseOne on the Deployment Server.

  2. Locate this file:

    <Oracle_Home>\deinstall\deinstall.bat

  3. Right click on the file that you located in Step 2 and select Run as administrator, where <Oracle_Home> is the directory where you installed the local Oracle database. For example, your directory might be:

    c:\Oracle\E1Local

  4. At the end of the deinstallation, verify that the Oracle_Home directory has been deleted (for example, c:\Oracle\E1local). If it still exists, you should attempt to manually delete it.

    Caution:

    Prior to any reinstall an Oracle local database on this same machine, the Oracle_Home directory (for example, c:\Oracle\E1local) must not exist. If you attempt to reinstall the local Oracle database and this directory still exists, it is likely that the new installation will fail.

    Tip:

    You may not be able to delete the Oracle_Home directory (for example, c:\Oracle\E1local) if a process has it locked. In that case, to determine which process(es) has it locked, run the steps in the section of this guide entitled: Section 3.10.5.4, "Process Explorer".

26.4 Manual Cleanup of a Deinstalled Oracle Database on the Deployment Server

If the deinstallation of the OEE database fails for some reason, you need to perform the manual steps in this procedure to completely remove the old installation before reinstalling the database.

  1. Deinstall the Deployment Server.

    Be sure the Deployment Server is deinstalled before attempting to deinstall the database. This should ensure that no EnterpriseOne tablespaces are imported (attached) to the EnterpriseOne database.

  2. Delete the following registry keys:

    \HKEY_LOCAL_MACHINE\SOFTWARE\ORACLE\KEY_E1Local

    \HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\ORACLE\KEY_E1Local

    \HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\(see Keys below)

    Keys. Delete any keys with names that start with "Oracle" and contain "E1Local".

  3. Delete this directory:

    c:\Oracle\E1Local

    If you cannot delete the E1Local subdirectory because a file in that directory is locked, follow these steps:

    1. Determine which file is locked and which process has the lock on the file. A freeware program called Process Explorer can be helpful in determining this information. You can obtain a free copy of Process Explorer from this web site:

      http://technet.microsoft.com/en-us/sysinternals

    2. Either kill the locking process with Process Explorer or Microsoft Windows Task Manager or, if the process was started as a Microsoft Windows service, change the Startup Type to Manual and reboot the computer again.

    3. Try again to delete the E1Local subdirectory.

  4. Remove the 64-bit Oracle inventory entries.

    1. With a text editor (such as Notepad), edit this file:

      c:\Program Files\Oracle\inventory\ContentsXML\inventory.xml

    2. Delete any lines that start with:

      <HOME NAME="E1Local"

    3. Save the file.

  5. Remove the entry from the Windows PATH.

    1. Navigate to Control Panel > System.

    2. Click Advanced system settings on the left.

    3. Click Environment Variables… near the bottom.

    4. In the System variables box near the bottom, highlight Path and click the Edit… button.

    5. In the Variable value field, delete this value:

      c:\Oracle\E1Local\bin

      Be sure to remove the semicolon as well.

    6. Click OK.

  6. Remove the ORACLE_HOME Windows environment variable.

    1. Navigate to Control Panel > System.

    2. Click Advanced system settings on the left.

    3. Click Environment Variables… near the bottom.

    4. In the System variables box near the bottom, highlight ORACLE_HOME and click Delete.

    5. Click OK.

26.5 Using the OUI Installer to Deinstall JD Edwards EnterpriseOne from the Deployment Server

You can use the OUI installer to deinstall JD Edwards EnterpriseOne from the Deployment Server. To deinstall the local database, depending on your local database type, refer to the preceding sections of this guide entitled: Section 26.3, "Deinstalling the Local OEE from the Deployment Server".

To use the OUI installer to deinstall JD Edwards EnterpriseOne from the Deployment Server:

  1. Log on to the Deployment Server as a user with Administrator rights.

    Caution:

    Ensure that the Administrator account name that you use does not contain any special characters.
  2. If JD Edwards EnterpriseOne is running on the Deployment Server, stop it.

    Use Task Manager to verify these processes are stopped:

    • activConsole.exe

    • jdenet_n.exe

    • java.exe

    If any of these processes are running, either wait for them to finish or kill them via Task Manager.

  3. Go to Start > All Programs > Oracle - JDE_DEP910_Home > Oracle Installation Products > Universal Installer.

    Surrounding text describes oui_dep_svr_deinstall_wel.gif.
  4. On Oracle Universal Installer: Welcome, select the Deinstall Products ... button.

    Surrounding text describes oui_dep_srv_deinstall_inv.gif.
  5. On Inventory, with the Contents tab select, put a check mark next to the Oracle Homes for the Deployment Server Home.

    For example, if you followed recommendation in this guide the Oracle Home for your Deployment Server is:

    JDE_DEP910_HOME

  6. Select the Remove button.

    Surrounding text describes oui_dep_svr_deinstall_con.gif.
  7. On Confirmation, verify that you want to deinstall the listed components and their dependent components and if so, select the Yes button.

    Surrounding text describes oui_dep_svr_deinstall_prog.gif.

    The Remove dialog indicates the progress of the deinstall action.

    Surrounding text describes oui_dep_svr_deinstall_done.gif.
  8. When the deinstallation process completes, the Inventory is shown again. The products you selected for deinstallation should no longer be displayed in the inventory.

  9. Select the Close button.

    Surrounding text describes oui_dep_svr_deinstall_wel.gif.

    You are returned to the Oracle Universal Installer: Welcome screen.

  10. On Oracle Universal Installer: Welcome, select the Cancel button to exit the Oracle Universal Installer.

26.6 Dropping DB2 UDB Databases

This section lists the DB2 UDB databases that must be manually dropped by a DBA. This is the list of databases that were created by the JD Edwards EnterpriseOne 9.1 Installation of the Platform Pack on your Enterprise or Database Server for your JD Edwards EnterpriseOne installation, or from a previous JD Edwards EnterpriseOne installation.

By design, these databases are not automatically removed by the JD Edwards EnterpriseOne deinstallation program. You should have a DBA for your RDBMS manually remove any unused databases listed in the table below.

Note:

When removing DB2 UDB, you must drop all the tables within the tablespaces you want to remove, then drop the tablespaces (which automatically removes the indexes).

Tip:

The JD Edwards EnterpriseOne installer delivers sample scripts which you can use as examples of how to drop the databases. You should examine and edit these to suit your needs with the understanding that they have not been delivered 'ready to run '. You should pay attention to environment variables and arguments the scripts are expecting. Your DBA may prefer to drop the databases themselves instead of using scripts.

Sample drop scripts are located in the UDB directory under the JD Edwards EnterpriseOne installation directory (E910):

drop_db.sh (run signed on as instance owner)

drop_db.bat

You should also be aware that when you run the JD Edwards EnterpriseOne deinstaller, the directory structure containing sample drop scripts is deleted.

DB2 UDB Database Name (Alias) JD Edwards EnterpriseOne Component Schema Tablespace JD Edwards EnterpriseOne Purpose
OWSH910

(JDE910)

Foundation SVM910 svm910i

svm910l

svm910t4k

svm910t32k

Server Map
SY910 sy910i

sy910l

sy910t4k

sy910t32k

System    
OL910 ol910i

ol910l

ol910t4k

ol910t32k

Object Librarian    
DD910 dd910i

dd910l

dd910t4k

dd910t32k

Data Dictionary    
OWSH910

(JDE910)

Development Object Specifications DV910 dv910i

dv910l

dv910t4k

dv910t32k

Central Objects and Versions
CRP Object Specifications PY910 py910i

py910l

py910t4k

py910t32k

   
Production Object Specifications PD910 pd910i

pd910l

pd910t4k

pd910t32k

   
Pristine Object Specifications PS910 ps910i

ps910l

ps910t4k

ps910t32k

   
OW_PROD

(JDE_PROD)

Production Environment PRODCTL prodctli

prodctll

prodctlt4k

prodctlt32k

Production Control Tables
PRODDTA proddtai

proddtal

proddtat4k

proddtat32k

Production Data    
OW_DEV

(JDE_DEV)

Development Environment TESTCTL testctli

testctll

testctlt4k

testctlt32k

Development Control Tables
TESTDTA testdtai

testdtal

testdtat4k

testdtat32k

Development Data    
OW_PS910

(JDE_P910)

Pristine Environment PS910CTL ps910ctli

ps910ctll

ps910ctlt4k

ps910ctlt32k

Pristine Control Tables
PS910DTA ps910dtai

ps910dtal

ps910dtat4k

ps910dtat32k

Pristine Data    
OW_CRP

(JDE_CRP)

Prototype Environment CRPCTL crpctli

crpctll

crpctlt4k

crpctlt32k

CRP Control Tables
CRPDTA crpdtai

crpdtal

crpdtat4k

crpdtat32k

CRP Data    

26.7 Removing System Accounts for DB2 UDB

This section lists the DB2 UDB system accounts that must be manually dropped by a DBA. This is the list of system accounts that were created by the JD Edwards EnterpriseOne 9.1 Installation of the Platform Pack on your Enterprise or Database Server for your JD Edwards EnterpriseOne installation, or from a previous JD Edwards EnterpriseOne installation.

The database users are not automatically removed by the JD Edwards EnterpriseOne deinstallation program. You should have a DBA for your RDBMS manually remove any unused items listed in the table below.

Database Name System Account
SY910

OL910

DD910

SVM910

SY910

OL910

DD910

SVM910

You should also remove this System Group:

  • JDESHARE (system group)

You should also remove these users of the JD Edwards EnterpriseOne system:

  • jde

  • applead

  • produser

  • devuser

Production PD910

PRODDTA

PRODCTL

Note: For your installation, the proddta and prodctl users may be needed for a previous release.

Pristine PS910

PS910DTA

PS910CTL

Development DV910

TESTDTA

TESTCTL

Note: For your installation, the testdta and testctl users may be needed for a previous release.

Prototype PY910

CRPDTA

CRPCTL

Note: For your installation, the crpdta and crpctl users may be needed for a previous release.


26.8 Deinstalling the Platform Pack

You should always use the JD Edwards EnterpriseOne OUI-based installation program to remove JD Edwards EnterpriseOne. If you manually remove the software, the deinstallation cannot be guaranteed to be complete and, as a result, subsequent reinstallation of JD Edwards EnterpriseOne may be hindered.

It is also very important you drop your DB2 UDB databases prior to running the deinstaller, as specified in the warning in the section entitled: Section 26.6, "Dropping DB2 UDB Databases". If you do not do this you will lose the drop.sh script that was delivered in the installation, because it will be removed by the deinstaller.

On the machine which you initially installed the Platform Pack:

  1. Locate and execute the runInstall file under the /install subdirectory. Typically the directory structure of the extracted install image is similar to that shown below:

    Surrounding text describes ppack_structure_unix_udb.gif.

    Note:

    The byte counts in this example will likely not match those of your unzipped files.

    Caution:

    You must sign on as the UDB instance owner in order to run the runInstall file. You cannot run a OUI installer as root.

    The installer requires that you are signed on as the UDB database user, even if you are only installing the Logic portion of the Platform Pack. You must install the UDB database client software and sign on as the owner of that install when running the Platform Pack. The Installer uses information about this account to configure the enterpriseone.sh. If you sign on as any other user, you will see errors during the install and will need to manually configure the database variables in enterpriseone.sh.

    This image is described in surrounding text.
  2. On Oracle Universal Installer, Welcome, click the Deinstall Products… button.

    This image is described in surrounding text.
  3. Turn on the check box next to the Oracle Home for the Platform Pack and expand the node to show all installed components. For example, the Oracle Home might be named JDE_PPack910_Home.

    Note:

    At this step, you should select only the Oracle Home that is associated with this particular OUI. That is, the Oracle Home name that you select on this screen should match the Oracle Home name that you selected from Start > Programs.
  4. Click the Remove… button.

    This image is described in surrounding text.
  5. On Confirmation, verify that you want to deinstall the listed components and their dependent components and if so, select the Yes button.

    Surrounding text describes deinstall_ppack_progress.gif.

    The Remove dialog indicates the progress of the deinstall action.

    Surrounding text describes deinstall_ppack_inv_done.gif.
  6. When the deinstallation process complete, the Inventory is shown again. The products you selected for deinstallation should no longer be displayed in the inventory.

  7. Select the Close button.

    This image is described in surrounding text.

    You are returned to the Oracle Universal Installer: Welcome screen.

  8. On Oracle Universal Installer: Welcome, select the Cancel button to exit the Oracle Universal Installer.

  9. Verify that the installation directory (Oracle Home) has been deleted. If it still exists, you can delete it.