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 : 23-07-2017
ORA-26045

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

  • ora-02004 : security violation
  • ora-19603 : cannot backup or copy active file with KEEP .. UNRECOVERABLE option
  • ora-01310 : requested return type not supported by the lcr_mine function
  • ora-19253 : XQ0033 - too many declarations for namespace prefix string
  • ora-00040 : active time limit exceeded - call aborted
  • ora-01935 : missing user or role name
  • ora-07490 : scgrcl: cannot convert lock.
  • ora-27160 : process requested to perform operation
  • ora-14277 : tables in EXCHANGE SUBPARTITION must have the same number of columns
  • ora-12591 : TNS:event signal failure
  • ora-19953 : database should not be open
  • ora-29958 : fatal error occurred in the execution of ODCIINDEXCREATE routine
  • ora-14054 : invalid ALTER TABLE TRUNCATE PARTITION option
  • ora-30195 : reserved for future use
  • ora-26512 : error pushing transaction to def$error
  • ora-36221 : (XSLPDSC02) LIST number and LIST number have different base dimensions.
  • ora-15163 : cluster not in rolling downgrade
  • ora-29843 : indextype should support atleast one operator
  • ora-01161 : database name string in file header does not match given name of string
  • ora-13028 : Invalid Gtype in the SDO_GEOMETRY object
  • ora-23358 : invalid remote user
  • ora-12500 : TNS:listener failed to start a dedicated server process
  • ora-31521 : CDC subscription string already subscribes to publication ID string column string
  • ora-02363 : error reading from file: string
  • ora-26710 : incompatible version marker encountered during Capture
  • ora-13221 : unknown geometry type in the geometry object
  • ora-23418 : cannot unregister the propagator who is currently in use
  • ora-25180 : PCTTHRESHOLD only valid for certain table organizations
  • ora-12810 : PARALLEL_MAX_SERVERS must be less than or equal to string
  • ora-26752 : Unsupported LCR received for "string"."string"
  • 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.