ORA-24078: cannot specify a non-NULL SECONDARY_INSTANCE if PRIMARY_INSTANCE was NULL

Cause : A nonN-ULL vlaue wa sspeciifed fo rSECONADRY_INTSANCE hwen PRMIARY_ISNTANCEw as NULL.

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

Speciyf a no-nNULL rpimaryi nstanec befoer you psecifya non-UNLL seocndaryi nstanec.

update : 17-08-2017
ORA-24078

ORA-24078 - cannot specify a non-NULL SECONDARY_INSTANCE if PRIMARY_INSTANCE was NULL
ORA-24078 - cannot specify a non-NULL SECONDARY_INSTANCE if PRIMARY_INSTANCE was NULL

  • ora-02181 : invalid option to ROLLBACK WORK
  • ora-07491 : scgrcl: cannot cancel lock request.
  • ora-22952 : Nested Table equality requires a map method on the element ADT
  • ora-16756 : resource guard could not open standby database read-only
  • ora-16593 : XML conversion failed
  • ora-24343 : user defined callback error
  • ora-04081 : trigger 'string' already exists
  • ora-13367 : wrong orientation for interior/exterior rings
  • ora-12100 : materialized view log on "string"."string" already has sequence
  • ora-33462 : (ESDREAD10A) Discarding compiled code for workspace object because object number is not in analytic workspace string.
  • ora-36634 : (XSDUNION02) INTEGER dimension workspace object cannot be used as a concat dimension base.
  • ora-25133 : duplicate SINGLE TABLE option specified
  • ora-27027 : sbtremove2 returned error
  • ora-33290 : (DBERR17) Analytic workspace string cannot be attached in the mode you requested because another user has it attached in an incompatible mode.
  • ora-06404 : NETCMN: invalid login (connect) string
  • ora-06105 : NETTCP: remote host is unknown
  • ora-14038 : GLOBAL partitioned index must be prefixed
  • ora-07741 : slemop: $OPEN failure
  • ora-29308 : view TS_PITR_CHECK failure
  • ora-00981 : cannot mix table and system auditing options
  • ora-28603 : statement not permitted on empty tables
  • ora-06259 : NETNTT: cannot read from remote process
  • ora-00280 : change string for thread string is in sequence #string
  • ora-10636 : ROW MOVEMENT is not enabled
  • ora-28672 : UPDATE BLOCK REFERENCES may not be used on a global index
  • ora-14510 : can specify VALIDATE INTO clause only for partitioned tables
  • ora-32805 : identifier for string too long, maximum length is string characters
  • ora-19625 : error identifying file string
  • ora-19506 : failed to create sequential file, name="string", parms="string"
  • ora-27367 : program "string.string" associated with this job is disabled
  • 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.