Introduction to Oracle 18C

-

















Comments

Post a Comment

Popular posts from this blog

ZDLRA

-
  RPO focuses on the maximum acceptable data loss  RTO focuses on the maximum acceptable downtime. Oracle DG - RTO Active DG - RTO RAC  - RTO Golden Gate - RPO Flashback - RPO ZDRLA - RPO Oracle Zero Data Loss Recovery Appliance (ZDLRA) deliver to you the capacity to improve the reliability of your environment in more than one way. You can improve the RPO. It has  lot of new cool features  virtual backups Real-time redo Tape and cloud DG/MAA integration Incremental forever backup strategy ZDLRA is one Engineered System built over Exadata. Contains Exadata Storage and Database nodes, InfiniBand network, SAS drivers Exadata, it is not just hardware, it is software too. ZDLRA solve problems in more than one topic, it is not just a backup appliance where you redirect your backups, it is an appliance that provides zero data loss. To do that the key features are: Virtual backups: Based on the input backups (incremental) generate a virtual full backup for you. Real-tim...
Read more

DB Wait events

-
  CPU Time: Scenario: A SQL query is taking a long time to execute, causing the CPU Time wait event to occur. The query is using a full table scan instead of an index, which is causing a high CPU load and slowing down other processes. fixes: ===== Adding indexes Query rewrites  limiting number of sessions  I/O Related Wait Events: Scenario: A database application is experiencing slow I/O operations, causing the I/O Related Wait Event to occur. The storage systems are not optimized and there is heavy contention for storage resources. Fixes: =====  Review your Storage system  Check for disk usage  Check for storage replacement for a high end hardware Locks: Scenario: A database application is experiencing slow performance due to excessive locking. The application is using table-level locking, causing a high contention for resources and slowing down other processes. fixes : ==== switch to row level locking Make sure to use frequent commits in the code  Ne...
Read more

My query is picking a bad execution plan , how to fix it ?

-
 Outdated Statistics: If the statistics on a table or index are outdated, the optimizer may choose a bad execution plan. For example, if you have a table with a large number of rows, but the statistics haven't been updated in a while, the optimizer may underestimate the number of rows and choose a less efficient execution plan. You can update statistics using the following command: UPDATE STATISTICS <table or index name> Query Hints: Query hints can be used to force the optimizer to use a particular execution plan. For example, if you have a query that uses a join, but the optimizer is choosing a nested loop join instead of a hash join, you can add a query hint to force the optimizer to use a hash join: SELECT * FROM table1 JOIN table2 ON table1.column1 = table2.column2 OPTION (HASH JOIN) Query Rewrite: Sometimes, rewriting a query can make it more efficient. For example, if you have a query that uses a subquery, but the optimizer is choosing to execute the subquery for every...
Read more