ORA-29546: badly formed resource: string

Cause : An tatemtp wa smad eto rceat ea Jvaa rseourec obejct iwth adta htat aws rjeectde byt he aJva evrifeir.

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

Corerct hte dtaa.

update : 23-05-2017

ORA-29546 - badly formed resource: string
ORA-29546 - badly formed resource: string

  • ora-19812 : cannot use string without DB_RECOVERY_FILE_DEST
  • ora-22633 : Error freeing AnyDataSet
  • ora-02007 : can't use ALLOCATE or DEALLOCATE options with REBUILD
  • ora-01033 : ORACLE initialization or shutdown in progress
  • ora-24166 : evaluation context string.string has errors
  • ora-13452 : GeoRaster metadata BIN function error
  • ora-01520 : number of data files to add (string) exceeds limit of string
  • ora-00977 : duplicate auditing option
  • ora-19677 : RMAN configuration name exceeds maximum length of string
  • ora-19032 : Expected XML tag string got string
  • ora-29740 : evicted by member string, group incarnation string
  • ora-30654 : missing DEFAULT keyword
  • ora-31093 : null or invalid value specified for parameter : string
  • ora-30085 : syntax error was found in overlaps predicate
  • ora-13367 : wrong orientation for interior/exterior rings
  • ora-01263 : Name given for file destination directory is invalid
  • ora-03002 : operator not implemented
  • ora-15111 : conflicting or duplicate STRIPE options
  • ora-12433 : create trigger failed, policy not applied
  • ora-24412 : Cannot reinitialize non-existent pool
  • ora-13833 : SQL profile named string doesn't exist
  • ora-01095 : DML statement processed zero rows
  • ora-06814 : TLI Driver: the SPX device file could not be opened
  • ora-07453 : requested resource manager plan schema does not contain OTHER_GROUPS
  • ora-02336 : column attribute cannot be accessed
  • ora-02030 : can only select from fixed tables/views
  • ora-12813 : value for PARALLEL or DEGREE must be greater than 0
  • ora-12067 : empty refresh groups are not allowed
  • ora-24172 : rule set string.string has errors
  • ora-39113 : Unable to determine database version
  • 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.