My Oracle Support Banner

Current Known Argus Performance Related Bugs and Enhancements - With Fixed Versions (Doc ID 2100142.1)

Last updated on MAY 21, 2021

Applies to:

Oracle Argus Interchange - Version 5.0.2 to 8.1 [Release 5.0.0 to 8.1]
Oracle Argus Safety Japan - Version 5.0.0 to 8.1 [Release 5.0.0 to 8.1]
Oracle Argus Unblinding - Version 5.0.0 to 8.1 [Release 5.0.0 to 8.1]
Oracle Argus Affiliate - Version 5.0.2 to 8.1 [Release 5.0.0 to 8.1]
Oracle Argus Safety - Version 5.0.2 to 8.1 [Release 5.0.0 to 8.1]
Information in this document applies to any platform.

Details

Summary of Bugs and Enhancements Related to Performance - Along with Fix Version (Where Applicable)
Bug Number Description Found Version Fixed Version Summary
Bug 21891122  Performance 7.0.6: the E2B difference report performance slower than 7.0.3  7.0.6  8.1.1 Comparing the performance of the E2B Difference Report between Argus Safety Version 7.0.3 and
Argus Safety Version 7.0.6, it was found significantly slower in Argus 7.0.6
Bug 20179775  Performance Issue When Using Datasheet  6.0.5  Open Users are experiencing serious performance issues when using creation or copy of datasheets, adding or removing PT from datasheets.
Bug 18030285  Slow Performance On Type Ahead Fields From Worklist Search Screen  7.0.3  Open In Worklists => New case search, when selecting a Filter such as "Product Name" and entering a value, the type ahead feature has significant slow performance.
Bug 17422348  Enhancement: MedDRA Wild Card Search Impacts System Performance  7.0.2  Open When do a search '%'(Wild card character) in the MedDRA browser for LLT. All the results are displayed on the MedDRA Browser(count:62,000+) in
this scenario it hampers performance.
Recommended to implement something similar to what is done for WHODrug browser, i.e. display only 1000 LLT terms and then a message such as
'Only the first 1000 matching results are displayed.'
Bug 11068703  FWDPRT: Binary Data Is Moved To DLP Negatively Impacting Performance  5.0.3.3  5.0.3.4 Currently, DLP ETL copies BLOB data into DLP database which may not be used in periodic or expedited reports executed on DLP (such as Case Attachments
and Letters data). This causes negative impact on DLP ETL performance
Bug 9460084 DLP Performance Issue Due To Cartesian Product Caused By A Missing Table Join  5.0.3  5.0.5 PSUR with attached UD CIOMS II line listings executes the following SQL creating a cartisian product due to lack of join ((lm_product lp, lm_product_family lpf)
Bug 11730068 FWDPRT: Binary Data Is Unnecesarily Moved to DLP Impacting Performance  --  5.0.5 DLP ETL was moving letters and attachments into DLP database
Bug 9543548  EOSU Performance Loading Treatment Randomization File  5.1  5.1.1 A Study having more than 800 cases and 1400 records in CSV file takes 2.5 hours to load randomization data from EOSU Tool.
Bug 12648832

FWDPRT: PERIODIC REPORTS EXECUTION PERFORMANCE ON DLP

(See Base Bug 12648028 for details as Bug 12648832 is not published/visible onMy Oracle Support Portal)

 4.2.1.1  5.1.3 Periodic reports and aggregate reports take a long time to execute due to clean up of the temp data of previous executions.
Bug 13036338 Performance Issue in DSUR SQL For Cummulative Summary 5.1.3  5.1.3.1 When running a periodic report with cumulative summary, the report will not return on large databases.
Bug 11724574 FWDPRT: Large Tables Have Excessive Joins In DLP Impactiing Performance  6.0  6.0.2

Some DLP tables like DLP_CASE_EVENT_ASSESS which have huge number of rows and are also referred heavily are used in DLP view definitions.

This leads to negative impact on performance of periodic reports executed on DLP database.

Bug 12365186 FWDPRT 505: Performance Issue With CIOMS II Line Listing Part Of Periodic Report  --  6.0.3 PSUR with attached UD CIOMS II line listings executes the following SQL creating a cartesian product due to lack of join ((lm_product lp, lm_product_family lpf)
Bug 11724563 FWDPRT: Binary Data Unneccarily Moved to DLP Negatively Impacting Performance  --  7.0.1 Currently, DLP ETL copies BLOB data into DLP database which may not be used in periodic or expedited reports executed on DLP (such as Case  Attachments and Letters data). This causes negative impact on DLP ETL performance and causes the DLP database to grow faster.
Bug 13644009 Performance Issue When Selecting Studies In The Book-In Screen  --  7.0.1 The system is taking very long time (> 10 minutes) to return the studies or does not return the results and turns into not responding state when searching for a study that contains large number of study centers in the clinical trial selection dialog during the initial case entry
Bug 15990735 FWDPRT:Performance Issue With Report Tab - Reports - Periodic - ICHPSUR 6.0.5 7.0.2

Periodic report list sql is using CMN_REG_REPORTS insted of CMN_REG_REPORTS_PERIODIC.

This caused performance issues due to large amount of data fetched.

Bug 19326690 Bug 19326690 - BCKPRT: Argus Slow performance issue 7.0.3.001 7.0.2.5

When Argusvr2 executes a sql with a join, the ROWID select column added by the Oraclm32 data layer causes the sql to throw an error.

Subsequently Oraclm32 removes the ROWID and re-executes the originial sql. There is one sql in ProfileInfo.cpp that gets executed for every request to Argusvr2.
Since the number of executions of this sql is huge when the concurrent user load is big, this caused unnecessary parsing of the sql in the database every time.

Because of this, the Library Cache Lock failures started showing up intermittently.

Bug 16436860 FWDPRT:Performance Is Slow During MEDDRA Recoding On Large Database 6.0.5.4 7.0.3 MedDRA recoding is slow on large databases due to missing indexes and full table scan on PDP_QUEUE_DUP_CASE_DATA and MedDRA_RECODE_SUCCESS
Bug 17966643 Argus Slow performance issue 7.0.3.001 7.0.3.002 Intermittent slow performance was being observed across the Argus Safety application due to a large number of concurrent users.
Bug 10135340 Case Save - Performance Slowness  4.2.1.5A 7.0.3.1

Case Save performed after modifying / adding / changing / receiving follow-up data is very time consuming.

The performance of the Argus case form when working with "Bulky" cases (i.e. having very large number of event assessment rows - cases greater than 5,000 rows or only after 10,000 rows, or 15,000 rows) is very time consuming.

Saving the Case takes severalminutes or may eventually time out with an XML error. Impact is worse when the Save is done from the Event Tab .

Bug 19818150 FWDPRT:Argus Slow Performance Issue 7.0.3.001 7.0.3.201

Argus application exhibited slow performance throughout various functions as listed below:
1. On Log in by simultaneous users, displaying random blank screen when launching log in page
2. On Case Book in
3. E2B Report Generation
4. Application Log out
5. Batch report scheduling and generation
6. LAM report creation

See Base Bug 17995683 for more details

Bug 19784291 FWDPRT: Argus Slow Performance Issue 7.0.3.001 7.0.3.3

When Argusvr2 executes a sql with a join, the ROWID select column added by the Oraclm32 data layer causes the sql to throw an error.

Subsequently Oraclm32 removes the ROWID and re-executes the originial sql. There is one sql in ProfileInfo.cpp that gets executed for every request to Argusvr2.
Since the number of executions of this sql is huge when the concurrent user load is big, this caused unnecessary parsing of the sql in the database every time.

Because of this, the Library Cache Lock failures started showing up intermittently.

See Base Bug 17995683 for more details

Bug 18814314 Performance Issue With Running Periodic Reports  7.0.3 7.0.4.1 The Report SQL's were taking huge execution time 14+ hours before index creation.
Bug 11715494 FWDPRT: Binary Data Unnecesarily Moved to DLP Negatively Impacting Performance. 5.1 8.0

DLP ETL copies BLOB data into DLP database which may not be used in periodic or expedited reports executed on DLP (such as Case Attachments and Letter data).

This causes negative impact on DLP ETL performance and causes the DLP database to grow faster.

Bug 19889029 Performance Issue With ESM Related Query Causing Lock Contention 7.0.3 8.0

SQL Queries used in ESM were executing very slowly in big databases

Bug 20194723 Index Creation for J-Periodic Performance Improvement 7.0.3 8.0

For performance improvement in J-Periodic a few New Indexes are created

Bug 17999420 FWDPRT: Argus Slow Performance Issue 7.0.3.001 8.0 When Argusvr2 executes a sql with a join, the ROWID select column added by the Oraclm32 data layer causes the sql to throw an error.

Subsequently Oraclm32 removes the ROWID and re-executes the originial sql. There is one sql in ProfileInfo.cpp that gets executed for every request to Argusvr2.
Since the number of executions of this sql is huge when the concurrent user load is big, this caused unnecessary parsing of the sql in the database every time.

Because of this, the Library Cache Lock failures started showing up intermittently.

See Base Bug 17995683 for more details

Bug 18896926 FWDPRT: Performance issue with running Periodic reports  8.0 8.0 The sqls for periodic reports were taking huge execution time 14+ hours before indexcreation.
After fix, the sqls were re-tested after putting the index in place and the execution time dropped from 14+ hours to under 2 minutes
18860323 FWDPRT: Random blank screens appear when using Argus Safety 8.0 8.0 Random blank screens were appearing at the following instances, when using the Argus Safety application:

Routing a case.

Blank screen when trying to login.

Upgrading a case from Non-serious to Serious.

Performing a duplicate search.

After Fix

The issue of random blank screens has now been resolved and no such instances appear when using the Argus Safety application.

18086095 Large number of rows in LM_PROTOCOLS causes 100% CPU usage 8.0 8.0 The application takes several minutes to open the Clinical Trial Selection dialog if there are thousands of Study Protocols.

After Fix

The Protocol dropdown list in the Clinical Trial Selection dialog has been changed to a type-ahead field to load limited data, when requested.

18158212 FWDPRT:SELECT FROM CMN_AUDIT_LOG CAUSING PROBLEMS ON LARGE DATABASES 8.0 8.0 Performance of E2B generation was slow for Initial reports due to improper use of sequence number while writing entries to Audit Log database.

After the fix, performance of E2B generation has improved for Initial reports, as SQL has been tuned to write entries efficiently to Audit Log database.

17999420 FWDPRT:Argus Slow performance issue 8.0 8.0 The Argus Safety application exhibited slow performance throughout various functions, as listed below:

1. On Log in by simultaneous users

2. On Case Book in

3. E2B Report Generation

4. Application Log out

5. Batch report scheduling and generation

6. LAM report creation

After fix, Argus application shows an improved performance throughout the various functions listed above.

14825382 Bug 14825382 - REPORTER CODELIST SCREEN HANGS WITH RECORDS > 3.5LAKHS 6.0.7.1 8.1

Application stopped responding and did not display the page even after a long waiting time for reporter codelist having more than 5 lakh records.

After fix, Application displays the page if reporter codelist has more than 5 lakh records.

17516227 Bulk Transmit E2B screen is not showing transmission status for EDI out /MDN 7.0.1.5 8.1

The Bulk ICSR Transmit screen was not displaying the transmission status for EDI out/MDN due to performance issues.

After fix, the Bulk ICSR Transmit screen displays the transmission status for EDI out/MDN.

22284635 PERFORMANCE IMPROVEMENT IN WAN HYBRID ARCHITECTURE 8.0 8.1 Over WAN hybrid architecture, the Argus MART ETLs were very slow and running for long periods of time. The ETLs did not complete in many instances.

After fix, the Safety application has been enhanced to improve the Argus MART ETL performance such that ETLs are processed and completed in an acceptable duration.

21906400 FWDPRT: Poor performance in Argus Safety Console when opening Report Rules in AS 7.0.2 8.1 On the Expedited Reporting Rules screen, navigating from the first screen of countries to the next using [>] was taking 15-20 seconds.

After the fix, the performance of loading the Expedited Reporting Rules tree under Console -> Business Configuration, and the performance of navigating the tree has been improved. For example, navigating from the first screen of the data tree organized on Country/License Type/Reporting Rule to the next screen of data tree using [>] has been significantly improved.

General 4.1.27 Performance Improvements 8.0 8.1 As part of this release, there has been a number of areas where performance improvements have been made. These areas include the following:

Worklist Contacts and Letters

Worklist Action Items (View Individual)

ICSR Pending

E2B Generation

Check Japanese Character functionality

General overall improvement

Improvement of general database procedure execution performance



Actions

Additional Notes:

Oracle HSGBU performance team has executed independent performance tests simulating customer environments and performance methodology, and based on this, Technical Brief documents have been published for 6.x, 7.x and 8.x Argus Safety Versions.

Link to Technical Brief Documents

Argus Safety 6.x, 7.x, and 8.x Performance Benchmark and System Recommendation Documentation (Doc ID 2109123.1)

Contacts

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Details
Actions
Contacts
References

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.