Load Data Warehouse Job Failing at Jaspersoft Domain Update

[James Teh]

I've set up an instance of Clarity 14.2 with Jaspersoft.

 

The installation proceeded with no issue:

- Installed PMO Pack on Jasper - can see the ppmjasperadmin users created, as well as all the domains/reports

- Generated/shared the key files

- Create/Update Jaspersoft users job runs successfully

- Can access Advanced Reporting using admin account from Clarity

 

However when I try to run the Load Data Warehouse job, it is populating the warehouse, but at the end when trying to do Jaspersoft Domain updates, it is failing with the error:

Error occured while processing domain attributes. Could not update attribute align_corporate_key of object inv to domain CSK_APP_Management

I've checked the bg-ca.log too, and no other error message appears in there apart from the above.

align_corporate_key I believe is a stock out-of-the-box attribute

Also tried restarting Clarity and Jaspersoft services, to no avail.

 

Would appreciate any guidance on the above issue.

[Jerin Sebastian]

Hi, Do you see something in the dwh-log? Regards, Jerin

[James Teh]

Hi Jerin

 

Nothing in the bg-dwh.log file indicating this problem with Jaspersoft

It actually says on the final line of the log - dwh.event dwh_etl_master - Job execution finished

So that's why I suspect it's more of a Jaspersoft update issue than a DWH update issue - the DWH part of the Job actually seems to complete without issue.

[Suman Pramanik]

Hi James,

 

Can you run the load data warehouse rights job, if you don't find in reports and jobs then please activate the same from administration side.

 

Do let me know if that helps.

 

Regards

Suman Pramanik

[James Teh]

Hi Suman

Yes I can run the Load Data Warehouse Access Rights job, and yes it completes successfully.

However even after the successful run of the above, the Load Data Warehouse job still fails with the same error.

[Suman Pramanik]

From the error it looks like align corporate key attribute under investment object has some issue. Can you check if the attribute is checked to included for dwh. You can find the same by going to the attribute property.

 

Regards

Suman

[James Teh]

Hi Suman

Thanks for your replies.

From my investigation, I don't think the attribute is the issue.

 

Firstly yes I did check the attribute is enabled for DWH.

When I disable it for DWH, and run the Load Data Warehouse job, the same error appears but for the next attribute - so that''s why I think the actual attrirbute is ok.

[navzjoshi00]

Is the object itself, checked to included for dwh ?

 

NJ

[James Teh]

Hi NJ

 

Yes, the Investment object is included for DWH

[Suman Pramanik]

Ok, the last check did you applied the PMO addin from the administration. Did the datamart and time slice completed successfully before running the load dataware house job.

Regards

Suman Pramanik

[James Teh]

Yes, the PMO add-in has been applied from the Administration side

 

Datamart Extraction run and the time-slices are all up to date.

 

On the Jaspersoft side, using the Clarity admin account and going through Advanced Reporting I can actually manually add the attribute to the the CSK_App_management domain (same thing the Data Warehouse Load job is appearing to do).

 

So I'm thinking maybe the Jaspersoft user the Data Warehouse Load job is using (is it ppmjasperadmin?) has something wrong with it and cannot update the domain due to permissions?

[Suman Pramanik]

It does use ppmjasperadmin and that the super user and I haven't seen this is giving issue. what user was used to import the csk content in jaspersoft server?

 

Regards

Suman Pramanik

[James Teh]

The superuser account was used to import the csk content.

 

Is there a way I can log in to Jasper as ppmjasperadmin?

I guess what I've trying to find here is a deeper level of logging - exactly why on the Jaspersoft side, the attribute cannot be updated to the Domain by ppmjasperadmin - all the logs I see are from the Clarity side - what about the Jasper side?

[Suman Pramanik]

No you cannot login user ppmjasperadmin, only super user can be used to login to console, you can enable the details ETLlogging from CSA like any other trace. I hope you provided all the database privileges mentioned in the installed guide.

 

Regards

Suman Pramanik

[Benitha Balachandran]

We have got the same issue in our development environment.

ERROR 2021-10-20 07:01:23,840 [Dispatch Load Data Warehouse : bg@XXXX (tenant=clarity)] niku.njs (clarity:XXXXXX:222266914__E2B69E5F-6422-48DB-A732-3C6AD0C41B0E:Load Data Warehouse) Error executing job: 7270993
com.ca.jasper.restAdapter.JasperException: Could not update attribute align_corporate_key of object inv to domain CSK_IDE_Management

How can this issue be resolved?

Regards,
Benitha

[Nika Hadzhikidi]

Hi Benitha

To fix this, please run the Restore Domains job and then run Load Data Warehouse - Full Load. 
Hope this helps -Nika

------------------------------
Nika Hadzhikidi
Sr Principal Support Engineer
Broadcom
------------------------------

[Benitha Balachandran]

Hi Nika,

That worked.

Thank You.

Regards,
Benitha

[Suman Pramanik]

Hi James,

 

Did you made any modification to out of box domains?

 

Regards

Suman Pramanik

[James Teh]

Hi Suman

 

No modifications have been made at all to any Domains, everything out-of-the-box right now.

[Nika Hadzhikidi]

Hi James,

 

Is this happening on a clustered environment? If yes, please ensure that both servers are communicating successfully by setting up the bind addresses in the properties.xml file to match on both servers. Bind addresses should include all the NIC in the cluster, added with commas and no spaces.

If this is not set up properly on a clustered environment then an attribute may be included for DWH on one server, and excluded on another and DWH job will fail with this error message.

 

Please let me know how it goes.

 

Kind Regards

Nika Hadzhikidi

CA Technologies

Principal Support Engineer

[Legacy User]

Did you ever find a solution to this?  I'm running into the exact same issue.  I am NOT running in a clustered environment for this issue.  (Still in QC.)

[James Teh]

Hi all

 

Apologies for the much delayed reply but the root cause of this issue was because the MS SQL database had the wrong date/time format and so the syncing between Jasper, the DWH and PPM was out of alignment.

 

Once the date format was corrected, the issue was resolved.

 

As an aside, although the above may not resolve the issue you are facing, I would investigate the DWH_CFG_LOG table (in the DWH table) or the DWH_ tables (in the PPM database) for further clue into why this problem is occuring.

[Anon Anon]

I've got the same issue, but i don't understand what you mean by correcting date format, could you explain me?

[James Teh]

Hi DanAdjoa

 

Date format was incorrect in MS SQL Server - it was set to DD/MM/YYYY (UK Date format) when it should have been MM/DD/YYYY (USA Date format)

[Anon Anon]

Unfortunatly i don't know how to change this date format in sql server.

All databases (clarity, datawarehouse and jaspersoft) are on the same server and we access these with the same login.

How Is it possible to specify this date format by database ?

[Suman Pramanik]

Hi Dan,

 

See if this helps

 

 

 

How to change Date Format after installing SQL server - Microsoft SQL Server Tips & Tricks - Site Home - MSDN Blog

 

Regards
Suman Pramanik

[kumu]

Facing exactly same issue with idea object attributes, I am on oracle and all on same server.  So it doesn't seems as date format issue.

 

Any ideas ? Thanks.

[kumu]

One observation attributes its reporting error are the custom once. All system attributes getting updated correctly. Will need to check whats wrong with custom attributes.

[Suman Pramanik]

We need to look at logs and then analyse further. It may be worth opening a support case

[kumu]

Job throws error -

Error occurred while processing domain attributes. Could not update attribute corporate_key of object idea to domain CSK_IDE_Management

[kumu]

Resolved by disabling and re-enabling custom attributes on each object.

 

Wired issue.. some config was holding DW job to pick custom attributes.

[Suman Pramanik]

Hi Kumu,

 

If you are making any change at the attribute definition then you must select the full load and run. If you do that I believe you will not run into this issue.

 

Regards

Suman Pramanik

[Legacy User]

For what it's worth, it doesn't appear to be a date issue for us either.  I actually have opened a support case, and provided CA a copy of our production database.  They're working on it.  I'll come back and post whatever OUR issue is once we figure it out.  Seems like this problem might be caused by a couple different issues though, so I don't know if it would be the same for you.

[UweKerntopf]

Hello, have you got a solution for your that? Can you please provide me with the CA support case number? Thanks!

[Legacy User]

Yes, we have a solution to this particular issue!  (Got it working in QC.  Still not close to working in Prod, we've got some completely different error going on there.  This install is awful.)  Anyway, for us the issue was the MS SQL Transaction Log.  I followed the steps in this link and it resolved:

http://www.ca.com/us/support/ca-support-online/product-content/knowledgebase-articles/tec511215.aspx

The MSSQL transaction log for the database is full, or has grown excessively.

 

Just FYI, the steps in that link are specific to SQL Server 2005 (which isn't mentioned in the aritcle).  "WITH TRUNCATE_ONLY" isn't supported after SQL2005.  Here's what I found to replace that bit:  

USE dbname;

GO

-- Truncate the log by changing the database recovery model to SIMPLE.

ALTER DATABASE dbname

SET RECOVERY SIMPLE;

GO

-- Shrink the truncated log file to 1 MB.

DBCC SHRINKFILE (2, 1);  -- here 2 is the file ID for trasaction log file,you can also mention the log file name (dbname_log)

GO

-- Reset the database recovery model.

ALTER DATABASE dbname

SET RECOVERY FULL;

GO