Deleting orphaned data | HCL Digital Experience
You use the SLCheckerTool to delete orphaned data in the database.
Before you begin
When portal resources are deleted, dependent resources that are stored in a different database domain are not deleted at the same time. These remaining resources are still available for backup scenarios or other production lines that might share the database domain. For example, when an administrator deletes pages, the user customization to the deleted pages are not deleted. The SLCheckerTool enables the detection of orphaned data that is not needed any more by any of the production lines that share the domain. You can use the SLCheckerTool to prepare an XML script for later deletion of the orphaned data by the XML configuration interface.
wp.db.slchecker.jar
in
the following directory: - AIX®
HP-UX
Linux™
Solaris:
wp_profile_root/PortalServer/bin/slcheckertool.sh
- IBM® i:
wp_profile_root/PortalServer/bin/slcheckertool.sh
- Windows™:
wp_profile_root\PortalServer\bin\slcheckertool.bat
- z/OS®:
wp_profile_root/PortalServer/bin/slcheckertool.sh
- AIX®
HP-UX
Linux™
Solaris:
wp_profile_root/PortalServer/bin/slcheckertool.sh
- IBM® i:
wp_profile_root/PortalServer/bin/slcheckertool.sh
- Windows™:
wp_profile_root\PortalServer\bin\slcheckertool.bat
- z/OS®:
wp_profile_root/PortalServer/bin/slcheckertool.sh
To prepare and complete deleting orphaned data, you also complete some steps by using the XML configuration interface. For details about the XML configuration interface and how to use it refer to the appropriate topics. A sample XML script for exporting orphaned data that are listed enables the preparation of the orphaned data for work with the SLCheckerTool.
About this task
- Before you delete the orphaned data by using the SLCheckerTool, secure your databases by making a backup.
- To delete all orphaned data, you must include every production line that shares the database domain. Otherwise, resources that are still valid in a skipped production line might be unintentionally removed.
To delete the orphaned data, proceed by the following steps. For each step, use the target file from the previous step as the source file.
Procedure
- Run the cleanup service to delete resources that are marked for delayed deletion. To run the cleanup service, use the XML configuration interface and the XML sample file Task.xml as the input.
- Create a full export that includes orphaned data of each production line that shares the particular domain. To complete this step, use the XML configuration interface and the XML sample file ExportIncludingOrphanedData.xml.
- Use the SLCheckerTool to create an XML script file to delete
the orphaned data. Complete this step with the substeps given later.
Observe the following rules:
- For each step, start the SLCheckerTool with the appropriate parameters as described under that step.
- Replace all file name variables (given in italics) by the complete directory path location and file name.
- For each step, use the target file or files from the previous step as the source file or files.
Start the SLCheckerTool by using the following shell scripts:- AIX®
HP-UX
Linux™
Solaris:
wp_profile_root/PortalServer/bin/slcheckertool.sh
- IBM® i:
wp_profile_root/PortalServer/bin/slcheckertool.sh
- Windows™:
wp_profile_root\PortalServer\bin\slcheckertool.bat
- z/OS®:
wp_profile_root/PortalServer/bin/slcheckertool.sh
- Optional: You can check whether all production lines were considered during the creation of the XML script file. To check, review the comment in the file header. The header contains information about all full exports that were used.
-
Delete the orphaned data by starting the XML configuration interface with the XML script that
you obtained as the
xml_target_file
with the orphaned data in the substep for generating the XML script. You must start the XML configuration interface with the XML script only on one production line that shares the database domain. This step deletes the orphaned data for all production lines that share that database domain.