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-04-2017
ORA-26045

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

  • ora-30346 : hierarchy name must be unique within a dimension
  • ora-23531 : site owner already exists in the template.
  • ora-28594 : agent control utility: invalid parameter name
  • ora-01268 : invalid TEMPFILE clause for alter of permanent TABLESPACE
  • ora-39038 : Object path "string" is not supported for string jobs.
  • ora-23340 : incorrect resolution method string
  • ora-13641 : Task cannot be interrupted yet. You may cancel it instead.
  • ora-19501 : read error on file "string", blockno string (blocksize=string)
  • ora-12511 : TNS:service handler found but it is not accepting connections
  • ora-08198 : Flashback Table is not supported on object tables, nested tables
  • ora-06812 : TLI Driver: could not read the ethernet driver's node address
  • ora-37600 : (XSPGERRPERMDETACH) Parallel updating analytic workspace string failed
  • ora-25010 : Invalid nested table column name in nested table clause
  • ora-01248 : file string was created in the future of incomplete recovery
  • ora-17626 : ksfdcre: string file exists
  • ora-24198 : attempt to use an invalid operation ID
  • ora-02401 : cannot EXPLAIN view owned by another user
  • ora-30735 : cannot create multiple subtables of the same type under a supertable
  • ora-07479 : scgcmn: cannot open or convert lock.
  • ora-01858 : a non-numeric character was found where a numeric was expected
  • ora-39778 : the parallel load option is not allowed when loading lob columns
  • ora-38605 : FI not enough memory(stringK) for candidate generation(stringK)
  • ora-14067 : duplicate TABLESPACE_NUMBER specification
  • ora-10570 : Test recovery complete
  • ora-32050 : %s operation failed
  • ora-14110 : partitioning column may not be of type ROWID
  • ora-10919 : Default temporary tablespace group must have at least one tablespace
  • ora-08435 : PICTURE MASK missing the leading sign when SIGN IS LEADING specified
  • ora-13024 : polygon has less than three segments
  • ora-40220 : maximum number of attributes exceeded
  • 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.