Import error after SUA 2.2 patch 6 install

Usage and Config
1

Since updating to patch 6, I started seeing the following message in the import:

===========================================================

2014-11-18 18:46:02 (+0:00:00.634) INFO: Begin applying migration version 2, direction: up
2014-11-18 18:46:02 (+0:00:00.141) ERROR: NativeException: com.ibm.db2.jcc.am.SqlSyntaxErrorException: No authorized routine named “FN_EXTRACTFIELD1M” of type “FUNCTION” having compatible arguments was found… SQLCODE=-440, SQLSTATE=42884, DRIVER=4.14.111: create or replace view dss.computer_groups as
select O.*,
case
when length(Fields) <= 1048576
then dss.fn_ExtractField1M( ‘GroupSpecificationXML’, 0, O.Fields)
when length(Fields) <= 134217728
then dss.fn_ExtractField128M(‘GroupSpecificationXML’, 0, O.Fields)
– field is huge, DB2 needs to allocate a ton of memory
else dbo.fn_ExtractField( ‘GroupSpecificationXML’, 0, O.Fields)
end as GroupSpecificationXML,
case
when length(Fields) <= 1048576
then dss.fn_ExtractField1M( ‘EvaluateMembershipOnClient’, 0, O.Fields)
when length(Fields) <= 134217728
then dss.fn_ExtractField128M(‘EvaluateMembershipOnClient’, 0, O.Fields)
– field is huge, DB2 needs to allocate a ton of memory
else dbo.fn_ExtractField( ‘EvaluateMembershipOnClient’, 0, O.Fields)
end as EvaluateMembershipOnClient
from dss.objects O
where FixletType = ‘ComputerGroup’

2014-11-18 18:46:02 (+0:00:00.011) INFO: Initialize datasource Data Source: Failed

===========================================================

Anyone else see this? Any ideas?

Thanks

2

I have figured out how to solve this, but not sure exactly what happened to cause the problem.

The function above and others are defined in a file called bes_extensions.sql. I opened this file in Data Studio and executed it on my IEM/DB2 server. In the first run, it created quite a few functions that did not previously exist including the failure above. I also noticed that it failed creating/updating some views. It appears that these ones failed because they did not include “DBO.” in the FROM line where the rest of them did. The views that failed were:

dss.object_metadata
dss.reserved_analysis_metadata
dss.analysis_activations

For example:

create or replace view dss.analysis_activations as
select O.*,
case
when length(Fields) <= 1048576
then dss.fn_ExtractField1M( ‘SourceSiteURL’, 0, O.Fields)
when length(Fields) <= 134217728
then dss.fn_ExtractField128M(‘SourceSiteURL’, 0, O.Fields)
else dbo.fn_ExtractField( ‘SourceSiteURL’, 0, O.Fields)
end as SourceSiteURL,
case
when length(Fields) <= 1048576
then dss.fn_ExtractField1M( ‘SourceFixletID’, 0, O.Fields)
when length(Fields) <= 134217728
then dss.fn_ExtractField128M(‘SourceFixletID’, 0, O.Fields)
else dbo.fn_ExtractField( ‘SourceFixletID’, 0, O.Fields)
end as SourceFixletID
from ***DBO.***LOCAL_OBJECT_DEFS O
where ContentType = 6

I will see if I can find time to root cause this, but for now I am working and thought I would share it.