Quantcast
Channel: Support & Bugs - Matomo forums
Viewing all articles
Browse latest Browse all 5706

Issue with upgrade 4.2.1 Error query

$
0
0

Just upgraded to version 4.2.1 and receiving

ERROR Piwik\Tracker\Handler[2021-04-07 18:16:19 UTC] [cc35c] Error query: SQLSTATE[42S22]: Column not found: 1054 Unknown error 1054 In query: SELECT visit_last_action_time, visit_first_action_time, idvisitor, idvisit, user_id, visit_exit_idaction_url, visit_exit_idaction_name, visitor_returning, visitor_seconds_since_first, visitor_seconds_since_order, visitor_count_visits, visit_goal_buyer, location_country, location_region, location_city, location_latitude, location_longitude, referer_name, referer_keyword, referer_type, idsite, profilable, visit_entry_idaction_url, visit_total_actions, visit_total_interactions, visit_total_searches, referer_url, config_browser_name, config_client_type, config_device_brand, config_device_model, config_device_type, visit_total_events, visit_total_time, location_ip, location_browser_lang, last_idlink_va, custom_dimension_1, custom_dimension_2, custom_dimension_3, custom_dimension_4, custom_dimension_5  FROM matomo_log_visit FORCE INDEX (index_idsite_idvisitor)  WHERE idsite = ? AND visit_last_action_time <= ? AND idvisitor = ?

Just did a complete reinstall of version 4.2.1 and I am still receiving this error. Based on the documentation the schema shouldn’t have changed, but not sure why the schema is different. The schema below is what is showing from our table:

mysql> DESCRIBE matomo_qa.matomo_log_visit;
+------------------------+---------------------+------+-----+---------+----------------+
| Field                  | Type                | Null | Key | Default | Extra          |
+------------------------+---------------------+------+-----+---------+----------------+
| idvisit                | bigint(10) unsigned | NO   | PRI | NULL    | auto_increment |
| idsite                 | int(10) unsigned    | NO   | MUL | NULL    |                |
| idvisitor              | binary(8)           | NO   |     | NULL    |                |
| visit_last_action_time | datetime            | NO   |     | NULL    |                |
| config_id              | binary(8)           | NO   |     | NULL    |                |
| location_ip            | varbinary(16)       | NO   |     | NULL    |                |
| last_idlink_va         | bigint(20) unsigned | YES  |     | NULL    |                |
| custom_dimension_1     | varchar(255)        | YES  |     | NULL    |                |
| custom_dimension_2     | varchar(255)        | YES  |     | NULL    |                |
| custom_dimension_3     | varchar(255)        | YES  |     | NULL    |                |
| custom_dimension_4     | varchar(255)        | YES  |     | NULL    |                |
| custom_dimension_5     | varchar(255)        | YES  |     | NULL    |                |
+------------------------+---------------------+------+-----+---------+----------------+

Is there any issue or bug with 4.2.1 that is behind this? Any insight to this issue would be greatly appreciated.

1 post - 1 participant

Read full topic


Viewing all articles
Browse latest Browse all 5706

Trending Articles