Plugin:Dbx mdbx/pl: Difference between revisions

From Miranda NG
Plugin:Dbx mdbx/pl
Jump to navigation Jump to search
(Updating to match new version of source page)
(Updating to match new version of source page)
 
(18 intermediate revisions by the same user not shown)
Line 1: Line 1:
<languages/>{{PluginCard}}
<languages/>{{PluginCard}}
{{TNT|Warning| This database driver might suffer problems because of PC instability or disk damages. Thus that's vitally important to {{Plugin|PluginUpdater|make backups}} once a day to minimize the chance of data loss.}}
{{TNT|Warning|This database driver does not work correctly under Wine due to the lack of some necessary functions in the Wine itself. Use {{Plugin|Dbx_sqlite}} database driver.}}
Zapewnia obsługę bazy danych Mirandy: ustawień globalnych, kontaktów, historii, ustawień dla każdego kontaktu z osobna.
Zapewnia obsługę bazy danych Mirandy: ustawień globalnych, kontaktów, historii, ustawień dla każdego kontaktu z osobna.


<div class="mw-translate-fuzzy">
Wtyczka stworzona w oparciu o bibliotekę '''[https://github.com/leo-yuriev/libmdbx libmdbx]'''.
Wtyczka stworzona w oparciu o bibliotekę '''[https://github.com/leo-yuriev/libmdbx libmdbx]'''.
</div>
== Database check ==
<pre style="overflow:auto;">
Miranda32.exe /svc:dbchecker
</pre>
or
<pre style="overflow:auto;">
Miranda64.exe /svc:dbchecker
</pre>
== Database repair ==
{{TNT|Important|Make a backup copy of the damaged database before restoring!}}
mdbx_chk.exe is located in the Miranda root folder.
<pre style="overflow:auto;">
mdbx_chk.exe -i -w -v -t -1 "path\to\corrupted.dat"
</pre>
This command will select the second to last meta page (since the last one is probably pointing to corrupted snapshot).
Each meta page contains the necessary information (number transactions, geometry, etc.) as well as a pointer (usually) to
own MVCC snapshot that seems to "float" in many pages along with the rest of the MVCC snapshots. Each such snapshot is generated when the writing transaction is committed.
== If the above does not help ==
mdbx_dump.exe and mdbx_load.exe are located in the Miranda root folder.
<pre style="overflow:auto;">
mdbx_dump.exe -n -a -f "%TEMP%\corrupted.tmp" "path\to\corrupted.dat"
mdbx_load.exe -n -a -f "%TEMP%\corrupted.tmp" "path\to\repaired.dat"
</pre>
This extracts as much data as possible from the corrupted.dat to the temporary file and builds repaired.dat.


{{PluginGroups}}
{{PluginGroups}}

Latest revision as of 18:10, 10 February 2021

Other languages:
Miranda NG MDBX database driver

Nazwa pliku Dbx_mdbx.dll
Autor Miranda NG team
Pobierz
Wersja stabilna: 32-bit, 64-bit
Wersja rozwojowa: 32-bit, 64-bit

Uwaga
This database driver might suffer problems because of PC instability or disk damages. Thus that's vitally important to make backups once a day to minimize the chance of data loss.
Uwaga
This database driver does not work correctly under Wine due to the lack of some necessary functions in the Wine itself. Use Dbx_sqlite database driver.

Zapewnia obsługę bazy danych Mirandy: ustawień globalnych, kontaktów, historii, ustawień dla każdego kontaktu z osobna.

Wtyczka stworzona w oparciu o bibliotekę libmdbx.

Database check

Miranda32.exe /svc:dbchecker

or

Miranda64.exe /svc:dbchecker

Database repair

Ważne
Make a backup copy of the damaged database before restoring!

mdbx_chk.exe is located in the Miranda root folder.

mdbx_chk.exe -i -w -v -t -1 "path\to\corrupted.dat"

This command will select the second to last meta page (since the last one is probably pointing to corrupted snapshot).

Each meta page contains the necessary information (number transactions, geometry, etc.) as well as a pointer (usually) to own MVCC snapshot that seems to "float" in many pages along with the rest of the MVCC snapshots. Each such snapshot is generated when the writing transaction is committed.

If the above does not help

mdbx_dump.exe and mdbx_load.exe are located in the Miranda root folder.

mdbx_dump.exe -n -a -f "%TEMP%\corrupted.tmp" "path\to\corrupted.dat"
mdbx_load.exe -n -a -f "%TEMP%\corrupted.tmp" "path\to\repaired.dat"

This extracts as much data as possible from the corrupted.dat to the temporary file and builds repaired.dat.