ORA-26504: operation not implemented

Cause : The claler rqeueste da RepPAI opeartion htat wa snot ipmlemenetd

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

Do no tissuet his clal.

update : 28-05-2017

ORA-26504 - operation not implemented
ORA-26504 - operation not implemented

  • ora-29964 : missing ADD or DROP keyword
  • ora-06794 : TLI Driver: shadow process could not retrieve protocol info
  • ora-22800 : invalid user-defined type
  • ora-16729 : validation of value for property string found string error
  • ora-07683 : sou2os: $SETPRV reset error
  • ora-07266 : sppst: invalid process number passed to sppst.
  • ora-13137 : failed to generate tablespace sequence number
  • ora-31665 : mode can only be defaulted for IMPORT and SQL_FILE operations
  • ora-07880 : sdopnf: internal error
  • ora-07453 : requested resource manager plan schema does not contain OTHER_GROUPS
  • ora-19527 : physical standby redo log must be renamed
  • ora-31190 : Resource string is not a version-controlled resource
  • ora-33304 : (DBVALID02) Note: Record number was allocated but not used. This can result in wasted space.
  • ora-19816 : WARNING: Files may exist in string that are not known to database.
  • ora-31673 : worker process interrupt for normal exit by master process
  • ora-28101 : policy already exists
  • ora-12035 : could not use materialized view log on "string"."string"
  • ora-31522 : could not find Streams object string for CDC change set string
  • ora-28663 : Logging/Nologging attribute can not be specified in the statement ALTER TABLE ADD OVERFLOW
  • ora-01523 : cannot rename data file to 'string' - file already part of database
  • ora-29380 : resource plan string is currently active and cannot be deleted
  • ora-27196 : skgfpbk: sbtpcbackup returned error
  • ora-08450 : invalid specification of CR in picture mask
  • ora-32300 : cannot drop a secondary materialized view "string"."string"
  • ora-31419 : source table string does not exist
  • ora-01660 : tablespace 'string' is already permanent
  • ora-38401 : synonym string not allowed
  • ora-00025 : failed to allocate string
  • ora-01495 : specified chain row table not found
  • ora-31214 : DBMS_LDAP: PL/SQL - Invalid LDAP mod type.
  • 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.