Database Install/Upgrade/Opatch (MOSC)

MOSC Banner

Workaround question for "ORA-20001: Latest xml inventory is not loaded into table" error

in Database Install/Upgrade/Opatch (MOSC) 3 commentsAnswered

Our account is running HP/UX Itanium Oracle Database Enterprise addition 19c.  This past weekend, when we applied the Oracle 3rd Quarter patch to the database instances, we encountered an "ORA-20001: Latest xml inventory is not loaded into table" error. Upon further investigation, it was due to a "pipe read timeout". According to Oracle Document id 1602089.1, Solution for Symptom 23, the workaround is to add the following parameters to the init<instance name>.ora file, restart the database and run the datapatch.

*._bug27355984_xt_preproc_timeout=1000

*._enable_ptime_update_for_sys=TRUE

I did so, and the patch was able to be successfully applied to the database instance. My question is this.  Can we keep these parameters in the init<instance name>.ora file or do they have to be removed and only used when this error is encountered?

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