VBO-5530 User cannot be dropped
Piter Ustinov
------------------------------
Connected to Oracle9i Enterprise Edition Release 9.2.0.7.0
Connected as SYS
SQL>
DROP USER t2 CASCADE
ORA-01001: invalid cursor
ORA-00600: internal error code, arguments: [qmxiUnpPacked2], [121], [], [],
[], [], [], []
------------------------------
google вообще странные вещи пишет, типа саппорт тоже ничем помочь не может.
Может кто сталкивался, и знает волшебное слово?
Oleg Dvornikov
PU> From: "Piter Ustinov" <wo...@vazs.tlt.ru>
PU> Вот такая ситуация.
PU> ------------------------------
PU> Connected to Oracle9i Enterprise Edition Release 9.2.0.7.0
PU> Connected as SYS
SQL>>
PU> DROP USER t2 CASCADE
PU> ORA-01001: invalid cursor
PU> ORA-00600: internal error code, arguments: [qmxiUnpPacked2], [121], [],
PU> [], [], [], [], []
PU> ------------------------------
PU> google вообще странные вещи пишет, типа саппорт тоже ничем помочь не
PU> может.
PU> Может кто сталкивался, и знает волшебное слово?
Hе сталкивался, но на Металинке есть поиск по второму аргументу ORA-600, не
всегда находит, но в этот раз нашло:
Subject: ORA-600 [qmxiUnpPacked2]
Doc ID: Note:222876.1 Type: REFERENCE
Last Revision Date: 03-DEC-2005 Status: PUBLISHED
Note: For additional ORA-600 related information please read Note 146580.1
PURPOSE:
This article discusses the internal error "ORA-600 [qmxiUnpPacked2]", what
it means and possible actions. The information here is only applicable
to the versions listed and is provided only for guidance.
ERROR:
ORA-600 [qmxiUnpPacked2] [a]
VERSIONS:
versions 9.2 to 10.1
DESCRIPTION:
When unpickling an XOB or an array of XOBs an unexpected datatype was
found.
Generally due to XMLType data that has not been successfully upgraded from
a previous version.
ARGUMENTS:
Arg [a] Type of XOB
FUNCTIONALITY:
Qernel xMl support Xob to/from Image
IMPACT:
PROCESS FAILURE
NON CORRUPTIVE - No underlying data corruption.
SUGGESTIONS:
Please review the following article on Metalink :
Note 235423.1 How to resolve ORA-600 [qmxiUnpPacked2] during upgrade
If you still encounter the error having tried the suggestions in the
above article, or the article isn't applicible to your environment then
ensure that the upgrade to current version was completed succesfully
without error.
This error can occur if a patch has been applied and catpatch
(or equivalent) has not been run to patch the database.
column comp_name format a35
select comp_name, status, substr(version,1,10) as version
from dba_registry;
If the Known Issues section below does not help in terms of identifying
a solution, please submit the trace files and alert.log to Oracle
Support Services for further analysis.
Hу, и Note 235423.1:
Subject: How to resolve ORA-600 [qmxiUnpPacked2] during upgrade
Doc ID: Note:235423.1 Type: HOWTO
Last Revision Date: 05-FEB-2007 Status: PUBLISHED
Checked for relevance on 05-Feb-2007
The information in this article applies to:
Oracle 9.2.0.2
Multiple Platforms, 64-bit
Symptom(s)
~~~~~~~~~~
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 150Mb the 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 <XDB_PASSWD> <TABLESPACE> <TEMP_TABLESPACE>
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.
Piter Ustinov
You wrote to Piter Ustinov on Mon, 26 Mar 2007 07:42:30 +0400:
OD> Hе сталкивался, но на Металинке есть поиск по второму аргументу ORA-600,
OD> не всегда находит, но в этот раз нашло:
OD> Subject: ORA-600 [qmxiUnpPacked2]
OD> Doc ID: Note:222876.1 Type: REFERENCE
OD> Last Revision Date: 03-DEC-2005 Status: PUBLISHED
Да, вроде оно. Будем пробовать. Спасибо.