

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
error in dbcollector.log : Column 'ASSIGNED_USER_UUID' not found in SHR_4930_EVENTEXT
hello,
i found this error in default installation:
ERROR, com.hp.bto.bsmr.collection.collector.db.DataProcessor.dumpJoinData , [ ABCBatchID:147806, ABCStreamID:PMDB_Platform@platform_poller_db_data_process, ABCStepID:Process_DB_Data, ABCProcessID:147807 ] Error occurred while processing extracted data with query select
SHR_4930_EVENTEXT.ID,
SHR_4930_EVENTEXT.TITLE,
SHR_4930_EVENTEXT.DESCRIPTION,
SHR_4930_EVENTEXT.SOLUTION,
SHR_4930_EVENTEXT.CIRES_STATUS,
SHR_4930_EVENTEXT.NODEHINTS_HINT,
SHR_4930_EVENTEXT.RELATED_CI_HINT,
SHR_4930_EVENTEXT.OM_SERVICE_ID,
SHR_4930_EVENTEXT.SOURCECIHINTS_HINT,
SHR_4930_EVENTEXT.UA_CALL,
SHR_4930_EVENTEXT.AA_CALL,
SHR_4930_EVENTEXT.EVENT_KEY,
SHR_4930_EVENTEXT.CLOSE_KEY_PATTERN,
SHR_4930_EVENTEXT.ORIGINAL_DATA,
SHR_4930_EVENTEXT.OBJECT,
(CASE WHEN SHR_4930_EVENTEXT.CIREF_ID = 'NotFound' or SHR_4930_EVENTEXT.CIREF_ID is null Then 'CI_Unknown' Else SHR_4930_EVENTEXT.CIREF_ID END) as CIREF_ID,
(CASE WHEN SHR_4930_USERS.user_name = 'NotFound' or SHR_4930_USERS.user_name is null Then 'User_Unknown' Else SHR_4930_USERS.user_name END) as user_name,
(CASE WHEN SHR_4930_GROUPS.group_name = 'NotFound' or SHR_4930_GROUPS.group_name is null Then 'GroupName_Unknown' Else SHR_4930_GROUPS.group_name END) as group_name
FROM SHR_4930_EVENTEXT, SHR_4930_USERS, SHR_4930_GROUPS
WHERE SHR_4930_EVENTEXT.ASSIGNED_USER_UUID *= SHR_4930_USERS.USER_ID
AND SHR_4930_EVENTEXT.ASSIGNED_GROUP_UUID *= SHR_4930_GROUPS.GROUP_ID. Cause : SQL Anywhere Error -143: Column 'ASSIGNED_USER_UUID' not found
any idea how to fix it ?
thx,
R


- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
anyone ?
it is "default" - out of the box installation .....
thx


- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
Are you using OMi10? The SQL above is for the OMi10 collector. However, if you deploy the OMi10 collector against a earlier version of OMi, it is going to fail because in the earlier version the column was 'ASSIGNED_USER’ and OMi 10 uses 'ASSIGNED_USER_UUID’.
Since the query cannot find 'ASSIGNED_USER_UUID’ in the database, it is failing.
My guess: You using an OMi10 ETL against OMi9.x?


- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
yes, i'm using OMi10
but problem is in SHR not OMi, because the column doesn't exist in SHR table, not in OMi

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
But how do you think SHR knows which columns to create? SHR does it depending on which CPs you installed, which in turn depend on the data sources. So it looks like you installed an ETL CP designed for BSM/OMi 9.2x instead of one designed for OMi 10.


- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
i think deployment of OMi ETL is correct
R

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
Hi,
I presume you are using SHR 9.40 - if so, please use the latest content pack version which has enhacements and fixes factored in OMi Extended content.
you can download the package from https://hpln.hp.com/contentoffering/hp-shr-operations-events-operations-manager-content
And prior to that, follow step by step instructions from the ReadMe which is available on HP LN @ https://hpln.hp.com/node/25070/attachment
>> FYI - SHR 9.30 does not support OMi10; however, similar fixes in OMi Extended Content for SHR 9.3x(OMi9.x sources) are available as community content on BSM community @ https://hpln.hp.com/node/14127/contentfiles/?dir=24788 - please ensure you follow instructions from the ReadME .pdf.
Thanks & Regards,
Vineetha