Re: [Gnumed-devel] Fix up script

[Sebastian Hilbert]

Am Montag, 16. Dezember 2013, 18:59:15 schrieb Karsten Hilbert:
> On Sat, Dec 14, 2013 at 07:43:35PM +0530, Vaibhav Banait wrote:
> > Thanks for identifying the problem. I had presumed
> > that database upgrade are required only for major
> > version upgrade. I had decided the I would not
> > go for minor updates after 1.7.
> > 
> > Would you like to point out the server version and fix up+
> > script I should run before trying out v1.4 . Kindly guide.
> 
> AFAIK the Windows packages so far do not offer point-and-click
> running of fixup scripts so ATM it would need some manual
> running of things on the commandline. I am not sure I can
> safely say how to do that on Windows.
> 
> Sebastian is likely going to provide guidance but it will
> take some time, maybe even past Christmas.
> 
> The general principle is to go find the fixup-db.sh script
> -- which lives in .../server/bootstrap/ -- and run that
> with the argument 18 as, root, postgres, admin ?
> 
> Karsten
Since the upgrade v18 to v19 does include all the fixup scripts I have prepared 
v19.4 for Windows. The template count which failed has been deactivated for 
v19.4 on Windows. This pretty much means it should be possible to install 
v19.4 package, upgrade (not bootstrap) the database (v18.x to v19.4) and have 
all the required fixups taken care of by the upgrade.

Once the upgrade ran check c:\Programme\gnumed-server\GNUmed\bootstrap\

for update_db-v18_v19.log

In my test installation the last few lines read

2013-12-16 16:40:54  INFO      gm.bootstrapper 
(<string>::check_data_plausibility() #884): plausibility check [vaccines (must 
have indications)] succeeded
2013-12-16 16:40:54  INFO      gm.bootstrapper 
(<string>::check_data_plausibility() #884): plausibility check [vaccinations] 
succeeded
2013-12-16 16:40:54  INFO      gm.bootstrapper 
(<string>::check_data_plausibility() #884): plausibility check [requests on 
results] succeeded
2013-12-16 16:40:54  INFO      gm.bootstrapper 
(<string>::check_data_plausibility() #884): plausibility check [clinical code 
links (total) - internal consistency] succeeded
2013-12-16 16:40:54  INFO      gm.bootstrapper 
(<string>::check_data_plausibility() #884): plausibility check [automatic 
hints] succeeded
2013-12-16 16:40:54  INFO      gm.bootstrapper 
(<string>::check_data_plausibility() #884): plausibility check [raw keyword 
expansions] succeeded
2013-12-16 16:40:54  INFO      gm.bootstrapper 
(<string>::check_data_plausibility() #884): plausibility check [mapped keyword 
expansions] succeeded
2013-12-16 16:40:54  INFO      gm.bootstrapper 
(<string>::check_data_plausibility() #884): plausibility check [at least one 
org unit (thereby org)] succeeded
2013-12-16 16:40:54  INFO      gm.bootstrapper (<string>::connect() #253): 
trying DB connection to gnumed_v19 on localhost as postgres
2013-12-16 16:40:54  DEBUG     gm.db (d:\workplace\gnumed-
server.19.4\build\pyi.win32\gnumed\outpyz1.pyz\gnumed.pycommon.gmpg2::get_raw_connection()
 
#1536): new database connection, backend PID: 1612, readonly: False
2013-12-16 16:40:54  DEBUG     gm.db (d:\workplace\gnumed-
server.19.4\build\pyi.win32\gnumed\outpyz1.pyz\gnumed.pycommon.gmpg2::get_raw_connection()
 
#1575): access mode [READ WRITE]
2013-12-16 16:40:54  DEBUG     gm.db (d:\workplace\gnumed-
server.19.4\build\pyi.win32\gnumed\outpyz1.pyz\gnumed.pycommon.gmpg2::get_connection()
 
#1638): client string encoding [UTF8], isolation level [serializable], time 
zone [01:00:00.00]
2013-12-16 16:40:54  INFO      gm.bootstrapper (<string>::connect() #264): 
successfully connected
2013-12-16 16:40:54  INFO      gm.bootstrapper 
(<string>::check_holy_auth_line() #913): hba file: 
C:/Programme/PostgreSQL/9.3/data/pg_hba.conf
2013-12-16 16:40:54  INFO      gm.bootstrapper 
(<string>::check_holy_auth_line() #932): did not find active standard GNUmed 
authentication directive in pg_hba.conf
2013-12-16 16:40:54  INFO      gm.bootstrapper 
(<string>::check_holy_auth_line() #933): regex: local.*samerole.*\+gm-logins
2013-12-16 16:40:54  INFO      gm.bootstrapper 
(<string>::check_holy_auth_line() #944): did not find inactive standard GNUmed 
authentication directive in pg_hba.conf either
2013-12-16 16:40:54  INFO      gm.bootstrapper 
(<string>::check_holy_auth_line() #945): regex: #\s*local.*samerole.*\+gm-
logins
2013-12-16 16:40:54  INFO      gm.bootstrapper 
(<string>::check_holy_auth_line() #947): bootstrapping is likely to have 
succeeded but clients probably cannot connect yet
2013-12-16 16:40:54  WARNING   gm.bootstrapper (<string>::main() #1605): open 
connection detected: database.__connect_owner_to_db via 
database.__connect_superuser_to_db
2013-12-16 16:40:54  WARNING   gm.bootstrapper (<string>::main() #1606): 
<connection object at 0x00F1D608; dsn: 'dbname=gnumed_v19 port=5432 
user=postgres password=xxxxxxxxxxxxxxxx sslmode=prefer', closed: 0>
2013-12-16 16:40:54  WARNING   gm.bootstrapper (<string>::main() #1607): 
closing connection
2013-12-16 16:40:54  INFO      gm.bootstrapper (<string>::main() #1610): 
shutdown

which shows that the template check has not run and apparently the upgrade 
succeeded.

Download from 
http://www.gnumed.de/downloads/server/v19/

http://www.gnumed.de/downloads/server/v19/GNUmed-server.19.4-1frozen.exe

Regards,
Sebastian