Ok, I solved the problem. It was a tablespace issue:
ORA-1652: unable to extend temp segment by 128 in tablespace MGMT_ECM_DEPOT_TS
Why that shows up as an invalid user or password is beyond me.
Scott Canaan ‘88
Sr Database Administrator
Information & Technology Services
Finance & Administration
Rochester Institute of Technology
o: (585) 475-7886 | f: (585) 475-7520
srcdco@xxxxxxx<mailto:srcdco@xxxxxxx> | c: (585) 339-8659
CONFIDENTIALITY NOTE: The information transmitted, including attachments, is
intended only for the person(s) or entity to which it is addressed and may
contain confidential and/or privileged material. Any review, retransmission,
dissemination or other use of, or taking of any action in reliance upon this
information by persons or entities other than the intended recipient is
prohibited. If you received this in error, please contact the sender and
destroy any copies of this information.
From: oracle-l-bounce@xxxxxxxxxxxxx <oracle-l-bounce@xxxxxxxxxxxxx> On Behalf
Of Rich J
Sent: Thursday, July 30, 2020 8:41 PM
To: oracle-l@xxxxxxxxxxxxx
Subject: Re: Cloud Control Issue
In case the patch rebuilt roles, I'm thinking it's possible one or more of them
did not get reapplied to your database account. You could still login to the
database, but would not have the proper roles in the repository DB for logging
into EM13. You'll need at least MGMT_USER, I think. Easiest way to determine
that is to create another admin and compare that account to yours.
My $.02,
Rich
On Thu, Jul 30, 2020 at 4:13 PM Mladen Gogala
<gogala.mladen@xxxxxxxxx<mailto:gogala.mladen@xxxxxxxxx>> wrote:
Hi Scott,
Yes, I am talking about the database password file. I believe you should
recreate it without the "format" option. As for the question why, I can only
guess, just like you. New feature perhaps?
Regards
On 7/30/20 5:02 PM, Scott Canaan wrote:
I’m assuming you are talking about the database password file. If so, then it
was created using format=12, because it was 12c at the time. Should I
recreate it with a different format? Why would it have worked yesterday before
I patched and not now?
Scott Canaan ‘88
Sr Database Administrator
Information & Technology Services
Finance & Administration
Rochester Institute of Technology
o: (585) 475-7886 | f: (585) 475-7520
srcdco@xxxxxxx<mailto:srcdco@xxxxxxx> | c: (585) 339-8659
CONFIDENTIALITY NOTE: The information transmitted, including attachments, is
intended only for the person(s) or entity to which it is addressed and may
contain confidential and/or privileged material. Any review, retransmission,
dissemination or other use of, or taking of any action in reliance upon this
information by persons or entities other than the intended recipient is
prohibited. If you received this in error, please contact the sender and
destroy any copies of this information.
From: oracle-l-bounce@xxxxxxxxxxxxx<mailto:oracle-l-bounce@xxxxxxxxxxxxx>
<oracle-l-bounce@xxxxxxxxxxxxx><mailto:oracle-l-bounce@xxxxxxxxxxxxx> On Behalf
Of Mladen Gogala
Sent: Thursday, July 30, 2020 4:53 PM
To: oracle-l@xxxxxxxxxxxxx<mailto:oracle-l@xxxxxxxxxxxxx>
Subject: Re: Cloud Control Issue
I have had a similar problem with a client. I was able to log in using sqlplus
but unable to log in using dgmgrl. The problem was the password file format.
Client has specified 12c format, which doesn't enforce the security rules and
that was fine for SQL*Plus but not fine for dgmgrl. Your description leads me
to the conclusion that this is the same problem. However, the database that I
was working with was 19.7, not 19.8. I am unable to reproduce this with 19.8.
Regards
On 7/30/20 4:42 PM, Scott Canaan wrote:
Yesterday, I applied the July PSU to the database behind Cloud Control. Now, I
can’t log in via Cloud Control. I try to log in and I get the message saying
that the user or password is invalid. But I can log into the database via
SQL*Plus with the user / password. How do I fix this?
DB version = 19.8
CC version = 13.3
Scott Canaan ‘88
Sr Database Administrator
Information & Technology Services
Finance & Administration
Rochester Institute of Technology
o: (585) 475-7886 | f: (585) 475-7520
srcdco@xxxxxxx<mailto:srcdco@xxxxxxx> | c: (585) 339-8659
CONFIDENTIALITY NOTE: The information transmitted, including attachments, is
intended only for the person(s) or entity to which it is addressed and may
contain confidential and/or privileged material. Any review, retransmission,
dissemination or other use of, or taking of any action in reliance upon this
information by persons or entities other than the intended recipient is
prohibited. If you received this in error, please contact the sender and
destroy any copies of this information.
--
Mladen Gogala
Database Consultant
Tel: (347) 321-1217
--
Mladen Gogala
Database Consultant
Tel: (347) 321-1217
