Browse these frequently asked questions (FAQs)

How can I prevent wrapping of data type objects?

The MT installer performs the steps to prevent wrapping data type installers. To verify this configuration:

1. Log into the Administration Console.
2. In the Domain Structure tree, select Services > Data Sources.
3. On the Summary of Data Sources page, click OH-TRC-DS.
4. Select the Connection Pool tab.
5. Scroll down and click Advanced to show the advanced connection pool options.
6. Verify if Wrap Data Types check box is not selected.

Why is the application running out of connections?

• This issue can be resolved by increasing the number of connections as mentioned below.
• Better performance can be achieved by modifying the following attributes:
  • Initial Capacity
  • Maximum Capacity: Maximum number of connections depends on the number of users. For example, if there are10 users the suggested number of connections should always be multiplied by 10 (that is, 10 *10 = 100).
  • Capacity Increment: This value depends upon the multiplication factor being used to calculate maximum capacity (as per above scenario, it is 10).

For more information, see Tuning Data Source Connection Pools available at

https://docs.oracle.com/middleware/12212/wls/JDBCA/jdbc_datasources.htm#JDBCA712

How can I increase the connection pool size?

Perform the following steps to increase the connection pool size:

1. Log into the Oracle WebLogic Server console.
2. Go to Services > Data Sources.
3. Click the data source for which you want to increase the connection pool size.
4. Go to the Connection Pool tab.
5. Specify the number of connections in the attribute Maximum Capacity. Oracle recommends that you set this to at least 100.
6. For details on this configuration, click More Info… right across this attribute.

How can I increase the default row fetch size?

For better performance, increase the default row fetch size to 100 for the Oracle Healthcare Translational Research data source.

1. Log into the Oracle WebLogic Server console.
2. Go to Services > Data Sources under oh_domain.
3. Select the data source OH-TRC-DS.
4. Go to Configuration > Connection pool.
5. Edit the property field oracle.jdbc.defaultRowPrefetch as shown in the following example:

   user=app
   oracle.jdbc.defaultRowPrefetch=100
   

How can I increase the Heap Size?

To optimize performance, Oracle recommends that you update the heap memory of the Oracle WebLogic Server with the following values:

• Exadata

  Initial Heap Size: 8 GB or higher

  Max Heap Size: 816 GB or higher

• Non-Exadata

  Initial Heap Size: 4 GB or higher

  Max Heap Size: 8 GB or higher

There are different ways to increase the heap memory. For example, to change the Java Heap size for a managed server:

1. If you have not already done so, in the Change Center of the Administration Console, click Lock & Edit.
2. In the left pane of the console, expand Environment > Servers.
3. In the Servers table, click the managed server where Oracle Healthcare Translational Research is deployed to configure.
4. On the Configuration tab, click Server Start.
5. In the Arguments field, specify the Java option to increase the initial and maximum heap size.

   For example,

   -Xms8G -Xmx16G, for Exadata
   -Xms4G -Xmx8G, for Non-Exadata

6. Click Save.
7. To activate these changes, in the Change Center of the Administration Console, click Activate Changes. Not all changes take effect immediately—some require a restart.
8. After you finish, you must restart the managed server, so it uses the new heap values.