cancel
Showing results for 
Search instead for 
Did you mean: 

Tunknown... what is it?

ganimede_dignan
Contributor
0 Kudos

Hi,

after migration to ASE we can see sometimes, in SM66 or SM50, a case where table name is "Tunknown"... is it OK?

Thank you.

Accepted Solutions (1)

Accepted Solutions (1)

crisnormand
Active Participant
0 Kudos

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

ganimede_dignan
Contributor
0 Kudos

Hi,

mhmm... and if I've already applied last lib_dbls patch? I've donwloaded in the past: lib_dbsl_520-10011372.sar

I see that, as example, I can see Tunknown during index creation.

Thank you.

Johan_sapbasis
Active Contributor
0 Kudos

HI Ganimede,

Hopefully this note sets your mind at ease.

1524630 - SM50/SM66: Tunknown

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

Answers (1)

Answers (1)

Johan_sapbasis
Active Contributor
0 Kudos

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