Query Runtime Statistics - Delta Load Errors

[Former Member]

Good Morning,

We recently upgraded our BI system to 7.0. One of the consultants who was here activated some standard business content, as the title of my subject shows, Query Runtime Statistics. The Infocube that is being loaded in the process chain he activated is: 0TCT_C01. This load utilizes 4 individual delta loads, coming from Datasources: 0TCT_DSA1, 0TCT_DSO1, 0TCT_DSO2, and 0TCT_DSO3.

The problem we're having is that at least 2 of these frequently fail ( 0TCT_DSO2 and 0TCT_DSO3 ).

The failure messages we get is that some of the data coming in for object 0TCTSTATOBJ (Query Runtime Object) is always bad. Some example values of the data that it is trying to load include:

FILTER(1)

TABELLE(1)

GENERISCHER NAVIGATIONSBLOCK(1

I'm not seeing anything in particular that would indicate these as being invalid values. The ()'s I wouldn't think would be causing it, given that those are in our system as acceptable characters (checked RSKC to verify) and there's nothing else that looks out of place (aside from the values coming in as German). Has anyone else come across an error like this for this particular statistics load? Manually changing these erroneous in the PSA is not an option given the frequency of the failures.

Any help would be greatly appreciated. If I need to clarify or relay any additional information, please let me know as well. Thanks

[Former Member · Accepted solution]

Hi Craig,

Sometimes it so happens that a value does not show any invalid chars in the monitor, but when you check the data in the PSA, you can see the invalid chars if any...

Please check the PSA data...double click on a record and see the value...check if you can see any of the special chars...

Please also note that a space in the beginning the data is converted to '#'. This could also cause an error..in this case you can just add '#' to RSKC...

Do let me know if you need any further info...

Sita.

[Former Member · Accepted solution]

Sita,

I greatly appreciate your response. However, I probably should have provided some additional technical information regarding the issue.

The values I posted actually are from the PSA. These values that are given are telling the person what Java object the report being used, has had an issue (may not just be reporting issues, but general statistics for the use of these java objects, not sure yet).

I am aware that when BI gets an invalid character, it replaces it (in the display screen) with a #. Unfortunately, we do have # in our permitted characters and the reason why that doesn't work to qualify what was entered is because while it shows up in your display screen as a #, in the background it still sees it as the invalid char. Subsequently, you won't always be able to see what that invalid char is. We've encountered this many times over the years with our Sales Orders when a Rep (or someone within the company) enters invalid characters (typically they do a copy and paste from Excel using a different Font, or are using arabic or other foreign characters).

Given that the values we're recieving are in German, my only conclusion is that the words themselves contain german characters often used in certain letters. For example, the letter U can sometimes have what they call an umlout (spelling may be off on that). An umlout almost looks like a quotation mark that is placed directly above the letter itself. Another common letter in German is the ß symbol.

We may be able to bypass our problem by entering in these german characters, but I guess I was looking for more than just a "hack" solution and was curious if anyone else out there has had a similar issue on their system and if they were able to come up with a solution other than trying to guess and add in "special characters" that are not normally used in the english language.

Again, my appologies for not being more descriptive and thank you again for replying.

[Former Member · Accepted solution]

Hi

The best solution would be to write a global routine or transfer routine in the general tab of the info object level to allow the special characters or remove the special routine. Maintianing the special characters in the Tcode RSKC is not advisable as it is the global definition for the entire system.

Hope it helps

Regards

Sadeesh

[Former Member · Accepted solution]

Hi,

OSS note Note 1244190 - Char 0TCTBWOBJCT contains invalid characters (BRAIN 60) seems to fix the issue.

Thanks,

Renee

Edited by: refehri on Apr 24, 2009 1:58 PM

[Former Member · Accepted solution]

Thank you refehri,

That definately solved the problem. I was looking for a solution like this, rather than a custom work-around to bypass the errors.

As such, I've given you full points.

[Former Member]

This message was moderated.