针对你提出的“not enough shared pool memory, should be at least 531837747 bytes”这一错误信息,我将从几个方面进行详细解答: 1. 确认错误信息的来源和上下文 这个错误信息通常出现在使用Oracle数据库时,特别是当数据库实例尝试加载大量的PL/SQL代码、包、存储过程、函数等对象到共享池(Shared Pool)中时。共享...
SQL>startup pfile='/home/oracle/initgabsjsb.ora'; ORA-00371:notenough shared pool memory 几经折腾发现是参数文件中缺少processes这个参数而导致,如果没有设置process,process的默认值可能根据cpu的数量来估算,会是一个很高的值,进一步造成oracle认为需要很多shared pool。因此启动时候报错如果小于2G shared pool,...
9 ORA-00371: not enough shared pool memory, should be atleast 750203385 bytes 参数文件内容 pfile.ora 解决方法 按照提示将sharepool size设置为要求的大小 pfile.ora SHARED_POOL_SIZE=750203385 原因分析 这是oracle没有公布的一个bug Bug 13606499 - PHSB: DEFAULT MEMORY PARAMETER(INIT.ORA) IS NOT BIG...
8 9 ORA-00371: not enough shared pool memory, should be atleast 750203385 bytes 1. 2. 3. 4. 5. 6. 7. 8. 9. 参数文件内容 pfile.ora 解决方法 按照提示将sharepool size设置为要求的大小 pfile.ora SHARED_POOL_SIZE=750203385 原因分析 这是oracle没有公布的一个bug Bug 13606499 - PHSB: DE...
1. Instance startup with default shared_pool_size fails with below error SQL> startup nomount pfile=/tmp/inittest.ora ORA-00371: not enough shared pool memory, should be atleast 'XXXXXX' bytes 2. The parameter file inittest.ora contains only DB_NAME parameter or no SHARED_POOL_SIZE para...
启动数据库出现ORA-00371: not enough shared pool memory, should be atleast 218227097 bytes。。 解决过程 //先从pfile启动 SQL> startup nomount pfile='/ora/oracle/admin/sm/pfile/init.ora.632008194025'; ORACLE instance started. Total System Global Area 1308622848 bytes ...
ORA-00371: Not Enough Shared Pool Memory signaled on Startup Database will not start even after restore. The Server has plenty of memory. A corruption occurred previously. Changes Restore was performed or other activity related to possible corruption. Cause Sign In To view full details, sign ...
ORA-00371: not enough shared pool memory, should be atleast 218227097 bytes 然后报错,显示pool size过小 只能重新加载 (2) 解决过程 最麻烦的就是不能startup nomount,只能利用比较旧的pfile进行启动. SQL> startup nomount pfile= startup nomount pfile='E:/oracle/product/10.1.0/admin/orcl/pfile/init...
错误检查 0x136:VHD_BOOT_HOST_VOLUME_NOT_ENOUGH_SPACE 错误检查 0x137:WIN32K_HANDLE_MANAGER 错误检查 0x138:GPIO_CONTROLLER_DRIVER_ERROR 错误检查 0x139:KERNEL_SECURITY_CHECK_FAILURE 错误检查 0x13A:KERNEL_MODE_HEAP_CORRUPTION 错误检查 0x13B:PASSIVE_INTERRUPT_ERROR ...
drivers using improper addresses. If kernel debugger is available get stack backtrace. Arguments: Arg1: fffff808add27150, memory referenced Arg2: 0000000000000002, IRQL Arg3: 0000000000000000, value 0 = read operation, 1 = write operation Arg4: fffff808adc386a6, address which referenc...