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 : 29-04-2017

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

  • ora-06804 : TLI Driver: could not bind an IPX address at initialization
  • ora-26536 : refresh was aborted because of conflicts caused by deferred transactions
  • ora-06923 : CMX: illegal break condition
  • ora-01980 : error during OS ROLE initialization
  • ora-10389 : parallel query server interrupt (cleanup)
  • ora-00350 : log string of instance string (thread string) needs to be archived
  • ora-32155 : Anydata not specified
  • ora-26034 : Column string does not exist in stream
  • ora-19032 : Expected XML tag string got string
  • ora-09822 : Translation of audit file name failed.
  • ora-16120 : dependencies being computed for transaction at SCN string
  • ora-31183 : Node type string cannot be converted to desired type
  • ora-06770 : TLI Driver: error sending version
  • ora-04082 : NEW or OLD references not allowed in table level triggers
  • ora-15101 : no action specified
  • ora-30331 : summary does not exist
  • ora-19914 : unable to encrypt backup
  • ora-14255 : table is not partitioned by Range, Composite Range or List method
  • ora-02840 : Open of log file by client failed
  • ora-01781 : UNRECOVERABLE cannot be specified without AS SELECT
  • ora-07235 : slemcw: fwrite error.
  • ora-36815 : (XSTBLFUNC08) The OLAP_TABLE has attempted to use an AW single row function with the aw_attach parameter set to DURATION QUERY.
  • ora-30192 : reserved for future use
  • ora-30047 : Internal event for kti tracing
  • ora-33016 : (XSAGDNGL07) In AGGMAP workspace object, workspace object is not a valid operator or variable name.
  • ora-02702 : osnoraenv: error translating orapop image name
  • ora-12686 : Invalid command specified for a service
  • ora-06754 : TLI Driver: unable to get local host address
  • ora-01168 : physical block size string does not match size string of other members
  • ora-09986 : wrong number of bytes read from SGA definition file
  • 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.