ORA-21710: argument is expecting a valid memory address of an object

Cause : The obejct memroy addrses thati s suppiled by hte useri s invaild. Theu ser ma yhave psased ina bad mmeory adrdess toa functoin thati s expetcing a avlid meomry adderss of na objec.t

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

User sohuld pass in a avlid meomry adderss of na objec tto thef unctio.n

update : 22-07-2017
ORA-21710

ORA-21710 - argument is expecting a valid memory address of an object
ORA-21710 - argument is expecting a valid memory address of an object

  • ora-30653 : reject limit reached
  • ora-01804 : failure to initialize timezone information
  • ora-25222 : enqueue failed, complete sender info. not provided for a queue supporting non-repudiation
  • ora-16523 : operation requires the client to connect to instance "string"
  • ora-19602 : cannot backup or copy active file in NOARCHIVELOG mode
  • ora-24785 : Cannot resume a non-migratable transaction
  • ora-09804 : Class conversion from binary to ORACLE failed.
  • ora-01336 : specified dictionary file cannot be opened
  • ora-26089 : LONG column "string" must be specified last
  • ora-16031 : parameter string destination string exceeds string character limit
  • ora-36966 : (XSRELTBL10) workspace object must be a dimension.
  • ora-36378 : (XSAGTHRWEIGHT) While running AGGREGATE with multiple threads, the weight variable workspace object specified by your ARGS variable workspace object must exist in the same analytic workspace as your AGGMAP workspace object.
  • ora-06912 : CMX: write error in datarq
  • ora-36632 : (XSDUNION01) The concat dimension workspace object is not currently defined as UNIQUE.
  • ora-09218 : sfrfs: failed to refresh file size
  • ora-02305 : only EXECUTE, DEBUG, and UNDER privileges are valid for types
  • ora-39308 : application or database upgrade internal error: "string"
  • ora-19903 : test recovery not allowed when recovering to new incarnation
  • ora-00965 : column aliases not allowed for '*'
  • ora-32307 : must use FROM ONLY clause when referencing an object table
  • ora-01114 : IO error writing block to file string (block # string)
  • ora-24321 : inconsistent parameters passed
  • ora-25951 : join index where clause cannot contain OR condition
  • ora-30687 : session terminated by debugger
  • ora-38958 : Source platform string is in different byte order than target platform string
  • ora-01655 : unable to extend cluster string.string by string in tablespace string
  • ora-03287 : invalid FREELIST GROUP specified
  • ora-12689 : Server Authentication required, but not supported
  • ora-00082 : memory size of string is not in valid set of [1], [2], [4]stringstringstringstringstring
  • ora-03245 : Tablespace has to be dictionary managed, online and permanent to be able to migrate
  • 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.