Oracle Instance Properties / General Tab

The General tab on the Oracle Instance Properties page allows you to view and change properties for existing Oracle instances.

Tip:The next inventory import updates the values of properties returned in inventory, overwriting changes you may have made to the same properties.

The following table lists the available fields in display order:

Oracle Instance Properties on the General Tab

Property

Description

Application

The full name of the application which is a concatenation of the product name, product version, and product edition values. For example:

Oracle Database 11g Enterprise

Not editable.

Business Application

The friendly name given to the Oracle application.

Enter the business application name for this Oracle application.

Device

The name of the inventory device where this Oracle instance is installed.

Enter the name of the inventory device where the Oracle instance is installed.

Environment

The deployment environment to which this Oracle instance belongs. An organization generally divides the software and hardware infrastructure into multiple deployment environments and assigns a role (primary, backup) to each device within an environment. For example, the infrastructure (application and database servers, storage, and so on) required for development is most often a part of the Development environment.

Select one of the following values. Ensure that you check the current license consumption rules pertaining to each of the following Oracle environments.

• Development—The environment where ongoing changes to the software are developed.
• Test—The environment where the newly-developed features are tested before releasing them to production.
• Staging—The pre-production environment that is used to test all the installation, configuration, or migration scripts, before applying them to the production environment.
• Production—The live environment that is processing user requests.
• Other—Any other environment that is not in the list.

Note:The selection of a particular environment does not set license consumption exemptions for a license. You can manually set license consumption exemptions from the Consumption tab of the license properties (see License Properties / Compliance Tab) or through the inventory device roles (see Allocations and Exemptions).

Selectable in the Environment field in the General tab of the Oracle instance properties.

Installation path

The path where the database is installed on the physical machine.

Enter the path where the database is installed on the physical machine.

Last inventory date

The date when inventory was last collected from this Oracle database instance.

Note:When the inventory source is the locally-installed Inventory Agent, this normally matches the last inventory date for the host server (inventory device record). If this date is older, it may indicate recent problems in gathering inventory from this database instance, or perhaps the database instance no longer exists. (For automatic clean-up of stale inventory, navigate to Administration > IT Asset Management Settings > General, and click the Inventory tab.)

Not editable.

Licensable

Displays Yes or No to indicate whether the Oracle instance is consuming a license.

Select this check box if you want this instance to consume a license.

Managing OEM

May display any of:

• None when there has been no data gathered from any installation of Oracle Enterprise Manager (OEM) that references this database instance (or any of its related options).
• The server name of the OEM repository (data) server, when this current database instance is referenced by OEM. (Most often, the same server also hosts the OEM console, although the repository and console may sometimes be separated.) When this current database instance is referenced by OEM with the OEM repository server displayed here, check the Options tab of these properties for any Oracle options that may be enabled by this installation of Oracle Enterprise Manager.

Tip:This value relies on matching the host name for the database instance collected in FlexNet inventory with the host name reported for the instance by Oracle Enterprise Manager. If Oracle Enterprise Manager is configured to recognize hosts by IP address rather than host name, this matching cannot occur, and this field cannot display any value.

This value is not editable, and is set by data gathered from Oracle Enterprise Manager relating to this Oracle database instance.

Name

The name of the Oracle database instance. (Where this name is not yet available, a placeholder is formed from the Oracle Database application, including version and edition, or the Oracle option identified during discovery or other sources.) You can click the value displayed to view the properties (so far available) for the Oracle instance.

Tip:If an instance name ends with ~CDB_ROOT, this means the instance is a container database that can include additional pluggable databases (supported from Oracle 12c). Each of the included pluggable databases is displayed in this format, in the Instance column:

instanceName~pluggableDatabaseName 

(that is, the instance name and pluggable database name are separated by a tilde character). The pluggable databases in a related set are all prefixed with the same instance name, and of course are all hosted on the same Oracle server.

Enter the name of an Oracle instance.

Role

Specifies the role assigned to an Oracle instance within a deployment environment.

Assigning a role to an Oracle instance is a method to achieve logical grouping of databases within an environment. For example, you can assign the Primary role to a database that is actively processing the user transactions in the Production environment.

Select one of the following values. Ensure that you check the current license consumption rules pertaining to each of the following Oracle roles.

• None—Indicates that no role has been assigned.
• Backup—Specifies that the Oracle instance is being used as a backup database.
• Failover—Specifies that the Oracle instance is being used as a failover resource. The failover database is automatically transitioned to primary when the primary database fails. A database license includes right to run the licensed program(s) on an unlicensed spare computer in a failover environment for up to a total of ten separate days in any given calendar year.
• Mirroring—Specifies that the Oracle instance is being used to mirror another Oracle instance.
• Standby—Specifies that the Oracle instance is being used as a standby database. The standby database has to be manually transitioned to primary in the events like planned maintenance of the primary database.
• Other—Specifies that the device is being used for any other purpose that the above-specified options.
• Primary—Specifies that the Oracle instance is actively processing the user transactions.

Note:The selection of a particular Oracle role does not set license consumption exemptions for a license. You can manually set license consumption exemptions from the Consumption tab of the license properties (see License Properties / Compliance Tab) or through the inventory device roles (see Allocations and Exemptions).

Your chosen value is not overwritten by the discovery and inventory process.