【故障处理】EXP-00003: no storage definition found for segment

EXP-00003: no storage definition found for segment


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
http://docs.oracle.com/cd/E11882_01/server.112/e22490/original_export.htm#SUTIL3634


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 Version Documentation
    11.1.1 Oracle 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.4 Oracle Application Server Portal Configuration Guide
    10g Release 2 (10.1.4)
    10.4 Recommended Best Practices When Exporting and Importing
    10.1.2 Oracle 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 Version Documentation
    11.1.1 Oracle Fusion Middleware Administrator's Guide for Oracle Portal
    11g Release 1 (11.1.1)
    G Troubleshooting Oracle Portal

    Oracle Fusion Middleware Error Messages Reference
    11g Release 1 (11.1.1.5.0)
    99 WWU-52262 to WWU-83028
    10.1.4 Oracle Application Server Portal Error Messages Guide
    10g Release 2 (10.1.4)
    5 WWU-52262 to WWU-80002

    Oracle Application Server Release Notes
    10g Release 2 (10.1.2) for Linux x86
    9.2.4 Export and Import Issues and Workarounds

    Oracle Application Server Portal Installation and Upgrade Guide
    10g Release 2 (10.1.4) 
    4.1.6 Reenabling Portal Export and Import 
    10.1.2 Oracle Application Server Portal Error Messages Guide
    10g Release 2 (10.1.2) 
    4 WWU-52262 to WWU-80002

    Oracle Application Server Release Notes
    10g Release 2 (10.1.2) for Linux x86
    9.2.4 Export and Import Issues and Workarounds

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: http://sources.redhat.com

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 

Bug 3309543 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:

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

Bug 5614340  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:

Bug 3281880 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 Bug:3355915.

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='<Transport_set_name>'
    /

    In the query above, replace <Transport_set_name> 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 = <export_id_of_large_transport_set>
    where transport_mode = 'IMPORT'
    order by id;
    spool off

Reference:

Bug 3981832 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:

Bug 3784697 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

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

Problem Description:

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

. . exporting table WWSRC_PREFERENCE$ 441 rows exported
EXP-00006: internal inconsistency error
EXP-00056: ORACLE error 1403 encountered
ORA-01403: no data found

The database version is 9.0.1.X.

Cause:

Bug 2906613 DURING DB EXPORT, CUSTOMER RECEIVES 'EXP-6: INTERNAL INCONSISTENCY ERROR'

This problem is a database bug and is fixed in database release 9.2.

Workaround:

Only apply this workaround when you get the above error.
Create the following view, connected as sys, before running the export:

set long 9999
set pagesize 9999
spool old_exu8con_view.log
select OWNER||'.'||VIEW_NAME, TEXT
from dba_views where VIEW_NAME = 'EXU8CON';
spool off

CREATE OR REPLACE VIEW exu8con (
     objid, owner, ownerid, tname, type, cname,
     cno, condition, condlength, enabled, defer,
     sqlver, iname) AS

SELECT o.obj#, u.name, c.owner#, o.name,
     decode(cd.type#, 11, 7, cd.type#),
     c.name, c.con#, cd.condition, cd.condlength,
     NVL(cd.enabled, 0), NVL(cd.defer, 0),
     sv.sql_version, NVL(oi.name, '')
FROM sys.obj$ o, sys.user$ u, sys.con$ c,
     sys.cdef$ cd, sys.exu816sqv sv, sys.obj$ oi
WHERE u.user# = c.owner# AND
     o.obj# = cd.obj# AND
     cd.con# = c.con# AND
     cd.spare1 = sv.version# (+) AND
     cd.enabled = oi.obj# (+) AND
     NOT EXISTS (
         SELECT owner, name
         FROM sys.noexp$ ne
         WHERE ne.owner = u.name AND
         ne.name = o.name AND
         ne.obj_type = 2);

spool new_exu8con_view.log
select OWNER||'.'||VIEW_NAME, TEXT
from dba_views
where VIEW_NAME = 'EXU8CON';
spool off

After the export you can recreate the exu8con view using the original definition from admin/catexp.sql

Explanation:

The modification of exu8con simply adds support for a constraint type that had not previously been supported by this view. There is no negative impact.

References:

Note 270881.1 Error while exporting the portal user tables: EXP-00006 EXP-00056 ORA-01403

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

Precheck failed for search items on import

Portal Version: ALL

Problem Description:

Importing a Page Group using Portal Export/Import utilities is failing with the following error:

[ERROR] id = ORA-29273: HTTP request failed
ORA-6512: at "SYS.UTL_HTTP", line 1665
ORA-28868: certificate chain context = wwutl_api_import_security.import_external_application user = PORTAL unexpected_sqlerrm
ORA-29273: HTTP request failed
ORA-6512: at "SYS.UTL_HTTP", line 1665
ORA-28868: certificate chain check failed

Pre checking search items

...

Precheck failed for search item with id <id> on page <page_name> in page group <page_group_name>

The search item is customized to search in a page group which is not in the target portal or included in the transport set. On import the search item is defaulted to search in all page groups

...

Search Items precheck complete

Cause:

There are items of type "Basic Search Box" in the page group that were customized to search in specific page groups and those page groups do not exist in the target portal.

Workaround:

Note 362007.1 Precheck failed for search items on import

Error on Import: ORA-29273: HTTP request failed

Portal Version: ALL

Problem Description:

Importing a Page Group using Portal Export/Import utilities is failing with the following error:

[ERROR] id = ORA-29273: HTTP request failed
ORA-06512: at "SYS.UTL_HTTP", line 1674
ORA-29024: Certificate valid context = wwutl_api_import_security.import_external_application user = PORTAL unexpected_sqlerrm
ORA-29273: HTTP request failed
ORA-06512: at "SYS.UTL_HTTP", line 1674
ORA-29024: Certificate validation failure

or

[ERROR] id = ORA-29273: HTTP request failed
ORA-6512: at "SYS.UTL_HTTP", line 1665
ORA-28868: certificate chain context = wwutl_api_import_security.import_external_application user = PORTAL unexpected_sqlerrm
ORA-29273: HTTP request failed
ORA-6512: at "SYS.UTL_HTTP", line 1665
ORA-28868: certificate chain check failed

Cause:

The query Path URL is not correctly set in the Portal Global Settings.

Fix:

Note 304163.1 Portal Import Error On : ORA-29273: HTTP request failed

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

Error Importing a page group: Pre-check failed for search portlet with reference path xxxx

Portal Version: ALL

Problem Description:

Importing a Page Group is failing with the following error:

Checking for missing search portlet preference dependencies...

Pre-check failed for search portlet with reference path <XXXX>_PAGESEARCH_<YYYY>

Search portlet has dependencies which are not included in the transport set or do not exist in the target

If import continues, all missing dependencies are removed or reset accordingly as described below

PAGE GROUPS : All of the page groups to be searched are missing. On import, the portlet will search all page groups

Pre-check failed for search portlet with reference path <XXXX>_PAGESEARCH_<YYYY>

After import all Custom Search Portlet customizations are lost. All Custom Search Portlet customizations are reset to the defaults.

Cause:

The Page Group being imported has Custom Search Portlets that have references to other objects like Page Groups/Pages that do not exist in the target portal.

Fix:

Note 382807.1 Importing a page group fails with error: Pre-check failed for search portlet with reference path xxxx

Error Importing a page group: ORA-01691: unable to extend lob segment

Portal Version: ALL

Problem Description:

Importing a Page Group is failing with the following error:

[Error: ] context = NULL user = PORTAL WWUTL_API_EXPORT_PAGEGROUP.start_export
ORA-06510: PL/SQL: unhandled user-defined exception
ORA-06512: at "PORTAL.WWUTL_DB_EXPORT_IMPORT", line 1527
ORA-01691: unable to extend lob segment PORTAL.SYS_LOB0000272921C00009$$ by 138254 in tablespace PORTAL

Cause:

Lack of Space in the Portal tablespace.

Fix:

Note 1612758.1 ORA-1691: unable to extend lobsegment when inserting to table with securefile

Error Importing a page group: wwutl_api_import_security.set_user_acl Unexpected Error: Setting User ACL

Portal Version: 10.1.2.X

Problem Description:

Importing a Page Group using Portal Export/Import utilities is failing with the following error:

Running import necessary privileges step

Context: wwutl_api_import_security.set_user_acl Unexpected Error: Setting User ACL

ORA-01403: no data found
ORA-01403: no data found
ORA-06512: at "PORTAL.WWSEC_SYSP_BRI_TRG", line 19
ORA-04088: error during execution of trigger 'PORTAL.WWSEC_SYSP_BRI_TRG'

Cause:

Bug 5026917 Error In Post-Import Step While Assigning Privileges To User Performing Import

Fix:

Note 384256.1 Error Importing a page group: wwutl_api_import_security.set_user_acl Unexpected Error: Setting User ACL ORA-01403

1.7 Issues Deleting Transport Sets.

Trying to remove a transport set returns Internal Error (WWC-00006)

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

Problem Description:

Unable to delete a Portal Export/Import Transport Set.

Trying to delete the transport set results in the following errors:

Internal Error (WWC-00006)
Unexpected error - User-Defined Exception (WWU-52200).

Cause:

The Export/Import failed and the transport set was created but it can't be removed.

Workaround:

Note 329705.1 Trying to remove a transport set returns Internal Error (WWC-00006)

1.8 Getting Unexpected Results after Import.

After import all URLs items are pointing to the Source System

Portal Version: ALL

Problem Description:

You have URL Items pointing to other items in the portal.

The URL field is using a full URL like this:

http://server:port/pls/portal/url/ITEM/GUID

You migrated your pages using Portal Export/Import Utilities.
After import the URL Items are pointing to the source system.

Cause:

URLs in URL Items are not modified after import.
The URLs are preserved exactly as they are in the source.
This is the expected behavior.

Fix:

Note 358673.1 After import all URLs items are pointing to the Source System

After import all Providers are pointing to the Source System

Portal Version: ALL

Problem Description:

You have portlets from web providers in your pages.
You migrated your pages using Portal Export/Import utilities.
After import all providers are pointing to the source system.

Cause:

The provider was not registered in the target before the import.
On import if the provider does not exists in the target the import will register the provider using the URL from the source.

Fix:

Note 358677.1 After import all Providers are pointing to the Source System

After Import all URLs to call your Components from a Portal DB Provider are Pointing to the Source System

Portal Version: ALL

Problem Description:

You have a select statement in a Portal Component (i.e from a Report from SQL Query, or a Chart from SQL Query, or a Calendar, or a Dynamic Page, etc) that calls another Component from a Locally Built DB Provider.

You are using a full URL in the query to call the other component like this:

select 'http://server:port/pls/portal/PORTAL.wwa_app_module.link?'||
       'p_arg_names=_moduleid&p_arg_values=1464896185'||
       '&p_arg_names=EMPNO&p_arg_values='||to_char(empno)||
       '&p_arg_names=_empno_cond&p_arg_values=%3D' empno,
       ename
from SCOTT.EMP

You are migrating your Portal Objects using Portal Export/Import Utilities.

After import the URLs to the components are still pointing to the source system.

Cause:

URLs in the queries are not modified after import.
The URLs are preserved exactly as they are in the query from the source.
This is the expected behavior.

Fix:

Note 358720.1 After Import all URLs to call your Components from a Portal DB Provider are Pointing to the Source System

After import content Items added in the target are lost

Portal Version: ALL

Problem Description:

You exported a Page Group, then added some content in the target Portal (i.e. added some file items).

Then after repeating the Import of the Page Group the items added in the target are lost.

Cause:

Content Items added in the target will be removed or preserved depending on the import mode selected (replace or reuse).

Explanation:

The following note explains what happens when you add items in the target and what happens if you repeat the import of the page group:

Note 358690.1 Where to add content such file items when using Portal Export/Import utilities ... Development or Production

Users Not Getting To Their Default Home Page after Import

Portal Version: ALL

Problem Description:

Users are redirected to the portal global default home page rather than the user's default home page.

The default home page is assigned to a group that is the default group of the users.

The user's default home page was imported from another Portal instance.

Cause:

The groups were created in the target OID after the portal import.

Bug 5648421 USERS NOT GETTING TO THEIR DEFAULT HOME PAGE

Workaround:

Note 406978.1 Users Not Getting To Their Default Home Page after Import

Automatic_merge option has no effect during manually Page group Import on Windows platforms

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

Problem Description:

You are importing from the command line using the automatic_merge option. The transport set is created but the Page Group is not being created.

Cause:

Bug 3516664 IMPORT OPTION "AUTOMATIC_MERGE" HAS NO EFFECT ON WINDOWS

This bug is fixed in Portal 10.1.4.

Workaround:

Import the transport set from the Portal UI.

After Portal Import: Oracle Drive Doesn't Show Pages Created Through Portal UI

Portal Version: 10.1.2.0.2

Problem Description:

New pages created in some imported page groups are not visible from webdav. It happens on page group having translations.

Cause:

Bug 5747283 NEW PAGES CREATED IN SOME IMPORTED PAGE GROUPS CAN'T BE SEEN VIA WEBDAV

Workaround:

Note 414746.1 After Portal Import: Oracle Drive Doesn't Show Pages Created Through Portal UI

Oracle Report Items do not bring the parameters after import

Portal Version: 9.0.4.1

Problem Description:

After Import all Oracle Report Items in the pages return the following error when click on "Run Report":

Not Found

The requested URL /pls/portal/PORTAL.wwv_rw_utl.show_report was not found on this server.

Cause:

Bug 12028612 IMPORT DOES NOT INCLUDE THE MULTIPLE INPUT VARIABLE FOR PROCEDURE CALL

Workaround:

Note 336241.1 Oracle Report Items do not bring the parameters after import

Portal Surveys are missing after Import

Portal Version: ALL

Problem Description:

After Import all Portal Surveys are missing.

Cause:

Export/Import of Portal Survey components is not supported.

References:

Note 333867.1 Portal Export and Import Utility Supportability Scenarios

2. Known Issues applying Export/Import Patches.

Installing Portal patches with OPATCH on Unix environments completes successfully but the patches are not installed

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

Problem Description:

Installing a portal patch using OPATCH on a Unix environment completes usefully but the patch is not applied.

No error was reported anywhere.

The following query from sqlplus as portal schema doesn't show the patch in the list of installed patches:

select * from WWUTL_PATCHLOG$;

Cause:

Bug 4358353 PROBLEM WITH DBI LIB ON OPATCH CALL

Fix:

Note 316775.1 Installing Portal patches with OPATCH on Unix environments completes successfully but the patches are not installed

Applying a One-Off Patch On All Operating Systems Except Windows and SPARC Solaris after applying Application Server Patchset 2 (10.1.2.2)

Portal Version: 10.1.4.1 (With iAS Patchset 10.1.2.2)

Problem Description:

After applying the Oracle 10g Application Server Patchset 2 (10.1.2.2.0) on non-Windows and Solaris platforms the following error will be seen:

OPatch detects your platform as 23 while this patch < XXXXXXX > supports platforms:

This patch is not suitable for this operating system.
Please contact support for the correct patch.

Cause:

Bug 5861907 IAS 10.1.2.2 PATCHSET UPDATES ORACLEHOMEPROPERTIES.XML WITH WRONG ARU_ID & ARU_I.

Fix:

Note 413788.1 Applying a One-Off Patch On All Operating Systems Except Windows and SPARC Solaris Fails After Application Server Patchset 2 (10.1.2.2)

Unable to apply a Portal Patch with opatch : None of the patch actions is applicable to the Oracle Home

Portal Version: 10.1.4.X and 10.1.2.X (With iAS Patchet 10.1.2.1)

Problem Description:

When attempting to apply a Portal Patch the following error occurs:

ERROR
SKIPPING_COMPONENT=oracle.webdb,10.1.2.0.1

None of the patch actions is applicable to the Oracle Home.
OPatch will not apply the patch, exiting...

Cause:

The Midtier was upgraded with an iAS Patch from 10.1.2.0.0 to 10.1.2.1.

The reason of this error is that patches are included with an inventory file to validate the version of the Midtier where the patch can be applied. As new iAS Patches are released it could be that the patch was released before the iAS Patch. So the inventory file of the patch doesn't contemplate the new version of the upgraded iAS Midtier.

Fix:

Note 437952.1 Unable to apply a Portal Patch with opatch : None of the patch actions is applicable to the Oracle Home

Applying a Portal Patch with OPATCH returns the following Error: MISSING_COMPONENT : oracle.webdb, 10.1.2.0.1

Portal Version: 10.1.4, 10.1.2.0.2

Problem Description:

Trying to apply a Portal Patch using OPATCH returns the following error:

MISSING_COMPONENT : oracle.webdb, 10.1.2.0.1

This Oracle Home does not have components/versions required by the patch.

ERROR: OPatch failed during pre-reqs check.

The Midtier was upgraded from 10.1.2.0.0 or 10.1.2.0.1 to 10.1.2.1.0 (Patch 4908436)

Cause:

Portal patches check the Midtier Version and the patch is expecting a 10.1.2.0.2 Midtier.

Fix:

Note 387596.1 Applying a Portal Patch with OPATCH returns the following Error: MISSING_COMPONENT : oracle.webdb, 10.1.2.0.1

Applying a portal patch with OPATCH returns ERROR: Invalid SYS Connect Info

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

Problem Description:

While applying a portal patch using opatch you get the following error:

ERROR: Invalid SYS Connect Info, cannot proceed with the installation.

Cause:

Bug 4138095 Applying Patch 4119778 Version 4 For 9.0.4.1 Results In Error

Fix:

Note 329791.1 Applying a portal patch with OPATCH returns ERROR: Invalid SYS Connect Info

Error PLS-00323 running the recompile.sql script from the latest export/import consolidated patch for 9023 (Patch:3965222)

Portal Version: 9.0.2.3, 9.0.2.3b

Problem Description:

When you run the recompile.sql script that comes with the consolidated patch you get the following error:

SQL> @recompile.sql
...
Error in alter package WWUTL_API_IMPORT_PAGEGROUP compile body
1083/33 PLS-00306: wrong number or types of arguments in call to 'GET_OBJECTS_LIST'
1083/13 PL/SQL: Statement ignored
Error in alter package WWUTL_DB_EXPORT_IMPORT compile body
765/15 PLS-00323: subprogram or cursor 'GET_OBJECTS_LIST' is declared in a package specification and must be defined in the package body

Cause:

You enabled the debug option for the Export using Note 216087.1.

You compiled the utldbmgr.pks package to enable the debug option for export.

But you used the script from the following location:

$MIDTIER_HOME/portal/admin/plsql/wwu/utldbmgr.pks

The above script is the corresponding to the base release of Portal (9.0.2.2.22). 

Fix:

You need to use the script for Portal 9.0.2.3/9.0.2.3b from the correct location. Compile the utldbmgr.pks package from here:

$MIDTIER_HOME/portal/patch-9-0-2-3-0/p90230/wwu/utldbmgr.pks

Then recompile the objects again using recompile.sql

Error PLS-00306 applying the latest export/import consolidated patch for 9023 (Patch:3965222)

Portal Version: 9.0.2.3, 9.0.2.3b

Problem Description:

When you compile the utlimsbr.pkb package that comes with the consolidated patch you get the following error:

SQL> @utlimsbr.pkb
Warning: Package Body created with compilation errors.
Errors for PACKAGE BODY WWUTL_API_IMPORT_PAGEGROUP:
LINE/COL ERROR
-------- ------------------------------------------- ----------------------
1083/13 PL/SQL: Statement ignored
1083/33 PLS-00306: wrong number or types of arguments in call to 'GET_OBJECTS_LIST'

Cause:

You upgraded your Portal to 9.0.2.3/9.0.2.3b but the Portal repository is not correctly patched with this release.
You can verify this as follows:

Connect to sqlplus as portal user and execute the following query:
select version from wwc_version$;

This query should return the following version:

  • 9.0.2.3b
    If you have the iAS 90230 Patchset for 9iAS 9.0.2.X installed in your Midtier (Patch 3038037).
  • 9.0.2.3
    If you have the Portal Patch Release 9.0.2.3 installed in your Midtier (Patch 2744619).

Fix:

If the query on wwc_version$ table doesn't show the correct version of Portal (9.0.2.3b or 9.0.2.3) then the portal repository should be patched manually as follows:

  • Connect to the Midtier.
  • Change to the following directory:

    $MIDTIER_HOME\portal\patch-9-0-2-3-0\p90230

  • Patch the portal repository manually:

    patch.csh -s <portal_schema> -p <portal_password> -l patch.log -c <host>:<port>:<sid>

    Where:
       <portal_schema> - Is the portal schema.
       <portal_password> - Is the portal schema password.
       <host>:<port>:<sid> - Is the connect string to the portal repository.

REFERENCES

NOTE:263995.1 - Master Note for OracleAS Portal Export / Import Issues
NOTE:270881.1 - Exporting Portal Schema User Fails with ORA-01403 for WWSRC_PREFERENCE$
NOTE:286619.1 - SCHEMA VALIDATION UTILITY (SVU)
NOTE:304163.1 - Portal Import Error On : ORA-29273: HTTP request failed
NOTE:308553.1 - Checking your Portal meets the requirements for doing Portal Export/Import
NOTE:316215.1 - Getting EXP-00003 Errors While Exporting a Transport Set to Create the .dmp File
NOTE:316775.1 - Installing Portal patches with OPATCH on Unix environments completes successfully but the patches are not installed
NOTE:329705.1 - Trying to remove a transport set returns Internal Error (WWC-00006)
NOTE:329791.1 - Applying a portal patch with OPATCH returns ERROR: Invalid SYS Connect Info
NOTE:333867.1 - Portal Export and Import Utility Supportability Scenarios
NOTE:336241.1 - Oracle Report Items do not bring the parameters after import
NOTE:356711.1 - Press Portal Import Button it does Not do Anything While Using French Language
NOTE:358673.1 - After import all URLs items are pointing to the Source System
NOTE:358677.1 - After import all Providers are pointing to the Source System
NOTE:358690.1 - Where to add content such file items when using Portal Export/Import utilities ... Development or Production instance?
NOTE:358720.1 - After Import all URLs to call your Components from a Portal DB Provider are Pointing to the Source System
NOTE:362007.1 - Precheck failed for search items on import
NOTE:382807.1 - Importing a page group fails with error: Pre-check failed for search portlet with reference path xxxx
NOTE:384256.1 - Error Importing a page group: wwutl_api_import_security.set_user_acl Unexpected Error: Setting User ACL ORA-01403
NOTE:387596.1 - Applying a Portal Patch with OPATCH returns the following Error: MISSING_COMPONENT : oracle.webdb, 10.1.2.0.1
NOTE:406978.1 - Users Not Getting To Their Default Home Page after Import
NOTE:413788.1 - Applying a One-Off Patch On All Operating Systems Except Windows and SPARC Solaris Fails After Application Server Patchset 2 (10.1.2.2)
NOTE:414746.1 - After Portal Import: Oracle Drive Doesn't Show Pages Created Through Portal UI
NOTE:419473.1 - Portal Transport Set Import Hangs When Importing to 10.2 Database
BUG:3981832 - TRANSPORT SET LOG SCREEN TIMES OUT FOR LARGE PAGE GROUP IMPORTS
BUG:12028612 - SUNBT4582721 ICS 2.1 DOES NOT WORK WITH I.E. ON THE MACINTOSH
BUG:2906613 - DURING DB EXPORT, CUSTOMER RECEIVES 'EXP-00006: INTERNAL INCONSISTENCY ERROR'
BUG:3281880 - OHS: GET "THE PAGE CANNOT BE FOUND" ERROR EXPORTING A PAGE
BUG:3309543 - NEED OPEASST FOR WINDOWS PLATFORM
BUG:3355915 - BACKPORT BUG#3329645
BUG:3516664 - IMPORT OPTION "AUTOMATIC_MERGE" HAS NO EFFECT ON WINDOWS
BUG:3784697 - EXPORT OF LOB FROM 9205 WITH PRE-9205 EXP GIVES EXP-3 (NO STORAGE DEF FOUND)
BUG:4138095 - APPLYING PATCH 4119778 VERSION 4 FOR 9.0.4.1 RESULTS IN ERROR
BUG:4358353 - PROBLEM WITH DBI LIB ON OPATCH CALL
BUG:4950649 - PROBLEM ON IMPORT WINDOWS WHEN I USE FRENCH LANGUAGE
BUG:5026917 - ERROR IN POST-IMPORT STEP WHILE ASSIGNING PRIVILEGES TO USER PERFORMING IMPORT
BUG:5614340 - NLS: STRINGS USED IN JAVASCRIPT ALERT OR CONFIRM MESSAGES SHOULD ESCAPE QUOTES
BUG:5648421 - USERS NOT GETTING TO THEIR DEFAULT HOME PAGE
BUG:5747283 - NEW PAGES CREATED IN SOME IMPORTED PAGE GROUPS CAN'T BE SEEN VIA WEBDAV
BUG:5861907 - IAS 10.1.2.2 PATCHSET UPDATES ORACLEHOMEPROPERTIES.XML WITH WRONG ARU_ID & ARU_I
NOTE:242030.1 - Upgrade the database and now getting: Error: Unable to Set Context for Portal User
NOTE:259398.1 - Portal Export/Import Times Out In Portal 9.0.2.6+ With Error: No Response from Application Web Server
NOTE:437952.1 - Unable to apply a Portal Patch with opatch : None of the patch actions is applicable to the Oracle Home
NOTE:1612758.1 - ORA-1691: unable to extend lobsegment when inserting to table with securefile

About Me


.............................................................................................................................................

● 本文作者：小麦苗，只专注于数据库的技术，更注重技术的运用

● 本文在itpub（http://blog.itpub.net/26736162/abstract/1/）、博客园（http://www.cnblogs.com/lhrbest）和个人微信公众号（xiaomaimiaolhr）上有同步更新

● 本文itpub地址：http://blog.itpub.net/26736162/abstract/1/

● 本文博客园地址：http://www.cnblogs.com/lhrbest

● 本文pdf版、个人简介及小麦苗云盘地址：http://blog.itpub.net/26736162/viewspace-1624453/

● 数据库笔试面试题库及解答：http://blog.itpub.net/26736162/viewspace-2134706/

● DBA宝典今日头条号地址：http://www.toutiao.com/c/user/6401772890/#mid=1564638659405826

.............................................................................................................................................

● QQ群号：230161599（满）、618766405

● 微信群：可加我微信，我拉大家进群，非诚勿扰

● 联系我请加QQ好友（646634621），注明添加缘由

● 于 2017-09-01 09:00 ~ 2017-09-30 22:00 在魔都完成

● 文章内容来源于小麦苗的学习笔记，部分整理自网络，若有侵权或不当之处还请谅解

● 版权所有，欢迎分享本文，转载请保留出处

.............................................................................................................................................

● 小麦苗的微店：https://weidian.com/s/793741433?wfr=c&ifr=shopdetail

● 小麦苗出版的数据库类丛书：http://blog.itpub.net/26736162/viewspace-2142121/

.............................................................................................................................................

使用微信客户端扫描下面的二维码来关注小麦苗的微信公众号（xiaomaimiaolhr）及QQ群（DBA宝典），学习最实用的数据库技术。

   小麦苗的微信公众号      小麦苗的DBA宝典QQ群1     小麦苗的DBA宝典QQ群2        小麦苗的微店

.............................................................................................................................................
时间： 2024-09-15 13:28:51

【故障处理】EXP-00003: no storage definition found for segment的相关文章

【ORACLE 导入导出】exp 错误

EXP-00000: Export terminated unsuccessfully Cause: Export encountered an Oracle error. Action: Look up the accompanying Oracle message in the ORA message chapters of this manual, and take appropriate action. EXP-00001: data field truncation - column

js仿微博实现统计字符和本地存储功能_javascript技巧

随着移动设备和Web应用的普及,为了更好的便于用户的使用,对于网页或应用程序的用户体验要求就越来越高,确实是这样,作为用户更喜欢选择用户体验效果好的网站或应用程序,所以作为开发者的我们就需要开发出更人生化的应用程序了. 相信许多人有使用微博的经验,像微博这样的社交平台,好的用户体验就变得尤其重要了. 例如:我们在发微博时,文本框会实时地提示我们剩余字符数,这样人性化的提示方便了用户知道微博字数的限制,同时也限制了用户的输入字数. 有一句话我们要牢记在心的是:凡是输入,必有限制:凡是输入,必须校验

Systemwide Tuning using STATSPACK Reports [ID 228913.1]

Systemwide Tuning using STATSPACK Reports [ID 228913.1]   修改时间 09-MAR-2012     类型 BULLETIN     状态 ARCHIVED   Systemwide Tuning using StatsPack Reports PURPOSE This article is a reference to understand the output generated by the STATSPACK utility. Si

关于segment的一个小问题

  今天统计数据的时候,发现一个奇怪的小问题,通过segment去判断一个表的大小,然后查表的count,有一个表明明在,但是从segment里面去查的时候查不出来. SQL> select distinct segment_name,to_number(to_char(sum(bytes/1024/1024/1024))) from user_segments where segment_name in (select table_name from user_tables where tab

Laravel 5.1 on SAE环境开发教程【附项目demo源码】_php实例

本文实例讲述了Laravel 5.1 on SAE环境开发方法.分享给大家供大家参考,具体如下: Laravel-简洁.优雅的PHP开发框架,为 WEB 艺术家创造的 PHP 框架,如今正式移植到SAE环境. 由于Laravel 5.1相比于Laravel 4有很多的改动,不仅以目录结构更加清晰,而且功能也更丰富.但是Laravel官方还是没有原生支持SAE环境(估计永远不会支持),所以我就做了一个移植版本,可以很优雅的切换本地和SAE环境. 由于SAE的特殊性,那么这几个核心问题就必须要解决

Laravel 5.1 on SAE环境开发教程【附项目demo源码】

本文实例讲述了Laravel 5.1 on SAE环境开发方法.分享给大家供大家参考,具体如下: Laravel-简洁.优雅的PHP开发框架,为 WEB 艺术家创造的 PHP 框架,如今正式移植到SAE环境. 由于Laravel 5.1相比于Laravel 4有很多的改动,不仅以目录结构更加清晰,而且功能也更丰富.但是Laravel官方还是没有原生支持SAE环境(估计永远不会支持),所以我就做了一个移植版本,可以很优雅的切换本地和SAE环境. 由于SAE的特殊性,那么这几个核心问题就必须要解决

【故障处理】IMP-00010错误 12C的dmp文件导入11G

[故障处理]IMP-00010错误 12C的dmp文件导入11G 1  BLOG文档结构图   2  前言部分 2.1  导读和注意事项 各位技术爱好者,看完本文后,你可以掌握如下的技能,也可以学到一些其它你所不知道的知识,~O(∩_∩)O~: ① 12C的dmp文件导入11g数据库 ② IMP-00010: not a valid export file, header failed verification错误解决一例 ③ 软件PilotEdit Lite的使用       ④ 从dmp文件

【故障处理】DG环境主库丢失归档情况下数据文件的恢复

[故障处理]DG环境主库丢失归档情况下数据文件的恢复 1  BLOG文档结构图     2  前言部分   2.1  导读和注意事项 各位技术爱好者,看完本文后,你可以掌握如下的技能,也可以学到一些其它你所不知道的知识,~O(∩_∩)O~: ① BBED的编译 ② BBED修改文件头让其跳过归档从而可以ONLINE(重点) ③ OS命名格式转换为ASM的命名格式 ④ DG环境中备库丢失数据文件的情况下的处理过程(重点) ⑤ 数据文件OFFLINE后应立即做一次RECOVER操作 ⑥ BBED环境

Oracle exp中的选项compress测试

Default: y Specifies how Export and Import manage the initial extent for table data. The default, COMPRESS=y, causes Export to flag table data for consolidation into one initial extent upon import. If extent sizes are large (for example, because of t