This chapter describes where to go after you have completed an Oracle Database installation, such as how to check the installed contents, start various tools, and identify and locate various files. It covers these topics:
Checking the Installed Oracle Database Contents and Directory Location
Logging In to Oracle Enterprise Manager Database Express 12c
Use Oracle Universal Installer to check the contents and directory location of your Oracle Database installation.
Follow these steps:
From the Start menu, select All Programs, then Oracle - HOMENAME, then Oracle Installation Products, then Universal Installer.
In the Welcome window, click Installed Products to display the Inventory dialog box.
To check the installed contents, find the Oracle Database product in the list.
To find additional information about an installed product, click Details.
To check the directory location of the installed contents, click the Environment tab.
Click Close to exit the Inventory dialog box.
Click Cancel to exit Oracle Universal Installer, then click Yes to confirm.
To start Oracle Enterprise Manager Database Express, use the EM Express URL provided by Oracle Database Configuration Assistant (Oracle DBCA) during the database installation and creation. For information about logging in to Oracle Enterprise Manager Database Express see "Starting EM Express" in Oracle Database 2 Day DBA and "Accessing the Database Home Page" in Oracle Database 2 Day DBA.
If Oracle DBCA did not provide the EM Express URL during the database installation and creation, or if you need to change the EM Express port later on, then see "Configuring the HTTP Port for EM Express" in Oracle Database 2 Day DBA.
This section covers the following topics:
To start and stop Oracle Automatic Storage Management, in addition to using SQL*Plus, you can use the srvctl utility.
To start Oracle Automatic Storage Management instance using the srvctl utility, run the following command:
srvctl start asm
To stop Oracle Automatic Storage Management instance using the srvctl utility, run the following command:
srvctl stop asm
See Also:
Oracle Automatic Storage Management Administrator's Guide for information about starting and stopping Oracle Automatic Storage Management instances by using SQL*PlusTo manage Oracle Automatic Storage Management, you can use the following tools:
asmcmd: This command-line tool lets you manage Oracle Automatic Storage Management disk group files and directories.
asmtool: This command-line tool is required to stamp the disks to create or modify disk groups later on after the database installation.
Oracle Automatic Storage Management Configuration Assistant: Oracle Automatic Storage Management Configuration Assistant (ASMCA) is an interactive utility that enables you to create an Oracle Automatic Storage Management instance or upgrade existing Oracle Automatic Storage Management instances. It also enables you to create and configure disk groups, Oracle Automatic Storage Management volumes and Oracle Automatic Storage Management File Systems (ASMFS).
Oracle Enterprise Manager Cloud Control: If you have Oracle Enterprise Manager installed, you can use Cloud Control to manage Oracle ASM functions, such as migrating an existing database to Oracle ASM, checking the status of the Oracle ASM instance, checking the performance of the Oracle ASM disk groups, and creating or dropping Oracle ASM disk groups.
Oracle Enterprise Manager Database Express 12c: This utility enables you to perform basic administrative tasks such as user, performance, memory, and space management.
SQL*Plus: You can use Oracle Automatic Storage Management-specific commands from this tool. To connect to the Oracle Automatic Storage Management instance, you use the same methods that you use to connect to an Oracle Database instance.
See Also:
Oracle Automatic Storage Management Administrator's Guide for more information about managing Oracle Automatic Storage ManagementYou can start and stop an Oracle database by using any of the following methods:
Starting and Stopping the Database with Oracle Administration Assistant for Windows
Starting and Stopping the Database from the Microsoft Windows Services Utility
To start or stop the database:
From the Start menu, select All Programs, then Oracle - HOMENAME, then Configuration and Migration Tools, and then Administrative Assistant for Windows.
In the console window, expand the Oracle Administration Assistant for Windows tree structure.
Under Databases, right-click the name of the database, and from the menu, select from the following options:
Connect Database
Start Service
Disconnect Database
Stop Service
Startup/Shutdown Options
Process Information
You can use SQL or srvctl utility to start or stop the database instance. SRVCTL starts the service automatically.
To use SQL to start the database instance, start the Windows services:
From the Start menu, select All Programs, then Administrative Tools, and then Services.
In the Services dialog box, locate the name of the database you want to start or stop.
Right-click the name of the database, and from the menu, select either Start, Stop, or Pause.
To set its startup properties, right-click Properties, and in the dialog box, select either Automatic, Manual, or Disabled from the Startup type list.
To issue SQL and PL/SQL statements to Oracle Database, you can use SQL*Plus. This tool enables you to perform the same database management operations, and query, insert, update, or delete data directly in the database.
To start SQL*Plus, from the Start menu, select All Programs, then Oracle - HOMENAME, then Application Development, and then SQL Plus.
Alternatively, at the command line, you can enter the following command at a Windows command prompt:
C:\> sqlplus /nolog SQL> CONNECT user_name Enter password: password
For example, to log on as SYSTEM using the password password, you enter:
C:\> sqlplus /nolog
SQL> CONNECT SYSTEM
Enter password: password
If you are logging on as SYS, you must connect as SYSDBA:
C:\> sqlplus /nolog
SQL> CONNECT SYS AS SYSDBA
Enter password: password
See Also:
Oracle Database Administrator's Guide for more information about accessing Oracle Database using SQL*Plus.
To issue SQL and PL/SQL statements to Oracle Database, you can use SQL Developer. All SQL and PL/SQL commands are supported as they are passed directly from the SQL Worksheet to the Oracle Database.
To start SQL Developer:
From the Start menu, select All Programs, then Oracle - HOMENAME, then Application Development, and then SQL Developer.
If you are asked to enter the full path name for java.exe, click Browse and find java.exe. For example, C:\Program Files\Java\jdk1.6.0_25\bin\java.exe.
Once SQL Developer starts, perform the following steps:
Right-click Connections.
Select New Connection.
In the New/Select Database Connection dialog box, enter a Connection name, username, password, and for the host string, the name of the database to which you want to connect.
Click Connect.
Once connected, you can view, create, modify, and delete the database objects using the Connection Navigator or issue any SQL or PL/SQL command using a SQL Worksheet (From the Tools menu, select SQL Worksheet).
SQL*Plus commands have to be interpreted by the SQL Worksheet before being passed to the database. The SQL Worksheet currently supports many SQL*Plus commands. SQL*Plus commands which are not supported by the SQL Worksheet are ignored and are not sent to the Oracle Database.
See Also:
"SQL*Plus Statements Supported and Not Supported in SQL Worksheet" in Oracle SQL Developer User's GuideAll databases created by Oracle Database Configuration Assistant include the SYS, SYSTEM, 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. This section covers the following topics:
See Also:
"Unlocking and Resetting User Passwords" for information about using Oracle Enterprise Manager Database Express to view a complete list of the user accounts defined for your database
Oracle Database Administrator's Guide for information about Oracle security procedures and security best practices
Note:
Use Oracle Enterprise Manager Database Express 12c to view the complete list of database accounts.Table 8-1 describes the administrative user names.
Table 8-1 Administrative Accounts
| User Name | Description | See Also |
|---|---|---|
|
The account owns the Oracle Application Express schema and metadata. |
||
|
The minimally privileged account used for Oracle Application Express configuration with Oracle HTTP Server and mod_plsql. |
||
|
|
Used for storing or managing all data and metadata required by Oracle Quality of Service Management. |
None |
|
|
The account where the unified audit data trail resides. |
|
|
Owns the Business Intelligence schema included in the Oracle Sample Schemas. It is only available if you loaded the Sample Schemas. |
||
|
The Oracle Text account. |
||
|
Used by Management Agent of Oracle Enterprise Manager to monitor and manage the database. |
Oracle Enterprise Manager Cloud Control Administrator's Guide |
|
|
Used by Directory Integration Platform (DIP) to synchronize the changes in Oracle Internet Directory with the applications in the database. |
None |
|
|
|
The account owned by Database Vault that contains public functions to retrieve the Database Vault Factor values. |
|
|
|
There are two roles associated with this account. Database Vault owner role manages the Database Vault roles and configurations. The Database Vault Account Manager is used to manage database user accounts. Note: Part of Oracle Database Vault user interface text is stored in database tables in the DVSYS schema. By default, only the English language is loaded into these tables. You can use the |
|
|
Owns the Expression Filter schema. |
None |
|
|
The account owns the Oracle Application Express uploaded files. |
||
|
|
The internal account that owns the Global Data Services schema. It should not be unlocked or used for a database login. |
Oracle Database Global Data Services Concepts and Administration Guide |
|
|
The account used by Global Service Manager to connect to the Global Data Services catalog. |
Oracle Database Global Data Services Concepts and Administration Guide |
|
|
The account used by Global Service Manager to connect to the database. |
Oracle Database Global Data Services Concepts and Administration Guide |
|
Owns the Human Resources schema included in the Oracle Sample Schemas. It is available only if you loaded the Sample Schemas. |
||
|
Owns the Information Transport schema included in the Oracle Sample Schemas. This account is available only if you loaded the Sample Schemas. |
||
|
The Oracle Label Security administrator account. |
||
|
The schema used by Oracle Spatial and Graph for storing geocoder and router data. |
||
|
The Oracle Spatial and Graph, and Oracle Multimedia Locator administrator account. |
||
|
Owns the Order Entry schema included in the Oracle Sample Schemas. This account is available only if you loaded the Sample Schemas. |
||
|
This account contains the instrumentation for configuration collection used by the Oracle Configuration Manager. |
Oracle Configuration Manager Installation and Administration Guide |
|
|
|
This account contains the Oracle Multimedia DICOM data model. |
|
|
The Oracle Multimedia user. Plug-ins supplied by Oracle and third party plug-ins are installed in this schema. |
||
|
The Oracle Multimedia administrator account. |
||
|
Centrally manages metadata associated with stored outlines. Supports plan stability, which enables maintenance of the same execution plans for the same SQL statements. |
||
|
Owns the Product Media schema included in the Oracle Sample Schemas. This account is created only if you loaded the Sample Schemas. |
||
|
An account used by Oracle sample programs and examples. |
||
|
Owns the Sales History schema included in the Oracle Sample Schemas. This account is available only if you loaded the Sample Schemas during an Enterprise Edition installation |
||
|
Stores the information views for the SQL/MM Still Image Standard. |
||
|
|
The Catalog Services for the Web (CSW) account. It is used by the Oracle Spatial and Graph CSW cache manager to load all record type metadata, and record instances from the database into the main memory for the record types that are cached. |
|
|
|
The Web Feature Service (WFS) account. It is used by the Oracle Spatial and Graph WFS cache manager to load all feature-type metadata, and feature instances from the database into main memory for the feature types that are cached. |
|
|
Used for performing database administration tasks. |
||
|
|
The account used to perform backup and recovery tasks. |
Oracle Database Installation Guide (this guide) |
|
|
The account used to administer and monitor Oracle Data Guard. |
Oracle Database Installation Guide (this guide) |
|
|
The account used to perform encryption key management. |
Oracle Database Installation Guide (this guide) |
|
Used for performing database administration tasks. |
||
|
The account used to store the metadata information for Oracle Workspace Manager. |
||
|
Used for storing Oracle XML DB data and metadata. |
See Also:
"Database Administrator Usernames" in Oracle Database Administrator's Guide
"Administering External Users and Roles on Windows" in Oracle Database Platform Guide for Microsoft Windows
Passwords for all Oracle system administration accounts except SYS, SYSTEM, and DBSNMP are revoked after installation. Before you use a locked account, you must unlock it and reset its password. If you created a starter database during the installation, Oracle Database Configuration Assistant displays a screen with your database information and the Password Management button. Use the Password Management button and unlock only the user names you use.
Apply the following guidelines when specifying passwords:
Passwords must be between 8 and 30 characters long.
Passwords must not start with a numeral.
Password cannot contain invalid characters: ! @ % ^ & * ( ) + = \ | ` ~ [ { ] } ; : ' " , < > ?
Passwords must not be the same as the user name.
Passwords must not be Oracle reserved words.
The SYS account password cannot be change_on_install. (case-insensitive)
The SYSTEM account password cannot be manager. (case-insensitive)
The SYSMAN account password cannot be sysman. (case-insensitive)
The DBSNMP account password cannot be dbsnmp. (case-insensitive)
If you choose to use the same password for all the accounts, then that password cannot be change_on_install, manager, sysman, or dbsnmp. (case-insensitive)
Passwords must have at least one alphabetic, one numeric, and one special character.
Passwords must not be simple or obvious words, such as welcome, account, database, and user.
Note:
If you select the option to create the database as a multitenant container database, then you must provide the pluggable database administrator password.If you created a starter database during the installation, but you did not unlock the required account, unlock the account using one of the following methods:
See Also:
Oracle Database Administrator's Guide for more information about:Unlocking and changing passwords after installation
Oracle security procedures
Security best practices
To unlock and reset user account passwords using Oracle Enterprise Manager Database Express 12c see the "Administering Database User Accounts" section in Oracle Database 2 Day DBA.
See Also:
Click Help in the Oracle Enterprise Manager Database Express 12c window for more informationUse SQL*Plus to unlock accounts and change passwords any time after the installation process.
To change a password after installation:
Start SQL*Plus:
C:\> sqlplus /nolog
Connect as SYSDBA:
SQL> CONNECT SYS AS SYSDBA
Enter password: SYS_password
Enter a command similar to the following, where account is the user account to unlock and password is the new password:
SQL> ALTER USER account IDENTIFIED BY password ACCOUNT UNLOCK;
See Also:
Oracle Database Security Guide to learn how to add new users and change passwords
Oracle Database SQL Language Reference for the ALTER USER statement syntax used for unlocking user accounts
Oracle Database Administrator's Guide for information about the users SYS and SYSTEM
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 when using Oracle Database Configuration Assistant.
The database name input field is used to set the DB_NAME, DB_UNIQUE_NAME, and DB_DOMAIN Oracle initialization parameter values.
For example:
sales_world.example.com
In this example:
sales_world is the name of the database. The database name (DB_UNIQUE_NAME) portion is a string of no more than 30 characters that can contain alphanumeric, underscore (_), dollar ($), and pound (#) characters but must begin with an alphabetic character. No other special characters are permitted in a database name.
sales_wo is the DB_NAME. The DB_NAME initialization parameter specifies a database identifier of up to eight characters.
example.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.
However, the DB_NAME parameter need not necessarily be the first eight characters of DB_UNIQUE_NAME.
The DB_UNIQUE_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.
For example, if the SID and database name for an Oracle database are ORCL, then each database file is located in the ORACLE_BASE\oradata\orcl directory, and the initialization response file is located in the ORACLE_BASE\admin\orcl\pfile directory.
The starter database contains one database initialization response file. The initialization response file, init.ora.xxxxx, must exist for an instance to start. A response file is a text file that contains a list of instance configuration parameters. The starter database init.ora file has preconfigured parameters. You must not edit this file to use the starter database.
The server parameter file (SPFILE) is created from the initialization response file, then the initialization response file is renamed. The SPFILE file name is spfileSID.ora and is located in the ORACLE_HOME\database directory.
To use Oracle Enterprise Manager Database Express 12c to view the location of the server parameter file and list the initialization parameters, see the "Viewing and Modifying Initialization Parameters" section in Oracle Database 2 Day DBA.
See Also:
Click Help in the Oracle Enterprise Manager Database Express 12c window for more informationAn 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. A data file can be associated with only one tablespace and database.
Note:
TheSYSAUX and SYSTEM tablespaces must be present in all Oracle Database 12c databases.Table 8-2 list the tablespaces and data files in the Oracle Database. By default, the data files are located in the ORACLE_BASE\oradata\DB_NAME directory.
Table 8-2 Tablespaces and Data Files
| Tablespace | Data File | Description |
|---|---|---|
|
Serves as an auxiliary tablespace to the |
||
|
Stores the data dictionary, including definitions of tables, views, and stored procedures needed by the Oracle Database. Information in this area is maintained automatically. |
||
|
Stores temporary tables and indexes created during the processing of your SQL statement. If you run a SQL statement that involves a lot of sorting, such as the constructs |
||
|
|
Stores undo information. The undo tablespace contains one or more undo segments that maintain transaction history that is used to roll back, or undo, changes to the database. All starter databases are configured to run in automatic undo management mode. |
|
|
|
Stores database objects created by database users. |
See Also:
Oracle Database Concepts and the Oracle Database Administrator's Guide for more informationTo use Oracle Enterprise Manager Database Express 12c to view the list of data files used by the database and their associated tablespaces see the "Viewing Tablespace and Data File Information" section in Oracle Database 2 Day DBA.
For more information about Oracle Enterprise Manager Database Express 12c, and to view, modify, and create tablespaces, click Help in the Oracle Enterprise Manager Database Express 12c window.
The preconfigured database uses three redo log files. Redo log files record all 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 User's Guide for more information about redo log filesTo view or modify the redo log files for the preconfigured database using Oracle Enterprise Manager Database Express 12c see the "Viewing Online Redo Log File Information" and "Viewing Archived Redo Log File Information" sections in Oracle Database 2 Day DBA.
For more information about using Oracle Enterprise Manager Database Express 12c to view, modify, and create redo log files, click Help in the Oracle Enterprise Manager Database Express window.
The preconfigured database contains two control files located in the ORACLE_BASE\oradata\DB_NAME directory. Oracle recommends that you keep at least two control files (on separate physical drives) for each database, and set the CONTROL_FILES initialization parameter to list each control file.
A control file is an administrative file. Oracle Database 12c requires a control file to start and run the database. The control file defines the physical structure of the database. For example, it defines the database name and the names and locations of the database data files and redo log files.
To use Oracle Enterprise Manager Database Express 12c to view information about the control files for the preconfigured database see the "Viewing Control File Information" section in Oracle Database 2 Day DBA.
See Also:
Oracle Database Administrator's Guide for more information about setting theCONTROL_FILES initialization parameter valueFor more information about using Oracle Enterprise Manager Database Express 12c to perform various tasks related to tablespaces and data files, redo log files, and control files, click Help in the Oracle Enterprise Manager Database Express window.
See Also:
Oracle Database Administrator's Guide for more information about setting theCONTROL_FILES initialization parameter valueTwo main Oracle services are automatically started after installation when you create a database:
OracleServiceSID (Oracle Database service)
OracleHOMENAMETNSListener (Oracle Database listener service)
If you configured Oracle Automatic Storage Management, the OracleOHService and OracleASMService+ASM services are listed as well. However, other services for networking or other individual components may not automatically start.