permanent increasing of Temporary Used Area

[hubert_heitzer]

Hello,

since yesterday somthing is increasing the temp. used area of our MaxDB (Release: 7.7.07.028) from 1.000 KB to 382.287.256 KB up to now.

Are there ways to to find the origin (e.g. programm, user etc.)

Thanks,

Hubert

[hubert_heitzer · Accepted solution]

The problem occured with a select like this:

SELECT adrnp tel_number tel_extens fax_number fax_extens smtp_addr
   INTO TABLE lt_asppa
   FROM vbpa
   LEFT JOIN adr2
          ON adr2~client     = vbpa~mandt
         AND adr2~persnumber = vbpa~adrnp
   LEFT JOIN adr3
          ON adr3~client     = vbpa~mandt
         AND adr3~persnumber = vbpa~adrnp
   LEFT JOIN adr6
          ON adr6~client     = vbpa~mandt
         AND adr6~persnumber = vbpa~adrnp
  WHERE mandt = '100'
     AND vbeln = '0021001214'.

If vbpa-adrnp of record vbpa-vbeln = '0021001214' is initial, then the join conditions adr2~persnumber = vbpa~adrnp, adr3~persnumber = vbpa~adrnp and adr6~persnumber = vbpa~adrnp are ignored and the select will be done on a join-table with size

1* count(adr2) * count(adr3) * count(adr6).

Creating this join-table filled the temp. used area of our MaxDB.

[former_member229109]

Hello Hubert,

please create the SAP message to BC-DB-LCA or BC-DB-LVC if you could not find the reason of the perm data size increasing reson.

-> Check if users created/coped new planing versions.

-> Check if you have superflous liveCache data left from aborted liveCache appl. transactions.

-> //om17 inconsistensies check.

   Do you have the liveCache objects existed only in liveCache?

- Please start/keep the DB analyzer running.

-> Further need to login and check what kind data you have in liveCache.

Regards, NK