Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Hi,
One of my QlikView dashbords does not load successfully.
Here's the error :
07/09/2016 16:56:25: 0444 SQL SELECT *
07/09/2016 16:56:25: 0445 FROM "QTP"
07/09/2016 16:56:30: Error: ErrorSource: OraOLEDB, ErrorMsg: ORA-04031: unable to allocate 3896 bytes of shared memory ("shared pool","SELECT *
07/09/2016 16:56:30: FROM "QTP"
07/09/2016 16:56:30: General Script Error
07/09/2016 16:56:30: Execution Failed
07/09/2016 16:56:30: Execution finished.
Could you kindly advise.
Wiem,
You need more shared memory than allocated.
This error is related to DB.
The Oracle documentation has these notes on the ORA-04031 error:
ORA-04031: unable to allocate nn bytes of shared memory
Cause: More shared memory is needed than was allocated in the shared pool.
Action: If the shared pool is out of memory, either use the dbms_shared_pool package to pin large packages, reduce your use of shared memory, or increase the amount of available shared memory by increasing the value of the INIT.ORA parameters "shared_pool_reserved_size" and "shared_pool_size". If the large pool is out of memory, increase the INIT.ORA parameter "large_pool_size".
The ORA-04031 error also happens when you are using automatic memory management (sga_max_size), and the memory specific is too small.
Wiem,
You need more shared memory than allocated.
This error is related to DB.
The Oracle documentation has these notes on the ORA-04031 error:
ORA-04031: unable to allocate nn bytes of shared memory
Cause: More shared memory is needed than was allocated in the shared pool.
Action: If the shared pool is out of memory, either use the dbms_shared_pool package to pin large packages, reduce your use of shared memory, or increase the amount of available shared memory by increasing the value of the INIT.ORA parameters "shared_pool_reserved_size" and "shared_pool_size". If the large pool is out of memory, increase the INIT.ORA parameter "large_pool_size".
The ORA-04031 error also happens when you are using automatic memory management (sga_max_size), and the memory specific is too small.
Thanks Pradeep. You are right. The Database administrators of my company fixed that.