Comments on: Corrupt download caused installation to hang, unzip lessons learned

By: Dan Norris

Dan Norris — Fri, 05 Sep 2008 23:32:30 +0000

Good tips. I am pretty sure I'll remember unzip -q before I'll remember
to check the exit code. Weird how I usually remember to check $? in a
script, but never do it interactively.

Thanks for the ideas!

By: markie_mark

markie_mark — Fri, 05 Sep 2008 19:52:21 +0000

Ah yeah - and a general good practice is to check the error code of the command you last ran (especially for important steps!).

$ echo $?

Will return the exit status of the last command - generally '0' implies a successful execution - consulting the man page for most commands will give a detailed description of the exit status meanings:

DIAGNOSTICS
The exit status (or error level) approximates the exit codes defined by PKWARE and takes on the following values, except under VMS:

0 normal; no errors or warnings detected.

1 one or more warning errors were encountered, but processing completed successfully anyway. This includes zipfiles where one or more files was skipped due to unsupported compression
method or encryption with an unknown password.

HTH

Mark

By: markie_mark

markie_mark — Fri, 05 Sep 2008 19:25:55 +0000

Another “gotya” of this nature is with tar files, especially with the non-GNU versions of tar, some of which have limitations with the length of basename and filename – resulting in tar spitting out files which are not usable – this is especially prevalent in older traditional unix systems (Solaris etc.). The problem is reported however because most people execute tar with the verbose flag that there is so much output you don't notice the errors – $ tar xfv mark.tar. If you drop the verbose flag – only errors and the tar summary are printed.

The resolution to opening tar files with long pathname is to install and use the GNU version of tar (often called gtar) and use it when manually creating and extracting tar files (Note: do not replace the system tar – it's used by pkginfo).

HTH

By: Dan Norris

Dan Norris — Fri, 05 Sep 2008 16:32:30 +0000

By: markie_mark

markie_mark — Fri, 05 Sep 2008 12:52:21 +0000

By: markie_mark

markie_mark — Fri, 05 Sep 2008 12:25:55 +0000

HTH

By: Jeremy

Jeremy — Thu, 28 Aug 2008 18:22:03 +0000

Useful tip. I've now started using the -q flag most of the time when I do an unzip. Thanks!

By: Dan Norris

Dan Norris — Thu, 28 Aug 2008 11:47:20 +0000

I hadn't checked the certification matrix on that, but I am rarely
seeing 3rd party clusterware being used these days (maybe it's just me),
so I haven't had a need to look it up. Thanks for the tip.

By: Miles Anderson

Miles Anderson — Thu, 28 Aug 2008 11:29:00 +0000

Dan,

Thanks for clearing up this issue with Clusterware and Oracle. Just so you know Oracle RAC with RHEL-5 OS is only certified with Oracle Clusterware.

Thanks,
Miles

By: Dan Norris

Dan Norris — Wed, 27 Aug 2008 11:56:14 +0000

It sure could have, but this .zip file had been successfully been used
previously on other computers, so it was presumed to be “good” and there
was no reason to go through the extra checking step at this point. The
issue must have been when the .zip was copied from the shared drive to
my local machine–somehow a corruption was introduced during that copy.
Good tip, though–it'll definitely be on my list for troubleshooting if
this happens again!