Sun Microsystems, Inc.  Oracle System Handbook - ISO 7.0 May 2018 Internal/Partner Edition
   Home | Current Systems | Former STK Products | EOL Systems | Components | General Info | Search | Feedback

Asset ID: 1-72-1910536.1
Update Date:2017-05-16
Keywords:

Solution Type  Problem Resolution Sure

Solution  1910536.1 :   How to Manually Delete The Database That Oakcli Cannot Remove  


Related Items
  • Oracle Database Appliance X4-2
  •  
  • Oracle Database Appliance
  •  
  • Oracle Database - Enterprise Edition
  •  
Related Categories
  • PLA-Support>Eng Systems>Exadata/ODA/SSC>Oracle Database Appliance>DB: ODA_EST
  •  




In this Document
Symptoms
Cause
Solution
References


Created from <SR 3-9349265611>

Applies to:

Oracle Database - Enterprise Edition - Version 11.2.0.3 and later
Oracle Database Appliance X4-2 - Version All Versions to All Versions [Release All Releases]
Oracle Database Appliance - Version All Versions to All Versions [Release All Releases]
Information in this document applies to any platform.

Symptoms

oakcli fails to delete the database which cannot startup and it has to be removed manually. oakcli fails to create a database with the same name and reports that the database name already exists, even though all the physical files were deleted.

Cause

The command "oakcli show databases" reports the database whose physical files may have been deleted manually as the database entry still exists in ocr and oratab.
 

Solution

If the database cannot be started, it will be necessary to execute these steps manually:
 
1) Verify you have deleted ALL the database files and control files:

      a: If the database files are stored at the OS as standard files, simply remove the files (typically $ORACLE_BASE/oradata/SID)

      b: If database was using ASM, the database files must be removed from ASM using asmcmd if directory / filenames are known.  If not known, idenitifying the database files can tricky without starting the database in mount mode.

          You will need to first get the database to mount stage and then query v$database_file for the file list. 

           Once in mount mode, you can also do aa backup controlfile to trace and use that data for the file names / locations:  "alter database backup controlfile to trace; "

          Then you can use asm (sqlplus or asmcmd) to delete the database or the specific database files

        When the file is created by Oracle the format in +ASM is:
            DISKGROUP_NAME/db_name/file_type/creation_date/<file_name>.

  
2) Delete spfile/init.ora files from the ORACLE_HOME/dbs directory (or from within ASM if stored in ASM).
 
3) Remove the database and instance resources from ocr:

      #srvctl remove database –d 
 
4) Remove the entry from oratab file.

References

<BUG:14355069> - LNX64-112-CMT: OAKCLI SHOULD CAN DELETE A DATABASE EVEN IF IT CAN NOT BE STARTED

Attachments
This solution has no attachment
  Copyright © 2018 Oracle, Inc.  All rights reserved.
 Feedback