Skip to main content

Oracle Database and ASM Password File Administration


<<Back to DB Administration Main Page

Password File Administration

In this post I will discuss about the password file, its usages and how to maintain it. Starting from 12c it is possible to store the password file in a Diskgroup. The benefit of storing a password file in DG is, its shared among the instances in case of RAC and ease the administration
The COMPATIBLE.ASM disk group attribute must be set to at least 12.1 for the disk group where the password is to be located. The SYSASM privilege is required to manage the
Oracle ASM password file. The SYSDBA privilege on Oracle ASM is required to manage the database password file.
The shared password file in a disk group is managed by ASMCMD commands, the ORAPWD tool, and SRVCTL commands. ORAPWD supports the creation of password files on
an Oracle ASM disk group. All other password file manipulation is performed with ASMCMD or SRVCTL commands.
Important Note :- Before running commands, such as ORAPWD, to create a password file, ensure that the ORACLE_SID and ORACLE_HOME environmental variables have been set properly.
Some Quick Facts about Password File
1> Orapwd is utility used to create Database and ASM password file
2> OS authentication always takes precedence over password file authentication
3> Setting REMOTE_LOGIN_PASSWORDFILE parameter to non ignores password file authentication even if the password file is present
4> Password file cannot be modified  if REMOTE_LOGIN_PASSWORDFILE parameter is set to null
5> Creating a password file via orapwd enables remote users  to connect with administrative privileges through SQL*Net
6> There must be no spaces around the equal-to ('=') character.

Creating a Password File Located in an Oracle ASM Disk Group

$ orapwd FILE='+DG_TEST_DATA/testa/orapwtesta' ENTRIES=4 DBUNIQUENAME='testa' FORMAT=12
Enter password for SYS:
Note:- If you are using 12.2 Format do ensure to use complex password to qualify the defined password complexity

Creating a Database Password File with a SYSBACKUP Entry

$orapwd FILE='+DG_TEST_DATA/testa/orapwtesta' ENTRIES=10 DBUNIQUENAME='testa' SYSBACKUP=y
Note: You can create a password file for following Role
SYSDBA
SYSOPER
SYSASM
SYSBACKUP
SYSDG
SYSKM 

Creating a Database Password File Located in a File System

$orapwd FILE='/u01/dbatest1/12.2.0.1/dbp1/dbs/orapwtest' ENTRIES=4 FORMAT=12.2

Migrating a Legacy Database Password File to Oracle Database 12c Format

$orapwd FILE='/u01/dbatest1/12.2.0.1/dbp1/dbs/orapwtest'  FORMAT=12.2 INPUT_FILE='/u01/dbatest1/12.2.0.1/dbp1/dbs/orapwtest'  FORCE=y

Describing a Password File

You can describe the password file to find its format
$orapwd DESCRIBE FILE='/u01/dbatest1/12.2.0.1/dbp1/dbs/orapwtest'
Password file Description : format=12.2

Check the list of users in the password file


SQL> col USERNAME for a25
select USERNAME,SYSDBA,SYSOPER,SYSASM,SYSBACKUP,SYSDG,SYSKM from  v$PWFILE_USERS
USERNAME                  SYSDB SYSOP SYSAS SYSBA SYSDG SYSKM
------------------------- ----- ----- ----- ----- ----- -----
SYS                       TRUE  TRUE  FALSE FALSE FALSE FALSE

Adding the user to password file 

Grant any of the password file managed privilege to add the user in password file

SQL> grant sysdba to test;
SQL> grant sysbackup to test1;

Removing the user from password file

To revoke the privilege from password file just revoke the privilege
SQL> Revoke sysdba from test;
Note:- In ASM revoking the privilege from user does not delete the user from password file. To delete the user from password file in ASM you need to drop that user

Where is the Database Password File

$ srvctl config database -d testa
Database unique name: TESTA
Database name: WDTESTDB
Oracle home: /u01/dbatest1/12.2.0.1/dbp1
Oracle user: dbatest1
Spfile: /u01/dbatest1/12.2.0.1/dbp1/dbs/spfileTESTA.ora
Password file: +DG_TEST_DATA/testa/orapwtesta
Domain:
Start options: open
Stop options: immediate
Database role: PRIMARY
Management policy: AUTOMATIC
Disk Groups: DG_TEST_DATA,DG_TEST_FRA,DG_TEST_REDO
Services:
OSDBA group:
OSOPER group:
Database instance: TESTA
OR 
$ asmcmd pwget --dbuniquename testa
+DG_TEST_DATA/testa/orapwtesta

How to Delete Database Password File

$orapwd delete=y dbuniquename=testa

How to Migrate Password File from File System to ASM DG

$ srvctl config database -d testa
Database unique name: TESTA
Database name: WDTESTDB
Oracle home: /u01/dbatest1/12.2.0.1/dbp1
Oracle user: dbatest1
Spfile: /u01/dbatest1/12.2.0.1/dbp1/dbs/spfileTESTA.ora
Password file: /u01/dbatest1/12.2.0.1/dbp1/PWDtesta.ora
Domain:
Start options: open
Stop options: immediate
Database role: PRIMARY
Management policy: AUTOMATIC
Disk Groups: DG_TEST_DATA,DG_TEST_FRA,DG_TEST_REDO
Services:
OSDBA group:
OSOPER group:
Database instance: TESTA
$ asmcmd pwcopy --dbuniquename testa /u01/dbatest1/12.2.0.1/dbp1/PWDtesta.ora +DG_TEST_DATA -f
copying /u01/dbatest1/12.2.0.1/dbp1/PWDtesta.ora -> +DG_TEST_DATA/PWDtesta.ora

How to Find the ASM Password File

$srvctl config asm
ASM home: <CRS home>
Password file: +DG_TEST_DATA/orapwasm
Backup of Password file:
ASM listener: LISTENER
Spfile: /u01/oragrid/spfile/spfileASM.ora
ASM diskgroup discovery string: AFD:*
OR
$ asmcmd pwget --asm
+DG_TEST_DATA/orapwasm

How to Delete ASM Password File

$orapwd delete=y asm=y

How to Create ASM Password File

$ orapwd file='+DG_TEST' asm=y
Enter password for SYS:

 Note: You can also use asmcmd pw* commands to create and manage ASM and Database Password File


ORAPWD

Syntax 12cR1:-
orapwd FILE=filename [ENTRIES=numusers] [FORCE={y|n}] [ASM={y|n}]
[DBUNIQUENAME=dbname] [FORMAT={12|legacy}] [SYSBACKUP={y|n}] [SYSDG={y|n}]
[SYSKM={y|n}] [DELETE={y|n}] [INPUT_FILE=input-fname]
Syntax 12cR2
orapwd file=<fname> force=<y/n> asm=<y/n>
dbuniquename=<dbname> format=<12/12.2>
delete=<y/n> input_file=<input-fname>
sys=<y/password/external(<sys-external-name>)>
sysbackup=<y/password/external(<sysbackup-external-name>)>
sysdg=<y/password/external(<sysdg-external-name>)>
syskm=<y/password/external(<syskm-external-name>)>

ASMCMD

pwcopy <=Copies a password file to the specified location.
pwcreate  <=Creates a password file at the specified location.
pwdelete <=Deletes a password file at the specified location.
pwget <=Returns the location of the password file. 
pwmove <=Moves the location of the password file.
pwset <=Sets the location of the password file.
lspwusr <=Lists the users from an Oracle ASM password file. 
orapwusr <=Adds, drops, or changes an Oracle ASM password user

Comments

  1. EloisaSteuberOctober 31, 2021 at 7:52 AM

    Attractive section of content. I just stumbled upon your blog and in accession capital to assert that I get actually enjoyed account your blog posts. Anyway I will be subscribing to your feeds and even I achievement you access consistently fast. shipping container sizes and prices

    ReplyDelete
  2. AnonymousApril 18, 2022 at 8:18 PM

    Oracle Database And Asm Password File Administration >>>>> Download Now

    >>>>> Download Full

    Oracle Database And Asm Password File Administration >>>>> Download LINK

    >>>>> Download Now

    Oracle Database And Asm Password File Administration >>>>> Download Full

    >>>>> Download LINK iF

    ReplyDelete

Post a Comment

Popular posts from this blog

How to Power On/off Oracle Exadata Machine

<<Back to Exadata Main Page How to Power On/off Oracle Exadata Machine Oracle Exadata machines can be powered on/off either by pressing the power button on front of the server or by logging in to the ILOM interface. Powering on servers using  button on front of the server The power on sequence is as follows. 1. Start Rack, including switches  Note:- Ensure the switches have had power applied for a few minutes to complete power on  configuration before starting Exadata Storage Servers 2.Start Exadata Storage Servers  Note:- Ensure all Exadata Storage Servers complete the boot process before starting the   database servers 3. Start Database Servers Powering On Servers Remotely using ILOM The ILOM can be accessed using the Web console, the command-line interface (CLI), IPMI, or SNMP. For example, to apply power to server dm01cel01 using IPMI, where dm01cel01-ilom is the host name of the ILOM for the server to be powered on, run the
Post a Comment
Read more

How to Find VIP of an Oracle RAC Cluster

<<Back to Oracle RAC Main Page How to Find Out VIP of an Oracle RAC Cluster Login clusterware owner (oracle) and execute the below command to find out the VIP hostname used in Oracle RAC $ olsnodes -i node1     node1-vip node2     node2-vip OR $ srvctl config nodeapps -viponly Network 1 exists Subnet IPv4: 10.0.0.0/255.255.0.0/bondeth0, static Subnet IPv6: Ping Targets: Network is enabled Network is individually enabled on nodes: Network is individually disabled on nodes: VIP exists: network number 1, hosting node node1 VIP Name: node1-vip VIP IPv4 Address: 10.0.0.1 VIP IPv6 Address: VIP is enabled. VIP is individually enabled on nodes: VIP is individually disabled on nodes: VIP exists: network number 1, hosting node node2 VIP Name: node2-vip VIP IPv4 Address: 10.0.0.2 VIP IPv6 Address: VIP is enabled. VIP is individually enabled on nodes: VIP is individually disabled on nodes:
1 comment
Read more

ORA-28374: typed master key not found in wallet

<<Back to Oracle DB Security Main Page ORA-46665: master keys not activated for all PDBs during REKEY SQL> ADMINISTER KEY MANAGEMENT SET KEY FORCE KEYSTORE IDENTIFIED BY xxxx WITH BACKUP CONTAINER = ALL ; ADMINISTER KEY MANAGEMENT SET KEY FORCE KEYSTORE IDENTIFIED BY xxxx WITH BACKUP CONTAINER = ALL * ERROR at line 1: ORA-46665: master keys not activated for all PDBs during REKEY I found following in the trace file REKEY: Create Key in PDB 3 resulted in error 46658 *** 2019-02-06T15:27:04.667485+01:00 (CDB$ROOT(1)) REKEY: Activation of Key AdnU5OzNP08Qv1mIyXhP/64AAAAAAAAAAAAAAAAAAAAAAAAAAAAA in PDB 3 resulted in error 28374 REKEY: Keystore needs to be restored from the REKEY backup.Aborting REKEY! Cause: All this hassle started because I accidently deleted the wallet and all wallet backup files too and also forgot the keystore password. There was no way to restore the wallet back. Fortunately in my case the PDB which had encrypted data was supposed to be deco
7 comments
Read more

ORA-16905: The member was not enabled yet

<<Back to Oracle DataGuard Main Page ORA-16905 Physical Standby Database is disabled DGMGRL> show configuration; Configuration - DG_ORCL1P   Protection Mode: MaxPerformance   Members:   ORCL1PP - Primary database     ORCL1PS - Physical standby database (disabled)       ORA-16905: The member was not enabled yet. Fast-Start Failover:  Disabled Configuration Status: SUCCESS   (status updated 58 seconds ago) DGMGRL> DGMGRL> enable database 'ORCL1PS'; Enabled. DGMGRL>  show configuration; Configuration - DG_ORCL1P   Protection Mode: MaxPerformance   Members:   ORCL1PP - Primary database     ORCL1PS - Physical standby database Fast-Start Failover:  Disabled Configuration Status: SUCCESS   (status updated 38 seconds ago)
Post a Comment
Read more

How to Switch Log File from All Instances in RAC

<<Back to Oracle RAC Main Page Switch The Log File of All Instances in Oracle RAC. In many cases you need to switch the logfile of the database. You can switch logfile using alter system switch logfile command but if you want to switch the logfile from all the instances you need to execute the command on all the instances individually and therefore you must login on all the instances. You can avoid this and switch logfile of all instances by just running the below command from any of the instance in RAC database SQL> ALTER SYSTEM SWITCH ALL LOGFILE;   System altered.
Post a Comment
Read more

ORA-65104: operation not allowed on an inactive pluggable database alter pluggable database open

<<Back to DB Administration Main Page ORA-65104: operation not allowed on an inactive pluggable database SQL> alter pluggable database TEST_CLON open; alter pluggable database TEST_CLON open * ERROR at line 1: ORA-65104: operation not allowed on an inactive pluggable database Cause The pluggable database status was UNUSABLE. It was still being created or there was an error during the create operation. A PDB can only be opened if it is successfully created and its status is marked as NEW in cdb_pdbs.status column SQL> select PDB_NAME,STATUS from cdb_pdbs; PDB_NAME             STATUS -------------------- --------------------------- PDB$SEED             NORMAL TEST_CLON            UNUSABLE Solution:  Drop the PDB and create it again. Related Posts How to Clone Oracle PDB (Pluggable Database) with in the Same Container
Post a Comment
Read more

ORA-46630: keystore cannot be created at the specified location

<<Back to DB Administration Main Page ORA-46630: keystore cannot be created at the specified location CDB011> ADMINISTER KEY MANAGEMENT CREATE KEYSTORE '+DATAC4/CDB01/wallet/' IDENTIFIED BY "xxxxxxx"; ADMINISTER KEY MANAGEMENT CREATE KEYSTORE '+DATAC4/CDB01/wallet/' IDENTIFIED BY "EncTest123" * ERROR at line 1: ORA-46630: keystore cannot be created at the specified location Cause  Creating a keystore at a location where there is already a keystore exists Solution To solve the problem, use a different location to create a keystore (use ENCRYPTION_WALLET_LOCATION in sqlnet.ora file to specify the keystore location), or move this ewallet.p12 file to some other location. Note: Oracle does not recommend deleting keystore file (ewallet.p12) that belongs to a database. If you have multiple keystores, you can choose to merge them rather than deleting either of them.
Post a Comment
Read more

Starting RMAN and connecting to Database

  <<Back to Oracle Backup & Recovery Main Page Starting RMAN and connecting to Database Starting RMAN and connecting to Database To start RMAN you need to set the environment and type rman and press enter. You can connect to database either using connect command or using command line option. using command line option localhost:$ export ORACLE_HOME=/ora_app/product/18c/dbd2 localhost:$ export PATH=$ORACLE_HOME/bin:$PATH localhost:$ export ORACLE_SID=ORCL1P localhost:$ rman target / Recovery Manager: Release 18.0.0.0.0 - Production on Sun Apr 4 08:11:01 2021 Version 18.11.0.0.0 Copyright (c) 1982, 2018, Oracle and/or its affiliates.  All rights reserved. connected to target database: ORCL1P (DBID=4215484517) RMAN> using connect option localhost:$ rman RMAN> connect target sys@ORCL1P  target database Password:******** connected to target database: ORCL1P (DBID=4215484517) NOTE: To use connect command you need to ensure that  you have proper TNS sentry for database (ORCL
Post a Comment
Read more

How to Attach to a Datapump Job and Check Status of Export or Import

<<Back to Oracle DATAPUMP Main Page How to check the progress of  export or import Jobs You can attach to the export/import  job using ATTACH parameter of oracle datapump utility. Once you are attached to the job you check its status by typing STATUS command. Let us see how Step1>  Find the Export/Import Job Name You can find the datapump job information from  DBA_DATAPUMP_JOBS or  USER_DATAPUMP_JOBS view. SQL> SELECT OWNER_NAME,JOB_NAME,OPERATION,JOB_MODE,STATE from DBA_DATAPUMP_JOBS; OWNER_NAME JOB_NAME                       OPERATION            JOB_MODE   STATE ---------- ------------------------------ -------------------- ---------- ---------- SYSTEM     SYS_EXPORT_FULL_02             EXPORT               FULL       EXECUTING OR You can also find the job name for export/import in logfile in beginning itself. Step2>Attach to the Job and check status One you get the Export/Import Job Name attach the job and check its status. You can attach or det
7 comments
Read more

ORA-15040: diskgroup is incomplete

<<Back to Oracle ASM Main Page ORA-15040: diskgroup is incomplete SQL> startup ORA-00099: warning: no parameter file specified for ASM instance ASM instance started Total System Global Area 1140850688 bytes Fixed Size                  8629704 bytes Variable Size            1107055160 bytes ASM Cache                  25165824 bytes ORA-15110: no diskgroups mounted Reason: The reason of this error is simply the ASM is not able to find the some or all the disks. Solution: Investigate and make all the disks available to ASM to mount the disk group. Make sure the disks has proper permissions. If you are using AFD check following services are online oracleacfs oracleadvm oracleoks  oracleafd   Source of Problem : Issue started after restart of the server After restarting the server when I tried to start the ASM instance its started throwing error.  ORA-15110: no diskgroups mounted Investigation in my Case Step1> ASM Logfile Scanning  Looked i
2 comments
Read more