on 12-08-2010 6:51 AM
Hi Sap Gurus,
BZ Y Unexpected return value 1 when calling up DbSlR
BY J Function ROLLBACK on connection R/3 failed
R3 9 Error in DB rollback/SyFlush, return code 016384
BY 4 Database error 0 at UPD access to table TST01
BY 0 >
F6 H Database error: TemSe->XRTAB(3)->1 for table TST01 key
Q0 2 Stop Workp. 14, PID 4186340
Q0 1 Start Workp. 14, 16 times since system startup. PID 9 646770
F6 F TemSe object JOBLGX22303300X49850 was closed remotely
F6 V Invalid address (NULL) was transferred
EC F Failed to create the log for job No joblog, 4C412205C6C80300E1008
R4 7 Delete session 001 after error 023
Q0 I Operating system call getaddrinfo failed (error no. 0 )
Q0 I Operating system call getaddrinfo failed (error no. 0 )
BZ Y Unexpected return value 1 when calling up DbSlR
BY J Function ROLLBACK on connection R/3 failed
R3 9 Error in DB rollback/SyFlush, return code 016384
BY 4 Database error 0 at UPD access to table TST01
BY 0 >
F6 H Database error: TemSe->XRTAB(3)->1 for table TST01 key
Any idea to avoid the system log entries.
Regards
Munish Jindal
Even though is an old question but I recently ran in the same problem and followed all the recommendations in the post. That did help in making TemSe consistent but I kept hitting the error. Watching the process I realize that process was dying after using almost 4GB share memory. I increased the em/address_space_MB to 20 GB which resolved the problem. In our case we don't have any heap memory configured. It seems that sometime SAP is not able to create a shortdump for memory and SM21 error is misleading in those case. FYI I did configure heap too to see if I get page_alloc shortdump but that didn't happen.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Munish,
For TemSe error first point of resolution will be at T - Code : SP12. In there select,
TemSe Data Storage --> Consistency Check. This will run for a while depending on the number of recored within the TSTO1 table. Once the execution is completed delete all the records displayed in red.
Apart from above step, you can use T - Code: SPAD. In there, you will find two tabs
a) Devices/servers
b) Admin.
within admin tab select "Delete Old Spool Request". You will see a popup. In there you can select "Request already printed" check box and Minimum Age in day <> depends on your requirement. I sugest for 7 days and execute. This also takes certain amount of time to get executed.
In the same T - Code: SPAD, Select Administration --> Check Consistency
Make sure Spool re-organizing job is scheduled that will be executed daily at night to clear spool requrest that are older than 10 days in age.
I guess this helps to some extent.
Regards,
Nani Chowdary
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Please check this note: Note 48400 - Reorganization of TemSe and Spool
Kind regards,
Mark
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
95 | |
11 | |
10 | |
9 | |
9 | |
7 | |
6 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.