cancel
Showing results for 
Search instead for 
Did you mean: 

RSA1 transaction is running long

Former Member
0 Kudos

Hi All,

The RSA1 transaction in a BW system is running very long time and not getting executed; also it is not throwing any error.

When Checked in ST02; I found the following values with many Red 'Swaps'; In Table definition, Field definition, Program, CUA, etc

Can anyone please help me, how to find the root cause of this issue?

I understand this is a basis issue; but atleast finding the root cause and updating them is better.

Buffer

HitRatio %

Alloc. KB

Freesp. KB

% Free Sp.

Dir. Size

FreeDirEnt

% Free Dir

Swaps

DB Accs

-


Nametab (NTAB)

0

Table definition

99.27

6,799

20,000

15,005

262,028

Field definition

99.83

31,563

277

0.92

20,000

5,637

28.19

11,899

36,230

Short NTAB

99.92

3,625

2,404

80.13

5,000

2,685

53.70

0

2,375

Initial records

76.96

6,625

4,569

76.15

5,000

545

10.90

10,388

17,183

0

program

99.15

800,000

2,131

0.29

200,000

172,732

86.37

15,469

143,040

CUA

99.79

3,000

455

18.51

1,500

1,391

92.73

46,960

2,129

Screen

99.87

4,297

723

17.66

2,000

1,738

86.90

8

2,338

Calendar

100.00

488

294

61.51

200

44

22.00

0

156

OTR

4,096

3,373

99.94

2,000

1,993

99.65

0

0

Tables

0

Generic Key

97.62

29,297

1,353

4.88

5,000

664

13.28

5,381

9,162,185

Single record

84.13

10,000

1,334

13.59

500

360

72.00

117

3,310,527

0

Export/import

78.98

4,096

581

17.21

2,000

362

18.10

108,659

Exp./ Imp. SHM

71.99

4,096

2,077

61.54

2,000

1,957

97.85

0

-


-


SAP Memory

Curr.Use %

CurUse[KB]

MaxUse[KB]

In Mem[KB]

OnDisk[KB]

SAPCurCach

HitRatio %

-


Roll area

2.30

6,030

14,128

131,072

131,072

IDs

94.92

Page area

31.53

82,641

91,944

65,536

196,608

Statement

95.00

Extended memory

4.52

757,760

3,047,424

16,777,216

0

0.00

Heap memory

0

928,929

0

0

0.00

-


Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Check with Basis team.

Also check jobs running in sm50, sm37. may be some locks got created check in sm12.

Also if you know when problem is started, just check logs in system if someone has played in the system. This you can do by right click on any provider and in additional functions > Display Logs. Remove all selections and see if any specific error is coming in system and from which activity.

Provide some more details so that we can help you.

Answers (4)

Answers (4)

Former Member
0 Kudos

The issue existed with the Long running data loads in the system.

The jobs started 2 days back and was on hold, due to which the RSA1 transaction was not accessbile.

Once killing those jobs manually, the transaction ran fine.

Former Member
0 Kudos

Hi,

If you fill any of answers here helped you, please reward points to them.

former_member210615
Contributor
0 Kudos

hi,

you can ask your BASIS team to increase DIA jobs on the server, as rest of parameters looks fine to me.

when a Tcode is run a DIA processor job is created and if there are no processes available then it takes long time to execute.

so by Increase the DIA processes in server and the t-code will run fine i guess.

hope it helps

regards,

laksh

Former Member
0 Kudos

Hi,

You can ask your basis team to check Table Space in tcode DB02OLD/DB02.

If any process is running long then ask the basis team to cancel that in tcode : SM66/SM50

Br

Alok

KamalMehta
Advisor
Advisor
0 Kudos

Hi ,

Please check the tcode SM37 and check all the active jobs in the system .Check the job logs .

Go to SM50 and from there check the jobs in all the application servers and check whether there is any job in sleep mode .

If yes then kill the job immediatly .

also check SM12 entries and refesh it regularly to see if the entries are increasing regularly .

Check and updated accoordingly later .

Regards

Kamal