HOWTO Handle Repository ID Space Limitations (Doc ID 1593294.1)

Last updated on OCTOBER 26, 2015

Applies to:

Oracle ATG Web Commerce - Version 9.0 and later
Information in this document applies to any platform.

Goal

Customers are sometimes concerned about the available ID space for data stored in a SQL repository. This document is a collection of notes about questions that have arisen in this area and possible techniques for providing answers.

Out of the box SQL repositories in the Oracle ATG product are configured to use the component /atg/dynamo/service/IdGenerator which is based on the Java class SQLIdGenerator. When a repository asks for a batch of repository IDs, it uses rows in the database table das_id_generator to persist information about the IDs which have already been issued. The data file idspaces.xml in the CONFIGPATH of various application modules defines details about rows that should be added to das_id_generator for out of the box repository ID spaces during the initial setup of a core schema intended for use by Oracle ATG servers.

The repository ID column used by a conventional SQL repository is a 40 character column in a SQL table. The IdGenerator component issues repository IDs that are numerical character strings which may have an alphabetical prefix of a few characters in length. It is a common practice to configure an ID prefix by naming the prefix string in the prefix column of a row in das_id_generator. 

Solution

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms