ORA-38453: ExpFilter index should be created in the same schema as the base table.

Cause : An attepmt was mdae to craete the xEpressio nFilter nidex in aschema toher tha nthat oft he baset able.

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

Create hte indexi n the smae schem aas the abse tabl.e

update : 23-08-2017
ORA-38453

ORA-38453 - ExpFilter index should be created in the same schema as the base table.
ORA-38453 - ExpFilter index should be created in the same schema as the base table.

  • ora-29955 : error occurred in the execution of ODCIINDEXEXCHANGEPARTITION routine
  • ora-19601 : output file is string string (string)
  • ora-38907 : DML error logging is not supported for FILE column "string"
  • ora-26671 : maximum number of STREAMS processes exceeded
  • ora-26077 : direct path column array is not initialized
  • ora-33217 : (CINSERT20) Custom member values cannot be added to concat dimension workspace object, or to any of its bases, because it is not defined as UNIQUE.
  • ora-37136 : (XSCCOMP11) Cannot ROLLUP dimension workspace object which is a base of COMPRESSED COMPOSITE workspace object, use AGGREGATE instead.
  • ora-22898 : existing scope clause on "string" points to a table other than the one mentioned in the referential constraint
  • ora-10284 : simulate zero/infinite asynch I/O buffering
  • ora-31660 : metadata filter name can not be defaulted
  • ora-13049 : unable to determine tolerance value from table _SDODIM
  • ora-19122 : unsupported XQuery declaration
  • ora-16255 : Log Auto Delete conflicts with another LogMiner session
  • ora-03230 : segment only contains string blocks of unused space above high water mark
  • ora-02098 : error parsing index-table reference (:I)
  • ora-12825 : explicit degree of parallelism must be specified here
  • ora-34871 : (PERMIT06) Session-only value 'value' of workspace object has been deleted because a PERMIT change has revealed a duplicate value.
  • ora-14016 : underlying table of a LOCAL partitioned index must be partitioned
  • ora-22330 : cannot alter a type that is not valid
  • ora-06135 : NETTCP: connection rejected; server is stopping
  • ora-02439 : Unique index on a deferrable constraint is not allowed
  • ora-02250 : missing or invalid constraint name
  • ora-25329 : AQ array operations not allowed on 8.0 queues
  • ora-27490 : cannot open disabled window "string.string"
  • ora-00479 : RVWR process terminated with error string
  • ora-15072 : command requires at least string failure groups, discovered only string
  • ora-02167 : LOGFILE clause specified more than once
  • ora-33066 : (XSAGDNGL32) In AGGMAP workspace object, the hierarchy dimension QDR workspace object must be a hierarchy dimension of the relation.
  • ora-07585 : spdcr: $PARSE failure
  • ora-12408 : unsupported operation: string
  • 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.