Support Article
Performance degrades when running BIX extract for Work history
SA-53519
Summary
Performance degrades when running a Business Intelligence Exchange (BIX) extract for a Work history.
Error Messages
Not Applicable
Steps to Reproduce
Unknown
Root Cause
A defect or configuration issue in the operating environment. For History extract, performance degrades when running the below SQL.
[your_host] [ ] [ ] ( internal.access.ExtractImpl) DEBUG - sql statement is: SELECT count(pzInsKey) FROM your_schema.your_pc_history_work WHERE pzInsKey like ? AND pxTimeCreated >= ? AND pxTimeCreated < ? AND ((pxHistoryForReference is not null) AND ((pyWorkClass like ?) OR (pyWorkClass like ?)))
2018-02-23 13:52:33,538 [your_host] [ ] [ ] ( internal.access.ExtractImpl) INFO - {i=<pxInsName>}
Resolution
Here's the explanation for the reported behavior:
A Database Administrator must review the SQL using the PLSQL tool to analyze the query.
View the History table partitioning if the performance does not improve despite optimizing the query.
Published April 27, 2018 - Updated October 8, 2020
Have a question? Get answers now.
Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.