ORA-23325: parameter type is not string

Cause : A conflict resolution priority function was given a type different than the type assigned to the priority group; or the priority group has no type assigned or a function; or dbms_defer_sys_query was called to retrieve a deferred rpc parameter from the deferred rpc queue, but the type of the parameter does not match the return type of the function.

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

Use the function corresponding to the parameter type.

update : 21-07-2017

ORA-23325 - parameter type is not string
ORA-23325 - parameter type is not string

  • ora-24307 : invalid length for piece
  • ora-19643 : datafile string: incremental-start SCN is too recent
  • ora-23314 : database is not a materialized view site for "string"."string"
  • ora-28277 : LDAP search, while authenticating global user with passwords, failed.
  • ora-14175 : a subpartition maintenance operation may not be combined with other operations
  • ora-31629 : unable to allocate additional memory
  • ora-01515 : error dropping log group string: no such log
  • ora-07411 : slgfn: full path name too big for supplied buffer.
  • ora-00110 : invalid value string for attribute string, must be between string and string
  • ora-25184 : column name expected
  • ora-40225 : model is currently in use by another process
  • ora-13767 : End snapshot ID must be greater than or equal to begin snapsho ID.
  • ora-10580 : Can not modify datafile header during test recovery
  • ora-12058 : materialized view cannot use prebuilt table
  • ora-13415 : invalid or out of scope point specification
  • ora-30506 : system triggers cannot be based on tables or views
  • ora-31493 : could not prepare session for LogMiner session
  • ora-39960 : scope can only be SYSTEM or SESSION
  • ora-01351 : tablespace given for Logminer dictionary does not exist
  • ora-37039 : (XSMLTDCL05) You cannot maintain triggers in analytic workspace string because it is attached in MULTI mode.
  • ora-19759 : block change tracking is not enabled
  • ora-24396 : invalid attribute set in server handle
  • ora-08112 : a composite partition may not be coalesced as a whole
  • ora-12043 : invalid CREATE MATERIALIZED VIEW option
  • ora-19608 : %s is not a backup piece
  • ora-19924 : there are no row with id string
  • ora-21705 : service context is invalid
  • ora-08109 : nosort is not a supported option for online index build
  • ora-02165 : invalid option for CREATE DATABASE
  • ora-04068 : existing state of packagesstringstringstring has been discarded
  • 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.