| Oracle® Database Installation Guide 10g Release 2 (10.2) for Microsoft Windows (x64) Part Number B15681-01 |
|
|
View PDF |
| Oracle® Database Installation Guide 10g Release 2 (10.2) for Microsoft Windows (x64) Part Number B15681-01 |
|
|
View PDF |
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:
Use Oracle Universal Installer to check the contents and directory location of your Oracle Database installation.
Follow these steps:
From the Start menu, select Programs, then Oracle - HOME_NAME, 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.
Oracle Enterprise Manager Database Control provides a Web-based user interface that you can use to monitor, administer, and maintain an Oracle database, including Automatic Storage Management.
To log in to Oracle Enterprise Manager Database Control:
Open your Web browser and enter the following URL
http://hostname:port/em
In a default installation, the port number is 1158. If you are unsure of the correct port number to use, look for the following line in the ORACLE_BASE\ORACLE_HOME\install\portlist.ini file:
Enterprise Manager Console HTTP Port (db_name) = port
For example, if you installed the database on a host computer named mgmt42, and the port number listed in the portlist.ini file is 5500, then enter the following URL
http://mgmt42:5500/em
Enterprise Manager displays the Database Control Login Page.
Log in to the database using the SYSMAN database user account. Enterprise Manager displays the Oracle Database home page.
Use the password you specified for the SYSMAN account during the Oracle Database installation.
|
See Also:
|
When you log in to 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 the management functionality provided with Database Control.
You can also use the SYS and SYSTEM accounts to log in to Database Control. In addition, you can grant login privileges to other database users. To grant management access for other database users, use the following procedure:
Log in to Database Control.
Click Setup at the top of the Database Control home page.
Click Administrators in the left navigation bar.
Click Create to create a new Enterprise Manager user.
In the Name field, enter the username of an existing database user or click the flashlight icon and select a user from the pop-up window.
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.
You can start and stop an Oracle database by using any of the following methods:
Starting and Stopping the Database with Oracle Enterprise Manager Database Control
Starting and Stopping the Database with Oracle Administration Assistant for Windows
Starting and Stopping the Database from the Microsoft Windows Services Utility
From a Web browser, start Enterprise Manager Database Control and log in, for example:
http://myserver:1158/em
Click Home to go to the home page.
Under General, click Start to start the database or Shutdown to shut it down.
Oracle Administration Assistant is available from the Custom installation type.
Follow these steps:
From the Start menu, select Programs, then Oracle - HOME_NAME, then Configuration and Migration Tools, 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 that you want, and from the menu, select from the following options:
Connect Database
Start Service
Disconnect Database
Stop Service
Startup/Shutdown Options
From the Start menu, select Programs, then Administrative Tools, 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 start-up properties, right-click Properties, and in the dialog box, select either Automatic, Manual, or Disabled.
This section covers the following topics:
To start and stop Automatic Storage Management, in addition to using SQL*Plus or iSQL*Plus, you can use the Windows Services utility.
To start Automatic Storage Management using the Services utility:
From the Start menu, select Programs, then Administrative Tools, then Services.
In the Services dialog box, start the following services by right-clicking their names and in the menu, selecting Start:
OracleCSService
OracleASMService+ASM
To set the start-up properties for these services, right-click Properties, and in the Properties dialog box, under Startup Type, select either Automatic, Manual, or Disabled.
Exit Services.
To stop Automatic Storage Management using the Services utility:
From the Start menu, select Programs, then Administrative Tools, then Services.
In the Services dialog box, Shut down any databases that use ASM. Names of Oracle databases are preceded with OracleService.
Right-click the OracleCSService and Oracle ASMService+ASM services and from the menu, select Stop.
Exit Services.
|
See Also: Oracle Database Administrator's Guide for information on starting and stopping ASM instances by using SQL*Plus or iSQL*Plus |
To manage Automatic Storage Management, you can use the following tools:
asmcmd: This command-line tool lets you manage ASM disk group files and directories.
Oracle Enterprise Manager Grid Control: If you have Oracle Enterprise Manager installed, you can use Grid Control to manage Automatic Storage Management functions such as migrating an existing database to ASM, checking the status of the ASM instance, checking the performance of the ASM disk groups, creating or dropping ASM disk groups, and so on.
Oracle Enterprise Manager Database Control: This utility lets you perform functions similar to Grid Control.
SQL*Plus or iSQL*Plus: You can use Automatic Storage Management-specific commands from either of these tools. To connect to the ASM instance, you use the same methods that you use to connect to an Oracle Database instance.
|
See Also:
|
To issue SQL and PL/SQL statements to Oracle Database, you can use either SQL*Plus or its Web version, iSQL*Plus. These tools enable you to perform the same database management operations, as well as to query, insert, update, or delete data directly in the database.
To start SQL*Plus:
From the Start menu, select Programs, then Oracle - HOME_NAME, then Application Development, then SQL Plus.
In the Log On dialog box, enter the user name, password, and for the host string, the name of the database to which you want to connect.
Alternatively, at the command line, you can enter the following command at a Windows command prompt:
c:\> sqlplus username/password
For example, to log on as SYSTEM using the password welcome, you would enter:
c:\> sqlplus system/welcome
If you are logging on as SYS, you would need to connect as SYSDBA:
c:\> sqlplus sys/welcome as sysdba
To start iSQL*Plus:
Open your Web browser and enter the following URL:
http://hostname:port/isqlplus
If you are unsure of the correct port number to use, check the ORACLE_BASE\ORACLE_HOME\install\portlist.ini file.
In the Login window, enter the username, password, and for the connect identifier, the name of the database to which you want to connect.
|
See Also:
|
All databases created by Oracle Database Configuration Assistant 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 usernames and passwords.
|
See Also:
|
Table 5-1 describes the administrative usernames.
Table 5-1 Administrative Accounts
|
See Also:
|
Passwords for all Oracle system administration accounts except SYS, SYSTEM, SYSMAN, 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 to unlock only the usernames you will use.
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:
|
Note: To permit unauthenticated access to your data through HTTP, unlock theANONYMOUS account. |
|
See Also: Oracle Database Administrator's Guide for more information about:
|
Use 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/SYS_password 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 IDENTIFIED BY password clause resets the password.
To unlock and reset user account passwords with Oracle Enterprise Manager Database Control:
Log in to Database Control.
Click Administration.
In the Security section of the Administration page, click Users.
Enterprise Manager displays a table containing all database accounts. The Account Status column indicates whether the account is locked and whether the password is expired.
Select the user account you want to modify, then click Edit.
Use the General page of the Users property sheet to change the password and lock or unlock the selected account. Click Help for additional information.
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 Oracle Database Configuration Assistant. For example:
sales.us.mycompany.com
In this example:
sales is the name of the database. The database name portion is a string of no more than 30 characters that can contain alphanumeric, underscore (_), dollar ($), and pound (#) characters. The DB_NAME initialization parameter specifies the database name.
us.mycompany.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.
For example, if the SID and database name for an Oracle database are ORCL, then each database file is located in the ORACLE_BASE\ORACLE_HOME\orcl directory and the initialization parameter file is located in the ORACLE_BASE\admin\orcl\pfile directory.
The starter database contains one database initialization parameter file. The initialization parameter file, init.ora.xxxxx, must exist for an instance to start. A parameter file is a text file that contains a list of instance configuration parameters. The starter database init.ora file has preconfigured parameters. You do not need to edit this file to use the starter database.
The server parameter file (SPFILE) is created from the initialization parameter file, then the initialization parameter file is renamed. The SPFILE filename is spfileSID.ora and is located in the ORACLE_BASE\ORACLE_HOME\database directory.
You can use Oracle Enterprise Manager Database Control to view the location of the server parameter file and list all of the initialization parameters, as follows:
Log in to Database Control.
Click Administration.
In the Instance section of the Administration page, click All Initialization Parameters.
Database Control displays a table listing the current value of each initialization parameter.
Click SPFile.
Database Control 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 before the table.
|
See Also:
|
An Oracle Database is divided into smaller logical areas of space known as tablespaces. Each tablespace corresponds to one or more physical datafiles. Datafiles contain the contents of logical database structures such as tables and indexes. A datafile can be associated with only one tablespace and database.
|
Note: TheSYSAUX and SYSTEM tablespaces must be present in all Oracle Database 10g release 1 (10.2) databases. |
Table 5-2 list the tablespaces and datafiles in the Oracle Database. By default, the datafiles are located in the ORACLE_BASE\oradata\DB_NAME directory.
Table 5-2 Tablespaces and Datafiles
| Tablespace | Datafile | 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 are running 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. |
To use Oracle Enterprise Manager Database Control to view the list of tablespaces currently available in your database:
Log in to Database Control.
Click Administration.
In the Storage section of the Administration page, click Tablespaces.
Enterprise Manager displays a table containing all the tablespaces currently defined for this database instance. For more information about using Database Control to view, modify, and create tablespaces, click Help.
|
See Also:
|
A redo log can be either an online redo log or an archived redo log. The online redo log is a set of two or more redo log groups that records all changes made to Oracle datafiles and control files. An archived redo log is a copy of an online redo log that has been copied to an offline destination. If the database is in ARCHIVELOG mode and automatic archiving is enabled, then the archive process or processes copy each online redo log to one or more archive log destinations after it is filled.
The starter database and the custom database each contain three redo log files located in the ORACLE_BASE\oradata\DB_NAME directory. Redo log files hold a record of 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.
To use Oracle Enterprise Manager Database Control to view or modify the redo log files for your starter database:
Start your Web browser and log in to Database Control.
Click Administration.
In the Storage section of the Administration page, click Redo Log Groups.
Enterprise Manager displays a table containing the control files currently defined for this database instance.
To view the name and location of the redo log file associated with a particular group, select that group then click View.
For more information about using Database Control to view, modify, and create tablespaces, click Help.
|
See Also:
|
The starter database and the custom database contain three control files located in the ORACLE_BASE\oradata\DB_NAME directory. 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.
A control file is an administrative file required to start and run the database. The control file records the physical structure of the database. For example, a control file contains the database name, and the names and locations of the database datafiles and redo log files.
To use Oracle Enterprise Manager Database Control to view or modify the control files for your starter database:
Log in to Database Control.
Click Administration.
In the Storage section of the Administration page, click Controlfiles.
Enterprise Manager displays a table containing the control files currently defined for this database instance. For more information about using control files and backing up control files, click Help.
|
See Also: "Managing Control Files" of Oracle Database Administrator's Guide for information about setting this initialization parameter value |
Two main Oracle services are automatically started after installation when you create a database:
OracleServiceSID (the Oracle Database service)
OracleHOME_NAMETNSListener (the Oracle Database listener service)
If you installed Oracle Enterprise Manager Database Control, then the OracleDBConsoleSID service is automatically started. In you configured Automatic Storage Management, the OracleCSService and OracleASMService+ASM services are listed as well. However, other services for networking or other individual components may not automatically start.
