ITPub博客

This parameter sets the password for user SYS. If you issue the ALTER USERstatement to change the password for SYS after connecting to the database, both thepassword stored in the data dictionary and the password stored in the password fileare updated. This parameter is mandatory.Note: You cannot change the password for SYS ifREMOTE_LOGIN_PASSWORDFILE is set to SHARED. An errormessage is issued if you attempt to do so.orapwd参数之 : PASSWORD1. 指定sys用户的密码 , 该参数是必须的.2. 如果使

This parameter sets the name of the password file being created. You must specify thefull path name for the file. The contents of this file are encrypted, and the file cannot beread directly. This parameter is mandatory.The types of filenames allowed for the password file are operating system specific.Some operating systems require the password file to adhere to a specific format and belocated in a specific directory. Other operating systems allow the use of environmentvariables to specify the n

When you invoke this password file creation utility without supplying anyparameters, you receive a message indicating the proper use of the command asshown in the following sample output:> orapwdUsage: orapwd file=<fname> password=<password> entries=<users> force=<y/n>wherefile - name of password file (mand),password - password for SYS (mand),entries - maximum number of distinct DBAs and OPERs (opt),force - whether to overwrite existing file (opt)There are no spaces ar

Administrative users can be connected and authenticated to a local or remote databaseby using the SQL*Plus CONNECT command. They must connect using their usernameand password and the AS SYSDBA or AS SYSOPER clause. For example, user oe hasbeen granted the SYSDBA privilege, so oe can connect as follows:CONNECT oe/oe AS SYSDBAHowever, user oe has not been granted the SYSOPER privilege, so the followingcommand will fail:CONNECT oe/oe AS SYSOPERNote: Operating system authentication takes precedence

This section describes how to authenticate an administrative user using password fileauthentication.Preparing to Use Password File Authentication To enable authentication of an administrative user using password file authentication you must do the following: 1. If not already created, create the password file using the ORAPWD utility: ORAPWD FILE=filename PASSWORD=password ENTRIES=max_users 2. Set the REMOTE_LOGIN_PASSWORDFILE initialization parameter to EXCLUSIVE. (This

OSDBA and OSOPERTwo special operating system groups control database administrator connectionswhen using operating system authentication. These groups are generically referred toas OSDBA and OSOPER. The groups are created and assigned specific names as partof the database installation process. The specific names vary depending upon youroperating system and are listed in the following table:The default names assumed by the Oracle Universal Installer can be overridden. Howyou create the OSDBA and

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

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.不安全的远程连接以赋予权限的用户登录而非不安全的连接 , 必须用密码文件认证 .当使用密码文件认证时 ,数据

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

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

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

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@]

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

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@]

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默认安装 . 在日常的管理任务中 , 推荐创建另外一个管理员用户并且赋予适当的角色来执行这些任务

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

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

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

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