Page locked

This page is currently locked for editing by another user. You have to wait until this user finishes editing or the lock expires.
Currently locked by: 172.69.214.137,216.73.216.155
Lock expires at: 2025/10/30 10:30 (14 min)
This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.
===== How to Upgrade the Chia db =====

Upgrading the Chia db from v1 to v2 The process of upgrading the Chia db CAN be a very simple process. 
However, the reason you are reading this guide is most probably because you want to learn how to upgrade AFTER your drive is full and you don't want to sync from scratch. 

We will go through three different ways:
  - Upgrading the easy way
  - Download v2 from a trusted source and replace v1 
  - Using an external SSD


==== Updating the easy way ====

  * in CLI change directory to chia ''cd c:\Users\%USERNAME%\AppData\Local\chia-blockchain\a*\resources\app.asar.unpacked\daemon\''
  * run ''chia db upgrade'' in CLI. 
  * Update your config.yaml under the ''full_node:'' section from ''database_path: db/blockchain_v1_CHALLENGE.sqlite'' to ''database_path: db/blockchain_v2_CHALLENGE.sqlite''. 


There are two prerequisites for upgrading the Chia db the easy way. 
  * enough space on the target directory
  * enough space on your temporary directory (often overlooked)

For further reference, see https://github.com/Chia-Network/chia-blockchain/wiki/FAQ#what-is-the-new-database. 

==== Download and replace ====
The advantage of this method is that it is easy and has minimal downtime. The trick is to download the db right after the snapshot, so your node needs to do minimal syncing to catch up with the latest blockheight. The downside is that you need to trust the source from which you download the snapshot. 

  - Stop all chia processes
  - go to DIRECTORY
  - delete the VERSION1DB
  - download trusted v2
  - edit config.yaml

==== Using an external SSD ====

  * stop all chia processes ''chia stop all''
  * [[guides/farming/movedb|Move the chia db v1 to another folder]]
  * Make sure your TMP folder has enough space available (size of v1+v2). If not, see the fix under "Error when TMP folder full".
  * in CLI change directory to chia ''cd c:\Users\%USERNAME%\AppData\Local\chia-blockchain\a*\resources\app.asar.unpacked\daemon\''
  * ''chia db upgrade''
  * when done, ''chia start all'' and wait for it to sync

=== Error when TMP folder full ===
The method above doesn't work if your TMP folder (which is  ''C:\Users\%USERPROFILE%\Appdata\Local\Temp'' by default on Windows) is on the full drive. 

You will attempt to do so, you get a pop-up with the following window somewhere in the process: 
<code>Chia.exe - Delayed Write Failed
Windows was unable to save all the data for the file \chiaDB\blockchain_v2_mainnet.sqlite: the data has been lost. 
This error may be caused if the device has been removed or the media is write-protected.</code>

And in the CLI you will find the following:
<code>Conversion failed with error: disk I/O error. 
The target v2 database is left in place (possibily in an incomplete state) D:\<PathforDB>\blockchain_v2_mainnet.sqlite

If your failure was caused by a full disk, ensure the volumes of your temporary- and target directory have sufficient free space. 
Your temporary directory may be ''C:\Users\%USERNAME%\Appdata\Local\Temp''
you can specify the "TMP" environment variable to control the temporary directory to be used. </code>

The work-around for this is to change your temporary folder to the new SSD (temporarily), by configuring your accounts Environmental Variables.

  * Go to Settings and search: edit environmental variables for your account
  * Edit the TMP field and change from ''C:\Users\%USERPROFILE%\Appdata\Local\Temp''  to the new drive, e.g. ''D:\chiaDB\''
  * In case you already used ''chia db upgrade'', remove the blockchain_v2_mainnet.sqlite that was created in your target folder.
  * ''chia db upgrade''