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 : 29-05-2017
ORA-26045

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

  • ora-02443 : Cannot drop constraint - nonexistent constraint
  • ora-32142 : maximum number of iterations exceeded
  • ora-27058 : file I/O question parameter is invalid
  • ora-00333 : redo log read error block string count string
  • ora-36666 : (XSDPART04) workspace object is not a concat dimension.
  • ora-25109 : standby lock name space has illegal character 'string'
  • ora-09754 : sppst: invalid process number passed to sppst.
  • ora-32162 : Read/Write SQL method not registered
  • ora-26053 : Row was not loaded due to conversion error.
  • ora-25959 : join index must be of the bitmap type
  • ora-22054 : underflow error
  • ora-18000 : invalid outline name
  • ora-39181 : Only partial table data may be exported due to fine grain access control on string
  • ora-02067 : transaction or savepoint rollback required
  • ora-12684 : encryption/crypto-checksumming: Diffie-Hellman seed too small
  • ora-27076 : unable to set limit for open files
  • ora-01284 : file string cannot be opened
  • ora-14042 : partition bound may not be specified for a partition being moved, modified or rebuilt
  • ora-39054 : missing or invalid definition of the SQL output file.
  • ora-36921 : (XSVPMVTOPART02) workspace object and workspace object are not in the same analytic workspace.
  • ora-23435 : cannot create an updatable ROWID materialized view with LOB columns
  • ora-14267 : cannot specify PARALLEL clause when adding a (Composite) Range partition
  • ora-01643 : system tablespace can not be made read only
  • ora-16824 : Fast-Start Failover and other warnings detected for the database
  • ora-39060 : table(s) dropped because of conflict with master table
  • ora-01874 : time zone hour must be between -12 and 14
  • ora-01245 : offline file string will be lost if RESETLOGS is done
  • ora-00398 : abort thread recovery due to reconfiguration
  • ora-14614 : List value 'string' specified twice in subpartition 'string'
  • ora-02720 : osnfop: shmat failed
  • 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.