Local Connections and Secure Remote Connections (36)
You can connect to Oracle Database as a privileged user over a local connection or asecure remote connection in two ways:■ If the database has a password file and you have been granted the SYSDBA orSYSOPER system privilege, then you can connect and be authenticated by apassword file.■ If the server is not using a password file, or if you have not been granted SYSDBAor SYSOPER privileges and are therefore not in the password file, you can useoperating system authentication. On most operating sy
Nonsecure Remote Connections (35)
To connect to Oracle Database as a privileged user over a nonsecure connection, youmust be authenticated by a password file. When using password file authentication,the database uses a password file to keep track of database usernames that have beengranted the SYSDBA or SYSOPER system privilege. This form of authentication isdiscussed in "Using Password File Authentication" on page 1-15.不安全的远程连接以赋予权限的用户登录而非不安全的连接 , 必须用密码文件认证 .当使用密码文件认证时 ,数据
Selecting an Authentication Method (34)
The following methods are available for authenticating database administrators:■ Operating system (OS) authentication■ A password fileNotes:■ These methods replace the CONNECT INTERNAL syntaxprovided with earlier versions of Oracle Database. CONNECTINTERNAL is no longer supported.■ Operating system authentication takes precedence overpassword file authentication. If you meet the requirements foroperating system authentication, then even if you use apassword file, you will be authenticated by
Connecting with Administrative Privileges: Example (33)
This example illustrates that a user is assigned another schema (SYS) when connectingwith the SYSDBA system privilege. Assume that the sample user oe has been grantedthe SYSDBA system privilege and has issued the following statements:CONNECT oe/oeCREATE TABLE admin_test(name VARCHAR2(20));Later, user oe issues these statements:CONNECT oe/oe AS SYSDBASELECT * FROM admin_test;User oe now receives the following error:ORA-00942: table or view does not existHaving connected as SYSDBA, user oe now ref
SYSDBA and SYSOPER (32)
The following operations are authorized by the SYSDBA and SYSOPER systemprivileges:SYSDBA ■ Perform STARTUP and SHUTDOWN operations■ ALTER DATABASE: open, mount, back up, or change character set■ CREATE DATABASE■ DROP DATABASE■ CREATE SPFILE■ ALTER DATABASE ARCHIVELOG■ ALTER DATABASE RECOVER■ Includes the RESTRICTED SESSION privilegeEffectively, this system privilege allows a user to connect as user SYS.SYSOPER ■ Perform STARTUP and SHUTDOWN operations■ ALTER DATABASE OPEN/MOUNT/BACKUP
Administrative Privileges (31)
Administrative privileges that are required for an administrator to perform basicdatabase operations are granted through two special system privileges, SYSDBA andSYSOPER. You must have one of these privileges granted to you, depending upon thelevel of authorization you require.Note: The SYSDBA and SYSOPER system privileges allow accessto a database instance even when the database is not open. Controlof these privileges is totally outside of the database itself.The SYSDBA and SYSOPER privileges c
Database Administrator Authentication (30)
As a DBA, you often perform special operations such as shutting down or starting upa database. Because only a DBA should perform these operations, the databaseadministrator usernames require a secure authentication scheme.数据库管理员认证数据库管理员需要进行一些特别的操作如 : 关闭 , 打开数据库等 . 只有DBA才能进行这些操作,因此数据库管理员用户需要进行安全认证[@more@]
The DBA Role (29)
A predefined DBA role is automatically created with every Oracle Databaseinstallation. This role contains most database system privileges. Therefore, the DBArole should be granted only to actual database administrators.Note: The DBA role does not include the SYSDBA or SYSOPERsystem privileges. These are special administrative privileges thatallow an administrator to perform basic database administrationtasks, such as creating the database and instance startup andshutdown.DBA角色该角色不包含sysdb
SYSTEM (28)
When you create an Oracle Database, the user SYSTEM is also automatically createdand granted the DBA role.The SYSTEM username is used to create additional tables and views that displayadministrative information, and internal tables and views used by various OracleDatabase options and tools. Never use the SYSTEM schema to store tables of interest tonon-administrative users.system用户system用户被赋予了DBA角色[@more@]
Database Administrator Usernames (26)
Two user accounts are automatically created when Oracle Database is installed:■ SYS (default password: CHANGE_ON_INSTALL)■ SYSTEM (default password: MANAGER)Create at least one additional administrative user and grant to that user an appropriateadministrative role to use when performing daily administrative tasks. Do not use SYSand SYSTEM for these purposes.数据库管理员用户名称安装Oracle时 , sys 与 system默认安装 . 在日常的管理任务中 , 推荐创建另外一个管理员用户并且赋予适当的角色来执行这些任务
SYS (27)
When you create an Oracle Database, the user SYS is automatically created andgranted the DBA role.All of the base tables and views for the database data dictionary are stored in theschema SYS. These base tables and views are critical for the operation of OracleDatabase. To maintain the integrity of the data dictionary, tables in the SYS schema aremanipulated only by the database. They should never be modified by any user ordatabase administrator, and no one should create any tables in the schema
The Database Administrator's Operating System Account (25)
To perform many of the administrative duties for a database, you must be able toexecute operating system commands. Depending on the operating system on whichOracle Database is running, you might need an operating system account or ID to gainaccess to the operating system. If so, your operating system account might requireoperating system privileges or access rights that other database users do not require(for example, to perform Oracle Database software installation). Although you do notneed the
Checking Your Current Release Number (23)
To identify the release of Oracle Database that is currently installed and to see therelease levels of other database components you are using, query the data dictionaryview PRODUCT_COMPONENT_VERSION. A sample query follows. (You can also querythe V$VERSION view to see component-level information.) Other product releaselevels may increment independent of the database server.COL PRODUCT FORMAT A35COL VERSION FORMAT A15COL STATUS FORMAT A15SELECT * FROM PRODUCT_COMPONENT_VERSION;It is important to
Major Database Release Number (22)
The first digit is the most general identifier. It represents a major new version of thesoftware that contains significant new functionality.Database Maintenance Release NumberThe second digit represents a maintenance release level. Some new features may alsobe included.Application Server Release NumberThe third digit reflects the release level of the Oracle Application Server (OracleAS).Component-Specific Release NumberThe fourth digit identifies a release level specific to a component. Differe
Database Administrator Security and Privileges (24)
To perform the administrative tasks of an Oracle Database DBA, you need specificprivileges within the database and possibly in the operating system of the server onwhich the database runs. Access to a database administrator's account should betightly controlled.数据库管理员安全与权限执行DBA的相关任务 , 需要数据库运行服务器操作系统 以及 数据库 特殊的权限[@more@]
Identifying Your Oracle Database Software Release (21)
Because Oracle Database continues to evolve and can require maintenance, Oracleperiodically produces new releases. Not all customers initially subscribe to a newrelease or require specific maintenance for their existing release. As a result, multiplereleases of the product exist simultaneously.As many as five numbers may be required to fully identify a release. The significanceof these numbers is discussed in the sections that follow.To understand the release nomenclature used by Oracle, examine
Selecting an Instance with Environment Variables : Windows Example (20)
On Windows, you must set only the ORACLE_SID environment variable to select aninstance before starting SQL*Plus.SET ORACLE_SID=SAL1使用环境变量选择实例之 : Windows环境Windows环境下 , 可使用SET语句来选择唯一的ORACLE_SID环境便令来选择实例 , 如SET ORACLE_SID=SAL1[@more@]
Selecting an Instance with Environment Variables : Solaris Example (19)
The following Solaris example sets the environment variables that are required forselecting an instance. When switching between instances with different Oracle homes,the ORACLE_HOME environment variable must be changed.% setenv ORACLE_SID SAL1% setenv ORACLE_HOME /u01/app/oracle/product/10.1.0/db_1% setenv LD_LIBRARY_PATH /usr/lib:/usr/dt/lib:/usr/openwin/lib:/usr/ccs/libMost UNIX installations come with two scripts, oraenv and coraenv, that can beused to easily set these environment variables.
Selecting an Instance with Environment Variables (18)
Before you attempt to use SQL*Plus to connect locally to an Oracle instance, you mustensure that environment variables are set properly. When multiple database instancesexist on one server, or when an Automatic Storage Management (ASM) instance existson the same server as one or more database instances, the environment variablesdetermine which instance SQL*Plus connects to. (This is also true when there is onlyone Oracle instance on a server.)For example, each Oracle instance (database or ASM) h
Tasks of a Database Administrator : Roll Out to Additional Hosts (17)
After you have an Oracle Database installation properly configured, tuned, patched,and tested, you may want to roll that exact installation out to other hosts. Reasons todo this include the following:■ You have multiple production database systems.■ You want to create development and test systems that are identical to yourproduction system.Instead of installing, tuning, and patching on each additional host, you can clone yourtested Oracle Database installation to other hosts, saving time and e