HP B6960-90078 manual Performance Problems, DC binary files are corrupted or missing

		Troubleshooting
		Troubleshooting the IDB
	•	On UNIX, the Data Protector MMD (/opt/omni/lbin/mmd) is not
		displayed when listing the Data Protector processes using the ps -ef
		grep omni command.
		On Windows, the Data Protector MMD process (mmd.exe) is not listed
		among processes in the Windows Task Manager.
Action	1.	Close the Data Protector GUI.
	2.	Run the omnisv –stopcommand to stop the Data Protector
		services/processes.
	3.	Run the omnisv –startcommand to start the Data Protector
		services/processes.
	4.	Run the omnisv –statuscommand to check if all the
		services/processes are running.
	The DC binary files are corrupted or missing
	If the DC binary files are corrupted or missing, the error message Open
	of Detail Catalog Binary File failed is displayed when browsing
	backed up objects in the Restore context.
	•	The omnidbcheck -bfcommand reports that one or several DC
		binary files are missing or of incorrect size, or the omnidbcheck -dc
		command reports that one or several DC binary files are corrupted.
	•	The debug.log file on the Cell Manager, located in the
		<Data_Protector_home>\log\debug.log (Windows systems) or
		in the /var/opt/omni/log/debug.log (UNIX systems) contains
		one or several entries on Data Protector not being able to open a DC
		binary file.
Action	Recreate DC binary files by importing catalog from media. For more
	information refer to “Handling Minor Database Corruption in the DCBF
	Part” on page 422.

Performance Problems

The number of IDB objects and IDB objects' sizes are too large

When browsing object versions and single files for restore, it can take a long time before the information is read from the IDB and displayed.

Chapter 12 599