| Oracle® Database Installation Guide 10g Release 2 (10.2) for hp OpenVMS Part Number B25414-02 |
|
|
View PDF |
| Oracle® Database Installation Guide 10g Release 2 (10.2) for hp OpenVMS Part Number B25414-02 |
|
|
View PDF |
This chapter provides information about the default preconfigured database, including information about Oracle database accounts, passwords, and file locations. It includes information about the following topics:
All databases that are created by Database Configuration Assistant (DBCA) include the SYS, SYSTEM, SYSMAN, and DBSNMP database accounts. In addition, Oracle provides several other administrative accounts. Before using these accounts, you must unlock them and reset their passwords. Table 7-1 describes these accounts and lists their user names and default passwords.
Note:
You can use the Oracle Enterprise Manager Database Control to view the complete list of database accounts. For more information, refer to the "Unlocking and Resetting User Passwords" section.Table 7-1 Database Accounts
| User Name | Default Password | Description | See Also |
|---|---|---|---|
|
ANONYMOUS |
ANONYMOUS |
Allows HTTP access to Oracle XML DB. |
None |
|
CTXSYS |
CTXSYS |
The Oracle Text account. |
Oracle Text Reference |
|
DBSNMP |
Password set during installation or in the Database Configuration Assistant |
The account used by the Management Agent component of Oracle Enterprise Manager to monitor and manage the database. It is created only if you configure the database to use the Database Control. |
Oracle Enterprise Manager Grid Control Installation and Basic Configuration |
|
DMSYS |
DMSYS |
The data mining account. DMSYS performs data mining operations. |
Oracle Data Mining Administrator's Guide |
|
HR |
HR |
The account that owns the Human Resources schema included in the Oracle Sample Schemas. It is available only if you loaded the Sample Schemas. |
Oracle Database Sample Schemas |
|
LBACSYS |
LBACSYS |
The Oracle Label Security administrator account. |
Oracle Label Security Administrator's Guide |
|
MDDATA |
MDDATA |
The schema used by Oracle Spatial for storing Geocoder and router data. |
Oracle Spatial User's Guide and Reference |
|
MDSYS |
MDSYS |
The Oracle Spatial and Oracle interMedia Locator administrator account. |
Oracle Spatial User's Guide and Reference |
|
OE |
OE |
The account that owns the Order Entry schema included in the Oracle Sample Schemas. It is available only if you loaded the Sample Schemas. |
Oracle Database Sample Schemas |
|
ORDPLUGINS |
ORDPLUGINS |
The Oracle interMedia user. Plugins supplied by Oracle and third-party plugins are installed in this schema. |
|
|
ORDSYS |
ORDSYS |
The Oracle interMedia administrator account. |
|
|
OUTLN |
OUTLN |
The account that supports plan stability. Plan stability enables you to maintain the same execution plans for the same SQL statements. OUTLN acts as a role to centrally manage metadata associated with stored outlines. |
|
|
PM |
PM |
The account that owns the Product Media schema included in the Oracle Sample Schemas. It is available only if you loaded the Sample Schemas. |
Oracle Database Sample Schemas |
|
SCOTT |
TIGER |
An account used by Oracle sample programs and examples. |
Oracle Database Administrator's Guide |
|
SH |
SH |
The account that owns the Sales History schema included in the Oracle Sample Schemas. It is available only if you loaded the Sample Schemas during an Enterprise Edition installation. |
Oracle Database Administrator's Guide |
|
SYS |
Password set during installation or in the Database Configuration Assistant |
The account used to perform database administration tasks. |
Oracle Database Administrator's Guide |
|
SYSTEM |
Password set during installation or in the Database Configuration Assistant |
Another account used to perform database administration tasks. |
Oracle Database Administrator's Guide |
|
WKPROXY |
WKSYS |
The Ultra Search proxy user. |
Oracle Ultra Search Administrator's Guide |
|
XDB |
XDB |
The account used for storing Oracle XML DB data and metadata. |
Oracle XML DB Developer's Guide |
Passwords for all Oracle system administration accounts except SYS, SYSTEM, SYSMAN, and DBSMP are revoked after installation. Before you use a locked account, you must unlock it and reset its password. If you created a preconfigured database during the installation, but you did not unlock a required account, then you must unlock it, by using one of the following methods:
Section 7.2.1, "Using Grid Control to Unlock Accounts and Reset Passwords"
Section 7.2.2, "Using SQL*Plus to Unlock Accounts and Reset Passwords"
Note:
If you use Database Configuration Assistant to create a new database, you can unlock accounts after the database is created by clicking Password Management before you exit from Database Configuration Assistant.To unlock and reset user account passwords using Oracle Enterprise Manager Grid Control, perform the following steps:
Log on to the Grid Control.
Click Administration.
In the Security section of the Administration screen, click Users.
Enterprise Manager displays a table listing all database accounts. The Account Status column indicates whether the account is locked and whether the password has expired.
Select the user account that you want to modify, then click Edit.
Use the General screen of the Users property sheet to unlock the account and (optionally) to change the password.
See Also:
Click Help in the Grid Control screen for more information about using the Grid ControlPerform the following steps to unlock and reset user account passwords manually:
Start SQL*Plus and log in as SYSDBA:
$ SQLPLUS/NOLOG SQL> CONNECT / AS SYSDBA
Enter a command similar to the following, where account is the user account that you want to unlock and password is the new password:
SQL> ALTER USER account [ IDENTIFIED BY password ] ACCOUNT UNLOCK
In this example:
The ACCOUNT UNLOCK clause unlocks the account.
The IDENTIFED BY password clause resets the password.
Note:
If you unlock an account but do not reset the password, then the password remains expired. The first time you connect as that user, you must change the user account password.To permit unauthenticated access to your data through HTTP, unlock the ANONYMOUS user account.
See Also:
Oracle Database Administrator's Guide for more information about:Unlocking and changing passwords after installation
Oracle security procedures
Best security practices
The Oracle Database 10g software identifies a database by its global database name. A global database name consists of the database name and database domain. Usually, the database domain is the same as the network domain, but it need not be. The global database name uniquely distinguishes a database from any other database in the same network. You specify the global database name when you create a database during the installation, or using the Database Configuration Assistant. For example:
sales.us.oracle.com
In this example:
sales is the name of the database. The database name is a string of maximum eight characters that can contain alphanumeric, underscore (_), and hash (#) characters. The DB_NAME initialization parameter specifies the database name.
us.oracle.com is the network domain in which the database is located. The database name and the network domain together constitute the unique global database name. The domain is a string of maximum 128 characters that can contain alphanumeric, underscore (_), and hash (#) characters. The DB_DOMAIN initialization parameter specifies the domain name.
The DB_NAME and DB_DOMAIN parameters combine to create the global database name value. This value is assigned to the SERVICE_NAMES parameter in the initialization parameter file.
The system identifier (SID) identifies a specific database instance. The SID uniquely distinguishes the instance from any other instance on the same computer. Each database instance requires a unique SID and database name. In most cases, the SID is the same as the database name portion of the global database name.
Note:
The SID must contain no more than 6 characters on OpenVMS-based systems.The database initialization parameter file is generated when a database is created. By default, the preconfigured database uses a server parameter file named SPFILEsid.ORA. The following subsections describe the process of locating the parameter files:
The database initialization parameter file (INIT.ORA) is generated when a database is created. The INIT.ORA file is used to start the database instance, and create the database and data dictionary. When the database creation is complete, the instance is shutdown, and the INIT.ORA file is saved to ORA_ROOT:[DBS]INITsid.ORA. The logical name ORA_PARAMS, points to ORA_ROOT:[DBS]INITsid.ORA.
The INIT.ORA file is a text file that contains a list of preconfigured instance configuration parameters that must exist for an instance to start. You do not need to edit this file to use the starter database.
See Also:
Oracle Database Administrator's Guide and Oracle Database Reference for more information about database-specific initialization parameters and their default valuesBy default, the preconfigured database uses a server parameter file named SPFILEsid.ORA, which is stored in the ORA_ROOT:[DBS] directory.
If the server parameter file is not located in this directory, then the database uses the SPFILE parameter in an initialization parameter file to locate it. The default file name and location of this initialization parameter file is ORA_ROOT:[DBS]INITsid.ORA.
You can use the Oracle Enterprise Manager to view the location of the server parameter file and list all the initialization parameters as follows:
Log on to the Enterprise Manager Control.
Under Targets tab, select the correct database target to display its home screen.
Click Administration.
In the Instance section of the Administration screen, click All Initialization Parameters.
Enterprise Manager displays a table listing the current value of each initialization parameter.
Click SPFile.
Enterprise Manager displays a table listing the value of each initialization parameter specified in the server parameter file. The location of the server parameter file is displayed above the table.
The following sections contain information about tablespaces and data files, redo log files, and control files:
An Oracle Database is divided into smaller logical areas of space known as tablespaces. Each tablespace corresponds to one or more physical data files. Data files contain the contents of logical database structures such as tables and indexes. You can associate each data file with only one tablespace and database.
Note:
The
SYSAUX and SYSTEM tablespaces must be present in all Oracle Database 10g databases.Table 7-2 describes the tablespaces that are provided by the default preconfigured database and a description of what they store.
Table 7-2 Tablespaces and Descriptions
| Tablespace | Description |
|---|---|
|
EXAMPLE |
Stores the sample schemas, if you included them. |
|
SYSAUX |
Serves as an auxiliary tablespace to the SYSTEM tablespace. Some products and options that previously used the SYSTEM tablespace now use the SYSAUX tablespace, which reduces the load on the SYSTEM tablespace. |
|
SYSTEM |
Stores the data dictionary, which includes definitions of tables, views, and stored procedures needed by Oracle Database. |
|
TEMP |
Stores temporary tables and indexes when processing SQL statements. |
|
UNDOTBS1 |
Stores undo information. |
|
USERS |
Stores database objects created by database users. |
See Also:
Oracle Database Concepts and the Oracle Database Administrator's Guide for more information about tablespaces and data filesTo use the Oracle Enterprise Manager Grid Control to view the list of data files that are used by the database and their associated tablespaces:
Log on to the Enterprise Manager Control.
Under Targets tab, select the correct database target to display its home screen.
Click Administration.
In the Storage section of the Administration screen, click Datafiles.
Enterprise Manager displays a table listing each data file and the tablespace with which it is associated.
Note:
For more information about using the Grid Control to view, modify, and create tablespaces, click Help in the Grid Control screen.The starter database and the custom database each contain three redo log files that are located in the ORA_ROOT:[ORADATA.db_name] directory. The preconfigured database uses three redo log files. These files record all the changes made to data in the database buffer cache. If an instance fails, then Oracle Database uses the redo log files to recover the modified data in memory.
Oracle Database uses redo log files in a cyclical fashion. For example, if three files constitute the online redo log, Oracle Database fills the first file, then the second file, and then the third file. In the next cycle, it reuses and fills the first file, the second file, and so on.
See Also:
Oracle Database Backup and Recovery Basics for more information about redo log filesTo use the Oracle Enterprise Manager Database Control to view or modify the redo log files for the preconfigured database, perform the following steps:
Log on to the Enterprise Manager Control.
Under the Targets tab, select the correct database target to display its home screen.
Click Administration.
In the Storage section of the Administration screen, click Redo Log Groups.
Oracle Enterprise Manager displays a table listing the redo log groups that are used by the database.
To view the name and location of the redo log file associated with a particular group, select that group and then click View.
See Also:
For more information about using the Database Control to view, modify, and create redo log files, click Help in the Database Control windowA control file is an administrative file. Oracle Database requires a control file to start and run the database. A control file defines the physical structure of the database. For example, it defines the database name and the names and locations of the data files and redo log files.
The starter database contains three control files. These files are located in the ORA_ROOT:[ORADATA.db_name] directory. The CONTROL101.CTL, CONTROL102.CTL, and CONTROL103.CTL files are automatically included in the custom database. A preconfigured database uses three control files. Oracle recommends that you keep at least three control files (on separate physical drives) for each database and set the CONTROL_FILES initialization parameter to list each control file.
To use the Oracle Enterprise Manager Grid Control to view information about the control files for the preconfigured database, perform the following steps:
Log on to the Enterprise Manager Control.
Under Targets tab, select the correct database target to display its home screen.
Click Administration.
In the Storage section of the Administration screen, click Controlfiles.
Enterprise Manager displays a table listing the control files used by the database.
See Also:
For more information about using the Database Control to view information about control files and creating backups of these files to trace them, click Help in the Database Control windowFor more information about setting the CONTROL_FILES initialization parameter value, refer to Oracle Database Administrator's Guide
The following section describe the steps to add or upgrade Oracle products:
Perform the following steps before you add or upgrade a product:
Verify that the system has Oracle Database installed.
Log on to the computer.
Run the ORAUSER command procedure for the database:
$ SET DEFAULT disk:[oracle_home_path]
$ @ORAUSER sid
If you plan to upgrade any Oracle product tables, then change the Oracle SYSTEM password to MANAGER.
Note:
If you do not change the OracleSYSTEM password to MANAGER, then the installation may fail. Oracle installation scripts often assume that the password is MANAGER. Alternatively, you can check for hard-coded user names and passwords in Oracle scripts and change them to the required user names and passwords.Back up the old code and database files (data, redo log, and control).
Mount the distribution media.
Run Oracle Universal Installer, and select Custom install.
After completing these preliminary steps, you can load and configure Oracle products.
To add a product summary:
Start Oracle Universal Installer as follows:
$ SET DEFAULT dvd_device:[DATABASE] $ @RUNINSTALLER.COM
Point to the existing Oracle home.
Select Custom Install.
Select Products to Install.
Configure the products if Oracle Universal Installer asks for any specifications.
Click Install.
Exit Oracle Universal Installer.
Start an instance.
Build or upgrade the database tables menu.
The Oracle code must be relinked under the following conditions:
Change of operating system (including an upgrade)
Changes made to Oracle Net Services configuration
Changes made to RDBMS configuration
The following sections describe how you can relink Oracle code.
Step 1 Shutting Down the Given Database(s)
Verify that you point to the right database instance. To do this, enter the following at the DCL prompt:
$ SHOW LOGICAL ORA_SID ORA_SID" = "V10G" (LNM$JOB_TABLE)
Start SQLPlus and connect to SYS. Check the V$PROCESS view to see if other processes are active.If no other processes are active, and if you are pointing to the correct instance, then shut down the given database.
Oracle background processes stop after the database is shut down. To verify this, enter the SHOW SYSTEM command at the DCL prompt.
Step 2 Removing Images
To remove images, enter the following command at the system prompt:
$ REMORACLE
Note:
Generally, no response is returned except for the return of the DCL prompt.Step 3 Relinking the Oracle Code
To relink the Oracle code, enter the following command at the DCL prompt:
@ORA_ROOT:[BIN]RELINK product | ALL
