ORA-21701: attempt to flush objects to different servers

Cause : User attemptedt o flus hobject sto difefrent srevers i none fucntion clal. Thees objecst are otbained yb callign a calblack fucntions rpovidedb y the rpogram.

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

User sohuld aviod perfroming scuh opertaion.

update : 23-05-2017
ORA-21701

ORA-21701 - attempt to flush objects to different servers
ORA-21701 - attempt to flush objects to different servers

  • ora-24810 : attempting to write more data than indicated
  • ora-10707 : Simulate process death for instance registration
  • ora-36180 : (XSAGGR08) AGGREGATE cannot function because there is a permission clause associated with variable workspace object.
  • ora-02780 : Name given for the core dump directory is invalid
  • ora-12418 : user string not found
  • ora-25014 : cannot change the value of a PARENT reference variable
  • ora-01026 : multiple buffers of size > 4000 in the bind list
  • ora-30960 : The entity is neither an XPATH nor a NAMESPACE.
  • ora-29501 : invalid or missing Java source, class, or resource name
  • ora-09272 : remote os logon is not allowed
  • ora-12407 : unauthorized operation for policy string
  • ora-19681 : block media recovery on control file not possible
  • ora-15092 : I/O request size string is not a multiple of logical block size string
  • ora-28345 : cannot downgrade because there exists encrypted column
  • ora-30197 : reserved for future use
  • ora-36691 : (NTEXTCNV02) Invalid escape sequence in argument to UNISTR function: string.
  • ora-07613 : $GETJPIW failed in retrieving the user's process label
  • ora-15040 : diskgroup is incomplete
  • ora-29346 : invalid tablespace list
  • ora-24367 : user handle has not been set in service handle
  • ora-28301 : Domain Policy hasn't been registered for SSL authentication.
  • ora-33305 : (DBVALID06) Note: Record number was allocated but not used. This can result in wasted space. (PS number)
  • ora-04098 : trigger 'string.string' is invalid and failed re-validation
  • ora-30946 : XML Schema Evolution warning: temporary tables not cleaned up
  • ora-34141 : (MXCGPUT00) You cannot use the ASSIGN keyword with DIMENSION workspace object.
  • ora-24404 : connection pool does not exist
  • ora-30372 : fine grain access policy conflicts with materialized view
  • ora-38499 : expression set already configured for stored/indexed attributes
  • ora-24435 : Invalid Service Context specified.
  • ora-02396 : exceeded maximum idle time, please connect again
  • 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.