BACKGROUND JOBS FAILURE REASONS

                            BACKGROUND JOBS FAILURE REASONS

1. User and password issues(authorization ) user lock, userid expiry, password changes, lackof roles etc.
2. 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.
3. Variants are not properly defined.
4. deadlocks issue
5. update mechanism failed
6. table space overflow
7. table space max extent reached
8. archive struck
9. the memory is not sufficient no roll area, PXA BUFFER PAGE ERRORS
10. problems in the program and inputs
11. dependent jobs events failure
12. Target systems are not available to process the jobs.

                                   UPDATE MONITORING

1. update deactivated in sm14
2. programming problems in LUM
3. table space overflow
4. max extents reached
5. archive struck

                                         SPOOL PROBLEMS

1. page setting issues
2. cartridge issues
3. printer not available
4. paper out
5. print server not available
6. Drivers corrupt
7. Network issues
8. More request in queue.

                                      Export Import method

1. Client creation in target system
2. Logical system creation
3. Assigning logical system to created client
4. Local client copy
5. Memory availability
6. No user should logon(Down time needed depends upon client size)
7. Client export from source system through scc8.
8. Client import from in target system through STMS. DEV.
9. 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