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 : 28-06-2017

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

  • ora-28583 : remote references are not permitted during agent callbacks
  • ora-26577 : PRESERVE TABLE can not be used when dropping old style materialized view string.string
  • ora-16074 : ARCH processes must be active
  • ora-01861 : literal does not match format string
  • ora-01059 : parse expected before a bind or execute
  • ora-01092 : ORACLE instance terminated. Disconnection forced
  • ora-19121 : duplicate attribute definition - string
  • ora-10915 : TABLESPACE GROUP cannot be specified for this type of tablespace
  • ora-14281 : CHECK constraint mismatch in ALTER TABLE EXCHANGE SUBPARTITION
  • ora-06596 : unsupported LOB operation in RPC call
  • ora-01167 : two files are the same file/group number or the same file
  • ora-21521 : exceeded maximum number of connections in OCI (object mode only)
  • ora-10270 : Debug shared cursors
  • ora-39706 : schema 'string' not found
  • ora-28030 : Server encountered problems accessing LDAP directory service
  • ora-12201 : TNS:encountered too small a connection buffer
  • ora-19582 : archivelog file header validation for string failed
  • ora-26517 : materialized view control entry for 'string.string' was not found
  • ora-30011 : Error simulated: psite=string, ptype=string
  • ora-08344 : srapp: failed to send redo data to the redo server
  • ora-25401 : can not continue fetches
  • ora-13039 : failed to update spatial index for element string.string.string
  • ora-13118 : invalid node_id [string]
  • ora-07847 : sllfop: $CONNECT failure
  • ora-12452 : label tag string already exists
  • ora-24046 : protocol attribute reserved for future use
  • ora-38490 : invalid name: quotes do not match
  • ora-38472 : VARCHAR representation of the data item is too long.
  • ora-06441 : ssvwatev: Incorrect parameter passed to function call
  • ora-26019 : Column string in table string of type string not supported by direct path
  • 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.