ORA-15034: disk 'string' does not require the FORCE option

Cause : An attempt was made to add the disk to the diskgroup using the FORCE option. The disk was not found to be in use at the present time, so the FORCE option was not permitted.

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

Avoid gratuitous use of the FORCE option.

update : 29-06-2017

ORA-15034 - disk 'string' does not require the FORCE option
ORA-15034 - disk 'string' does not require the FORCE option

  • ora-24408 : could not generate unique server group name
  • ora-16538 : no match on requested item
  • ora-06806 : TLI Driver: could not complete protocol initialization for SPX
  • ora-02244 : invalid ALTER ROLLBACK SEGMENT option
  • ora-12731 : invalid collation class in regular expression
  • ora-19906 : recovery target incarnation changed during recovery
  • ora-06904 : CMX: no transport address available for remote application
  • ora-26098 : direct path context is not prepared
  • ora-08209 : scngrs: SCN not yet initialized
  • ora-12656 : Cryptographic checksum mismatch
  • ora-03281 : invalid ALLOCATE EXTENT option
  • ora-14016 : underlying table of a LOCAL partitioned index must be partitioned
  • ora-00832 : no streams pool created and cannot automatically create one
  • ora-01058 : internal New Upi interface error
  • ora-01531 : a database already open by the instance
  • ora-29356 : These parameters can be specified only for directives that refer to consumer groups
  • ora-06030 : NETDNT: connect failed, unrecognized node name
  • ora-36258 : (XSAGINFO00) When the AGGMAPINFO function is called, workspace object must be an AGGMAP.
  • ora-28582 : a direct connection to this agent is not allowed
  • ora-12333 : database (link name string) is not mounted
  • ora-19273 : XQ0053 - empty string in namespace declaration
  • ora-23502 : valid directory for offline instatiation is not specified
  • ora-07620 : smscre: illegal database block size
  • ora-02365 : error seeking in file: string
  • ora-01935 : missing user or role name
  • ora-22955 : The cardinality parameter is not within the allowed limits
  • ora-06022 : NETASY: channel open failure
  • ora-00346 : log member marked as STALE
  • ora-37002 : Oracle OLAP failed to initialize. Please contact Oracle OLAP technical support.
  • ora-13012 : an invalid window type was specified
  • 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.