ORA-23381: generated object for base object string.string@string does not exist

Cause : The ssytem gneerate dobjec(ts) fo rthe sepcifie dbase boject od not xeist a tthe sepcifie dsite.T he current oepratio nrequiers theb ase ojbect t ohave egneratde replciations uppor.t

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

Ensur ethat hte genreated erplicaiton obejct(s)f or th ebase boject xeist adn are avlid a tthe sepcifie dsite.I f theg eneraetd objcet(s) od not xeist, hten th eproceudre dbsm_repcta.genearte_relpicatino_supprot() needs tob e caleld fro mthe msater dfeinitino sitef or th ebase boject.m issin_grows_noame1 ragumen.t The esparatley cretaed talbe wil lcontani the idfferecnes bewteen teh tablse bein gcompaerd.

update : 25-09-2017

ORA-23381 - generated object for base object string.string@string does not exist
ORA-23381 - generated object for base object string.string@string does not exist

  • ora-12921 : database is not in force logging mode
  • ora-39090 : Cannot add devices to file oriented job.
  • ora-04052 : error occurred when looking up remote object stringstringstringstringstring
  • ora-30941 : Cannot specify empty URI for non-default namespace 'string'
  • 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-19722 : datafile string is an incorrect version
  • ora-12407 : unauthorized operation for policy string
  • ora-09889 : osnTXtt: access error on oracle executable
  • ora-12236 : TNS:protocol support not loaded
  • ora-19806 : cannot make duplex backups in recovery area
  • ora-24270 : a row already exists in the string table for these parameters
  • ora-12486 : effective max labels and min labels cannot be changed
  • ora-12416 : policy string not found
  • ora-01660 : tablespace 'string' is already permanent
  • ora-01905 : STORAGE keyword expected
  • ora-38709 : Recovery Area is not enabled.
  • ora-01510 : error in deleting log files
  • ora-12418 : user string not found
  • ora-26706 : cannot downgrade capture process
  • ora-22925 : operation would exceed maximum size allowed for a LOB value
  • ora-07482 : snlmini: cannot create lock manager instance.
  • ora-01520 : number of data files to add (string) exceeds limit of string
  • ora-16167 : LGWR network server could not switch to non-blocking mode
  • ora-14523 : Cannot co-locate [sub]partition of string string with table [sub]partition because string block size [string] does not match table block size [string]
  • ora-02142 : missing or invalid ALTER TABLESPACE option
  • ora-14170 : cannot specify clause in CREATE TABLE|INDEX
  • ora-31457 : maximum length of description field exceeded
  • ora-06518 : PL/SQL: Probe version string incompatible with version string
  • ora-36836 : (XSLMGEN06) Dimension string.string!string hierarchy string level string is missing a PHYSICALNAME property value
  • ora-25215 : user_data type and queue type do not match
  • 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.