HOME   ·Î±×ÀΠ  ȸ¿ø°¡ÀÔ
    
ȸ¿ø°¡ÀÔ
ºñ¹Ð¹øÈ£ ã±â ÀÚµ¿·Î±ä
ÀÌÀü°Ô½ÃÆÇ
   free_board
   °Ç°­°Ô½ÃÆÇ
   ¿À¶óŬDB
   Linux
   HTML/javascript
   Áú¹®°ú ´ä
È£¼­±â
   À̹ÌÁö°Ô½ÃÆÇ  
   °Ç°­°Ô½ÃÆÇ  
   À½¾ÇÀÚ·á  
   ¼ºÁØÀÌ °Ô½ÃÆÇ  
[ÀϹÝ] XDB »èÁ¦ÈÄ ´Ù½Ã ¼³Ä¡Çϱâ
  È£¼® ´Ô²²¼­ ¾´ ±ÛÀÔ´Ï´Ù - 211.¢½.74.31 ÀÐÀ½:5322  
Á¦¸ñ:  How to Deinstall and Reinstall XML Database (XDB)
  ¹®¼­ ID:  °øÁö:243554.1 À¯Çü:  BULLETIN
  ¸¶Áö¸· °»½Å ³¯Â¥:  20-APR-2006 »óÅÂ:  PUBLISHED


PURPOSE
-------

This article provides the steps to manually deinstall and install the XML
Database feature into a database. 

SCOPE & APPLICATION
-------------------

This article is for DBA's that need to remove, install and/or reinstall the XDB
schema into an existing Oracle database. 

NOTE:  If the XML DB features are currently being utilized, and you have experienced a
corrupted XML DB repository or installation, it may be more efficient to perform point
in time recovery to a point prior to the problem.
      
How to Deinstall and Reinstall XML Database (XDB)
-------------------------------------------------

XDB SCHEMA REMOVAL STEPS
*************************

WARNING: The steps to remove the XML Database feature (XDB schema) will completely
remove the XDB repository including any user defined information contained
within it. 
Therefore, if there are any registered schemas or XML Database items created, you will be
required to recreate all of your user defined structures, data and re-register
all schemas previously registered.

1.  Shutdown and restart the database.

2.  Connect as sysdba and run the catnoqm.sql script.  Maintain a spool of the script running:

    UNIX: $ORACLE_HOME/rdbms/admin subdirectory
    WINDOWS: $ORACLE_HOME\rdbms\admin subdirectory

    For Example:

    SQL> set echo on
    SQL> spool xdb_removal.log
    SQL> @?/rdbms/admin/catnoqm.sql

3.  Modify the init.ora file or spfile to include the following minimums to prepare the DB for reinstalling the XDB schema:

    shared_pool_size =150 MB
    java_pool_size =150 MB

4.  Turn on AUTO EXTEND on the XDB tablespace.
    If you do not want to do this , make sure you target a tablespace with at least
       .100 MB of free space for non-UTF8 DB
       .150 MB of free space for an AL32UTF8 DB

5.   Shutdown the database immediate, and startup the database normal

     NOTE:  Failure to restart the database at this step can cause XDB catqm.sql
     installation to fail with an internal error similar to the following:
     ORA-7445 [qmr_hdl_copy()+48]


XDB SCHEMA INSTALL STEPS
*************************

1. Connect as sysdba and run the catqm.sql script.  Maintain a spool of the script running:

   UNIX: $ORACLE_HOME/rdbms/admin subdirectory
   WINDOWS: $ORACLE_HOME\rdbms\admin subdirectory

   The catqm.sql script requires the following parameters be passed to it when run: 
    A.  XDB user password
    B.  XDB user default tablespace
    C.  XDB user temporary tablespace
   Therefore the syntax to run catqm.sql will be: 
   SQL> catqm.sql A B C

   For Example:
   SQL> set echo on
   SQL> spool xdb_install.log
   SQL>@?/rdbms/admin/catqm.sql XDB XDB TEMP

2.  Reconnect to SYS again and run the following to load the XDB java library.

   SQL>  catxdbj.sql

   NOTE:  In order to load the XDB java libraries in catxdbj.sql, you must
   first have a valid Java Virtual Machine installation in the DB (JVM)
   and a valid XDK. 
   Also, make sure that the database is started with Oracle9i Release 2
   (9.2.0) compatibility or higher for database version 9.2,
   10.1.0.2 for 10g rel 2 , etc..


3.  If the following line is not already apart of the database system parameters (init.ora/spfile).
    ***** NOTE:
     PLEASE REPLACE <sid> ,instanceid1,2 etc with your actual values

    a. Non-RAC
          dispatchers="(PROTOCOL=TCP) (SERVICE=<sid>XDB)"
    b. RAC
          instanceid1.dispatchers="(PROTOCOL=TCP) (SERVICE=<instanceid1>XDB)"
          instanceid2.dispatchers="(PROTOCOL=TCP) (SERVICE=<instanceid2>XDB)"
          etc ...
    c.If you are not using the default Listener ensure you have set LOCAL_LISTENER in the (init.ora/spfile)
      as prescribed for RAC/NON-RAC instances or the end points will not register.
  

4. Check for any invalid XDB owned objects:

   SQL> select count(*) from dba_objects
        where owner='XDB' and status='INVALID';

        COUNT(*)
        ----------
         0
5.  Check DBA_REGISTRY for XDB status:
    SQL>  select comp_name, status, version from DBA_REGISTRY where comp_name='Oracle XML Database'
          The results should indicate the correct version and patch in a valid status.

6.  Restart database and listener to enable Oracle XML DB protocol access.

RELATED DOCUMENTS
-----------------

XML Database online Documentation


È£¼®
211.¢½.74.31
Á¦¸ñ:  PLS-201 and ORA-06512 at "XDB.DBMS_XDBUTIL_INT" while Exporting Database
  ¹®¼­ ID:  °øÁö:243133.1 À¯Çü:  PROBLEM
  ¸¶Áö¸· °»½Å ³¯Â¥:  07-JUL-2004 »óÅÂ:  PUBLISHED


Problem Description
-------------------
An export from an Oracle9i database fails with:

...
. exporting triggers
EXP-00056: ORACLE error 6550 encountered
ORA-06550: line 1, column 26:
PLS-00201: identifier 'XDB.DBMS_XDBUTIL_INT' must be declared
ORA-06550: line 1, column 14:
PL/SQL: Statement ignored
EXP-00056: ORACLE error 6550 encountered
ORA-06550: line 1, column 26:
PLS-00201: identifier 'XDB.DBMS_XDBUTIL_INT' must be declared
ORA-06550: line 1, column 14:
PL/SQL: Statement ignored
EXP-00000: Export terminated unsuccessfully


You have verified the following:

1. The package DBMS_XDBUTIL_INT object does not exist:

   SQL> SELECT status,object_id,object_type,SUBSTR(owner||'.'||object_name,
        1, 40) "OWNER.OBJECT" FROM dba_objects
        WHERE object_name = 'DBMS_XDBUTIL_INT';

   no rows selected

2. The error messages during export are identical as mentioned above.
   For the error ORA-1422 (exact fetch returns more than requested number
   of rows) in XDB.DBMS_XDBUTIL_INT (line 52), refer to:
   - Note 221178.1 "ORA-01422 ORA-06512: at "XDB.DBMS_XDBUTIL_INT" while
                      exporting full database"
   - Note 256548.1 "Export of Database with XDB Throws ORA-1422 Error"


Solution Description
--------------------
There are three possible solutions:

1. If you are *NOT* having any schema's in the database that use the
   XML functionality, remove the XDB schema and the XDB tablespace by
   following the steps in the article mentioned below.  The XDB schema
   and the XML functionality can be re-installed at a later time if
   actually needed.

   Note 243554.1 "How to Deinstall and Reinstall XML Database (XDB)"

   WARNING: DO NOT DE-INSTALL XDB IF THERE ARE REGISTERED SCHEMA'S OR
            IF XML DATABASE ITEMS HAVE BEEN CREATED !

2. If you are using the XML functionality, and you have recently applied
   a patch-set, check whether the data dictionary has been upgraded
   accordingly.

   SQL> SELECT SUBSTR(comp_id,1,15) comp_id, status, SUBSTR(version,1,10)
        version, SUBSTR(comp_name,1,30) comp_name
        FROM dba_registry ORDER BY 1;

   If the version of the components CATALOG, CATPROC, XDB (among others)
   is lower than the patch-set version that you have applied, re-run the
   script catpatch.sql after a startup migrate. See the readme file of
   the patch-set for all these mandatory post-installation instructions.

3. If you are using the XML functionality, and the data dictionary
   components have the correct version and are VALID or LOADED,
   then re-create the package XDB.DBMS_XDBUTIL_INT with (example with
   UNIX syntax):

   SQL> connect sys/<password> AS SYSDBA
   SQL> @?/rdbms/admin/prvtxdb.plb
   SQL> exit


Explanation
-----------
The PLS-201 indicates that the export utility is expecting to find the
packge DBMS_XDBUTIL_INT.  This package together with its package body
should exist in the XDB schema and should be valid.


.
06-06-27 08:54


¸ñ·Ï

ºÐ·ù ¼±ÅÃ
64 ÀÏ¹Ý [SQL] ¿À¶óŬ ¼ÓµµÀúÇÏ ¹®Á¦ ÃßÃâ È£¼® 07-02-02 5368
63 ÀÏ¹Ý ¿À¶óŬ ÃʱâÈ­ ÆÄÀÏÀ» º¯°æÇؼ­ ¿ÀÇÂÇϱâ È£¼® 07-01-31 3475
62 ÀÏ¹Ý [Æ©´×] ¿À¶óŬ Æ©´× °ü·Ã Æß È£¼® 07-01-30 6261
61 ÀÏ¹Ý Åäµå 7.4 ±ò±¸³ª¼­ ¿¡·¯ ³ª¸é regedit ·Î Å°°ªÀ» º¯°æÇØ¾ßµÊ toad È£¼® 07-01-19 3946
60 ÀÏ¹Ý Äõ¸®¹æ½ÄÀ» ÀÌ¿ëÇÑ export dump data ¹Þ±â exp È£¼® 06-12-19 4034
59 ÀÏ¹Ý Æ©´×½ÎÀÌÆ® È£¼® 06-12-10 3613
58 ÀÏ¹Ý [ORA-06508] ¿¡·¯Ã³¸® È£¼® 06-09-05 6267
57 ÀÏ¹Ý [sql] Å×ÀÌºí ½ºÆäÀ̽º Á¤º¸ È®ÀÎ , Áõ°¡À²µµ È®ÀΠȣ¼® 06-08-17 11506
56 ÀÏ¹Ý ¿À¶óŬ È°¿ë¸í·É [ÀÎÅÍ³Ý ÂüÁ¶ÀÚ·á ] È£¼® 06-08-06 4370
55 ÀÏ¹Ý ¿À¶óŬ Á¤¸®ÀÚ·á sql [ÀÎÅÍ³Ý ÂüÁ¶ÀÚ·á ] È£¼® 06-08-06 4393
54 Áú¹® Á¶¾ðÀ» ºÎŹµå¸³µð´Ï´Ù. ³ªÁß¿¬ 06-07-26 2858
  ÀÏ¹Ý    Á¶¾ðÀ» ºÎŹµå¸³µð´Ï´Ù. È£¼® 06-08-06 3118
53 ÀÏ¹Ý ¿À¶óŬ Æ÷·³ .com ½ÎÀÌÆ® È£¼® 06-07-08 3376
52 ÀÏ¹Ý ÀÓÀÇ°èÁ¤À¸·Î sqlplus ½ÇÇà½Ã ¿¡·¯ ORA-27121 & Permission denied ÀÏ°æ¿ì È£¼® 06-06-28 4803
ÀÏ¹Ý XDB »èÁ¦ÈÄ ´Ù½Ã ¼³Ä¡Çϱâ (1) È£¼® 06-06-27 5323
óÀ½ÀÌÀü  [1] [2] [3] [4] [5] 6 [7] [8] [9] [10]  ´ÙÀ½¸Ç³¡

 
Copyright © zenos.pe.kr. All rights reserved.