![query performance tuning in oracle 10g query performance tuning in oracle 10g](https://docs.oracle.com/cd/E11882_01/server.112/e41481/img/ratug002.gif)
- #Query performance tuning in oracle 10g update
- #Query performance tuning in oracle 10g archive
- #Query performance tuning in oracle 10g software
The redo log makes it possible to replay SQL statements.This redo log records all changes made in datafiles.
![query performance tuning in oracle 10g query performance tuning in oracle 10g](https://vladmihalcea.com/wp-content/uploads/2019/09/OracleSQLDeveloperExplainPlan.png)
Redo Log - Each Oracle database has a redo log.Please ensure that your Oracle DBA takes appropriate advice from Oracle themselves, to ensure that your backup strategy is not compromised.
#Query performance tuning in oracle 10g software
Oracle is a 3rd party software vendor, so our advice is merely a guideline. CAUTION: Changing your log strategy may impact on your backup strategy.For more details see separate IBM Technote #1347841įor best performance, you could choose to configure your Oracle server to perform only the minimum of logging. For example, copy a reasonably large folder to (and from) the Oracle Server. Verify the bandwidth of the LAN Connection between the Oracle Server and Application Server for both directions. For more details see separate IBM Technote #2001776. This can be done via a variety of methods (for example automated scripts). Make sure that your Oracle database's statistics and indexes are automatically updated/maintained. (4) Oracle statistics and index maintenance For more information, see separate Technote #1367485. Typically, most customers will run this 1 or 2 times a month The superuser should regularly run this function, by clicking on the relevant menu item (inside the Controller client), whilst in 'single-user mode'. (3) Database Optimise (internal - inside the Controller client GUI) => By far the most common/recommended blocksize is 8k. This is opposite to when having a datawarehouse (with long transactions), where there could be large (32k) blocks. As a general rule of thumb, when having an OLTP application with many "small" transactions it is often better to use small database block sizes (4k-8k). When creating a tablespace, you can choose the blocksize. If one is not specified, Oracle defaults to SYSTEM, which is almost guaranteed to have a negative impact on performance. Specify a TEMPORARY TABLESPACE for each user (schema).Create a separate tablespace (usually called TEMP) for temporary segments, and place the datafile(s) for this tablespace on a separate disk device.In addition, temporary segments are used to perform complex queries like joins, UNIONs etc. When insufficient sort memory is allocated to the user process to perform a required sort, Oracle performs the sort on disk by creating temporary segments in the tablespace specified by the TEMPORARY TABLESPACE parameter for the user. (B) Further ' general ' Oracle tuning recommendations/good practices: Change the default setting of the optimizer_index_cost_adj parameter in the init.ora file.Such logs can slow down the performance significantly.