Anonymous_User Absent Member.
Absent Member.
595 views

FiLR-Upgrade 3.4.3 -> 4.0.0.155: DB not migrated

Hi,

during an upgrade of a small-deployment FiLr it seems that the DB was
not migrated:

The new VA is running and the access to VA-Admin console is possible.
But the access to the FiLR services ifself are not possible because they
are not running. (All other services shown at the VA-Console are
Running) When checking 'Filr Appliance Tools / Configuration' in
VA-Console I get: Failed to setup and migrate to PostgreSQL database.

Postgres is running;
A user named 'filr' exists;
In /vastorage/mysql-backup/
are the files:final-dump.psql; mysql-dump.sql; old-sequence and
sequence-dump.psql

But I am miss the filr db. Postgres shows only the three std. DB
(postgres, template0 and template1)

Any hints?

Bernd
0 Likes
7 Replies
Highlighted
Anonymous_User Absent Member.
Absent Member.

Re: FiLR-Upgrade 3.4.3 -> 4.0.0.155: DB not migrated

Am 24.04.19 um 12:00 schrieb nntp-user:
> Hi,
>
> during an upgrade of a small-deployment FiLr it seems that the DB was
> not migrated:
>
> The new VA is running and the access to VA-Admin console is possible.
> But the access to the FiLR services ifself are not possible because they
> are not running. (All other services shown at the VA-Console are
> Running) When checking 'Filr Appliance Tools / Configuration' in
> VA-Console I get: Failed to setup and migrate to PostgreSQL database.
>
> Postgres is running;
> A user named 'filr' exists;
> In /vastorage/mysql-backup/
> are the files:final-dump.psql; mysql-dump.sql; old-sequence and
> sequence-dump.psql
>
> But I am miss the filr db. Postgres shows only the three std. DB
> (postgres, template0 and template1)
>
> Any hints?
>
> Bernd


The log says that the role root does not exists and the password of user
postgres does not match. When changing
/vastorage/postgres/conf/vabase-pg_hba.conf line 1 an 2 from 'md5' to
'trust' and restart postgreSQL the VA-Admin shows a turning icon but
nothing happens ... the db did not created.

Even if I create the role(user) root (privileges createdb) and restart
nothing happens 😕

How is the way to migrate the db afterwards?

Bernd
0 Likes
Smaharana Absent Member.
Absent Member.

Re: FiLR-Upgrade 3.4.3 -> 4.0.0.155: DB not migrated

Hi

Can you please provide us with the logs inside the folder /var/opt/novell/va/logs/ folder?

Thanks
Sachi
0 Likes
Smaharana Absent Member.
Absent Member.

Re: FiLR-Upgrade 3.4.3 -> 4.0.0.155: DB not migrated

Hi Bernd


In filr 3-4-3 , do you have dbusername configured other than filr?

Then it will cause a problem.

Thanks
Sachi
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: FiLR-Upgrade 3.4.3 -> 4.0.0.155: DB not migrated

Am 25.04.19 um 09:04 schrieb Smaharana:
(...)
> In filr 3-4-3 , do you have dbusername configured other than filr?
>
> Then it will cause a problem.

(...)

Yes, this was the reason.

I was trapped by the premigration tool. This ends with the line that it
was successfull ... so I go forward. But then ... 😕

Maybe the migration script can be changed to rebuild the SQL dump to
reflect the new username?!

For a major release upgrade I would expect that the migration tools are
more ... failure resistent.

Nov^wMF products are business solutions. And they are used for a long
time with upgrades from version to version w/o a new installation (we
are not at M$ were you should recommended to do a fresh install to get a
SW running ...)


Bernd

0 Likes
vduggi Absent Member.
Absent Member.

Re: FiLR-Upgrade 3.4.3 -> 4.0.0.155: DB not migrated

Hi Bernd,

Is it possible to change the dbuser name to 'filr' in 3.4.3 appliance? It will work if the db username is 'filr'.

Follow this TID on Filr appliance. https://support.microfocus.com/kb/doc.php?id=7016687

Thanks
Venkat
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: FiLR-Upgrade 3.4.3 -> 4.0.0.155: DB not migrated

Am 29.04.19 um 12:36 schrieb vduggi:
(...)
> Is it possible to change the dbuser name to 'filr' in 3.4.3 appliance?

(...)

Log into the VAadmin-Console (Port 9443) and choose 'Configuration' and
there 'Database'. Change the DB-User and password. (after you has
followed the TID 7016687.)

Bernd
0 Likes
Smaharana Absent Member.
Absent Member.

Re: FiLR-Upgrade 3.4.3 -> 4.0.0.155: DB not migrated

Now if you upgrade there will be no issues with dbmigration during upgrade.
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.