Re: [U2] fixtool help
FIXTOOL Use FIXTOOL to both verify and repair UniVerse files. Exclusive access to the file is required to when using the `-fix’ option to repair the file. SYNTAX FIXTOOL – file [filename] [-level #] [-dumppath dir] [-nodump] [-filepath path] [-help] [-logging] [-logpath] [-start #] [-stop #] [-zero] QUALIFIERS -file filename specifies the name of the file to process. If file is not local to the current account must use in conjunction with – filepath option. -filepath path specifies the directory where the file is located. Necessary when executing the command from a different directory. -level # Specifies the verbosity level of the information that will be output from fixtool. Level specified with value of 1-10. NOTE: Must use –start and/or –stop otherwise -level will be ignored. `-level 4’ will display the address of each record block in the file. `-level 5’ will display the record keys and data. - fix Indicates that fixtool should attempt to repair any corruption detected. -dumppath path Indicates the location where the temporary directory used by the fixtool should be located. A sub-directory in the form `dump.’filename will be created at this location. Default is to create the directory in the current directory. -nodump This switch indicates that fixtool should bypass creating the temporary dump directory. -help Display a brief screen containing the command line arguments available for fixtool. -logging Indicates that fixtool should create a sub-directory to log the errors encountered during processing. The sub-directory is created as `log.’ followed by the filename. Within this directory is a text file `LOGFILE’ that contains information regarding the problems detected with the file. -logpath Maybe used in conjunction with –logging option to specify a different location to use when creating the `log.’ Sub-directory that will contain the LOGFILE. See –logging option. -start # Maybe used to limit the scan and repair to a range of groups. By default fixtool will process all groups in the file. -stop # Maybe used to limit the scan and repair to a range of groups. By default fixtool will process all groups in the file. -zero This switch is used to clear a range of groups. All data within the targeted groups will be removed from the file. This option requires both the –start and –stop arguments be used to limit the function to a range of groups. DESCRIPTION fixtool was developed as part of the project to support 64BIT files in UniVerse. It is intended to replace uvfixfile which may only be used with older style 32BIT files. fixtool can be used to verify the integrity of UniVerse files without having to take the file off-line. When tracing a file (no-fix) it is possible to receive `bogus’ errors when a group is being updated at the same time it is being processed by fixtool. When tracing a file that is in use, it is recommended that any problem groups be processed a second time using the – start and –stop options to verify that the group in question is indeed corrupt. It is recommended that the `logging’ option be used when tracing a file. This option will create a sub-directory that contains a `LOGFILE’ with information specific to the location and type of errors detected. This file can later be used to process only those groups that contain errors. This approach will limit the time the file must be off-line. The `-fix’ option should never be executed against the only copy of the file. It is recommended that a backup copy of the file be made prior to attempting to fix the file. The fixtool utility may create sub-directories. By default the fixtool utility will create a `dump’ directory for the file in the event it is needed. This directory will be named `dump.’ followed by the file name. The creation of this directory may be suppressed by using the `-nodump’ command argument. If the `logging’ option is used fixtool will create a subdirectory to store the log created during processing. This directory will be created as `log.’ Followed by the file name. Once the process of a given file has been completed the `log.’ And `dump.’ Subdirectories may be removed from the system. NOTE NOTE: Using –start and/or –stop options will eliminate certain types of error checking. For example when –start and/or –stop is used the free-chain pointer of a file is not validated. Data bytes used in dynamic files to determine when a split or merge operation should occur will not be validated when –start and/or –stop is used. EXAMPLES This example traces the first 1000 groups of `XYZ’ file logging any errors to `log.XYZ/LOGFILE’. fixtool –file XYZ –logging –start 1 –stop 999 This example will dump the record keys and data for group 101 in file XYZ to stdout: fixtool –file XYZ –level 5 –start 101 –stop 101 This example will clear group 101, any data present will be lost. fixtool –file XYZ –start 101 –stop 101 –zero This option will put the temporary subdirectories into the /tmp directo
RE: [U2] fixtool
> - Original Message - > From: "Dan Fitzgerald" <[EMAIL PROTECTED]> > To: u2-users@listserver.u2ug.org > Subject: RE: [U2] fixtool > Date: Mon, 4 Aug 2008 13:59:55 -0400 > "Wide and shallow" shall be your files. That was Dan channeling Yoda (though the verb should have been at the end: wide and shallow your files shall be). It's good advice nonetheless. --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
RE: [U2] fixtool
Heehee, Chuck! I once heard a 3rd party presidential candidate refer to the
major parties' "fixing Social Security" that way.
You can use fixtool in the interactive mode, if you really feel bold,
adventurous, know what you're doing and it helps if your family owns the
company. If it's a broken flink, you're pretty much hosed (ok, you _could_
restore the file somewhere else from tape & find the proper flink for that
frame by looking at the restored file). But if it's a blink, you can trace to
the break, and key in the proper backward link, fixing - er, "correcting" -
the chain.
May I interject here that this is (to me) a major reason why you want to avoid
overflow. "Wide and shallow" shall be your files. If you have no overflow (an
impossible ideal, but strive in that direction), you cannot have broken links
to overflow. > Subject: RE: [U2] fixtool> Date: Mon, 4 Aug 2008 12:04:30
-0400> From: [EMAIL PROTECTED]> To:
u2-users@listserver.u2ug.org> > > > I read somewhere that all it does is fix
the broken link ("fixing"> the > > > file but losing the data that the broken
link pointed to).> > > > This may be all that can be done. A backward link
error often means> that> > two groups apparently own the same overflow block.
The data of one> will> > have overwritten the other. There is no way that any
recovery tool> could> > ever get back the lost data.> > Yes, data truncated. >
"Fix", as in when you get your dog "fixed": snip, snip.> ---> u2-users
mailing list> u2-users@listserver.u2ug.org> To unsubscribe please visit
http://listserver.u2ug.org/
_
Your PC, mobile phone, and online services work together like never before.
http://clk.atdmt.com/MRT/go/108587394/direct/01/
---
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/
RE: [U2] fixtool
> > I read somewhere that all it does is fix the broken link ("fixing"
the
> > file but losing the data that the broken link pointed to).
>
> This may be all that can be done. A backward link error often means
that
> two groups apparently own the same overflow block. The data of one
will
> have overwritten the other. There is no way that any recovery tool
could
> ever get back the lost data.
Yes, data truncated.
"Fix", as in when you get your dog "fixed": snip, snip.
---
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/
Re: [U2] fixtool
Hi Doug,
is fixtool the best way to repair a universe file?
In my experience with the various repair tools over many years of working
with UniVerse, fixtool does seem to be able to repair more corruptions than
the previous tools.
I read somewhere that all it does is fix the broken link ("fixing" the
file but losing the data that the broken link pointed to).
This may be all that can be done. A backward link error often means that two
groups apparently own the same overflow block. The data of one will have
overwritten the other. There is no way that any recovery tool could ever get
back the lost data.
Martin Phillips, Ladybridge Systems Ltd
---
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/
