Not using ASM or clusterware. We figured it out. We were provided a custom
cloning script by our senior development dba. She appended ".ora" to the
password file and although it was created it didn't work. We proved that when
I had one of the other DBA's grant himself sysdba. When he tried to log in he
got an error, "The password file is missing or disabled." We deleted it and
recreated it without the extension and it works fine. It's one of those that
you know before you start that there is some kind of mistake at work :D. One
of the responders here, Vishnu, provided the answer that the password file
shouldn't have an extension.
" Does your password file ends with .ora or some other extension? If so, create
password file without any .xxx names .(it needs to be simply dbname like
orapwdbname and not orapwddbname.ora or some others)"
Thank you Vishnu!
R/
Donald Freeman
Systems Dev Spec, Principle
ManTech International
-----Original Message-----
From: samuel guiñales cristobal [mailto:samuelg.cristobal@xxxxxxxxx] ;
Sent: Saturday, April 29, 2017 5:25 AM
To: Binh.Le@xxxxxxx
Cc: Freeman, Donald G. CTR; oracle-l-freelists
Subject: [Non-DoD Source] Re: Created new 12C Release 2 databases SYS@db as
sysdba doesn't work
Hi Donald,
Do you using clusterware/asm,? maybe orapw file on asm? check what is using
your database:
crsctl stat res ora.[daatbase_name].db -f | grep PWFILE
1) recreate orapwsd in asm and you don't need to copy file to other nodes:
orapwd asm=y file='+[diskgroup]' password='[password]'
2) enter CDB and: alter user sys identified by [password]
---
Samuel Guiñales Cristobal <samuelg.cristobal@xxxxxxxxx> «Que tu alimento sea tu
medicina, y la medicina tu alimento.» Hipócrates
On 28 April 2017 at 22:01, Le, Binh T. <Binh.Le@xxxxxxx> wrote:
Password file only need for remote connect to the database as sysdba
sqlplus sys/passwordHere@yourdatabase as sysdba
You can try to recreate the password file:
orapwd file=$ORACLE_HOME/dbs/orapwYourdatabase entries=5 force=y
If you not specify which instance you try to connect to (RAC) then
remember create password file the same at ALL nodes (or copy to other node)
Good luck.
-----Original Message-----
From: oracle-l-bounce@xxxxxxxxxxxxx
[mailto:oracle-l-bounce@xxxxxxxxxxxxx ;<mailto:oracle-l-bounce@xxxxxxxxxxxxx> ]
On Behalf Of Freeman, Donald G. CTR
Sent: Friday, April 28, 2017 2:36 PM
To: oracle-l-freelists <oracle-l@xxxxxxxxxxxxx>
Subject: Created new 12C Release 2 databases SYS@db as sysdba doesn't
work
We manually created or migrated existing databases in these new
environments
on Solaris 11 and upgraded them to 12C. We cannot get the sys account
to
work properly. We are getting invalid userid/password. We have a
password
file, and REMOTE_LOGIN_PASSWORDFILE is set to exclusive. We have tried
mixed case, lower case, uppercase. Other accounts other than sys can
connect using userid/password@12cdatabase. sys@12cdatabase as sysdba
does not work. Any ideas? We have a lot of stumped dba's here. We
did
find a note relating that deep packet inspection might cause this. We
do
have a ticket in but haven't heard anything back. We're on a very tight
deadline to get all these systems working.
Donald Freeman
Systems Dev Spec, Principle
ManTech International
Notice of Confidentiality: **This E-mail and any of its attachments may
contain
Lincoln National Corporation proprietary information, which is
privileged, confidential,
or subject to copyright belonging to the Lincoln National Corporation
family of
companies. This E-mail is intended solely for the use of the individual
or entity to
which it is addressed. If you are not the intended recipient of this
E-mail, you are
hereby notified that any dissemination, distribution, copying, or
action taken in
relation to the contents of and attachments to this E-mail is strictly
prohibited
and may be unlawful. If you have received this E-mail in error, please
notify the
sender immediately and permanently delete the original and any copy of
this E-mail
and any printout. Thank You.**
--
//www.freelists.org/webpage/oracle-l ;
<//www.freelists.org/webpage/oracle-l>
Attachment:
smime.p7s
Description: S/MIME cryptographic signature
