BACKGROUND JOBS FAILURE REASONS IN SAP SYSTEM

 BACKGROUND JOBS FAILURE REASONS

User and password issues(authorization ) user lock, userid expiry, password changes, lackof roles etc.

file system problems, btc reads from the file system to update the database, file not opened or corrupted, file sharing, file came with different characters, file not found as well.

Variants are not properly defined.

deadlocks issue

update mechanism failed

table space overflow

table space max extent reached

archive struck

the memory is not sufficient no roll area, PXA BUFFER PAGE ERRORS

problems in the program and inputs

dependent jobs events failure

Target systems are not available to process the jobs.

UPDATE MONITORING

update deactivated in sm14

programming problems in LUM

table space overflow

max extents reached

archive struck

SPOOL PROBLEMS

page setting issues

cartridge issues

printer not available

paper out

print server not available

Drivers corrupt

Network issues

More request in queue.

Export Import method

Client creation in target system

Logical system creation

Assigning logical system to created client

Local client copy

Memory availability

No user should logon(Down time needed depends upon client size)

Client export from source system through scc8.

Client import from in target system through STMS. DEV.

Client import post processing through scc7 in target client. QUA

Transport Got hang what are all to check

1.       Check RDDIMPDP JOB RUNNING OR NOT FROM SM37

2.       IF NOT RUNNING START RDDNEWPP FROM SE38

3.       CHECK FILE SYSTEM IS FULL

4.       CHECK TABLE SPACE

5.       CHECK ORAARCH IS FULL

6.       CHECK SYSTEM IS UP ARE NOT

7.       CHECK USER IS LOCKED OR NOT OR EXPIRED

  

What are all thing need to check when system is down

1.       check services like saposcol , sapsid ,orasid ,oralistener,oraagent-----5 services

2.       check network if Ip is reachable or not

3.       check file system

4.       check table space

5.       check database is reachable or not with command //// r3trans –d -----Return code 0000/0004/0008

6.       If db not reachable check db alert file.//////

Path: oracle/sid/ora102/saptrace/backgroundtrace

7.       Check work process over view with//////  ps –ef .

8.       check any offline backup running or not by using “ ps –ef|grep backup”

9.       check disp log message server log and work directory logs

10.   check work directory logs