tdposync utility

Edit online

The tdposync utility checks for items on the IBM® Storage Protect server that are not in the RMAN catalog or Oracle control file. With this utility, you can repair these discrepancies by removing unwanted objects from the IBM Storage Protect, and reclaim space on the server.

Attention: Deleted files and inactive files cannot be restored.

When you are using this utility to delete files, ensure that you do not log in to the wrong node name. You might query a different database than intended, and delete files in error. Ensure that the node name in the PICK window is the one you need. See Optional parameters and PICK window for further details.

When you run an RMAN deletion script, entries are deleted in the RMAN recovery catalog or Oracle control file before confirmation from the IBM Storage Protect server. In cases where objects are not found on the IBM Storage Protect server, RMAN tries to delete backup sets from the IBM Storage Protect server and fails. However, the entries in the RMAN catalog or control file for these objects are still removed. When they are deleted, RMAN can no longer identify these backups through the catalog or control file even though the file exists on the IBM Storage Protect server. Therefore, this utility synchronizes the contents of the servers.

When the RMAN catalog or control file contains backups that are marked as expired, RMAN still considers these objects as existing. If you run the tdposync utility against these objects, it recognizes these objects in the RMAN catalog or control file and on the IBM Storage Protect server and considers them to be in sync. Therefore, you must delete these objects from the RMAN catalog or control file for them to be deleted from the IBM Storage Protect server. Use the Oracle crosscheck command to verify whether the backups exist. Then, use the Oracle delete expired command to remove their record from the RMAN catalog or control file.

When you start tdposync, the following processing takes place:

  1. Prompts you for the RMAN catalog owner ID or the Oracle database user name, password, and connect string.
  2. Gathers information for the Oracle servers.
  3. Queries the Oracle backup catalog and the IBM Storage Protect server.
  4. Displays a list of files that exist on the IBM Storage Protect server but not in the RMAN catalog or Oracle control file.
  5. Prompts you to take one of the following actions:
    • Delete any files found causing the discrepancy.
    • Delete all files.
    • Exit the program without deleting files from the IBM Storage Protect server.

You can automate the maintenance of IBM Storage Protect Data Protection for Oracle without the need for user interaction. You can use an input file to allow the tdposync utility to receive input from a script or batch file.

For example, tdposync syncdb < input.txt

The input.txt file contains the required responses to the prompts for information as in the following example:

 
06/01/2016
06/07/2016
rman
rman
orcl
+
o
y
The description of each line of the input.txt file is listed in the following table:
06/01/2016 # from date
06/07/2016 # to date
rman # RMAN user
rman # RMAN password
orcl # Oracle connection string
+ # pick windows selection, + selects all objects
o # proceed with the operation
y # confirm