Communities
A collaborative platform to connect and grow with like-minded Informaticans across the globe
Product Communities
Connect and collaborate with Informatica experts and champions
Discussions
Have a question? Start a Discussion and get immediate answers you are looking for
User Groups
Customer-organized groups that meet online and in-person. Join today to network, share ideas, and get tips on how to get the most out of Informatica
Get Started
Community Guidelines
Knowledge Center
Troubleshooting documents, product guides, how to videos, best practices, and more
Knowledge Base
One-stop self-service portal for solutions, FAQs, Whitepapers, How Tos, Videos, and more
Support TV
Video channel for step-by-step instructions to use our products, best practices, troubleshooting tips, and much more
Documentation
Information library of the latest product documents
Velocity (Best Practices)
Best practices and use cases from the Implementation team
Learn
Rich resources to help you leverage full capabilities of our products
Trainings
Role-based training programs for the best ROI
Certifications
Get certified on Informatica products. Free, Foundation, or Professional
Product Learning Paths
Free and unlimited modules based on your expertise level and journey
Resources
Library of content to help you leverage the best of Informatica products
Tech Tuesdays Webinars
Most popular webinars on product architecture, best practices, and more
Product Availability Matrix
Product Availability Matrix statements of Informatica products
SupportFlash
Monthly support newsletter
Support Documents
Informatica Support Guide and Statements, Quick Start Guides, and Cloud Product Description Schedule
Product Lifecycle
End of Life statements of Informatica products
Ideas
Events
Change Request Tracking
Marketplace
English
  • Common Content for Data Engineering 10.5.3
  • All Products

Table of Contents

Search

  1. Preface
  2. Command Line Programs and Utilities
  3. Installing and Configuring Command Line Utilities
  4. Using the Command Line Programs
  5. Environment Variables for Command Line Programs
  6. Using infacmd
  7. infacmd as Command Reference
  8. infacmd aud Command Reference
  9. infacmd autotune Command Reference
  10. Infacmd bg Command Reference
  11. infacmd ccps Command Reference
  12. infacmd cluster Command Reference
  13. infacmd cms Command Reference
  14. infacmd dis Command Reference
  15. Infacmd dis Queries
  16. infacmd dp Command Reference
  17. infacmd idp Command Reference
  18. infacmd edp Command Reference
  19. Infacmd es Command Reference
  20. infacmd ics Command Reference
  21. infacmd ipc Command Reference
  22. infacmd isp Command Reference
  23. infacmd ldm Command Reference
  24. infacmd mas Command Reference
  25. infacmd mi Command Reference
  26. infacmd mrs Command Reference
  27. infacmd ms Command Reference
  28. infacmd oie Command Reference
  29. infacmd ps Command Reference
  30. infacmd pwx Command Reference
  31. infacmd roh Command Reference
  32. infacmd rms Command Reference
  33. infacmd rtm Command Reference
  34. infacmd sch Command Reference
  35. infacmd search Command Reference
  36. infacmd sql Command Reference
  37. infacmd tdm Command Reference
  38. infacmd tools Command Reference
  39. infacmd wfs Command Reference
  40. infacmd ws Command Reference
  41. infacmd xrf Command Reference
  42. infacmd Control Files
  43. infasetup Command Reference
  44. pmcmd Command Reference
  45. pmrep Command Reference
  46. Working with filemanager
  47. Working with pmrep Files

Command Reference

Command Reference

Back Next

PurgeVersion

PurgeVersion

Purges object versions from the repository database. You can purge versions of deleted objects and active objects. An object is a deleted object if the latest version is checked in and it has the version status Deleted. Other objects are active objects.
When you purge versions of deleted objects, you purge all versions. The deleted objects must be checked in. You can purge versions for all deleted objects or for objects deleted before a specified end time. You can specify the end time as a date and time, a date only, or a number of days before the current date.
When you purge versions of active objects, you can specify purge criteria. You can specify the number of versions to keep and purge the previous versions, and you can purge versions that are older than a specified purge cutoff time. You cannot purge a checked-out version or the latest checked-in version.
If you purge versions of a composite object, consider which versions of the dependent objects are purged.
You can use the -k option to display the objects that do not purge and the reason object versions do not purge. For example, you might not have permission to purge an object version. You cannot purge object versions that are part of a deployment group.
The PurgeVersion command uses the following syntax: 
purgeversion
{-d <all | time_date | num_day> | 
{-n <last_n_versions_to_keep> |
 -t <time_date | num_day>}}
[-f <folder_name>]
[-q <query_name>]
[-o <output_file_name>]
[-p (preview purged objects only)]
[-b (verbose)]
[-c (check deployment group reference)]
[-s dbd_separator]
[-k (log objects not purged)]
The following table describes
pmrep
 PurgeVersion options and arguments:
Option
Argument
Description
-d
all
time_date
num_day
Required if you do not use -n or -t. Purges all versions of checked-in deleted objects. You can specify
all
 for all deleted objects, or you can specify an end time to purge all versions of objects that were deleted before the end time. You specify the end time in MM/DD/YYYY HH24:MI:SS format, MM/DD/YYYY format, or as the number of days before the current date. If you specify a number of days, the value must be an integer greater than 0.
-n
last_n_versions_to_keep
Required if you do not use -d or -t. Number of latest checked-in object versions to keep for an active object. The value must be an integer greater than 0. For example, enter 6 to purge all versions except the last six checked-in versions. If the object is checked out, you also retain the checked-out version.
After you purge object versions, you cannot retrieve them. To ensure that you can revert to past versions, avoid purging all versions of an object.
-t
purge_cutoff_time
Required if you do not use -d or -n. Cutoff time for purging object versions of active objects. Purges versions that were checked in before the cutoff time. You can specify the purge cutoff time in MM/DD/YYYY HH24:MI:SS format, MM/DD/YYYY format, or as a number of days before the current date. If you specify a number of days, the value must be an integer greater than 0. When you use the ‑t option, you retain the latest checked-in version even if it was checked in after the purge cutoff time.
-f
folder_name
Optional. Folder from which object versions are purged. If you do not specify a folder, you purge object versions from all folders in the repository.
-q
query_name
Optional. Query used to purge object versions from a particular query result set.
If you use the -d option, you purge all versions of the deleted objects. To keep recent versions of deleted objects and purge older versions, you can define a query that returns the deleted objects and then use the -q option with -n, -t, or both.
-o
outputfile_name
Optional. Output file for saving information about purged object versions.
-p
-
Optional. Previews the PurgeVersion command.
pmrep
 displays the purge results without actually purging object versions.
-b
-
Optional. Displays or saves purge information in verbose mode. Verbose mode provides detailed information about object versions, including repository name, folder name, version number, and status. You can use the -b option with -o and -p.
-c
-
Optional. Checks deployment groups in the repository for references to the object versions returned in a purge preview. If a purge preview contains an object version in a deployment group,
pmrep
 displays a warning.
When you use the -c option with the -p option, the command lists objects that purge, then lists which object versions are contained in deployment groups. When you use the -c option without the -p option, the command does not purge object versions that are part of deployment groups.
The -c option can have a negative impact on performance.
-s
dbd_separator
Optional. If an ODBC source has a period (.) in the name, define a different separator character when you define the source object. For example, instead of database_name.source_name, define the source object as database_name\source_name, and define the dbd_separator as backslash (\).
-k
-
Optional. Lists all the object names and versions that do not purge although they match the purge criteria. The -k option also lists the reason that the object versions do not purge. For example, an object version does not purge if you do not have sufficient privileges to purge the object.
An object version does not purge when it belongs to a deployment group. When an object is a member of more than one deployment group, the reason lists the first deployment group that causes the object not to purge.
0 COMMENTS
We’d like to hear from you!