Database desk help oracle software support support unix user

Create this group if you want a separate group of operating sytem users to have a limited set of privileges for encryption key management such as Oracle Wallet Manager management the SYSKM privilege.

Create this group as a separate group if you want to have separate administration privileges groups for Oracle ASM and Oracle Database administrators. Oracle ASM can support multiple databases. After you create the required operating system groups described in this section, you must add the Oracle software owner user typically, oracle to these groups, otherwise these groups will not be available as an option in Oracle Universal Installer while performing the database installation.

Instead, provide common assigned group and user IDs, and confirm that they are unused before you create or modify groups and users. If necessary, contact your system administrator before using or modifying an existing user or group. An OSDBA group exists, but you want to give a different group of operating system users database administrative privileges for a new Oracle Database installation. If an OSOPER group exists, but you want to give a different group of operating system users database operator privileges in a new Oracle installation.

If you require, create an OSASM group using the group name asmadmin unless a group with that name already exists:. Depending on whether you want to create a new user, or use an existing user, see the following sections:.

If an Oracle software owner user does not exist; for example, if this is the first installation of Oracle software on the system. If an Oracle software owner user exists, but you want to use a different operating system user, with different group membership, to give database administrative privileges to those groups in a new Oracle Database installation.

If you have created an Oracle software owner for Oracle Grid Infrastructure, such as grid , and you want to create a separate Oracle software owner for Oracle Database software, such as oracle. To determine if an Oracle software owner user named oracle or grid exists, enter commands similar to the following:. If the oracle user exists, then the output from this command is similar to the following:. If the grid user exists, then the output from this command is similar to the following:.

Determine whether you want to use an existing user, or create a new user. Depending on your choice, see one of the following sections for more information:. If the Oracle software owner user oracle or grid does not exist, or if you require a new Oracle software owner user, then create it as described in this section in this case to create the oracle user. In the following procedure, use the user name oracle unless a user with that name exists:. To create an oracle user, enter a command similar to the following:.

The -u option specifies the user ID. Using this command flag is optional because the system can provide you with an automatically generated user ID number. However, Oracle recommends that you specify a number.

You must note the user ID number because you need it during preinstallation. The -g option specifies the primary group, which must be the Oracle Inventory group, for example oinstall. Specify the primary group using the -g option and any required secondary group using the -G option:.

Oracle does not support modifying an existing installation owner. On Oracle Linux systems, Oracle recommends that you install Oracle Preinstallation RPMs to meet preinstallation requirements like configuring your operating system to set the resource limits in the limits. Oracle Preinstallation RPM only configures the limits.

If you are implementing Oracle Grid Infrastructure job role separation, then copy the values from the oracle user to the grid user in the limits. For each installation software owner, check the resource limits for installation, using the following recommended ranges:. Check the soft and hard limits for the file descriptor setting.

Ensure that the result is in the recommended range, for example:. Check the soft and hard limits for the number of processes available to a user. Check the soft limit for the stack setting. However, note that the configuration file is distribution specific. Contact your system administrator for distribution specific configuration file information. If you are on a remote terminal, and the local system has only one visual which is typical , then use the following syntax to set your user account DISPLAY environment variable:.

To ensure that X11 forwarding does not cause the installation to fail, create a user-level SSH client configuration file for the Oracle software owner user, as follows:.

Consider the following before you install Oracle Grid Infrastructure for a standalone server, or Oracle Database:. If you plan to use Oracle Restart, then you must install Oracle Grid Infrastructure for a standalone server before you install and create the database. When you perform a database installation, the database must use the same listener created during the Oracle Grid Infrastructure for a standalone server installation, thereafter you do not have to perform the steps listed in this section.

The default listener and any additional listeners must run from the Oracle Grid Infrastructure home. If an existing Oracle Net listener process is using the same port or key value, Oracle Universal Installer looks for the next available port for example, and configures and starts the new listener on this available port. To determine if an existing listener process is running and to shut it down, if necessary:. Enter the following command to determine if a listener process is running and to identify its name and the Oracle home directory in which it is installed:.

Enter a command similar to the following to stop the listener process:. You must run Oracle Universal Installer from the oracle or grid account. However, before you start Oracle Universal Installer, you must configure the environment of the oracle or grid user. To configure the environment, you must:. Set the default file mode creation mask umask to in the shell startup file. To set the Oracle software owners' environments, follow these steps, for each software owner oracle , grid. The following procedure lists the steps for the oracle user only:.

If you are not logged in as the user, then switch to the software owner user you are configuring. For example, as the oracle user. To determine the default shell for the oracle user, enter the following command:.

Enter or edit the following line, specifying a value of for the default file mode creation mask:. If you are not installing the software on the local computer, then run the following command on the remote computer to set the DISPLAY variable:. To change the display location from the default display to a remote system display, run the following command on the local computer:.

To verify that the X applications display is set properly, run an Xbased program that comes with the operating system such as xclock. If you get any display errors see "X Window Display Errors". If xclock does not start, then contact your system administrator. You can click Browse to select a different location. See " Installation Type for Oracle Database ". Character Set—Choose the character set to use to store the data within the database. You can choose between the Default , which is based on the operating system language settings, or Unicode.

Host computer users in this group have administrative privileges on the database. This group is typically named dba. Global Database Name—Enter the fully qualified global database name. See " Database Identifiers for Oracle Database " for more about global database names. If the password you choose is not a secure password, a warning message will be displayed. Create as Container database : Enable this option to create the database as a multitenant container database CDB that can support zero, one, or many user-created pluggable databases PDBs.

This option is recommended for database installation to ensure that Oracle services run with limited privileges. For single instance databases, you can also choose to allow the Oracle Installer to create a new Windows User Account local user only which will then be used as the Oracle Home User.

If Oracle software has not previously been installed on this server, then the Create Inventory window appears. If this is not the first installation attempt on this server, then the Perform Prerequisite Checks window appears. If this is the first time you are installing any Oracle software on this computer, then the Create Inventory Directory window appears. You must specify a local directory for the inventory, which OUI uses to keep track of all Oracle software installed on the computer.

This information is used while applying patches or upgrading an existing installation, and while deinstalling Oracle software. Note that this directory is different from the Oracle home directory. In this window you can also specify the operating system group that has write permissions on the inventory directory. This prevents other users from writing over the Oracle product installation files.

Typically the oinstall group is selected. After you enter a directory path and specify an operating system group, click Next to continue. OUI performs several environment checks and indicates whether the check was a success, or resulted in a warning or failure. Details of the checks are provided in the displayed window. The installation can proceed only when all checks have a status of either Succeeded or Warning. If any of the environment checks failed, then they must be resolved manually.

If all the prerequisite checks passed, or after you click Next , the Summary window appears,. The Install window appears, showing the installation progress. After the installation phase, the Configuration Assistants window appears. This window lists the configuration assistants that are started automatically. If you chose to create a starter database, then DBCA starts automatically in a separate window.

In the Execute Configuration Scripts window, you are prompted to open a new terminal window, and to run scripts as the root user. After you run the scripts, return to this window and click OK.