Once you installed the patch DPWIN_00483 (VEPA patch) you are no longer able to create new integration backups (Exchange, SQL, …). Withhin GUI you are not able to browse for instances. The bug comes from changed manager.exe through patch DPWIN_00483. As a workaround you may use the JAVA GUI where the bug was not seen so far. HP also released an advisory – see corresponding section.
Category Archives: Bugs
Data Protector Bugs
Initialization of medium failed – filelibrary full
The error Initialization of medium failed
is shown when the Filelibrary is full or almost full (one or more mountpoints / folders in filelibrary). If you did not install the GR Patches from July 2010, you may also see a lot of media with blue question mark withhin the mountpoint from your filelibrary. In addition it has been seen that the file cart.txt is quite large when you would do an export of MMDB (omnidbutil -writedb -mmdb Verzeichnis
).
As a first starting mount you may want to increase diskspace for the mountpoint or you can migrate media from the filelibrary to another media off the filelibrary to get free diskspace. As a second step you may want to try to format the media with the blue question mark.
If you still encounter problems try following procedure:
omnidownload -library Libraryname -file Filename
omniupload -modify_library Library -file Filename
In any case you should install the lateste patches (current: GR Patches from July 2010) as the error is already resolved with these patches.
If you still encounter problems I recommend to completly empty the file library (migrate all media from involved file library to another media off the filelibrary) and to remove not needed (or wrong) entries from cart.txt. What has to be deleted in cart.txt is not explained here, as this way is not supported. For some bucks I take over this work in a remote session.
faulting module vbda.exe, …, faulting module msvcr71.dll
No translation for this article available.
External utility reported error
If you receive the error below during a backup of a Oracle Instance, a faulty Perl module on the client is the source of the problem…
The problem is difficult to debug, so just ask support for QCIM2A24591_TM3. With the fix the module DPoracle.pm will be changed, this should resolve the problem.
Recovery Manager complete.
[Major] From: ob2rman@server "Instanz" Time: 02.08.2010 09:30:26
External utility reported error.
RMAN PID=PID nummer
[Major] From: ob2rman@server "Instanz" Time: 02.08.2010 09:30:26
Oracle Recovery Manager completed with errors.
[Major] From: ob2rman@server "Instanz" Time: 02.08.2010 09:30:26
Backup of target database failed.
Size matters
No translation for this article available.