Let it be more efficient, more wealthy and more healthy for all of us.

Posted by admin | 4 Comments »

I wish you a Marry Christmas and a Happy New Year!!!

Posted by admin | 3 Comments »

You can find a lot of useful information in the section Resources, in the section Useful Links and also in the section Useful Books, that I personally think all SAP and Oracle Administrators must read one day.

Posted by admin | 2 Comments »

Sometimes some newbie SAP administrators are wondering what to do on a daily basis, what to check, how to check, what does it mean a strange message, etc.

Of course a lot of companies have their own procedures for System Administration and Monitoring. Here I will give an example what could be checked and what should be paid more attention to.

These transactions I will explain in more details one by one in separate postings. Here they are included in brief.

List of SAP Systems you can see with transaction SM51. Actually a lot of other transactions could be started from here.

One of the most important things is the System Log. The transaction for it is SM21. Here you can see a lot of information, warning and error messages. Of course error messages should be treat with big attention, but all other should be checked as well.

The next one are Short Dumps. Their appearance is logged in the System Log. So, if you found a message for a short dump, you could start transaction ST22 and check the dumps.

Next could be check of database activities and performance via transaction ST04 or ST04N. You can see current activities, some useful and important indicators.

Batch job activities are also important as well as regular users activities. Some batch jobs are very important especially from business point of view. SM37 will help you in this case to find whether all is OK or there are some jobs failed.

SMQ1 and SMQ2 will give you an overview of Outbound and Inbound queues in the system if there are communication with other systems, i.e. R/3 with CRM, CRM with BI, BI with R/3, CRM and SCM, etc.

Database backups are also very important, because in case of failure the presence of backups is only thing that could help to recover the systems. DB12 is the transaction you can use to check database backups as well as archiving of online redo log files.

SLG1 give you an opportunity to check the Application Log.

SM50 – the status of Work Processes on the instance where you are logged.

SM66 – System-wide Work Processes Overview.

SM12 – Display and delete Locks on SAP level.

SM13 – Administrate Update Records.

ST03N – Performance, SAP Statistics, Workload – very useful transaction.

ST02 – Tune summary – buffers, memory, etc.

ST06 – Operating System Monitor.

ST05 – Performance Analysis – it is used on demand for SQL, Enqueue, RFC or Buffer trace.

There are a lot of other transactions for System Administrators. Some of them are dependant of the system itself. These ones are valid for all kind of SAP systems.

Posted by admin | 4 Comments »

Maybe I must start with a simple classification of the OSS notes first.

There are three types of OSS notes.

1. Descriptive – in this notes you can find a description of a problem and how to resolve it with means of customizing or different settings in the system. Kind of these notes are FAQ’s, general notes for something – there is collection of OSS notes related to any problem.

2. Code correction – these notes are easily to implement with SNOTE transaction.

3. Mixed type – in this case there are some manual corrections or customizing in the system described in the note and also code correction implementation. Implementation could be before or after manual corrections – this is described in the note and is very important in some cases.

The other classification of the OSS notes is: release dependent or release independent. Below we will discuss about release dependent OSS notes with code corrections.

First you need to check the section “Affected Releases”. You must find whether your release is mentioned there. After that you must check in the next section “Correction delivered in Support Package” for your release what Package Name is mentioned there. If this package is greater than what you have installed in the system then the note is applicable. The opposite – when the package in the note is equal or less than yours – the note is not applicable, because the functionality delivered with the note are already in the system.

Some times there is a section “Related notes”. Some of them could be a prerequisite for our note. It is better practice you to check the correction instructions, because there you could find also the prerequisites, even though they are not mentioned as related notes. It is better you to check these prerequisites (if there are) before implementing, because some of them could consists of manual corrections.

Posted by admin | 3 Comments »

And again back …

Posted by admin | 5 Comments »

It is great … sea, sun, breeze, dreams …

Posted by admin | 3 Comments »

Task

You would like to change the ABAP program package from $TMP to a z* package.

Solution

You could do this with the following steps:

In SE38, enter your program name. Then use the menu option “goto -> object directory entry”. Click on “Change”, and you can enter the new package. You’ll be prompted for a workbench request number also. The same technique can be used to change packages in other objects.

You can also use transaction SE03 (or the tools option from SE09/SE10), but access is sometimes restricted.

Posted by admin | No Comments »

You would like to find the indexes for a table in Oracle database.

You could find this with the following SQL using user_ind_columns view:
Select table_name, index_name, column_name,

FROM user_ind_columns

WHERE table_name= ‘My_Table_Name’;

If you want to find Column position then add column_position column in the query.

My_Table_Name is the name of the table which you would like to check the history of the statistics for.

In an SAP system you can use the report RSORADJV for this purpose or use SQL*Plus at OS level.

Posted by admin | 4 Comments »

It is a little bit late for some countries, but for other it is still valid – 31 July is a SysAdmin Day this year.
I would like to wish all the best to all colleagues – Sys Admins and they to be as always very professional and good in all their activities in computer’s areas.

Posted by admin | 4 Comments »