[ovirt-users] Re: Upgrade from 4.1 to 4.2 failing - SQL Issues

25 Jul 2018

      Hi Simone,

if I use the same command as you did I get the following information:

[root@ovirt-engine ~]# sudo -u postgres scl enable rh-postgresql95 -- psql --list
could not change directory to "/root": Permission denied
                                              List of databases
         Name         |        Owner         | Encoding  |   Collate   |    Ctype    |   Access privileges
----------------------+----------------------+-----------+-------------+-------------+-----------------------
engine               | engine               | UTF8      | en_US.UTF-8 | en_US.UTF-8 |
 ovirt_engine_history | ovirt_engine_history | UTF8      | en_US.UTF-8 | en_US.UTF-8 |
 postgres             | postgres             | SQL_ASCII | C           | C           |
 template0            | postgres             | SQL_ASCII | C           | C           | =c/postgres          +
                      |                      |           |             |             | postgres=CTc/postgres
template1            | postgres             | UTF8      | en_US.utf8  | en_US.utf8  |
(5 rows)

As I’m not a DB admin, I don’t really know how go about these encodings. I restored the current system from a 4.1.7 Backup to a 4.1.9 image and all went well.

Do you need any other values ?

Thanks,
Sven

Von: Simone Tiraboschi [mailto:stirabos@redhat.com]
Gesendet: Dienstag, 24. Juli 2018 15:47
An: Sven Achtelik <Sven.Achtelik@eps.aero>; Yedidyah Bar David <didi@redhat.com>
Cc: users <users@ovirt.org>; Gobinda Das <godas@redhat.com>
Betreff: Re: [ovirt-users] Re: Upgrade from 4.1 to 4.2 failing - SQL Issues

Hi,
it seams still pretty close to https://bugzilla.redhat.com/show_bug.cgi?id=1528371 although that one was on lc_collate and this on encoding.
Adding also Didi.

I just double check on a system of mine upgrade from 4.1 to 4.2 and template1 is still on UTF8.

[root@enginevm tmp]# sudo -u postgres scl enable rh-postgresql95 -- psql --list
                                             List of databases
         Name         |        Owner         | Encoding |   Collate   |    Ctype    |   Access privileges
----------------------+----------------------+----------+-------------+-------------+-----------------------
 engine               | engine               | UTF8     | en_US.UTF-8 | en_US.UTF-8 |
 ovirt_engine_history | ovirt_engine_history | UTF8     | en_US.UTF-8 | en_US.UTF-8 |
 postgres             | postgres             | UTF8     | en_US.UTF-8 | en_US.UTF-8 |
 template0            | postgres             | UTF8     | en_US.UTF-8 | en_US.UTF-8 | =c/postgres          +
                      |                      |          |             |             | postgres=CTc/postgres
 template1            | postgres             | UTF8     | en_US.UTF-8 | en_US.UTF-8 | postgres=CTc/postgres+
                      |                      |          |             |             | =c/postgres
(5 rows)

So the point is why the upgrade process is trying to force SQL_ASCII.
Can you please share your env variable values?

On Tue, Jul 24, 2018 at 2:57 PM Gobinda Das <godas@redhat.com<mailto:godas@redhat.com>> wrote:
Hi Sven,
 I think you need to use same encoding.The error clearly says your dump encoding is "UTF8" and the new database encoding is "SQL_ASCII"
As per I know PostgreSQL does not convert encoding from one type to another during restore.
Can you please check what's the current encoding configured?

On Tue, Jul 24, 2018 at 5:00 PM, Sven Achtelik <Sven.Achtelik@eps.aero<mailto:Sven.Achtelik@eps.aero>> wrote:
Hi All,

I’m still struggling to upgrade from 4.1 to 4.2 and the root cause seems to be the SQL upgrade. I installed my 4.1.9 with the engine appliance image and restored a DB to it. My Upgrade to 4.2 is failing with the errors below:
--------------------------------
Performing Consistency Checks
-----------------------------
Checking cluster versions                                   ok
Checking database user is the install user                  ok
Checking database connection settings                       ok
Checking for prepared transactions                          ok
Checking for reg* system OID user data types                ok
Checking for contrib/isn with bigint-passing mismatch       ok
Checking for invalid "line" user columns                    ok
Creating dump of global objects                             ok
Creating dump of database schemas
  engine
  ovirt_engine_history
  postgres
  template1
                                                            ok

encodings for database "template1" do not match:  old "UTF8", new "SQL_ASCII"
Failure, exiting

I tried everything that could do and I also tried to find a solution on google to make this work. Could someone with DB knowhow please advise on the next steps to resolve this ? I really would like to upgrade somehow.

Thank you,
Sven

_______________________________________________
Users mailing list -- users@ovirt.org<mailto:users@ovirt.org>
To unsubscribe send an email to users-leave@ovirt.org<mailto:users-leave@ovirt.org>
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/
List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/H7KQJ4VDGVDBQX...

--
Thanks,
Gobinda
_______________________________________________
Users mailing list -- users@ovirt.org<mailto:users@ovirt.org>
To unsubscribe send an email to users-leave@ovirt.org<mailto:users-leave@ovirt.org>
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/
List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/T7AE7KYVIB2SXU...