SAP Basis,Oracle and Redhat Linux Factory

SAP GUI installation on Mac OS

2013-06-01T03:06:00.001-07:00

SAP GUI for Java Installation

System Requirements

Make sure you have installed a supported Java Virtual Machine (JVM) and the necessary run time libraries.

Installation

PlatinGUI730MacOSX_2-20008876.JAR

The complete installation program is contained in the SAP GUI for Java package PlatinGUI-<Platform>-<Version>S.jar.
The package is signed and versioned. You can verify the integrity of the package with the jarsigner program included with your Java Virtual Machine to make sure the code is authentic and the package is not damaged.
jarsigner -verify -verbose PlatinGUI-<Platform>-<Version>S.jar

To verify the version and build details of the package you can ask for the version information:
java -jar PlatinGUI-<Platform>-<Version>S.jar version
To start the installation procedure just double click the installation package or if your environment does not provide direct support for starting jar packages invoke the installer from a command line interpreter.
java -jar PlatinGUI-<Platform>-<Version>S.jar [command] [options]
The installer knows three different commands install, uninstall and version.
The most important command is the install command, which is also the default if no command is specified.

The `install` command

java -jar PlatinGUI-<Platform>-<Version>S.jar install [options]
or equivalent
java -jar PlatinGUI-<Platform>-<Version>S.jar [options]
The install command can take several options.
General option syntax states that long option names start with two dashes and that boolean options are positive and denoted in lower case. Boolean options can be negated and the negative short option is denoted with an uppercase letter the long option name changes to --no<option>. Short options can not be clustered (so -fG is not correct but would be interpreted as a non existent option -f taking one parameter G). The space between an option and its parameter is not really required but recommended.

--help, -?: Print all installation options.
--force, -f, negated: --noforce, -F: Normally the installer will do nothing if it detects that this version of the SAP GUI for Java is already installed, -f forces a reinstallation.
--installdir <path>, -d <path>: Absolute path to installation directory if this option is omitted a reasonable platform dependent default location is used.
--verbose, -v, negated: --noverbose, -V: Provide verbose installation output on the console.
--standard, -s, negated: --nostandard, -S: Use standard options and install without user interaction. This is not a silent installation since progress indication and installation summary and all error dialogs are still displayed.This is well suited for automatic graphical installations.
--desktopicons, -m, negated: --nodesktopicons, -M: Install desktop menu and shortcuts. Per default this option is true so usually it is used as negated option -M, --nodesktopicons to prevent icons and menu entries to be created.
--gui, -g, negated: --nogui, -G: Use the graphical user interface for the installation. Per default this option is true so to turn off the graphical user interface use the negated form of the option -G, --nogui.If you turn off the graphical user interface you will get error messages and a short installation summary on the console.
--register, -r, negated: --noregister, -R: Centrally register the executable application as application path on Windows, as link into /usr/bin on Unix.
--inputfile <path>, -i <path>: Provide an installation response file to define installation parameters.
--logfile <path>, -l <path>: Write the installation log to the path.
--trace <tracekey1:tracekey2>, -t <tracekey1:tracekey>: Activate tracekey1 and tracekey2 during installation. Traces are always written to standard error.

The `uninstall` command

java -jar PlatinGUI-<Platform>-<Version>S.jar uninstall
The uninstall command removes an installed version of the SAP GUI for Java.

The `version` command

java -jar PlatinGUI-<Platform>-<Version>S.jar version
The version command just lists version information for the installation package.

Build date           : 2012-08-16 06:01:11 +0200
Build Info           : ldm046, 730_REL, 1353310
Product type         : 1
Numeric Version      : A073000020200
Short Version Number : 7.30beta2
Long Version Number  : 7.30 beta 2
Short Version        : SAPGUI7.30beta2
Long Version         : SAP GUI 7.30 beta 2
Full Version         : SAP GUI for Java 7.30 beta 2
Official Version     : SAP GUI for the Java Environment 7.30 beta 2

Installation Response File

You can automate the installation process by providing an installation response file using the -i <responsefile> option to the install command.
Available Properties:

installdir=<path> or installpath=<path>: Absolute path to installation directory, the special value default installs into the platform dependent default location (same as -d <path>).
disableui=true: Disables the interactive graphic installation program. All installation parameters have to be supplied using an installation response file or as command line options. All installation messages are written to standard output and standard error (same as -G).
automatic=true: If all necessary parameters are specified only show progress indication and error dialogs (same as -s).
reinstall=true: If this version of the SAP GUI for Java is already installed it is silently reinstalled and the installation proceeds as normal (same as -f).
uninstall=true: Remove the SAP GUI for Java installation if this version is installed, then exit (corresponds to the uninstall command).
logfile=<path>: Absolute path to installation log file including file name (same as -l <path>).
noshortcuts=true: Do not create desktop menus and desktop shortcuts (same as -M).
registerapplication=true: Centrally register executable application as application path on Windows, as link into /usr/bin on Unix (same as -r).

The file format is a list of lines with each one describing a property as a key value pair. Key names are delimited by "=" and ":". These characters can be escaped in key names and in the value text using "\" as escape character. Therefore a literal "\" also has to be escaped.
Complete lines can be commented with "#".
Example of a Typical Response File:

# Example of a typical installation response file
# suppress user interaction
disableui=true
# install to the default path
installidir=default
# reinstall gui if already present
reinstall=true

Web Deployment

Web installation is triggered by the content of a web page that was set up by the system administrator. If there is currently no SAP GUI for the Java Environment installed on the front-end computer, or if the version does not meet the requirements specified on the web page, the automatic installation is triggered. In order for this to work, your web browser security settings must be set to enable download and installation of controls and executable files.
The SAP GUI for the Java Environment applet will be downloaded and started from the website provided.
In order to run the applet with the required privileges, its signature has to be verified. Click 'Grant always' or 'Grant this session' on the certificate verification dialog. This will ensure that the GUI applet code can run as a trusted applet (this dialog only appears if the certificate has not been generally accepted by clicking 'Grant always'). See Background Information: Signed Applets for more information)
If there is no SAP GUI for the Java Environment installed or if the installed version is older than the version requested on the web page, the installation will be started.
When the installation has finished, the SAP GUI for Java is started.

Browser Default Version

Several versions of SAP GUI for the Java Environment can be installed and run on a single front-end computer in parallel. However, only one of the installed versions can be used within the web browser at any one time. This dedicated version is called the "browser default version".
By default, the browser default version is always the most recent version installed.
You can configure the current browser default version by using the 'Version Options' dialog. Start SAP GUI for the Java Environment as a standalone application and choose 'Options/Version' from the logon window menu to open this dialog. Use the 'Default version' drop down list box to choose the default browser version.

Installation Log File

Each installation of SAP GUI for the Java Environment writes a detailed protocol of all installation activities to the 'sapgui.log' log file. Please consult this file if you encounter any installation problems.The file is located in a place that is platform-specific:

Windows and UNIX platforms:: <home directory>/sapgui.log
Mac OS X:: <home directory>/Library/Logs/sapgui.log

Remove a SAP GUI for Java installation

If the installation user interface detects that this version of the SAP GUI for Java is already installed it allows to remove the installation or to reinstall.
On all platforms you can also use the command line installer to remove a installed version by calling
java -jar PlatinGUI-<Platform>-<Version>S.jar uninstall
On Win32 platforms you can remove a centrally-installed SAP GUI for the Java Environment using the Software control panel. User installations are not centrally-registered under Windows and can just be deleted (for Windows Vista specific information please see "Windows Vista Deinstallation").

`PATH` and Environment

By default, the GUI start scripts use the Java Runtime Environment found in PATH (see requirements) or the application registration. If you want to use a different Java Runtime Environment, you may specify it using the PLATIN_JAVA environment variable which points to the Java executable to be used for example: /usr/bin/java. You can also use PLATIN_JAVA to provide the Java Runtime Environment with additional options.

You can add the bin directory of the SAP GUI installation to your PATH in order to allow the invocation of the SAP GUI for Java from everywhere.

ora-27101 shared memory realm does not exist linux No such file exists. R3trans -d error 0012

2013-04-03T22:32:00.004-07:00

One of the silly error after installation of SAP with Oracle 9i,10g on both RHEL 4 and RHEL 5.This error wasted our one week.But at last now we'are able to find solution.

Description of error:

ORA-01034: ORACLE not available

ORA-27101: shared memory realm does not exist

After Installation of SAP ECC 5.0 ,on successful startup of Database.

Error : R3trans -d command failed with error 0012 .No connection possible

Here's the Solution:

Oracle docs note this about ORA-27101:

ORA-27101: shared memory realm does not exist

Cause: Unable to locate shared memory realm

Action: Verify that the realm is accessible

MOSC offers valuable information regarding ORA-27101. ORA-27101 is often thrown along with ORA-01034 during database installation. ORA-27101 is also seen after installation is complete, when attempting to use SQL*Plus.
To resolve this issue with ORA-27101, you should be sure that ORACLE_HOME andORACLE_SID are correct, and ORACLE_HOME should not have trailing slash.

For checking on trailing trash:

su - orasid

$ echo $ORACLE_HOME
$ /oracle/SID/102_32/ << Incorrect

$ echo $ORACLE_HOME
$ /oracle/SID/102_32 << Correct

For ORACLE_SID:

$ echo $ORACLE_SID
SID

These steps deadly resolve your this issue.

Also refer two SAP NOTES :

Note 491174 - Composite SAP note for ORA-01034

Note 583861 - UNIX: Errors due to Oracle executable

Thanks,

Gaurav

MOS-01022 sap error

2013-01-29T00:02:00.000-08:00

While SAP ECC 5.0 Installation at DB Instance Phase on database extraction getting error MOS-01022.

Solution: Check only your RAM ...RAM ...RAM only RAM issue.

SAP BASIS ERROR during unicode conversion:error during conversion of cluster item

2012-07-10T21:36:00.001-07:00

(DB) INFO: REGUC created #20120710113304

myCluster (55.23.Imp): 1596: inconsistent field count detected.

myCluster (55.23.Imp): 1599: nametab says field count (TDESCR) is 179.

myCluster (55.23.Imp): 1602: alternate nametab says field count (TDESCR) is 181.

myCluster (55.23.Imp): 1270: unable to retrieve nametab info for logic table REGUP .

myCluster (55.23.Imp): 8166: unable to retrieve nametab info for logic table REGUP .

myCluster (55.23.Imp): 2687: failed to convert cluster data of cluster item.

myCluster: REGUC **700****20060206****00001O**** ****1000****0000310014**** **** ****0100000002**

myCluster (55.23.Imp): 324: error during conversion of cluster item.

myCluster (55.23.Imp): 327: affected physical table is REGUC.

(CNV) ERROR: data conversion failed. rc = 2

(DB) INFO: disconnected from DB

/sapmnt/PRD/exe/R3load: job finished with 1 error(s)

/sapmnt/PRD/exe/R3load: END OF LOG: 20120710113310

Solution :

1. Incorrect data should be removed from source system before export of ABAP Database System.

2. At target System stop the current database import phase and perform under

/tmp/sapinst_instdir/ECC50/COPY/IMPORT/SYSTEM/ABAP/ORA/UC/DB

and

Modify DDL<dbs>.TPL (<dbs> = ADA, DB2, DB4, DB6, IND, MSS, ORA) before the R3load TSK files are generated; search for the keyword "negdat:" and add "REGUC" and "VER_CLUSTR" to this line.

Modify the TSK file (most probably SAPCLUST.TSK) before the R3load import is (re-)started; search for the lines starting with "D REGUC I" and "D VER_CLUSTR I" and change the status (i.e. "err" or "xeq") to "ign" or remove the lines.

Also Refer SAP Note Number : 967124

3. Restart the database import phase .

CJS-00030 SAP Installation error.

2012-07-04T08:47:00.000-07:00

First you will have to reset your installation and delete installation log directory.

1- Be sure that on the root session you are using to launch sapinst for DBInstance there is no ORACLE_HOME environment variable set.

2- Check your oraInst.loc file (see SAP note 350251), adapt it so that

inventory_loc=/oracle/oraInventory

and create directory if necessary. This avoid problems on unix with previous installations of oracle.

######################################################

Also

ORACLE_HOME=/opt/oracle/product/102_32 is not a valid path.
it should be like
/oracle/[SID]/102_32

#################################################################

Also comment out environment variable under file

vim /root/.bash_profile

#ORACLE_HOME=/oracle/SID/102_32

ORA-00904 error Solution at the time of SAP Installation

2012-07-02T21:53:00.001-07:00

ORA-00904: "SYS"."DBMS_EXPORT_EXTENSION"."FUNC_INDEX_DEFAULT": invalid identifier

[Problem]

Export: Release 9.2.0.8.0 - Production on Wed Jul 25 10:47:29 2007

Connected to: Oracle9i Enterprise Edition Release 9.2.0.5.0 - 64bit Production
With the Partitioning, OLAP and Oracle Data Mining options
JServer Release 9.2.0.5.0 - Production
Export done in US7ASCII character set and AL16UTF16 NCHAR character set
server uses UTF8 character set (possible charset conversion)

About to export specified tables via Direct Path ...
Current user changed to DBAPL
. . exporting table RPT_LOCAL__01 1012208 rows exported
EXP-00056: ORACLE error 904 encountered
ORA-00904: "SYS"."DBMS_EXPORT_EXTENSION"."FUNC_INDEX_DEFAULT": invalid identifier
Export terminated successfully with warnings.

[Root Cause]

It caused by different DB version in the server , as below two version is installed:

DB1 V9.2.0.8 , while DB2 is 9.2.0.5

In operator id 's env , the ORACLE_HOME is point to 9.2.0.8, caused using higher version exp to exp data from lower version db.

[solution]
in the script , explicitly specify the path of exp , i.e:

/software/oradb1/product/9.2.0/bin/exp $RPT_CONNECT@$RPT_DB file=$expfile log=$LOGFILE direct=y recordlength=65535 buffer=10240000 compress=N tables=${tab_name} statistics=none

Today 21-Jan-2009, hit another similar case. get new findings from metalink

Doc ID:

358508.1

Applies to:

Oracle Server - Enterprise Edition - Version: 9.2.0.1 to 10.2.0.1
This problem can occur on any platform.

Symptoms

Export fails with:

EXP-00056: ORACLE error 904 encountered
ORA-00904: "SYS"."DBMS_EXPORT_EXTENSION"."FUNC_INDEX_DEFAULT": invalid identifier

Changes

A patchset was recently installed against the database.

Cause

After the patchset installation, the data dictionary components have not been upgraded to the patchset release (e.g. 10.1.0.4)

A patchset (e.g. 10.1.0.4) was applied to an existing ORACLE_HOME install but one or more of the patchset steps were not performed per the patchset readme to bring the database components up to the same version as the patched software as shown in DBA_REGISTRY.

If the database components versions do not match the software and the running instance, then the exp utility fails as it finds an earlier version of the exp packages in the database.

Solution

Follow the Post-Installation Tasks section of the Oracle Database Server Patch Set Notes to run the catpatch.sql script with the database started in migrate mode and then retry the export.

Connect to the database as SYSDBA and run:

SQL> STARTUP MIGRATE
SQL> SPOOL patch.log
SQL> @?/rdbms/admin/catpatch.sql
SQL> SPOOL OFF
SQL> SHUTDOWN
SQL> STARTUP

2012-07-02T21:48:00.004-07:00

Step By Step Update SAP Kernel in UNIX based

1. Login as root

2. Make new backup directory
cd /
mkdir 09062010 (Date based)

3. Create latest kernel backup
cp -pr /sapmnt/SID/exe/* /09062010

4. Compare the original kernel and the backup
du -sk /sapmnt/SID/exe/  840413 /sapmnt/SID/exe #
du -sk /SIDkernel_10102007  841992 /SIDkernel_10102007 #

5. Make new shadow kernel directory
cd /
mkdir kernel

6. Copy the new downloaded kernel files into /kernel

7. Unpack the new downloaded kernel in folder /kernel
SAPCAR -xvf SAPEXE_175-20000221.SAR
SAPCAR -xvf SAPEXEDB_175-20000223.SAR

8. Login as sidadm

9. Stop the SAP System
stopsap

10. Stop saposcol
saposcol -k

11. Login as root

12. Go to the current kernel directory
cd /usr/sap/SID/SYS/exe/run

13. Copy all extracted support packages into this folder
cp -pr /kernel/* /usr/sap/SID/SYS/exe/run

14. Copy back the original file saproot.sh into this folder.
cp -p /09062010/saproot.sh /usr/sap/SID/SYS/exe/run

15. Go to the current kernel directory
cd /sapmnt/SID/exe
Then run:
./saproot.sh SID

16. Login as sidadm

17. Start the saposcol service
saposcol

18. Start the SAP system
startsap

NOTE: Download the latest patch level from https://websmp109.sap-ag.de/support path Support Packages and Patches - Entry by Application Group Additional Components SAP Kernel SAP KERNEL 32-BIT UNICODE SAP KERNEL 6.40 32-BIT UNICODE

Download only two .SAR files e.g

SAPEXE_175-20000221.SAR
SAPEXEDB_175-20000223.SAR

#Database independent

#Oracle

2012-07-02T21:42:00.003-07:00

Rebuilding of Index in SAP

1 In transaction SE14, enter the name of your table and select Edit
2) On the resulting screen, select Indexes.
3) Select the Index you wish to rebuild
4) Select the appropriate Execute Database Operation
5) Go back (using the green arrow) to the Table definition
Repeat steps 2 --> 5 till all indexes have been rebuilt

2 Check statistics in transaction DB20

2012-07-02T21:03:00.000-07:00

VB Script to convert Excel sheet into .csv format

Open Notepad, create a file called XlsToCsv.vbs and paste this in:

if WScript.Arguments.Count < 2 Then

WScript.Echo "Error! Please specify the source path and the destination. Usage: XlsToCsv SourcePath.xls Destination.csv"

Wscript.Quit

End If

Dim oExcel

Set oExcel = CreateObject("Excel.Application")

Dim oBook

Set oBook = oExcel.Workbooks.Open(Wscript.Arguments.Item(0))

oBook.SaveAs WScript.Arguments.Item(1), 6

oBook.Close False

oExcel.Quit

WScript.Echo "Done"

Then from a command line, go to the folder you saved the .vbs file in and run:

XlsToCsv.vbs [sourcexlsFile].xls [destinationcsvfile].csv

This requires Excel to be installed on the machine you are on though.

2012-07-02T20:50:00.003-07:00

VMware Tools for Linux Guests

On a Linux guest, you can install VMware Tools within X or from the command line

· Installing VMware Tools within X

· Installing VMware Tools from the Command Line with the Tar Installer

· Installing VMware Tools from the Command Line with the RPM Installer

Installing VMware Tools within X

You can install VMware Tools within X using the .tar installer in a terminal window. See Installing VMware Tools from the Command Line with the Tar Installer.

To install VMware Tools from X with the RPM installer:

1. Choose VM > Install VMware Tools.

The guest operating system mounts the VMware Tools installation virtual CD.

2. Double-click the VMware Tools CD icon on the desktop.

Note: In some Linux distributions, the VMware Tools CD icon may fail to appear when you install VMware Tools within an X windows session on a guest. In this case, you should continue installing VMware Tools as described in Installing VMware Tools from the Command Line with the Tar Installer, beginning with step 3.

3. Double-click the RPM installer in the root of the CD-ROM.

4. Enter the root password.

5. Click Continue.

The installer prepares the packages.

6. Click Continue when the installer presents a dialog box saying Completed System Preparation.

A dialog appears for Updating system, with a progress bar. When the installer is done, VMware Tools are installed. There is no confirmation or finish button.

7. In an X terminal, as root (su -), configure VMware Tools.

vmware-config-tools.pl

Respond to the questions the installer displays on the screen. Press Enter to accept the default value.

Note: Be sure to respond yes when the installer offers to run the configuration program.

8. Launch the VMware Tools background application:

vmware-toolbox &

Note: Some guest operating systems require a reboot for full functionality.

Installing VMware Tools from the Command Line with the Tar Installer

The first steps are performed on the host, within Workstation menus:

1. Power on the virtual machine.

2. After the guest operating system has started, prepare your virtual machine to install VMware Tools.

Choose VM > Install VMware Tools.

The remaining steps take place inside the virtual machine.

3. As root (su -), mount the VMware Tools virtual CD-ROM image, change to a working directory (for example, /tmp), uncompress the installer, then unmount the CD-ROM image.

Note: Some Linux distributions automatically mount CD-ROMs. If your distribution uses automounting, do not use the mount and umount commands below. You still must untar the VMware Tools installer to /tmp.

Some Linux distributions use different device names or organize the /dev directory differently. If your CD-ROM drive is not /dev/cdrom or if the mount point for a CD-ROM is not /mnt/cdrom, you must modify the following commands to reflect the conventions used by your distribution.

mount /dev/cdrom /mnt/cdrom

cd /tmp

Note: If you have a previous installation, delete the previous vmware-distrib directory before installing. The default location of this directory is
/tmp/vmware-tools-distrib.

4. Untar the VMware Tools tar file:

tar zxf /mnt/cdrom/VMwareTools-5.0.0-<xxxx>.tar.gz

umount /dev/cdrom

Where <xxxx> is the build/revision number of the VMware Workstation release.

Note: If you attempt to install a tar installation over an rpm installation — or the reverse — the installer detects the previous installation and must convert the installer database format before continuing.

5. Run the .tar VMware Tools installer:

cd vmware-tools-distrib

./vmware-install.pl

Respond to the configuration questions on the screen. Press Enter to accept the default value.

6. Log off of the root account.

exit

7. Start X and your graphical environment.

8. In an X terminal, launch the VMware Tools background application.

vmware-toolbox &

Note: You may run VMware Tools as root or as a normal user. To shrink virtual disks, you must run VMware Tools as root (su -).

Installing VMware Tools from the Command Line with the RPM Installer

The first steps are performed on the host, within Workstation menus:

1. Power on the virtual machine.

2. After the guest operating system has started, prepare your virtual machine to install VMware Tools.

Choose VM > Install VMware Tools.

The remaining steps take place inside the virtual machine.

3. As root (su -), mount the VMware Tools virtual CD-ROM image, change to a working directory (for example, /tmp), uncompress the installer, then unmount the CD-ROM image.

mount /dev/cdrom /mnt/cdrom

cd /tmp

Note: If you have a previous installation, delete the previous vmware-distrib directory before installing. The default location of this directory is
/tmp/vmware-tools-distrib.

4. At the command prompt, enter:

rpm -Uhv /mnt/cdrom/VMwareTools-5.0.0-<xxxx>.i386.rpm

umount /dev/cdrom

Where <xxxx> is the build/revision number of the VMware Workstation release.

Note: If you attempt to install an rpm installation over a tar installation — or the reverse — the installer detects the previous installation and must convert the installer database format before continuing.

5. Configure VMware Tools:

vmware-config-tools.pl

Respond to the questions the installer displays on the screen. Press Enter to accept the default value.

6. Log off of the root account.

exit

7. Start X and your graphical environment.

8. In an X terminal, launch the VMware Tools background application.

vmware-toolbox &

Note: You may run VMware Tools as root or as a normal user. To shrink virtual disks, you must run VMware Tools as root (su -).

Starting VMware Tools Automatically

You may find it helpful to configure your guest operating system so VMware Tools starts when you start your X server. The steps for doing so vary depending on your Linux distribution and your desktop environment. Check your operating system documentation for the appropriate steps to take.

For example, in a Red Hat Linux 7.1 guest using GNOME, follow these steps.

1. Open the Startup Programs panel in the GNOME Control Center.

Main Menu (click the foot icon in the lower left corner of the screen) > Programs > Settings > Session > Startup Programs

2. Click Add.

3. In the Startup Command field, enter vmware-toolbox.

4. Click OK, click OK again, then close the GNOME Control Center.

The next time you start X, VMware Tools starts automatically.

Uninstalling VMware Tools

To remove VMware Tools from your Linux guest operating system, log on as root (su -) and enter the following command:

· From a tar install

vmware-uninstall-tools.pl

· From an RPM install

rpm -e VMwareTools

2012-07-02T20:49:00.003-07:00

How to reset SAP ddic & sap* passowrds on client 000

I install sapr3 4.7 and on WIN 2003& orale Db and after installation I set the the passwords for SAP* & DDIC on client 000 then I forget it. Pls help me how to reset them to login to the system by client 000& i in form u i can login with 001 & 066
=====
## Rest the password of 'sap*' in client 000
## Log on to oracle database using sqlplus.
sqlplus / nolog
SQL>connect /as sysdba
SQL>update <SchemaOwner>.USR01 set bname='SAP*1' where bname='SAP*' and MANDT=000;
## [ e.g.: update SAPR3.USR01 set bname='SAP*1' where bname='SAP*' and MANDT=000; ]
## [e.g. : update SAP<SID>.USR01 set bname='SAP*1' where bname='SAP*' and MANDT=000;]
SQL>commit;
SQL>exit
## This will reset the user SAP* in client 000 . After loggin in client with user SAP* change the passwords for other users.
## You can user client number of your respective client.
## Please note do not reset any other user than SAP* with this method.

2012-07-02T20:31:00.001-07:00

SAP R/3 System Parameters

This overview describes how security and controls can be implemented through system parameters. System parameters are used to maintain configuration over the operation of the SAP system. System parameters may define key settings for the whole system on which SAP runs, individual hosts systems (e.g. configuration for only one of many application servers) or the instances that are running on these servers. The majority of system parameters ensure that SAP operates effectively on the customer’s preferred hardware, operating system and database platforms. System parameters also control how SAP operates and provides system wide control over some aspects of Security. System parameters are set using transaction RZ10. To make the parameters globally effective set them in the default profile, DEFAULT.PFL. To make them instance-specific, you must set them in the profiles of each application server in your R/3 System. System parameters can be reviewed with transaction TU02 or from the standard SAP report RSPARAM using transaction SA38.

Incorrect Logon, Default Clients and Default Start Menus

· Login/fails_to_session_end (default value - 3)

defines the number of times a user can enter an incorrect password before the system terminates the logon attempt.

· Login/fails_to_user_lock (default value - 12)

the number of times a user can enter an incorrect password before the system locks the user. If the system locks, an entry is written to the system log, and the lock is released at midnight.

· Login/failed_user_auto_unlock (default value - 1)

unlocks users who are locked by logging on incorrectly. The locks remain if the parameter value is 0.

· Login/system_client

This parameter specifies the default client. This client is automatically filled in on the system logon screen. Users can enter a different client.

· Login/ext_security

Since release 3.0E, external security tools such as Kerberos or Secude have managed R/3 System access. If this parameter is set, an additional identification can be specified for each user (in user maintenance) where users log on to their security system. To activate, set the value to X.

· rdisp/gui_auto_logout (default value - 0)

Maximum time allowed between input from the GUI before the frontend is automatically logged out. The value is set in seconds and the value of zero is used when this facility is not active.

· Start_menu

This parameter specifies the default start menu for all users and can be overwritten with the user-specific start menu (transaction SU50). The default is S000, and this value can be set to any other area menu code.

Password Security

System profile parameters define the minimum length of a password and the frequency with which users must change passwords.

· Login/min_password_lng

minimum password length. The minimum is three characters and the maximum eight characters.

· Login/password_expiration_time

number of days after which a password must be changed. The parameter allows users to keep their passwords without time limit and leaves the value set to the default, 0.

· To prevent use of a certain password, enter it in table USR40. Maintain this table with transaction SM30. In USR40, you may also generically specify prohibited passwords.

There are two wild-card characters:

– ? means a single character

– * means a sequence of any combination characters of any length

Examples:

– 123* in table USR40 prohibits any password that begins with the sequence 123.

– *123* prohibits any password that contains the sequence 123.

– AB? prohibits passwords that begin with AB and have an additional character, such as ABA, ABB, and ABC.

Securing SAP* user master record

· login/no_automatic_user_sapstar

By default SAP is installed with a user master record SAP*. This user has the profile SAP_ALL with access to all transactions and programs in SAP. By default if this user master record is deleted then SAP allows logon using SAP* and a password of ‘PASS’. Although the user master record does not exist, SAP grants unrestricted system access privileges to SAP*. By setting this parameter value to ‘1’ this ‘backdoor’ access is blocked in the event the SAP* user master record is deleted. Prior to version 4.0 this parameter was login/no_automatic_user_sap*.

Tracing Authorizations

• Auth/check_value_write_on (default value - 0)

Authorization failures can be evaluated immediately they occur by running transaction SU53. This functionality is only active if the parameter is set to a value greater than zero in the system profile parameter.

• Auth/authorization_trace (version 4.0B onwards - default value - ‘N’)

When the parameter is set, any authorization checks performed are validated against existing entries in table USOBX. If the table does not contain the transaction/authorization object combination, then a new entry is added to the SAP reference table (i.e. USOBT not USOBT_C). Due to significant performance issues, SAP does not recommend this parameter being set in customer systems.

• Auth/test_mode (version 4.0B onwards - default value ‘N’)

When activated every authority check starts report RSUSR400. However SAP recommends not activating this parameter as the system is paralyzed if syntax errors occur in running the report and it has a significant performance impact .

Authority Check De-activation

• Auth/no_check_on_sucode (version 3.0E to version 3.1H - default value ‘N’), Auth/no_check_on_tcode (version 4.0 onwards - default value - ‘N’)

From release 3.0E, the system checks on object S_TCODE. In upgrades from versions prior to 3.0E to set this flag to ‘Y’ to ensure that old profiles operate in the new system. By default, the function is inactive.

The flag should not normally be switched on because of the degradation in security that results.

• Auth/no_check_in_some_cases (version 3.0F onwards -default value depends on release)

This parameter needs to be set to ‘Y’ for installation of the profile generator. It defines the use of table USOBT in the authority checks undertaken and allows authority checks to be disabled in individual transactions. Whilst SAP recommends switching off unnecessary authority checks, the full impact of this should be considered carefully.

• Auth/object_disabling_active (default value -‘N’)

Whilst_no_check_in_some_cases allows authority checks to be switched off in for individual transactions, this parameter allows checks on individual objects to be switched off globally within SAP. It is recommended that this parameter is not set.

Number of Authorizations in User Buffers

• Auth/auth_number_in_userbuffer

When a user logs onto SAP, the authorizations contained in the user’s profiles are copied to a user buffer in memory. The maximum number of authorizations copied is set by this parameter. The size of the buffer must always exceed the maximum number of authorizations as authorization checks are made only against those in the buffer.

The default value is 800, but this can be set to between 1–2000. Refer to OSS notes 84209 and 75908 for more detailed information regarding changes to the size of the user buffer.

Transaction SU56 shows the contents of the user’s user buffer and a total for all the authorizations in a user master record.

Table, ABAP and RFC system parameters

• Rec/client (default value - ‘N’)

The parameter switches automatic table logging on. Images of the table before and after are logged rather than just changes and so consideration to which tables are to be logged and log volumes must be made before using this as part of a control solution.

• Auth/rfc_authority_check (default value - ‘1’)

The parameter determines how object S_RFC is checked during RFC calls. The object has three fields, activity, the name of the function being called and the function group in which the function resides. The parameter defines whether S_RFC object is checked and if so, whether the function group field is included in the validation.

Value = 0, no check against S_RFC

Value = 1, check active but no check for SRFC-FUGR

Value = 2, check active and check against SRFC-FUGR

• Auth/system_access_check_off (default value - ‘0’ - check remains active)

This parameter inactivates the automatic authorization check for particular ABAP/4 language elements (file operations, CPIC calls, and calls to kernel functions). This parameter ensures the downward compatibility of the R/3 kernel.

Useful Transactions

• TU02 Shows current parameters for all hosts and gives a history of changes to parameters

• RZ10 Maintain system parameters

• RZ11 View single system parameters and their functional area.

• SU56 Shows all authorizations a user has in their user master record and the total number. This is useful to

identify apparent authorization failures caused by user buffer overflow.

Useful Reports

RSPARAM displays all system parameters set and applicable to the system and instance in which it is run.

From version 4.0 the RSUSR003 report also shows the settings for some of the critical password parameters. The report also shows identifies whether SAP*, DDIC or CPIC have insecure passwords by comparing value of the encrypted password field with the encrypted values of the standard shipped passwords. It also shows whether the SAP* user master record is absent from any clients.

2012-07-02T20:27:00.004-07:00

Kernel Parameters for Installation of SAP on Redhat Linux 5

Add the following lines to the "/etc/sysctl.conf" file.

kernel.shmall = 2097152

kernel.shmmax = 2147483648

kernel.shmmni = 4096

# semaphores: semmsl, semmns, semopm, semmni

kernel.sem = 250 32000 100 128

fs.file-max = 65536

net.ipv4.ip_local_port_range = 1024 65000

net.core.rmem_default=262144

net.core.rmem_max=262144

net.core.wmem_default=262144

net.core.wmem_max=262144

2012-07-02T20:25:00.001-07:00

SAP Transaction SU24

SU24 gives you the list of authorization objects that are checked when an tocde is executed. For example when you enter tcode mbo2 there are many authorization objectschecked for the transaction to be executed successfully. This tcode gives all of the authorization objexts that are checked or included for checking during the execution of this tcode. A security consultant will have acces to su24 transaction. This is helpful when dealing with su53 dumps.
Goto transaction Su24 you will end up with a screen as shown below

Then enter transaction like ME28 ( int the figure different Tcode is used)
and press F8 key. Then you will see the following screen. Here you can see list of objects that has will be checked during execution of the tcode. The objects with proposal values (last column) set to YS will be checked and are added to the profile when the tcode is entered in role menu.
Click on the image to see full view.
And the color indicator (first column) green === globally active
light gray OR DIAMOND shape == globally inactive objects which are not checked in any case.

The objects with proposal YS are checked definitely. The objects with proposal NO will not be checked normally. They will be checked based on the input entered in the tcode.

as you can see the last but one column is global check indicator which indicates whether the object is disabled globally or not.

Re-Creating PSAPTEMP on Oracle

2012-07-02T20:19:00.001-07:00

Re-Creating PSAPTEMP on Oracle

Following procedure helps you to re-create Temporary Tablespace PSAPTEMP while system is running.

SQL> CREATE TEMPORARY TABLESPACE temp2
2  TEMPFILE '/oracle/<SID>/sapdata<n>/temp2_1/temp2.data1' SIZE 5M REUSE
3  AUTOEXTEND ON NEXT 1M MAXSIZE unlimited
4  EXTENT MANAGEMENT LOCAL UNIFORM SIZE 1M;

Tablespace created.

SQL> ALTER DATABASE DEFAULT TEMPORARY TABLESPACE temp2;

Database altered.

SQL> DROP TABLESPACE PSAPTEMP INCLUDING CONTENTS AND DATAFILES;

Tablespace dropped.

SQL> CREATE TEMPORARY TABLESPACE PSAPTEMP
  2 TEMPFILE '/oracle/<SID>/sapdata<n>/temp_1/temp.data1' SIZE 500M REUSE
  3 AUTOEXTEND ON NEXT 100M MAXSIZE unlimited
  4  EXTENT MANAGEMENT LOCAL UNIFORM SIZE 1M;

Tablespace created.

SQL> ALTER DATABASE DEFAULT TEMPORARY TABLESPACE PSAPTEMP;

Database altered.

SQL> DROP TABLESPACE temp2 INCLUDING CONTENTS AND DATAFILES;

Tablespace dropped.

2012-07-02T02:42:00.002-07:00

Redhat SquirrelMail Configuration step by step

Installation and configuration of SquirrelMail on a RedHat/CentOS/Fedora Linux based mail server with Sendmail mail server and Apache web server.
Scenario:
Primary Mail Server: linuxbox4 (192.168.0.14)
Domain Name: abc.com
Trusted IP Pool: 192.168.0.0/24
Note: Replace domain name and system name and IP according to your scenario.

Prerequisites:
1. DNS is configured with proper MX record.
2. All necessary packages/ softwares are installed.

Step 1:
Configure all service to start at boot time.
chkconfig sendmail on
chkconfig httpd on
chkconfig dovecot on

Step 2:
Configure /etc/hosts file. In this scenario /etc/hosts file should look like this:
192.168.0.14 linuxbox4 www.abc.com

Step 3:
Outgoing Mail Server Configuration (Sendmail):
Open /etc/mail/sendmail.mc file and change the following two lines.
From:
DAEMON_OPTIONS(`Port=smtp,Addr=127.0.0.1, Name=MTA’)dnl
FEATURE(`accept_unresolvable_domains’)dnl
To:
dnl DAEMON_OPTIONS(`Port=smtp,Addr=127.0.0.1, Name=MTA’)dnl
dnl FEATURE(`accept_unresolvable_domains’)dnl
Save and exit.
- First line here enables sendmail to receive incoming emails on all installed the NICs. Otherwise mail server would only be able to
- Second line here tells sendmail, do not receive emails from mail servers whose PTR record is not configured in DNS server. This is a basic level SPAM control settings in sendmail.
Generate sendmail.cf file from sendmail.mc file.
m4 /etc/mail/sendmail.mc > /etc/mail/sendmail.cf

Step 4:
Allow RELAY for trusts (organization’s) IP addresses that you want to permit sending emails using this mail server. Open /etc/mail/access in this file we specify all those addresses that will be sending emails through this mail server. At the end of this file add the following line:
192.168.0 RELAY
Save and exit and convert this text database into DB format by following command.
makemap hash access.db < access

Step 5:
Tell sendmail that it will be acting as a primary mail server for “abc.com” domain. We do this by adding domain name in /etc/mail/local-host-names. If this server is acting as a mail server for more then one domains then add names of all of the domains in this file on separate line. Open /etc/mail/local-host-names and add “abc.com” at the end of this file.
Note: A mail server can act as a primary mail server for more then one domains at the same time and as well as can act as a primary and secondary mail server for more than one domain at the same time.

Step 6:
All system users are mail users as well. Now create mail only users.
useradd -s /usr/sbin/smrsh mailuser1
useradd -s /usr/s2n/smrsh mailuser1
Also set their passwords:
passwd mailuser1
passwd mailuser2

Step 7:
Finally restart sendmail service.
service sendmail restart
Step 8:
Incoming Mail Server Configuration (Dovecot):
Open /etc/dovecot.conf and change the following lines.
From:
#protocols = imap pop3
To:
protocols = imap imaps pop3 pop3s
Save and exit and restart dovecot service.
service dovecot restart

Step 9:
Webserver Configuration (Apache):
Apache comes pre-configured, you just have to change the ServerName parameter in /etc/httpd/conf/httpd.conf file and restart the service, that’s all. Open /etc/httpd/conf/httpd.conf and set the ServerName parameter.
ServerName www.abc.com
Save and exit and restart httpd service.
service httpd restart

Installation & Configuration of Squirrelmail
• Check that Squirrelmail is installed on the system.
# rpm –q squirrelmail
• If squirrelmail is not installed on the system then install it through rpm:
# rpm –ivh squirrelmail
• Now go to the squirrelmail directory, located in /usr/share.
# cd /usr/share/squirrelmail
• Then go to the config directory:
# cd config
• Now run one of the following commands to configure squirrelmail.
# ./conf.pl
OR
perl conf.pl
• Now select option 1 (Organization Preferences).
Organization Name : YOUR_ORG_NAME
Organization Title : YOUR_ORG_NAME Webmail
Provider link : http://YOUR_ORG_SITE_ADDRESS
Provider name : YOUR_ORG_NAME
• Now select option 2 (Server Settings).
Domain : abc.com
Sendmail or SMTP : Sendmail
IMAP Server : localhost
IMAP Port : 143
Server software : uw
Delimiter : /
• Now select option 3 (Folder Settings).
Default Folder Prefix : mail/
Show Folder Prefix Option : true
Trash Folder : Trash
Sent Folder : Sent
Drafts Folder : Drafts
By default, move to trash : true
By default, move to sent : true
By default, save as draft : true
List Special Folders First : true
Show Special Folders Color : true
Auto Expunge : true
Default Sub. of INBOX : false
Show ‘Contain Sub.’ Option : true
Default Unseen Notify : 2
Default Unseen Type : 1
Auto Create Special Folders : true
Folder Delete Bypasses Trash : false
Enable /NoSelect folder fix : false
• Now select option 4 (General Settings).
Data Directory : /var/lib/squirrelmail/prefs/
Attachment Directory : /var/spool/squirrelmail/attach/
Directory Hash Level : 0
Default Left Size : 150
Usernames in Lowercase : false
Allow use of priority : true
Hide SM attributions : false
Allow use of receipts : true
Allow editing of identity : true
Allow editing of name : true
Remove username from header : false
Allow server thread sort : true
Allow server-side sorting : true
Allow server charset search : true
Enable UID support : true
PHP session name : SQMSESSID
Location base :
• Now choose option 8 (Plugins) and select the plugins that you wish to provide to your webmail users.
• Now open the browser with the following link:

http://YOUR_SITE_ADDRESS/webmail

http://192.168.0.14/webmail

SAP Specific Movement Type Blocking

2012-07-02T02:16:00.002-07:00

How you can block specific movement type in SAP

MOVEMENT TYPE BLOCK METHOD

You can restrict Transfer posting using Transaction Code: OMJJ>> double click on allowed Transaction> then you can remove T-code: MB1B which is assign to 309 Movement Type.

SPRO>>Materials management>>Inventory Management and Physical Inventory>>Movement Types>>Copy, Change Movement Types Execute

Now select Movement type.

Enter movement type 311

In left hand side tree structure Go to allowed transcation folder and double click

Delete all the transaction code by which you want to avoid goods issue

Symantec Veritas Netbackup error no.183

2012-07-02T02:10:00.000-07:00

This Solution is from Symantec Support :Error No.183 Solution

Third party-related issue: Backups performed with VERITAS NetBackup (tm) exit with status 0 (successful), but show "ERR - invalid tar header encountered, attempting to continue" during a restore from a backup that has spanned media on the Sony AIT-4 SDX 900V tape drives. When this error occurs, the data is not restorable.

Article Type
Technical Solution

Product(s)

Show all

Environment

Show all

Languages

Show all

Problem

Error

ERR - invalid tar header encountered, attempting to continue

Solution

Vendor: Sony

OS platform: This issue is known to affect Windows 2000 and 2003 platforms that are supported with NetBackup 5.x. The operating system versions known to be affected are listed at the bottom of this TechNote.

Hardware: Sony AIT-4 SDX 900V tape drives

If the issue described in this TechNote is occurring in your environment, please contact Sony Support: 800-801-7927.

Issue: In the above OS/Hardware configuration, VERITAS NetBackup (tm) Enterprise Server 5.x and NetBackup Server 5.x, backups exit with status 0 (successful), but show "ERR - invalid tar header encountered, attempting to continue" in the Restores Progress log. This issue occurs when attempting a restore from a tape that has spanned media. When this error occurs the data is not restorable.

(Important Note: This issue also affects UNIX platforms, however, with UNIX platforms NetBackup exits with a Status Code 84: media write error. Please visit the following TechNote for UNIX platforms: http://support.veritas.com/docs/274292 .)

This issue is known to occur with the Sony AIT-4 SDX 900V tape drives. This happens when the last of block of data that is written at EOM (End of Media) and the image spans media, NetBackup does not know that it gets written. This issue resides within the firmware on the tape drives. Customer's using these tapes drives should contact Sony for further information.

How to tell if affected:
After attempting a restore with NetBackup and the above OS/Hardware configuration, view the Restore Progress log and look for the message that is in bold within the following snippet:

12/16/2004 8:59:25 AM - begin Restore
12/16/2004 8:59:26 AM - 1 images required
12/16/2004 8:59:26 AM - media 000027 required
12/16/2004 8:59:26 AM - media 000024 required
12/16/2004 8:59:29 AM - restoring image hcl-959_1103163163
12/16/2004 8:59:29 AM - connecting
12/16/2004 8:59:30 AM - started process bptm (2708)
12/16/2004 8:59:30 AM - mounting 000027
12/16/2004 8:59:34 AM - connected; connect time: 00:00:05
12/16/2004 9:01:14 AM - mounted; mount time: 00:01:44
12/16/2004 9:01:14 AM - positioning 000027 to file 34
12/16/2004 9:03:57 AM - positioned 000027; position time: 00:02:43
12/16/2004 9:03:57 AM - begin reading
12/16/2004 9:12:05 AM - started process bptm (2708)
12/16/2004 9:12:05 AM - mounting 000024
12/16/2004 9:24:51 AM - mounted; mount time: 00:12:46
12/16/2004 9:24:51 AM - positioning 000024 to file 1
12/16/2004 9:24:51 AM - positioned 000024; position time: 00:00:00
12/16/2004 9:24:52 AM - Error bpbrm(pid=916) from client hcl-959: ERR - invalid tar header encountered, attempting to continue
12/16/2004 9:24:52 AM - Warning bpbrm(pid=916) from client hcl-959: WRN - unknown file type Q encountered, continuing to process file '' (0)
12/16/2004 9:24:52 AM - Critical bpbrm(pid=916) from client hcl-959: FTL - expected file '/E/TestData/Set05/Dir02/SubDir05/File013064', found file ''
12/16/2004 9:24:52 AM - Error bpbrm(pid=916) from client hcl-959: UTF - /E/TestData/Set05/Dir02/SubDir05/File013064
12/16/2004 9:24:52 AM - Error bpbrm(pid=916) from client hcl-959: UTF - /E/TestData/Set05/Dir02/SubDir05/File013065
12/16/2004 9:24:52 AM - Error bpbrm(pid=916) from client hcl-959: UTF - /E/TestData/Set05/Dir02/SubDir05/File013066
12/16/2004 9:24:52 AM - Error bpbrm(pid=916) from client hcl-959: UTF - /E/TestData/Set05/Dir02/SubDir06/
12/16/2004 9:24:52 AM - Error bpbrm(pid=916) from client hcl-959: UTF - /E/TestData/Set05/Dir02/SubDir06/File013067
12/16/2004 9:24:53 AM - Error bpbrm(pid=916) from client hcl-959: UTF - /E/TestData/Set05/Dir02/SubDir06/File013068
12/16/2004 9:24:53 AM - Error bpbrm(pid=916) from client hcl-959: UTF - /E/TestData/Set05/Dir02/SubDir06/File013069
12/16/2004 9:24:53 AM - Error bpbrm(pid=916) from client hcl-959: UTF - /E/TestData/Set05/Dir02/SubDir06/File013070
12/16/2004 9:24:53 AM - Error bpbrm(pid=916) from client hcl-959: UTF - /E/TestData/Set05/Dir02/SubDir06/File013071
12/16/2004 9:24:53 AM - Error bpbrm(pid=916) from client hcl-959: ERR - more than 10 files not restored, logging will only continue in the progress log
12/16/2004 9:24:57 AM - restored image hcl-959_1103163163 - (media manager - system error occurred(174)); restore time 00:25:28
12/16/2004 9:24:57 AM - Warning bprd(pid=2744) Restore must be resumed prior to first image expiration on 12/29/2004 9:12:43 PM
12/16/2004 9:24:57 AM - end Restore; elapsed time: 00:25:32
the restore failed to recover the requested files(5)

Issue exists at firmware version: VERITAS is unable to positively identify or specify firmware version. Please contact Sony Support to assist you in identifying which firmware version you have in your environment: 800-801-7927.

Workarounds:
1. Uncheck the box in front of "Allow backups to span media" from the following location: Admin GUI > Host Properties > Master Server properties > Media (Refer to Figure 1). Please note: This option is selected by default.

Figure 1

2. If it is necessary to span media in your environment, VERITAS recommends that you use an alternate drive destination.

After either of the above workarounds are implemented, perform a full backup.

Formal Resolution: At the time of this writing, VERITAS and Sony are working together to re-qualify these drives with updated firmware provided by Sony. Until VERITAS can re-qualify the Sony AIT-4 SDX 900V tape drives, VERITAS NetBackup 5.x will not support the Sony AIT-4 SDX 900V tape drives. The process to re-qualify the Sony AIT-4 SDX 900V tape drives is currently in progress. VERITAS strongly recommends implementing either workaround provided in this TechNote until these drives are re-qualified. Please contact Sony Support for more information: 800-801-7927.

Sony developed a new firmware version (ref.# 0101) which fixes this problem. End users must get this firmware upgrade from Sony, and upgrade their installed drives. Firmware upgrades are available from:

1. Tech Support Tel# 1-800-801-7927

2. Or Email Support at Tape.Support@am.sony.com

3. Or by Web @ http://sony.storagesupport.com/ait/sdx900v.htm

For further updates on this issue, please subscribe to this document by clicking on the following link: http://maillist.support.veritas.com/notification_services.asp?doc=274864

If you have not received this TechNote from the VERITAS Email Notification Service for Software Alerts, please subscribe at the following link:

http://maillist.support.veritas.com/subscribe.asp

If you have any questions or concerns regarding this issue, please contact VERITAS Technical Services.

NetBackup status code 183: tar received an invalid archive

Article: TECH58657

Created: 2008-01-19

Updated: 2009-01-12

Article URL http://www.symantec.com/docs/TECH58657

Show all

Problem

NetBackup status code 183: tar received an invalid archive

Solution

Message: tar received an invalid archive

Explanation: The data that was passed to tar was corrupt.

Recommended action:
If the problem is with a UNIX client, create a /usr/openv/netbackup/logs/tar debug log directory on the client and rerun the operation.

a Check the tar debug log file for any error messages that explain the problem.

b Reboot the client to see if it clears the problem.

c When you finish with your investigation of the problem, delete the /usr/openv/netbackup/logs/tar directory on the client.

If the problem is with a Microsoft Windows, NetWare, or Macintosh client:

a Create a bpcd debug log directory on the client (on a Macintosh NetBackup creates the log automatically).

b On a Windows client, create a tar debug log directory.

c Increase the debug or log level as explained in the debug log topics in Chapter 3.

d Rerun the operation and check the resulting debug logs. e Reboot the client to see if it clears the problem.

NET_BUFFER_SZ, SIZE_DATA_BUFFERS and NUMBER_DATA_BUFFERS - how they work and how to configure them

Article: TECH1724

Created: 1999-01-15

Updated: 2011-01-01

Article URL http://www.symantec.com/docs/TECH1724

Article Type
Technical Solution

Product(s)

Environment

Subject

Languages

Problem

NET_BUFFER_SZ, SIZE_DATA_BUFFERS and NUMBER_DATA_BUFFERS - how they work and how to configure them

Solution

Here is some information on undocumented features for setting the Network Buffer Size, Data Buffer Size, and Number of Data Buffers used by NetBackup (tm) on UNIX platforms.

NOTE: These settings are used to tune the performance of NetBackup.

TCP/IP Network Buffer Size.

/usr/openv/netbackup/NET_BUFFER_SZ is a file containing a number indicating the TCP/IP socket buffer size that should be used for data transfers between the NetBackup media server and its clients. If the file does not exist, the default value used is 32032 bytes.

The default value can be changed by creating the file /usr/openv/netbackup/NET_BUFFER_SZ on the NetBackup media server and client systems.

The /usr/openv/netbackup/NET_BUFFER_SZ file is a text file containing a single line specifying the value of the Network Buffer Size in bytes in decimal format.

For example, a Network Buffer Size of 64KB could be configured and checked like this:

# echo "65536" > /usr/openv/netbackup/NET_BUFFER_SZ
# cat /usr/openv/netbackup/NET_BUFFER_SZ
65536
#

Most networks can handle a NET_BUFFER_SZ of 262144 (256K). In this case to make the changes
to the NetBackup media server and Unix clients, the commands would be:

# echo "262144" > /usr/openv/netbackup/NET_BUFFER_SZ
# cat /usr/openv/netbackup/NET_BUFFER_SZ
262144
#

For Windows clients, the Communications Buffer size setting is modified to 256. See the
Technote reference below for further details.

Specifying a larger value in the NET_BUFFER_SZ file may improve the performance of backups and restores. It is recommended that if NET_BUFFER_SZ is used, the same value should be set on all the NetBackup media servers and clients.

Data Buffer Size and Number of Data Buffers.

The NetBackup media server uses shared memory to buffer data between the network and the tape drive (or between the disk and the tape drive if the NetBackup media server and client are the same system). By default, NetBackup uses a default value of 8 x 32KB shared memory buffers for non-multiplexed backups and 4 x 64KB for a multiplexed backup.

These buffers can be configured by creating the files /usr/openv/netbackup/db/config/SIZE_DATA_BUFFERS and/usr/openv/netbackup/db/config/NUMBER_DATA_BUFFERS on the NetBackup media server. These parameters are meant exclusively for media servers, and should not be used on a pure master server or client.

The SIZE_DATA_BUFFERS file should contain a single line specifying the data buffer size in bytes in decimal format.
The NUMBER_DATA_BUFFERS file should contain a single line specifying the number of data buffers in decimal format.

The value in the SIZE_DATA_BUFFERS file has to be a multiple of 1024B.
It is common to increase SIZE_DATA_BUFFERS to 256KB and NUMBER_DATA_BUFFERS to 16.

IMPORTANT: Because the data buffer size equals the tape I/O size, the value specified in SIZE_DATA_BUFFERS must not exceed the maximum tape I/O size supported by the tape drive or operating system. This is usually 256 KB or 128 KB.

In order to configure NetBackup to use 16 x 256 KB data buffers, specify 262144 (256 x 1024) in SIZE_DATA_BUFFERS and 16 inNUMBER_DATA_BUFFERS:

# echo "262144" > /usr/openv/netbackup/db/config/SIZE_DATA_BUFFERS
# echo "16" > /usr/openv/netbackup/db/config/NUMBER_DATA_BUFFERS
# cat /usr/openv/netbackup/db/config/SIZE_DATA_BUFFERS
262144
# cat /usr/openv/netbackup/db/config/NUMBER_DATA_BUFFERS
16
#

Care should be taken when changing these values. For example, increasing the tape buffer size can cause some backups to run slower and there have been cases where there have been restore problems.

IMPORTANT: After making any changes, it is vitally important to verify that the following tests can be completed successfully:

1. Run a backup
2. Restore data from the new backup created in step 1
3. Restore data from a backup created prior to the changes to SIZE_DATA_BUFFERS and NUMBER_DATA_BUFFERS

The number and size of the data buffers used by the NetBackup media server can be checked by looking in the bptm log file:

12:02:55 [28551] <2> io_init: using 32768 data buffer size
12:02:55 [28551] <2> io_init: CINDEX 0, sched bytes for monitoring = 2000
12:02:55 [28551] <2> io_init: using 8 data buffers

or

15:26:01 [21544] <2> mpx_setup_restore_shm: using 12 data buffers, buffer size is 65536

Increasing the size and number of the data buffers will use up more shared memory, which is a limited system resource. The total amount of shared memory used is: (buffer_size * num_buffers) * drives * MPX.

So, for two tape drives, each configured with an MPX of 4, and with 16 data buffers of 256 KB, the total shared memory usage would be:

(16 * 256k) * 2 * 4 = 32 MB (32768 KB)

Take into consideration the total system resources and the entire network.
The Maximum Transmission Unit (MTU) for the LAN may also have to be changed.

NOTE: For Digital Linear Tape (DLT) drives, the number that seems to give the best performance for SIZE_DATA_BUFFERS is 65536. Further performance improvements can be achieved by increasing the value in the NUMBER_DATA_BUFFERS file.

2012-07-02T02:05:00.001-07:00

SAP BRBACKUP COMMAND for backup:

At oracle administrator e.g oraprd >
run directly following commands after settings in initSID.sap file

brbackup -u / -c force -t offline_force

brbackup -u / -c force -t online_force

2012-07-02T01:45:00.000-07:00

SAP CJS-00096 : extract archive failed

Solution:

1.First of all check about the software pack,it should be completely downloaded.
2.The main issue may be with your RAM (Hardware on which you are doing installations)
3.Check your Hard disks.

SAP Basis,Oracle and Redhat Linux Factory

SAP GUI installation on Mac OS

System Requirements

The install command

The uninstall command

The version command

ora-27101 shared memory realm does not exist linux No such file exists. R3trans -d error 0012

MOS-01022 sap error

SAP BASIS ERROR during unicode conversion:error during conversion of cluster item

CJS-00030 SAP Installation error.

ORA-00904 error Solution at the time of SAP Installation

Re-Creating PSAPTEMP on Oracle

SAP Specific Movement Type Blocking

Symantec Veritas Netbackup error no.183

NetBackup status code 183: tar received an invalid archive

Problem

Solution

NET_BUFFER_SZ, SIZE_DATA_BUFFERS and NUMBER_DATA_BUFFERS - how they work and how to configure them

Problem

Solution

The `install` command

The `uninstall` command

The `version` command