|
Last change
on this file was
19532,
checked in by westram, 5 weeks ago
|
- reintegrates 'help' into 'trunk'
- tweak arb documentation:
- automatically link
- ticket references to arb
 tracker (only affects html version).
- found URLs.
- page titles
- warn about long titles.
- introduce SUBTITLEs (automatically triggered by multi-line titles in source files).
- increase allowed length (limited by subwindow width).
- cleanup header sections in all helpfiles.
- fix and/or update several help files.
- document syntax of help sources.
- build issues:
- when xml validation fails, next build no longer uses invalid xml ⇒ keeps failing.
- remove output files on error (including files below ARBHOME/lib).
- pipe output through logs to ensure proper wrapping in Entering/Leaving lines.
- moves Tree admin + NDS menu entries to top of menu
- adds: log:branches/help@18783:19531
|
|
File size:
1.6 KB
|
| Line | |
|---|
| 1 | # main topics: |
|---|
| 2 | UP arb.hlp |
|---|
| 3 | UP glossary.hlp |
|---|
| 4 | |
|---|
| 5 | # sub topics: |
|---|
| 6 | #SUB subtopic.hlp |
|---|
| 7 | |
|---|
| 8 | # format described in ../help.readme |
|---|
| 9 | |
|---|
| 10 | |
|---|
| 11 | TITLE Re-repair database |
|---|
| 12 | |
|---|
| 13 | OCCURRENCE ARB_NT/Tools/DB admin/Re-repair DB |
|---|
| 14 | |
|---|
| 15 | DESCRIPTION At startup ARB_NT runs several checks about known database problems. |
|---|
| 16 | |
|---|
| 17 | These are problems that were caused by buggy ARB versions and may have |
|---|
| 18 | caused specific incorrect data in your database. |
|---|
| 19 | |
|---|
| 20 | Normally it is enough to run each check once, repair the problem if it gets |
|---|
| 21 | detected and remember, that the problem has been |
|---|
| 22 | checked (that's how it works behind the scenes). |
|---|
| 23 | |
|---|
| 24 | Problems arise if such a "repaired database" is loaded again into an older, still |
|---|
| 25 | buggy ARB-installation, which then again may break already fixed data. |
|---|
| 26 | Afterwards your newer ARB-installation will assume things are already fixed and |
|---|
| 27 | fine, while the opposite is true. |
|---|
| 28 | |
|---|
| 29 | Such a scenario might happen e.g. if you give a database to a colleague who does some |
|---|
| 30 | modifications and then brings the database back to you. |
|---|
| 31 | |
|---|
| 32 | In doubt call the function described here. It will re-run all available checks |
|---|
| 33 | and again attempt to repair all detected problems. |
|---|
| 34 | |
|---|
| 35 | NOTES Most checks report whether problems are detected and if they get fixed. |
|---|
| 36 | |
|---|
| 37 | If you get such reports after the scenario above, please |
|---|
| 38 | encourage your colleague to update to a newer ARB version ;-) |
|---|
| 39 | |
|---|
| 40 | EXAMPLES None |
|---|
| 41 | |
|---|
| 42 | WARNINGS None |
|---|
| 43 | |
|---|
| 44 | BUGS No bugs known |
|---|
Note: See
TracBrowser
for help on using the repository browser.
