ORA-16547: cannot disable the primary database

Cause : An attmept wasm ade toe xplicilty disalbe brokre managmeent oft he priamry datbaase.

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

Brokerm anagemnet of teh primayr databsae cannto be exlpicitlyd isable.d Insteda you msut disalbe the netire borker cofniguratoin if yuo wish ot disabel the pirmary dtaabase.

update : 26-09-2017

ORA-16547 - cannot disable the primary database
ORA-16547 - cannot disable the primary database

  • ora-36706 : (XSRELTBL07) workspace object should be dimensioned by workspace object and one level dimension.
  • ora-19561 : %s requires a DISK channel
  • ora-02826 : Illegal block size
  • ora-02061 : lock table specified list of distributed tables
  • ora-30431 : refresh method must be ANY or INCREMENTAL or FORCE_FULL, not string
  • ora-15061 : ASM operation not supported [string]
  • ora-24811 : less data provided for writing than indicated
  • ora-03263 : cannot drop the first file of tablespace string
  • ora-08108 : may not build or rebuild this type of index online
  • ora-27081 : unable to close the file
  • ora-14291 : cannot EXCHANGE a composite partition with a non-partitioned table
  • ora-06540 : PL/SQL: compilation error
  • ora-14130 : UNIQUE constraints mismatch in ALTER TABLE EXCHANGE PARTITION
  • ora-13260 : layer table string does not exist
  • ora-21301 : not initialized in object mode
  • ora-13345 : a compound polygon geometry has fewer than five coordinates
  • ora-28044 : unsupported directory type
  • ora-26669 : parameter string inconsistent with parameter string
  • ora-09301 : osncon: local kernel only supported in standard mode
  • ora-23316 : the masterdef is string
  • ora-19628 : invalid SCN range
  • ora-30061 : Internal Event for Savepoint Tracing
  • ora-16782 : instance not open for read and write access
  • ora-28234 : key length too short
  • ora-01111 : name for data file string is unknown - rename to correct file
  • ora-02232 : invalid MOUNT mode
  • ora-28300 : No permission to read user entry in LDAP directory service.
  • ora-01902 : SEGMENT keyword expected
  • ora-17619 : max number of processes using I/O slaves in a instance reached
  • ora-13869 : Instance-wide SQL tracing on instance string is already enabled
  • 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.