PeopleSoft: Clean Up PUM

 

Manual Cleanup steps for WINDOWS

  1. Before carrying out the advanced steps in this section: Run the command: psft-dpk-setup.bat --cleanup.
  2. If you deployed the environment using the use_alternate_puppet_install option, use this command:  psft-dpk-setup.bat --cleanup --use_alternate_puppet_install
  3. If the script displays a FAILED message, run it again.
  4. If it succeeds, check the BASE_DIR folders to be sure everything has been deleted.
  5. If the BASE_DIR folders are not clear, or if a subsequent deployment is not successful, carry out the steps
    below.

For the ADVANCED CLEAN UP PROCESS on Microsoft Windows, please see the following steps.

NOTE: These 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. 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 V12.2.2.0.0_VS2017 and TListen 12.2.2.0.0_VS2017(Port3050) 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_OraDB19cHome (BASE_DIR\db by default)
    • KEY_OraTux1222Home (BASE_DIR\pt\bea\tuxedo by default)
    • KEY_OraWL12213Home (BASE_DIR\pt\bea by default)
  10. In the Registry Editor, locate the HKLM\SOFTWARE\ORACLE\TUXEDO folder.
    Select the 12.2.2.0.0_VS2017 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="OraWL12213Home" LOC="C:/psft/pt/bea" TYPE="O" IDX="16"/>
    <HOME NAME="OraTux1222Home" LOC="C:\psft\pt\bea\tuxedo" TYPE="O" IDX="17"/>
    <HOME NAME="OraDB19cHome" LOC="C:\psft\db\oracle-server\19.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.58 (PS_CFG_HOME).
  18. If you performed a customized deployment that installed software such as Oracle Tuxedo or Oracle WebLogic, or 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.

 

Manual Cleanup steps for UNIX/LINUX

  1. Before carrying out the advanced steps in this section: Run the command ./psft-dpk-setup.sh --cleanup.
  2. If you deployed the environment using the use_alternate_puppet_install option, use this command:  psft-dpk-setup.sh --cleanup --use_alternate_puppet_install
  3. If the script displays a FAILED message, run it again.
  4. If it succeeds, check the BASE_DIR folders to be sure everything has been deleted.
  5. If the BASE_DIR folders are not clear, or if a subsequent deployment is not successful, try the following steps.

For the ADVANCED CLEAN UP PROCESS  on Linux,AIX, HP-UX and Solaris, please see the following steps. Depending upon where the cleanup process failed, some of the items mentioned may have already been removed.

  1. Check for left-over PeopleSoft processes.
    ps -aux|more
  2. Stop the processes using this command with the process ID:
    kill -9 <PID>
  3. Check for the five PeopleSoft user IDs using these commands
    id psadm1
    id psadm2
    id psadm3
    id oracle2
    id esadm1
    When you carry out the cleanup using the DPK setup script, it should remove the PeopleSoft users cleanly. However, if the users' home directory was deleted by mistake before running the cleanup, the user definition may remain. If the commands give an output, it means the user exists.
  4. If there are left-over PeopleSoft users, check for running processes associated with the users with this command:
    ps -ef|grep <user_id>
  5. Stop any running processes associated with the users, if necessary.
  6. Delete the users, with this command:
    userdel -r <user_id>
  7. Remove the PeopleSoft base directory (BASE_DIR).
    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 BASE_DIR.
  8. Delete the following files, if they exist:
    /etc/oraInst.loc
    /opt/oracle/psft/db/oraInventory
    /etc/oratab
    /srv/dpk/oracle
  9. 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.
    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.
  10. Remove any environment variables referring to the BASE_DIR that you removed, or to any of the customized locations (for example, TUXDIR, WL_HOME, BEA_HOME, PS_HOME, PS_CFG_HOME,
    PS_APP_HOME).
  11. Delete the NFS shared directories listed below from /etc/exports on the Linux server if any of them exist.

            Note: If these shared NFS folders are not removed, DPK deployment for PUM (PeopleSoft Update Images) will fail at the step for setting up NFS shares, shares if the folder names are the same for the new deployment.

            This applies to deployments on PeopleTools 8.61 and later.

            11a. Run the cat /etc/exports command to get the list of NFS shares created for tools_client, pi_home, ps_app_home.

For example:

[root@serversample setup]# cat /etc/exports

/opt/oracle/psoft/pum49/pt/hcm_pi_home *(ro,sync,all_squash,secure)

/opt/oracle /psoft/pum49/pt/hcm_app_home *(ro,sync,all_squash,secure)

/opt/oracle /psoft/pum49/pt/tools_client *(ro,sync,all_squash,secure)

            11b. If any of the above entries exist, edit /etc/exports file, for example with vi editor, and manually remove the entries for the above folders.

 

Comments

Post a Comment

Popular posts from this blog

Postgres: Clean up stopped replication slot

Image
  When a slot is inactive, that means that Murty and his team have stopped the replication on their side. The SQL below will identify inactive slots. We should schedule this script in a job , running every hour.    (1) SELECT  slot_name,  pg_size_pretty(pg_wal_lsn_diff(pg_current_wal_lsn(),restart_lsn)) AS size,  active,  slot_type  FROM pg_replication_slots;       (2) Once you identify the replication slot, the job should drop it with the following command:     SELECT pg_drop_replication_slot ('pg_replication_slot_name_from_above');         (3) Restart the database instance to clean up unwanted disk space.   Notes from Google:- Thank you for contacting Google Cloud Support. My name is Jagadeesh and I will be assisting you with this issue.   I understand that WAL logs are expanding to over 1.5TB and you want to know what is causing WAL logs to grow and you want to reduce it. Please confirm if ...
Read more