Professional Documents
Culture Documents
BR-BACKUP
BR Backup is used to take backup of the database (Datafiles). When ever a backup is triggered BR
Backup is initialized.
There are various types of backups
1. Offline Backup
2. Online Backup
3. Incremental Backup
4. Partial Backup
1. Offline Backup (Cold Backup)
The database is down during backup and no transaction is allowed as it is down.
It is consistent and reliable.
Whole Offline Backup: The backup taken fully and a catalog is opened to start the incremental
backup.
Eg: A database is of 2000 GB Which is not possible to take a daily full offline backup with a backup
speed of 150GB/ Hour.
Full Offline Backup: It is a complete database backup without any Catalog.
Catalog (SUNDAY - The rest will be taken)
2. Online Backup
The DB is up and running with out effecting the user transactions. It is consistent and reliable with
redo logs that are generating during backup.
Whole Online Backup: The backup is taken fully and a catalog is opened to start the online
incremental backup.
Full Online Backup: It is complete database backup with out any catalogs.
Online Backup: It is consistent always with redo logs.
3. Incremental Backup
It is initiated from level0 backup and used when the database size is too big. It
can be online or offline.
4. Partial Backup
It is taken for a specific table during a patch (Especially HR Patches)
Backup type is defined by a parameter
Backup_mode = all
Backup_type = offline
Backup_dev_type = Tape or Disk
Backup_root_dir = H:\oracle\SID\sapbackup
All the above backups are performed by using brbackup.
BR ARCHIVE (initSID.sap)
It is used to backup the offline redolog file to tape or disk i.e. from ORAARCH directory to tape or
disk.
Archive_function = SAVE/ COPY/ DELETE
Archive_copy_dir = H:\Oracle\NWD
Tape_size= 100G
Volume_archive=NWDA01...... NWDA30...
Reads content from Log Buffer. Log writer writes to OrigLogA and OrigLog B, Mirror Log A, Mirror
Log B. When OrigLog A is full it is moved to OrigLog B When OraArch is full it is backed up to a tape
or disk.
- Archive function means the saving mechanism of log files.
- Log writer logs into OriglogA, OriglogB, MirrorLogA, MirrorLogB
-When online redo logs are full then Arch writes contents to Oraarch i.e
(Offline redologs) the content of oraarch is referred as offline redo logs.
- If Oraarch is full the archive gets stuck and the complete update mechanism stuck and users
encounter congestion.
- So the Oraarch content needs to be moved to alternative location on hourly, bi-hourly for every 4
hours or daily depending upon the frequency of updates.
- While copying Oracle provides various means of log save because we don't want the corruption of
logs.
DATABASE BACKUP:
*************************************************************************************
OS- Windows Server 2003-64Bit
SAP: ECC6.0 SR3
Database: Oracle 10.2.0.4.0 64-BIT
Backup Tool: BRTOOLS
Backup Type: offline_force
SID: DEC
Note: Take The Offline Backup of Database and Take Backup of Controlfiles.
Login as <SID>adm
Edit the init<SID>.sap file stored in /oracle/<SID>/102/database.
Select 1 for backup and you will see the following screen
Press c to continue
Enter
Now Backup is completed We can Restore the system with this backup .
Change the entries as shown in the figure above(Change "backup_dev_type = disk" and "backup_root_dir
= :\location" and save and quit.
Step2: Start Brtools utility from the command prompt by logging in as SIDadm on windows and oraSID in
Linux.
It will show you the summary of all the files which it will copy during this backup activity, Press "c" and
continue.
You can see the progress of your backup as shown in the screen above.
Finally once your backup is over, you can see the return code 0 on the screen which shows that your
backup was successfull.
Select 3 ~ Tablespace names (tablespace) .. []And provide the table space name, Example "
PSAPSR3700" etc.
Select 4 ~ Data file names (file) ......... [] and enter the detail of the datafile which you want
to move, Example = "/oracle/SID/sapdata1/sr3700_3/sr3700.data3
Please note the new destination should have the name starting with "sapdataXX" the location can be
any where.
Enter "c" continue 2 times
Enter "c"
This is just a simple example and please refer to SAP note for exact steps to move Oracle data file through Brtools
= Instance management
- Space management
- Segment management
- Backup and database copy
- Restore and recovery
- Check and verification
- Database statistics
- Additional functions
- Exit program
= Extend tablespace
- Create tablespace
- Drop tablespace
- Alter tablespace
- Alter data file
- Move data file
- Additional space functions
- Reset program status
Step2:
------------------------------------------------------------------------------Tablespace extension main menu
1
2
3
4
5
= Extend tablespace
- Show tablespaces
- Show data files
- Show disk volumes
* Exit program
Note: Please refer to the SAP/Oracle note for exact procedure for adding datafile, the blogger is not responsible for any issue arising by using
the above blog.
brspace -u / -f dbparam
If a developer want to develop any object in SAP namespace then system ask for developer access key.
That mean if a ABAP developer want to change standard SAP object then he need a access key. See
how to generate access key.
If a developer want to edit this object
Register object
Select the installation no as per the first screen shot then click on Register Access key will be generated.
After the successful registration of the object the the access key will be generated.
Netweaver Tools
Tools used in Netweaver 7.0
In Netweaver 7.0 we commony use following tools.
1. Templete Config Tool
2. Config Tool (Offline Tool)
3. Visual Admin Tool (Online Tool)
4. Integrated Log Viewer
Console based tool
5. Telnet Tool (Console base tool)
6. Jcmon
Software Deployment Manager is a tool widely used in WEBAS 640 and replaced by JSPM in Netweaver
7.0 and completely phased out in Netweaver 7.1.
It requires SDM password and port 50018 which runs based on JLaunch process.
it is accessed by using /usr/sap/SID/Instance/SDM/program/remotegui.bat in windows and remotegui.sh
in Linux operating system.it contains its own startup menu, inbox, log etc.
it is used to deploy and undeploy the support packages, business packages, add-ons etc in Netweaver
Java system.it is used to deploy the patches to Java Engine, File System (j2ee/cluster/server/apps) and
Database.It requires manual feed(frontend)unlike spam/saint/jspm which reads from EPS/in.
Due to its un-deployment feature it is discontinued from Netweaver 7.1. If a content is selected for undeployment it does not check the dependencies and the functionality of the deployed content is lost.
it is necessary to redeploy the content which is un-deployed (probably with an older version).
Example: Visual Composer is updated from patch level 12 to 15,but 15 found to be not compatible, so it is
un-deployed. un-deploy means the complete content of visual composer is un-deployed and visual
composer no more works. So redeploy the visual composer with version 12 or higher version 18
The SPAM/SAINT are incremental and they could not be reverted where as the java patches are
cumulative and replaces the content.The SDM deploys the files with extension *.sca,*.sda,*.war,*.ear etc.
sdm starts by reading the profile sdm_jstartup.propertes.it stores the information in sdmrepository.sdc and
backup the file in predefined intervals
SDM contains SDM Logs, Documentation, temp directory(used during export and import).
JSPM is a widely used tool to apply support packages in Java stack or Dual stack SAP system. Now a
days we use SUM (Software Upgrade Manager ) to update support packages or version upgrade.
Java Support package manager is consistent /stable/reliable tool used to deploy the patches. It works
similar to SPAM/SAINT and reads from EPS/in. It is also used to deploy the kernel.
it is accessed by path usr/sap/SID/DVEBMGS00/j2ee/jspm/go.bat
It requires SDM password and works only in the <SID>ADM environment.
Un-deployment function is not available in JSPM.(it handles the task of spam and saint)
It displays the source version and calculates the target version from EPS/in.
It is used to apply new usage types, support packages, add-ons, business packages, support
stack update along with SAP Kernel. It is also possible to skip the packages that are in queue
3200
Dispatcher Port
3300
Gateway Port
3600
3900
3901
4800
Secured Gateway
8000
Http Port
8001
Https Port
50000
50004
P4 Port
50008
Telnet Port
50018
SLD Port
3297
3298
SMD Port
3299
Router Port
1527
Important DB transaction
DB01 Analyze exclusive lock waits
DB02 Analyze tables and indexes
DB12 DB Backup Monitor
DB13 DBA Planning Calendar
DB15 Data Archiving: Database Tables
DBACOCKPIT - Contains relevant functionality from the old transaction
codes ST04, DB02, DB13, DB12, DB14, and DB13C
Spool Administration
SPAD Spool Management
SP00 Spool and Relate Area
SP01 Spool Control
SP02 Display output Requests
SP03 Spool: Load Formats
SPCC Spool Consistency check
SPIC Spool : Installation Check Tables
SP11 TemSe Contents
SP12 TemSe Administration
Step 6: Move the script file to the location where offline backup is taken.
Step 7: Rename the script file _NODE0000.scr to _NODE0000.clp so that we can edit the file.
Step 8: Create directory structure where you want to place sapdata. And copy the content from old
storage location.
Here is the example above, the files from sapdata3 and sapdata4 are moved from D Drive to F Drive, so
we copied the files after creating similar directory structure(D:\db2\SID to F:\db2\SID) and copied the
content from parent location to target location.
Step 9: Open the file SID_NODE00000.clp in an editor, and modify the storage as shown below,
STORAGE_PATH=,
Eg: STORAGE_PATH=D:\db2\ST1\sapdata4,F:\db2\ST1\sapdata4
Step13: Start SAP and DB now and check the new location from DB13 transaction.
Thanks,
Sharib Tasneem
Note: Please try this your own risk. This blog is only intended for sharing knowlodge only. Not to be used in production landscape.
If you find index quality to be below 60%, please follow the Step 4 to rebuild it.
Step 3: Improving Index Quality
You can enter the detail as shown below. Please make sure that your ID should be same during analysis.
And click on execute button.
Once, you rebuild the index, you can check to it using Step1 and Step2.
Step4: Repeat step number 2 & 3 for creating more operation mode.
Step5: Steps for Creating Instance and distributing work process.
Click on Opertaion Modes --> Maintain Instance --> Operation Mode View.
After that Click on Create New Instance and enter the following detail.
Instance Number
Start Profile
Instance Profile
Select the time range by double clicking on the duration and Click on "Assign".
Note: This blog is only for your reference, please refer to SAP note or SAP document for exact
Ex: D:\usr\sap\saprouter
Step4: Install the certificate in our saprouter by running
:\usr\sap\saprouter>sapgenpse.exe import_own_cert -c srcert -p local.pse
Now we have to create the credentials for the SAProuter with command
:\usr\sap\saprouter>sapgenpse seclogin -p local.pse -O
This will create a file called cred_v2 in the same directory.
Step5: Check if the certificate has been imported correctly
:\usr\sap\saprouter>Sapgenpse get_my_name -v -n Issuer
ISSUES
Solution:
Login as adm
To start,
sidadm>saposcol -l
To stop,
sidadm>saposcol -k
To check status,
sidadm>saposcol -s
But some time we have error messages like "Cannot create Shared Memory".
you can see that shared memory is assigned and the owner is root.
To clean this you need to execute below command:
ipcrm -m {Memory ID}
In above screenshot you can see that the memory id is 4.
So, the command to clear shared memory is
>ipcrm -m 4
In my example, I tried to clear memory with SIDadm user which is not the owner of the memory assigned.
So, clear this memory with root user.
Once it is cleared, you can try starting saposcol with the same command which is shown above.
Example is:
And once, it is started you can check the status with below command:
>saposcol -s.
Googled this and found many confusing solutions. Also, for your information, our servers were on AIX and
I am sure the solution will work on all linux flavors.
Solution:
Follow SAP note number, Note 446172 - SXPG_COMMAND_EXECUTE (program_start_error) in
DB13 section 8.
Login to system as root user and execute the command which is shown below in your SAP primary
application Server(CI):
rsh -l adm sapxpg
Ex: rsh -l SIDadm sapxpg
where hostname name is the hostname of the DB Server.
In my case it failed with permission denied error("Permission denied", "Can't establish connection" or a
password query). Now, follow the procedure to fix this error.
Open file /etc/hosts.equiv and make an entry about the other host and the user which should be allowed
to execute the command in Db server.
Ex:
hostname sidadm
hostname orasid
Where hostname is the hostname of your SAP Primary application Server and "sid" is the SID of your
SAP Server.
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
To fix this error, Please follow the step below:
Move to the location:
cd /usr/sap/SID/SUM/abap/bin
Execute the command: ./SAPup reset prepare
And then, once this command is executed successfully, delete SUM directory and extract fresh SUM files
in the same location and continue.
---------------------------------------------------------------END--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------