Manually Removing the PeopleSoft Environment on Microsoft Windows

This section includes advanced steps to be used only if the cleanup procedures using the DPK setup script or psft_puppet_apply script in this section failed, or if you were not able to use the previous procedures for any reason.

If the cleanup process on Microsoft Windows was not totally successful, the BASE_DIR folders may not be entirely cleared, or you may have trouble when carrying out another deployment. Before carrying out the advanced steps in this section:

  1. Run the command psft-dpk-setup.bat --cleanup.

  2. If the script displays a FAILED message, run it again.

  3. If it succeeds, check the BASE_DIR folders to be sure everything has been deleted.

  4. If the BASE_DIR folders are not clear, or if a subsequent deployment is not successful, carry out the steps below.

For the advanced manual cleanup on Microsoft Windows, there are several steps. The steps in this section should be performed by someone familiar with modifying the Microsoft Windows registry. Depending upon where the cleanup process failed, some of the items mentioned in these steps may have already been removed. The user should remove whatever remains in this order:

  1. Start the Microsoft Windows Services utility.

  2. Stop the services OracleServiceCDB<Product> (for example, OracleServiceCDBFSCM) and OracleOraDB19cHomeTNSListener<Listener_Name> (for example, OracleOraDB19cHomeTNSListenerpsft_listener) by highlighting the names, right-clicking and selecting Stop.

    Note:

    If your database is not on an Oracle platform, the references to the Oracle database services here are not applicable.

    Note:

    When you stop the service for the CDB (Oracle container database), you may see a message informing you that it will also stop the services for the PeopleSoft application server and Process Scheduler domains that were deployed for that database.

  3. Stop the services for the PeopleSoft application server, Process Scheduler, and PeopleSoft PIA domains, if necessary.

  4. Open a command prompt, running as administrator, and remove the two database services and the PeopleSoft domains services with the commands: 

    sc delete OracleServiceCDB<Product>
sc delete OracleOraDB19cHomeTNSListener<Listener_Name>

    sc delete PsftAppServerDomain<Appserver_domain_name>Service
sc delete PsftPrcsDomain<ProcSched_domain_name>Service
sc delete PsftPIADomain<PIA_domain_name>Service

  5. In the Services window, stop ORACLE ProcMGR V22.1.0.0.0 and TListen 22.1.0.0.0 (Port 3050) by highlighting the names, right-clicking and selecting Stop.

  6. In the Services window, right-click each of the services in step 5, select Properties, and copy the correct service name (rather than the alias).

  7. Open a command prompt and remove the two preceding services with the command:

    sc delete <service_name>

  8. Open the Microsoft Windows registry; for example, select Start, Run, and enter regedit.

  9. In the Registry Editor, locate the HKLM\SOFTWARE\ORACLE folder.

    Select the following keys and verify that they contain references to the DPK installation locations in BASE_DIR:

    • KEY_OraDB19Home1 (BASE_DIR\db by default)

    • KEY_OraTux2210Home<date_time> (BASE_DIR\pt\bea\tuxedo by default)

    • KEY_OracleWLHome<date_time> (BASE_DIR\pt\bea by default)

  10. In the Registry Editor, locate the HKLM\SOFTWARE\ORACLE\TUXEDO folder.

    Select the 22.1.0.0.0 key and verify that it contains references to the DPK installation locations in BASE_DIR (BASE_DIR\pt\bea\tuxedo by default).

  11. In the Registry Editor, only for the keys from step 9 and 10 that reference the DPK installation locations, right-click and select Delete.

  12. Close the Registry Editor window.

  13. Open the file C:\Program Files\Oracle\Inventory\ContentsXML\inventory.xml in a text editor.

  14. Locate the lines that reference the DPK deployment:

    Note:

    This sample has been formatted for readability.

    <HOME NAME="OracleWLHome<date_time>" LOC="C:/psft/pt/bea" TYPE="O" IDX="16"/>
<HOME NAME="OraTux2210Home<date_time>" LOC="C:\psft\pt\bea\tuxedo" TYPE="O" 
IDX="17"/>
<HOME NAME="OraDB19Home1" LOC="C:\psft\db\oracle-server\19.3.0.0" 
TYPE="O" IDX="18"/>

  15. Delete only the lines referencing the DPK deployment, and save the file.

  16. Remove everything under the BASE_DIR folder (BASE_DIR\db, BASE_DIR\dpk, and BASE_DIR\pt).

    Note:

    If you performed a customized deployment, back up the psft_customizations.yaml file and any log files, to refer to if necessary. Save them outside of the BASE_DIR.

    Note:

    You may get a message that some of the file names are too big for the recycle bin. Click OK to accept.

  17. Remove C:\User\<username>\psft\pt\8.63 (PS_CFG_HOME).

  18. If you performed a customized deployment that installed software such as Oracle Tuxedo or Oracle WebLogic, PS_APP_HOME, or PS_CFG_HOME, in non-default locations, remove that software manually, unless you need to retain the installations.

    Note:

    If you want to retain the additional components, do not remove the installation locations. Be sure to use a customized deployment and specify the location of the additional components for any subsequent deployments.

  19. Delete any user-defined System environment variables, such as PS_HOME, TUXDIR, PS_CFG_HOME, PS_APP_HOME, ORACLE_HOME, TNS_ADMIN.

  20. Completely clean up any DPK install directory that was used for previous DPKs.

    If you do not delete these or move them off the machine, they may be picked up by a subsequent DPK setup process and may cause the new DPK to fail.

  21. Check the PATH environment variable, and remove the directories or path associated with the previous DPK deployments.

  22. Restart the windows machine to release any caches or processes in the memory.