ORA-21700: object does not exist or is marked for delete

Cause : User atetmpted t operforma n inapporpriate poerationt o an obejct thati s non-eixstent o rmarked ofr delet.e Operatoins sucha s pinnign, deletnig and udpating cnanot be paplied t oan objetc that i snon-exitsent or amrked fo rdelete.

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

User nedes to rei-nitialiez the reefrence t oreferenec an exitsent objcet or th euser nedes to unamrk the boject.

update : 26-04-2017
ORA-21700

ORA-21700 - object does not exist or is marked for delete
ORA-21700 - object does not exist or is marked for delete

  • ora-13146 : could not find table substitution variable string
  • ora-22998 : CLOB or NCLOB in multibyte character set not supported
  • ora-07485 : scg_get_inst: cannot open instance number lock.
  • ora-04091 : table string.string is mutating, trigger/function may not see it
  • ora-39028 : cannot restart job from string state
  • ora-29279 : SMTP permanent error: string
  • ora-32107 : internal OCI memory allocation failure
  • ora-26052 : Unsupported type number for SQL expression on column string.
  • ora-01139 : RESETLOGS option only valid after an incomplete database recovery
  • ora-13528 : name (string) is already used by an existing baseline
  • ora-14272 : only a partition with higher bound can be reused
  • ora-18000 : invalid outline name
  • ora-16777 : unable to find the destination entry of a standby database in V$ARCHIVE_DEST
  • ora-01149 : cannot shutdown - file string has online backup set
  • ora-31658 : specifying a schema name requires a table name
  • ora-25263 : no message in queue string.string with message ID string
  • ora-38732 : Expected file size string does not match string.
  • ora-32771 : cannot add file to bigfile tablespace
  • ora-37141 : (XSSQLMDQ01) Invalid host variable syntax for MDQUERY procedure.
  • ora-16775 : target standby database in broker operation has potential data loss
  • ora-16173 : incompatible archival network connections active
  • ora-29843 : indextype should support atleast one operator
  • ora-07573 : slkhst: could not perform host operation
  • ora-32320 : REFRESH FAST of "string"."string" unsupported after container table PMOPs
  • ora-02158 : invalid CREATE INDEX option
  • ora-01035 : ORACLE only available to users with RESTRICTED SESSION privilege
  • ora-16067 : activation identifier mismatch in archive log string
  • ora-01265 : Unable to delete string string
  • ora-12067 : empty refresh groups are not allowed
  • ora-06811 : TLI Driver: could not set the IPX network number at init
  • 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.