Update 4.1 -> 4.2

[Leonhard Maylein]

Hello!

We just have done an upgrade from v4.1 to v4.2 on our test server.
On that occasion we noticed that we do not know the password
for the database user dvnapp. Does the installation script
automatically generate a password?

The deployment of dataverse-4.2.war shows a lot of warnings/
database errors:

asadmin deploy /tmp/dataverse-4.2.war

PER01003: Deployment encountered SQL Exceptions:
PER01000: Got SQLException executing statement "CREATE TABLE
VARIABLECATEGORY (ID SERIAL NOT NULL, CATORDER INTEGER, FREQUENCY
FLOAT, LABEL VARCHAR(255), MISSING BOOLEAN, VALUE VARCHAR(255),
DATAVARIABLE_ID BIGINT NOT NULL, PRIMARY KEY (ID))":
org.postgresql.util.PSQLException: ERROR: relation "variablecategory"
already exists
PER01000: Got SQLException executing statement "CREATE INDEX
INDEX_VARIABLECATEGORY_datavariable_id ON VARIABLECATEGORY
(datavariable_id)": org.postgresql.util.PSQLException: ERROR: relation
"index_variablecategory_datavariable_id" already exists

...

PER01000: Got SQLException executing statement "CREATE TABLE
SEQUENCE (SEQ_NAME VARCHAR(50) NOT NULL, SEQ_COUNT DECIMAL(38), PRIMARY
KEY (SEQ_NAME))": org.postgresql.util.PSQLException: ERROR: relation
"sequence" already exists
PER01000: Got SQLException executing statement "INSERT INTO
SEQUENCE(SEQ_NAME, SEQ_COUNT) values ('SEQ_GEN', 0)":
org.postgresql.util.PSQLException: ERROR: duplicate key value violates
unique constraint "sequence_pkey"
Detail: Key (seq_name)=(SEQ_GEN) already exists.
Command deploy completed with warnings.

Am I right in assuming that we can ignore these warnings?

Leonhard Maylein

University library of Heidelberg

[Philip Durbin]

Yes, the default database password is "secret"[1] but you should have been prompted by the `install` script to select a different database password if you wish. "Postgres user password" is one of the many choices[2] you can make at install time.

I'm trying to figure out where this fits in the proposed Installation Guide reorg: https://docs.google.com/document/d/1GLky44JbtCNhGuavLXGEP8WPNdjbyHNxalEGjR78MaA/edit?usp=sharing

If you have any suggestions, please let us know.

I did go ahead and add to that doc the following:

'deploy the new WAR... "CREATE TABLE" SQLException errors are normal because "eclipselink.ddl-generation" is set to "create-tables" in https://github.com/IQSS/dataverse/blob/master/src/main/resources/META-INF/persistence.xml '

That is to say, those exceptions are expected. I believe the "CREATE INDEX" and "INSERT INTO SEQUENCE" exceptions are normal as well. I know they scary, but I think they all have to do with the fact that we let Glassfish create database tables when the war file is deployed. I'm not sure how we would avoid this.

Phil

1. https://github.com/IQSS/dataverse/blob/v4.2/scripts/installer/install#L74

2. https://github.com/IQSS/dataverse/blob/v4.2/scripts/installer/install#L83

--
You received this message because you are subscribed to the Google Groups "Dataverse Users Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email to dataverse-commu...@googlegroups.com.
To post to this group, send email to dataverse...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/dataverse-community/561622F3.5090207%40ub.uni-heidelberg.de.
For more options, visit https://groups.google.com/d/optout.

--

Philip Durbin
Software Developer for http://dataverse.org
http://www.iq.harvard.edu/people/philip-durbin