May 11, 2016 The only updates that the Server Cleanup Wizard can remove from the database are: Expired Updates (that have been Not Approved for at least 3 months) Old revisions of updates (that have been Not Approved for at least 30 days) The only other way to physically remove updates from the database is via the WSUS API. To update to the most recent product release, click Update to Latest Version. If you have not updated for a while, there may have been multiple versions released since your last update. In this case, you can select a version to which to update. To select a previous version to update to, navigate to that version and click Update. Apr 13, 2018 This will remove the obsolete updates. “exec spDeleteUpdate @localUpdateID=000000”, where 000000 is the ID For me I removed 10 records manually and then I was able to open the WSUS console but you can continue following the article if you are still unable to open the console.
Purpose
Use the
DELETE
command to perform the following actions: - Delete physical backups and copies.
- Delete obsolete backups of sparse databases.
- Update the repository records in the target control file to show that the files are deleted. For example, the record for a backup piece in
V$BACKUP_PIECE.STATUS
shows the valueD
. - Remove the repository records for deleted files from the recovery catalog (if you use a catalog). For example,
RC_BACKUP_PIECE
no longer contains a row for a deleted backup piece.
See Also:
BACKUP
to learn about the BACKUP ... DELETE INPUT
command Prerequisites
RMAN must be connected to a target database, which must be mounted or open.
RMAN uses all configured channels to perform the deletion. If you use
DELETE
for files on devices that are not configured for automatic channels, then you must use ALLOCATE CHANNEL FOR MAINTENANCE
. For example, if you made a backup with an SBT channel, but only a disk channel is configured, then you must manually allocate an SBT channel for DELETE
. An automatic or manually allocated maintenance channel is required when you use DELETE
on a disk-only file. For preplugin backups, the CDB must be open in read-write mode and you must connect as a common user with the
SYSDBA
or SYSBACKUP
privilege. Usage Notes
The best practice is to run
CROSSCHECK
to update the status of backups and copies in the repository and then run DELETE
to remove the desired files. When running RMAN interactively, DELETE
displays a list of files and prompts for confirmation before deleting any file in the list. If you confirm, then RMAN shows each item as it is deleted. When reading commands from a command file, RMAN does not prompt for confirmation. You can view the status of backups and copies recorded in the RMAN repository through
LIST
, V$
views, or recovery catalog views (if you use a catalog). The repository record for a backup can fail to reflect its physical status. For example, a user deletes a disk backup with the Linux rm
command. The backup record cannot be updated by rm
, so the RMAN repository shows the file as available although it no longer exists. Behavior of DELETE Command for Files of Different Status Values
Table 2-5 describes the behavior of
DELETE
when the FORCE
option is not specified. Table 2-5 Behavior of DELETE Command Without FORCE Option
Repository Status | Physical Status | Behavior of DELETE Command |
---|---|---|
AVAILABLE | Not found on media | Does not delete the object and reports the list of mismatched objects at the end of the job. RMAN does not update the repository status. |
EXPIRED | Found on media | Does not delete the object and reports the list of mismatched objects at the end of the job. RMAN does not update the repository status. |
UNAVAILABLE | Any | Removes repository record and deletes object if it exists. All I/O errors are ignored. |
Backup Deletion in a Data Guard Environment
'RMAN Backups in a Data Guard Environment' explains the difference between the association and accessibility of a backup. In a Data Guard environment, the database that creates a backup or copy is associated with the file. You can use maintenance commands such as
CHANGE
, DELETE
, and CROSSCHECK
for backups when connected to any database in the Data Guard environment if the backups are accessible. In general, RMAN considers tape backups created on any database as accessible to all databases in the environment, whereas disk backups are accessible only to the database that created them. If a deletion is successful, then RMAN removes the metadata for the file, even if the file is associated with another database. If a deletion was not successful, and if the file is associated with another database in the Data Guard environment, then RMAN prompts you to perform the same
DELETE
command while connected as TARGET
to the database associated with the file. You must use DELETE ... FORCE
to delete the file metadata. Syntax
delete::=
(maintSpec::=, obsOperandList::=, deviceSpecifier::=)
maintSpec::=
Description of the illustration maintspec.eps
(listObjList::=, archivelogRecordSpecifier::=, maintQualifier::=, deviceSpecifier::=, recordSpec::=)
forDbUniqueNameOption::=
Description of the illustration fordbuniquenameoption.eps
Semantics
Syntax Element | Description |
---|---|
FORCE | Deletes specified files—whether or not they exist on the media—and removes repository records (see Example 2-80). RMAN ignores any I/O errors for the deleted objects. RMAN also ignores any CONFIGURE ARCHIVELOG DELETION POLICY settings. RMAN displays the number of deleted objects at the end of the job. |
NOPROMPT | Deletes specified files without first listing the files or prompting for confirmation. The DELETE NOPROMPT command displays each item as it is deleted. |
PREPLUGIN | Deletes preplugin backups and removes their repository records. |
EXPIRED | Removes only files whose status in the repository is EXPIRED (see Example 2-77). RMAN marks backups and copies as expired when you run a CROSSCHECK command and the files are absent or inaccessible. To determine which files are expired, run a LIST EXPIRED command. If for some reason a backup marked EXPIRED exists when you run the DELETE EXPIRED command, then RMAN does not delete the physical file. |
Deletes backups and copies. You can set rules for the deletion with the maintQualifier clause. For example, you can delete archived redo log files that are backed up to tape (see Example 2-79). When deleting backups of PDBs that were dropped, you identify the PDB using its GUID. Use the GUID clause with the DELETE command to delete backups of dropped PDBs. The dba_pdb_history view contains the GUID of dropped PDBs. Note: DELETE ARCHIVELOG ALL considers only the archived log deletion policy and does not consider the configured retention policy. Note: In CDBs, you must connect to the root as a user with the SYSDBA or SYSBACKUP privilege to delete archived redo logs. You cannot delete archived redo logs when connected to a PDB. See Also: maintSpec and maintQualifier | |
Deletes the backups and copies in maintSpec that are exclusively associated with the specified DB_UNIQUE_NAME in a Data Guard environment. Note: The FOR DB_UNIQUE_NAME option is not allowed with the DELETE OBSOLETE command. If RMAN successfully deletes tape backups associated with the specified DB_UNIQUE_NAME , then RMAN removes the metadata for these files from the recovery catalog. If RMAN could not delete these files because they are associated with a different database in the Data Guard environment, then RMAN prompts you to perform the same DELETE operation for these files at the database that is associated with them. Note: You cannot use FORCE to override the default behavior and specify that RMAN deletes files that are associated with a different database. In this way, RMAN protects you from accidental deletions caused by incorrect RMAN configurations for SBT. To remove the metadata for files that RMAN prevents you from deleting, use the CHANGE RESET DB_UNIQUE_NAME command. See Also: forDbUniqueNameOption for descriptions of the options in this clause | |
OBSOLETE | Deletes data file backups and copies recorded in the RMAN repository that are obsolete, that is, no longer needed (see Example 2-78). RMAN also deletes obsolete archived redo log files and log backups. RMAN determines which backups and copies of data files are no longer needed, which in turn determines when logs (and backups of logs) are no longer needed. RMAN considers the creation of a data file as a backup when deciding which logs to keep. RMAN first uses the options specified with obsOperandList to determine which files are obsolete. If you do not specify options in obsOperandList , then RMAN uses the options specified in CONFIGURE RETENTION POLICY . Note: DELETE OBSOLETE considers only the backup retention policy and does not use the configured archived log deletion policy to determine which logs are obsolete. In contrast, DELETE ARCHIVELOG ALL considers only the configured archived log deletion policy. Note: If you make a backup with the KEEP UNTIL TIME clause, then this backup becomes obsolete after the specified KEEP time passes and is removed by DELETE OBSOLETE . RMAN does not consider the backup retention policy for archival backups whose KEEP time has expired. Note: The DELETE...OBSOLETE command cannot be used when backups are stored to Zero Data Loss Recovery Appliance, commonly known as Recovery Appliance. |
obsOperandList | Specifies the criteria for determining which backups and copies are obsolete. See Also: obsOperandList |
DEVICE TYPE deviceSpecifier | Restricts the deletion to obsolete backups and copies created on the specified device type only. See Also: deviceSpecifier |
Example 2-77 Deleting Expired Backups
This example uses a configured
sbt
channel to check the media manager for expired backups of the tablespace users
that are more than one month old and removes their recovery catalog records. Example 2-78 Deleting Obsolete Backups
This example deletes backups and copies that are not needed to recover the database to an arbitrary SCN within the last week. RMAN also deletes archived redo log files that are no longer needed.
Example 2-79 Deleting Archived Redo Log Files That Are Backed Up
Assume that you have configured RMAN settings as follows:
The following
DELETE
command deletes all archived redo log files on disk if they are not needed to meet the configured deletion policy, which specifies that logs must be backed up twice to tape (sample output included): Example 2-80 Forcing the Deletion of a Backup Set
The following example attempts to delete the backup set copy with tag
weekly_bkup
: Data Bases Obsolete But Update Fails At 78%25
RMAN displays a warning because the repository shows the backup set as available, but the object is not actually available on the media:
Databases Obsolete But Update Fails At 78% 2017
The following command forces RMAN to delete the backup set (sample output included):