Skip to Content

Uninstall Database manually for Unicode Conversion

Hi Guys,

While performing a Unicode Conversion, during Export, Unistall and Import of Database, I would like to improve times for Database Creation since its 5TB

My goal is to delete SAP/DB Instance Non-Unicode but keeping Tablespaces and Datafiles Layout, in order to not recreate them when re-installing SAP/DB Instance Unicode

According to SAP Note 1260050 - UNIX:Deleting Oracle DB Instance Based on NW7.1 and Higher, the steps are the following.


drop user SAP<SCHEMA_ID> cascade;

drop tablespace <TABLESPACE_NAME> including contents;


Are this steps valid to delete a ABAP Database, and keeping Datafiles structures for when Installing Unicode SAP Instance?


Thanks!


Add a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

2 Answers

  • Best Answer
    Posted on Jul 17, 2014 at 03:48 PM

    Hi Martin,

    While performing a Unicode Conversion, during Export, Unistall and Import of Database, I would like to improve times for Database Creation since its 5TB

    Why don't you drop the entire target system and install from fresh using system copy method.

    This will require a parallel system to be setup where you can have target system installed a Unicode system using system copy option.

    To minimize the downtime, you may perform parallel Database export import with table splitting.

    Regards,

    Deepak Kori

    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on Jul 17, 2014 at 03:43 PM

    Hello

    This will not delete the database itself... it will drop the SAP all the schema objects (segments, object, tablespaces, datafiles...) for the selected ABAP/JAVA stack (depending on the user selected sapsr3 or sapsr3db)

    The rest will be preserved

    • Oracle instance (binaries/service)
    • system tablespaces (system, sysaux, undo...)
    • Control files
    • redo logs
    • directory structure

    For the next run of your procedure you won't be able to run a regular installation as the DB will still be there and SAPinst is supposed to create the DB... So you will either have to drop the DB or perfom a system copy.

    Regards

    Add a comment
    10|10000 characters needed characters exceeded

    • The drop command "including contents" will delete the datafiles... thus SAPinst will have to create them again... and it can take while for a 5 Tb DB.

      SAPinst is supposed to recreate the whole DB thus you should entirely delete it

      startup mount exclusive restrict

      drop database;

      One solution would be to keep the datafiles

      => just run the first SQL command : drop user SAP<SCHEMA_ID> cascade;

      and play with sapinst option SAPINST_SET_STEPSTATE to skip the DB creation step

      pastedImage_4.png (70.3 kB)

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.