合 EXP-3 No Storage Definition Found For Segment (文档 ID 443453.1)

 

0    263    1

Tags：

👉 本文共约22152个字，系统预计阅读时间或需84分钟。

EXP-3 No Storage Definition Found For Segment (文档 ID 443453.1)


In this Document

Symptoms
Cause
Solution

APPLIES TO:

Oracle Database - Enterprise Edition - Version 10.2.0.2 and later
Information in this document applies to any platform.
Checked for relevance on 16-Dec-2014

SYMPTOMS

When attempting to perform an export, the following error occurs:

EXP-00003: no storage definition found for segment(76, 66347)

CAUSE

Problem caused by an index on the object being owned by a different user.

When trying to export an object, all associated objects are exported as well. If one of the indexes is owned by a user and the exporting user does not have permissions on that index object the export fails.

SOLUTION

Redefine the index to be owned by the correct schema owner.

Error During Schema Level Export - EXP-00003: no storage definition found for segment(0, 0) (文档 ID 1969081.1)

In this Document

Symptoms
Cause
Solution

APPLIES TO:

Oracle Database - Enterprise Edition - Version 11.2.0.4 and later
Information in this document applies to any platform.

SYMPTOMS

EXP utility is showing errors while exporting schemas

EXP-00003: no storage definition found for segment(0, 0)

CAUSE

The database is on a Linux server and the Oracle database version is 11.2.0.4.

The client software is being used on a Windows client where exp is being run from version 11.2.0.1.

SOLUTION

Match the client version of the exp utility to the installed database version.

Installing the 11.2.0.4 client software on the Windows client, the error no longer occur.

NOTE:
Original Export is desupported for general use as of Oracle Database 11g. The only supported use of original Export in Oracle Database 11g is backward migration of XMLType data to Oracle Database 10g release 2 (10.2) or earlier.
Please refer to

OERR: EXP 3 "no storage definition found for segment(%lu, %lu)" (文档 ID 21599.1)

APPLIES TO:

Oracle Server - Enterprise Edition - Version 7.0.16.0 and later
Information in this document applies to any platform.

PURPOSE

Checked for relevance on 15 June 2012

QUESTIONS AND ANSWERS

Enter the Main Content

Error: EXP 3
Text: no storage definition found for segment(%lu, %lu)
-------------------------------------------------------------------------------
Cause: Export could not find the storage definitions for a cluster, index, or table.
*Action: Record the accompanying messages and report this as an Export internal error to customer support.

Diagnosis:
We could not find a storage clause for the named segment.

- The arguments above are file and block, referred to here as
F and B

- First determine what the segment is:

​ select * from dba_segments
​ where HEADER_FILE = F
​ and HEADER_BLOCK = B;

- If it is an INDEX see Bug:231159

- If it is a TABLE it may be best to run this to find table SEGMENTS
whose segment owner differs from the OBJECT owner:

​ select o.owner#, o.name, o.type#, o.namespace, s.user#
​ from obj$ o, tab$ t, seg$ s
​ where o.obj#=t.obj#
​ and t.file#=s.file#
​ and t.block#=s.block#
​ and o.owner#!=s.user#
​ ;

​ Any rows returned should be investigated.

Known Issues:
EXP 3 against Indexes / Constraints See Bug:231159

Troubleshooting Guide to Solve Common Errors with Portal Export/Import (文档 ID 364463.1)

APPLIES TO:

Portal - Version 9.0.2.2 to 11.1.1.4.0 [Release 9iASR2 to FMW11g]
Information in this document applies to any platform.
Checked for relevance on 23-Jun-2014

PURPOSE

This Note describes the most common issues reported with Portal Export/Import, their causes, and suggested actions that you may encounter while exporting and importing with OracleAS Portal.

In addition to the Support Notes below, you can get additional information here: Discussion Forums.

SCOPE

For Portal Administrators who need to migrate Portal content using Portal Export/Import utilities.

DETAILS

This document contains the following sections:

1. Known Issues with Portal Export/Import.

1.1 Start here.

1.2 Issues running a Portal Export/Import from the Portal UI.

1.3 Issues accessing the Export or Import View Logs from the Portal UI.

1.4 Issues running the Export or Import scripts from the command line.

1.5 Errors in the Export or Import Logs generated by the Export/Import script.

1.6 Errors in the Export or Import View Logs from the Portal UI.

1.7 Issues Deleting Transport Sets.

1.8 Getting Unexpected Results after Import.

2. Known Issues applying Export/Import Patches.

1. Known Issues with Portal Export/Import.

1.1 Start here.

If you have issues when doing Portal Export/Import check first the following documentation:

  • Be sure you have the latest Export/Import patches applied to both Portals (source and target).
    More Information about the latest Export/Import patches is here:

    Note 263995.1 Master Note for OracleAS Portal Export / Import Issues

  • Run the Schema Validation utility (SVU) in REPORT mode before starting a Portal Export or Import to be sure there are no inconsistencies in your portal that could cause the Export/Import to fail.

    More Information about the latest SVU patches and how to use the SVU is here:

    Note 263995.1 Master Note for OracleAS Portal Export / Import Issues
    Note 286619.1 SCHEMA VALIDATION UTILITY

  • Check your Portal meets the requirements for doing Export/Import.
    More Information about the requirements for doing Portal Export/Import is here:

    Note 308553.1 Checking your Portal meets the requirements for doing Portal Export/Import

  • Check what you are doing is supported.

    More information about supported/unsupported scenarios when using Portal Export/Import is here:

    Note 333867.1

    Portal Export/Import Supportability Guide

    And here:

    Portal VersionDocumentation
    11.1.1Oracle Fusion Middleware Administrator's Guide for Oracle Portal 11g Release 1 (11.1.1) 11.9 Recommended Best Practices When Exporting and Importing
    10.1.4Oracle Application Server Portal Configuration Guide 10g Release 2 (10.1.4) 10.4 Recommended Best Practices When Exporting and Importing
    10.1.2Oracle Application Server Portal Configuration Guide 10g Release 2 (10.1.2) 10.4 Recommended Best Practices When Exporting and Importing

  • Check the following additional documentation for documented issues.

    Portal VersionDocumentation
    11.1.1Oracle Fusion Middleware Administrator's Guide for Oracle Portal 11g Release 1 (11.1.1) Oracle Fusion Middleware Error Messages Reference 11g Release 1 (11.1.1.5.0)
    10.1.4Oracle Application Server Portal Error Messages Guide 10g Release 2 (10.1.4) Oracle Application Server Release Notes 10g Release 2 (10.1.2) for Linux x86 Oracle Application Server Portal Installation and Upgrade Guide 10g Release 2 (10.1.4)
    10.1.2Oracle Application Server Portal Error Messages Guide 10g Release 2 (10.1.2) Oracle Application Server Release Notes 10g Release 2 (10.1.2) for Linux x86

1.2 Issues running a Portal Export/Import from the Portal UI.

Unable to Export: Transport set status remains on "Export" status

Portal Version: ALL

Problem Description:

Doing an Export from the Portal UI does nothing.
The Export View log shows only the following:

Before Submitting Job for export
After Submitting Job for export

Cause:

The database parameter job_queue_processes is set to 0.
Minimum value of job_queue_processes to do Portal Export/Import is 2.
However in some environments a higher value might be required.

Fix:

Set job_queue_processes to 2 or a greater value.

References:

Note 308553.1 Checking your Portal meets the requirements for doing Portal Export/Import

Unable to Import: Transport Set Status remains on "Import"

Portal Version: ALL

Problem Description:

Doing an Import from the Portal UI does nothing.
The Import View log shows only the following:

Before Submitting Job for import
After Submitting Job for import

Cause:

The database parameter job_queue_processes is set to 0.

Minimum value of job_queue_processes to do Portal Export/Import is 2.
However in some environments a higher value might be required.

Fix:

Set job_queue_processes to 2 or a greater value.
If 2 is not enough then set to a higher value like 5 or 10.

References:

Note 308553.1 Checking your Portal meets the requirements for doing Portal Export/Import

Unable to Export or Import with security: Transport Set Status remains in Progress

Portal Version: ALL

Problem Description:

The Export Job seems to get into a loop.
The Portal database is setup to use Cost Based Optimizer (CBO).

Other symptoms:

Enabling a trace of the job session shows ORA-07445 errors while doing a query on wwpre_name$.

The following query from sqlplus as portal user returns ORA-3113 error:

select id, name from wwpre_name$
where name = 'default' or name = 'defaultmobile';

Cause:

The entire Portal schema has being analyzed to gather statistics for Performance.
Portal schema should NOT be analyzed. This is not supported.

Fix:

Ensure that there are no errant statistics in the Portal schema, issue the following command from SQL*Plus:
exec dbms_stats.delete_schema_stats(ownname=>'PORTAL');

Then use the procedure WWSBR_STATS.GATHER_STATS for managing the CBO statistics (execute as portal schema):

exec wwsbr_stats.gather_stats;

Unable to Export: Export Times Out with error "No Response from Application Web Server"

Portal Version: 10.1.4.X, 10.1.2.X, 9.0.4 , 9.0.2

Problem Description:

Doing the export or import of a large page group or DB Provider from the Portal UI the export or import seems to be very slow.
After a while you get the following error (in the browser):

No Response from Application Web Server

Cause:

Starting with Portal 9.0.2.6 the product has being improved to check for dependencies and show this information in order to have all dependencies imported first.

Large page groups involve large amounts of dependency checks. Since these have to be done prior to exporting the transport sets as a foreground job, the UI could time-out prematurely.

The same issue will exist when pre-checks are done during import to validate the transport set objects.

Other possible cause could be that the Apache Timeout value is too low.
You can try to implement Solution 2 of Note 259398.1.
But if increasing the Apache Timeout doesn't solve the Export Timeout error then you need to use the next workaround.

Workaround (Unix):

Do the export using the opeasst.csh Tool.

Workaround (Windows):

Run the shell script tool (opeasst.csh) on the Windows operating system using one of the following UNIX emulation utilities:

o Cygwin 1.3.2.2-1 or later. Visit:

o MKS Toolkit 6.1. Visit: @ http://www.datafocus.com/

References:

Note: 259398.1 Portal Export/Import Times Out In Portal 9.0.2.6+ With Error: No Response from Application Web Server

NEED OPEASST FOR WINDOWS PLATFORM

Portal Import Button does nothing while using a Language other than English

Portal Version: 10.1.4.1

Problem Description:

When using the Portal UI in a Language other than English to perform a Portal Import the buttons available to complete the import in the Dependency Manager page do nothing.

The user clicks the buttons (Import Now, Closed, Save for Later) and they don't do anything.

Cause:

PROBLEM ON IMPORT WINDOWS WHEN I USE FRENCH LANGUAGE (Public).

NLS: STRINGS USED IN JAVASCRIPT ALERT OR CONFIRM MESSAGES SHOULD ESCAPE QUOTES (Public)

Fix / References:

Note 356711.1 Press Portal Import Button it does Not do Anything While Using French Language

Unable to Export: Get "The page cannot be found" error exporting from the Portal UI

Portal Version: 9.0.2.6

Problem Description:

Get the following error in the browser when doing Export:

The page cannot be found
HTTP 400 - Bad Request

The error_log file shows the following error:

[error] mod_plsql: /pls/cust_portal/PORTAL.wwutl_ui_export_import.create_new_eds
HTTP-400 Too many arguments. It is 2625. Upper limit is 2000

Cause:

GET "THE PAGE CANNOT BE FOUND" ERROR EXPORTING A PAGE

Fix:

Install the 9.0.2.6.0A version of mod_plsql which is available in patch for .

Or as an alternative way you can do the export using the opeasst.csh Tool (see Note:259398.1 for details on how to run this script).

1.3 Issues accessing the Export or Import View Logs from the Portal UI.

Accessing the Transport Set Logs from the Portal UI Times Out with error: No Response from Application Web Server

Portal Version: 10.1.4.X, 10.1.2.X, 9.0.4 , 9.0.2

Problem Description:

Attempting to look at the Transport Set Log from the Portal UI the response seems to be very slow.
After a while you get the following error (in the browser):

No Response from Application Web Server

Cause:

This is related with exporting/importing large page groups explained here.

Workaround:

  • Connect to sqplus as portal schema.

  • Run the following query to identify the export_id for the transport set:

    SELECT Distinct export_id, name FROM wwutl_export_import$
    WHERE name=''
    /

    In the query above, replace with the transport set name.

  • Use the following query to extract the log:

    spool large_pg_ts_imp.log
    select entry from wwutl_export_import_log$
    where export_id =
    where transport_mode = 'IMPORT'
    order by id;
    spool off

Reference:

TRANSPORT SET LOG SCREEN TIMES OUT FOR LARGE PAGE GROUP IMPORTS

1.4 Issues running the Export or Import scripts from the command line.

Error running the Import Script: Unable to Set Context for Portal User

Portal Version: ALL

Problem Description:

Running the import script to import a transport set you get the following error:

Mode Selected is IMPORT
Enter company name (default=none):
Checking for privileges...
Setting the Context...
Error: Unable to Set context for Portal User Portal
Cannot proceed with Import

Cause 1:

The values specified for portal username, portal password, and company are incorrect causing the authentication to fail. Make sure that the correct values are provided for the following prompts:

Fix:

Run the export script without specifying any parameters so you get prompted for the required values. When prompted provide the following information.

  • Enter the name of the portal user:
    Specify the portal lightweight username you use to login to Portal from your browser.

  • Enter the password for the portal user:
    Specify the portal lightweight user password you use to login to Portal from your browser.

  • Enter company name (default=none):
    Hit return if hosting is not enabled or if you are unsure; otherwise, enter the company name ONLY if you have hosting enabled.

You can also specify the values to the above parameters in the command line using:

MyScript.csh ... -pu portal_username -pp portal_userpassword -company NONE ...

Cause 2:

You upgraded the Portal database after installing Portal.

Some database upgrades include changes to the DBMS_LDAP_UTL package.

Fix:

Reload the LDAP package.

Reference:

Note 242030.1 Upgrade the database and now getting: Error: Unable to Set Context for Portal User

Running the Import Script: Importing a Transport Set to a 10.2 or later Release of the Database Hangs

Portal Version: ALL

Problem Description:

Running the import script to import a Transport Set with "-mode import" hangs and does not return to the prompt.

Import is run from the Midtier Oracle Home or the Infrastructure Oracle home.

Target Portal Database version is 10.2 or later.

Cause:

This issue is caused by a Database Import Utility compatibility.
The database export/import utilities installed with Oracle Portal Home or the Infrastructure Oracle home might be lower than the database Release.

Fix:

Run the Import script from the Database Home.

Reference:

Note 419473.1 Portal Transport Set Import Hangs when Importing to 10.2 Database

1.5 Errors in the Export or Import Logs generated by the Export/Import script.

Error in the Export log generated by the Export Script: EXP-00003 no storage definition found for segment

Portal Version: ALL

Problem Description:

Running the export script from the command line to extract the transport set tables returns the following errors:

EXP-00003: no storage definition found for segment(%lu, %lu)

The portal Repository is installed in a Database version is 9.2.0.5 or higher.

Cause:

Export Of Lob From 9205 With Pre-9205 Exp Gives Exp-3 (No Storage Def Found)

Fix:

Note 316215.1 Getting EXP-00003 Errors While Exporting a Transport Set to create the .dmp File

Error in the Export log generated by the Export Script: EXP-6: Internal Inconsistency Error

本人提供Oracle(OCP、OCM)、MySQL(OCP)、PostgreSQL(PGCA、PGCE、PGCM)等数据库的培训和考证业务，私聊QQ646634621或微信dbaup66，谢谢！
AiDBA后续精彩内容已被站长无情隐藏，请输入验证码解锁本文！
验证码：
获取验证码： 请先关注本站微信公众号，然后回复“验证码”，获取验证码。在微信里搜索“AiDBA”或者“dbaup6”或者微信扫描右侧二维码都可以关注本站微信公众号。

标签：

Avatar photo

小麦苗

学习或考证，均可联系麦老师，请加微信db_bao或QQ646634621

您可能还喜欢...

发表回复