Specific application solutions for Oracle Performance

If you are interested in how Oracle performance is adjusted and how to recycle tablespace fragments. You can browse the following articles. The following articles mainly introduce how Oracle performance is adjusted and how to recycle table space fragments.

1. Use the compress = Y parameter exp to extract the tablespace, truncate the table, and import the table imp.

2. Use

 
 

  
  
alter tablespace name coalesce; 
 
 

Manually contract once.

3. In Oracle performance adjustment, change the pctincreace parameter of the tablespace to a value greater than 0 to make it automatically contract. Generally, it is changed to 1.

 
 

  
  
alter tablespace name storage (pctincrease 1); 
 
 

About tablespace pctincrease = 1:

1) do not set pctincrease to 0 because the SMON process will only periodically merge idle chunks of tablespaces not equal to 0 in PCTINCREASE. If it is set to 0, SMON cannot merge idle fragments. In this case, you must manually use alter tablespace xxx coalesce to merge fragments.

2) do not set PCTINCREASE To a large number. It is only used to prevent the newly created table from using a large PCTINCREASE and cause uncontrollable space usage. If you no longer need to create a new table in the tablespace, this parameter will not be affected as long as it is not equal to 0.

In addition, PCTINCREASE has nothing to do with the automatic growth of tablespaces. The automatic growth of tablespaces is controlled by autoextend on, and it is purely linear growth, that is, the specified growth, it will always increase at a time). Unlike the PCTINCREASE of a table, it may lead to geometric growth.

The content above is an introduction to how Oracle performance is adjusted and how to recycle tablespace fragments. I hope you will find some gains.