ORA-38784: Cannot create restore point 'string'.

Cause : Ana ttmeptt o rceaet ar esotrep oitn fiale.d See ohtere rrros no teh errors takc fro teh sepciifc erasno.

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

Fi xth eprbole man drerty.

update : 24-08-2017
ORA-38784

ORA-38784 - Cannot create restore point 'string'.
ORA-38784 - Cannot create restore point 'string'.

  • ora-02165 : invalid option for CREATE DATABASE
  • ora-16631 : operation requires shutdown of database/instance "string"
  • ora-33003 : (XSAGDIMDROP) workspace object, to be transformed during data load, must be a base dimension and not otherwise referenced in the AGGMAP.
  • ora-00301 : error in adding log file 'string' - file cannot be created
  • ora-23343 : no match for specified conflict resolution information
  • ora-00126 : connection refused; invalid duplicity
  • ora-12688 : Login failed: the SecurID server rejected the new pincode
  • ora-36767 : (XSAGGCNTMOVE05) workspace object cannot be used as an AGGCOUNT while there are permissions applied to it.
  • ora-22865 : more than one column specified
  • ora-07485 : scg_get_inst: cannot open instance number lock.
  • ora-16803 : unable to query a database table or fixed view
  • ora-14175 : a subpartition maintenance operation may not be combined with other operations
  • ora-00205 : error in identifying control file, check alert log for more info
  • ora-14056 : partition number string: sum of PCTUSED and PCTFREE may not exceed 100
  • ora-38448 : Indexing predicates with "string" operator is not supported.
  • ora-19107 : invalid XQueryX - unsupported construct - string
  • ora-13011 : value is out of range
  • ora-15194 : Internal ASM-DB interaction testing event number 15194
  • ora-27086 : unable to lock file - already in use
  • ora-36714 : (XSMXALLOC03) TARGETLOG variable workspace object must have the same data type as TARGET variable workspace object.
  • ora-35810 : (XSINPUTERR) The command has requested more input than was supplied in the command string.
  • ora-30460 : 'string.string' cannot be refreshed because it is marked UNUSABLE
  • ora-01592 : error converting Version 7 rollback segment (string) to Oracle 8 format
  • ora-16168 : LGWR network server could not switch to blocking mode
  • ora-25116 : invalid block number specified in the DUMP DATAFILE/TEMPFILE command
  • ora-24123 : feature string is not yet implemented
  • ora-24084 : DBLINK name in address field of agent string is not unique within the first 24 bytes
  • ora-38407 : The ADT associated with the attribute set already exists.
  • ora-06109 : NETTCP: message receive failure
  • ora-08232 : smsdes: cannot detach from SGA
  • 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.