<aside> 💡

For a more detailed break down of the cleanup process, refer to My Oracle Support.

E-DPK: Manual Cleanup Process for PUM deployments on NativeOS Windows and Unix (Doc ID 2117053.1)

</aside>

DPK Cleanup Process

The DPK uses a process called “cleanup” to remove installed software and domains. The cleanup process uses Puppet to delete installed files and folders. You can run the cleanup process two ways:

1. The bootstrap script
2. Using puppet apply

The bootstrap script

The bootstrap scripts (psft-dpk-setup) has a parameter you can pass to remove installed software:

Windows

.\\psft-dpk-setup.bat --cleanup

Linux

.\\psft-dpk-setup.sh --cleanup

Using puppet apply

To run the cleanup process with Puppet, you set the ensure: absent parameter in the defaults.yaml file. When you run puppet apply, Puppet will remove everything it knows about.

Controlling the cleanup process

If there is software, domains or users you want to keep, you can use your psft_customizations.yaml file to keep things. For example, if you want to keep your old PS_HOME folder, copy the ps_home: hash to your psft_customizations.yaml file and add the remove: false to the hash:

ps_home:
  db_type:    "%{hiera('db_platform')}"
  unicode_db: "%{hiera('unicode_db')}"
  location:   "%{hiera('ps_home_location')}"
  remove:     false

Many of the hashes in the psft_deployment.yaml and psft_unix_system.yamlsupport the remove: false setting.