ORA-26045: REF column string expects string arguments; found string.

Cause : The number of arguments for the REF column is incorrect.

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

Specify the correct number of input arguments for REFs. 1. Unscoped system-generated REFs can have exactly 1 or 2 input arguments. a) It has exactly 1 input argument (one for the OID value) if a fixed table name was specified through OCI_DIRPATH_EXPR_REF_TBLNAME. b) It has exactly 2 input arguments (one for the table name and one for the OID value) if a fixed table name was not specified through OCI_DIRPATH_EXPR_REF_TBLNAME. 2. Scoped system-generated REFs can have 1 or 2 input arguments. Because a table name argument is not needed for a scoped ref, only 1 argument (OID value) is expected. But if the table name argument is given, it's still accepted. 3. Scoped primary-key REFs with N columns in its primary-key OID can have N or N+1 input arguments. Because a table name argument is not needed for a scoped ref, only N arguments (making up the OID value) is expected. But if the table name argument is given, it's still accepted.

update : 26-09-2017
ORA-26045

ORA-26045 - REF column string expects string arguments; found string.
ORA-26045 - REF column string expects string arguments; found string.

  • ora-14514 : LOCAL option not valid without subpartition name
  • ora-00287 : specified change number string not found in thread string
  • ora-12170 : TNS:Connect timeout occurred
  • ora-01502 : index 'string.string' or partition of such index is in unusable state
  • ora-39122 : Unprivileged users may not perform string remappings.
  • ora-19952 : database should be mounted exclusively
  • ora-01260 : warning: END BACKUP succeeded but some files found not to be in backup mode
  • ora-29383 : all leaves of top-plan string must be consumer groups
  • ora-24814 : operation not allowed for temporary LOBs
  • ora-00251 : LOG_ARCHIVE_DUPLEX_DEST cannot be the same destination as string string
  • ora-22065 : number to text translation for the given format causes overflow
  • ora-19957 : database should have no datafiles in unknown state
  • ora-07715 : sksadtd: could not dismount archival device (SYS$DISMNT failure)
  • ora-30446 : valid workload queries not found
  • ora-00566 : cannot request processor group - NUMA not enabled
  • ora-32338 : on commit refresh grab all the detailed tables
  • ora-02024 : database link not found
  • ora-01734 : illegal parameters - EXTENT MIN higher than EXTENT MAX
  • ora-32131 : bind data type cannot be changed
  • ora-39214 : Data Pump does not support external tables with encrypted columns. string will not be exported
  • ora-16817 : unsynchronized Fast-Start Failover configuration
  • ora-30066 : test support - drop rollback segment wait
  • ora-16661 : the standby database needs to be reinstated
  • ora-12402 : invalid format string: string
  • ora-24393 : invalid mode for creating connection pool
  • ora-24004 : invalid column name string in SORT_LIST, should be ENQ_TIME or PRIORITY
  • ora-09940 : ORACLE password file header is corrupt
  • ora-29353 : The transportable list is too long.
  • ora-01079 : ORACLE database was not properly created, operation aborted
  • ora-06706 : TLI Driver: service not found
  • 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.