topic Re: RBF backup image goes corrupt afer bzip usage in Operating System - OpenVMS

RBF backup image goes corrupt afer bzip usage

smsc_1 — Thu, 05 Nov 2009 15:45:18 GMT

Hi all,

We are trying to backup Oracle Database into DB.RBF file on OpenVMS 8.3.1H1.

If e try to restore it directly after creation the database runs.

To tranfer to a Linux system we need to compress the backup first, such preserving the file attributes.

# bzip2 -k -s -1 -f DB.RBF

When we uncompress with (version 1.0.5a)

# bzip2 -d DB.RBF-BZ2

and restore the database next errors popup
=========================================
%RMU-E-READERR, error reading DKA200:[BACKUP]DB.RBF;1
-RMU-E-BLOCKCRC, software block CRC error
%RMU-E-INVBLKSIZ, invalid block size in backup file
%RMU-E-INVRECTYP, invalid record type in backup file
%RMU-E-INVRECEXP, Error expanding compressed backup file record.
%RMU-F-RTNERR, Call to routine COSIZLIB$DECOMPRESS failed
-COSI-F-FATINTERR, fatal internal error
%RMU-F-FATALERR, fatal error on RESTORE
%RMU-F-FTL_RSTR, Fatal error for RESTORE operation at 5-NOV-2009 16:08:45.89
=========================================

We have tried with restoring the file attributes but not success so far. We believe that there might be an issue with bzip2.

Thanks in advance.

Re: RBF backup image goes corrupt afer bzip usage

Hoff — Thu, 05 Nov 2009 15:57:56 GMT

Use zip, not bzip, here.

zip preserves this stuff, and zip 3.0 and unzip 6.0 and later handle large files.

Chances are that bzip stripped off some of the file system metadata.

You might be able to use SET FILE /ATTRIBUTES to restore the metadata, based on the attributes associated with an uncorrupted Rdb RBF file.

Re: RBF backup image goes corrupt afer bzip usage

smsc_1 — Thu, 05 Nov 2009 16:23:32 GMT

Thanks Hoff,
I'll try with zip 3 and unzip 6 or higher.
Where do you propose download them from for IA64?

Regards
Gianluca

Re: RBF backup image goes corrupt afer bzip usage

Steven Schweda — Thu, 05 Nov 2009 16:40:39 GMT

> [...] such preserving the file attributes.

Which bzip2 does not do.

> We have tried with restoring the file
> attributes but not success so far.

Not a useful description of what you tried
(or what happened when you tried it). You
might look at:

http://antinode.info/dec/sw/fixrec.html

> Where do you propose download them from for
> IA64?

http://info-zip.org/
ftp://ftp.info-zip.org/pub/infozip/vms/

The usual VMS binary kits offer only standard
"deflate" compression, which is usually not
so good as bzip2 compression, but, with a
little extra work (and a C compiler), Zip 3.0
and UnZip 6.0 can be built with support for
bzip2 compression. The details are in the
documentation.

Re: RBF backup image goes corrupt afer bzip usage

smsc_1 — Thu, 05 Nov 2009 16:49:58 GMT

thanks Steven,
But I can't compile it due to system limits.

Do you have please a link to .exe files (both for zip.exe and unzip.exe) ??

Thanks

Re: RBF backup image goes corrupt afer bzip usage

Steven Schweda — Thu, 05 Nov 2009 17:10:01 GMT

Try:

http://antinode.info/ftp/info-zip/u6z3_ia64.zip

Built on V8.3-1H1. Includes whole [.IA64L]
directories, so you may even be able to
re-link things, if needed.

[un]zip -v output should mention BZIP2 (and
LARGE_FILE_SUPPORT).

Wake me when it catches fire.

Re: RBF backup image goes corrupt afer bzip usage

Hoff — Thu, 05 Nov 2009 17:17:40 GMT

Just posted the basic details of building zip here:

http://forums13.itrc.hp.com/service/forums/questionanswer.do?threadId=1384424

Usage here:

http://labs.hoffmanlabs.com/node/575

Build details now posted here:

http://labs.hoffmanlabs.com/node/842

Re: RBF backup image goes corrupt afer bzip usage

smsc_1 — Thu, 05 Nov 2009 17:27:17 GMT

Thanks again Steven,
but is there any parameters I should use with new ZIP to retain metadata?

I tried wothout parameters but again I loose some file attribues like "Extend".

Re: RBF backup image goes corrupt afer bzip usage

Hoff — Thu, 05 Nov 2009 17:28:19 GMT

But you can't compile it due to system limits?

System limits? No.

These are management limits.

No test server?

No tools?

Here, your management seems to be trying to ensure that you and your business will fail.

I'd have a word with your boss.

Get the necessary tools.

Or get a test server.

Or both.

Or get a different boss, however you choose to do that.

Sorry, but life's too short to deal with this sort of "system limit".

Re: RBF backup image goes corrupt afer bzip usage

Hoff — Thu, 05 Nov 2009 17:30:50 GMT

Retaining OpenVMS file metadata?

zip "-V" retains metadata. The "-V" quoting is necessary when you're set to traditional parsing; when the default is set to SET PROCESS /PARSE = TRADITIONAL or when you're operating on an older release.

See:

http://labs.hoffmanlabs.com/node/575

Re: RBF backup image goes corrupt afer bzip usage

smsc_1 — Thu, 05 Nov 2009 17:35:04 GMT

OPS! Reading just now message from hoff...
I tried -V but .RBF goes always corrupt!!!

Using: zip -V db.zip db.rbf

Re: RBF backup image goes corrupt afer bzip usage

smsc_1 — Thu, 05 Nov 2009 17:55:52 GMT

Guys! The "" did the trick.
A zip and unzip, on the VMS system, are now possible and result in a running database.

Thanks

Re: RBF backup image goes corrupt afer bzip usage

Hoff — Thu, 05 Nov 2009 17:56:44 GMT

Quote it. The zip "-V" retains metadata. The quoting of the "-V" switch is necessary when you're set to traditional parsing within DCL. This when the DCL process parsing style is set to SET PROCESS /PARSE = TRADITIONAL or when you're operating on an older release, or when you're operating with the default DCL parsing on recent releases.

Re: RBF backup image goes corrupt afer bzip usage

smsc_1 — Thu, 05 Nov 2009 18:02:43 GMT

Ok, closing the post and give points to all people who help me!

Re: RBF backup image goes corrupt afer bzip usage

smsc_1 — Thu, 05 Nov 2009 18:03:25 GMT

Closing thread!

Re: RBF backup image goes corrupt afer bzip usage

Steven Schweda — Fri, 06 Nov 2009 04:15:11 GMT

> [...] "-V" quoting is necessary when [...]

As the (Zip 3.0 or UnZip 6.0) "-h" help says,

[...]
(Must quote upper-case options, like "-V", unless SET PROC/PARSE=EXTEND)

(In older versions, the upper-case options
were shown with quotation marks.)