Avatar for Username

Przeszukaj pomoc

Unikaj oszustw związanych z pomocą.Nigdy nie będziemy prosić Cię o dzwonienie na numer telefonu, wysyłanie SMS-ów ani o udostępnianie danych osobowych. Zgłoś podejrzaną aktywność, korzystając z opcji „Zgłoś nadużycie”.

Więcej informacji

Wątek został zarchiwizowany. Jeśli potrzebujesz pomocy, zadaj nowe pytanie.

Is there a limit to the amount of data contained within a single tab in ESR 52.9?

BrianKing
BrianKing
more options

When we run a concurrent report export from Oracle R12, we've seen that in our larger exports we are unable to save the data from the browser. Typically, we can "save page" to a text document, and all the data is visible. When the exports are large, the save page option results in an "authentication failure" response from the server.

When using InternetExplorer we do not see this issue, and we only see this issue in Firefox when the export data size is large (> 64 MB).

When we run a concurrent report export from Oracle R12, we've seen that in our larger exports we are unable to save the data from the browser. Typically, we can "save page" to a text document, and all the data is visible. When the exports are large, the save page option results in an "authentication failure" response from the server. When using InternetExplorer we do not see this issue, and we only see this issue in Firefox when the export data size is large (> 64 MB).

Wszystkie odpowiedzi (1)

jscher2000 - Support Volunteer
jscher2000 - Support Volunteer
  • Top 25 Contributor
more options

64MB of text displayed in a single tab? Who designed this reporting?!

Based on the error, it sounds as though Firefox is re-requesting the page from the server. I think that may be common for "Save Page As" and it certainly would be slow even if it worked. What if you switch Firefox to working offline (File menu) and then try to save again. Can Firefox save what it has cached?

I notice you are running 32-bit Firefox on 64-bit Windows. Not sure if that is a factor, or should I say, I don't know whether using 64-bit Firefox would avoid the issue.

Also, Firefox 52 is no longer supported. Have you tried a current version?