[prev in list] [next in list] [prev in thread] [next in thread]
List: turba
Subject: Re: [turba] SQL QUERY FAILED - 'object_category' is not found.
From: "T. Welz" <horde () twelz ! de>
Date: 2015-06-25 20:02:18
Message-ID: 558C5E4A.2030305 () twelz ! de
[Download RAW message or body]
Hello Michael,
you've been right - great - thank you ^^
Kind regards
Tobias
Am 25.06.2015 um 18:16 schrieb Michael J Rubinsky:
>
> Quoting T. Welz <horde@twelz.de>:
>
>> Hello,
>> Sorry - I forgot to write the Version numbers.
>>
>> Versions:
>> Horde Groupware 5.2.2
>> Kalender (kronolith) 4.2.2
>> Adressbuch (turba) 4.2.2
>> Webmail (imp) 6.2.2
>> Server is Debian Stable.
>>
>> Regards Tobias
>>
>> Am 25.06.2015 um 18:06 schrieb T. Welz:
>>> Hello,
>>>
>>> I currently have an issue with syncing my contacts - I find this
>>> issue in my server log, that 'object_category' is not found.
>>>
>>> From Syslog:
>>> HORDE: [turba] SQL QUERY FAILED: SQLSTATE[42S22]: Column not found:
>>> 1054 Unknown column 'object_category' in 'field list' #012#011SELECT
>>> object_id, owner_id, object_type, object_members,
>>> object_uid,#012#011 object_firstname, object_lastname,
>>> object_middlenames,#012#011 object_nameprefix, object_namesuffix,
>>> object_alias,#012#011 object_yomifirstname, object_yomilastname,
>>> object_bday,#012#011 object_anniversary, object_spouse,
>>> object_photo, object_phototype,#012#011 object_homestreet,
>>> object_homepob, object_homecity,#012#011 object_homeprovince,
>>> object_homepostalcode, object_homecountry,#012#011
>>> object_workstreet, object_workpob, object_workcity,#012#011
>>> object_workprovince, object_workpostalcode,
>>> object_workcountry,#012#011 object_otherstreet, object_otherpob,
>>> object_othercity,#012#011 object_otherprovince,
>>> object_otherpostalcode, object_othercountry,#012#011
>>> object_department, object_manager, object_assistant,
>>> object_tz,#012#011 object_email, object_homephone,
>>> object_homephone2, object_homefax,#012#011 object_workphone,
>>> object_workphone2, object_cellphone,#012#011 object_carphone,
>>> object_radiophone, object_companyphone,#012#011
>>> object_assistantphone, object_fax, object_pager,
>>> object_title,#012#011 object_role, object_company, object_logo,
>>> object_logotype,#012#011 object_category, object_notes, object_url,
>>> object_freebusyurl,#012#011 object_pgppublickey,
>>> object_smimepublickey, object_imaddress,#012#011 object_imaddress2,
>>> object_imaddress3 FROM turba_objects WHERE#012#011 (owner_id =
>>> 'tw') [pid 8847 on line 204 of
>>> "/usr/share/php/Horde/Db/Adapter/Pdo/Base.php"]
>>>
>>>
>>> I tried already horde-db-migrate which didn't help. I post the
>>> results - as It is maybe important to know the database versions:
>>>
>>> root@lando:~# horde-db-migrate
>>>
>>> [ INFO ] Migrating DB up.
>>> [ INFO ] Current imp schema version: 3
>>> [ INFO ] Ending imp schema version: 3
>>> [ INFO ] Current kronolith schema version: 22
>>> [ INFO ] Ending kronolith schema version: 22
>>> [ INFO ] Current turba schema version: 11
>>> [ INFO ] Ending turba schema version: 11
>>> [ INFO ] Current nag schema version: 13
>>> [ INFO ] Ending nag schema version: 13
>>> [ INFO ] Current mnemo schema version: 7
>>> [ INFO ] Ending mnemo schema version: 7
>>> [ INFO ] Current trean schema version: 5
>>> [ INFO ] Ending trean schema version: 5
>>> [ INFO ] Current wicked schema version: 6
>>> [ INFO ] Ending wicked schema version: 6
>>> [ INFO ] Current gollem schema version: 3
>>> [ INFO ] Ending gollem schema version: 3
>>> [ INFO ] Current content schema version: 2
>>> [ INFO ] Ending content schema version: 2
>>> [ INFO ] Current Horde_ActiveSync schema version: 21
>>> [ INFO ] Ending Horde_ActiveSync schema version: 21
>>> [ INFO ] Current Horde_Alarm schema version: 2
>>> [ INFO ] Ending Horde_Alarm schema version: 2
>>> [ INFO ] Current Horde_Auth schema version: 1
>>> [ INFO ] Ending Horde_Auth schema version: 1
>>> [ INFO ] Current Horde_Cache schema version: 2
>>> [ INFO ] Ending Horde_Cache schema version: 2
>>> [ INFO ] Current Horde_Core schema version: 1
>>> [ INFO ] Ending Horde_Core schema version: 1
>>> [ INFO ] Current Horde_Dav schema version: 2
>>> [ INFO ] Ending Horde_Dav schema version: 2
>>> [ INFO ] Current Horde_Group schema version: 3
>>> [ INFO ] Ending Horde_Group schema version: 3
>>> [ INFO ] Current Horde_History schema version: 6
>>> [ INFO ] Ending Horde_History schema version: 6
>>> [ INFO ] Current Horde_Imap_Client schema version: 2
>>> [ INFO ] Ending Horde_Imap_Client schema version: 2
>>> [ INFO ] Current Horde_Lock schema version: 3
>>> [ INFO ] Ending Horde_Lock schema version: 3
>>> [ INFO ] Current Horde_Perms schema version: 2
>>> [ INFO ] Ending Horde_Perms schema version: 2
>>> [ INFO ] Current Horde_Prefs schema version: 3
>>> [ INFO ] Ending Horde_Prefs schema version: 3
>>> [ INFO ] Current Horde_Queue schema version: 1
>>> [ INFO ] Ending Horde_Queue schema version: 1
>>> [ INFO ] Current Horde_SessionHandler schema version: 2
>>> [ INFO ] Ending Horde_SessionHandler schema version: 2
>>> [ INFO ] Current Horde_SyncMl schema version: 1
>>> [ INFO ] Ending Horde_SyncMl schema version: 1
>>> [ INFO ] Current Horde_Token schema version: 1
>>> [ INFO ] Ending Horde_Token schema version: 1
>>> [ INFO ] Current Horde_Vfs schema version: 4
>>> [ INFO ] Ending Horde_Vfs schema version: 4
>>> root@lando:~#
>>>
>>>
>>> I assume that over time, at some time data migration failed maybe.
>>> Shall I somehow add the missing field, or is some migration needed?
>
> The opposite. You probably upgraded but continued to use the same
> configuration for your address book. The category field was removed
> some time ago (and replaced with tags). Check your backends.local.php
> file.
>
>
>
--
turba mailing list
Frequently Asked Questions: http://wiki.horde.org/FAQ
To unsubscribe, mail: turba-unsubscribe@lists.horde.org
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic