Surety is performing system maintenance this weekend. Electronic date stamps on new Prior Art Database disclosures may be delayed.
Browse Prior Art Database

Extending record based file systems transparent to applications

IP.com Disclosure Number: IPCOM000246964D
Publication Date: 2016-Jul-19
Document File: 3 page(s) / 31K

Publishing Venue

The IP.com Prior Art Database


Older databases may have limitations caused by 32 bit addresses (4 GB limit for certain record types). This disclosure describes a method to get around such limitation without changing application interfaces. That is you may get much more capacity without changing the application.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 58% of the total text.

Page 01 of 3

Extending record based file systems transparent to applications

As an example, database records of a specific type may be organized in one file,

which in this case is limited to 4 GB today. Customers reaching this limit can not grow their database and have to split the database. That also means, applications are to be adapted, which is a major effort. This disclosure describes, how those types of records can grow across multiple files. This is indicated in the last up to n bits of the record address. Each bit represents 2**n files. That is the records may grow "2**n" times 4 GB. This method may be used for any kind of database. The approach is transparent for user applications.


In a database system, there is a way to address the different records of the database. Depending on the database system's design and the underlying data access method, the addressing scheme may vary.

In the sample database system addresses are integral part of the database records and a database record is an entity basically consisting of a 1) Record identification number 2) One or more addresses (Addr 1, Addr 2, Addr 3, …) to point to
other database records
3) The user data



above figure shows how such a record could look like

The addresses may represent e.g. the offset to the start of - a section within - external storage and be expected to have a fixed maximum value. Addresses may reflect the offset of a database record in a dataset.

In the sample database system, offsets are 4-byte pointers allowing to address a maximum of 4 GB of data.

0 1 2 3 … 28 29 30 31

32 bit offset ↔ 4 GB


Capacity constraints arise, when the database records need more than the max. addressable range of storage.

As one possible solution, the database records could be split. This would allow to

Addr 1 Addr 2 Addr 3 …

→ → →

User data


Page 02 of 3

use multiple datasets - e.g. one dataset for each split part -, but require adaptations in the user applications. Extending the addressable range of storage by e.g. advancing from 32-bit to 64-bit addressing appears like a most obvious solution, but could have significant implications with the underlying subsystems, including the Operating System.


In the solution presented here, pointers will no more consist of the offsets into a dataset alone, but also include a dataset number, so that they are composed of the following two parts:
1) Offset i...