tdposync considerations

The following information must be considered before you use the tdposync command:

• Resynchronize Oracle catalogs with the target databases before you run the tdposync syncdb command. First, connect to the target database and the catalog database. The following is an example:

  $ rman target xxx/yyy@targetdb  rcvcat xxx/yyy@catalogdb 

  When you are connected to both databases, type resync catalog at the RMAN prompt.
• By default, Data Protection for Oracle prompts you to synchronize with one Oracle catalog at a time. If you use multiple Oracle catalogs to back up multiple target databases to the same file space, the same node name, and the same owner name on the same IBM Storage Protect server, you must use –numcatalogs=number. This action is necessary so that tdposync has all the information to correctly query both Oracle and the IBM Storage Protect™.

  Similarly, if you use Oracle control files to back up multiple target databases to the same file space, the same node name, and the same owner name on the same, you must use -numorinstances=number.

  If, for example, you back up only one target database by using two catalogs, do not specify this option. However, if you back up two target databases by using two catalogs, one catalog for each, to the same under the same file space, node name, and owner name, you must specify numcatalogs. If you fail to provide information for the second target database by not specifying two catalogs, that database is displayed as eligible for deletion.

  Restriction: Failure to provide all pertinent and correct information can result in erroneous output. To prevent the erroneous output, see the next consideration.
• If you have more than one Oracle database, back up each Oracle target database to its own file space on the IBM Storage Protect server. To back up each Oracle target database to its own file space, use the tdpo_fs option in the tdpo.opt file. For best results, use a separate Data Protection for Oracle options file for each database that you back up to IBM Storage Protect. In this way, it is only necessary to synchronize one catalog at a time, one for each target database. The possibility of showing wrong information in the PICK window is minimized.
  Tip: Make sure to use the same tdpo.opt file that was used for the original backup.
• If the information for sqlplus that you provide to tdposync is incorrect, such as logon, password, or connect string information, sqlplus stops at its logon screen. You must log on again at the prompt by using the RMAN catalog owner ID, password, and connect string. For example:

  login/password@connectstring

  where connectstring represents the Oracle database in which to connect. The connectstring is also sometimes referred to as the Transparent Network Substrate (TNS) alias. When the correct input is entered, tdposync proceeds.