Utlrp.sql results to "Warning: XDB Now Invalid, Could Not Find Xdbconfig"


When trying to recompile invalid objects by running the utlrp.sql script, the below error is thrown:
"XDB now invalid, could not find xdbconfig"
Furthermore, Oracle XML Database (XDB) is INVALID.


ERROR at line 1:
ORA-31024: Parser initialization failed with LPX-201 error
while parsing a stream to XOB
ORA-06512: at "SYS.UTL_RECOMP", line 865
ORA-06512: at line 4



Applying AD and TXK Release Update Packs to Oracle E-Business Suite Release 12.2

The latest RUPs while writing this post are R12.AD.C.Delta.10 (Patch 25820806) and R12.TXK.C.Delta.10 (Patch 25828573).

Apply Required Database Patches

AD-TXK Delta 10 requires a number of database bug fixes to install and operate correctly.
NOTE: Take Central Inventory backups on the database and application tiers.
Before you apply the AD and TXK Delta 10 release update packs (RUPs), you must run the latest version (available via Patch 17537119) of the EBS Technology Codelevel Checker (ETCC). Use the command checkDBpatch.sh (on UNIX) or checkDBpatch.cmd (on Windows).

Check the OPatch utility version.

/u01/oracle/product/dbhome1/OPatch/opatch version
OPatch Version:

OPatch succeeded.

Upgrade to the latest OPatch Utility.

[oracle@ebsdb01 OPatch]$ ./opatch version
OPatch Version:

OPatch succeeded.



REP-0004: Warning: Unable to open user preference file


Concurrent request logfiles have the below error:

REP-0004: Warning: Unable to open user preference file



The prefs.ora is either missing or non-accessible.



1. No prefs.ora file in HOME directory:

Oracle Reports will look into the user's HOME directory for the prefs.ora preferences file.  If a prefs.ora file does not exist in your HOME directory, you can copy the prefs.ora file that came with the Oracle Tools.



Enforcing password complexity for database users

It is recommended to enforce checks and response actions for failed logins, password complexity, password expiration and password reuse.
Password complexity can be implemented through profiles.
The script for password management implementation utlpwdmg.sql can be used to create a new function to verify password complexity rules.
Verify Function is a quick and easy way to enforce quality of database passwords—for example, they should contain a certain number of characters, should not be identical to the username, and so on.
By executing this script utlpwdmg.sql, it will attach the function to the profile DEFAULT, which is the default profile for all users.

The following password complexity is set with the 'utlpwdmg.sql' script.

  • Password length less than 8
  • Password same as or similar to user
  • Password same as username reversed
  • Password same as or similar to server name
  • Password too simple
  • Password must contain at least one digit, one character
  • Password must contain at least one digit, and one character
  • Password should differ from the old password by at least 3 characters
  •

    Back to Top