Friday, November 16, 2007

SAP FORUM : Review SM13 on Manual Check

Now about SM13
The Question is:

  1. What do you know about SM13 Check?
  2. If you found error, how you must report that error (for email report)? I ask this, because for this T-Code we have different way to report the error.
------------------------------answer---------------------------------------

I’ll try to answer J

1. About SM13 transaction code:

  • SM13 (generally) is Update management tcode.
  • SM13 used for checking terminated update records on our manual check.
  • Basically Update management is used for the following:
    • Display update requests.
    • Analyze problems pertaining to the update.
    • Test and debug canceled update requests.
    • Display and reset the status of update requests.
    • Delete update requests.
    • Display statistics on updates.
  • SM13 transaction code is basically used to monitor the update statistics. In this tcode we can find out if any uncommitted updates are there for a particular user. We can check critical updates and non critical updates here. And also we can specify the date and time when there is an update error happened in our system. In netweaver system, Shift +F5 will lead us to the administration of the update system.
2. I don’t understand the question. But based on my opinion, my skill J, my knowledge, my head, my habits, this answer to report by email:

Terminated update records happen on the system for Solidpack SPP, number of entries is 3

Detail:

Clnt User Date Time TCode Information Status

800 EBOSMAN 06.03.2007 13:11:44 CO40 Err

800 IF_OMPSAP 20.03.2007 08:15:12 CO02 Err

800 IF_OMPSAP 21.03.2007 09:39:47 CO02 Err
Make sure all that record with date (red marked font) yesterday or today, exception on Monday, where you also inform Friday to Monday and on system that has to be checked once a week or once a month, we should also have to review the date from the previous week.

That’s all my answer, CMIIW, thanks


------------------------------answer---------------------------------------

Just one to underline about Question no 2

If you found error, how you must report that error (for email report)? I ask this, because for this T-Code we have different way to report the error


The way to report this error is:


-
as you can see, you found an update terminated below

- When you found error like above, please also give the reason by click the error two times and you will be go to screen (see below),

put function module and error text from screen below

This is example report you can place on the email report to customer:

Update terminated happen on the system

Detail:

Cln User Date Time Status

100 DDIC 22.03.2007 11:17:19 Error

Function module: CRM_ORDERADM_I_UPDATE_DU

Error detail: CRM_ORDER_MISC 002: Error in updating object ORDERADM_I

For Question 1 this is my answer I found from SAP R3 Administration made easy; maybe this can update your knowledge about this T-Code

A failed update, or an “update terminate,” is an update to the failed database. These failed updates occur when a user entry or transaction is not entered or updated in the database. The following analogy should help clarify this concept:

1. A secretary gives a file clerk a folder (similar to a save).

2. The file clerk gives the secretary a receipt (similar to the R/3 document number).

3. On the way to the file cabinet, the clerk falls, and gets hurt.

The folder in not put into the cabinet (this is the failed update).

4. The end result is the folder is not in the cabinet—even though the secretary has the receipt.

For performance reasons, the database update is done in asynchronous mode. In this mode, the user continues to work while the system takes over the update process and waits for the database update to complete. In synchronous mode, users would have to wait until the database successfully updated before they could continue to work.

Continue Reading...

SAP FORUM: Review DB12 on Manual Check

After some little investigation, I found some different opinion about how to handle manual check or SSM, I think this is because we have shift working on our daily operation. Base on that reason, I want to review about our daily operational with this forum.

Please answer and reply this email by your knowledge about any issue we founded, and we will start with Manual Checking until we found same perception about how to handle every event.

DB12:
Below is result from Database backup (SQL Server database) DB12 manual check. We check this on Monday 19/03/2007.

The question is:

1. Are below result is success or not

Last Successful Backups:
Full R/3 backup 16 Mar 2007 04:13:15
Full master backup 15 Mar 2007 23:49:54
Full MSDB backup 15 Mar 2007 23:49:44

Last Successful Backups:
Full R/3 Backup 15 Mar 2007 23:06:06
Full Master Backup 15 Mar 2007 20:45:43
Full MSDB Backup 15 Mar 2007 20:45:29

2. How about this

Last successful backups:
Full R/3 backup 14 Mar 2007 23:43:20
Transaction log backup 15 Mar 2007 12:16:48
Full master backup 14 Mar 2007 23:43:26
Full MSDB backup 14 Mar 2007 23:43:38

-------------------------Answer-----------------------------

I’ll try to answer based on my knowledge (and of course SOP too)...

1. Are below result is success or not

Last Successful Backups:
Full R/3 backup 16 Mar 2007 04:13:15 (Friday Morning)
Full master backup 15 Mar 2007 23:49:54 (Thursday night)
Full MSDB backup 15 Mar 2007 23:49:44

Last Successful Backups:
Full R/3 Backup 15 Mar 2007 23:06:06 (Thursday night)
Full Master Backup 15 Mar 2007 20:45:43 (Thursday night)
Full MSDB Backup 15 Mar 2007 20:45:29 (Thursday night)

Success!!

Taken from SOP “If last successful backups to today-morning or yesterday-night, except for Monday check which OK if last successful backup on Thursday night, Friday Morning/Night."

2. How about this

Last successful backups:
Full R/3 backup 14 Mar 2007 23:43:20
Transaction log backup 15 Mar 2007 12:16:48
Full master backup 14 Mar 2007 23:43:26
Full MSDB backup 14 Mar 2007 23:43:38

Unsuccessful!!

Because that result happen on Wednesday night and Thursday Morning. If we have assumption that this perform on Thursday 15th, it’s successful.

-------------------------Answer-----------------------------

OK, I’ll try to answer this question too, from my opinion the backup is not success because, for point off number one :

1. Are below result is success or not

Last Successful Backups:
Full R/3 backup 16 Mar 2007 04:13:15 (Friday Morning)
Full master backup 15 Mar 2007 23:49:54 (Thursday night)
Full MSDB backup 15 Mar 2007 23:49:44

Last Successful Backups:
Full R/3 Backup 15 Mar 2007 23:06:06 (Thursday night)
Full Master Backup 15 Mar 2007 20:45:43 (Thursday night)
Full MSDB Backup 15 Mar 2007 20:45:29 (Thursday night)

Unsuccessfull !!

The backup is finish on date 16 Mar 2007 04:13:15 (Friday Morning), and because we check on Monday

it’s should be finish on Sunday night or Monday morning, and when I take a look on the backup history looks like the backup is running (schedule) every day see the picture below:















So the backup should be finish every day (today-morning or yesterday-night).

And for the point number 2 this is definitely Unsuccessfull if we check on Monday 19-03-2007.

2. How about this

Last successful backups:
Full R/3 backup 14 Mar 2007 23:43:20
Transaction log backup 15 Mar 2007 12:16:48
Full master backup 14 Mar 2007 23:43:26
Full MSDB backup 14 Mar 2007 23:43:38

OK that’s all Thank you, and correct if I’m wrong ....


-------------------------Answer-----------------------------

You are true if your reason base on the sop, but I think there is need little correction to the SOP.

The reason is: I agree with F**y, if we check backup on Monday, the result show from Friday night until Monday morning is success backup. So if the result is Thursday night it should be failed backup. And the rights answer for question 1: Backup Failed

-------------------------Answer-----------------------------

Regarding the backup issue, these are some of the concepts:

· If the Backup was scheduled Daily, it means that on today’s backup check, we are check whether yesterday’s backup end with success or not. And because it’s run daily for Master, MSDB, and Full R/3, it means that for today’s backup check will be successful when on DB12 check said that the date of last successful backup is Yesterday Night (> 18.00) or today morning, except for Monday check, because what we check is backup for Friday, so it will be stated as successful backup when on DB12 said Last successful backup on : Friday Night (>18:00) or Monday morning or in time between Friday night and Monday Morning (it can be Saturday or Sunday).

So, according to the concept, point 1 was not success and need to be reported (also ticket if necessary). While for the SOP, it needs to be adjusted.

· For Transaction backup: we have to check whether it was set on or off, by run transaction DB02 and if we find the recovery mode was simple, it means that the Transaction log is set to off, further, it means that the transaction log backup is not necessary to be checked, but the other backup (Master, Full R/3 and MSDB) still need to be checked. One important thing here: if you found on Production system the transaction log backup was set off (Transaction log is not success), please reported this as an issue.

· Backup should not running inside office hours, so if you find backup running during the office hours (HOLLAND OFFICE HOURS) please report this as an issue, and also ticket if necessary.

· When you find backup is not successful on Manual check, please also check on SSM, and add the info about backup there (check whether backup is currently running or not, and so on).

For point 2, it’s already obvious according the concept.

Continue Reading...
 

+dimanaanakku+ Copyleft © 2009 AllFight Deserved | WoodMag is Designed by Ipietoon and Modified by Yafet St. OfGod