Install Network Card Drivers in Solaris 10

1.1 Preparing For Installation
Install your PCI card and boot Solaris 10. Copy Gani-2.6.8 drivers to Desktop. Add hostname for the NIC card into /etc/hosts file

Ex.

Make links to correct binary directory and Makefile according to your configuration. I386 and gcc are default.

# cd /Desktop/gani-2.6.8
# rm -f Makefile
# ln -s Makefile.amd64_gcc Makefile
# ln -s amd64 obj

1.2 Making Binaries Only For Open Solaris Users.

# rm Makefile.config
# ln -s Makefile.config_gld3 Makefile.config
# /usr/ccs/bin/make
1.3 Testing
Testing before installation is strongly recommended.

# cd /Desktop/gani-2.6.8
# /usr/ccs/bin/make install
# ./adddrv.sh
# modload obj/gani
# ifconfig ganiN plumb (where N is an instance number, typically 0 for first card) Ex: gani0 (Network card name)
# ifconfig -a (you will see an entry for ganiN)
# ifconfig gani0 YOUR-HOST-NAME
# ifconfig gani0 (ensure IP address is correct)
# ifconfig gani0 up (and then you can test with ping, telnet, ftp ...)
1.4 Installation
After you ensure that the gani driver is fully functional, install it. Configure the network interface. Create and/or modify the following file:

Edit /etc/hostname.gani0
Enter
OR
# vi /etc/hostname.gani0
Enter & Save.

1.5 Reboot the System

# init 6

Adding Network Gateway in Solaris 10

edit /etc/defaultrouter
# vi /etc/defaultrouter
Add

Assign the current default route. To implement the new default route without rebooting the system, use the following command substituting your default route for 192.168.8.1.

# route add default 192.168.8.1

Adding DNS Name servers in Solaris 10

1.7 Adding DNS

edit /etc/resolv.conf & add
nameserver 4.2.2.2
nameserver 202.56.250.6 and Save.
# cp /etc/nsswitch.dns /etc/nsswitch.conf

Enabling TELNET & FTP in Solaris 10

2.1 Enabling TELNET
Comment CONSOLE=/dev/console in /etc/default/login file.
Ex. # CONSOLE=/dev/console

2.2 Enabling FTP
Comment root in /etc/ftpd/ftpusers file.
Ex. #root

Creating FILE SYSTEM for Sap ECC 6.0 in Solaris 10

3.1 Creating File System for DB2

Before creating file system make sure disk is free for creating partition.

login: root
Password:
Last login: Sat Feb 26 15:20:36 on console
Oracle Corporation SunOS 5.10 Generic Patch January 2005
# format
Searching for disks...done
AVAILABLE DISK SELECTIONS:
0. c0d0
/pci@0,0/pci-ide@1f,2/ide@0/cmdk@0,0

Specify disk (enter its number): 0
selecting c0d0
Controller working list found
[disk formatted, defect list found]
Warning: Current Disk has mounted partitions.
/dev/dsk/c0d0s0 is currently mounted on /. Please see umount (1M).
/dev/dsk/c0d0s1 is currently used by swap. Please see swap (1M).
FORMAT MENU:
disk - select a disk
type - select (define) a disk type
partition - select (define) a partition table
current - describe the current disk
format - format and analyze the disk
fdisk - run the fdisk program
repair - repair a defective sector
show - translate a disk address
label - write label to the disk
analyze - surface analysis

defect - defect list management
backup - search for backup labels
verify - read and display labels
save - save new disk/partition definitions
volname - set 8-character volume name
! - execute , then return
quit
format> p
format> p
PARTITION MENU:
0 - change `0' partition
1 - change `1' partition
2 - change `2' partition
3 - change `3' partition
4 - change `4' partition
5 - change `5' partition
6 - change `6' partition
7 - change `7' partition
select - select a predefined table
modify - modify a predefined partition table
name - name the current table
print - display the current table
label - write partition map and label to the disk
! - execute , then return
quit

format> p
PARTITION MENU:
0 - change `0' partition
1 - change `1' partition
2 - change `2' partition
3 - change `3' partition
4 - change `4' partition
5 - change `5' partition
6 - change `6' partition
7 - change `7' partition
select - select a predefined table
modify - modify a predefined partition table
name - name the current table
print - display the current table
label - write partition map and label to the disk
! - execute , then return
quit

partition> p
Current partition table (original):
Total disk cylinders available: 38910 + 2 (reserved cylinders)
Part Tag Flag Cylinders Size Blocks
0 root wm 36952 - 38909 15.00GB (1958/0/0) 31455270
1 swap wu 3 - 1569 12.00GB (1567/0/0) 25173855
2 backup wm 0 - 38909 298.07GB (38910/0/0) 625089150
3 unassigned wm 0 0 (0/0/0) 0
4 unassigned wm 0 0 (0/0/0) 0
5 unassigned wm 0 0 (0/0/0) 0
6 unassigned wm 0 0 (0/0/0) 0
7 unassigned wm 0 0 (0/0/0) 0
8 boot wu 0 - 0 7.84MB (1/0/0) 16065
9 alternates wu 1 - 2 15.69MB (2/0/0) 32130
partition> 3
Part Tag Flag Cylinders Size Blocks
3 unassigned wm 0 0 (0/0/0) 0
Enter partition id tag[unassigned]:
Enter partition permission flags[wm]: wm
Enter new starting cyl[0]: 1570
Enter partition size[0b, 0c, 1570e, 0.00mb, 0.00gb]: 12gb

partition> label
Ready to label disk, continue? y
partition> q
FORMAT MENU:
disk - select a disk
type - select (define) a disk type
partition - select (define) a partition table
current - describe the current disk
format - format and analyze the disk
fdisk - run the fdisk program
repair - repair a defective sector
show - translate a disk address
label - write label to the disk
analyze - surface analysis
defect - defect list management
backup - search for backup labels
verify - read and display labels
save - save new disk/partition definitions
volname - set 8-character volume name
! - execute , then return
quit
format> verify
Primary label contents:
Volume name = < >
ascii name =
pcyl = 38912
ncyl = 38910
acyl = 2
bcyl = 0
nhead = 255
nsect = 63
Part Tag Flag Cylinders Size Blocks
0 root wm 36952 - 38909 15.00GB (1958/0/0) 31455270
1 swap wu 3 - 1569 12.00GB (1567/0/0) 25173855
2 backup wm 0 - 38909 298.07GB (38910/0/0) 625089150
3 unassigned wm 1570 - 3136 12.00GB (1567/0/0) 25173855
4 unassigned wm 0 0 (0/0/0) 0
5 unassigned wm 0 0 (0/0/0) 0
6 unassigned wm 0 0 (0/0/0) 0
7 unassigned wm 0 0 (0/0/0) 0
8 boot wu 0 - 0 7.84MB (1/0/0) 16065
9 alternates wu 1 - 2 15.69MB (2/0/0) 32130
format> label
Ready to label disk, continue? y
format> q
# format
Searching for disks...done
AVAILABLE DISK SELECTIONS:
0. c0d0
/pci@0,0/pci-ide@1f,2/ide@0/cmdk@0,0
Specify disk (enter its number): 0
selecting c0d0
Controller working list found
[disk formatted, defect list found]
Warning: Current Disk has mounted partitions.
/dev/dsk/c0d0s0 is currently mounted on /. Please see umount (1M).
/dev/dsk/c0d0s1 is currently used by swap. Please see swap (1M).
FORMAT MENU:
disk - select a disk
type - select (define) a disk type
partition - select (define) a partition table
current - describe the current disk
format - format and analyze the disk
fdisk - run the fdisk program
repair - repair a defective sector
show - translate a disk address
label - write label to the disk
analyze - surface analysis
defect - defect list management
backup - search for backup labels
verify - read and display labels
save - save new disk/partition definitions
volname - set 8-character volume name
! - execute , then return
quit
format> save
Saving new disk and partition definitions
Enter file name["./format.dat"]:
format> q
Repeat the above steps to create additional Partitions



************* After creating parition disk name C0d0s0 to s1,s2,s3 try this

# newfs /dev/rdsk/c0d0s3 (For sapmnt)
newfs: construct a new file system /dev/rdsk/c0d0s3: (y/n)? y
Warning: 5518 sector(s) in last cylinder unallocated
/dev/rdsk/c0d0s3: 41945714 sectors in 6828 cylinders of 48 tracks, 128 sectors
20481.3MB in 427 cyl groups (16 c/g, 48.00MB/g, 5824 i/g)
super-block backups (for fsck -F ufs -o b=#) at:
32, 98464, 196896, 295328, 393760, 492192, 590624, 689056, 787488, 885920,
Initializing cylinder groups:
........
super-block backups for last 10 cylinder groups at:
40997024, 41095456, 41193888, 41292320, 41390752, 41489184, 41587616, 41686048, 41784480, 41882912

# mkdir /db2
# mkdir /db2/db2ids
# mkdir /db2/IDS
# mkdir /db2/IDS/db2dump
# mkdir /db2/IDS/db2ids
# mkdir /db2/IDS/log_dir
# mkdir /db2/IDS/sapdata1
# mkdir /db2/IDS/sapdata2
# mkdir /db2/IDS/sapdata3
# mkdir /db2/IDS/sapdata4

Creating USERS & GROUPS IN Solaris 10 For SAP ECC 6.0

4.1 Changing Permissions for HOME Directory

Edit /etc/auto_master & Change

/home auto_home -nobrowse TO
/auto_home auto_home -nobrowse & Save

4.2 Adding Users to HOME Directory

# cd home
# mkdir idsadm
# mkdir sapids
# mkdir sapidsdb
4.3 Creating Users & Groups



# groupadd -g 101 dbidsadm
# useradd -u 101 -g 101 -d /db2/db2ids -m -s /bin/sh db2ids
# passwd db2ids
New Password:
Re-enter new Password:
passwd: password successfully changed for db2ids
# groupadd -g 102 sapsys
# groupadd -g 103 dbidsctl
# useradd -u 102 -g 102 -d /home/idsadm -m -s /bin/sh idsadm
# usermod -G sapsys,dbidsctl idsadm
# passwd idsadm
New Password:
Re-enter new Password:
passwd: password successfully changed for idsadm

# groupadd -g 104 dbidsmnt
# useradd -u 104 -g 104 4 -d /home/sapidsdb -m -s /bin/sh sapidsdb
# passwd sapidsdb
New Password:
Re-enter new Password:
passwd: password successfully changed for sapidsdb

Prerequisite for SAP Installation

5.1 Hardware Requirement

Hard Disk: 320GB
RAM: 4GB
Processor: CORE 2 Duo

5.2 Setting Parameter for SAP

Edit /etc/system and add
Set rlim_fd_cur = 8192
# ulimit –n
256
# ulimit –n 8192

Step by Step GUIDE Db2 BACKUP Restore Production server to Quality Server (Db2 Database Refresh with Production Offline Backup)

Login in To Production db2 Data base Server .

Login User ID: SIDadm

# run beloow command 

brdb6brt -bm RETRIEVE -es –replace <Proudction SID>=<Quality SID>,db2ecp=db2ecq,/db2/<ProductionSID>=/db2/<QualitySID>

Output file Created with File extension is .scr

Open and check the file

Login telnet in Quality Server

Output file and Db2 backup are mounted or copied in Quality Server

Change Permission of files

Stop the SAP in Quality server.

Stopsap all

>cat ECP_NODE0000.scr---à to view the file

In below screen we can view the file

Now we have to edit the “ECP_NODE0000.scr” file.

To edit this copy the ECP_NODE0000.scr file to your system using FileZilla.

Open the file with NOTEPAD and edit the file.

Save and copy the above file to the /qabackup.

Login in Quality server with db2SID user

Run below commands.

      db2set DB2_RESTORE_GRANT_ADMIN_AUTHORITIES=NO

      db2set DB2_WORKLOAD=SAP

   db2set –all | grep –I db2 restore grant

   db2 –tvf  ECP_NODE0000.scr (Output file .scr file)

Now open new session(192.168.1.67) and check the file systems.

To check the status

Successfully completed.

And create user id in Quality server with <ProductionServerSID>adm

Run below  command

dscdb6up –create <password of SIDadm user>  <sapsid user password>

if it will give error like not a valid user then

edit dscdb6.conf file from  /usr/sap/SID/global

write production server Username SIDadm .

Regards,

Alihamed.sa

Search for SAP Basis Transaciton codes

Search for SAP Basis Transaciton codes
You can access all the transaction codes by using the transaction code 'SDMO'.
This is the transaction code for the Dynamic Menu.
Based on your search string, you can get all related transaction codes for all the SAP application modules.
For e.g. the Search text for ADMIN returns the following results:
----------------------------------------------------------
|Tcode|Transaktionstext |
----------------------------------------------------------
|ADOK |AM: System Administration Guide |
|BALE |Area Menu for Administration |
|BDMO |ALE CCMS Group Administration |
|CATSX|Time Sheet Admin.: Initial Screen |
|CICY |CTI Administration |
|CJV6 |Maintenance: Version administration |
|CN84 |PS: Archiving project - admin. |
|COA4 |PP: Archiving order - administration |
|CSADM|Content Server Administration |
|FC_BW|Administrator Workbench |
|FDTA |TemSe/REGUT Data Administration |
|FDTT |Treasury Data Medium Administration |
|FO86 |Change active admin.contract fees |
|FO8E |Create admin.contract event |
|FO8F |Change admin.contract event |
|FO8G |Display admin.contract event |
|FO8H |Admin.costs acct sttlmnt simulation |
|FOART|REsearch: Administration Web-User |
|HRCMP|Compensation Administration |
|HRCMP|Budget Administration: Display |
|HRCMP|Budget Administration: Change |
|IM_AR|Admin. of App. Request Archives |
|KA18 |Archive admin: assess., distr., ... |
|KE72 |Archive Administration: Line Items |
|KE73 |Archive Administration: Totals Recs |
|KPRO |KPRO Administration |
|OAAD |ArchiveLink Administration Documents |
|OG00 |Personnel Administration Customizing |
|OG01 |Personnel Administration Customizing |
|OMSM |CS MM Set Up Administrative Data |
|OOCM_|Compensation Administration Settings |
|OOML |Room Administration Mail Connection |
|OOPC |Administration: Personnel No. Check |
|OY22 |Create subadministrator Customizing |
|OYEA |IDoc administration |
|PA97 |Compensation administration - matrix |
|PA98 |Compensation Administration |
|PA99 |Compensation Admin. - Release Report |
|PACA |PF administration |
|PAT1 |Personnel Administration infosystem |
|PC00_|CBS survey salary administrations |
|PC00_|Tax Certificates - Administration 16 |
|PP26 |Plan Scenario Administration |
|PP2D |Administer Payroll Results |
|PSO5 |PD: Administration Tools |
|PUCA |PC administration for PF |
|PVSEA|Administer Search Engine |
|QD25 |Archiving Notifications: Admin. |
|S002 |Menu Administration |
|SA02 |Academic title (cent. addr. admin.) |
|SA04 |Name prefixes (centr. addr. admin.) |
|SA05 |Name suffix (centr. addr. admin.) |
|SA07 |Address groups (centr. addr. admin.) |
|SA08 |Person groups (centr. addr. admin.) |
|SA09 |Internat. versions address admin. |
|SA10 |Address admin. communication type |
|SARA |Archive Administration |
|SBPT |Administration Process Technology |
|SCC4 |Client Administration |
|SCON |SAPconnect - Administration |
|SCOT |SAPconnect - Administration |
|SCUA |Central User Administration |
|SCUM |Central User Administration |
|SE78 |SAPscript: Graphics administration |
|SECST|Administration of Secure Memory |
|SENG |Administration of External Indexes |
|SENGE|Explorer Index Administration |
|SIAC1|Web Object Administration |
|SLICE|Administer SAP Licenses |
|SLWA |Translation Environment Administratn |
|SM14 |Update Program Administration |
|SP12 |TemSe Administration |
|SPAD |Spool Administration |
|SPAT |Spool Administration (Test) |
|SPHA |Telephony administration |
|SPHB |SAPphone: System Administration |
|SSAA |System Administration Assistant |
|SSCA |Appointment Calendar: Administration |
|SSCA1|Appointment calendar: Administration |
|SSO2 |Workplace Single Sign-On Admin. |
|SSO2_|Workplace Administration SSO2 Ticket |
|STMA |Proposal Pool Administration |
|SURAD|Survey Administration |
|SURL_|Personalization for URL Gen. Admin. |
|SUUMD|Display User Administration |
|SWDC |Workflow Definition: Administration |
|SWEAD|Event Queue Administration |
|SWEQA|Event Queue Administration |
|SWEQA|Queue Administrator Maintenance |
|SWIA |Selection rep. for work items(admin) |
|SWRK |Administrtation using work areas |
|SWUF |Administration of Runtime System |
|SWUL |Customizing: Process Administrator |
|SWUX |SAPforms Administration |
|SYSAD|System Administration: Task List |
|S_ALR|IMG Activity: CIC_V_CCMCTIADMIN |
|S_ALR|IMG Activity: SIMG_EURO_ADMINUSER |
|S_BCE|IMG-Aktivität: BCDIGSI_ADMIN |
|S_PH0|InfoSet Query: Administration |
|S_PH0|InfoSet Query: Administration |
|S_PH0|InfoSet Query: Administration |
|S_PH0|InfoSet Query: Administration |
|S_PH0|InfoSet Query: Administration |
|TBD0 |Datafeed: Adminster Archives |
|TBD3 |Datafeed: Market data administration |
|TBD6 |Datafeed: Log file administration |
|WE46 |IDoc administration |
|WORKI|Administrtation using work areas |
----------------------------------------------------------
What the difference between tcode SE09 & SE10?
SE09 transaction is for workbench transport request wherein the developers can track their changes or modifications to the workbench objects .
Whereas SE10 is a customising transport request transaction.this is used for displaying customising requests. Sometimes this may be restricted to business analysts.

SAP Administrator Daily Activities

SAP Administrator Daily Activities
SAP DAILY ACTIVITIES
1] Check that all the application servers are up:
sm51 SAP Servers
sm04/al08 Logon Users
2] Check that daily backup are executed without errors
db12 Backup logs: overview
3] SAP standard background jobs are running successfully. Review for cancelled and critical jobs.
sm37 Background jobs--- Check for successful completion of jobs. Enter * in user-id field and verify that all critical successful jobs and review any cancelled jobs.
4] Operating system Monitoring
st06
5] Extents monitoring
db02 Database monitoring--Check for max-extents reached
6] Check work-processes(started from sm51)
sm50 Process overview-- All work processes with a running or waiting status.
7] Check system log
sm21 System log-- Set date and time to before the last log review. Check for errors ,warning, security, message-bends, database events.
8] Review workload statistics
st03 Workload analysis of
sto2 tune summary instance
9] Look for any failed updates
sm13 update records
10] check for old locks
sm12 lock entry list
11] Check for spool problems
sp01 spool request screen-- check for spool that are in request for over an hour.
12] Review and resolve dumps
st22 ABAP Dump analysis
13] Checking .trc file in SAP trace directory for block corruption on daily basis.
C:\ORacle\sid\saptrace
14] Archive backup
brarchive -f force -cds -c
Insert the archive backup tape
15] Review NT system logs for problem
-> NT system log- look 4 errors or failures
-> NT security log- failed logon 2 sap servers
-> NT Application log -look 4 errors or failures

Tcodes used for Daily System Monitoring

Tcodes used for Daily System Monitoring
After running daily system monitoring transaction, what should we check for:
In st22 look for the core dumps if any and report to the respective consultants and try to know why it happened.
In sm21 try to check for errors.
In sp01 try to see if any spool jobs have failed.
In st02 look if any swaps are happening, swaps are not good for performance.
In st04 look for Database alert logs and Performance.
In st03 look for ratio hits.
In sm59 look for connectivety tesing if there are other systems also connected to your SAP R/3 system
In db13 look if the jobs have run successfully.
In sm37 look for any cancelled scheduled job and take action appropriately.
In sm12 look for any pending locks from the previous days.
In sm13 look for any hanged updates, or updates pending for long or updates in PRIV mode.

How to know or get the Kernel Version of SAP system

How to know or get the Kernel Version of SAP system

Posted by Basis-Consultant | 1:21 PM | Basis, how to's, Security | 1 comments »

There are many ways through which you can get the Version Number of SAP Kernel.
One of the method is from any window in the top menu go to
system--> status and click on the other kernel info button which is between the navigate and cancel buttons.

Another method is to login as administrator and enter the following disp+work -v. in command field on left top corner. This will show you the kernel version of SAP.

You can also check the log or trace files at os level /usr/sap/work/dev_disp.

You can also get this kernel information from sm51 screen. Go to transaction sm51 then click on database server (single click only. Not double click) and then click on release notes. Then you will see the kernel information and patch level.

Backup profile for SAP ECC6 + Oracle

Backup profile for SAP ECC6 + Oracle
This is my sample backup profile (initSID.sap) for taking disk backup on path /local/
backup_mode = all
restore_mode = all
backup_type = online
backup_dev_type = disk
backup_root_dir = /local/BKP
stage_root_dir = /oracle/SID/sapbackup
compress = yes
compress_cmd = "compress -c $ > $"
uncompress_cmd = "uncompress -c $ > $"
compress_dir = /oracle/SID/sapreorg
archive_function = save
archive_copy_dir = /local/arch
archive_stage_dir = /local/arch
tape_copy_cmd = cpio
disk_copy_cmd = copy
stage_copy_cmd = rcp
cpio_flags = -ovB
cpio_in_flags = -iuvB
cpio_disk_flags = -pdcu
dd_flags = "obs=64k bs=64k"
dd_in_flags = "ibs=64k bs=64k"
saveset_members = 1
copy_out_cmd = "dd ibs=8k obs=64k of=$"
copy_in_cmd = "dd ibs=64k obs=8k if=$"
rewind = "mt -f $ rew"
rewind_offline = "mt -f $ offline"
tape_pos_cmd = "mt -f $ fsf $"
tape_size = 1200M
exec_parallel = 0
tape_address = /dev/rmt/0mn
tape_address_rew = /dev/rmt/0m
volume_archive = (SIDA01, SIDA02, SIDA03, SIDA04, SIDA05,
SIDA06, SIDA07, SIDA08, SIDA09, SIDA10,
SIDA11, SIDA12, SIDA13, SIDA14, SIDA15,
SIDA16, SIDA17, SIDA18, SIDA19, SIDA20,
SIDA21, SIDA22, SIDA23, SIDA24, SIDA25,
SIDA26, SIDA27, SIDA28, SIDA29, SIDA30)
volume_backup = (SIDB01, SIDB02, SIDB03, SIDB04, SIDB05,
SIDB06, SIDB07, SIDB08, SIDB09, SIDB10,
SIDB11, SIDB12, SIDB13, SIDB14, SIDB15,
SIDB16, SIDB17, SIDB18, SIDB19, SIDB20,
SIDB21, SIDB22, SIDB23, SIDB24, SIDB25,
SIDB26, SIDB27, SIDB28, SIDB29, SIDB30)
expir_period = 30
tape_use_count = 100

SAP Kernel Upgrade

SAP Kernel Upgrade
SAP Kernel Upgrade Tutorial step by Step:
1. Login as root
2. Make new backup directory
cd /
mkdir SIDkernel_10102007
3. Create latest kernel backup
cp -pr /sapmnt/SID/exe/* /SIDkernel_10102007
4. Compare size of the original kernel and the backup
du -sk /sapmnt/SID/exe/
=>840413 /sapmnt/SID/exe
du -sk /SIDkernel_10102007
=>840413 /SIDkernel_10102007
5. Make new shadow kernel directory
cd /
mkdir newkernel_175
6. Copy the new downloaded kernel files into /newkernel_175
7. Unpack the new downloaded kernel in folder /newkernel_175
/sapmant/SID/exe/SAPCAR -xvf SAPEXE_175-20000221.SAR
/sapmant/SID/exe/SAPCAR -xvf SAPEXEDB_175-20000223.SAR
8. Login as sidadm
9. Stop the SAP System
stopsap
10. Stop saposcol
saposcol -k
11. Go to the current kernel directory
Login as root
cd /sapmnt/SID/exe
12. Copy all extracted support packages into this folder
cp -pr /newkernel_175/* /sapmnt/SID/exe13.
13. Change file permission of files into kernel folder
cd /sapmnt/SID/exe
chown SIDadm:sapsys ./*
14. Copy back the original file from backup saproot.sh into this folder.
cp -p /SIDkernel_10102007/saproot.sh /sapmnt/SID/exe
15. Login as SIDadm with root privilege
Login as SIDadm
su root
16. Go to the current kernel directory
cd /sapmnt/SID/exe
Then execute:
./saproot.sh SID
Solaris Error (refer SAP Note 420417):
# ./saproot.sh SID
> ./saproot.sh: whoami: not found
> ./saproot.sh: test: argument expected
Solution:
#PATH=/usr/ucb:$PATH
#./saproot.sh <SID>
Again execute:
disp+work
17. Start the saposcol service
Login as sidadm
saposcol
18. Start the SAP system
startsap

How lock and unlock client in sap to prevent user login

How lock unlock client in sap to prevent user login
This is a workaround to lock a client to prevent user to login during patching or any maintenance activity of SAP R/3 (ECC 6.0). Example with detaile are given below:-
Client locking:-----------
SE37->SCCR_LOCK_CLIENT
Press Run/Test (look like ZIP file button)
enter your Client No. i.e. 210/300/500/900 etc
Press Execute button only.
Done
Client Unlocking:-----------
Client lock-> SE37->SCCR_UNLOCK_CLIENT
Press Run/Test (look like ZIP file button)
enter your Client No. i.e. 210/300/500/900 etc
Press Execute button only.
Done
Best of Luck

Enable Audit to sys user to SYSLOG in Oracle 10g

Enable Audit to sys user to SYSLOG in Oracle 10g
Workaround to Enable Audit to sys user to SYSLOG
Oracle 9i onward, we have new feature to enable audit for sysdba privilege users. Record Audition writes to the system audit log.
This is an example to audit sys user to SYSLOG utility.
Edit syslog.conf and insert below line.
vi /etc/syslog.conf
Step 1
# vi /etc/syslog.conf
user.notice /var/log/syslog-orcl
# touch /var/log/syslog-orcl
Syntax to Restart syslog etc/init.d/syslog restart
Step 2
# /etc/init.d/syslog restart
Shutting down kernel logger: [ OK ]
Shutting down system logger: [ OK ]
Starting system logger: [ OK ]
Starting kernel logger: [ OK ]
Syntax to Modify AUDIT_SYSLOG_LEVEL initialization parameter on Database
AUDIT_SYSLOG_LEVEL = facility.level
Here the value of facility can be any of the below:
USER, LOCAL0-LOCAL7, SYSLOG, DAEMON, KERN, MAIL, AUTH, LPR, NEWS, UUCP or CRON.
The value of level can be any of the following: NOTICE, INFO, DEBUG, WARNING, ERR, CRIT, ALERT, EMERG .
Examples:
SYS> show parameter AUDIT_SYSLOG_LEVEL
NAME TYPE VALUE
------------------------------------ ----------- ------------------------------
audit_syslog_level string
SYS> alter system set audit_syslog_level='user.notice' scope=spfile;
System altered.
Restart Oracle instance
SYS> shutdown immediate;
Database closed.
Database dismounted.
ORACLE instance shut down.
SYS> startup
ORACLE instance started.
Total System Global Area 810053632 bytes
Fixed Size 2217712 bytes
Variable Size 645925136 bytes
Database Buffers 155189248 bytes
Redo Buffers 6721536 bytes
Database mounted.
Database opened.
Where and How to see log file?
# tail -f /var/log/syslog-orcl
Feb 27 11:37:39 RHEL5-ORQS Oracle Audit[18624]: LENGTH : '155' ACTION :[7] 'STARTUP' DATABASE USER:[1] '/' PRIVILEGE :[4] 'NONE' CLIENT USER:[6] 'oracle' CLIENT TERMINAL:[13] 'Not Available' STATUS:[1] '0' DBID:[0] ''
Feb 27 11:37:39 RHEL5-ORQS Oracle Audit[18827]: LENGTH : '148' ACTION :[7] 'CONNECT' DATABASE USER:[1] '/' PRIVILEGE :[6] 'SYSDBA' CLIENT USER:[6] 'oracle' CLIENT TERMINAL:[5] 'pts/1' STATUS:[1] '0' DBID:[0] ''
Test to Logon by sys: $ sqlplus "/ as sysdba"
SYS>
Syslog after logging as sysdba
# tail -f /var/log/syslog-orcl
Feb 27 11:40:12 RHEL5-ORQS Oracle Audit[19269]: LENGTH : '159' ACTION :[7] 'CONNECT' DATABASE USER:[1] '/' PRIVILEGE :[6] 'SYSDBA' CLIENT USER:[6] 'oracle' CLIENT TERMINAL:[5] 'pts/1' STATUS:[1] '0' DBID:[10] '1233539256'
Syntax to Audit sys operation (audit_sys_operations=true):
Example to display current value
SYS> show parameter audit_sys_operations
NAME TYPE VALUE
------------------------------------ ----------- ------------------------------
audit_sys_operations boolean FALSE
Example to enable Audit or set true
SYS> alter system set audit_sys_operations=TRUE scope=spfile;
System altered.
SYS> shutdown immediate;
Database closed.
Database dismounted.
ORACLE instance shut down.
SYS> startup
ORACLE instance started.
Total System Global Area 810053632 bytes
Fixed Size 2217712 bytes
Variable Size 645925136 bytes
Database Buffers 155189248 bytes
Redo Buffers 6721536 bytes
Database mounted.
Database opened.
Test Query with sysdba privilage: SYS> select count(*) from v$session;
COUNT(*)
----------
105
1 row selected.
Syslog after logging as sysdba
# tail -f /var/log/syslog-orcl
Feb 27 11:49:19 RHEL5-ORQS Oracle Audit[20698]: LENGTH : '183' ACTION :[30] 'select count(*) from v$session' DATABASE USER:[1] '/' PRIVILEGE :[6] 'SYSDBA' CLIENT USER:[6] 'oracle' CLIENT TERMINAL:[5] 'pts/1' STATUS:[1] '0' DBID:[10] '1233539256'
Enjoy it........................

How to auto start or run SAP Instance?

How to auto start or run SAP Instance?
This solution is only applicable to windows server.
1. RZ10
2. Select Startup profile
3. Create parameter autostart
4. Put value 1
5. Copy
6. Save and activate
7. Logout
8. Stop Instance
9. Restart Server
This time it will automatically start SAP Instance.

Regards,
Alihamed.sa

Email configuration in sap , Incoming Mail or Inbound mail configuration in SAP ECC 6.0 hp-ux Servers or windows servers

 Email configuration in sap

Incomming mail or inbound mail configuration SAP ECC6.0 .

Rz10 tcode

Create below prameters.

1)      Tcode   sicf

Create a     smail   “service user id” . which client will recevie email.

Profile S_A.SCON.

Tcode : scot

Connection between   Exchange server  to SAP Server.

1)      Create DNS record on domain dns server.

Create A record in DNS server

2)      Create MX record finding mail server

3)      Add a 192.168.1.68:25000 port to ironport.

How to reset root password on a HP-UX Integrity system

How to reset root password on a HP-UX Integrity system

Login to the console.

Enter the command menu:
MP> CM
Halt the system:
CM> RS
Go back to the MP> prompt by typing CTRL B then go back to the console:
MP> CO

When the system comes back with a series of boot options, highlight the HPUX boot option, click enter and click enter again to interrupt the boot process. Then boot in single user mode:

HPUX> hpux -is
Once the system has come up, you will have to mount the following file systems: /usr, /var, /var/tmp, /opt and /tmp. You will also have to fsck them.
# TERM=vt100
# export TERM

Find out which file systems need to be mounted:
# cat /etc/fstab
Mount the relevant file systems:
# mount /dev/vg00/lvol7 /usrUX:vxfs mount: ERROR: V-3-21268: /dev/vg00/lvol7 is corrupted. needs checking

# fsck /dev/vg00/lvol7log replay in progress
replay complete - marking super-block as CLEAN

# mount /dev/vg00/lvol7 /usr

# mount /dev/vg00/lvol9 /var
UX:vxfs mount: ERROR: V-3-21268: /dev/vg00/lvol9 is corrupted. needs checking

# fsck /dev/vg00/lvol9
log replay in progress
replay complete - marking super-block as CLEAN

# mount /dev/vg00/lvol9 /var

# mount /dev/vg00/lvol11 /var/tmp
UX:vxfs mount: ERROR: V-3-21268: /dev/vg00/lvol9 is corrupted. needs checking

# fsck /dev/vg00/lvol11log replay in progress
replay complete - marking super-block as CLEAN

# mount /dev/vg00/lvol11 /var/tmp

Repeat with /opt and /tmp

Remove root password:
# cd /tcb/files/auth/r
# vi rootRemove the line beginning with :u_pwd
Save the file and exit

# passwd rootType your chosen password. Make sure there is a numeric character.

Reboot the system:
# shutdown -r
NOTE: if your system isn’t a Trusted Computer Base system, there won’t be a /tcb directory. Therefore, you will have to:
# vi /etc/passwdRemove the password field from the root entry and save the file.

Reboot the system:
# shutdown -r
When the system comes back up:
# passwd rootType your chosen password. Make sure there is a numeric character.

SAP* User unlock and Delete

SAP* User unlock

****************************

db2 => update SAPIDS.USR02 set UFLAG=0 where BNAME='SAP*' and MANDT='000'

DB20000I  The SQL command completed successfully.

**************************************

SAP* User Delete

***********************************

db2 => DELETE SAPIDS.USR02  where BNAME='SAP*' and MANDT='000'

DB20000I  The SQL command completed successfully.

db2 =>