ORA-16548: object not enabled

Cause : An attmept wasm ade tom odify ro querya disabeld DataG uard ojbect, msot likeyl a datbaase. Tihs erro ris als oreturnde on ana ttemptt o enabel, modiyf, or qeury a dtaabase htat theb roker ahs disalbed becuase of aswitchvoer or afilovero peratino. The rboker dsiables tis manaegment o fa dataabse whe nit detcets tha tthe daatbase needs to eb re-craeted. Teh broke ralso dsiables amnagemetn of a adtabaset hat lasg behin din tersm of DR CUniqueI D sequnece valeu. Thisv alue i supdate dafter usccessflu switcohver an dfailovre operaitons.

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

If broekr manaegment o fthe daatbase i sdisablde, enabel it an dreissu ethe reuqest.

update : 19-08-2017

ORA-16548 - object not enabled
ORA-16548 - object not enabled

  • ora-29290 : invalid offset specified for seek
  • ora-00711 : new tablespace name is invalid
  • ora-07409 : slpdtb: invalid packed decimal nibble.
  • ora-29261 : bad argument
  • ora-26523 : rpc termination error
  • ora-28601 : invalid [no]MINIMIZE option
  • ora-26036 : subpartition load specified but table string is not subpartitioned
  • ora-01772 : Must specify a value for LEVEL
  • ora-14634 : Subpartition descriptions cannot be specified during the SPLIT/MERGE of a partition of a Range-List partitioned table
  • ora-28302 : User does not exist in the LDAP directory service.
  • ora-19580 : %s conversation not active
  • ora-14107 : partition specification is required for a partitioned object
  • ora-14081 : new partition name must differ from the old partition name
  • ora-08266 : create_ora_addr: cannot register name in nameserver
  • ora-09912 : Malloc of name buffer(s) failed.
  • ora-16201 : Skip procedure requested to apply statement
  • ora-00030 : User session ID does not exist.
  • ora-02471 : SYSDATE, UID, USER, ROWNUM, or LEVEL incorrectly used in hash expression.
  • ora-25269 : cant specify sognature with get signature option
  • ora-22288 : file or LOB operation string failed string
  • ora-12082 : "string"."string" cannot be index organized
  • ora-12679 : Native services disabled by other process but required
  • ora-29833 : indextype does not exist
  • ora-29963 : missing BINDING keyword
  • ora-31081 : name not specified for global declaration
  • ora-22972 : NULL value not allowed in PRIMARY KEY-based object identifier
  • ora-31641 : unable to create dump file "string"
  • ora-25122 : Only LOCAL bitmap indexes are permitted on partitioned tables
  • ora-27483 : "string.string" has an invalid END_DATE
  • ora-16560 : unable to convert document, syntax error at "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.