Results for “temporary_tablespace”

42 results




AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

FND_OAM_DBAUSERS_VL is a reporting and diagnostic view owned by the APPS schema in Oracle E-Business Suite Release 12.1.1 and 12.2.2. It belongs to the FND (Application Object Library) product and is classified as a database view with VALID status in the ETRM repository. The view provides a thin, security-consistent projection of database user account information drawn from the Oracle data dictionary, exposing the account name, numeric user identifier, default (permanent) tablespace, and temporary tablespace for each database user known to the instance.

Its principal role is to make dictionary-level user and tablespace attributes available to EBS application code, concurrent programs, and administrative diagnostics running under the APPS schema without requiring direct grants on DBA_USERS. The "OAM" segment of the name associates the object with the Oracle Applications Manager (OAM) toolset, which surfaces it through the Applications Dashboard and related system administration pages. Because the view carries the "_VL" suffix, it participates in the EBS translated-view convention and is normally consumed through the associated synonym exposed to runtime sessions.

Underlying Base Objects

The documented view text is a simple, unfiltered selection:

  • DBA_USERS (referenced through a SYNONYM in the APPS schema) — the Oracle data dictionary view that describes all users of the database, including their authentication method, account status, profile, and default and temporary tablespace assignments.

FND_OAM_DBAUSERS_VL does not join to any EBS application tables; it is a direct projection over the dictionary. Because APPS normally cannot query DBA_USERS directly under least-privilege conventions, the synonym and this view act as the sanctioned access path. The view therefore inherits the real-time, instance-scoped nature of the dictionary: its contents reflect current database state and are not subject to EBS auditing or the APPLSYS who-column tracking applied to transactional tables.

Key Columns

  • USERNAME — the database account name, uniquely identifying each user in the instance, including EBS schemas such as APPS, APPLSYS, and custom schemas.
  • USER_ID — the numeric dictionary identifier for the account, usable as a stable join key against DBA-level and V$ session views.
  • DEFAULT_TABLESPACE — the permanent tablespace into which the user's segments are created by default; essential for capacity planning and verifying schema placement.
  • TEMPORARY_TABLESPACE — the temporary tablespace assigned to the user for sort, hash, and temporary segment activity; frequently queried to confirm consistent TEMP assignment across EBS accounts.

Common Use Cases and Queries

The most frequent reason this view is referenced is the identification of temporary tablespace assignments across EBS schemas. A typical query, matching the search term that surfaces this object, is:

  • SELECT username, default_tablespace, temporary_tablespace FROM apps.fnd_oam_dbausers_vl ORDER BY username; — produces a full inventory of account-to-tablespace mappings.
  • SELECT username FROM apps.fnd_oam_dbausers_vl WHERE temporary_tablespace = 'TEMP'; — isolates accounts bound to a specific TEMP tablespace, useful when validating a tablespace migration or confirming that all EBS schemas point to the same temporary tablespace.
  • SELECT default_tablespace, COUNT(*) FROM apps.fnd_oam_dbausers_vl GROUP BY default_tablespace; — summarizes schema distribution by permanent tablespace for capacity review.

Additional scenarios include troubleshooting sort or temp space errors reported by a specific EBS schema, auditing account placement after a database clone, and supporting OAM system administration pages that present dictionary user attributes. Because the view reads live dictionary data, results always reflect the current instance state and require no concurrent program or refresh.