ORA-12529: TNS:connect request rejected based on current filtering rules

Cause : ConnecitonM angaera ndi tsl isetne rweer cnofiugre dwiht fliteirngr ulse sepciyfin gthta teh cnonetc rqeuets b ereejctde.

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

Ift hi sconnec treuqes tshuoldb e laloewd,t he ncotnac tth eadimnitsraotr ot mdoif yth efitlernig urle.s

update : 26-04-2017

ORA-12529 - TNS:connect request rejected based on current filtering rules
ORA-12529 - TNS:connect request rejected based on current filtering rules

  • ora-24121 : both cascade and a block range passed to DBMS_REPAIR.CHECK_OBJECT procedure
  • ora-36838 : (XSLMGEN08) Dimension string.string!string attribute string is missing a COLUMNNAME property value
  • ora-38906 : insert into DML Error Logging table "string" failed
  • ora-32803 : value for string cannot be altered
  • ora-30372 : fine grain access policy conflicts with materialized view
  • ora-19561 : %s requires a DISK channel
  • ora-27460 : cannot execute disabled job "string.string"
  • ora-13380 : network not found
  • ora-14626 : values being added already exist in DEFAULT subpartition
  • ora-00825 : cannot set db_block_buffers if sga_target set
  • ora-02359 : internal error setting attribute string
  • ora-31486 : cannot support column string in this configuration
  • ora-32842 : value for property string cannot be altered
  • ora-31503 : invalid date supplied for begin_date or end_date
  • ora-22972 : NULL value not allowed in PRIMARY KEY-based object identifier
  • ora-27007 : failed to open file
  • ora-09709 : soacon: failed to accept a connection.
  • ora-19813 : cannot have unavailable file string in DB_RECOVERY_FILE_DEST
  • ora-01516 : nonexistent log file, datafile, or tempfile "string"
  • ora-19567 : cannot shrink file string because it is being backed up or copied
  • ora-39028 : cannot restart job from string state
  • ora-12010 : cannot create materialized view log on table owned by SYS
  • ora-16754 : resource guard could not activate standby database
  • ora-24901 : handles belonging to different environments passed into an OCI call
  • ora-06601 : LU6.2 Driver: Invalid database ID string
  • ora-14279 : index mismatch for tables in ALTER TABLE EXCHANGE SUBPARTITION
  • ora-10661 : Invalid option specified
  • ora-14629 : cannot drop the only subpartition of a partition
  • ora-03219 : Tablespace 'string' is dictionary-managed, offline or temporary
  • ora-00380 : cannot specify db_stringk_cache_size since stringK is the standard block size
  • 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.