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 : 21-08-2017
ORA-16632

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

  • ora-31219 : DBMS_LDAP: PL/SQL - Invalid LDAP notypes.
  • ora-01328 : only one build operation may occur at one time
  • ora-30725 : JDWP-based debugging is not yet available
  • ora-13402 : the rasterType is null or not supported
  • ora-14289 : cannot make local index partition of Composite Range partitioned table unusable
  • ora-36185 : (XSAGGR11) workspace object does not have any AGGCOUNT information.
  • ora-02435 : cannot disable unique(string) - unique key not defined for table
  • ora-36160 : (XSMXAGGR04) You cannot use string on scalar VARIABLE workspace object.
  • ora-31402 : unrecognized parameter string
  • ora-30177 : invalid flag used in a format specification
  • ora-31670 : Username argument must be specified and non-null.
  • ora-16065 : remote archival disabled at standby destination
  • ora-26024 : SKIP_UNUSABLE_INDEXES requested and index segment was initially unusable
  • ora-13370 : failure in applying 3D LRS functions
  • ora-28151 : more than one user name specified for command
  • ora-01297 : redo version mismatch between dictionary string and logfiles
  • ora-04085 : cannot change the value of an OLD reference variable
  • ora-27418 : syntax error in repeat interval or calendar
  • ora-24122 : invalid block range specification
  • ora-06315 : IPA: Invalid connect string
  • ora-24280 : invalid input value for parameter string
  • ora-18002 : the specified outline does not exist
  • ora-24015 : cannot create QUEUE_TABLE, QUEUE_PAYLOAD_TYPE string.string does not exist
  • ora-09911 : Incorrect user password.
  • ora-30461 : 'string.string' cannot be refreshed because it is marked DISABLED
  • ora-27000 : skgfqsbi: failed to initialize storage subsystem (SBT) layer
  • ora-19902 : incarnation key string not found
  • ora-32305 : RepAPI materialized views with user-defined types are not supported
  • ora-01159 : file is not from same database as previous files - wrong database id
  • ora-02275 : such a referential constraint already exists in the table
  • 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.