Open Microscopy Environment

I followed all the instructions in

http://www.openmicroscopy.org/site/supp ... nd-restore

Now I have an issue. I lost the config file. Is it possible to restore OMERO with a dummy config file?

You can definitely re-configure your server to point it at the right omero.data.dir and the right DB instance. Do you still have the original omero_dist directory? If so, you can copy over the etc/grid/config.xml file.

Cheers,
~Josh

no. we don't. all we have is the binary repo and sql dump.

Then you'll need to re-issue the commands you ran to configure your original server, or similar ones, possibly including:

Code: Select all

bin/omero config set omero.db.name
bin/omero config set omero.db.user
bin/omero config set omero.db.host
bin/omero config set omero.data.dir
# etc...


~J.

josh
i tried restoring the SQL database

Code: Select all

bash-3.2$ pg_restore -Fc -d ascb omero_ASCB.dump.2Feb12
pg_restore: [archiver] unsupported version (1.12) in file header

then i tried

Code: Select all

psql -d ascb < omero_ASCB.dump.2Feb12

which outputs

Code: Select all

ERROR:  invalid byte sequence for encoding "UTF8": 0xae
HINT:  This error can also happen if the byte sequence does not match the
encoding expected by the server, which is controlled by "client_encoding".

because of this, we changed theencoding of the database but we still got the first error. thus i assumed that i did something wrong. and went back to an older copy omero_ASCB.dump.26Aug11 which was built by a member of omero. we changed the encoding and when we dump it back it wouldn't fully load. specifically, the image table is empty.

have you encountered a similar problem before? do you have any feedback that might help us? we need to restore ascb to extract some ome-tiffs.

What are the versions of PostgreSQL involved (before and after the dump)? ~J

before i don't know. whichever one was used in searcher-usa-dev. in our node

Code: Select all

bash-3.2$ psql --version
psql (PostgreSQL) 8.3.4
contains support for command-line editing


I'm fairly certain that searcher-usa-dev was running PostgreSQL 9.0.x. You'll need at least that to restore the database.