# Upgrading to temporal 1.11.3

**URL:** <https://community.temporal.io/t/upgrading-to-temporal-1-11-3/2679>\
**Category:** Community Support\
**Tags:** upgrading\
**Created:** [August 9, 2021, 6:56am UTC](https://community.temporal.io/t/upgrading-to-temporal-1-11-3/2679 "2021-08-09T06:56:26Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![madhu](https://avatars.discourse-cdn.com/v4/letter/m/a8b319/32.png) [@madhu](https://community.temporal.io/u/madhu)\
**Post date:** [August 9, 2021, 6:56am UTC](https://community.temporal.io/t/upgrading-to-temporal-1-11-3/2679/1 "2021-08-09T06:56:26Z")

</div>

Hi i am just trying my hand out with v 1.11.3  
i was on 1.10.3 .

I was able to use the sql tool to upgrade temporal schema , but when i try to upgrade the visiblity schema i get the below error

> /etc/temporal # temporal-sql-tool update -schema-dir schema/mysql/v57/visibility/  
> 2021/08/09 06:44:38 UpdateSchemeTask started, config=&{DBName: TargetVersion: SchemaDir:schema/mysql/v57/visibility/ IsDryRun:false}  
> 2021/08/09 06:44:38 error listing schema dir:no subdirs found with version \>= 1.6

Any idea what i am missing? Please note i use mysql visisblity (not ES visiblity)

---

<div class="post-metadata">

**Author:** ![madhu](https://avatars.discourse-cdn.com/v4/letter/m/a8b319/32.png) [@madhu](https://community.temporal.io/u/madhu)\
**Post date:** [August 9, 2021, 7:55am UTC](https://community.temporal.io/t/upgrading-to-temporal-1-11-3/2679/2 "2021-08-09T07:55:23Z")

</div>

does this mean, there is no need to upgrade visiblity?

I am able to bring up temporal after temporal db upgrade alone.

But, i dont see the checksum in the logs too.

---

<div class="post-metadata">

**Author:** ![maxim](https://sea2.discourse-cdn.com/flex016/user_avatar/community.temporal.io/maxim/32/8_2.png) [@maxim](https://community.temporal.io/u/maxim)\
**Post date:** [August 9, 2021, 3:55pm UTC](https://community.temporal.io/t/upgrading-to-temporal-1-11-3/2679/3 "2021-08-09T15:55:12Z")

</div>

Please follow the release notes that contain instructions on upgrading visibility:

> **[Release v1.11.2 · temporalio/temporal](https://github.com/temporalio/temporal/releases/tag/v1.11.2)**
>
> Release Highlights
> IMPORTANT
> The release v1.11.2 reverts two PRs to fix a deadlock issue introduced in v1.11.0 and v1.11.1.
> 
> revert of #1699
> revert of #1697
> 
> The reason for reverting #1699 is to al...

---

<div class="post-metadata">

**Author:** ![alex](https://sea2.discourse-cdn.com/flex016/user_avatar/community.temporal.io/alex/32/15_2.png) [@alex](https://community.temporal.io/u/alex)\
**Post date:** [August 11, 2021, 11:03am UTC](https://community.temporal.io/t/upgrading-to-temporal-1-11-3/2679/4 "2021-08-11T11:03:34Z")

</div>

There were no changes to standard visibility in 1.11.x release.

You get this error because you forgot to specify visibility database name: `--db temporal_visibility` and tool tries to apply visibility schema changes to default database, which is `temporal`. Remember, main and visibility databases are different. Please refer to our [install-schema-mysql](https://github.com/temporalio/temporal/blob/master/Makefile#L348) `Makefile` target for examples.