ORA-16632: instance being added to database profile

Cause : The Data Guard broker determined that an instance has successfully found its database profile within the broker configuration file, but yet lacks an instance-specific profile. The broker automatically creates an instance-specific profile and associates the instance with its database profile.

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

No user action is required. The broker will automatically associate the instance with its database profile and incorporate the instance in broker activity.

update : 28-04-2017
ORA-16632

ORA-16632 - instance being added to database profile
ORA-16632 - instance being added to database profile

  • ora-06125 : NETTCP: ORASRV exited unexpectedly
  • ora-39103 : Timeout before worker process string finished initialization. Worker error:
  • ora-23485 : Column group "string" must consist of a single numeric column only
  • ora-36688 : (NTEXTCNV00) Error during conversion from TEXT to NTEXT.
  • ora-23532 : tables with different synchronization mechanisms are in the same group
  • ora-15070 : maximum number of files string exceeded in diskgroup "string"
  • ora-24003 : Queue table index string inconsistent with queue table string
  • ora-01908 : EXISTS keyword expected
  • ora-16400 : quota attributes are not allowed with DB_RECOVERY_FILE_DEST
  • ora-13202 : failed to create or insert into the SDO_INDEX_METADATA table
  • ora-33215 : (CINSERT07) You cannot add session-only values to the workspace object dimension.
  • ora-27453 : %s is an invalid job or program argument name.
  • ora-16150 : FINISH recovery performed on another, older standby database
  • ora-02720 : osnfop: shmat failed
  • ora-12829 : Deadlock - itls occupied by siblings at block string of file string
  • ora-35019 : (QFCHECK07) The Analytic Workspace and EIF file definitions of workspace object have different partition dimensions.
  • ora-36630 : (XSDUNION00) An empty base dimension list was specified in the concat dimension definition.
  • ora-10620 : Operation not allowed on this segment
  • ora-16217 : prepare to switchover has not completed
  • ora-22294 : cannot update a LOB opened in read-only mode
  • ora-07456 : cannot set RESOURCE_MANAGER_PLAN when database is closed
  • ora-38746 : error occurred while restoring data block (file# string, block# string)
  • ora-24059 : invalid COMPATIBLE parameter setting string specified in DBMS_AQADM.string
  • ora-27140 : attach to post/wait facility failed
  • ora-08232 : smsdes: cannot detach from SGA
  • ora-31406 : change source string is referenced by a change set
  • ora-07578 : szprv: $FIND_HELD failure
  • ora-22894 : cannot add constraint on existing unscoped REF columns of non-empty tables
  • ora-00119 : invalid specification for system parameter string
  • ora-01500 : failure in getting date/time
  • 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.