Question from sdn :
We got a situation :Unable to Kill the Background job (BI_REQ*).It shows "ACTIVE" and been running for more than 19,000 secs (2 days..) .When this job started ,the PROCESS ID was : 244277..But after a day,this PROCESS ID : 244277 has been allocated to some other R3 Program(Monitored in SM50).But the Background Job is still "ACTIVE".Tried killing the Job in SM37--->Cancel Active Job or Delete the Job) but ,when tried to "Cancel" the Job,we get a message : The job is NOT ACTIVE !!!. Then when tried to "DELETE" the job ,we get a message " Job is still ACTIVE"......!!!!
----->Since there is no Work Process in SM50,what is the alternative solution to Kill this Job..........???
(In BW ,there is no Update of data records,with the monitor showing
Answere :
Go to SM37 >> select the job >> Click on the JOB tab in the top >> Click on Check status............
Then it status will show cancel...........
Actually sometimes it happens job gets cancelled but staus shows active....then we need to do this..........actually job is already cancelled......
Labels
- BW Architecture (1)
- BW Reporting (3)
- Data Loading issues (7)
- Datawarehousing (9)
- Extraction (3)
- General Maintainence (5)
- HANA (1)
Blog Archive
-
▼
2008
(21)
-
▼
September
(17)
- Difference between LIS and LO Extraction
- What will happend if a request in Green is deleted?
- When is reconstruction allowed? Questions
- Handling Amount Values with currencies in BW
- PSA reverse posting
- Unable to Cancel Job in SM37 (R3)
- Attribute delta loading "duplicate record found"
- How to supress messages generated by BW Queries
- Dimension Size Vs Fact Size
- BW Main tables
- Production Support Issues in BW
- Selective Deletion in Process Chain
- How to Debugg Update and transfer Rules
- BW tables
- How to define F4 Order Help for infoobject for rep...
- TCURF, TCURR and TCURX
- Error loading master data - Data record 1 ('AB03...
-
▼
September
(17)
19 Sept 2008
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment