Skip to content

Commit b933448

Browse files
paulofariadiasMartinSchoeler
authored andcommitted
(DOCS): Edit Database migration (RocketChat#1450)
* (DOCS): Edit Database migration * Edit header
1 parent 1bdf795 commit b933448

File tree

1 file changed

+5
-7
lines changed
  • administrator-guides/database-migration

1 file changed

+5
-7
lines changed

administrator-guides/database-migration/README.md

Lines changed: 5 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -6,9 +6,9 @@ The action of updating an older schema to a newer one (or vice versa) is called
66

77
When you incrementally update Rocket.Chat versions, database migration is automatic and you do not have to take any explicit action.
88

9-
However, from time to time, you may have need to skip multiple versions in your Rocket.Chat upgrades.
9+
However, from time to time, you may need to skip multiple versions in your Rocket.Chat upgrades.
1010

11-
Database migration may fail in these scenarios.
11+
Database migration may fail in a scenario like this.
1212

1313
A typical failure message is similar to:
1414

@@ -21,9 +21,9 @@ A typical failure message is similar to:
2121
| Database target version: 58 |
2222
```
2323

24-
As an example, the above migration is locked and stuck on 18. We need a target of 19 before migration to 58.
24+
As an example, the migration above is locked and stuck on 18. We need a target of 19 before migrating to 58.
2525

26-
One way to force migration is to manually unlock the migration in mongo and also increase database version to the target version (19).
26+
One way to force this migration is to manually unlock the migration in Mongo and also increase the database version to the target version (19).
2727

2828
```js
2929
use rocketchat
@@ -32,6 +32,4 @@ db.migrations.update({_id: 'control'},{$set:{locked:false,version:19}})
3232

3333
Restart Rocket.Chat and the migration should succeed now to the latest version.
3434

35-
Note that certain new values that are vital to Rocket.Chat operations may remain unpopulated when you skip versions.
36-
37-
For example, you may have to manually apply roles to users.
35+
**Note**: certain new values that are vital to Rocket.Chat operations may remain unpopulated when you skip versions. For example, you may have to manually apply roles to users.

0 commit comments

Comments
 (0)