RSDBAJOB failing Message no. 00564

Hi,

I have a job running as a systems user which keeps failing. At first there were two instances of the job running at the same time. I deleted the one and afterwards it still failed.

The message in the Job Detail log is Action in SDBAP unknown

I found the following note pertaining to this Note 368023. I have rescheduled the job for tomorrow morning.

I have also found another comment related to this issue on one of the other sites. Where the person mentioned to browse the SDBAP table to see if there is entries related to this job available in the table. I assume this was related to the scheduling of the job. Has any of you done this?

Johan
LVL 2
profjohan11Asked:
Who is Participating?
 
profjohan11Author Commented:
Hi guys,

I have found the solution. In my case the problem was that I had to patch the update tool to the newest level. This is a tool that is located with the binaries in the /usr/sap/SID/SYS/exe/run directory. Filename dmdb6srp it was on patch level 23 and is now on patch level 26. Hope this may help you guys.

I still have a problem with the jobs being duplicated but need to implement a note to correct that which I can only do in the new year.

Regards,

Johan
0
 
studdertCommented:
Hi Johan, I've hit a similar error mesg with a regularly scheduled job on my system. Some points/questions:

   -note 368023 appears to apply only to R/3 4.6, so unless you're running that (and are below the quoted patch level) this won't apply. It doesn't apply for me, we're running ECC 6.0.

   -what is the job that you're running? I'm running a checkdb job but the important point is the program that this is executing, what is this? Are you scheduling the job using 'db13' or 'sm36'?

   -you say you're running it as a "system" category user, does this user have SAP_ALL permissions?

   -I had a look using se11 + se16 at table SDBAP but this is only used AFAIK if you schedule your job with 'db13'. In any case all it shows is what you can see by going into the job within 'db13' anyway.

   Might be able to help further if you can answer the above. Still looking into my own issue here, have a couple of leads. I'll post again if I resolve it. Cheers, John.
0
 
profjohan11Author Commented:
Hi,


I am currently running 620 on my system.

SAPKB62055
SAPKH47025

So the note is not applicable to me. And yes the system user has all the necessary authentication.

And I have rescheduled it more than once.  Using different variations and users.  The job running on my system is a DBSTAT job.

Will still dig aroung on my side.

Johan


0
Cloud Class® Course: Microsoft Windows 7 Basic

This introductory course to Windows 7 environment will teach you about working with the Windows operating system. You will learn about basic functions including start menu; the desktop; managing files, folders, and libraries.

 
profjohan11Author Commented:
Hi,

I found this note 212868  which suggest the following actions.

Once again not valid for 620 but may assist you.

Call Transaction SE16 and delete all entries which have the value 'RCHCK' in the field BTYPE.
From the background job overview (Transaction SM37) delete the scheduled job. As a selection criteria, enter the job name 'DBA:STATC_CHECK*' and the user name

Johan
0
 
profjohan11Author Commented:
Hi,

Studdert I managed to find this note have a look at this.

752572

It is jobs that have replaced older runstats jobs I am testing it in my development environment tonight.

Regards,

JOhan
0
 
TwisteddkCommented:
Likely your jobstatus has "unknown" because it has not been able to write a status to the joblog file. Check all job tables for incorrect or in processing jobs that might match your job. If this is a DBA job, also check failed and scheduled jobs in SM37 aswell as jobs listed in DB13.
Additionally ensure that all dialloge and backgound processes are running in your system SM50/SM51. Also review tracefiles ST11 at around the time of the job execution, aswell as system log SM21 and error messages ST22.
If the job is a default SAP job try creating a message on the service system http://service.sap.com/message
0
 
studdertCommented:
Thanks for the tips Johan, apologies for not posting back I actually forgot about this question posting as I found out that I could just de-schedule this job, it wasn't necessary (I setup separate checkdb runs later without any issue), and without it repeatedly annoying me I completely forgot! Well done on finding the solution, appreciate you posting it here -- in the event that I run into a similar issue some other time it could be very useful.
0
 
profjohan11Author Commented:
Patching the update tool solved the problem
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.