Some behavior that you would expect from a typical Oracle Database is modified in the context of a distributed database.

In general, database limits on a per-user or per-schema basis are not aggregated across all databases in the distributed database, but only apply on a per-database level.

From an application perspective, a distributed database acts a single, logical database in most respects. However, a distributed database itself consists of several independent, loosely-coupled Oracle Database instances acting as shard catalogs, query coordinators, and shards. As a result, some behavior that you would expect from a typical Oracle Database is modified in the context of a distributed database.

For example, if a distributed database user is created and a user profile is assigned to the user with the SQL statement CREATE PROFILE, the limits set in the profile do not apply to the distributed database as a whole. Rather, they apply to each database that is a part of the larger, virtual distributed database.

Therefore, if you set the maximum number of failed login attempts to 20 for a sharded user, that limit does not apply to the entire distributed database but rather applies to each individual database in the configuration. If 20 failed attempts are reached when logging into a particular shard, then those failures do not count against the limits on the other shards or the shard catalog.