Using Reorganize Objects with LONG Columns

When the Reorganize Objects script generation completes, an impact report appears with information about the reorganization. If any tables included in the reorganization have columns of data type LONG, the following warning message appears in the report:

"Reorganization includes a table with a LONG column. To support reorganization of tables with LONG columns that are greater than 32Kbytes, the external procedure MGMT$REORG_MOVELONGCOMMAND must be configured properly. It has been determined this external procedure is not currently configured as expected."

If this message appears, examine the data in the LONG columns. If the data is less than 32K bytes, you can ignore this message. The reorganization job can be scheduled and submitted to the EM Jobs system for execution. If the data is greater than 32K bytes, use the following procedure to configure the database for external procedure connections.

Configuring the Database for External Procedure Connections

  1. Exit the Reorganize Objects wizard.

  2. Shut down the database and the listener.

  3. Edit $ORACLE_HOME/network/admin/tnsnames.ora and add the following entry:

    Graphic Quote

  4. Save the changes to tnsnames.ora and exit the editor.

  5. Edit $ORACLE_HOME/network/admin/listener.ora and make changes as indicated in the sub-steps below. An entry in this file appears similar to the following example:

    Graphic Quote

    1. Add a new Address List parameter to this entry as shown in the following example:

      Graphic Quote

    2. Add a second entry to the file as shown in the following example:
    3. Graphic Quote

    4. Add a new SID DESC parameter to the entry above as shown in the following example:

      Graphic Quote

  6. Save the changes to listener.ora and exit the editor.

  7. Ensure that $ORACLE_HOME/lib/libnmuc.so exists in your database installation.

  8. Start the Reorganize Objects wizard. The warning message shown at the beginning of this help topic should now not appear in the impact report.

  9. Restart the listener and the database.

  10. Schedule and submit the reorganization job. The following message will appear in the reorganization job output log:

    "Copy with PLSQL block failed due to size of long. Using Mgmt$Reorg_MoveLongCommand to perform the reorganization."

Despite this response, any tables with LONG columns will be reorganized successfully.

Related Topics

Enterprise Manager Information Roadmap