Sap 000 Client Database

Dear Experts, Accidentally DDIC and SAP. user in 000 client has locked. We are using SYBASE ASE database. I know how to unlock user in other database (eg:update.USR02 set UFLAG = 0 where BNAME = ' and mandt =.

• Sap Clients List
• Sap 000 Client Database Login

Skip to end of metadataGo to start of metadata

Technical Points:

• Job logs are Temse Objects
• Every TemSe object consists of a header entry in table TST01 and the actual object
• Job log is a OS file which created/controlled by TemSe
• Job log could not be larger than 2GB Because of the Temse limit
• Job log is saved under OS /usr/sap/<SID>/SYS/global/<client>JOBLG/ DIR
• Job will be cancelled if job log could not be created
  

Symptom:

Sap Clients List

Job canceled in SM37, there is no job log available, when try to display job log, it shows “Error reading job log”, like .

Root Cause:

Typical issues:

1) work process DB errors

For the 'job details' screen, you can see the exact time stamp of job starts('Scheduled Start' item). On the exactly job start time stamp, The error log entry like below can be seen in system log(sm21):

As mentioned in 'technical points' section, job log are also Temse objects, header entry and actual objects are store in TST01 table. Because the 'BY M SQL error -1 occurred' DB error occurs when job starts, job log TemSe object could not be updated into table TST01, job log creation failed, and therefore, job cancelled accordingly.

Please be aware that the following errors are just sequence errors of 'BY M SQL error -1 occurred' DB error.

BTC 012 000 SAPSYS F6 H Database error: TemSe->XRTAB(0)->1 for table TST01 key [<client>]<job log name>,1
BTC 012 000 SAPSYS F6 H Database error: TemSe->XRTAB(0)->1 for table TST01 key [<client>]<job log name>,1
BTC 012 000 SAPSYS F6 H Database error: TemSe->XRTAB(0)->1 for table TST01 key [<client>]<job log name>,1
BTC 012 000 SAPSYS F6 H Database error: TemSe->XRTAB(0)->1 for table TST01 key [<client>]<job log name>,1
BTC 012 000 SAPSYS EC F Failed to create log for job <job name and job count>/
BTC 012 000 SAPSYS EC J Failed to enter message 00& (application area 55) in job log
BTC 012 000 SAPSYS F2 0 Calling program reports invalid handle for TemSe object (magicX'NULL-ptr')

You are getting error 'error reading job log' while reading the job log for the canceled jobs because there is no job log at all due to 'BY M SQL error -1 occurred' DB error.

2) Job log could not be created on OS level

On exactly the same time stamp of job starts , the following log can be seen in system log(sm21):

<Error NR> above normally is 22(Windows OS) or 28(Linux/unix OS) from OS level.

'F3 V Error <Error NR> for write/read access to a file' error means that the job log file could not be created under /usr/sap/<SID>/SYS/global/<client>JOBLG/ DIR at that moment.

Sap 000 Client Database Login

Normally, you should check if there is enough space left in /usr/sap/<SID>/SYS/global/<client>JOBLG/, if /usr/sap/<SID>/SYS/global/<client>JOBLG/ can be access without any problem, if /usr/sap/<SID>/SYS/global/<client>JOBLG/ is full with job log file. you can just try to delete the useless job log file by running RSBTCDEL2 program and check if situation improved.

if OS is Windows, you can refer to 1909093 - How to check „file access“ problems on Windows platform for troubleshooting.

Please be note that the following errors are just sequence errors of 'F3 V Error <Error NR> for write/read access to a file' error.