Qlik Community

QlikView Connectors

Announcements
QlikView Fans! We’d love to hear from you.
Share your QlikView feedback with the product team… Click here to participate in our 5-minute survey.
Rules, plus terms and conditions, can be found here.
daniel_f
Contributor

SAP BW problem when extract

hi all,

I'm trying to extract data from bex. report (SAP-BW) end after the connection and read the data i get this error and finally don't get any data:

ErrorKey: TSV_TNEW_PAGE_ALLOC_FAILED, ErrorMessage: No more storage space available for extending an internal table

is someone know about this problem? is it provide from Qlikview or BW or SAP?

my connector is OLAP connector 5.8 SR2

my QlikView Version:11.20.12235.0 (build 14)

it's urgently

thanks in advance,

Daniel

1 Solution

Accepted Solutions
daniel_f
Contributor

Re: SAP BW problem when extract

For those how may experience this problem in the future, what was the solution:

to increase the volume of memory for data in reports in the SAP-BW definitions

(we had 2 GB and was raised to 3 GB)

it solve the problem

thanks & good luck

Daniel

5 Replies
Not applicable

Re: SAP BW problem when extract

This is an error from SAP related to the internal tables used and have to be checked at SAP side. Ask SAP System Admin to check for any dumps to get details.

daniel_f
Contributor

Re: SAP BW problem when extract

Thanks Daniel for your reply,

are you familiar with these kind of problems on SAP? it's the source of the problem in SAP or SAP-BW?

i'm interesting to update our SAP basis expert with most of relevant knowledge that i can get.

thanks again

Not applicable

Re: SAP BW problem when extract

The Source is SAP,just ask your SAP basis expert to check for dumps at the time you connected. In the dumps from SAP you get several more information and they will knew what to do.

daniel_f
Contributor

Re: SAP BW problem when extract

Thanks again Daniel

i'll do your recommendation

daniel_f
Contributor

Re: SAP BW problem when extract

For those how may experience this problem in the future, what was the solution:

to increase the volume of memory for data in reports in the SAP-BW definitions

(we had 2 GB and was raised to 3 GB)

it solve the problem

thanks & good luck

Daniel

Community Browser