sap Disaster Recovery

-

SAP Disaster Recovery


Disaster Recovery

S.No
         Primary Site
Disaster Recovery Site
1
Backup(Cold/Offline)
+ Redo logs
Prerequisite:
  • H/W & S/W should be same along with versions, patch levels and environment variables.
  • Same SID should be maintained in both systems.
2
Create Standby Control File:
alter database create standby controlfile as ‘/path../<filename>.ctl’

3
Copy Backup+Controlfile+initSID.ora to  respective locations in DR Site
Note: Remove all existing datafiles of the DR site before copying backup files.
4

Modify initSID.ora, if there are any changes in H/W.(RAM)
5

Mount State:
Shutdown immediate
Startup nomount
Alter database mount standby database;
6

Recovery:
Recover standby database;
Set auto recovery ON;
Alter database recover cancel;
7

Activate:
Alter database activate standby database;
Alter database open;
Read Only:
Alter database open read only;



Show parameter <parameter_name>;            //To view parameter value
Log_archive_dest=’path’                    //Archival destination text string
Log_archive_start=true/false              //Start archival process on SGA initiation
Alter database archivelog;                   //To change archiving from noarchivelog to archivelog mode.
Alter database noarchivelog;               //To change archiving from archivelog to noarchivelog mode.
Alter system archive log current;        //To manually flush current redolog file.
Alter system archivelog start;             //To start archiving when DB is online.




Select open_mode, log_mode from v$database;
Select status from v$instance;




Select max(sequence#) from v$log_history;              //To view current archivelog.
Select file#, online_status from v$recover_file;         //To verify whether any datafile is corrupted or not.





Database Refresh/System copy

S.No
Quality
Production
1
License Backup
Slicense à SAP T-code
Saplicense –show à OS cmd
.
2
All locked users
SU10

3

Backup (Cold/Hot)
DB13
4

Backup Control File:
alter database backup controlfile to trace;
d:\oracle\SID\saptrace\usertrace\<n>.trc
5
Delete all datafiles and restore backup to their respective locations.

6
Modify controlfile
Reuse          à set
PRD sid      à QAS sid
Noresetlogs à resetlogs
And save the control file as .sql

7
Nomount State:
Startup nomount
@ run the control file creation script.

8
Recover Database
Recover database using backup controlfile until cancel;

9
Open the DB
Alter database open resetlogs;






Log_archive_dest=d:\oracle\<SID>\oraarch\RP1arch  //Change this parameter for some time when applying redologs.


Select open_mode, log_mode from v$database;
Select file#, status, name from v$datafile;
Select * from v$backup;
Select max(sequence#) from v$log_history;

Alter database datafile ‘<datafile name>’ end backup;    //when backup is strucked
Create spfile from pfile;



Shutdown abort;     //when db is struck                                         

Comments

Post a Comment

Popular posts from this blog

SAP NWA: Net Weaver Administration Tool

-
SAP ERP NWA Tool    SAP NetWeaver Administrator  Use SAP NetWeaver Administrator is a Web-based tool for administration and monitoring that offers a single entry point to configure, administer, and monitor your SAP NetWeaver system, its components, and the applications running on top of it. Prerequisites The Application Server Java (AS Java) is running. Features The SAP NetWeaver Administrator unifies the most important administration, monitoring, and troubleshooting tools. Some of the main SAP NetWeaver Administrator features are:  ●  A single, central tool for administration, troubleshooting, and problem analysis of your SAP NetWeaver system. You can perform administration tasks, such as starting and stopping instances, checking and modifying configuration settings, analyzing logs and traces, ensuring the error-free functioning of all system components by continuous system monitoring.  ●  An easy-to-use, task-oriented interface.  ...
Read more

SAP BASIS Spool Process

-
SAP BASIS SPOOL PROCESS : Spool Work process: This is used to print the documents, user cannot access this process directly, user uses dialog process or background process to print the documents. The data which to be printed will be stored in Temse (Temporary sequential objects) either OS level or DB level .Spool process look into Tempse and print the documents.   Which is determined by parameter rspo/store_location= db/g If it is G (Global ) it is tored in sys global directory Usr/sap/sid/sys/Global If it is database , it is stored in the table TST01 & TSTC Advantage of TEMSE at G file System : It is easily accessable. Disadvantages : when the spool size is increases , managing the spool will difficult ( no indexing at file system level ) File system will (may ) be corrupted file system is a not a part of regular backup in case of crashes entire spool data will be lost Advantages of Tempse store at D/B ...
Read more

SAP BASIS SPOOLING : Printing problems and general issues

-
Image
SAP BASIS Printing problems : General Issues How to Resolve SAP Printing Problems Print request from SAP R/3 is not printing. Try to print something else from a different application (for instance an email message or a page from Netscape) via the network. If you cannot print at all then the problem is not SAP printing, but the network. If you can print a file from a different application but not from SAP, then the problem is SAP printing and probably not the network. If you have a local IT support provider , report the problem to this person. Tell your IT support provider the four-character printer name, e.g. "wtpr". Remember to give the four-character name of the printer and its location. You can find this information in SAP by looking at your User Profile or opening the Print Screen List screen. the SAP system from which you sent the print request the spool request number displa...
Read more