Sunday 27 July 2014

MESSAGE_TYPE_X dump in SAP

MESSAGE_TYPE_X  dump in SAP 

Find Your Message_Type_X dump on the list 


Double Click


Now You can see detailed information about dump

find the "source code Extract" area as shown below


Let  check the related line which is selected on the left side of the screen


You should see a "Message Info " Like message x001(ok)" for your example


Now get the info what is we need
Message   Class :Ok
Message number :001
Its time to check what does it mean , 
go to T-code SE91 


for click on DISPLAY button for the related info
Now you should see the detail information for the Message_Type_X dump like below



Statistical Information About Any SAP background job in SAP Enviornment

Statistical information about Any SAP Background Job 

Goto SM37 t-code select the Job which you want to get Statistical data for it

F8/Execute
Menu Steps:;
Goto --->Job Statistics

Then you will get the Job Statistics information like Below






Background Job Analysis Using ST13

Background Job Analysis Using ST13

Go to ST13 t-code
Press F4 to Get List


Select of them which you want to Execute
For example for Background Job Analysis  Select
"'BACKGROUND_JOB_ANALYSIS"   and execute

Batch Job Analysis Screen will be shown  and select the input areas as you wish

F8/Execute

You will get the Results







Complete information only for activated RFC calls (> settings) on SAP System

Complete information only for activated RFC calls (> settings)  on SAP System


Go to SM66  tcode you should see the message below

When you double click on message then you can get the details as follows

So Now go to -->Process list-->Settings--->Change

Uncheck the selection "Display only abbreviated information ,avoid RFC"

And Save it before exit

New License steps to Apply on SAP Netweaver 7.3 Java Stack

New License steps to  Apply on SAP Netweaver 7.3  Java Stack

Go to Netweaver Administration Tool  (NWA) Screen

Choose the "Check License " selection under "License and Certificates" area by Clicking the License option
Click The "Install from file" button to open new window to point the license file

point to license file location via "Browse" Button
Select the license file from the location and push the "ADD" button
After  the process is complete you will see screen like below

Applying license process has been complete.








How to Make Relased Transport to UnReleased in SAP System

How to Make Relased Transport to Un Released

Go to SE38 t-code execute the program RDDIT076



Click F8 /Execute



Request/Task :Request number which we want to change


F8/Execute


Now Check the Coloumn "STAT" if you see  "R" for the selected request then it means the request has been Released.

Then we have to press Change Button and Change R  Letter to D.

Now you have unreleased the specific request.

T-codes Executed By User

T-codes Executed By User


Go to  ST03 t-code on your SAP system and follow the below steps

ST03->Select DATE>User profile



Double click on the username from the right panel of the screen for the user which  we want to check 


We Should see the t-codes list for the selected user name for the specific date

                                                                      

Monday 21 July 2014

JARM

JARM- Java Application Response time Management



Used to fetch the information of users,threads,components and requests .similar to ST03 -Work load analysis

Log Viewer Standalone Tool

Log viewer Standalone Tool


It is used  to provide the log access at os level,when the instance is not started and also used to display the logs based on search text,date and time , severity etc..

/usr/sap/sid/DVEBMSG\j2ee\admin\logviewer.standalone

Cluster in SAP

Admin Directory:Used for administrating the J2EE engine using Visual Admin Tool .It also contains the directory standalone log viewer to display the logs of the J2ee engine if not started

Dispatcher+Server=Local instance (Cluster)

Cluster:It specifies the dispatcher ,server and bootstrap process.It contains binaries that are required to start the above process.It also contains instance proprties to start the instance(We can find by what time the instance is started)

Cluster\dispatcher\log

Defaulttrace0.trc is a file available in the log directory for both server and dispatcher.

Config tool:It provides a tool to change parameters of the instances either globally or locally.

Deploying:It is a tool  that is  used to deploy the small programs in to the JAVA Engine

JSPM:It is a tool applying patches (JAVA Support pack manager)

Log Directory:sol\DVEBMGS00  it specifies the MMC log/SM21 logs with log goto slog-clear all the logs and that is equal to Syslog

Sunday 20 July 2014

SQL Server Restore

SQL Server Restore


1. Open SQL Server 2005 Management Studio. 

2. Connect to the appropriate server. 

3. Expand Databases. 
4. Right-click the desired database, Select Tasks, Restore and select Database. 
5. The Restore Database window will appear. 
6. Ensure that the correct database name appears in the To database field. If not, select it from the dropdown. 
7. Under Source for restore, select the From device radio button. 
8. Click the button next to the textbox to select the device to restore from. 
9. The Specify Backup window will appear. 
10. Click Add and locate and select the backup file from the Locate Backup File Window. Click OK. 
11. Under Select the backup sets to restore, select full 
12. In the left pane, select Options. 
13. Under Recovery state, ensure that the Restore with Recovery radio button is selected. 
14. Click OK to begin restoring the database. 
15. Once the restore is complete, a notification box will appear. Click OK to close the box. You have now restored your database to the date of your backup. 


ORA-01017: Invalid Username/Password; Logon Denied

ORA-01017: Invalid Username/Password; Logon Denied

Check SAP Note 400241

Process to Open OSS Connection

Process to Open OSS Connection:

Login into service market place go to --àhelp and support->Connect to SAP

In the above screen click on Maintain Connections  TAB
This will lists below screen


Select the system  you want to open connection for SAP

Click  on system data
Make sure that SAP Router is connected


Click on maintain access data

The secure area will be shown


If modify  click below image will be shown






Sunday 13 July 2014

Long Running Transport Troubleshooting

Long Running Transport Troubleshooting


1.Go to Stms_import t-code
Long running issue due to following
a.Non availability of space to perform the operation.(ie file system or table space is 100% full)
solution:
Check out if any of the file systems(like sapmnt,oraarch etc )of the central instance ,Database and application servers is 100% full.If so , add necessary space,which resolves issue automatically and completes the import of Transport.
Also ,Check out tablespaces fill levels .If auto extend is off and table space is 100% full then add sufficient datafiles ,which resolves the issue.

b.RD* jobs are not running in SAP System
Solution:;
Check out in SM37 whether RDD* Jobs (RDDIMPDP,RDDIC3L,RDDVERSL etc)
 are running or not ,make sure that they are scheduled and perform import of transport of again.
c.Update got deactivated.
Solution:
Check out in SM13 whether  update is active or not .If not active ,Activate it and import the transport .
d.There are no free background processes.
Check SM50 whether all background workprocesses are running status.If so you would need to wait for the free background workprocess to run RDD* jobs to complete the Import  of transport .To Avoid issue in future increase the no.of background processes.
Transport Not Getting Terminated , How to Terminate:
If you unable to terminate a transport which is running , go to SM50 t-code and identify the PID of the transport process .Try to  cancel  the process without core.
2.IF it is not getting terminated from SAP Level, then go to OS Level and kill
In the windows it is taskmanager
In the unix  it is kill -9 PID
3.IF Tpt not getting terminated then go to import monitor delete entry.


Saturday 12 July 2014

How to Open a Client in SAP

How to  Open a Client in SAP
1.Go to t-code scc4.This will lists Clients Overview a below


2.Double click on the client  needs to be opened.

3.In the above screen ,  we can see that highlighted option that no changes allowed and no changes to repository and cross client customizing objects.These 2 settings means client is NOT Opened.
To open the Client we should set the client settings as shown below


In addition to the above 2 settings ,   in SE06 ,system change option should be set to “modificable”
As shown below


Go to t-code SE06
Click on System change option  go below screen

In the above Screen go to Global Settings as “modifiable “ make sure client is opened.
Above settings can be done from  SE03 t-code as well

                                

Friday 11 July 2014

SAP JAVA Request Flow

JAVA Request Flow

1.User Submit the request.
2.Request is handled by JAVA Dispatcher.
3.Dispatcher assigns the least loaded process.
4.Server Process assigns application thread manager to process request.
5.Server process the request till it is completed /or the memory is exhausted/timeout.
6.ATM Handles the user request internal  process/Intra process(For  Locking)is handled by server process.
7.Server process communicates with DB and the response is sent back to the user.
8.Central services are used for load balancing and locking purpose.(During the update)

SAP ABAP Request Handling

ABAP Request Handling

1.User Submits he request using GUI.
2.The Request is received by the dispatcher.
3.Dispatcher keeps the request in queue.
4.Dispatcher serves the request base on FIFO.
5.Dispatcher assigns the request to Work process.
6.Work process handles the request using the Work  Process Task handler.
7.Task handler interpret the request and submit the request to database.
8.The Database process the request and response back to the user.

Ports

Ports

3600 -3697  - ABAP Message Server
3900-3999   -JAVA Message Server
3200-3297 - Dispatcher Port
4700-4797 -Dispatcher Security Port
3300-3397-Gateway port
4800-4897-Secured Gateway Port
50000 --JAVA instance port if instance number is 00
if instance number is 25 then 52500



Installation of Instances

It is an integrated installation which consists of
1.Central Services Instance
2.Central Instance
3.Database Instance

Central Service instances are provided in JAVA Engine which consists of JAVA Message Server and Enque server to provide load balancing to the web users and central locking for all the JAVA instances.

Dialogue Process- Foreground
ABAP Instance : Central instance
DVEBMGS

Dialogue Instance: Except Message and Enque
Database Instance:Database processes
JAVA Instance:Consists of Dispatcher  and Server Processes.

Notes,Support packages,Support Stacks and Enhancement Pckg

Notes(Patch):This does the small corrections
Support Package:Group of Patches
Support Stack:Group of Support Packages(ABAP,BW,BASIS)
Enhancement Pckg: is an upgrade to the current functionality

What is a Netweaver

Netweaver :Is a common platform which provides EP,BI,ABAP & JAVA & Mobile integration

Sunday 6 July 2014

Delete Short Dumps

Delete Short Dumps


Method 1 : Dump analysis: Reorganization
• Go to transaction code ST22. Choose ‘Reorganize‘. You can now select all
short dumps older than n days for deletion.
Warning: If a large amount of records are deleted simultaneously during the
reorganization, ORACLE error ora1562 ‘failed to extend rollback segment …’
may occur. In this case, refer to error Note 6328.


Method 2 :  Drop and recreate the SNAP table
• With the database utility transaction code SE14, you can drop and
recreate the SNAP table.
Warning: When you do this, ALL short dumps are deleted.


Method 3 : Reorganization program RSSNAPDL
• To avoid database problems, this program deletes old short dumps
gradually from the SNAP table unless they are selected for retention. With
standard setting all short dumps that are older than 7 days and that are
not flagged are deleted. Since this program occupies the database when
large datasets are processed, it should be scheduled to run overnight.
Execute RSSNAPDL in transaction SE38

The Latest Support Package Stack is not visible in Maintenance Optimizer

The Latest Support Package Stack is not visible in Maintenance Optimizer.


Maintenance Optimizer retrieves the list of available support package stacks from Service market place. However it caches that information and retrieves a new version only once a day.
You need to delete the cached information .That way you force maintenance optimizer to reread the list of support package stacks from service market place. Refer  SAP note 1165587 for further details.

SAPPAD

SAPPAD


SAPPAD is a  tool for editing all files on windows and even Unix LF-only files -  better than notepad.

Friday 4 July 2014

SMD Agent Not Able to Connect Solution Manager

SMD Agent Not Able to Connect Solution Manager


Check SAP Note: 1611483 and 1992309

BRBackup return codes

BRBackup return codes

0 - Successful backup/restore. 

1 - Backup/restore ended with warnings. All files were saved/restored. 

2 - Backup/restore canceled during the initialization phase by a user or another signal. 

3 - Errors occurred during the initialization phase, backup/restore was not started. 

4 - Backup/restore was canceled by a user or another signal during processing. 

5 - Backup/restore was started, but not completed because errors occurred during processing. 

6 - Internal termination of the backup/restore (this value is also visible in summary logs during the program run)
 9 - Program run was not complete (this value is only visible in a summary log stored on a backup medium)

Tuesday 1 July 2014

SAP_APPL profile is not Showing in Export

SAP_APPL profile is not Showing in Export


Check SAP Note 619519

Sent Mail to Distribution List Mail fails for one user Recipient xxx does not exist in the address management"

Recipient xxx does not exist in the address management"


Make sure that  users have an e-mail address in their user master record (tcode SU01). 

Permissions for the Tool SUM to perform Upgrade

Permissions for the Tool SUM to perform Upgrade

User: sidadm Group: sapsys chmod: 770