Data Protector 8 was almost a brand new release as far as the Internal Database is concerned. It was transitioned from the RAIMA database to a PostgreSQL model
There have been several problems discovered in this transition that have been fixed with Site-Specific Patches (SSPs)
These patches should only be requested and applied if one of the actual symptoms occur
SSPUX800_001 HPUX
SSPLNX800_002 Linux
SSPNT800_002 Windows
Symptoms
===========================================================
1. The GUI is crashing when browsing files to restore.
2. There are inconsistencies in the Data Protector Omniinet,
Volume Restore Disk Agent (VRDA), and Restore Disk Agent (RRDA) functionality.
3. IDB check reports media inconsistency and IDB backup fails after upgrade
4. MMD ends abnormally during backup
5. omnidbcheck -dc ends abnormally because of null reference
Exception on media with missing positions
6. Upgrade of dcbf failed on linux and hpux
7. CSM ends abnormally during object copy
8. Unable to create NDMP drive: GUI reports DBAxxx errors
9. Cannot delete pre-upgrade media pool:
GUI reports DBAxxx errors
10. Cannot backup IDB - licensing problems
11. xSM reports [61:4039] Following error occurred while storing detail catalog
12. The "GB Written:" from
omnirpt -report -single_session -session <session_id>
is multiple time larger than object size.
13. omnirpt -list_sessions shows wrong value for "GB Written" for each session
The SSP installation instructions are contained in the SSP description
===================
SSPUX800_002 HPUX
SSPNT800_003 Windows
SSPLNX800_003 Linux
The fixes in this Site Specific Patch are only for the
symptoms and environment specified. This patch is a hot-fix
only, and has not been completely regression tested.
If your Data Protector environment has not been diagnosed by
HP as having this specific problem, installing this patch
may have detrimental consequences
This SSP is actually a script that corrects several corrupt IDB problems. It may take several hours for the script to run, known values
60GB IDB: over 2 hours
220 GB IDB: over 7 hours
Symptoms
===========================================================
1. omnidbcheck -media_consistency failed
2. CSM crash
3. omnidbutil -list_pools fails due to negative values in media blocks used in upgraded database
4. MMD ending abnormally during backup
5. Object copy session on DP 8.0 fails with error:
Internal error: DbaXXXX functions in copy session.
==================
Once again, these SSPs should NOT be installed pro-actively, only if you and encountering one or more of the symptoms shown. Open a case with the Response Center to make sure that they agree that your problem can be addressed by one, or both of the SSPs, and the Response Center will obtain the SSP for you