Inconsistent password files. See pwconv(1M).

i am trying to install an application on sun machine with solaris 9.
i recieve following error message.
sog group exist ...
sogadm user not exist create...
UX: /usr/sbin/useradd: ERROR: Inconsistent password files. See pwconv(1M).
pkgadd: ERROR: preinstall script did not complete successfully

Do as it says and check the man page for pwconv
Run the command (once you've read the man page and understood what it does) and it will fix the problems with the file

Similar Messages

Inconsistent password file in solaris

hi,
Iam using solaris 5.10 and installing oracle 10g database.
I have created groups. and when i am adding oracle user with following command:
useradd -g oinstall -G dba -d /export/home/oracle oracle
-it returns
man pages section 1M: System Administration Commands: passmgmt(1M)
error.
plz reply me urgent.
-Yuvraj

Check for inconsistent entries in /etc/passwd and /etc/shadow.
http://sysadmintalk.com/showthread.php?threadid=1218
Werner

Question about Password file

Good afternoon,
In the 2 Day DBA document it states:
>
When you invoke DBCA as part of the Oracle Database installation process, DBCA
creates a password file with one entry: the SYS user.
>
I created the database using DBCA and, it must have created a password file for me since I am able to log in remotely to the database.
The question is: I cannot locate the password file DBCA created, I don't know what its name is. Can someone provide me with the name DBCA uses for the password file ?
Thank you very much for helping,
John.

Hello SB,
>
post proof
>
I don't know if this qualifies as "proof" but... from the 2 Day DBA document distributed by Oracle, page 6-9:
>
When you invoke DBCA as part of the Oracle Database installation process, DBCA
creates a password file with one entry: the SYS user. Granting SYSDBA to a user adds
that user to the password file automatically.
>
I have no reason to doubt that statement. ;)
>
for some/many/most Oracle versions which you decided we did not need to know yours the file resides in
$ORACLE_HOME/dbs
>
I didn't decide you didn't need to know. I forgot to mention I am using Windows. As far as the Oracle version, since I used to constantly forget, I made the version part of my user name 11gR2, I can see how that can be easily overlooked.
Thank you for your help,
John.

Data Services (BODI) password file synchronization by external application

Hello,
Question: Is there any batch/shell process that update the BODS password file?
Issue: An external system (P-Synch) change the developper repository passwords every 60 days. The passwords have to be changed manually on the BODS server or account get locked.
Objective: Automation of BODI password syncrhonization (reset) on the server.
My dream: application_cmd -Repsoitory -Account -Password
Thank you,

There's not a good option for that.
In the past, there was ABC Amber IPD converter which could extract or convert data from backup files to CSV or text files, but ABC is no longer available and I don't know of another IPD file extractor.
I don't know of another option. Let's see if someone else might.
1. If any post helps you please click the below the post(s) that helped you.
2. Please resolve your thread by marking the post "Solution?" which solved it for you!
3. Install free BlackBerry Protect today for backups of contacts and data.
4. Guide to Unlocking your BlackBerry & Unlock Codes
Join our BBM Channels (Beta)
BlackBerry Support Forums Channel
PIN: C0001B7B4 Display/Scan Bar Code
Knowledge Base Updates
PIN: C0005A9AA Display/Scan Bar Code

Password file name in Unix

Hi,
on 10g R2 , on AIX 6.1
is the password file name format important ? What is it ?
Is the following a correct format :
orapwdMYDB
It is said in documents :
For name and location information for the Unix and Linux operating systems, see Administrator's Reference for UNIX-Based Operating Systems.
But I can not find Administrator's Reference for UNIX-Based.
Thanks.

user522961 wrote:
Thanks to all.
echo $ORACLE_HOME/appli/oracle/product/10.2.0/db_1
ls -ltr $ORACLE_HOME/dbs-rw-r----- 1 oracle dba 3072 Dec 15 16:00 orapwdMYDB_old
-rwx------ 1 oracle dba 1263 Dec 16 10:44 initMYDB.ora
-rwx------ 1 oracle dba 1263 Dec 16 14:18 initMYDB.ora
-rw-rw---- 1 oracle dba 24 Dec 16 14:58 lkMYDB
-rw-r----- 1 oracle dba 3072 Jan 17 13:20 orapwMYDB
-rw-rw---- 1 oracle dba 1544 Jan 17 15:00 hc_MYDB.dat
-rw------- 1 oracle dba 3584 Jan 17 15:21 spfileMYDB.ora
env | grep ORACLE
ORACLE_SID=MYDB
ORACLE_HOME=/appli/oracle/product/10.2.0/db_1
And I have no sqlnet.ora !!!!!!!!!!Also post there from sqlplus SHOW PARAMETER REMOTE_LOGIN_PASSWORDFILE

Password file - internal user

hi all,
when we create password file. then internal user is also created along with sys in oracle 9i. as we know that internal has been depricated since 9i.
SQL> select * from v$pwfile_users;
USERNAME SYSDB SYSOP
INTERNAL TRUE TRUE
SYS TRUE TRUE
regards
wire.

Please see
REP-0004 Warning - Unable to Open User Preference File. (Doc ID 26014.1)
ApPsMaStI
sharing is Caring

Password file locked??

Hi,
We have a reporting database on Oracle 10.2.0.4 (AIX 5.3) from which we want to create a DG physical standby.
The process fails because of a "possible" locked password file.
I have sorted things out, and it turns out that even on UNIX, when copying the file it says:
$ cp orapwREPPRD /tmp
cp: orapwREPPRD: A system call received a parameter that is not valid.Has anybody seen this behaviour. Can it be that the database holds an exclusive lock on the file, making it impossible for the OS to read/copy the file
The file's function looks OK. It gets updated if I grant 'sysdba' to a certain user.
However another database on the same server doesn't show this behaviour, so it could be the password file somehow got corrupted
The initfile says
SQL> show parameter remote_login_passwordfile
NAME TYPE VALUE
remote_login_passwordfile string EXCLUSIVE
SQL> Can I (simply) recreate the password file while the database is up and running?
Any hints are appreciated
Thanks

Password file is used when the first time connection is requested using it. So its not going to impact your current db if you are going to remove it. See here,
SQL> select * from V$version;
BANNER
Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Prod
PL/SQL Release 10.2.0.1.0 - Production
CORE 10.2.0.1.0 Production
TNS for Linux: Version 10.2.0.1.0 - Production
NLSRTL Version 10.2.0.1.0 - Production
SQL> select status from V$instance;
STATUS
OPEN
SQL> exit
Disconnected from Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Production
With the Partitioning, OLAP and Data Mining options
-bash-3.00$ cd $ORACLE_HOME
-bash-3.00$ cd dbs/
-bash-3.00$ ls
hc_orcl.dat initdw.ora initorcl.ora lkPROD orapwprod spfileprod.ora
hc_prod.dat init.ora lkORCL orapworcl spfileorcl.ora
-bash-3.00$ rm orapworcl
-bash-3.00$ ls
hc_orcl.dat hc_prod.dat initdw.ora init.ora initorcl.ora lkORCL lkPROD orapwprod spfileorcl.ora spfileprod.ora
-bash-3.00$ sqlplus / as sysdba
SQL*Plus: Release 10.2.0.1.0 - Production on Thu Aug 13 15:53:11 2009
Copyright (c) 1982, 2005, Oracle. All rights reserved.
Connected to:
Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Production
With the Partitioning, OLAP and Data Mining options
SQL> select status from V$instance;
STATUS
OPEN
SQL>
So if you are going to change the password file also, it won't impact the current db.
HTH
Aman....

Connecting to remote database (idle) with Password File Authentication

Hi all,
I was wondering if it's possible to connect to a remote database that is shut down (idle instance) as sys user with sysdba privileges? In the book Oracle - All in One on page 210 in the section - Operating System and Password File Authentication it says:
Connection with operating system or password file authentication is always possible, no matter what state the instance and database are in, and is necessary to issue STARTUP or SHUTDOWN commands.
Above indicates that it's possible but I'm unable to do so.
I managed to connect to remote database that was in nomount mode (see below for details).
When I first tried to connect to a remote database (idle instance) using password file authentication it was giving following error:
sqlplus sys@ORCL as sysdbaSQL*Plus: Release 11.2.0.3.0 Production on Fri Dec 21 13:59:28 2012
Copyright (c) 1982, 2011, Oracle. All rights reserved.
Enter password:
ERROR:
ORA-12514: TNS:listener does not currently know of service requested in connect
descriptor
Enter user-name:
After starting the database to nomount mode I was getting following error:
sqlplus sys@ORCL as sysdbaSQL*Plus: Release 11.2.0.3.0 Production on Fri Dec 21 13:48:36 2012
Copyright (c) 1982, 2011, Oracle. All rights reserved.
Enter password:
ERROR:
ORA-12528: TNS:listener: all appropriate instances are blocking new connections
Enter user-name:
So I added the clause (UR=A) to my listener.ora file and after that it work and I was able to connect:
sqlplus sys@ORCL as sysdbaSQL*Plus: Release 11.2.0.3.0 Production on Fri Dec 21 14:04:49 2012
Copyright (c) 1982, 2011, Oracle. All rights reserved.
Enter password:
Connected to:
Oracle Database 11g Enterprise Edition Release 11.2.0.2.0 - Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
SQL>
I have all necessairly entries in tnsnames.ora on my local host.
Also I have no problems when connecting as sys user with sysdba when the DB is open but can't get it work on an idle instance.
I know that I can use operating system authentication but want to know if there is a mistake in the book or I'm doing something wrong.
Regards,
Dawid
Edited by: 978239 on 2012-12-21 06:24

978239 wrote:
Hi all,
I was wondering if it's possible to connect to a remote database that is shut down (idle instance) as sys user with sysdba privileges? In the book Oracle - All in One on page 210 in the section - Operating System and Password File Authentication it says:
Connection with operating system or password file authentication is always possible, no matter what state the instance and database are in, and is necessary to issue STARTUP or SHUTDOWN commands.
Above indicates that it's possible but I'm unable to do so.
I managed to connect to remote database that was in nomount mode (see below for details).
When I first tried to connect to a remote database (idle instance) using password file authentication it was giving following error:
sqlplus sys@ORCL as sysdbaSQL*Plus: Release 11.2.0.3.0 Production on Fri Dec 21 13:59:28 2012
Copyright (c) 1982, 2011, Oracle. All rights reserved.
Enter password:
ERROR:
ORA-12514: TNS:listener does not currently know of service requested in connect
descriptorSince the database is down, the only way the listener is going to know of it is if you create a static registration by adding an entry for the db in the SID_LIST section of listener.ora
>
Enter user-name:
After starting the database to nomount mode I was getting following error:
sqlplus sys@ORCL as sysdbaSQL*Plus: Release 11.2.0.3.0 Production on Fri Dec 21 13:48:36 2012
Copyright (c) 1982, 2011, Oracle. All rights reserved.
Enter password:
ERROR:
ORA-12528: TNS:listener: all appropriate instances are blocking new connections
Enter user-name:
So I added the clause (UR=A) to my listener.ora file and after that it work and I was able to connect:
sqlplus sys@ORCL as sysdbaSQL*Plus: Release 11.2.0.3.0 Production on Fri Dec 21 14:04:49 2012
Copyright (c) 1982, 2011, Oracle. All rights reserved.
Enter password:
Connected to:
Oracle Database 11g Enterprise Edition Release 11.2.0.2.0 - Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
SQL>
I have all necessairly entries in tnsnames.ora on my local host.
Also I have no problems when connecting as sys user with sysdba when the DB is open but can't get it work on an idle instance.
I know that I can use operating system authentication but want to know if there is a mistake in the book or I'm doing something wrong.
Regards,
Dawid
Edited by: 978239 on 2012-12-21 06:24

Password file users issue... RAC help please...

Hi guys,
i have a two node rac database installed on my laptop.. 11gr2.
in rac a database will be accessed by more than once instance correct....
here i have two instance myinst1 and myinst2.
here if we add a user in any one of the instances (say myinst1).. using that user account. the user can connect to either the myinst1 and myinst2.... correct....
say now i grant the user i just created with the SYSDBA and SYSOPER privileges.. (user created on myinst1).
now i can connect to both of the instance using the following syntax as a sysdba..
connect user/password@servicename as sysdba
now here comes the best part..
oracle states that once the user is given either the sysdba or sysoper it will be updated in the password file...
now as i have created the user in the myinst1 instance and granted the privileges there... the password file at the node myinst1 shows the details of the user in the V$PWFILE_USERS views. where as the other instance myinst2 V$PWFILE_USERS does nt have the user...
can any one tell me why is this happening... do i have to explictly grant the SYSDBA privilege on all the instances once if i want to grant a user with the sysdba or sysoper privilege...

Surely there is more than this? I have always believed that the only valid configuration of a Password File in RAC is for a single file to be shared by all instances - by putting it on a shared file system or multipathed raw volume (like the database files), with a Unix symbolic link or init.ora SPFILE reference on each node. I have seen documentation that people have stored a database password file in ASM (SPFILE=+XYZ...) and even on NFS and CIFS.
SYSDBA and SYSOPER access uses the password file of course and it is effectively part of the database, and to me it seems reasonable to expect that an instance will only update the one Password File it knows aboutwhen SYSDBA/OPER access is added, removed or changed; so the consequences of having multiple copies for a single database may be expected to be bad. It was noted here that granting SYSDBA privilege on one node leads to inconsistency in that account's privileges across nodes. Maybe worse is that removing SYSDBA access from one node could leave SYSDBA access to other nodes/instances in place, in clusters where there are multiple local password files... this can be viewed as a very serious security defect, which one of our DBAs has demonstrated.
Now I have learned that Oracle's documentation does not actually give much advice about the configuration of Password Files for RAC; that while some people have done what I expected for years, some product guides suggest on the contrary that local copies should be created on each node; and even that Oracle may not support a single Password File on a shared device. Having Googled the web and scanned this forum quickly, I haven't found a resolution. I am stunned.
I am sure that, of all people, the RAC SIG will be able to advise on this authoritatively, so please do so. If it turns out that Oracle does not recommend or support the use of a single shared file (*),then I suggest there is a significant issue.
(*) Just to be clear, I am not refering to a SHARED password file, but to an EXCLUSIVE one that is on a shared storage volume accessed by every instance of the same RAC database. How Oracle behaves with a SHARED parameter setting may be another issue.

Password file for MQ - Encrypted

Hi,
I wish to use a passwordfile for my implementation of Java MQ, but do not want to have it stored in plain text.I use imqcmd as part of my deployment process and do no want to be prompted for passwords as it is automated.
Is there any way in which to encrypt the password file for imqcmd commands?
Thanks,
Anthonie

The source code for IMQ and J233 is available to download.
You can then customize the code to do whatever you want (i.e. read in a password in some encrypted format using an algorithm of your choice and then unencrypting it before passing it on).
You can easily do this for the KEYSTORE / TRUSTSTORE password files by writing your own Java security provider.
Here are the steps for that:
*1. Write a custom java security provider.*
public class YOUR_PROVIDER_Provider extends java.security.Provider
your code here ...
public class YOUR_PROVIDER_Provider extends Provider
public YOUR_PROVIDER_Provider()
super("YOUR_PROVIDER_Provider", 1.0, "A Custom Security provider");
String className = YOUR_PROVIDER_Provider.class.getName();
put("KeyStore.JKS", className);
2. then,
Need an entry in the java.security file like this:
security.provider.1=YOUR_PROVIDER_Provider
The above order MUST be 1 in order to override the Sun default security provider
* @see java.security java.security file located in: {$JRE_HOME}\lib\security\
*3. write your own JavaKeyStore* (you can download Sun's java source code to use as a baseline.
I would recommend using this one:
sun.security.provider.JavaKeyStore
If you change the package name to a custom one, you will need this (due to "package protect" accessor of this class)
sun.security.provider.KeyProtector
In this class:
sun.security.provider.JavaKeyStore
Modify these methods:
public Key engineGetKey(String alias, char[] password)
throws NoSuchAlgorithmException, UnrecoverableKeyException{
// ... your code
public void engineSetKeyEntry(String alias, Key key, char[] password,
Certificate[] chain)
throws KeyStoreException{
// ... your code
public void engineStore(OutputStream stream, char[] password)
throws IOException, NoSuchAlgorithmException, CertificateException
// ... your code
public void engineLoad(InputStream stream, char[] password)
throws IOException, NoSuchAlgorithmException, CertificateException
// ... your code
4. put your custom files inside a .jar file and put this in the java classpath AHEAD of the standard java ones:
e.g.
java -Xbootclasspath/p:YOUR_JAR.jar
you will have to do this inside the IMQ startup script
alternatively you can simply edit the imqbrokerd.conf file to something like this:
ARGS=-vmargs -Xbootclasspath/p:YOUR_JAR.jar:
this file is in: IMQ_HOME/etc/mq/

Apache password file

I am serving some sites from my iMac G5 running Leopard (not Server). I want to establish a password file to restrict access to one of my virtual hosts. I had accomplished this under previous versions of Mac OS X but somehow the same actions don't work under Leopard. When I run htpasswd under terminal trying to establish a password file at
/usr/local/apache/passwd/passwords
or at
/private/etc/apache2/passwd/passwords
I get "cannot create" so and so
I think my problem is that I don't actually know where or which version of apache is running (it would be the default version for Leopard since I haven't done anything fancy to make it something else).
Can anybody help me see what I am doing wrong?
Thanks

The default is /private/etc/apache2/
Did you sudo htpasswd? Did you create your password directory first?

How to change the default password file's name and path when the database created?

how to change the default password file's name and path when the database created?
null

Usage: orapwd file=<fname> password=<password> entries=<users>
where
file - name of password file (mand),
password - password for SYS and INTERNAL (mand),
entries - maximum number of distinct DBA and OPERs (opt),
There are no spaces around the equal-to (=) character.

How to change default location of password file ?

Hi all,
Can i change the location of my password file from default to any other user defined location ?
If yes then how ?
Thanx in advance.
Deep

Dad you moved here?
Can i change the location of my password file ?

How do i find the location of Oracle password file in the HDD

we giv the location of the password file while we use the orapwd command to create one.
later if we forget the location of the password file (incase it is not at the default location) then is there a way to find it or do we just create a new password file?
secondly, for oracle to use the password file we giv the remote_login_passwordfile='EXCLUSIVE' in the parameter file. wat tells oracle the location of the exact password file??
Thanks
Arvind
Edited by: iinfi on Sep 29, 2008 12:15 AM

The default location are OS dependant.
On Unix/Linus it is under $ORACLE_HOME/dbs
On Windows, it is under %ORACLE_HOME%/database
To change the default location, nothing inside database, but :
On Unix/Linux, you have to create a symbolic link for that file to the target location
On Windows, you have to change env variable (regedit) ORA_PWFILE and ORA_SID_PWFILE
So, you have to check this setting for the real password file location.
Nicolas.

Configuring password file in oracle 10g

Hi
Can anyone here guide me to the steps to be followed in configuring password file.
I am learning cloning using RMAN. For that purpose I need to configure password file at first.
I created the password file using orapwd utility.
and then made the required changes in tnsnames.ora and listener.ora files. Reloaded listener.
Set SQLNET.AUTHENTICATION_SERVICES = (NONE) in the sqlnet.ora file
Made the changes required in the initialization parameter file for the duplicate database instance.
Next, export ORACLE_SID= <DUPLICATE DATABASE NAME>
CREATE SPFILE FROM PFILE
STARTUP FORCE NOMOUNT;
rman TARGET sys/password@target-tnsname AUXILIARY sys/password@duplicate-tnsname
At this stage, I get the below error.
RMAN-00554 initialization of internal recovery manager package failed
RMAN- 04006 error from auxiliary database: ORA- 01031 : Insufficient privileges

userark160 wrote:
rman TARGET sys/password@target-tnsname AUXILIARY sys/password@duplicate-tnsname
At this stage, I get the below error.
RMAN-00554 initialization of internal recovery manager package failed
RMAN- 04006 error from auxiliary database: ORA- 01031 : Insufficient privileges
Are the Auxiliary and Target databases on the same machine?
Can you also check the parameter Local_Listener for Auxiliary Database?
Regards,
Z.K.

Inconsistent password files. See pwconv(1M).

Similar Messages

Maybe you are looking for