mhartung
asked on
Password grace period no longer generates ORA-28002
I am using Oracle Forms 9i, accessing an Oracle 10g database via an Oracle 10g application server. Since our client-server days, our logon form has checked dbms_error_code immediately after the logon statement (NOT in an on-error trigger), looking for -28002, in order to warn the user that he is in the password grace period. Apparently, this error is no longer getting trapped (don't know when that started), so our help desk is flooded with password reset requests. Is there some other message number that I should be looking for? We use the default message level in our forms, so I would think that warnings should show up as well as bona-fide errors.
Thanks.
Thanks.
jrb1
Can you look for MESSAGE_CODE of ORA-28002?
ASKER
I will give it a try. It will probably take me a day or so to get a dba to set an expiry date for me, so don't think that I am ignoring you if I don't reply for a couple of days. Thanks.
ASKER
I'm back. That didn't work. I put in some displays, and both dbms_error_code and message_code were zero. I thought that maybe it started with our upgrade to 10g, but when I pointed the form back to our 8.1.7.4 database, I got the same non-result. Even connecting through SQL Plus no longer generates the message. As a last resort, I can modify the form to check user_users and decide when the expiry date is close, but I'd really like to know what happened to ORA-28002...
Just wondering...what does this return?
select limit
from dba_profiles
where resource_name = 'PASSWORD_GRACE_TIME';
select limit
from dba_profiles
where resource_name = 'PASSWORD_GRACE_TIME';
ASKER
The limit is 3 for the profile that is assigned to my test user. The expiry date for that user is April 15th (in the morning), so I was hoping that ORA-28002 would be generated when I connected today. No such luck, though. I was wading through MetaLink, and read that being in the grace period throws a warning, rather than an error (no where did a different number get mentioned, though), but I can't seem to get anything thrown at all.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
You are right -- I was confused on the grace period. When the dba set the expiry date to yesterday and I connected today, I got the ORA-28002 message (in BOTH the 8i and 10g databases), and then the system set the expiry date to 3 days from today. Then, to my great surprise, I also got a value in dbms_error_code in the form in both environments. So it looks like my Production problem is a non-issue, resulting from the profiles getting reset to the defaults (unlimited) when the database was upgraded to 10g. What a waste of time. Thank you for your patience and persistence. I'm going to close this, but I wanted to give you an explanation first.