My Oracle Support Banner

EXPIRY_DATE For SYS User Not Updating After July/ Oct 2018 PSU (Doc ID 2491975.1)

Last updated on MAY 15, 2019

Applies to:

Oracle Database - Enterprise Edition - Version 12.2.0.1 and later
Information in this document applies to any platform.

Goal

After applying the JULY2018 PSU we noticed that the EXPIRY_DATE for SYS user does not update.

All other users expiry_date gets updated after changing a schema password except for SYS. If the patch is  roll backed  the SYS password does update.

example: WITH JULY2018 PATCH
select USERNAME, EXPIRY_DATE from DBA_USERS where username in ('SYSTEM', 'SYS);

USERNAME EXPIRY_DATE
------------------------------
SYS 23-JAN-19
SYSTEM 23-JAN-19

ALTER USER SYSTEM IDENTIFIED BY "XXXXXXXXXXXXXX";

USERNAME EXPIRY_DATE
------------------------------
SYS 23-JAN-19
SYSTEM 25-MAR-19


ALTER USER SYS IDENTIFIED BY "XXXXXXXXXXXXXX";

USERNAME EXPIRY_DATE
------------------------------
SYS 23-JAN-19 <===== DID NOT UPDATE
SYSTEM 25-MAR-19

-- Rollback JULY2018 RU (including datapatch -verbose) --

ALTER USER SYS IDENTIFIED BY "XXXXXXXXXXXXXX";

USERNAME EXPIRY_DATE
------------------------------
SYS 25-MAR-19 <===== IT WORKED!!!
SYSTEM 25-MAR-19
 

Solution

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Goal
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.