Shulou(Shulou.com)05/31 Report--

This article mainly explains "what are the new ASM features of Oracle 12c". The content of the explanation is simple and clear, and it is easy to learn and understand. Please follow the editor's train of thought to study and learn "what are the new ASM features of Oracle 12c".

Orapwd file='+data/HTZXDBPRI/password/orapwhtzxdbpri' force=y dbuniquename=htzxdbpri format=12 sys=oracle sysbackup=oracle sysdg=oracle syskm=oracle

Orapwd input_file='+data/HTZXDBPRI/password/orapwhtzxdbpri' file='+ocr/asm/password/orapwASM' asm=y force=y

Srvctl config db-d htzxdbpri-a

Srvctl modify db-d htzxdbpri-pwfile'+ data/HTZXDBPRI/password/orapwhtzxdbpri'

-password file linux is $ORACLE_SID case sensitive sysdba select* from v$pwfile_users

-- linux:orapw+$ORACLE_SID

-- windows: pwd+$ORACLE_SID.ora

-- password files are stored in ASM:

Orapwd file='+data/lhrracphy/PASSWORD/pwdlhrracphy' force=y dbuniquename=lhrracphy format=12 password=lhr

Orapwd file='+data' force=y dbuniquename=lhrracphy format=12 password=lhr

Orapwd file='+data/HTZXDBPRI/password/orapwhtzxdbpri' force=y dbuniquename=htzxdbpri format=12 sys=oracle sysbackup=oracle sysdg=oracle syskm=oracle

Replace the new password file with the old password file

Orapwd input_file='+data/HTZXDBPRI/password/orapwhtzxdbpri' file='+ocr/asm/password/orapwASM' force=y

Orapwd input_file='+data/HTZXDBPRI/password/orapwhtzxdbpri' file='+ocr/asm/password/orapwASM' asm=y force=y

-- back up password files

ASMCMD > pwcopy pwdorcl.378.98780432 / home/grid/

-- configure the password file of the database

Srvctl config db-d htzxdbpri-a

Srvctl modify db-d htzxdbpri-pwfile'+ data/HTZXDBPRI/password/orapwhtzxdbpri'

Oradim-NEW-sid orcl9i-INTPWD admin-pfile d:\ oracle\ ora90\ database\ initstorm.ora

C:\ Users\ Administrator > orapwd file= "E:\ oracle\ ora8i\ DATABASE\ PWDortest.ORA" password=lhr

[oracle@robinson dbs] $orapwd file=$ORACLE_HOME/dbs/orapworcl password=oracle force=y

Asmcmd can also create password files:

$asmcmd

ASMCMD > pwcreate

ASMCMD [+] > pwcreate-- asm + DG/mydir/mypwfile 'oracle'-f-- format 12

ASMCMD [+] > pwcreate-- dbuniquename racdb + DG/mydir/mypwfile 'oracle'-f-- format 12

Other commands:

Pwcreate 、 pwdelete 、 pwcopy 、 pwmove 、 pwset 、 pwget

ASMCMD > pwget-- dbuniquename htzxdbpri

+ data/HTZXDBPRI/password/orapwhtzxdbpri

The prerequisite for ASM to store password files is the COMPATIBLE.ASM > = 12.1of the ASM disk group.

Select name,compatibility from v$asm_diskgroup

-- 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 An asm diskgroup to another

ASMCMD > pwmove-- asm + CRS/asm/password/orapwasm + data/orapwasm

Problem of SYS password synchronization in oracle 11g 12c dg environment

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.

Here are a few points of knowledge:

1. The password file in 11g cannot be stored in the asm share to access. To change the SYS password, you need to manually synchronize each RAC node. Similarly, the password file of the slave library should also be updated and overwritten manually.

2. Version 12.1 can realize password file ASM shared storage, and only one node in RAC needs to execute alter user sys to synchronize all nodes in the main library, which cannot be realized in 11g. However, the password file in the standby library still needs to be overwritten by manually synchronizing the password file of the main library.

3. Version 12.2 oracle realizes automatic synchronization of password files on all master and standby nodes under the premise of ASM sharing and storage of password files.

MOS

Automatic Password file synchronization in 12.2 Dataguard Standby database

Data Guard Standby Automatic Password file Synchronization in 12.2 (document ID 2307365.1)

1 concept

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.

This feature automatically synchronizes password files in the Oracle data protection configuration. When the password for SYS, SYSDG, and so on changes, the password file in the primary database is updated and the change is propagated to all standby databases in the configuration.

This feature provides additional automation that further simplifies management of Oracle Data Guard configurations.

This feature provides additional automation and further simplifies the management of Oracle data protection configurations.

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.

In an Oracle data protection configuration, all physical and snapshot standby databases must use a copy of the password file for the autonomous database. When administrator privileges (SYSDG, SYSOPER, SYSDBA, and so on) are granted or revoked, the copy is automatically refreshed, and when the password of any user with administrator privileges is changed, the copy is automatically refreshed. The only exception is far sync instances. The updated password file must be manually copied to far sync instances because far sync instances receives redo but does not apply it. Once the password file is up to date in the remote synchronization instance, the redo that contains the password update on the primary server is automatically propagated to any standby database that is ready for far sync instances to receive the redo. Update the password file on the standby server when the redo is applied.

2 experiment

2.1 configure the network service of the master and standby libraries in 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 modify the password of the sys user in the main library

[oracle@dg1 admin] $sqlplus sys/PDBCNDBA_P@cndba as sysdbaSQL*Plus: Release 12.2.0.1.0 Production on Tue Aug 15 10:55:49 2017Copyright (c) 1982, 2016, Oracle. The password of All rights reserved.Connected to:Oracle Database 12c Enterprise Edition Release 12.2.0.1.0-64bit ProductionSQL > alter user sys identified by oracle_p; User altered.2.3 authentication slave is also changed. SQL > connect sys/oracle_p@PDBCNDBA_P as sysdbaConnected.SQL > connect sys/oracle_p@ "PDBCNDBA_S" as sysdbaConnected.

3 reference link

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/

New feature of ORACLE 12C ASM: sharing password files

Before ORACLE 12C, everyone knew that the password file was stored in? / dbs or? / database. If you want to change the password of a user with sysdba permission, you will change the password file, while the sys password file of rac database exists in each node. At this time, you need to do the same on both nodes to change the password of sysdba permission. For the database itself, you only need to change it on one node. Because the password is recorded in user$, it is because the password file is not shared and exists in each node, so you need to execute the password change command in each node to ensure that the password file is modified normally. Because of the non-sharing mechanism of rac password files, it is tedious to modify sysdba permissions and passwords, and sometimes some nodes even forget to modify them, which leads to failures such as abnormal DG transmission logs and abnormal operation of the database when using password files. In order to solve this problem in ORACLE 12C, a new feature that password files can be stored in ASM is introduced, which makes the password files stored in ASM and shared by all nodes, thus solving this problem.

ASM Storage password File prerequisites COMPATIBLE.ASM > = 12.1

Query ASM information

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

Query about db configuration in crs

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

Here the password file of db is empty, which means that the default value is used, that is, $ORACLE_HOME/dbs/orapwxifenfei

Create password files stored in ASM

-- create a new password file for db

[oracle@xifenfei ~] $orapwd file='+data/CDB/orapwdxifenfei' dbuniquename='cdb'

Enter password for SYS:

-enter sys user password

-- create a new password file for asm

Orapwd file='+data/ASM/orapwasm' asm=y

-asm=y indicates that the password file created is asm

-- create a new db/asm password file with the old password file

Orapwd input_file='/oraclegrid/dbs/orapwasm' file='+data/ASM/orapwasm' [asm=y]

-input_file means to create a new password file stored in ASM using the old password file

View password files in 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

Configure the password file entry in crs

[grid@xifenfei ~] $srvctl modify database-db cdb-pwfile + data/CDB/orapwdxifenfei

Query about db configuration in crs

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

At this point, the database startup is completed using the password file in the password ASM. It is added that the password file configured in ASM will only take effect when you start db through crs. If you manually use sqlplus to start the database, you will not use the password file, or use the default password file. Here, I would like to remind you of the code of practice: in the RAC environment (including a single-node GI environment), the startup and shutdown operation of the database is strongly recommended to use crs-related commands, rather than the sqlplus command.

Data Guard Standby Automatic Password file Synchronization in 12.2 (document ID 2307365.1) APPLIES TO:

Oracle Database-Enterprise Edition-Version 12.2.0.1 and later

Information in this document applies to any platform.

GOAL

Automatic Password file synchronization in 12.2 Dataguard Standby database

SOLUTION

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 database software has obtained the highest level of security certification, completely surpasses all other database software, and needs to move forward steadily based on a large number of practices in maintainability. Here are a few 12c new features of password.

1. New password hash algorithm

two。 New password verify function

3. Password files can be stored in ASM

4. Password is automatically synchronized from primary to standby in Dataguard environment

5. New password authentication protocol

Here are a few of them:

1. New password hash algorithm

Oracle improves the user password hash in Oracle Database 12c. By using the PBKDF2-based SHA512 hash algorithm instead of the simple SHA1 hash, the password hash is more secure, and the user$.spare4 column stores the password hash from 11g. In version 12.1.0.2, the spare4 column consists of three parts (S:H:T). At 12.2, there are only two parts left.

The S part is the same as the algorithm at 11g, with a length of 60 chars, which is based on SHA1 hash.

Part H is a MD5-based hash with a length of 32 chars, or it may be because MD5 hash is more convenient for intruders to break violently, which was removed from the Spare4 column in version 12.2.

The T part is increased from version 12.1.0.2 to 160 chars in length, using a PBKDF2-based SHA512-based algorithm. The verification data of the latter part of the 32chars is generated randomly. It's safer.

two。 New password verify function

In 12c, default profile has the same resource restrictions except for password verify function and 11g.

However, defense security requires a recommended value:

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 newly introduced verify function has ora12c_verify_function, ora12c_strong_verify_function (ora12c_stig_verify_function), and may be in 12.1.0.1,12.1.0.2, 12.2.0.1 profile default verify function names are all different.

For example, STIG has the following restrictions:

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

3. Password files can be stored in ASM

Before Oracle Database 12c, the password file was always under the $ORACLE_HOME / dbs file, even for RAC instances and RAC ASM clusters. For RAC, DBA must try to keep this password file synchronized on each node. Now, in Oracle 12c, the password file can be stored on ASM. This means that a shared password file Oracle RAC database is shared by all instances in the cluster, and unlike ASM spfile, access to ASM password files is available only when ASM is started and after the disk group mount. The command utility for creating a password file is still the same: "orapwd"

Asmcmd can also create a password file $asmcmdASMCMD > pwcreate

ASM Storage password File prerequisites COMPATIBLE.ASM > = 12.1

Create new password in ASMorapwd file='+data/ASM/orapwasm' asm=y-- create new password in ASM from locationorapwd input_file='/oraclegrid/dbs/orapwasm' file='+data/ASM/orapwasm' [asm=y]-- move password file from An asm diskgroup to anotherASMCMD > pwmove-- asm + CRS/asm/password/orapwasm + data/orapwasm2. Password is automatically synchronized from primary to standby in Dataguard environment

A useful enhancement in 12cR2 is that password files are automatically synchronized in the Data Guard environment, if the password for sys is changed on primary database, and it is automatically changed on standby database. It had to be done manually in previous versions, usually by replacing the password file on standby database with a primary database password file.

5. New password authentication protocol upgrade 12C Note: connection failure ORA-28040 ORA-1017 has written about the authentication protocol. If your database is upgraded from a version prior to 12c, you will be prompted to remove the SEC_CASE_SENSITIVE_LOGON=FALSE parameter when upgrading, but if you do not remove SEC_CASE_SENSITIVE_LOGON=FALSE, you will encounter ora-1017 errors after login, even if the password is correct, or even change the password after the upgrade (the new password version will be "11G 12C"). The solution is change SEC_CASE_SENSITIVE_LOGON=TRUE,-the default. Also note that if it is a user created by Data Pump import, the password version will be the same as the version at the time of export. RECOMMENDED ACTIONS=+ Consider removing the following DEPRECATED initialization parameters.They are not OBSOLETE in version 12.2.0.1.0but probably will be OBSOLETE in a future release.Parameter-sec_case_sensitive_logonNote: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 protocol3. Manually copy the password file from the main library RAC to the standby library

Copy from the main library ASM to the file system:

ASMCMD > pwcopy + DATA/HISS/PASSWORD/pwdhis.256.918602833/home/grid/

Use scp or other means to copy to the host of the standby library and rename it to hiss:

$scp / home/grid/pwdhis.256.91860283310.241.8.9:/home/grid

$mv pwdhis.256.918602833 orapwhiss

Copy from the standby file system to ASM:

ASMCMD > pwcopy / home/grid/orapwhiss + DATA/HISS/PASSWORD/

4. Password file management

Query ASM information

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

Query about db configuration in crs

[grid@orcl] $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:

Here the password file of db is empty, which means that the default value is used, that is, $ORACLE_HOME/dbs/orapworcl

Create password files stored in ASM

-- create a new password file for db

[oracle@orcl ~] $orapwd file='+data/CDB/orapwdorcl' dbuniquename='cdb'

Enter password for SYS:

-enter sys user password

-- create a new password file for asm

Orapwd file='+data/ASM/orapwasm' asm=y

-asm=y indicates that the password file created is asm

-- create a new db/asm password file with the old password file

Orapwd input_file='/oraclegrid/dbs/orapwasm' file='+data/ASM/orapwasm' [asm=y]

-input_file means to create a new password file stored in ASM using the old password file

View password files in ASM

ASMCMD > showversion

ASM version: 12.1.0.1.0

ASMCMD > pwd

+ data/cdb

ASMCMD > ls-l orapwdorcl

Type Redund Striped Time Sys Name

PASSWORD UNPROT COARSE MAY 31 19:00:00 N orapwdorcl = > + DATA/CDB/PASSWORD/pwdcdb.290.816897265

Configure the password file entry in crs

[grid@orcl ~] $srvctl modify database-db cdb-pwfile + data/CDB/orapwdorcl

Query about db configuration in crs

[grid@orcl] $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/orapwdorcl

Domain:

Start options: open

Stop options: immediate

Database role: PRIMARY

Management policy: MANUAL

Database instance: cdb

Disk Groups: DATA

Services:

At this point, the database startup is completed using the password file in the password ASM.

It is added that the password file configured in ASM in this way will not take effect until db is started by crs. If you start the database with sqlplus manually, the password file will not be used, or the default password file will be used.

Here, I would like to remind you of the code of practice: in the RAC environment (including a single-node GI environment), it is strongly recommended to use crs-related commands to start and close the database, rather than using the sqlplus command.

Thank you for your reading, the above is the content of "what is the new ASM feature of Oracle 12c". After the study of this article, I believe you have a deeper understanding of what the new ASM feature of Oracle 12c is, and the specific use needs to be verified in practice. Here is, the editor will push for you more related knowledge points of the article, welcome to follow!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.