cancel
Showing results for 
Search instead for 
Did you mean: 

DB13 jobs not working

former_member188806
Participant
0 Kudos

Hi,

We are not able to execute any jobs from DB13.

The same can be run from the O.S. level without any issues.

SAPXPG is working fine.

Its a 4.7 system on Unix, with Oracle 9.2.0.5.0.

Pls help.

Thanks,

Saba.

Accepted Solutions (0)

Answers (2)

Answers (2)

former_member227600
Contributor
0 Kudos

Hi,

Can you paste DB13 job logs here.

Thanks

karan

Former Member
0 Kudos

Hi

You can try these options:

1. try to connect with <SID>adm in Windows/Unix, execute : brconnect -u / -c -f check , if you have always the same problem, try to execute sapdba_role.sql with sql

sqlplus /nolog

connect /as sysdba

sql>@sapdba_role SID NT/UNIX

2. When you configure the backup in db13 that will create the background jb you can see it in sm37, so go to sm37 change the user name on which the ob is running and rerun the job this is because the user at r3 level doesn have the authorization you can do it like this.

3. But if the user name and password is incorrect with the database user yu can you can check it in st04 -->detail analysis menu -->oracle session. b which user the SAP is running the backup command then check the user exiss in database if exists reset it.

nelis
Active Contributor
0 Kudos

Hi sumant,

Are there any error messages in the job logs ?

Regards,

Nelis

former_member188806
Participant
0 Kudos

Hi,

There are absolutely no logs..either job or action.

The minute you start a job, its font changes to red & the background color remain blank..SM37 shows the job as cancelled, with no logs.

Thanks,

Saba.

markus_doehr2
Active Contributor
0 Kudos

And the joblog in SM37?

Markus

former_member188806
Participant
0 Kudos

No job log available:(---was the message when you try to view the log.

Thanks,

Saba.

Former Member
0 Kudos

Hi Sumant,

Is your system a distributed system? It sounds like when the DB13 job fires off it can't find the corresponding executable file and as a result just terminates without any messages.

I've had this happen to me but on a distributed system.

Regards,

Chengappa

Former Member
0 Kudos

HI ,

are you able start/stop DB through <sid>adm.If not then first thing to check the dev_w0 Log fo the same.

Next suggestion would be to update the dbsl for OS/DB specific. and Update the brtools .

Hope this will help.

To me its seems like the Softlink or oracle shared library issue.

can you paste the dev_w0 log ?

Regards,

King V.