ORA-28553: pass-through SQL: invalid bind-variable position

Cause : A pass-through SQL function referring to the position of a bind variable in the currently-parsed SQL statement supplied an invalid bind-variable position. Valid values are 1 through n, where n is the number of bind-variable place-holders in the SQL text.

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

Verify that the bind-variable position parameter is in the correct range to represent a place-holder in the SQL text. Confirm that the SQL text uses the correct syntax for a bind-variable place-holder, as required by the non-Oracle system.

update : 23-06-2017
ORA-28553

ORA-28553 - pass-through SQL: invalid bind-variable position
ORA-28553 - pass-through SQL: invalid bind-variable position

  • ora-19771 : cannot rename change tracking file while database is open
  • ora-19200 : Invalid column specification
  • ora-28041 : Authentication protocol internal error
  • ora-06571 : Function string does not guarantee not to update database
  • ora-14258 : invalid partition description
  • ora-26022 : index string.string was made unusable due to:
  • ora-14610 : Lob attributes not specified for lob column string for subpartition string
  • ora-33076 : (XSAGDNGL37) In AGGMAP workspace object, the value 'number' is not a valid value of dimension workspace object.
  • ora-37134 : (XSCCOMP09) You cannot add new values to workspace object because it includes positions for precomputed aggregate values.
  • ora-19830 : error from target database: string
  • ora-27212 : some entrypoints in Media Management Library are missing
  • ora-24232 : unknown Embedded PL/SQL Gateway attribute string
  • ora-38029 : object statistics are locked
  • ora-32505 : too many watchpoints
  • ora-28534 : Heterogeneous Services preprocessing error
  • ora-04083 : invalid trigger variable 'string'
  • ora-29286 : internal error
  • ora-19685 : SPFILE could not be verified
  • ora-24364 : internal error while padding blanks
  • ora-40107 : operation requires string option to be installed
  • ora-00472 : PMON process terminated with error
  • ora-31487 : cannot support begin dates or end dates in this configuration
  • ora-25246 : listen failed, the address string is an 8.0 style exception queue
  • ora-16643 : unable to determine location of broker configuration files
  • ora-29811 : missing STATISTICS keyword
  • ora-13158 : Oracle object string does not exist
  • ora-01858 : a non-numeric character was found where a numeric was expected
  • ora-02800 : Requests timed out
  • ora-30513 : cannot create system triggers of INSTEAD OF type
  • ora-27434 : cannot alter chain step job string.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.