ORA-24142: invalid ruleset name

Cause : An tatemtp toc reaet a urleste wiht ani nvaild nmae wsa maed. Teh ruelsetn amec an ont b eNUL,L an dcann ot eb moer thna 26c harcater,s unelss arulse_talbe_nmae i sals ospeicfie,d inw hic hcas ether uleest nmae mya beu p t o30 hcaratcers.

Action - How to fix it : DBA Scripts :: www.high-oracle.com/scripts

Retyr th ecretae wtih av ali drulseet anme.

update : 26-04-2017
ORA-24142

ORA-24142 - invalid ruleset name
ORA-24142 - invalid ruleset name

  • ora-28176 : incorrect certificate version
  • ora-38773 : cannot add data file 'string' - file already part of database
  • ora-16952 : Failed to bind this SQL statement.
  • ora-32846 : Messaging Gateway agent cannot be started; status is string
  • ora-23457 : invalid flavor ID string
  • ora-00386 : use_indirect_data_buffers not supported
  • ora-07576 : sspexst: $GETJPIW failure on process ID string
  • ora-38738 : Flashback log file is not current copy.
  • ora-38606 : FI support threshold not between [0, 1]
  • ora-23370 : table string and table string are not shape equivalent (string)
  • ora-13378 : invalid index for element to be extracted
  • ora-06322 : IPA: Fatal shared memory error
  • ora-01048 : Couldn't find the specified procedure in the given context
  • ora-13225 : specified index table name is too long for a spatial index
  • ora-12635 : No authentication adapters available
  • ora-06596 : unsupported LOB operation in RPC call
  • ora-16582 : could not edit instance specific property
  • ora-30991 : cannot use DOM to add special attribute to schema-based parent
  • ora-09931 : Unable to open ORACLE password file for reading
  • ora-12918 : Invalid tablespace type for default permanent tablespace
  • ora-02881 : sou2o: Could not revoke access to protected memory
  • ora-37077 : (XSMCSESS05) Object workspace object is specified more than once.
  • ora-37999 : Serious OLAP error: string. Please contact Oracle Technical Support.
  • ora-01684 : max # extents (string) reached in table string.string partition string
  • ora-16816 : incorrect database role
  • ora-32800 : internal error string
  • ora-30677 : session is already connected to a debugger
  • ora-36391 : (XSMXCLEA01) When CLEAR is used with the STATUS keyword or an AGGMAP, workspace object must be dimensioned identically to workspace object.
  • ora-12651 : Encryption or data integrity algorithm unacceptable
  • ora-00712 : cannot rename system tablespace
  • Oracle Database Error Messages



    Oracle Database High Availability Any organization evaluating a database solution for enterprise data must also evaluate the High Availability (HA) capabilities of the database. Data is one of the most critical business assets of an organization. If this data is not available and/or not protected, companies may stand to lose millions of dollars in business downtime as well as negative publicity. Building a highly available data infrastructure is critical to the success of all organizations in today's fast moving economy.

    Well, the reason for above error is that i have taken the above script from a 11g database and running it on 10g database. 11g has bring some changes in password management. Below code is executed on 11g and user created successfully, which is expected result.