遭遇600-[qmxiUnpPacked2]

最新推荐文章于 2024-10-02 00:27:17 发布

clbvxg9858

最新推荐文章于 2024-10-02 00:27:17 发布

阅读量107

点赞数

文章标签：数据库

今天在删除一用户时系统报600错误:

ORA-00600: internal error code, arguments: [qmxiUnpPacked2], [121], [], [], [], [], [], []

打开trc文件一片茫然,经过查找得到关于此错误的一些信息:

ORA-600 [qmxiUnpPacked2] []
Cause ~~~~~ If the error is seen after applying 9.2.0.2 on a 9.2.0.1
database or if using DBCA in 9.2.0.2 to create a new database
(which is using the 9.2.0.1 seed database) then it is very likely that either
shared_pool_size or java_pool_size was too small when catpatch.sql was executed.
Error is generally seen as ORA-600: internal error code, arguments: [qmxiUnpPacked2], [121]
There are 3 options to proceed from here:-
Fix ~~~~
Option 1 ======== If your shared_pool_size and java_pool_size are less than 150Mbthe do the following :-
1/ Set your shared_pool_size and java_pool_size to 150Mb each.
In some case you may need to use larger pool sizes.
2/ Get the xdbpatch.sql script from [NOTE:237305.1]
3/ Copy xdbpatch.sql to $ORACLE_HOME/rdbms/admin/xdbpatch.sql having taken a backup of the original file first
4/ Restart the instance with: startup migrate;
5/ spool catpatch @?/rdbms/admin/catpatch.sql
Option 2 ======== If you already have shared_pool_size and java_pool_size set at greater than 150Mb
then the problem may be caused by the shared memory allocated during
the JVM upgrade is not released properly. In which case do the following :-
1/ Set your shared_pool_size and java_pool_size to 150Mb each. In some case
you may need to use larger pool sizes.
2/ Get the xdbpatch.sql script from [NOTE:237305.1]
3/ Edit the xdbpatch.sql script and add the following as the first line in the script:- alter system flush shared_pool;
3/ Copy xdbpatch.sql to $ORACLE_HOME/rdbms/admin/xdbpatch.sql having taken a backup of the original file first
3/ Restart the instance with: startup migrate;
4/ spool catpatch @?/rdbms/admin/catpatch.sql
Option 3 ======== If XDB is NOT in use and there are NO registered XML Schemas an alternative is to drop, and maybe re-install XDB :-
1/ To drop the XDB subsystem connect as sys and run @?/rdbms/admin/catnoqm.sql
2/ You can then run catpatch.sql to perform the upgrade startup migrate; @?/rdbms/admin/catpatch.sql
3/ Once complete you may chose to re-install the XDB subsystem, if so connect as sys and run catqm.sql @?/rdbms/admin/catqm.sql
If the error is seen during normal database operation, ensure that upgrade
to current version was completed succesfully without error. Once this is
confirmed attempt to reproduce the error, if successful forward ALERT.LOG,
trace files and full error stack to Oracle Support Services for further analysis.