ORA-27475: "string.string" must be a string

Cause : An object of the wrong type was specified. For example, a table could have been passed to the drop_job() procedure.

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

Reissue a different command applicable to this object type or reissue the same command using an object of the valid type.

update : 24-05-2017

ORA-27475 - "string.string" must be a string
ORA-27475 - "string.string" must be a string

  • ora-29534 : referenced object string.string could not be resolved
  • ora-16597 : Data Guard broker detects two or more primary databases
  • ora-16646 : Fast-Start Failover is disabled
  • ora-19761 : block size string is not valid for change tracking file
  • ora-16154 : suspect attribute: string
  • ora-07848 : sllfrb: $GET failure
  • ora-31664 : unable to construct unique job name when defaulted
  • ora-30352 : inconsistent numeric precision or string length
  • ora-07672 : $PARSE_CLASS failed translating the string into a binary label
  • ora-31232 : DBMS_LDAP: invalid MOD_PROPERTY_SET
  • ora-00317 : file type string in header is not log file
  • ora-22297 : warning: Open LOBs exist at transaction commit time
  • ora-33558 : (LOCKCHECK01) The status or contents of the workspace object dimension cannot be changed while the LOCK_LANGUAGE_DIMS option is set to value.
  • ora-30400 : identical JOIN KEY clauses
  • ora-09840 : soacon: Name translation failure.
  • ora-02371 : Loader must be at least version string.string.string.string.string for direct path
  • ora-23411 : materialized view "string"."string" is not in refresh group "string"."string"
  • ora-01628 : max # extents (string) reached for rollback segment string
  • ora-24904 : invalid callback attribute passed into OCI call
  • ora-12403 : invalid internal label
  • ora-19161 : XP0004 - XQuery type mismatch: invalid argument type 'string' for function 'string'
  • ora-16253 : Logical Standby cannot start due to incomplete terminal apply
  • ora-13603 : The specified parameter string cannot be fetched as a numeric value for task or object string.
  • ora-25954 : missing primary key or unique constraint on dimension
  • ora-16606 : unable to find property "string"
  • ora-30977 : invalid Value Index option for XML Index
  • ora-36223 : (XSLPDSC04) object workspace object in IGNORE or DENSE list has illegal type
  • ora-13033 : Invalid data in the SDO_ELEM_INFO_ARRAY in SDO_GEOMETRY object
  • ora-14452 : attempt to create, alter or drop an index on temporary table already in use
  • ora-01194 : file string needs more recovery to be consistent
  • 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.