Difference: FileAnalysisAndRecovery (2 vs. 3)

Revision 32012-02-29 - ChrisBrower

Line: 1 to 1

META TOPICPARENT	name="SystemAdministration"

File Analysis and Recovery

The appx utilities, found in the /tools directory below the appx engine, allow batch manipulation and recovery of AppxIO files. In the Windows environment, execute these commands from a DOS popup box. Or use the command line to perform the same functions in Unix.

File Analysis and Recovery

Line: 39 to 39

(Consider the possibility of building your desired command line invocation strings in MS Word, Notepad or WordPad, then cutting and pasting them into your DOS box.)

For more information on appxutil.exe, see the APPXUTIL Overview.

Changed:

<
<

Verifying and Analyzing a File

>
>

Verifying and Analyzing a File

In Windows:	%APPXPATH%\..\tools\appxutil.exe -v={filename}
In Unix:	$APPXPATH/../tools/appx -v={filename}

Deleted:

<
<

... will manually verify an APPX datafile. This does the same thing as interactive "Verify Files Menu", "Verify Integrity" from the Database, Design File, and System Administration File Management menus, but from a command line.

If the invocation of this command results in no output, then the file passes verification. Any output from this command means that the file fails verification.

Changed:

<
< To analyze a damaged file ...

>
> To analyze a damaged file ...

In Windows:	%APPXPATH%\..\tools\appxutil.exe -an={filename}
In Unix:	$APPXPATH/../tools/appx -an={filename}

Changed:

<
<

>
>

... gives you a"BRF>" prompt for {filename}. The most useful command at this prompt is ...

Line: 103 to 101

If the file doesn't pass #ALL verification, but does pass COUNT REC verification, then it means that the *.dat portion of the file is probably OK, but the *.key indices are probably damaged. In this case, rename or delete the *.key file, then run 3)CreateFiles. This will recreate your indices from scratch. It will then be safe to export and re-import the file.

Changed:

<
< (For quite large files, it may be faster to use the 'recover.exe' procedure below, then 3)CreateFiles to recreate your keyfile, albeit at the cost of more designer time required to do this safely.)

>
> (For quite large files, it may be faster to use the 'recover.exe' procedure below, then 3)CreateFiles to recreate your keyfile, albeit at the cost of more designer time required to do this safely.)

Changed:

<
<

If the file doesn't pass COUNT REC analysis, you have a seriously damaged *.dat file. Your best bet at this point is to use the recover.exe procedure below, or if necessary restore from backup.

File Recovery: appx -r (or -recover)

>
>

If the file doesn't pass COUNT REC analysis, you have a seriously damaged *.dat file. Your best bet at this point is to use the recover.exe procedure below, or if necessary restore from backup.

File Recovery: appx -r (or -recover)

Usage:

In Windows:

%APPXPATH%\..\appx.exe -r old.file new.file [deleted.record.file]

Line: 146 to 144

Space Allocation Reduction = 0 bytes

* You MUST create a new '.key' file that matches your new '.dat' file!

Changed:

<
<

What to do with a file that Fails Verification?

>
>

What to do with a file that Fails Verification?

Deleted:

<
<

If 13)Verify 1)Integrity results in a 'Failed' condition, perform the following procedure:

Line: 191 to 189

Read what other users have said about this page or add your own comments.

Changed:

<
<

<--/commentPlugin-->

>
>

<--/commentPlugin-->

\ No newline at end of file

View topic | History: r8 < r7 < r6 < r5 | More topic actions...