When running the incremental update script for nominatim, I get a sql error. I recently updated from osmosis 0.35 to 0.42 and updated nominatim to the latest git revision. Is that a red hearing or is there new breakage?

./utils/update.php --import-osmosis-all --no-npi
/var/www/Nominate/osm2pgsql/osm2pgsql -U apache -klas -C 2000 -O gazetteer -d nominatim /var/www/Nominate/data/osmosischange.osc
osm2pgsql SVN version 0.81.0 (64bit id space)

Using projection SRS 4326 (Latlong)
Allocating memory for dense node cache
Allocating dense node cache in one big chunk
Allocating memory for sparse node cache
Sharing dense sparse
Node-cache: cache=2000MB, maxblocks=256001*8192, allocation method=11
Mid: pgsql, scale=10000000 cache=2000
Setting up table: planet_osm_nodes
Setting up table: planet_osm_ways
Setting up table: planet_osm_rels

Reading in file: /var/www/Nominate/data/osmosischange.osc
Processing: Node(136k 2.1k/s) Way(18k 0.36k/s) Relation(87 43.50/s)  parse time: 119s

Node stats: total(136962), max(2227049854) in 65s
Way stats: total(18889), max(212923522) in 52s
Relation stats: total(87), max(2843176) in 2s
node cache: stored: 134790(100.00%), storage efficiency: 87.00% (dense blocks: 133, sparse nodes: 9373), hit rate: 36.94%
Stopping table: planet_osm_nodes
Stopped table: planet_osm_nodes in 0s
Stopping table: planet_osm_rels
Stopping table: planet_osm_ways
Stopped table: planet_osm_ways in 0s
Stopped table: planet_osm_rels in 0s

Osm2pgsql took 119s overall
Completed for 2013-03-26T21:10:03Z in 1.98 minutes
string(127) "INSERT INTO import_osmosis_log values ('2013-03-26T21:10:03Z',32804717,'2013-04-13 01:03:35','2013-04-13 01:05:34','osm2pgsql')"
/var/www/Nominate/nominatim/nominatim -i -d nominatim -t 1
nominatim SVN version 2.1-git-a1670fa

Starting indexing rank (0 to 30) using 1 threads
Starting rank 0
  Done 0 in 0 @ 0.000000 per second - FINISHED

Starting rank 1
  Done 0 in 0 @ 0.000000 per second - FINISHED

Starting rank 2
  Done 0 in 0 @ 0.000000 per second - FINISHED

Starting rank 3
  Done 0 in 0 @ 0.000000 per second - FINISHED

Starting rank 4
  Done 1 in 0 @ 1.000000 per second - ETA (seconds): 0.000000
  Done 1 in 0 @ 1.000000 per second - FINISHED

Starting rank 5
  Done 0 in 0 @ 0.000000 per second - FINISHED

Starting rank 6
  Done 0 in 0 @ 0.000000 per second - FINISHED

Starting rank 7
  Done 0 in 0 @ 0.000000 per second - FINISHED

Starting rank 8
  Done 0 in 0 @ 0.000000 per second - FINISHED

Starting rank 9
  Done 0 in 0 @ 0.000000 per second - FINISHED

Starting rank 10
index_placex: UPDATE failed: ERROR:  column "importance" is of type double precision but expression is of type integer[]
LINE 2:       in_name_vector, in_geometry)
              ^
HINT:  You will need to rewrite or cast the expression.
QUERY:  INSERT INTO search_name_39 values (in_place_id, in_rank_search, in_rank_address, 
      in_name_vector, in_geometry)
CONTEXT:  PL/pgSQL function insertsearchname(integer,bigint,character varying,integer[],integer[],integer,integer,double precision,geometry,geometry) line 89 at SQL statement
PL/pgSQL function placex_update() line 635 at assignment
Error: 1

asked 13 Apr '13, 02:33

montanalow's gravatar image

montanalow
40225
accept rate: 0%

edited 13 Apr '13, 14:14

1

Umm, don't you think that some accompanying text (a question! pointing out the error, so not every need to scan the text) might be useful? Just throwing some error output at other people's head is not that nice. ;-)

(13 Apr '13, 13:27) aseerel4c26 ♦
2

Sorry, I was just a bit confused and not quite sure what exactly to ask. I've edited in a bit of a question.

(13 Apr '13, 14:15) montanalow

Just guessing, but depending on how long ago you did the last update, is it possible that the database schema has changed since then? If it is easy to do (doesn't take to long as you are not using the full planet), you might want to try and re-import the data with the new version of the tools.

(15 Apr '13, 02:02) apmon

I started a fresh full planet import about 12 days ago, with the most recent version of nominatim at the time. This is the first time I've attempted an incremental update to nominatim. Does nominatim include migrations to update the database schema that I should check?

(15 Apr '13, 03:02) montanalow

The database schema changed with this commit. There are no migration scripts but the manual steps to do the migration are described in this pull request.

permanent link

answered 16 Apr '13, 08:21

lonvia's gravatar image

lonvia
5.1k14976
accept rate: 38%

Thanks again, that fixed things up.

(16 Apr '13, 18:09) montanalow
Your answer
toggle preview

Follow this question

By Email:

Once you sign in you will be able to subscribe for any updates here

By RSS:

Answers

Answers and Comments

Markdown Basics

  • *italic* or _italic_
  • **bold** or __bold__
  • link:[text](http://url.com/ "title")
  • image?![alt text](/path/img.jpg "title")
  • numbered list: 1. Foo 2. Bar
  • to add a line break simply add two spaces to where you would like the new line to be.
  • basic HTML tags are also supported

Question tags:

×550
×217
×167
×164

question asked: 13 Apr '13, 02:33

question was seen: 4,056 times

last updated: 16 Apr '13, 18:09

powered by OSQA