5 Reviewing Your Preconfigured Database

Log In to the Oracle Enterprise Manager Database Control

If you configured the Oracle Enterprise Manager Database Control during the installation, you can use it to manage your database. Alternatively, you can also use Oracle Enterprise Manager Grid Control to manager your database. To display the Database Control:

1. Use a Web browser to access the Database Control URL:

   http://host:port/em
   
   

   In this example:

   • host is the name of the computer on which you installed Oracle Database

   • port is the port number reserved for the Database Control during installation

   If you are unsure of the correct port number to use, look for the following line in the $ORACLE_HOME/install/portlist.ini file:

   Enterprise Manager Console HTTP Port (db_name) = 5500
   
   

   The installation reserves the first available port from the range 5500 to 5519. For example, if you installed Oracle Database on host mgmt42, and the Database Control uses port 5500, enter the following URL:

   http://mgmt42:5500/em
   
   

   Oracle Enterprise Manager displays the Database Control login page.

2. Log in to the database using the user name SYS and connect as SYSDBA.

   Use the password that you specified for the SYS account during the installation.

When you log in to the Oracle Enterprise Manager Database Control using the SYSMAN user account, you are logging in as the Oracle Enterprise Manager super user. The SYSMAN account is automatically granted the roles and privileges required to access all of the management features provided by the Database Control.

You can also use the SYS and SYSTEM accounts to log in to the Database Control. In addition, you can grant login privileges to other database users, as follows:

1. Log in to the Database Control.

   
   

   See Also: See "Log In to the Oracle Enterprise Manager Database Control" for information about logging in to the Database Control.

   
   

2. Click Setup at the top of the Database Control home page.

3. Click Administrators in the left navigation bar.

4. Click Create to create a new Enterprise Manager user.

5. In the Name field, enter the user name of an existing database user or click the flashlight icon and select a user from the pop-up window.

6. Enter the password for this user, then click Finish.

   Enterprise Manager assigns login privileges to the specified user and includes this user in the list of Enterprise Manager users on the Setup Administrators page.

Review Accounts and Passwords

All databases created by the Database Configuration Assistant (DBCA) include the SYS, SYSTEM, SYSMAN, and DBSNMP database accounts. In addition, Oracle provides several other administrative accounts. Before using these other accounts, you must unlock them and reset their passwords. Table 5-1 describes these accounts, listing their user names and default passwords.

Unlock and Reset User Passwords

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, you must unlock it now, using one of the following methods:

• Using Database Control to Unlock Accounts and Reset Passwords

• Using SQL*Plus to Unlock Accounts and Reset Passwords

To unlock and reset user account passwords using Oracle Enterprise Manager Database Control:

1. Log in to the Database Control.

   
   

   See Also: See "Log In to the Oracle Enterprise Manager Database Control" for information about logging in to the Database Control.

   
   

2. Click Administration.

3. In the Security section of the Administration page, 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 is expired.

4. Select the user account that you want to modify, then click Edit.

5. Use the General page of the Users property sheet to unlock the account and, optionally, to change the password.

To unlock and reset user account passwords manually:

1. Start SQL*Plus and log in as SYSDBA:

   $ sqlplus /nolog
   SQL> CONNECT SYS/SYS_password AS SYSDBA
   
   

2. 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 someone connects as that user, they must change the user’s password. To permit unauthenticated access to your data through HTTP, unlock the ANONYMOUS user account.

   
   
   
   

   See Also: See the Oracle Database Administrator's Guide for more information about: Unlocking and changing passwords after installation Oracle security procedures Best security practices

   
   

Identify Databases

The Oracle Database 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.acme.com

In this example:

• sales is the name of the database. The database name portion is a string of no more than 8 characters that can contain alphanumeric, underscore (_), and pound (#) characters. The DB_NAME initialization parameter specifies the database name.

• us.acme.com is the network domain in which the database is located. Together, the database name and the network domain make the global database name unique. The domain portion is a string of no more than 128 characters that can contain alphanumeric, underscore (_), and pound (#) characters. The DB_DOMAIN initialization parameter specifies the domain name.

The DB_NAME parameter and the DB_DOMAIN name parameter combine to create the global database name value 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.

Locate the Parameter File

By default, the preconfigured database uses a server parameter file named spfilesid.ora, which is stored in the $ORACLE_HOME/dbs directory. However, if you choose ASM or raw device storage for the database, DBCA typically uses the same storage mechanism for the server parameter file.

If the server parameter file is not located in the $ORACLE_HOME/dbs directory, 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 $ORACLE_HOME/dbs/initsid.ora.

You can use the Oracle Enterprise Manager Database Control to view the location of the server parameter file and list all of the initialization parameters, as follows:

1. Log in to the Database Control.

   
   

   See Also: See "Log In to the Oracle Enterprise Manager Database Control" for information about logging in to the Database Control.

   
   

2. Click Administration.

3. In the Instance section of the Administration page, click All Initialization Parameters.

   Enterprise Manager displays a table listing the current value of each initialization parameter.

4. 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.

Review Tablespaces and Datafiles, Redo Log Files, and Control Files

The following sections contain information about tablespaces and datafiles, redo log files, and control files:

• Identifying Tablespaces and Datafiles

• Locating Redo Log Files

• Locating Control Files