Re: [Gnumed-devel] gnumed upgrade failure.

[Karsten Hilbert]

On Tue, Nov 26, 2013 at 01:56:52PM +0530, Vaibhav Banait wrote:

> Most problems appeared to be sorted out with new server installation. But few 
> problems still persists. Here is a log.

You are VERY nearly there.

The database has been upgraded successfully:

> 2013-11-26 12:16:21  INFO      gm.db 
> (d:\workplace\gnumed-server.19.1\build\pyi.win32\gnumed\outpyz1.pyz\gnumed.pycommon.gmpg2::database_schema_compatible()
>  #512): detected schema version [19], hash [9765373098b03fb208332498f34cd4b5]
> 2013-11-26 12:16:21  INFO      gm.bootstrapper 
> (<string>::verify_result_hash() #1025): database identity hash properly 
> verified

The only remaining thing is a data migration
plausibility check problem:

> 2013-11-26 12:16:21  ERROR     gm.bootstrapper 
> (<string>::check_data_plausibility() #880): plausibility check [paperwork 
> templates] failed, expected [79], found [80]
> 2013-11-26 12:16:21  ERROR     gm.bootstrapper (<string>::exit_with_msg() 
> #1439): Bootstrapping failed: plausibility checks inconsistent

In the clear this means that the bootstrapper expects
one additional paperwork template to exist in v19
as compared to v18. But it finds two more. This is
rather strange because the bootstrapper only inserts
one new template.

Let's have a look at the real data. Please run the following
query against both your v18 and your v19:

        select * from ref.v_paperwork_templates;

and report both outputs.

Karsten
-- 
GPG key ID E4071346 @ gpg-keyserver.de
E167 67FD A291 2BEA 73BD  4537 78B9 A9F9 E407 1346