Skip to main content

Oracle 9i Database Deletion Manually (When required)

Oracle 9i Database Deletion Manually (When required)

Database deletion task is not coming to DBA on regular interval. I was lucky to get few tasks for production database deletion. I have 10 year experience in database and first time, I got the opportunity to delete the production database after migration database on new server and updated from 9i to 11g. Delete the database on windows is easy but deletion of database manually without use of tool is a tricky task. To drop database is 9i is not so easy like 10g and above version, because 9i does not support drop database command. Here I am sharing my experience with DBA who is going to perform such type task in future. This step by step guide will give you how to delete database in UNIX environment where you are not able to use DBCA tools. Make sure before deleting the database unregistered database from catalog if you are using for backup & recover (Unregistered database from catalog).

In fact there is no direct command in oracle 9i to drop the database manually. You can only delete the database whenever required.
Steps to remove Oracle database refrences from Windows Env.:
  1. Ensure you are login with administrator user.
  2. Go to service.msc and stop all oracle related services.
  3. Remove oracle service using oradim utilities. For more about: How to Remove Oracle SID in Windows Env.
  4. Use OUI to uninstall the oracle products.
  5. Go to regedit to remove all oracle keys:
HKEY_LOCAL_MACHINE\SOFTWARE
HKEY_LOCAL_MACHINE\SOFTWARE\Classes, remove all keys that begin with Ora or ORCL
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\EventLog\Application
HKEY_LOCAL_MACHINE\SOFTWARE\ODBC remove all keys related with the "Oracle ODBC Driver" 
  1. Remove Environment variable and all the path of oracle references:
Example: C:\ORACLE\ORA81\BIN;C:\PROGRAM FILES\ORACLE\JRE\1.1.7\BIN  


  1. Delete all related oracle Icons from the drive location.
  2. Remove any Oracle-related *.INI files that may exist in the Windows directory.
    Typical Oracle .INI files include ORADIM73.INI, ORADIM80.INI, ORACLE.INI,ORAODBC.INI 
  3. Finally reboot the system.

Comments

Popular posts from this blog

Tablespace Management using Toad

You can view all of your tablespace information using toad tablespace screen from Database –> Administer –> Tablespaces Here each table describes different detailed information across all the tablespaces in database. If you open this screen from the toad DBA module then you are also able to see the “space history” and “IO history” tab along with Files, Free space, object, Fragmentation. With these tab you are able to able perform space monitoring and planning steps. These tab permits you check graphically space and IO usage over time. Through this way DBA are also able to estimate ‘Object size’ based on this estimation. From the below “alter tablespace” tab you can §          Modify the tablespace and datafile size. §          Add new datafile to the tablespace.

Import Excel Data into Oracle using Oracle form Button

Import Excel Data into Oracle using Oracle form Button 1. Create a button on the form with the name "IMPORT_EXCEL" and write a pl/sql on "WHEN BUTTON PRESSED" trigger. BEGIN IF :System.Cursor_Block<>'GL_DAILY_COMPOUND_HEADER' THEN   Go_Item('GL_DAILY_COMPOUND_HEADER.V_DATE'); END IF; IF :System.Mode = 'NORMAL' AND :System.Record_Status IN ('NEW','INSERT') THEN   IMPORT_EXCEL_PROC;   ---Form procedure ELSE  MESSAGE('Import allowed only for new entry!!!');  MESSAGE('Import allowed only for new entry!!!'); END IF; END; 2. Now write the procedure "IMPORT_EXCEL_PROC" into the program unit. Don't forget to create required table and folder for procedure IMPORT_EXCEL_PROC PROCEDURE IMPORT_EXCEL_PROC IS application    OLE2.Obj_Type; workbooks      OLE2.Obj_Type; workbook       OLE2.Obj_Type; worksheets      OLE2.Obj_Type; worksheet       OLE2.Obj_Type; cell      

Changing National Character Set AL16UTF16 to UTF8

Changing National Character Set AL16UTF16 to UTF8 The national character set is used for data that is stored in table columns of the types NCHAR, NVARCHAR2, and NCLOB.  In contrast, the database character set is used for data stored in table columns of the types CHAR, VARCHAR2 and CLOB. Like the database character set, the national character set is defined when the database is initially created and can usually no longer be changed, at least not easily or without involving quite a lot of work (export, recreate database, import). Except when creating the database, where the national character set is defined explicitly, it can change implicitly even when upgrading the database from Oracle8i to Oracle9i (or Oracle10g). You require SYSDBA authorization to change the national character set. Changing the national character set means changing an Oracle Dictionary entry, but no data is changed.  $sqlplus /nolog SQL> CONNECT / AS SYSDBA SQL> Select property_value fro