# US 2021/0081399 A1 · Automatic reclamation of storage space for database systems

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2021/0081399 A1
- Document ID: US20210081399A1
- Status: Published application
- Kind: A1
- Application number: 16/948,306
- Filed: 2020-09-11
- Published: 2021-03-18
- Earliest claimed: 2019-09-14
- Assignees: Oracle International Corporation
- Applicants: Oracle International Corporation
- Inventors: Teck Hua LEE; Tirthankar LAHIRI; Yunrui LI
- Web page: https://patentgrep.com/patent/US20210081399A1

## CPC

- G06F 16/2365: {Ensuring data consistency and integrity}
- G06F 16/22: Indexing; Data structures therefor; Storage structures
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

An approach is described to provide a method, a computer program product, and a computer system to implement hole punching. The described approach provides an automated way to free up space without requiring manual intervention by a DBA to manually reorganize database objects to free up space.

## Claims

### Claim 1

A method, comprising:
identifying a free extent in a database system, wherein a physical storage is allocated to the free extent at a physical storage layer;
determining that the free extent is a hole that is located between two allocated extents within a file;
determining whether a database consistency problem will exist if the free extent is disassociated from the physical storage; and
deallocating the physical storage from the free extent after making a determination whether the database consistency problem will occur if the free extent is disassociated from the physical storage.

### Claim 2 (depends on 1)

The method of claim 1, further comprising receiving a write request for the free extent, wherein a physical storage allocation is made to materialize storage at the physical storage layer for the free extent in response to the write request.

### Claim 3 (depends on 2)

The method of claim 2, wherein the storage that is materialized is at least one of a second physical storage within the physical storage layer, or the physical storage that was previously allocated to the free extent if currently available.

### Claim 4 (depends on 1)

The method of claim 1, further comprising receiving a read request for the free extent, wherein a read response having a designated data format indicative of deallocation of the physical storage is provided in response to the read request.

### Claim 5 (depends on 1)

The method of claim 1, wherein the physical storage layer maintains metadata that tracks associations between a physical storage allocation and a logical allocation of a database object that is associated with the physical storage allocation.

### Claim 6 (depends on 5)

The method of claim 5, wherein deallocation of the physical storage from the free extent comprises an action to break a link between the physical storage allocation and the logical allocation in the metadata.

### Claim 7 (depends on 1)

The method of claim 1, wherein determining whether the database consistently problem will exist if the free extent is disassociated from the physical storage is performed by evaluation of a system commit number (SCN) to determine whether a database change located within the physical storage to be deallocated will create the database consistently problem if deleted.

### Claim 8 (depends on 1)

The method of claim 1, wherein a space usage trend is identified, and a schedule is configured to control allocation or deallocation of the physical storage.

### Claim 9 (depends on 1)

The method of claim 1, wherein the database system does not maintain state that identifies the free extent as a hole.

### Claim 10

A system, comprising:
a processor;
a memory for holding programmable code; and
wherein the programmable code includes instructions executable by the processor for identifying a free extent in a database system, wherein a physical storage is allocated to the free extent at a physical storage layer; determining that the free extent is a hole that is located between two allocated extents within a file; determining whether a database consistently problem will exist if the free extent is disassociated from the physical storage; and deallocating the physical storage from the free extent after making a determination whether the database consistency problem will occur if the free extent is disassociated from the physical storage.

### Claim 11 (depends on 10)

The system of claim 10, wherein the programmable code further comprises the instructions for a write request for the free extent, wherein a physical storage allocation is made to materialize storage at the physical storage layer for the free extent in response to the write request.

### Claim 12 (depends on 11)

The system of claim 11, wherein the storage that is materialized is at least one of a second physical storage within the physical storage layer, or the physical storage that was previously allocated to the free extent if currently available.

### Claim 13 (depends on 10)

The system of claim 10, wherein the programmable code further comprises the instructions for receiving a read request for the free extent, wherein a read response having a designated data format indicative of deallocation of the physical storage is provided in response to the read request.

### Claim 14 (depends on 10)

The system of claim 10, wherein the physical storage layer maintains metadata that tracks associations between a physical storage allocation and a logical allocation of a database object that is associated with the physical storage allocation.

### Claim 15 (depends on 14)

The system of claim 14, wherein deallocation of the physical storage from the free extent comprises an action to break a link between the physical storage allocation and the logical allocation in the metadata.

### Claim 16 (depends on 10)

The system of claim 10, wherein determining whether the database consistently problem will exist if the free extent is disassociated from the physical storage is performed by evaluation of a system commit number (SCN) to determine whether a database change located within the physical storage to be deallocated will create the database consistently problem if deleted.

### Claim 17 (depends on 10)

The system of claim 10, wherein a space usage trend is identified, and a schedule is configured to control allocation or deallocation of the physical storage.

### Claim 18 (depends on 10)

The system of claim 10, wherein the database system does not maintain state that identifies the free extent as a hole.

### Claim 19

A computer program product embodied on a computer readable medium, the computer readable medium having stored thereon a sequence of instructions which, when executed by a processor, executes a method comprising:
identifying a free extent in a database system, wherein a physical storage is allocated to the free extent at a physical storage layer;
determining that the free extent is a hole that is located between two allocated extents within a file;
determining whether a database consistently problem will exist if the free extent is disassociated from the physical storage; and
deallocating the physical storage from the free extent after making a determination whether the database consistency problem will occur if the free extent is disassociated from the physical storage.

### Claim 20 (depends on 19)

The computer program product of claim 19, wherein the sequence of instructions performs receiving a write request for the free extent, wherein a physical storage allocation is made to materialize storage at the physical storage layer for the free extent in response to the write request.

### Claim 21 (depends on 20)

The computer program product of claim 20, wherein the storage that is materialized is at least one of a second physical storage within the physical storage layer, or the physical storage that was previously allocated to the free extent if currently available.

### Claim 22 (depends on 19)

The computer program product of claim 19, wherein the sequence of instructions performs receiving a read request for the free extent, wherein a read response having a designated data format indicative of deallocation of the physical storage is provided in response to the read request.

### Claim 23 (depends on 19)

The computer program product of claim 19, wherein the physical storage layer maintains metadata that tracks associations between a physical storage allocation and a logical allocation of a database object that is associated with the physical storage allocation.

### Claim 24 (depends on 23)

The computer program product of claim 23, wherein deallocation of the physical storage from the free extent comprises an action to break a link between the physical storage allocation and the logical allocation in the metadata.

### Claim 25 (depends on 19)

The computer program product of claim 19, wherein determining whether the database consistently problem will exist if the free extent is disassociated from the physical storage is performed by evaluation of a system commit number (SCN) to determine whether a database change located within the physical storage to be deallocated will create the database consistently problem if deleted.

### Claim 26 (depends on 19)

The computer program product of claim 19, wherein a space usage trend is identified, and a schedule is configured to control allocation or deallocation of the physical storage.

### Claim 27 (depends on 19)

The computer program product of claim 19, wherein the database system does not maintain state that identifies the free extent as a hole.
