BR BACKUP

BRBACKUP:

The BRBACKUP tool allows an online or offline backup of the control file, of data files in individual or all Table spaces and, if necessary, of the online redo log files, as shown in the graphic “SAP – Oracle Database Backup Using cpio. BRBACKUP also saves the profiles and logs relevant for the Backup.

In addition to the actual backup, BRBACKUP also:

·         Changes the state of the database automatically, depending on the type of backup wanted (that is, online

·         or offline)

·         Checks the status of files

·         Optimizes the data distribution on the backup media. The algorithm for distribution is specially adapted to

·         The requirements of a database backup, that is, to backing up a small number of large files. The

·         distribution of data depends on whether you carry out a serial or parallel backup

·         Performs software compression, if the option is selected

·         Saves to hardware compressing tape stations, taking previously determined compression rates into

·         account

The BRCONNECT program makes sure that the database status required for the online or offline backup remains unchanged during the backup. The saving rates largely depend on the number of tape stations in use and the CPU load (particularly when software compression is used).You can also back up any files or directories you want. However, the backup of a directory is restricted to thefiles it contains. This enables backups of all SAP objects that do not belong to the database (for example,Programs, SAP start profiles, selected logs, and so on).

You can also perform database backups on several disks or remotely connected tape stations. BRBACKUPalso supports Oracle databases on raw devices and, Oracle Real Application Cluster (RAC), and OracleAutomatic Storage Management (ASM), including Oracle database appliances like Oracle Exadata Database Machine configurations.

Process:

1.     You identify what needs to be backed up.

Normally, you back up the complete database and the redo log files.

2.     You identify the database backup type that you require.

Normally, you perform an online and complete backup.

3.     You work out a backup cycle. We recommend a minimum cycle of 14 days, although 28 days is preferable. For example, with a 28-day cycle, you reuse the backup media after 28 days.

4.     You schedule regular backups.

5.     You verify the:

·        Backup tape readability, that is, a check on the contents of the media after the backup. Database block consistency, that is, a check on the database itself

·        If possible, run both types of verify daily, otherwise preferably weekly. At the least, be sure to run a verify once in each backup cycle.

·        You can back up the database and then verify both the backup media and the database using a single BRBACKUP command, brbackup -w use_dbv|use_rmv. The -w use_dbv option is also available in the action patterns of the DBA Planning Calendar. Be aware that a verify considerably extends backup run times.

·        To only verify database block consistency (that is, without a database backup), use the command brbackup -w only_dbv|-w use_dbv.

·        To verify table and index structures, use the command brconnect -f stats -v.

·        To verify the backed up redo log files, use the command brarchive -w| use_rmv.

BRARCHIVE:

You can use the BRARCHIVE tool to back up the offline redo log files, that is, the online redo log files saved to the archiving directory by Oracle. For more information, see the graphic “SAP – Oracle Database Backup. BRARCHIVE also saves all the logs and profiles of the backup process.

Reasons for backing up offline redo log files include the following:

·        In the event of a failure, a consistent database status can only be recovered, if all relevant redo log files are available.

·        The database system of a production SAP System has to be operated in the ARCHIVELOG mode to

·        Prevent overwriting of unsaved online redo log files. To protect the archive directory against overflowing, it

·        Has to be emptied regularly.

·        An online backup of data files is useless if the related redo log files are missing. Therefore, you must back

·        up the offline redo log files generated during the online database backup immediately after running BRBACKUP.

For security reasons, BRARCHIVE offers duplicate backup of offline redo log files (redundant serial or parallel backup is possible). On the basis of the logs, BRARCHIVE can make sure that redo log files are not deleted before they have been backed up and that the same files are saved once or twice.

BRARCHIVE allows the database administrator to continually back up offline redo log files. This means that the archiving directory, where Oracle places the offline redo log files, can be kept free by continually saving and then deleting saved redo log files. You can save offline redo log files on local or remote tape or on local or remote disk. Backup on disk is used particularly in the standby database environment.

DB MONITORING:

The database monitor checks important performance indicators in the database system, such as the database size, quality of the database buffer, and the database indexes.

The database monitor works with any database system supported by SAP. The monitor uses statistics that are provided by the database system with which you are working. You can access most of these statistics for the database system using the performance monitoring of the Computing Center Management Systems (CCMS).

You can use the Database Monitor to:

● Check the database during the operation of a production SAP system

● Analyze various problems

● Fetch information required for the database system settings

Although the database monitors accesses and evaluates database-specific statistics tables, it usually has the same appearance, regardless of which database system you are using. You can call the database monitor from any application server of the SAP system. The same data is displayed by the database monitor is the same on all application servers.

We can also monitor the database with alert monitor by below procedure:

Using the alert monitor, you can monitor the following database alerts:

● Space management – reorganization and space monitoring

● DB system check – consistency and profile

● Backup/restore

The alerts described in this section are all triggered automatically from DB System Checks in CCMS (Informix).

                                                                                                 

Applying SAP S Note

Applying a SAP Note (SNOTE)

Not all SAP Notes can be applied via the SNOTE transaction. Some are information only, providing no code corrections. Others entail corrections that can only be done manually. This latter type of SAP Note should be applied to your SAP system in conjunction with a trained ABAP programmer. Also, SAP recommends that SNOTE change requests NOT be transported into other systems. Use the SNOTE transaction in each SAP system that needs the correction, and delete the generated change requests since they should never be transported and could lock resources during application of other SAP Notes and support package application.

If you do not have a working OSS connection, you can download an OSS note from the SAP Marketplace using the SAP Download Manager and use the upload feature in SNOTE to load it into the SAP instance instead.

1. Log on to client 000 in the appropriate SAP system.

2. Go to transaction SNOTE.

3. On the Note Assistant - Version XXX/XXXX: Worklist screen, on the top-most menu bar click Goto → SAP Note download.

4. On the Note Assistant: Download Note popup, type the number of the SAP note in the Note number box and click the clock picture-icon. A SAP Note XXXXXX is being downloaded message will appear in the bottom status bar. If you get a communications error message, verify that saprouter is up and try again.

5. Once the SAP Note has been downloaded, it will appear on the Assistant - Version XXX/XXXX: Worklist screen under the SAP Notes → New navigation tree. The SAP Note can only be applied if there is a blue box with a black arrow to the left of the note number. If there is a gray diamond instead, the downloaded note cannot be applied or is not application for this SAP system.

6. To apply the SAP Note, on the Note Assistant - Version XXX/XXXX: Worklistscreen double click on the downloaded SAP Note number.

7. On the Note Assistant – Display Note XXXXXX screen, read the note text to see if there are any necessary manual tasks to be performed after the note is applied. When you are ready to apply the note, click on the clock picture-icon.

8. If there are any prerequisite SAP Notes which need to be applied to the SAP system before the downloaded SAP Note can be applied, a list will appear in a Load the following notes into your SAP system popup will appear. Click the clock picture-icon to download these prerequisite SAP Notes as well. If any of the prerequisite SAP Notes must be applied in parallel with the original downloaded SAP Note, a list will appear in a SAP Note queue to be Imported popup. Click the clock picture-icon to apply all the listed SAP Notes.

9. Before applying any SAP Notes to your SAP system, a Confirmation: SAP Noteread popup will appear. Once you have read the information contained in this popup, click the Yes button.

10. A standard Make repairs in foreign namespaces… popup will appear. Click the green √ to continue.

11. On the Prompt for transportable Workbench request popup, click the blank page picture-icon to create a new change request. On the Create Requestpopup, fill in the Short description and click the Save picture-icon. You will be returned to the Prompt for transportable Workbench request popup which contains the generated change request number for this system change. Click the green √ to continue.

12. On the Confirm changes popup, click the green √ to continue.

13. After the SAP Note has been applied to the SAP system, you will be returned to the Note Assistant - Version XXX/XXXX: Worklist screen. There is no completion message. Click the green √ and pencil picture-icon.

14. On the Set Processing Status for Note XXXXXX popup, click on the Completedline to turn “on” the radio button. Click the green √. You can now leave the SNOTE transaction. Modified programs, functions, etc. may require recompilation.

15. If the OSS note you applied changed a ABAP program, you must go to the SE38transaction and manually recompile the program. If it changed a function, go to transaction SE37 and click the Single Test button – this is enough to force the function to rebuild and you can back out of the SE37 transaction.

Post date: 2011-05-12 23:03:26
Post date GMT: 2011-05-12 17:33:26
Post modified date: 2011-05-12 23:03:26
Post modified date GMT: 2011-05-12 17:33:26

Export of Post and Page has been powered by [ Universal Post Manager ] plugin from www.ProfProjects.com

Kernel Up gradation in detail

What is a Kernel?

·         The Kernel is the central program which acts as an interface between SAP application and operating system.

·         The Kernel consists of the executable programs that reside under the path "/sapmnt/<SID>/exe" (UNIX) or \usr\sap\SID\SYS\exe\run (Windows)

·         These files help startup the R/3 system, initialize the memory, create buffers and start managing the requests from users and effectively utilizing of hardware resources.

·         The kernel is also responsible for starting and stopping all the application services like dispatcher, message server, collector etc.

Why Kernel Upgrade?

·         SAP Kernel is the core of the application. Like all other applications the Kernel contains the executable files (.EXE files for stating various processes in SAP).

·         Kernel is the heart of the operating system. It contains those files which are used to run every event in SAP. E.g.|: starting database, shutdowns of database, starting sap, shutdown of sap, saposcol, to uncar the sap files etc.

·         That's the reason why when a Kernel upgrade is done it means new versions of the various EXE files replace the older versions.

How to check Kernel Version?

There are many ways to check the Kernel Version -

Method 1) Logon to SAP system and go to SM51 à Release Notes
 

Method 2) Logon to SAP system and go to System tab in the menu bar and select Status
  

Method 3) Logon in operating system, switch to user <SID>adm and give the command disp+work

You can also give disp+work –version 
  

Download Kernel from Service Marketplace

·         Go to "SAP Service Marketplace. " (https:\\service.sap.com) You will need your OSS ID and password.

·         Then go to Downloads à SAP Support Packages -> Entry By Application Group -> SAP Kernel 6.00 64 Bit -> Select your OS (LINUX/WINDOWS/SOLARIS/AIX) -> Database Dependent and Database independent Kernel Patch.

·         Two SAR files SAPEXE.SAR and SAPEXEDB.SAR are downloaded from Service Marketplace.   Database Independent, Database Dependent: ORACLE

Kernel Upgrade Steps:

1.      Create a new Directory at OS level with enough space. Name of Dir can be "exe_new<ddmmyy>".

2.      Transfer these SAPEXEDB.SAR & SAPEXE.SAR files which you have downloaded to the new directory at OS level.

3.      Change your current directory to path .SAR files are created (cd /sapmnt/PR2/exe_new20122006). Check the directory path with command 'pwd' to ensure you are in the same dir (exe_new<ddmmyy>).

4.      Now uncompress these .SAR files by sapcar exe. The command used for the same would be

SAPCAR –xvf sapexe.SAR

SAPCAR –xvf sapexedb.SAR

5.      Now create one more directory in that path with the name "exe_old<ddmmyy>". Take the backup of existing kernel.Copy (only copy not move) the existing kernel from exe directory to "exe_old<ddmmyy>"

6.      Now stop the SAP application. (For kernel upgrade the shutdown of database is not essential but we need to stop the SAP application)

stopsap r3

7.      Then copy the files from the new kernel directory exe_new<ddmmyy> to the existing kernel directory exe

cp -rp /sapmnt/<SID>/exe_new<ddmmyy>/* /sapmnt/<SID>/exe/

8.      This will copy / replace all the files in the existing kernel directory with a new kernel files.

9.      Then check the kernel version from OS level by the command disp+work. It should show that the patch number has been increased.

10. Then logon to OS level as root (specific to UNIX). In the kernel directory, there is a script called saproot.sh. Execute this script

./saproot.sh <SID>

11. This script assigns the correct permissions to all the executable programs in the kernel such br* file etc...

12. Then start the SAP system

startsap r3

13. Now you can also check the kernel version level from SM51 or by selecting system à status

Connecting with another Human being  in a relation looks so easy for all. But it is the toughest thing for me in the whole world.

Need less to say I have some Unusual habits, yet all these socially acceptable people can't pick up hammers and smash their food  into bits publicly. I think people are so HOSTILE.