Database Install/Upgrade/Opatch (MOSC)

MOSC Banner

Regarding hidden parameter "_enable_ptime_update_for_sys" and SYS user expiry_date

in Database Install/Upgrade/Opatch (MOSC) 9 commentsAnswered ✓

I upgraded a 12.2 database running on RHEL 7.9 to 19c (19.3 specifically and the db has since been patched through 19.14). I used DBUA to do so.

While running the 12.2 database we were using the hidden parameter to "fix" the issue with the SYS user expiry_date (per MOS 28538439.1)

However, per the preupgrade information tool ($ORACLE_HOME/rdbms/admin/preupgrade.jar) it was advised to remove hidden parameters prior to upgrading. In my specific case, the tool identified 4 parameters of which "_enable_ptime_update_for_sys" was one.

Now that I have removed this parameter, the issue with the SYS user expiry_date has returned. Can anyone advise? All MOS searches I've done to date always lead me back this parameter. Also, I found no indication in the "post upgrade" items this parameter should be reinstated.

Howdy, Stranger!

Log In

To view full details, sign in to My Oracle Support Community.

Register

Don't have a My Oracle Support Community account? Click here to get started.

Category Leaderboard

Top contributors this month

Instructions for posting

×

1. Select a discussion category from the picklist.


2. Enter a title that clearly identifies the subject of your question.


3. In the body, insert detailed information, including Oracle product and version.


Please abide by the Oracle Community guidelines and refrain from posting any customer or personally identifiable information (PI/CI).


Cloud / Fusion customers - Our Cloud community has moved! Please go to Cloud Customer Connect .


New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center