Cisco Cisco Prime Service Catalog 10.0 Technical References
5-14
Cisco Prime Service Catalog 10.0 Configuration Guide
OL-31034-01
Chapter 5 System Administration
Performing Application Housekeeping
Oracle:
AddPurgeFilter ORACLE [SID] [User] [Password] [Purge Filter Name] [Purge Filter Value]
SQL Server:
AddPurgeFilter SQLSERVER [Server] [Database] [User] [Password] [Purge Filter Name] [Purge
Filter Value]
Filter Value]
Performing a Dry Run for Requisition Purge
Before purging requisitions, you may optionally perform a “dry run” that to see which requisitions would
be removed without actually deleting them. This will serve as a validation for the filter criteria in effect.
be removed without actually deleting them. This will serve as a validation for the filter criteria in effect.
Use the PurgeRequisitions script to get a list of requisitions which meet the filter criteria.
Purge Filter Name
Description
Purge Filter Value
CREATIONSTARTDATE
Purge requisitions created on or
after this date.
after this date.
Date in DD-MON-YYYY format.
CREATIONENDDATE
Purge requisitions created on or
before than this date.
before than this date.
Date in DD-MON-YYYY format.
CLOSEDSTARTDATE
Purge requisitions closed on or
after this date.
after this date.
Date in DD-MON-YYYY format.
CLOSEDENDDATE
Purge requisitions closed on or
before than this date.
before than this date.
Date in DD-MON-YYYY format.
REQUISITIONSTATUS
Purge requisitions with the
specified status.
specified status.
Possible values are PREPARATION,
OPEN, ONGOING, CLOSED,
CANCELLED, REJECTED,
DELIVERY CANCELLED,
ORDERED or ALL.
OPEN, ONGOING, CLOSED,
CANCELLED, REJECTED,
DELIVERY CANCELLED,
ORDERED or ALL.
REQUISITIONID
Purge a specific requisition
based on the Requisition ID.
based on the Requisition ID.
Unique number assigned to the
requisition.
requisition.
REQUISITIONRANGE
Purge specific requisitions
based on the Requisition ID
range.
based on the Requisition ID
range.
The starting and ending Requisition ID
with a dash in between; for example,
30001-39999.
with a dash in between; for example,
30001-39999.
SERVICEID
Purge requisitions that contain a
specific service based on the
Service ID.
specific service based on the
Service ID.
Unique identifier of the service, as
displayed on the Service Designer
General page for the service definition.
displayed on the Service Designer
General page for the service definition.
SERVICENAME
Purge requisitions that contain a
specific service based on the
Service Name. For SERVICEID
and SERVICENAME filters, the
complete requisition is
deleted—including all service
requests. Purge is at the
requisition-level, not at the
individual entry-(service) level.
specific service based on the
Service Name. For SERVICEID
and SERVICENAME filters, the
complete requisition is
deleted—including all service
requests. Purge is at the
requisition-level, not at the
individual entry-(service) level.
Service Name enclosed in double
quotes, for example, “Email Service”.
quotes, for example, “Email Service”.
Note
This purge filter value must be
an exact match, and is
case-sensitive.
an exact match, and is
case-sensitive.
Note
On UNIX or Linux operating
systems, do not use this purge
filter if the Service Name
contains spaces.
systems, do not use this purge
filter if the Service Name
contains spaces.