这篇文章主要讲解了“Oracle 12c的ASM新特性是什么”，文中的讲解内容简单清晰，易于学习与理解，下面请大家跟着小编的思路慢慢深入，一起来研究和学习“Oracle 12c的ASM新特性是什么”吧！
成都创新互联服务项目包括柴桑网站建设、柴桑网站制作、柴桑网页制作以及柴桑网络营销策划等。多年来，我们专注于互联网行业，利用自身积累的技术优势、行业经验、深度合作伙伴关系等，向广大中小型企业、政府机构等提供互联网行业的解决方案，柴桑网站推广取得了明显的社会效益与经济效益。目前，我们服务的客户以成都为中心已经辐射到柴桑省份的部分城市，未来相信会继续扩大服务区域并继续获得客户的支持与信任！
|
When password file is used for Redo Transport Authentication, the password of redo transport user should be same across primary and all its physical and snapshot standby databases. By default SYS user is used to authenticate redo transport sessions when password file is used.
Till 12cR1 Dataguard setup, if there is a change in password file of Primary database like Changes in password or Changes in admin privileges, then the password file needs to be copied from Primary database to standby database server and rename it according to standby database Instance name. If the password file of Primary and Standby databases are not same, then errors will be seen.
In 12cR2, the password file of standby database gets synchronized automatically when there is a change in Primary database password file. The password file change of Primary will be included in Redo and when the Redo is applied to standby, the synchronization happens in the background.
这里延伸几个知识点：
1 、 11g中口令文件并不能实现存放于asm共享访问，修改SYS密码，需要再每个RAC节点手动实施同步 ，同样备库的口令文件也要手动进行更新覆盖
2、12.1版本可以实现口令文件ASM共享存储，RAC中只需要一个节点执行alter user sys 就可以实现主库所有节点同步，这点是11g中无法实现。但是备库中口令文件依然需要手动同步主库的口令文件过来覆盖
3 、12.2版本oracle在口令文件ASM共享存储的前提下，实现了口令文件自动同步主备所有节点
MOS ---
Automatic Password file synchronization in 12.2 Dataguard Standby database
Data Guard Standby Automatic Password file Synchronization in 12.2 (文档 ID 2307365.1)
1 概念
This feature automatically synchronizes password files across Oracle Data Guard configurations. When the passwords of SYS, SYSDG, and so on, are changed, the password file at the primary database is updated and then the changes are propagated to all standby databases in the configuration.
该特性自动同步Oracle数据保护配置中的密码文件。当SYS、SYSDG等的密码发生更改时，主数据库中的密码文件被更新，然后将更改传播到配置中的所有备用数据库。
This feature provides additional automation that further simplifies management of Oracle Data Guard configurations.
这个特性提供了额外的自动化，进一步简化了Oracle数据保护配置的管理。
Redo Transport Authentication Using a Password File
In an Oracle Data Guard configuration, all physical and snapshot standby databases must use a copy of the password file from the primary database. That copy is automatically refreshed whenever an administrative privilege (SYSDG, SYSOPER, SYSDBA, and so on) is granted or revoked, and after the password of any user with administrative privileges is changed. The only exception to this is far sync instances. Updated password files must still be manually copied to far sync instances because far sync instances receive redo, but do not apply it. Once the password file is up-to-date at the far sync instance the redo containing the password update at the primary is automatically propagated to any standby databases that are set up to receive redo from that far sync instance. The password file is updated on the standby when the redo is applied.
在Oracle数据保护配置中，所有物理和快照备用数据库必须使用来自主数据库的密码文件副本。当管理员权限(SYSDG、SYSOPER、SYSDBA等)被授予或撤销时，该副本将自动刷新，并且任何具有管理员权限的用户的密码发生更改后，该副本将自动刷新。唯一的例外是far sync instances。更新的密码文件必须手动复制到far sync instances，因为far sync instances接收重做，但不应用它。一旦密码文件在远同步实例中是最新的，那么在主服务器上包含密码更新的重做就会自动传播到任何准备far sync instances接收重做的备用数据库。在应用重做时，在备用服务器上更新密码文件。
2 实验
2.1 tnsname.ora 中配置主备库的网络服务
PDBCNDBA_P = (DESCRIPTION = (ADDRESS = (PROTOCOL = TCP)(HOST = 192.168.1.74)(PORT = 1521)) (CONNECT_DATA = (SERVICE_NAME = cndba) ) ) PDBCNDBA_S = (DESCRIPTION = (ADDRESS = (PROTOCOL = TCP)(HOST = 192.168.1.75)(PORT = 1521)) (CONNECT_DATA = (SERVICE_NAME = cndba) ) )
2.2 修改主库sys 用户密码
[oracle@dg1 admin]$ sqlplus sys/PDBCNDBA_P@cndba as sysdba SQL*Plus: Release 12.2.0.1.0 Production on Tue Aug 15 10:55:49 2017 Copyright (c) 1982, 2016, Oracle. All rights reserved. Connected to: Oracle Database 12c Enterprise Edition Release 12.2.0.1.0 - 64bit Production SQL> alter user sys identified by oracle_p; User altered. 2.3 验证备库密码也跟着改变。 SQL> connect sys/oracle_p@PDBCNDBA_P as sysdba Connected. SQL> connect sys/oracle_p@"PDBCNDBA_S" as sysdba Connected.
3 参考链接
http://docs.oracle.com/database/122/NEWFT/new-features.htm#NEWFT-GUID-A6211BAC-0534-44B9-B988-A7CC2B97044F
https://petesdbablog.wordpress.com/2017/03/11/12-2-new-feature-automatically-synchronize-password-files-in-oracle-data-guard/
https://uhesse.com/2017/01/10/auto-sync-for-password-files-in-oracle-12c-data-guard/
在ORACLE 12C之前大家都知道密码文件是存放在?/dbs或者?/database中,如果要修改修改sysdba权限的用户密码时候,会去修改密码文件,而在rac数据库的sys密码文件是存在各个节点中,这个时候修改sysdba权限的密码就需要在两个节点都要做同样的操作,而对于数据库来说本身是只要在一个节点上修改即可,因为密码是记录在user$中,就是因为密码文件非共享且在各个节点中都有,因此需要在各个节点均要执行修改密码命令,确保密码文件被正常修改。因为rac 密码文件非共享的机制存在,导致修改sysdba权限密码繁琐,有些时候甚至有节点忘记修改,导致需要使用密码文件操作数据库的时候不能正常进行,DG传输日志异常等故障。在ORACLE 12C中为了解决这个问题,引入了密码文件可以存入ASM新特性,从而使得密码文件存储在ASM中实现所有节点共享,从而解决该问题.
ASM存储密码文件前提条件 COMPATIBLE.ASM>= 12.1
查询ASM信息
SQL> select * from v$version;
BANNER CON_ID
-------------------------------------------------------------------------------- ----------
Oracle Database 12c Enterprise Edition Release 12.1.0.1.0 - 64bit Production 0
PL/SQL Release 12.1.0.1.0 - Production 0
CORE 12.1.0.1.0 Production 0
TNS for Linux: Version 12.1.0.1.0 - Production 0
NLSRTL Version 12.1.0.1.0 - Production 0
SQL> select NAME,COMPATIBILITY from v$asm_diskgroup;
NAME COMPATIBILITY
------------------------------ ------------------------------------------------------------
DATA 12.1.0.0.0
查询crs中关于db配置
[grid@xifenfei ~]$ srvctl config database -d cdb
Database unique name: cdb
Database name: cdb
Oracle home: /u01/app/oracle/product/12.1/db_1
Oracle user: oracle
Spfile: +DATA/cdb/spfilecdb.ora
Password file:
Domain:
Start options: open
Stop options: immediate
Database role: PRIMARY
Management policy: MANUAL
Database instance: cdb
Disk Groups: DATA
Services:
这里db的password file为空,即表示使用默认值,也就是为$ORACLE_HOME/dbs/orapwxifenfei
创建密码文件存储在ASM中
--创建db新密码文件
[oracle@xifenfei ~]$ orapwd file='+data/CDB/orapwdxifenfei' dbuniquename='cdb'
Enter password for SYS:
----输入sys用户密码
--创建asm新密码文件
orapwd file='+data/ASM/orapwasm' asm=y
----asm=y 表示创建的密码文件为asm的
--使用老密码文件创建db/asm新密码文件
orapwd input_file='/oraclegrid/dbs/orapwasm' file='+data/ASM/orapwasm' [asm=y]
----input_file 表示使用老的密码文件创建新的存储在ASM中的密码文件
查看ASM中密码文件
ASMCMD> showversion
ASM version : 12.1.0.1.0
ASMCMD> pwd
+data/cdb
ASMCMD> ls -l orapwdxifenfei
Type Redund Striped Time Sys Name
PASSWORD UNPROT COARSE MAY 31 19:00:00 N orapwdxifenfei => +DATA/CDB/PASSWORD/pwdcdb.290.816897265
配置crs中password file项
[grid@xifenfei ~]$ srvctl modify database -db cdb -pwfile +data/CDB/orapwdxifenfei
查询crs中关于db配置
[grid@xifenfei ~]$ srvctl config database -d cdb
Database unique name: cdb
Database name: cdb
Oracle home: /u01/app/oracle/product/12.1/db_1
Oracle user: oracle
Spfile: +DATA/cdb/spfilecdb.ora
Password file: +data/CDB/orapwdxifenfei
Domain:
Start options: open
Stop options: immediate
Database role: PRIMARY
Management policy: MANUAL
Database instance: cdb
Disk Groups: DATA
Services:
至此数据库启动使用密码ASM中的密码文件完成,补充说明,该方式配置在ASM中的密码文件,只能是通过crs方式启动db才会生效,如果手工使用sqlplus启动数据库不会使用该密码文件,还是使用默认密码文件。这里也就提醒大家操作规范: 在RAC环境(包含单节点的GI环境)中,对数据库的启动关闭操作强烈建议使用crs相关命令来完成,而不推荐使用sqlplus命令
| Data Guard Standby Automatic Password file Synchronization in 12.2 (文档 ID 2307365.1) |
Oracle Database - Enterprise Edition - Version 12.2.0.1 and later
Information in this document applies to any platform.
Automatic Password file synchronization in 12.2 Dataguard Standby database
When password file is used for Redo Transport Authentication, the password of redo transport user should be same across primary and all its physical and snapshot standby databases. By default SYS user is used to authenticate redo transport sessions when password file is used.
Till 12cR1 Dataguard setup, if there is a change in password file of Primary database like Changes in password or Changes in admin privileges, then the password file needs to be copied from Primary database to standby database server and rename it according to standby database Instance name. If the password file of Primary and Standby databases are not same, then errors will be seen.
In 12cR2, the password file of standby database gets synchronized automatically when there is a change in Primary database password file. The password file change of Primary will be included in Redo and when the Redo is applied to standby, the synchronization happens in the background.
Exception: Far-sync Instances (where the redo will not be applied). We need to manually copy the password file. Once the password file is sync at Far-Sync instance, the redo having password file information will get transmitted to standby which are suppose to receive from Far-sync instance.
Example:
PRIMARY>select username, sysdba, sysoper, sysasm,sysbackup,authentication_type AT from v$pwfile_users;
USERNAME SYSDB SYSOP SYSAS SYSBA AT
-------------------- ----- ----- ----- ----- --------
SYS TRUE TRUE FALSE FALSE PASSWORD
SYSDG FALSE FALSE FALSE FALSE PASSWORD
SYSBACKUP FALSE FALSE FALSE TRUE PASSWORD
SYSKM FALSE FALSE FALSE FALSE PASSWORD
STANDBY>select username, sysdba, sysoper, sysasm,sysbackup,authentication_type AT from v$pwfile_users;
USERNAME SYSDB SYSOP SYSAS SYSBA AT
---------- ----- ----- ----- ----- --------
SYS TRUE TRUE FALSE FALSE PASSWORD
SYSDG FALSE FALSE FALSE FALSE PASSWORD
SYSBACKUP FALSE FALSE FALSE TRUE PASSWORD
SYSKM FALSE FALSE FALSE FALSE PASSWORD
Let's grant a role to a user at Primary database which will make changes in Password file
PRIMARY>Grant SYSOPER to user1;
Grant succeeded.
PRIMARY>select username, sysdba, sysoper, sysasm,sysbackup,authentication_type AT from v$pwfile_users;
USERNAME SYSDB SYSOP SYSAS SYSBA AT
-------------------- ----- ----- ----- ----- --------
SYS TRUE TRUE FALSE FALSE PASSWORD
SYSDG FALSE FALSE FALSE FALSE PASSWORD
SYSBACKUP FALSE FALSE FALSE TRUE PASSWORD
SYSKM FALSE FALSE FALSE FALSE PASSWORD
USER1 FALSE TRUE FALSE FALSE PASSWORD
Password file of Primary database:
-rw-r-----. 1 oracle oinstall 4096 /u01/app/oracle/product/12.2.0/dbhome_1/dbs/orapwprimdb
Switch the logfile, so that the Redo reach its standby databases
PRIMARY>alter system switch logfile;
System altered.
At standby Media recovery is not active. Verify v$pwfile_users for the granted role
STANDBY>select username, sysdba, sysoper, sysasm,sysbackup,authentication_type AT from v$pwfile_users;
USERNAME SYSDB SYSOP SYSAS SYSBA AT
---------- ----- ----- ----- ----- --------
SYS TRUE TRUE FALSE FALSE PASSWORD
SYSDG FALSE FALSE FALSE FALSE PASSWORD
SYSBACKUP FALSE FALSE FALSE TRUE PASSWORD
SYSKM FALSE FALSE FALSE FALSE PASSWORD
Password file of Standby database:
-rw-r-----. 1 oracle oinstall 3584 /u01/app/oracle/product/12.2.0/dbhome_2/dbs/orapwstdbydb
Newly granted role is not reflected in Standby, lets start Media recovery and then query v$pwfile_users.
STANDBY>recover managed standby database disconnect;
Media recovery complete.
STANDBY>select username, sysdba, sysoper, sysasm,sysbackup,authentication_type AT from v$pwfile_users;
USERNAME SYSDB SYSOP SYSAS SYSBA AT
---------- ----- ----- ----- ----- --------
SYS TRUE TRUE FALSE FALSE PASSWORD
SYSDG FALSE FALSE FALSE FALSE PASSWORD
SYSBACKUP FALSE FALSE FALSE TRUE PASSWORD
SYSKM FALSE FALSE FALSE FALSE PASSWORD
USER1 FALSE TRUE FALSE FALSE PASSWORD
Password file of standby database:
-rw-r-----. 1 oracle oinstall 4096 /u01/app/oracle/product/12.2.0/dbhome_2/dbs/orapwstdbydb
We could see after media recovery v$pwfile_users has been updated
oracle数据库软件是获得过最高级别的安全认证，完全超越其它所有数据库软件，并且在可维护性上基于大量的实践需要稳步前行，这里简单列举几个12c 关于password几个新特性。
1. 新的password hash算法
2. 新的password verify function
3. 密码文件可以存储到ASM
4. 密码自动从primary同步到standby端在Dataguard环境中
5. 新的密码认证协议
以下将介绍其中几个内容：
Oracle对Oracle Database 12c中的用户密码哈希进行了改进， 通过使用基于PBKDF2的SHA512哈希算法，而不是简单的SHA1哈希，密码哈希更安全, 从11g起user$.spare4列存储着密码的哈希值。在12.1.0.2版本时spare4列有3部分组成（S:H:T）.12.2时只剩下（S:T ）2部分。
S部分和11g时的算法一样，长度60 chars,是基于SHA1的哈希。
H部分是基于MD5的哈希，长度为32 chars, 也可能是因为MD5 hash更方便入侵者的暴力破解，在12.2 版本时从Spare4列去掉该部分。
T部分是从12.1.0.2版本增加，长度为160 chars, 使用的是基于PBKDF2-based SHA512的算法。该算法后部分32chars 的验证数据部分是随机生成。更加安全。
在12c中default profile除了password verify function和11g不同，其它资源限制都是相同的。
不过国防安全要求有个建议值：
RESOURCE NAME LIMIT
PASSWORD_LIFE_TIME 60
PASSWORD_REUSE_TIME 365
PASSWORD_REUSE_MAX 5
FAILED_LOGIN_ATTEMPTS 3
PASSWORD_VERIFY_FUNCTION ora12c_strong_verify_function
12c新引入了verify function 有ora12c_verify_function, ora12c_strong_verify_function (ora12c_stig_verify_function) ，而且可能在12.1.0.1 ,12.1.0.2, 12.2.0.1 profile默认的verify function名都不一样。
比如STIG有以下限制：
Password at least 9 characters
at least 2 capital letters
at least 2 small letters
at least 2 digits
at least 2 special characters
password must differ by at least 4 characters from the old password
在Oracle Database 12c之前，密码文件始终位于$ ORACLE_HOME / dbs文件下，即使对于RAC实例和RAC ASM集群也是如此。 对于RAC而言，DBA必须设法保持这一点密码文件在每个节点上同步。现在，在Oracle 12c中，可以将密码文件存储在ASM上。 这意味着一个共享密码文件Oracle RAC数据库为集群中的所有实例共享，与ASM spfile不同，ASM密码文件的访问只有在启动ASM ，并且在磁盘组mount后才可以访问。用于创建密码文件的命令实用程序仍然是相同的：“orapwd”
asmcmd同样也可以创建密码文件 $ asmcmd ASMCMD> pwcreate
ASM存储密码文件前提条件 COMPATIBLE.ASM>= 12.1
-- create new password in ASM orapwd file='+data/ASM/orapwasm' asm=y -- create new password in ASM from location orapwd input_file='/oraclegrid/dbs/orapwasm' file='+data/ASM/orapwasm'[asm=y] -- move password file from A asm diskgroup to another ASMCMD> pwmove --asm +CRS/asm/password/orapwasm +data/orapwasm
12cR2中一个有用的增强功能是密码文件在Data Guard环境中自动同步，如果在primary database上更改了sys的密码，并且它自动也在standby database上进行了更改。 在早期版本中必须手动完成的，通常通过使用primary database 密码文件替换standby database上的密码文件。
5. 新的密码认证协议 升级12C注意事项： 连接失败 ORA-28040 ORA-1017 之前写过关于认证的协议的。如果你的数据库是从12c以前的版本升上来的，在升级时会提示去掉SEC_CASE_SENSITIVE_LOGON=FALSE参数如下，但是如果你没有去掉SEC_CASE_SENSITIVE_LOGON=FALSE，那么升级后登录可以会遇到ora-1017错误，即使密码是正确的，甚至修改在升级后再修改密码(新的密码版本将为”11G 12C”)。解决方法是：change SEC_CASE_SENSITIVE_LOGON=TRUE, –the default.另外注意如果是Data Pump导入创建的用户，密码版本会和导出时版本一致。 RECOMMENDED ACTIONS =================== + Consider removing the following DEPRECATED initialization parameters. They are not OBSOLETE in version 12.2.0.1.0 but probably will be OBSOLETE in a future release. Parameter —————————— sec_case_sensitive_logon Note: Oracle notes that the term “version” in the allowed_logon_version_server parameter name refers to the version of the authentication protocol. It does NOT refer to the Oracle release version. sqlnet.allowed_logon_version_server, depending on the version of the authentication protocol. sqlnet.allowed_logon_version_server=12a: For Oracle Database 12c Release 1 (12.1) release 12.1.0.2 or later. sqlnet.allowed_logon_version_server=12: For the critical patch updates CPUOct2012 and later Oracle Database 11g authentication protocols (recommended). sqlnet.allowed_logon_version_server=11: For Oracle Database 11g authentication protocols (default). sqlnet.allowed_logon_version_server=10: For Oracle Database 10g authentication protocols. sqlnet.allowed_logon_version_server=8: For Oracle8i authentication protocol
从主库ASM拷贝到文件系统中：
ASMCMD> pwcopy +DATA/HISS/PASSWORD/pwdhis.256.918602833/home/grid/
使用scp或者其它方式拷贝到备库的主机中并重命名为hiss：
$ scp /home/grid/pwdhis.256.91860283310.241.8.9:/home/grid
$ mv pwdhis.256.918602833 orapwhiss
从备库文件系统拷贝到ASM中：
ASMCMD> pwcopy /home/grid/orapwhiss +DATA/HISS/PASSWORD/
查询ASM信息
|
查询crs中关于db配置
|
这里db的password file为空,即表示使用默认值,也就是为$ORACLE_HOME/dbs/orapworcl
创建密码文件存储在ASM中
|
查看ASM中密码文件
|
配置crs中password file项
|
查询crs中关于db配置
|
至此数据库启动使用密码ASM中的密码文件完成。
补充说明,该方式配置在ASM中的密码文件,只能是通过crs方式启动db才会生效,如果手工使用sqlplus启动数据库不会使用该密码文件,还是使用默认密码文件。
这里也就提醒大家操作规范: 在RAC环境(包含单节点的GI环境)中,对数据库的启动关闭操作强烈建议使用crs相关命令来完成,而不推荐使用sqlplus命令。
感谢各位的阅读，以上就是“Oracle 12c的ASM新特性是什么”的内容了，经过本文的学习后，相信大家对Oracle 12c的ASM新特性是什么这一问题有了更深刻的体会，具体使用情况还需要大家实践验证。这里是创新互联，小编将为大家推送更多相关知识点的文章，欢迎关注！
