ORA-故障处理例.docVIP

ORA-30009 故障处理一例 背景：??? 刚才一网友问到ORA-30009的错误，数据库版本为，操作系统版本为Redhat 4；随即我考虑了到了硬件和buffer的限制这一块，对其做了验证，详细如下: 错误信息：SQL CREATE TABLE t AS SELECT rownum AS n, lpad(*,1000,*) AS pad FROM dual CONNECT BY level = 100000;CREATE TABLE t AS SELECT rownum AS n, lpad(*,1000,*) AS pad FROM dual CONNECT BY level = 100000???????????????????????????????????????????????????????????????????? *ERROR at line 1:ORA-30009: Not enough memory for CONNECT BY operation 处理步骤： 查看限制，结论是没有问题。[oracle@yangbo bdump]$ ulimit -acore file size????????? (blocks, -c) 0data seg size?????????? (kbytes, -d) unlimitedfile size?????????????? (blocks, -f) unlimitedpending signals???????????????? (-i) 1024max locked memory?????? (kbytes, -l) 32max memory size???????? (kbytes, -m) unlimitedopen files????????????????????? (-n) 1024pipe size??????????? (512 bytes, -p) 8POSIX message queues???? (bytes, -q) 819200stack size????????????? (kbytes, -s) 10240cpu time?????????????? (seconds, -t) unlimitedmax user processes????????????? (-u) 8192virtual memory????????? (kbytes, -v) unlimitedfile locks????????????????????? (-x) unlimited ? 查看数据库的buffer为自动设置，问题也不大。SQL show parameter buffer NAME???????????????????????????????? TYPE??????? VALUE buffer_pool_keep???????????????????? stringbuffer_pool_recycle????????????????? stringdb_block_buffers???????????????????? integer???? 0log_buffer?????????????????????????? integer???? 2875392use_indirect_data_buffers??????????? boolean???? FALSE ? 同时查看了下sga的配置，通过经验来看，发现好像小了。 19:46:31 SQL show parameter sga NAME???????????????????????????????? TYPE??????? VALUE lock_sga???????????????????????????? boolean???? FALSEpre_page_sga???????????????????????? boolean???? FALSEsga_max_size???????????????????????? big integer 312Msga_target?????????????????????????? big integer 312M 分析： ??? 通过如上的情况分析得出，他将要插入的数据是在100000行，但是他的sga配置只有312M，主机内存只有512M，数据库是跑在虚拟机上的，并且之前已经将该100000行数据的表进行了一次插入操作，并且没有提交在进行第二次插入的时候报ORA-30009这个错误，由此可判断是由于SGA太小导致。 处理过程： 1、添加内存到1G2、扩大SGAS