on 11-10-2015 5:15 PM
Hello,
As Nicolaas says, the Tunknown is harmless.
The 'Tunknown' object is just a replacement when the database interface (DBSL library) doesn't know the name of the object.
It could be a good idea to apply last patch of your DBSL.
Regards,
Cris
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
HI Ganimede,
Hopefully this note sets your mind at ease.
The note is addressed to mssql but it addresses SAP standard functionality, worst case scenario could be that your statistics on the query you identify in
SM50 might have too old statistics. If your statistics and performance tuning on said statement and index are fully addressed then there is nothing you can do about the tunknown.
Kind Regards,
Johan
Hi,
Unless it gives you an error in the sm21/st22 database sid log there is probably no reason to worry here.
SAPLSDB2 is the report that was running in your screenshot above why don't you look at the SQL statement cache to see what it was running perhaps i.e. tables in the query.
Johan
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
85 | |
23 | |
11 | |
9 | |
8 | |
5 | |
5 | |
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.