Oracle Database Facilities Management …

IBM Jay.Manaloto

Search Submit IBM

Profiles Communities Apps Share

Wikis This Wiki Search

IBM TRIRIGA Following Actions Wiki Actions

TRIRIGA Wiki Home You are in: IBM TRIRIGA > IBM TRIRIGA Application Platform > Performance > Best Practices for System Performance > Database specific considerations > Oracle database Facilities Management …

Facilities Maintenance Oracle database Like | Updated March 1, 2019 by Jay.Manaloto | Tags: database_performance, oracle, oracle_database, oracle_tuning, performance, system_performance Add or remove tags Environmental & Ener… Edit Page Actions Real Estate Management

Capital Project Manag…

CAD Integrator-Publis…

IBM TRIRIGA Connect…

IBM TRIRIGA Anywhere Best Practices for System Performance. IBM TRIRIGA Applicati…

Support Matrix 5 Database Server Tuning and Maintenance (continued)

Hints and Tips < Back to Table of Contents Installing 5 Database Server Tuning and Maintenance (continued) Admin Console 5.4 Oracle Database (was 5.7) 5.4.1 Oracle Database Server Tuning (was 5.1) Builder Tools a. Oracle Licensing Considerations (was 5.1.1) b. Oracle RAC Considerations (was 5.1.2) Connector for Busin… 5.4.2 Oracle Application Platform Indexes (was 5.4.2.b) 5.4.3 Reserve Indexes for Oracle (was 5.4.2.e) Connector for Esri GIS 5.4.4 Lease Indexes for Oracle Document Manager Next >

Extended Formula

Gantt Scheduler 5.4 Oracle Database

Globalization Notes: Group Object Because all functionality is based on database performance, the database should be a key focus for performance Label Manager tuning. TRIRIGA recommends that the database server be co-located on the same subnet as the application and process servers. Licensing For this reason, cloud database offerings such as Oracle’s Database Cloud Exadata Service are not recommended for adequate performance. However, hosting the entire TRIRIGA infrastructure in the cloud where the TRIRIGA Object Labels and R… infrastructure is hosted on the same subnet is a viable configuration for good performance. In addition, customers have Offlining reported good performance using Oracle’s Exadata Database Machine in on-premise deployments. Always check the IBM TRIRIGA Support and Compatibility Matrix for the latest database versions and fix packs OSLC supported. Performance issues where the database server is not co-located with the application and process servers are not supported. Performance

Best Practices for … 5.4.1 Oracle Database Server Tuning Introduction On an Oracle database, specify the following initialization parameters: Network consider… Set the CURSOR_SHARING parameter to EXACT (Oracle default) if it's not already configured that way. This ensures System architect… ideal performance because TRIRIGA uses bind variables extensively.

Operating system… If multibyte support is required, be sure to set the NLS_LENGTH_SEMANTICS parameter to CHAR and the database character set to AL32UTF8 or AL16UTF16. Database server t… Use the Program Global Area (PGA) WORKAREA_SIZE_POLICY=AUTO setting to automatically size work areas.

Database specific… Ensure the Optimizers (OPTIMIZER_FEATURES_ENABLE) are set to your current Oracle version and not to an older one. DB2 database PARALLEL_DEGREE_POLICY specifies whether automatic degree of parallelism, statement queuing, and in-memory parallel execution will be enabled. The default of MANUAL can be changed to ADAPTIVE. Oracle database Increase the process number to handle more concurrent users by setting the PROCESSES= initialization parameter to the Microsoft SQL … maximum number of users who can access Oracle concurrently. A general guideline is to add up all maximum JDBC connection pool values from each JVM and add another 100 for Oracle. For example, adding an application server (200), Application Serve… plus process server (200), plus Oracle (100), would require a PROCESSES value of at least 500.

IBM TRIRIGA tuni… In Oracle 11g and 12c, automatic memory management allows for automatically readjusting the sizes of the main pools (db_cache_size, shared_pool_size, large_pool_size, and java_pool_size) based on existing workloads. Initialization parameters TRIRIGA Anywhe… that are used to enable this feature are: SGA_TARGET and SGA_MAX_SIZE. Troubleshooting … The memory_target parameter is dynamic (changeable with "alter system" commands), where RAM can be de-allocated from an instance’s SGA/PGA and re-allocated to another instance. Initialization parameters that are used to enable this feature Information gathe… are: MEMORY_TARGET and MEMORY_MAX_TARGET. Consult with your database administrator to size these parameters to take advantage of this feature. Performance Probl… Use automatic memory management. For more details, see Enabling Automatic Memory Management. Performance Analy… For assistance in performing Oracle database tuning, see the Oracle Database Documentation Library. Workflow Analysis …

IBM TRIRIGA Appli… a. Oracle Licensing Considerations

Performance Consi… Oracle Database 12.1.0.2 Standard Edition and above has restricted the number of CPU sockets and threads that can be Understanding you… licensed. Thus, Oracle Database 12.1.0.2 Standard Edition would not likely be a good candidate for an advanced configuration. Instead, licensing the Enterprise Edition or using the IBM DB2 database in an advanced configuration is recommended. For more Database Indexes f… information, see Oracle Database 12.1.0.2 Standard Edition (SE2) available for download.

SQL Server Index … b. Oracle RAC Considerations Performance Degra…

DB2 Database Sho… Many customers think that many smaller nodes in a Real Application Clusters (RAC) configuration will yield better performance. This configuration may be fine for high availability, but small system-based RAC is not the best solution for performance, and Platform Logging overall, ends up hurting performance. To scale Oracle for performance, the solution is vertical scalability, that is, adding CPU, RAM, and disk to the individual nodes. Many performance issues are the result of environmental configuration and the choice to Portal and Navigation use smaller servers versus bigger ones.

Reporting RAC requires more resources because it must maintain the cluster state across all the nodes, as well as serve the data out to the applications. With resources consumed by the "busy work" to maintain the cluster, each node is less powerful than if it were Reserve in a single instance. RAC is good for being highly available, but at a great cost of maintainability and individual system resources. The nodes must be vertically scaled to handle the load of the requests from the application tier. But adding nodes horizontally Scheduler Engine (S… will only slow down the environment. Security SSO 5.4.2 Oracle Application Platform Indexes

Styling The following performance tuning indexes can be added to Oracle databases that are running TRIRIGA Platform 3.5.x. These System Sizing recommended Oracle performance tuning indexes are the result of iterative performance tuning cycles and collaboration with the TRIRIGA development team. The indexes listed here are not included in the TRIRIGA base product unless otherwise stated. TDI These indexes provide significant performance improvements when measured against a broad performance test workload. While Web Graphics TRIRIGA recommends adding these indexes to the Oracle database platform, performance gains might vary depending on an array of factors including application usage, load patterns, hardware sizing, application, database server configuration, and so Workflow on. Oracle database administrators should monitor databases for efficient index usage to determine the overall impact produced by applying the recommended indexes, and to determine additional indexes that will improve performance based on situational Release Notes and data composition needs. Media Library

Best Practices CREATE INDEX "PERF01_BUDGET_CODES" ON "BUDGET_CODES" ("STATUS","CODE_REF_ID","TRANSACTION_ID") TABLESPACE "TRIDATA_INDX"; Upgrading

Troubleshooting CREATE INDEX "PERF01_BUDGET_CURRENCIES" ON "BUDGET_CURRENCIES" UX Framework ("TRANSACTION_ID","CURRENCY_CODE","AMOUNT") TABLESPACE "TRIDATA_INDX”;

New Page CREATE INDEX "PERF01_BUDGET_TRANSACTION" ON "BUDGET_TRANSACTION" ("TRANSACTION_TYPE","REVERSE_FLAG","SYSTEM_DATE") TABLESPACE "TRIDATA_INDX”; Index Members CREATE INDEX "PERF01_ORGANIZATION" ON "T_ORGANIZATION" (SYS_GUIID,SYS_OBJECTID) TABLESPACE "TRIDATA_INDX" ; Trash

Tags CREATE INDEX "PERF02_ORGANIZATION" ON "T_ORGANIZATION" (UPPER(TRINAMETX)) TABLESPACE "TRIDATA_INDX”; Find a Tag analysis application CREATE INDEX "PERF01_TRIBUILDING" ON "T_TRIBUILDING" (SYS_GUIID,SYS_OBJECTID) TABLESPACE availability_section best_practices "TRIDATA_INDX" ; cad change_management changes compare compare_revisions CREATE INDEX "PERF01_TRIPEOPLE" ON "T_TRIPEOPLE" ("TRIRECORDNAMESY") TABLESPACE "TRIDATA_INDX"; customizations customize database db2 exchange find_available_times gantt_chart CREATE INDEX "PERF02_TRIPEOPLE" ON "T_TRIPEOPLE" (TRIIDTX) TABLESPACE "TRIDATA_INDX"; gantt_scheduler group memory_footprint modifications CREATE INDEX "PERF01_TRIPROPERTY" ON "T_TRIPROPERTY" (SYS_GUIID,SYS_OBJECTID) TABLESPACE modify object_label "TRIDATA_INDX" ; object_revision operating_system oracle CREATE INDEX "PERF01_TRISPACE" ON "T_TRISPACE" performance platform (SYS_OBJECTID,SYS_GUIID,UPPER(triNameTX),UPPER(triIdTX)) TABLESPACE "TRIDATA_INDX" ; problem_determination reports reserve reserve_performance revision revisioning CREATE INDEX "PERF01_TRISPACEALLOCATIONFACT" ON "T_TRISPACEALLOCATIONFACT" single_sign-on snapshot space (TRICAPTUREPERIODTXOBJID,triDimSpaceClassTXObjId,triDimLocationTXObjId,triDimWorkpointFlagLI, sql_server sso support system TRIFACTALLOCWORKPOINTS,TRIFACTALLOCAREAIMPNU) TABLESPACE "TRIDATA_INDX" ; system_performance tags: track_customizations CREATE INDEX "PERF02_TRISPACEALLOCATIONFACT" ON "T_TRISPACEALLOCATIONFACT" tririga troubleshoot tuning (TRICAPTUREPERIODTXOBJID,TRIFACTALLOCMOVESNU,TRIFACTALLOCWORKERSNU) TABLESPACE "TRIDATA_INDX" ; upgrade ux version versioning Cloud List CREATE INDEX "PERF01_TRIWORKTASK" ON "T_TRIWORKTASK" (SYS_GUIID,UPPER("TRINAMETX"),SYS_OBJECTID) TABLESPACE "TRIDATA_INDX";

Members 5.4.3 Reserve Indexes for Oracle

Any implementation of Reserve should be tuned to include appropriate indexes for performance improvement. The following indexes were identified to help increase performance dramatically for reserve queries by the TRIRIGA performance team on Oracle, but you should review and tune for your specific implementation. The following performance tuning indexes can be added to Oracle databases that are running TRIRIGA Platform 3.5.x. These recommended Oracle performance tuning indexes are the result of iterative performance tuning cycles and collaboration with the TRIRIGA development team. The indexes listed here are not included in the TRIRIGA base product unless otherwise stated. These indexes provide significant performance improvements when measured against a broad performance test workload. While TRIRIGA recommends adding these indexes to the Oracle database platform, performance gains might vary depending on an array of factors including application usage, load patterns, hardware sizing, application, database server configuration, and so on. Oracle database administrators should monitor databases for efficient index usage to determine the overall impact produced by applying the recommended indexes, and to determine additional indexes that will improve performance based on situational and data composition needs.

CREATE INDEX "PERF01_TRIRESERVATIONINSTANCE" ON "T_TRIRESERVATIONINSTANCE" (triPlannedStartDT,SYS_OBJECTID,SYS_GUIID,SYS_PROJECTID,triStatusCL) TABLESPACE "PERF34_INDX";

CREATE INDEX "PERF01_TRIRESERVATIONRESOURCE" ON "T_TRIRESERVATIONRESOURCE" (SPEC_ID,SYS_OBJECTID,triResourceTypeLI,SYS_PROJECTID) TABLESPACE "PERF34_INDX";

CREATE INDEX "PERF03_TRIPEOPLE" ON "T_TRIPEOPLE" (SPEC_ID,SYS_OBJECTID) TABLESPACE "PERF34_INDX";

CREATE INDEX "PERF01_MYPROFILE" ON "T_MYPROFILE" (SPEC_ID,SYS_OBJECTID,triRecordIdSY) TABLESPACE "PERF34_INDX";

CREATE INDEX "PERF01_TRIRESERVATIONDEF" ON "T_TRIRESERVATIONDEFINITION" (SPEC_ID,SYS_OBJECTID,SYS_GUIID,SYS_PROJECTID) TABLESPACE "PERF34_INDX";

CREATE INDEX "PERF01_TRIROLE" ON "T_TRIROLE" (SPEC_ID,triNameTX) TABLESPACE "PERF34_INDX";

CREATE INDEX "PERF01_TRICONTACTROLE" ON "T_TRICONTACTROLE" (SPEC_ID,SYS_OBJECTID,ClassifiedByRoleSysKey) TABLESPACE "PERF34_INDX";

5.4.4 Lease Indexes for Oracle

Performance benchmark testing for Lease was performed on the DB2 database platform. However, the findings from that platform may also be applicable to Oracle Database. Your database administrator can take the identified queries from the DB2 results and use the index adviser for your database platform to see what indexes are recommended on that platform.

Notes: The DB2 results in this wiki are based on out-of-the-box queries and does not take into account any additional columns that may be in your deployment. For more information, see the 5.3.4 Lease Indexes for DB2.