Skip Headers
Oracle® Application Server Portal Error Messages Guide
10g Release 2 (10.1.4)
B19304-01
  Go To Documentation Library
Home		 Go To Product List
Solution Area		 Go To Table Of Contents
Contents
Previous
Previous 		Next
Next 		 

5 WWU-52262 to WWU-80002

WWU-52262: Exception in %1 : %2.
Cause: An unknown exception occurred during the export-import operation.
Action: Do nothing. The selected object will be exported. If the export fails, contact Oracle Support Services.
WWU-52263: The object %1 was not added to the transport set because it already exists as (or is the child of) an explicit object.
Cause: The object is already marked for export.
Action: Do nothing. The selected object will be exported.
WWU-52293: An unknown exception occurred while validating the system tables. Aborting the export.
Cause: An abnormal exception occurred while performing the schema validation and cleanup.
Action: Check the schema-validation document, correct it, and export again.
WWU-52294: An unknown exception occurred while validating the system tables. Exiting the validation process. All changes performed by the validation process will be reverted.
Cause: An abnormal exception occurred while performing the schema validation and cleanup.
Action: Check the schema-validation document and correct it.
WWU-52295: An unknown exception occurred during the resolution of page group objects. The entire page group import is being rolled back.
Cause: An unknown exception occurred during the resolution of page group objects.
Action: Follow these steps:

1. If the log displays the cause of the error, correct the error and run the import again.

2. Run the schema-validation utility to correct the error and run the import again.

3. If you are still unable import successfully, contact Oracle Support Services.

WWU-52320: The source attribute %1 has been promoted to the Shared Objects page group. The same attribute on the target belongs to a local page group.
Cause: The same attribute on the source and the target belongs to different page groups. The source attribute was promoted to the Shared Objects page group, while the target attribute belongs to a local page group.
Action: Promote the local attribute on the target to the Shared Objects page group, and reimport it.
WWU-52321: The source attribute %1 belongs to a local page group. The same attribute on the target was promoted to the Shared Objects page group.
Cause: The same attribute on the source and the target belongs to different page groups. The source attribute belongs to a local page group, while the target attribute has been promoted to the Shared Objects page group.
Action: Promote the local attribute on the source to the Shared Objects page group, and reimport it.
WWU-52322: The Type or unique identifier of the source attribute %1 does not match the target attribute %1.
Cause: A different attribute on the target uses the same name as the attribute on the source.
Action: Delete the attribute on the target, and reimport it.
WWU-52323: The source attribute %1 exists on the target under a different name. The target attribute cannot be reused.
Cause: The attribute name has been changed on the source or the target.
Action: Import the attribute in overwrite mode, or make the names the same on both the source and the target.
WWU-52324: The length of the source attribute %1 is less than the same target attribute. Overwriting the target attribute can result in data inconsistency on the target.
Cause: The length of a text attribute on the target is greater than the length of the same text attribute on the source.
Action: Modify the length of the text attribute on the source and reimport it, or import it in reuse mode.
WWU-52325: The length of the target attribute %1 is less than the same source attribute. Reuse of the target attribute can result in data inconsistency on the source.
Cause: The length of a text attribute on the target is less than the length of the same text attribute on the source.
Action: Modify the length of the text attribute on the target and reimport it, or import it in overwrite mode.
WWU-52326: The source style %1 was promoted to the Shared Objects page group. The same style on the target belongs to a local page group.
Cause: The same style on the source and the target belongs to different page groups. The source style was promoted to the Shared Objects page group, while the target style belongs to a local page group.
Action: Promote the local style on the target to the Shared Objects page group and reimport it.
WWU-52327: The source style %1 belongs to a local page group. The same style on the target was promoted to the Shared Objects page group.
Cause: The source style belongs to a local page group, while the target style has been promoted to the Shared Objects page group.
Action: Promote the local style on the source to the Shared Objects page group and reimport it.
WWU-52328: The unique identifier of the source style %1 does not match the target style %1.
Cause: A different style on the target uses the same name as the source style.
Action: Delete the style on the target and reimport the source style.
WWU-52329: The source style %1 exists on the target with a different name. The target style cannot be reused.
Cause: The style name has been changed on the source or on the target.
Action: Either import the style in overwrite mode, or make the names the same on the source and the target.
WWU-52330: The source item type %1 exists on the target with a different name. The target item type cannot be reused.
Cause: The item type's name has been changed on the source or on the target.
Action: Either import the item type in overwrite mode, or make the names the same on the source and the target.
WWU-52331: The Type or unique identifier of the source item type %1 does not match the target item type %1.
Cause: A different item type on the target uses the same name as the item type on the source.
Action: Delete the item type on the target and reimport it.
WWU-52332: The source item type %1 was promoted to the Shared Objects page group. The same item type on the target belongs to a local page group.
Cause: The source item type has been promoted to the Shared Objects page group, while the target item type belongs to a local page group.
Action: Promote the local item type on the target to the Shared Objects page group and reimport it.
WWU-52333: The source item type %1 belongs to a local page group. The same item type on the target has been promoted to the Shared Objects page group.
Cause: The source item type belongs to a local page group, while the target item type has been promoted to the Shared Objects page group.
Action: Promote the local item type on the source to the Shared Objects page group and reimport it.
WWU-52334: The source page type %1 exists on the target with a different name. The target page type cannot be reused.
Cause: The page type's name has been changed on the source or on the target.
Action: Either import the page type in overwrite mode, or make the names the same on both the source and the target.
WWU-52335: The Type or unique identifier of the source page type %1 does not match the target page type %1.
Cause: A different page type on the target uses the same name.
Action: Delete the page type on the target and reimport it.
WWU-52336: The source page type %1 has been promoted to the Shared Objects page group. The same page type on the target belongs to a local page group.
Cause: The source page type has been promoted to the Shared Objects page group, while the target page type belongs to a local page group.
Action: Promote the local page type on the target to the Shared Objects page group and reimport it.
WWU-52337: The source page type %1 belongs to a local page group. The same page type on the target has been promoted to the Shared Objects page group.
Cause: The source page type belongs to a local page group, while the target page type has been promoted to the Shared Objects page group.
Action: Promote the local page type on the source to the Shared Objects page group and reimport it.
WWU-52338: The portlet instance with unique identifier (portlet_inst_guid): %1 will be deleted from the page in the transport set because it has a dependency that does not exist on the target.
Cause: The portlet's dependency, such as its page, Web Provider, Database Provider, or so on, does not exist on the target.
Action: Promote the portlet's dependency to the transport set in the source and reimport it. If the dependency is a Web Provider, register it on the target to make the portlet available in the Portlet Repository.
WWU-52339: An unexpected error occurred while extracting an HTML template's data into its corresponding transport tables.
Cause: An unexpected error occurred while extracting an HTML template's metadata.
Action: The HTML template's metadata will not be extracted, so the import may result in errors. Contact Oracle Support Services and provide the logs obtained.
WWU-52340: An unexpected error occurred while importing the HTML template with the unique identifier %1, in the page group with identifier %2.
Cause: An unexpected error occurred while importing an HTML template.
Action: Contact Oracle Support Services and provide the logs obtained.
WWU-52454: An unexpected error has occurred. Verify the log in debug mode, which provides detailed error messages.
Cause: An unexpected error occurred while importing the access related information.
Action: Contact Oracle Support Services and provide the logs obtained.
WWU-52463: You do not have permission to %0 ACLs on %1.
Cause: You do not have sufficient privileges to manage the ACLs of the listed object.
Action: Ask the Portal Administrator to grant you the required privileges. Try to reimport after the privileges have been granted.
WWU-52464: Unable to resolve %0 external application on the target OracleAS Portal.
Cause: Either the listed external application does not exist in the target OracleAS Single Sign-On, or there are multiple external applications with this name.
Action: Check the external application in the target OracleAS Single Sign-On. Create the application if it does not exist. Otherwise, check for external applications with duplicate names. Note that names of external applications are case in-sensitive. Delete any redundant external applications. Reimport after taking one of these corrective actions.
WWU-52465: Name not updated for object type: %0, object name: %1.
Cause: The object list has not been updated with the mapping name while importing.
Action: Contact Oracle Support Services and provide the logs obtained.
WWU-52501: Initialization of component(ID : %1 Name : %2) failed.
Cause: An unexpected error occurred while calculating the dependencies of the object.
Action: Retry the import. If the retry fails, contact Oracle Support Services.
WWU-52567: Import of %1 failed.
Cause: The import failed for the object in the transport set.
Action: Retry the import. If the retry fails, contact Oracle Support Services.
WWU-52571: Warning : Import of color %1 failed.
Cause: An unexpected error occurred while creating the color on the target.
Action: Retry the import. If the retry fails, contact Oracle Support Services.
WWU-52572: Warning : Import of font %1 failed.
Cause: An unexpected error occurred while creating the font on the target.
Action: Retry the import. If the retry fails, contact Oracle Support Services.
WWU-52573: Warning : Import of image %1 failed.
Cause: An unexpected error occurred while creating the image on the target.
Action: Retry the import. If the retry fails, contact Oracle Support Services.
WWU-52574: Warning : Import of template %1 failed.
Cause: An unexpected error occurred while creating the template on the target.
Action: Retry the import. If the retry fails, contact Oracle Support Services.
WWU-52594: The DB Provider schema %1 does not have EXECUTE privileges on the OracleAS Portal packages used by the DB Provider portlets.
Cause: The EXECUTE privilege on OracleAS Portal packages, used by the portlets, was not granted to the DB Provider schema.
Action: Grant the EXECUTE privilege on OracleAS Portal packages to the DB Provider schema using the script provsyns.sql.
WWU-52595: The schema %1 does not exist in this database instance.
Cause: The schema, that a Portal DB Provider, being imported in the current import operation, uses, was not found in this database instance.
Action: Create the schema in this database instance and grant the CONNECT and RESOURCE roles to it.
WWU-52872: Mapping not found for Page ID %1 and Page Group ID %2.
Cause: There is a dependency on the specified page and page group, and neither exist on the target.
Action: Promote the specified page/page group to the transport set in the source, and reimport it. If the import still fails, contact Oracle Support Services.
WWU-52883: Transport set name cannot be NULL.
Cause: No name has been specified for the transport set.
Action: Specify a name for the transport set.
WWU-52884: Transport set %1 has already been exported and is now available for import.
Cause: The transport set has already been exported.
Action: If the export was successful, the transport set can now be used for import.
WWU-52885: Transport set %1 has not yet been exported and is therefore unavailable for import.
Cause: The transport set has not been exported.
Action: Export the transport set.
WWU-52886: Transport set %1 does not exist.
Cause: The transport set was not found on the server.
Action: Verify that the transport set name was entered correctly. You may need to re-create the transport set.
WWU-52887: Transport set %1 is currently unavailable for either export or import. See the transport set for more details.
Cause: The transport set status is neither EXTRACT_COMPLETE nor AVAILABLE.
Action: Browse the list of transport sets to determine the status.
WWU-52888: Multiple matches found for transport set %1. Choose the one you want from the LOV.
Cause: More than one transport set with the same name was found.
Action: Use the user/timestamp on the list of values to identify the transport set you want.
WWU-52889: Transport set %1 is not available for adding more objects.
Cause: The transport set is not available because it has already been exported or imported.
Action: Browse the list of transport sets to determine the status.
WWU-52926: Transport set %1 does not contain any objects.
Cause: The transport set is empty.
Action: To access the transport set, add at least one object to it.
WWU-52927: Logged-in user %1 does not have MANAGE privilege on any transport set and therefore cannot perform this action.
Cause: You do not appear to have MANAGE privilege on any transport sets.
Action: Ask your portal administrator to assign you this privilege.
WWU-52969: Transport set does not exist. Cannot precheck search preferences.
Cause: Search preferences cannot be prechecked because the specified transport set does not exist.
Action: Verify the transport set name, or re-create the transport set.
WWU-52970: Could not obtain transport set information. Cannot precheck search preferences.
Cause: Search preferences cannot be prechecked because information about the given transport set could not be obtained.
Action: Verify the transport set name, or re-create the transport set.
WWU-52971: Cannot obtain search preference with ID %1 from system table.
Cause: The preference for a search portlet marked for export does not exist in the system tables.
Action: Contact Oracle Support Services.
WWU-52972: An error occurred when performing export precheck of search portlet preferences.
Cause: An unexpected error occurred while prechecking search preferences prior to export.
Action: Check that the customizations for the search portlets you are exporting are valid.
WWU-52973: An error occurred when exporting system preferences for search portlets.
Cause: The exporting of search preferences has failed.
Action: Contact Oracle Support Services.
WWU-52974: Transport set does not exist. Cannot export search preferences.
Cause: The specified transport set does not exist. Exporting of search preferences cannot continue.
Action: Verify the transport set name, or re-create the transport set.
WWU-52975: Could not obtain transport set information. Cannot export search preferences.
Cause: Cannot export search preferences because could not obtain information about the given transport set.
Action: Verify the transport set name, or re-create the transport set.
WWU-52976: Exception occurred while exporting search portlet preferences.
Cause: An unexpected error occurred while attempting to export search portlet preferences.
Action: Contact Oracle Support Services.
WWU-52977: Generating dependencies from search portlet preferences has failed. The transport set will not be valid for importing.
Cause: The dependencies in the search portlet preferences to be exported could not be obtained.
Action: Contact Oracle Support Services.
WWU-52978: An error occurred while generating search portlet dependencies.
Cause: The dependencies in the search portlet preferences to be exported could not be obtained.
Action: Contact Oracle Support Services.
WWU-52979: Exception occurred during search precheck.
Cause: An unexpected error occurred while prechecking search preferences.
Action: Contact Oracle Support Services.
WWU-52980: An error occurred while marking an object in the transport set.
Cause: An error occurred while marking a search portlet preference dependency included in the transport set.
Action: Contact Oracle Support Services.
WWU-52981: Exception occurred while setting the page as failed precheck.
Cause: An unexpected error occurred while attempting to mark a page as failed precheck.
Action: Contact Oracle Support Services.
WWU-52982: There was an error in checking dependencies. Dependencies contained in search preferences did not exist in dependency table.
Cause: Dependencies in the search preferences are not in the search dependency table.
Action: Contact Oracle Support Services.
WWU-52983: Error occurred checking for missing dependencies.
Cause: An unexpected error occurred while checking if a search preference has missing dependencies.
Action: Contact Oracle Support Services.
WWU-52984: Cannot obtain new IDs from target tables. Cannot proceed with search precheck.
Cause: An error occurred while attempting to get the ID of an object in the target tables.
Action: Contact Oracle Support Services.
WWU-52985: Precheck cannot continue because inconsistent data was found in dependency table and search transport table.
Cause: The information in the search preferences does not match information in the search dependency table.
Action: Contact Oracle Support Services.
WWU-52986: Exception occurred resolving search portlet preferences.
Cause: An unexpected error occurred while attempting to resolve search preference information.
Action: Contact Oracle Support Services.
WWU-52987: Exception occurred resolving search portlet preference import actions.
Cause: An unexpected error occurred while attempting to determine the import action of search portlet preferences.
Action: Contact Oracle Support Services.
WWU-52988: Exception occurred resolving search portlet preference reference paths.
Cause: An unexpected error occurred while attempting to resolve a search portlet's reference path.
Action: Contact Oracle Support Services.
WWU-52989: An error occurred getting object information from the object path. Object type does not exist.
Cause: The object type of a search preference dependency is not valid.
Action: Contact Oracle Support Services.
WWU-52990: Exception occurred while updating dependency table with new IDs from the object path.
Cause: An unexpected error occurred while attempting to update the dependency table with the new IDs.
Action: Contact Oracle Support Services.
WWU-52991: Exception occurred while determining IDs from the target tables.
Cause: An unexpected error occurred when attempting to obtain the ID of a search preference dependency from the target tables.
Action: Contact Oracle Support Services.
WWU-52992: Exception occurred while determining IDs from the transport tables.
Cause: An unexpected error occurred when attempting to obtain the ID of a search preference dependency from the transport tables.
Action: Contact Oracle Support Services.
WWU-52993: Exception occurred while resolving dependency IDs.
Cause: An unexpected error occurred while attempting to determine the new IDs of search preference dependencies.
Action: Contact Oracle Support Services. search import.
WWU-52994: Exception occurred while importing search portlet preferences.
Cause: An unexpected error occurred when attempting to import search portlet preferences.
Action: Contact Oracle Support Services.
WWU-52995: Exception occurred while inserting new search portlet preferences.
Cause: An unexpected error occurred when attempting to insert new search portlet preferences into the target tables.
Action: Contact Oracle Support Services.
WWU-52996: Error populating search dependency table with page group objects.
Cause: An unexpected error occurred when obtaining the page group dependencies from the search portlets being exported.
Action: Contact Oracle Support Services.
WWU-52997: An error occurred while populating search dependency table with image objects.
Cause: An unexpected error occurred when obtaining the image dependencies from the search portlets being exported.
Action: Contact Oracle Support Services.
WWU-52998: An error occurred while populating search dependency table with style objects.
Cause: An unexpected error occurred when obtaining the style dependencies from the search portlets being exported.
Action: Contact Oracle Support Services.
WWU-52999: An error occurred while populating search dependency table with attribute objects.
Cause: An unexpected error occurred when obtaining the attribute dependencies from the search portlets being exported.
Action: Contact Oracle Support Services.
WWU-74000: An error occurred while populating search dependency table with item type objects.
Cause: An unexpected error occurred when obtaining the item type dependencies from the search portlets being exported.
Action: Contact Oracle Support Services.
WWU-74001: Efforts to determine the page path have failed. Object not found.
Cause: An unexpected error occurred while obtaining the path of the page selected to display search results. The page cannot be found.
Action: Contact Oracle Support Services.
WWU-74002: Efforts to determine the page path have failed. Language not found.
Cause: An unexpected error occurred while obtaining the path of the page selected to display search results. The language cannot be found.
Action: Contact Oracle Support Services.
WWU-74003: Efforts to determine the page path have failed due to invalid domain.
Cause: An unexpected error occurred while obtaining the path of the page selected to display search results. The domain is invalid.
Action: Contact Oracle Support Services.
WWU-74004: Efforts to determine the page path have failed due to invalid object type.
Cause: An unexpected error occurred while obtaining the path of the page selected to display search results. The object type is invalid.
Action: Contact Oracle Support Services.
WWU-74005: An error occurred while populating search dependency table with page objects.
Cause: An unexpected error occurred while obtaining the page dependencies from the search portlets being exported.
Action: Contact Oracle Support Services.
WWU-74006: Efforts to determine the category path have failed because the category was not found.
Cause: An unexpected error occurred while obtaining the path of the category selected as search criteria. The category cannot be found.
Action: Contact Oracle Support Services.
WWU-74007: Efforts to determine the category path have failed because the language was not found.
Cause: An unexpected error occurred while obtaining the path of the category selected as search criteria. The language cannot be found.
Action: Contact Oracle Support Services.
WWU-74008: Efforts to determine the category path have failed due to invalid domain.
Cause: An unexpected error occurred while obtaining the path of the category selected as search criteria. The domain is invalid.
Action: Contact Oracle Support Services.
WWU-74009: Efforts to determine the category path have failed due to invalid object type.
Cause: An unexpected error occurred while obtaining the path of the category selected as search criteria. The object type is invalid.
Action: Contact Oracle Support Services.
WWU-74010: An error occurred while populating the search dependency table with category objects.
Cause: An unexpected error occurred while obtaining the category dependencies from the search portlets being exported.
Action: Contact Oracle Support Services.
WWU-74011: Efforts to determine the perspective path have failed because the object was not found.
Cause: An unexpected error occurred while obtaining the path of the perspective selected as search criteria. The object cannot be found.
Action: Contact Oracle Support Services.
WWU-74012: Efforts to determine the perspective path have failed because the language was not found.
Cause: An unexpected error occurred while obtaining the path of the perspective selected as search criteria. The language cannot be found.
Action: Contact Oracle Support Services.
WWU-74013: Efforts to determine the perspective path have failed due to invalid domain.
Cause: An unexpected error occurred while obtaining the path of the perspective selected as search criteria. The domain is invalid.
Action: Contact Oracle Support Services.
WWU-74014: Efforts to determine the perspective path have failed due to invalid object type.
Cause: An unexpected error occurred while obtaining the path of the perspective selected as search criteria. The object type is invalid.
Action: Contact Oracle Support Services.
WWU-74015: An error occurred while populating the search dependency table with perspective objects.
Cause: An unexpected error occurred while obtaining the perspective dependencies from the search portlets being exported.
Action: Contact Oracle Support Services.
WWU-74017: An error occurred when attempting to clean up search preferences.
Cause: An unexpected error occurred while removing dangling references from the preferences of the search portlets being exported.
Action: Contact Oracle Support Services.
WWU-74019: Copying data from source tables to transport tables failed.
Cause: An unexpected error occurred while copying preferences of the search portlets being exported from the source table to the transport table.
Action: Contact Oracle Support Services.
WWU-74021: The page on which portlet resides does not exist.
Cause: Obtaining the page on which the search portlet resides failed because the page does not exist in the transport set.
Action: Contact Oracle Support Services.
WWU-74022: Too many pages were returned when attempting to determine the page on which the portlet resides.
Cause: Obtaining the page on which the search portlet resides failed because too many pages were returned from the query.
Action: Contact Oracle Support Services.
WWU-74023: An error occurred getting the ID of the page object that contains the search portlet.
Cause: An unexpected error occurred when attempting to get the object ID of the page on which the search portlet resides.
Action: Contact Oracle Support Services.
WWU-74024: Checking page group dependencies failed.
Cause: An unexpected error occurred while checking if the page groups selected in search portlet customizations will exist in the target after import.
Action: Contact Oracle Support Services.
WWU-74025: Checking image dependencies failed.
Cause: An unexpected error occurred while checking if the images selected in search portlet customizations will exist in the target after import.
Action: Contact Oracle Support Services.
WWU-74026: Checking style dependencies failed.
Cause: An unexpected error occurred while checking if the styles selected in search portlet customizations will exist in the target after import.
Action: Contact Oracle Support Services.
WWU-74027: Checking page dependencies failed.
Cause: An unexpected error occurred while checking if the pages selected in search portlet customizations will exist in the target after import.
Action: Contact Oracle Support Services.
WWU-74028: Checking submission attributes dependencies failed.
Cause: An unexpected error occurred while checking if the submission attributes selected in search portlet customizations will exist in the target after import.
Action: Contact Oracle Support Services.
WWU-74029: Checking item type attribute default value failed.
Cause: An unexpected error occurred while checking to see if the item types selected in the search portlet customizations will exist in the target after import.
Action: Contact Oracle Support Services.
WWU-74030: Checking category attribute default value failed.
Cause: An unexpected error occurred while checking to see if the categories selected in the search portlet customizations will exist in the target after import.
Action: Contact Oracle Support Services.
WWU-74031: Checking perspective attribute default value failed.
Cause: An unexpected error occurred while checking to see if the perspectives selected in the search portlet customizations will exist in the target after import.
Action: Contact Oracle Support Services.
WWU-74032: Checking results attributes dependencies failed.
Cause: An unexpected error occurred while checking to see if the results attributes selected in the search portlet customizations will exist in the target after import.
Action: Contact Oracle Support Services.
WWU-74034: Resolving results page dependencies failed.
Cause: An unexpected error occurred while replacing source IDs with target IDs for the results page option in the search portlet customizations.
Action: Contact Oracle Support Services.
WWU-74035: Resolving image dependencies failed.
Cause: An unexpected error occurred while replacing source IDs with target IDs for the image option in the search portlet customizations.
Action: Contact Oracle Support Services.
WWU-74036: Resolving style dependencies failed.
Cause: An unexpected error occurred while replacing source IDs with target IDs for the style option in the search portlet customizations.
Action: Contact Oracle Support Services.
WWU-74037: Resolving page groups dependencies failed.
Cause: An unexpected error occurred while replacing source IDs with target IDs for the page group option in the search portlet customizations.
Action: Contact Oracle Support Services.
WWU-74038: Exception occurred while resolving default values identified by a pair of IDs.
Cause: An unexpected error occurred while replacing source IDs with target IDs for attributes in the search portlet customizations, where the default values are objects in the portal.
Action: Contact Oracle Support Services.
WWU-74039: Exception occurred while resolving default values identified by a set of ID pairs.
Cause: An unexpected error occurred while replacing source IDs with target IDs for attributes in the search portlet customizations, where the default values are objects in the portal.
Action: Contact Oracle Support Services.
WWU-74040: Resolving submission attributes dependencies failed.
Cause: An unexpected error occurred while replacing source IDs with target IDs for the submission attributes option in the search portlet customizations.
Action: Contact Oracle Support Services.
WWU-74041: Resolving display attributes dependencies failed.
Cause: An unexpected error occurred while replacing source IDs with target IDs for the display attributes option in the search portlet customizations.
Action: Contact Oracle Support Services.
WWU-74043: Cannot resolve search preferences because the transport set does not exist.
Cause: The search preferences for the portlets being imported cannot be resolved because the transport set does not exist.
Action: Contact Oracle Support Services.
WWU-74044: Could not resolve search preferences because the transport set information could not be obtained.
Cause: The search preferences for the portlets being imported cannot be resolved because the transport set information cannot be obtained.
Action: Contact Oracle Support Services.
WWU-74045: Exception occurred while updating existing search portlet preferences.
Cause: An unexpected error occurred while the preferences for the search portlets being imported were being updated.
Action: Contact Oracle Support Services.
WWU-74047: Could not import search preferences because the transport set does not exist.
Cause: The search preferences for the portlets being imported cannot be imported because the transport set does not exist.
Action: Contact Oracle Support Services.
WWU-74048: Could not import search preferences because transport set information could not be obtained.
Cause: The search preferences for the portlets being imported cannot be imported because the transport set information cannot be obtained.
Action: Contact Oracle Support Services.
WWU-74062: Error resolving search portlet translations.
Cause: An unexpected error occurred while resolving translations of search portlet preferences.
Action: Contact Oracle Support Services.
WWU-74063: Error resolving search portlet string preferences.
Cause: An unexpected error occurred whilst the translations of search string preferences were being resolved, with the languages that exist in the target portal.
Action: Contact Oracle Support Services.
WWU-74066: Error populating the search mapping table with page group objects.
Cause: An unexpected error occurred while attempting to obtain page group dependencies for the search items to be exported.
Action: Contact Oracle Support Services.
WWU-74071: Error resolving pages to be searched.
Cause: An unexpected error occurred while replacing source IDs with target IDs for the pages that are defined within search portlet customizations; that is, pages defined using the 'Search-In' option.
Action: Contact Oracle Support Services.
WWU-74072: Check for missing pages failed.
Cause: An unexpected error occurred while checking if the page groups selected in search item customizations will exist in the target after import.
Action: Contact Oracle Support Services.
WWU-74100: Page %1 of the page group with unique identifier %2 applies the user's default style. The default style of the user on the target will be used.
Cause: The page group is using a user default style.
Action: The default style of the user on the target will be used. Or bring the source user's default style on the target and associate it with the user.
WWU-74101: Unable to find data for the attribute with unique identifier %1 and page group identifier %2. An attempt to import this transport set could result in errors.
Cause: Data was not found for the specified attribute in the specified page group. The export proceeded without the attribute. An attempt to import the resulting transport set could result in errors. This is a data inconsistency issue in the base system, possibly in the itemtype or pagetype attribute association table.
Action: Contact Oracle Support Services, and provide the export logs.
WWU-74102: Multiple records were found while obtaining the metadata of the attribute with unique identifier %1 and page group identifier %2. An attempt to import this transport set could result in errors.
Cause: An unexpected error occurred while obtaining attribute metadata. The export will proceed without the attribute. An attempt to import the resulting transport set could result in errors. This error may indicate a data inconsistency issue in the base system, possibly in the attribute metadata table.
Action: Contact Oracle Support Services and provide the export logs.
WWU-74103: Unable to add the attribute with unique identifier %1 and page group identifier %2. An attempt to import this transport set could result in errors.
Cause: An unexpected error occurred while adding the specified attribute. The export proceeded without the attribute. An attempt to import the resulting transport set could result in errors.
Action: Contact Oracle Support Services, and provide the export logs.
WWU-74104: Multiple records were found while getting the page type of the page %1 in the page group with unique identifier %2. An attempt to import this transport set could result in errors.
Cause: An unexpected error occurred while obtaining the page type. The export will proceed without the type. An attempt to import the resulting transport set could result in errors. This error may indicate a data inconsistency issue in the base system, possibly in the pagetype metadata table.
Action: Contact Oracle Support Services, and provide the export logs.
WWU-74105: No page type definition found for page %1 in the page group with unique identifier %2. An attempt to import this transport set could result in errors.
Cause: An unexpected error occurred while obtaining the page type definition. The export proceeded without the page type definition. An attempt to import the resulting transport set could result in errors. This is a data inconsistency issue in the base system. The page table contains a inconsistent pagetype entry.
Action: Contact Oracle Support Services, and provide the resulting logs.
WWU-74106: Cannot add the page type of page %1 in the page group with unique identifier %2. An attempt to import this transport set could result in errors.
Cause: An unexpected error occurred while adding the page type metadata. The export will proceed without the page type metadata. An attempt to import the resulting transport set could result in errors.
Action: Contact Oracle Support Services, and provide the export logs.
WWU-74107: No item type definition found for item %1 in page group with unique identifier %2. An attempt to import this transport set could result in errors.
Cause: An unexpected error occurred while obtaining the item type definition. The export proceeded without the item type. An an attempt to import the resulting transport set could result in errors. This is a data inconsistency issue in the base system. A inconsistent itemtype entry is present in the item table.
Action: Contact Oracle Support Services, and provide the export logs.
WWU-74108: Multiple records were found while obtaining the item type of item %1 in the page group with unique identifier %2. An attempt to import this transport set could result in errors.
Cause: An unexpected error occurred while obtaining the specified item type. The export proceeded without the item type. An attempt to import the resulting transport set could result in errors. This may be a data inconsistency issue in the base system, possibly in the itemtype metadata table.
Action: Contact Oracle Support Services, and provide the export logs.
WWU-74109: Unable to add the item type of item %1 in the page group with unique identifier %2. An attempt to import this transport set could result in errors.
Cause: An unexpected error occurred while adding the item type. The export will proceed without the item type metadata. An attempt to import the resulting transport set could result in errors.
Action: Contact Oracle Support Services, and provide the export logs.
WWU-74110: Multiple records were found while obtaining the category of page %1 in the page group with unique identifier %2. An attempt to import this transport set could result in errors.
Cause: An unexpected error occurred while getting the specified category. The export proceeded without the category. An attempt to import the resulting transport set could result in errors. This error may indicate a data inconsistency issue in the base system, possibly in the category metadata table.
Action: Contact Oracle Support Services, and provide the export logs.
WWU-74111: Unable to add the category of page %1 in the page group with unique identifier %2. An attempt to import this transport set could result in errors.
Cause: An unexpected error occurred while adding the category. The export will proceed without the category metadata. An attempt to import the resulting transport set could result in errors.
Action: Contact Oracle Support Services, and provide the export logs.
WWU-74112: Cannot find the perspective with the unique identifier %1 and page group identifier %2. An attempt to import this transport set could result in errors.
Cause: An unexpected error occurred while getting the specified perspective. The export proceeded without the perspective. An attempt to import the resulting transport set could result in errors. This is a data inconsistency issue in the base system. An inconsistent perspective entry is present in the item or page perspective association tables.
Action: Contact Oracle Support Services.
WWU-74113: Multiple records were found while obtaining the perspective with the unique identifier %1 and page group identifier %2. An attempt to import this transport set could result in errors.
Cause: An unexpected error occurred while obtaining the specified perspective. The export proceeded without the perspective. An attempt to use the resulting transport set could result in errors. This error may indicate a data inconsistency issue in the base system, possibly in the perspective metadata table.
Action: Contact Oracle Support Services.
WWU-74114: Unable to add the perspective with the unique identifier %1 and page group identifier %2. An attempt to import this transport set could result in errors.
Cause: An unexpected error occurred while adding the perspective. The export will proceed without the perspective. An attempt to import the resulting transport set could result in errors.
Action: Contact Oracle Support Services, and provide the export logs.
WWU-74115: Multiple records were found while obtaining the style of the page %1 with page group identifier %2. An attempt to import this transport set could result in errors.
Cause: An unexpected error occurred while obtaining the style of the specified page. The export proceeded without the style. Import of the resulting transport set could result in errors. This error may indicate a data inconsistency issue in the base system, possibly in the style metadata table.
Action: Contact Oracle Support Services.
WWU-74116: Unable to add the style of the page %1 with page group identifier %2. An attempt to import this transport set could result in errors.
Cause: An unexpected error occurred while adding the style. The export will proceed without the style. An attempt to import the resulting transport set could result in errors.
Action: Contact Oracle Support Services, and provide the export logs.
WWU-74117: Cannot find record for the external application with the unique identifier %1. Portlets based on this application will get lost on import.
Cause: The specified external application was not found. The export will proceed without the dependencies. If the resulting transport set is imported, portlets that are dependent on this application will not be found. This error may indicate a data inconsistency issue in the base system. For example, there may be a inconsistent external application entry in the provider table.
Action: Contact Oracle Support Services.
WWU-74118: Multiple records were found while obtaining the details of external application with the unique identifier %1. Portlets based on this application will get lost during import.
Cause: An unexpected error occurred while obtaining the details of the specified external application. The export proceeded without the dependencies. If the resulting transport set is imported, the portlets that are dependent on this application will not be found. This error may indicate a data inconsistency issue in the base system, possibly in the external application table.
Action: Contact Oracle Support Services.
WWU-74119: Unable to add the external application dependency with the unique identifier %1. Portlets based on this application will get lost on import.
Cause: An unexpected error occurred while adding the external application dependency. The export proceeded without the dependency. If the resulting transport set is imported, portlets that are dependent on this application will not be found.
Action: Contact Oracle Support Services, and provide the export logs.
WWU-74120: Cannot find the page group with unique identifier %1, in which the portlet was exposed as shared. An attempt to import this transport set could result in errors.
Cause: The page group where the portlet is exposed as shared could not be found. The export proceeded without the page group. If the resulting transport set is imported, the portlet could be lost. This may be a data inconsistency issue in the base system, possibly in the portlet instance table. For example, the shared portlet instance entry may have a wrong pgrp identifier.
Action: Contact Oracle Support Services.
WWU-74121: Unable to add the dependencies of generic page portlet with the unique identifier %1 and page group identifier %2. An attempt to import this transport set could result in errors.
Cause: An unexpected error occurred while adding the dependencies of the generic page portlet. The export proceeded without the dependencies. If the resulting transport set is imported, the generic page portlet could result in errors.
Action: Contact Oracle Support Services, and provide the export logs.
WWU-74122: Cannot find the definition of the DB Provider component that is exposed as the portlet with unique identifier %1. Portlets based on this component will get lost upon import.
Cause: Could not find the definition of the specified DB Provider exposed as a portlet. The export proceeded without the portlet definition. If the resulting transport set is imported, portlets based on this component will get lost upon import. This error may indicate a data inconsistency issue in the base system. For example, the wrong portlet ID information may be stored in the portlet instance table.
Action: Contact Oracle Support Services.
WWU-74123: Cannot find details for the provider with the unique identifier %1. An attempt to import this transport set could result in errors.
Cause: No data was found while obtaining the provider definition. The export will proceed without it. An attempt to import the resulting transport set could result in errors, possibly the loss of the portlets owned by this provider. This error may indicate a data inconsistency issue in the base system. For example, a inconsistent provider entry may be stored in the portlet instance table.
Action: Contact Oracle Support Services.
WWU-74124: Multiple records were encountered while obtaining details for the provider with unique identifier %1. An attempt to import this transport set could result in errors.
Cause: An unexpected error occurred while getting the provider definition. The export proceeded without it. An attempt to import the resulting transport set could result in errors, possibly the loss of this provider's portlets. This error may indicate a data inconsistency issue in the base system, possibly in the provider metadata table.
Action: Contact Oracle Support Services.
WWU-74125: No data was found while obtaining the provider associated with the page group with unique identifier %1. An attempt to import this transport set could result in errors.
Cause: An unexpected error occurred while obtaining the specified provider. The export proceeded without the provider definition. An attempt to import the resulting transport set could result in errors. For example, the navigation page portlets dependent on this provider could be lost. This error may indicate a data inconsistency issue in the base system, possibly in the page group table or the provider metadata table.
Action: Contact Oracle Support Services.
WWU-74126: No data was found while obtaining the page with unique identifier %1 and page group %2. This page is a page-link dependency of another page. The page link will get lost on import.
Cause: An unexpected error occurred while obtaining the specified page. This page is a page-link dependency of another page. The export will proceed without the page link. An attempt to import the resulting transport set will result in errors, including the loss of the page link. This error may indicate a data inconsistency issue in the base system. For example, inconsistent page link entries may be present in the page table.
Action: Contact Oracle Support Services.
WWU-74127: Unable to get the page with unique identifier %1 and page group %2. This page is page-link dependency of another page. The page link will get lost on import.
Cause: An unexpected error occurred while adding the page link dependency. The export proceeded without the page link dependency definition. An attempt to import the resulting transport set will result in errors, most likely because the page link will get lost.
Action: Contact Oracle Support Services, and provide the export logs.
WWU-74128: Cannot find the template metadata with unique identifier %1 and page group %2. Import of this transport set could result in errors for pages based on this template.
Cause: An unexpected error occurred while obtaining the specified template metadata. The export proceeded without the template. Importing the resulting transport set could result in errors for any pages that are based on the specified template. This may a data inconsistency issue in the base system. For example, the page table may contain a inconsistent template entry.
Action: Contact Oracle Support Services.
WWU-74129: Multiple records were found while obtaining the template metadata with unique identifier %1 and page group %2. Importing this transport set could result in errors for pages based on this template.
Cause: An unexpected error occurred while obtaining the specified template's metadata. The export proceeded without the template. Importing the resulting transport set could result in errors for pages based on this template. This error may indicate a data inconsistency issue in the base system, possibly in the template metadata table.
Action: Contact Oracle Support Services.
WWU-74132: Unable to get the UI template %1 of schema %2 associated with the given page.
Cause: An unexpected error occurred while adding the specified UI template. The export proceeded without the template. Importing the resulting transport set could result in broken connections between pages and their related UI templates.
Action: Contact Oracle Support Services, and provide the export logs.
WWU-74133: Unable to get the dependencies associated with the page %1. Import this transport set could result in errors for this page.
Cause: An unexpected error occurred while adding the dependencies associated with the page. The export proceeded without the page dependencies. Importing the resulting transport could result in errors for this page.
Action: Contact Oracle Support Services, and provide the export logs.
WWU-74134: Unable to get the default settings of the page group with unique identifier %1. Some of the default settings could be lost on import.
Cause: An unexpected error occurred while adding the specified page group's default settings. The export proceeded without them. Importing the resulting transport set could result in loss of the page group's default settings.
Action: Contact Oracle Support Services, and provide the export logs.
WWU-74135: Unable to add the page group with unique identifier %1 as an external dependency. An attempt to import this transport set could result in errors.
Cause: An unexpected error occurred while adding the page group as an external dependency. The export proceeded without it. Importing the resulting transport set could result in errors attributable to the omitted page group.
Action: Contact Oracle Support Services, and provide the export logs.
WWU-74136: Unable to add the category with unique identifier %1 of the page group %2 as an external dependency. Import of this transport set could result in errors.
Cause: An unexpected error occurred while adding the category as an external dependency. The export proceeded without adding the category. Importing the resulting transport set could result in errors for any children of the omitted category.
Action: Contact Oracle Support Services, and provide the export logs.
WWU-74137: Unable to add the perspective with unique identifier %1 of the page group %2 as an external dependency. Import of this transport set could result in errors.
Cause: An unexpected error occurred while adding the perspective as an external dependency. The export proceeded without the perspective. Importing the resulting transport set could result in errors for any children of the omitted perspective.
Action: Contact Oracle Support Services, and provide the export logs.
WWU-74138: Unable to add the page with unique identifier %1 of the page group %2 as an external dependency. Import of this transport set could result in errors.
Cause: An unexpected error occurred while adding the page as an external dependency. The export proceeded without the page. Importing the resulting transport set could result in errors for any children of the omitted page.
Action: Contact Oracle Support Services, and provide the export logs.
WWU-74139: Unable to add the color %1. The components using this color that are imported from this transport set will use the default color that is specified for like components on the target.
Cause: An unexpected error occurred while adding the specified color. The export proceeded without the color metadata. All the components in the resulting transport set that used this color will no longer have access to it. On the target, these components will use the default color that is specified for like components. This error may indicate a data inconsistency issue in the base system.
Action: As a workaround, after importing this transport set, bring in the associated color and re-associate it with the relevant components. Before proceeding with the import of this transport set, consult the Export/Import section of the Portal Configuration Guide for additional information on object behavior.
WWU-74140: Unable to add the font %1. The components that use this font that are imported from this transport set will use the default font that is specified for like components on the target.
Cause: An unexpected error occurred while adding font. The export proceeded without the font metadata. If the resulting transport set contains components that used this font, on import they will use the default font specified on the target. This error may indicate a data inconsistency issue in the base system.
Action: As a workaround, after importing this transport set, bring in the associated font and re-associate it with the relevant components. Before proceeding with the import of this transport set, consult the Export/Import section of the Portal Configuration Guide for additional information on object behavior.
WWU-74141: Unable to add the image %1. The components in this transport set that use this image will use the target's default image instead. The default image is often an X, indicating a broken image.
Cause: An unexpected error occurred while adding the specified image. The export proceeded without the image. Components that used this image that are imported from the resulting transport set will use the target's default image. This error may indicate a data inconsistency issue in the base system.
Action: As a workaround, after importing this transport set, bring in the associated image and re-associate it with the relevant components. Before proceeding with the import of this transport set, consult the Export/Import section of the Portal Configuration Guide for additional information on object behavior.
WWU-74142: Unable to add the JavaScript %1. The components in the transport set that use this script will use the default JavaScript.
Cause: An unexpected error occurred while adding the JavaScript. The export proceeded without it. If the resulting transport set is imported, the components that used this script on the base will use the default JavaScript on the target. This error may indicate a data inconsistency issue in the base system.
Action: As a workaround, after importing this transport set, bring in the associated JavaScript and re-associate it with the relevant components. Before proceeding with the import of this transport set, consult the Export/Import section of the Portal Configuration Guide for additional information on object behavior.
WWU-74143: Unable to add the colors, images, and fonts that are referenced by the template with unique identifier %1. On the target, the template will use the default values of these referenced objects.
Cause: An unexpected error occurred while adding the colors, images, and fonts that are referenced by the template. The export proceeded without the referenced objects. Importing the resulting transport set will result in the use of the target's default values for the referenced objects. This error may indicate a data inconsistency issue in the base system.
Action: As a workaround, after importing this transport set, bring in the associated objects and re-associate them with the template. Before importing this transport set, consult the Export/Import section of the Portal Configuration Guide for additional information on object behavior.
WWU-74144: Unable to add the template %1. This transport set will not contain this template.
Cause: An unexpected error occurred while adding the specified template. The export proceeded without the template. Importing the resulting transport set could result in errors should any objects be dependent upon this template. This error may indicate a data inconsistency issue in the base system.
Action: As a workaround, after importing this transport set, bring in the associated template and re-associate it with the relevant objects. Before importing this transport set, consult the Export/Import section of the Portal Configuration Guide for additional information on object behavior.
WWU-74145: Unable to add the LOV %1. An attempt to import this transport set could result in errors.
Cause: An unexpected error occurred while adding the specified LOV. The export proceeded without the LOV. This error may indicate a data inconsistency issue in the base system.
Action: As a workaround, after importing this transport set, bring in the associated LOV and re-associate it with the relevant objects. Before proceeding with the import of this transport set, consult the Export/Import section of the Portal Configuration Guide for additional information on object behavior.
WWU-74146: Unable to add the link %1. An attempt to import this transport set could result in errors.
Cause: An unexpected error occurred while adding the specified link. The export proceeded without the link. Importing the resulting transport set could result in errors related to objects that use this link. This error may indicate a data inconsistency issue in the base system.
Action: As a workaround, after importing this transport set, bring in the associated link and re-associate it with the relevant objects. Before importing the transport set, consult the Export/Import section of the Portal Configuration Guide for additional information on object behavior.
WWU-74147: Unable to add all the colors. Importing this transport set could result in errors.
Cause: An unexpected error occurred while adding all the colors. The export proceeded without the colors. Importing the resulting transport set could result in the application of undesirable colors to any affected objects. This error may indicate a data inconsistency issue in the base system.
Action: As a workaround, after importing this transport set, bring in the associated color and re-associate it with the relevant objects. Before importing this transport set, consult the Export/Import section of the Portal Configuration Guide for additional information on object behavior.
WWU-74148: Unable to add all the fonts. Importing this transport set could result in errors.
Cause: An unexpected error occurred while adding all the fonts. The export proceeded without the fonts. Importing the resulting transport set could result in the application of undesirable fonts to affected objects. This error may indicate a data inconsistency issue in the base system.
Action: As a workaround, after importing this transport set, bring in the associated fonts and re-associate them with the relevant objects. Before importing this transport set, consult the Export/Import section of the Portal Configuration Guide for additional information on object behavior.
WWU-74150: Unable to add all the images. Import of this transport set could result in errors.
Cause: An unexpected error occurred while adding all the images. The export proceeded without the images. Import of the resulting transport set could result in problems for the objects that use these images. This error may indicate a data inconsistency issue in the base system.
Action: As a workaround, after importing this transport set, bring in the associated images and re-associate them with the relevant objects. Before proceeding with the import of this transport set, consult the Export/Import section of the Portal Configuration Guide for additional information on object behavior.
WWU-74151: Unable to add all the JavaScripts. Import of this transport set could result in errors.
Cause: An unexpected error occurred while adding all the JavaScripts. The export proceeded without these JavaScripts. Importing the resulting transport set could result in problems for the objects that use these JavaScripts. This error may indicate a data inconsistency issue in the base system.
Action: As a workaround, after importing this transport set, bring in the associated JavaScripts and re-associate them with the relevant objects. Before proceeding with the import of this transport set, consult the Export/Import section of the Portal Configuration Guide for additional information on object behavior.
WWU-74152: Unable to add all the templates. An attempt to import this transport set could result in errors.
Cause: An unexpected error occurred while adding all the templates. The export proceeded without these templates. This error may indicate a data inconsistency issue in the base system.
Action: As a workaround, after importing this transport set, bring in the associated templates and re-associate them with the relevant objects. Before proceeding with the import of this transport set, consult the Export/Import section of the Portal Configuration Guide for additional information on object behavior.
WWU-74153: Unable to add the objects referenced by the data component %1. Import of this transport set could result in errors.
Cause: An unexpected error occurred while adding objects referenced by the specified data component. The export proceeded without the referenced objects. Import of the resulting transport set could result in errors. This error may indicate a data inconsistency issue in the base system.
Action: As a workaround, after importing this transport set, bring in the associated objects and re-associate them with the relevant data component. Before proceeding with the import of this transport set, consult the Export/Import section of the Portal Configuration Guide for additional information on object behavior.
WWU-74154: Unable to add the objects referenced by the report %1. Import of this transport set could result in errors.
Cause: An unexpected error occurred while adding objects referenced by the specified report. The export proceeded without the referenced objects. Import of the resulting transport set could result in errors. This error may indicate a data inconsistency issue in the base system.
Action: As a workaround, after importing this transport set, bring in the associated objects and re-associate them with the specified report. Before proceeding with the import of this transport set, consult the Export/Import section of the Portal Configuration Guide for additional information on object behavior.
WWU-74155: Unable to add the objects referenced by the menu link %1. Import of this transport set could result in errors.
Cause: An unexpected error occurred while adding objects referenced by the specified menu link. The export proceeded without the referenced objects. Import of the resulting transport set could result in errors. This error may indicate a data inconsistency issue in the base system.
Action: As a workaround, after importing this transport set, bring in the associated objects and re-associate them with the specified menu link. Before proceeding with the import of this transport set, consult the Export/Import section of the Portal Configuration Guide for additional information on object behavior.
WWU-74156: Unable to add the objects referenced by the application %1.
Cause: An unexpected error occurred while adding objects referenced by the application. The export proceeded without the referenced objects. Import of the resulting transport set could result in errors. This error may indicate a data inconsistency issue in the base system.
Action: As a workaround, after importing this transport set, bring in the associated objects and re-associate them with the specified application. Before proceeding with the import of this transport set, consult the Export/Import section of the Portal Configuration Guide for additional information on object behavior.
WWU-74157: Unable to add the application %1. Import of this transport set could result in errors.
Cause: An unexpected error occurred while adding the specified application. The export proceeded without the application. Import of the resulting transport set could result in errors. This error may indicate a data inconsistency issue in the base system.
Action: As a workaround, after importing this transport set, bring in the associated objects and re-associate them with the specified application. Before proceeding with the import of this transport set, consult the Export/Import section of the Portal Configuration Guide for additional information on object behavior.
WWU-74158: Unable to add the component %1 of type %2 of the application %3. Import this transport set could result in errors.
Cause: An unexpected error occurred while adding the specified component. The export proceeded without the component. Import of the resulting transport set could result in errors. This error may indicate a data inconsistency issue in the base system.
Action: As a workaround, after importing this transport set, bring in the specified component. Before proceeding with the import of this transport set, consult the Export/Import section of the Portal Configuration Guide for additional information on object behavior.
WWU-74159: Unable to add item link dependency of item having unique identifier (id) %1 in pagegroup with identifier %2.
Cause: An unexpected error occurred while extracting item link dependency.
Action: The export will proceed without the dependency. On import, the itemlink item will lose the association. Edit the item link and point to another item or bring the page containing the required item from the source for it to work. Contact Oracle Support Services and provide the logs.
WWU-74160: Unable to add item template dependency having unique identifier %1 with pagegroup identifier %2. The export will proceed without the item template. On import, the item/page configured with the item template will throw run time errors.
Cause: An unexpected error occurred while adding item template dependency.
Action: The export will proceed without the item template dependency.Contact Oracle Support Services and provide the logs.
WWU-74161: Unable to add HTML template dependencies of regions in page with unique identifier %1 in pagegroup with identifier %2. The export will proceed without HTML template dependencies. However the import could result in errors.
Cause: An unexpected error occurred while adding HTML template of region. This could be due to a corrupted HTML template entry in region table.
Action: The export will proceed without HTML template dependencies. Contact Oracle Support Services and provide the logs.
WWU-74162: An unexpected error occurred while adding HTML template dependencies of pagegroup with identifier %1. The export will proceed without them. Import could result in errors for pages/regions using them.
Cause: An unexpected error occurred while adding HTML template dependencies of given pagegroup.
Action: The export will proceed without HTML templates. Contact Oracle Support Services and provide the logs.
WWU-74163: Unable to add item placeholder dependency of item. The configured item has unique identifier %1 in pagegroup with identifier %2.
Cause: An unexpected error occurred while extracting item placeholder dependency.
Action: The export will proceed without the item placeholder dependency. On import, the item placeholder item loses the association. You can edit the item and point it to another item or bring the page containing the required item from the source for it to work. Contact Oracle Support Services and provide the logs.
WWU-74201: The PL/SQL item with the unique identifier %1 will throw a runtime error because the schema %2 associated with it is not present on the target.
Cause: The schema associated with the PL/SQL item does not exist on the target database.
Action: Migrate the schema using the database export/import utilities, and re-associate it with the PL/SQL item.
WWU-74202: The PL/SQL page %1 will throw a runtime error because the schema %2 associated with it is not present on the target. You can migrate the schema later on and re-associate it again.
Cause: The schema does not exist on the target database.
Action: Migrate the schema using the database export/import utilities, and re-associate it with the PL/SQL page.
WWU-74203: The PL/SQL attribute %1 will throw a runtime error because the schema %2 associated with it is not present on the target.
Cause: The schema associated with the PL/SQL attribute does not exist on the target database.
Action: Migrate the schema using the database export/import utilities, and re-associate it with the PL/SQL attribute.
WWU-74204: The LOV %1 associated with %2 attribute does not exist. The LOV is being reset.
Cause: The list of values does not exist on the target.
Action: Bring in the list of values separately, and re-associate or promote it to the transport set in the source. Then reimport it.
WWU-74205: The contained object %1 will not be imported because the container object %2 is reused for the target.
Cause: This can happen when the contained object is forcefully set to reuse mode because the container object was set to reuse mode.
Action: If you want the contained object to be merged to the target, bring in the container object in overwrite mode.
WWU-74206: Unable to import the page group %1. The internal identifier of the new page group already exists.
Cause: The internal identifier of the page group being imported was already in use on the target.
Action: Try importing again. If the retry fails, contact Oracle Support Services.
WWU-74207: Unable to update the properties of the page group %1 being imported.
Cause: An unexpected error occurred while updating the page group properties.
Action: Try importing again. If the retry fails, contact Oracle Support Services.
WWU-74208: Unable to propagate the new internal identifier of the page group being imported.
Cause: The internal identifier of the page group was not updated to all of the page group objects.
Action: Contact Oracle Support Services.
WWU-74209: Unable to resolve the text attribute with internal identifier %1, of the custom item of the page group with internal identifier %2.
Cause: Resolution of the item with the text attribute failed.
Action: Try importing again. If the retry fails, contact Oracle Support Services.
WWU-74210: Multiple records found pointing to the same text attribute with internal identifier %1, of the custom item of the page group with internal identifier %2 .
Cause: More than one row was found for the text attribute of the custom item during resolution.
Action: Try importing again. If the retry fails, contact Oracle Support Services.
WWU-74211: Unable to resolve the URL with internal identifier %1, of the page group with internal identifier %2.
Cause: Resolution of the item with the URL attribute failed.
Action: Try importing again. If the retry fails, contact Oracle Support Services.
WWU-74212: Multiple records found pointing to the same URL with internal identifier %1, of the page group with internal identifier %2.
Cause: More than one row was found for the URL during resolution.
Action: Try importing again. If the retry fails, contact Oracle Support Services.
WWU-74213: Unable to find the page type function with internal identifier %1 of the page group with internal identifier %2.
Cause: The attempt to find the page type function failed.
Action: Try importing again. If the retry fails, contact Oracle Support Services.
WWU-74214: Unable to update the attribute %1.
Cause: The attribute update failed.
Action: Try importing again. If the retry fails, contact Oracle Support Services.
WWU-74215: Unable to update the style %1.
Cause: The style update failed.
Action: Try importing again. If the retry fails, contact Oracle Support Services.
WWU-74216: Unable to add translation for category %1 of the page group with internal identifier %2.
Cause: Failed to add translation for category.
Action: Contact Oracle Support Services.
WWU-74217: Unable to add translation for perspective %1 of page group with internal identifier %2.
Cause: Failed to add translation for perspective.
Action: Contact Oracle Support Services.
WWU-74218: create_item_DAV_err |Due to DAV error, unable to add item %1 of the page group with internal identifier %2.
Cause: An unexpected DAV error occurred while creating the item on the target.
Action: Contact Oracle Support Services.
WWU-74219: Due to an unexpected error, unable to add item %1 of the page group with internal identifier %2.
Cause: An unexpected error occurred while creating the item on the target.
Action: Try importing again. If the retry fails, contact Oracle Support Services.
WWU-74220: Due to DAV error, unable to update item %1 of the page group with internal identifier %2.
Cause: An unexpected DAV error occurred while updating the item on the target.
Action: Contact Oracle Support Services.
WWU-74221: Due to an unexpected error, unable to update item %1 of the page group with internal identifier %2.
Cause: An unexpected error occurred while updating the item on the target.
Action: Try importing again. If the retry fails, contact Oracle Support Services.
WWU-74222: Unable to create the region attributes for the region with unique identifier %1.
Cause: An unexpected error occurred while creating the region attributes.
Action: Try importing again. If the retry fails, contact Oracle Support Services.
WWU-74223: Unable to create region with unique identifier %1 for the page with internal identifier %2 because it already exists on the target system.
Cause: Could not create region because it already exists on the target system.
Action: Try importing again. If the retry fails, contact Oracle Support Services.
WWU-74224: Unable to create region with unique identifier %1 for the page with internal identifier %2, due to an unexpected error.
Cause: An unexpected error occurred while creating the region on the target.
Action: Contact Oracle Support Services.
WWU-74225: Unable to update region with unique identifier %1 for the page with internal identifier %2, due to an unexpected error.
Cause: An unexpected error occurred while updating the region on the target.
Action: Contact Oracle Support Services.
WWU-74226: Unable to update properties of the region with unique identifier %1 because it exists on another page.
Cause: Region exists on another page.
Action: Contact Oracle Support Services.
WWU-74227: Unable to create Page, Tab, Template, or Navigation Page %1 due to an unexpected error.
Cause: An unexpected error occurred while creating the page on the target.
Action: Contact Oracle Support Services.
WWU-74228: Unable to update Page, Tab, Template, or Navigation Page %1 due to an unexpected error.
Cause: An unexpected error occurred while updating the page on the target.
Action: Contact Oracle Support Services.
WWU-74229: Unable to share the portlet instance %1.
Cause: Failed to share the portlet instance on the target.
Action: Contact Oracle Support Services.
WWU-74230: Unable to locate page group %1 on the target. Child objects of this page group will not be imported.
Cause: The Child objects of this page group will not be imported because the page group does not exist on the target.
Action: In the source, promote the page group in your transport set, or export the page group explicitly, then import it.
WWU-74231: The source default language %1 of the page group %2 is either not installed or not available on the target.
Cause: The default language of the page group is either not installed or not available on the target.
Action: Install and make available the default language on the target and reimport.
WWU-74232: Default language %1 of the page group %2 is not installed on the target portal.
Cause: The source page group's default language is not installed on the target portal.
Action: Install the language on the target, and reimport.
WWU-74233: An unexpected error occurred while deleting version %1 of item with unique identifier %2 .
Cause: Deleting an item version has resulted in an unexpected error.
Action: Verify that the page with the item renders properly. If it doesn't, contact Oracle Support Services.
WWU-74234: Unable to merge approval related infrastructure due to an unexpected error.
Cause: An unexpected error occurred while merging approval-related infrastructure on the target.
Action: Manually re-create the approval process on the target.
WWU-74235: Unable to sync style attributes due to an unexpected error.
Cause: An unexpected error occurred while synchronizing style attributes on the target.
Action: Ensure that all the imported styles have correct settings for their attributes. If they don't, contact Oracle Support Services.
WWU-74236: The template %1 cannot be reused because it has undergone significant changes since the last import.
Cause: The template on the target has undergone significant changes since the last import. This will affect the import of pages that are dependent on the template. Consequently, the template cannot be reused.
Action: Set the import mode to overwrite. Save for later, and rerun precheck.
WWU-74237: The page %1 has failed precheck because its template %2 cannot be reused. Make %2 overwrite to proceed with import.
Cause: The page's template on the target has undergone significant changes since the last import. Consequently, the template cannot be reused if the pages are to be overwritten.
Action: Set the import mode of the template to overwrite. Save for later, and rerun precheck.
WWU-74239: Portal Template %1 belonging to %2 page group is being imported in replace on import mode. Any changes done to the template objects (items, portlets, etc) on the page(s) using the template will be overwritten by the template replication when the import operation completes.
Cause: Portal template replication deletes all template objects (items, portlets, etc) found in the pages using the template and re-creates them based on the template definition. This removes any changes made at the page level for those template objects.
Action: If portal template needs to undergo constant updates, do not make changes to the pages' template objects. If template objects changes need to be preserved, bring the portal template in the reuse mode (uncheck the Replace on Import check box in the manifest).
WWU-74240: Portal Template %1 belonging to %2 pagegroup is being reused. If pages using the template accompany the template in the same transport set (and are imported in replace on import mode) they might have inconsistent behavior upon import.
Cause: When importing the portal template in the reuse mode (and there are significant changes between the source and the target template) and pages using the template are imported in replace on import mode, the pages will not be correctly synchronized with portal template on the target.
Action: Make sure the source and the target template are synchronized first by importing the portal template in the overwrite mode. Once this synchronization is done, pages using the template can be imported in the replace on import mode with the template set to the reuse mode.
WWU-74241: The unique identifier of the source page/template/navigation page %1 of the page group %2 does not match the unique identifier of target page/template/navigation page %1. The page name you specified in source is already in use in target.
Cause: A different page already exists on the target with the same name.
Action: Delete the page on the target and import again.
WWU-74242: The unique identifier of the source category %1 of the page group %2 does not match the unique identifier of target category %1. The category name you specified on source is already in use on target.
Cause: A different category already exists on the target with the same name.
Action: Delete the category on the target and import again.
WWU-74243: The source category %1 has been promoted to shared objects but the same category %2 exists on the target in a local page group. The local category on the target cannot be overwritten or reused by the shared category on the source. Promote the local category on the target to shared objects and import the dump file again.
Cause: The source category has been promoted but the same category exists on the target in a local page group.
Action: Promote the local category on the target and reimport.
WWU-74244: The source category %1 belongs to a local page group. The same category %2 on the target has been promoted to shared objects. The shared category on the target cannot be overwritten or reused by the local category on the source.
Cause: The source category belongs to a local page group. The same category on the target has been promoted.
Action: Promote the local category on the source and reimport it.
WWU-74245: The unique identifier of the source perspective %1 of the page group %2 does not match the unique identifier of target perspective %1. The perspective name you specified on source is already in use on target.
Cause: A different perspective already exists on the target with the same name.
Action: Delete the perspective on the target and import again.
WWU-74246: The source perspective %1 has been promoted to shared objects but the same perspective %2 exists on the target in a local page group. The local perspective on the target cannot be overwritten or reused by the shared perspective on the source. Promote the local perspective on the target to shared objects and import the dump file again.
Cause: The source perspective has been promoted but the same perspective exists on the target in a local page group.
Action: Promote the local perspective on the target and reimport.
WWU-74247: The source perspective %1 belongs to a local page group. The same perspective %2 on the target has been promoted to shared objects. The shared perspective on the target cannot be overwritten or reused by the local perspective on the source.
Cause: The source perspective belongs to a local page group. The same perspective on the target has been promoted.
Action: Promote the local perspective on the source and reimport it.
WWU-74248: Precheck failed for %1 %2 of %3 pagegroup as %2 is being imported as an external object which does not exist on the target. An external object must exist on the target for it to be reused.
Cause: Object is being imported as an external object but it does not exist on the target.
Action: Promote the external object in the transport set and reimport.
WWU-74249: Unknown error occurred while resetting syspriv name for page with unique identifier %1. The syspriv name will not be reset for this page.
Cause: An unexpected error occurred while resetting the syspriv name for that page.
Action: Check if all the pages imported appear normally with all the links in the navigator. Otherwise, contact Oracle Support Services with the necessary logs.
WWU-74250: The page configured for generic page portlet: %1 does not exist on target. Therefore resetting the values to default.
Cause: The page configured for portlet was not found. The user might not have added the dependent page to the transport set. Normally you would see a warning status against the explicit object.
Action: Add the dependent page to the transport set and reimport. Or bring in the required page separately and reconfigure it manually.
WWU-74251: The unique identifier(GUID) of the source page group %1 does not match the unique identifier of target page group %1. The page group name you specified in source is already in use in target.
Cause: A different page group already exists on the target with the same name.
Action: Delete the page group on the target and import again.
WWU-74252: Page group %1 is not found in target or in the transport set, this is required for successful import of object type %2 named %3.
Cause: The page group object listed under External Objects is not present on the target or in the transport set. The import cannot proceed for the explicitly selected object since its page group is not available on target.
Action: In source, promote the page group object from the external objects section and export/import the transport set again.
WWU-74253: You (%1) cannot create a shared object since you do not have ANYTRANSPORTSET_MANAGE privilege.
Cause: A shared object can be imported only by a user who has ANYTRANSPORTSET_MANAGE privilege.
Action: Contact your administrator to obtain that privilege and then perform the import.
WWU-74254: HTML Template %1 belonging to %2 pagegroup does not exist on the target. All pages and regions using it will be reset.
Cause: The HTML template does not exist on the target and therefore its association was reset.
Action: The user can migrate the HTML template individually and re-associate it.
WWU-74255: Portal Template %1 belonging to %2 pagegroup does not exist on the target. All pages and items using it will be reset.
Cause: The Portal template does not exist on the target and therefore its association was reset.
Action: The user can migrate the Portal template individually and re-associate it.
WWU-74256: An unknown fatal error has occurred during the import of transport set. See the debug logs for details.
Cause: An unknown fatal error has occurred during the import of transport set.
Action: See the debug log for details and contact Oracle Support Services.
WWU-74257: The language %1 (%2) is not installed on target and hence all the language related data will be deleted.
Cause: The specified language is not installed on target.
Action: Install the language and reimport.
WWU-74263: Deleting the text entries from text/plsql items for the null text handler.
Cause: Text ID is null for the item.
Action: No action required.
WWU-74264: Deleting the text entries from pagetype attributes for the null text handler.
Cause: Text ID is null for pagetype attribute.
Action: No action required.
WWU-74265: Deleting the url entries from url-items for the null url handler.
Cause: Url ID is null for the item.
Action: No action required.
WWU-74266: Deleting the url entries from pagetype attributes for the null url handler.
Cause: Url ID is null for pagetype attribute.
Action: No action required.
WWU-74267: An unknown fatal error has occurred during the export of transport set. See the debug logs for details.
Cause: An unknown fatal error has occurred during the export of transport set.
Action: See the debug log for details and contact Oracle Support Services.
WWU-74268: The page configured for news announcement OIP portlet: %1 does not exist on target. Therefore resetting the values to null.
Cause: The page configured for the portlet was not found. It could have been deleted on the source.
Action: Edit the portlet and reconfigure it to point to any valid page.
WWU-74269: The pagegroup configured for OIP summary portlet: %1 was not found on target. Therefore resetting the values to null.
Cause: The pagegroup configured for the portlet was not found. This could be due to a data inconsistency or an import error.
Action: Edit the portlet and reconfigure it to point to a valid pagegroup.
WWU-74301: An error occurred while exporting registration properties.
Cause: A problem may have occurred while inserting entries into the registration properties transport table.
Action: Contact Oracle Support Services.
WWU-74302: An error occurred while exporting user category maps.
Cause: A problem may have occurred while inserting entries into the role maps transport table.
Action: Contact Oracle Support Services.
WWU-74402: There has been a metadata inconsistency.
Cause: A metadata inconsistency resulted from the direct manipulation of system tables, such as WWAPP_APPLICATION$, WWAPP_APPLICATION_DETAIL$, WWV_MODULES$, or WWV_MODULE_DETAILS$, or from an incorrect component state during export.
Action: Contact Oracle Support Services.
WWU-74403: Metadata for %1 is not available in %2.
Cause: Metadata is not available due to the direct manipulation of system tables, such as WWAPP_APPLICATION$, WWAPP_APPLICATION_DETAIL$, WWV_MODULES$, or WWV_MODULE_DETAILS$.
Action: Contact Oracle Support Services.
WWU-74404: %1 contains more than one row for %2.
Cause: This error message can result from the direct manipulation of system tables, such as WWAPP_APPLICATION$, WWAPP_APPLICATION_DETAIL$, WWV_MODULES$, or WWV_MODULE_DETAILS$.
Action: Contact Oracle Support Services.
WWU-74405: %1 will not be considered for export.
Cause: Export time prechecks have failed.
Action: Contact Oracle Support Services.
WWU-74406: No versions for component %1 are available at the time of this export.
Cause: No versions are available due to the direct manipulation of system tables, such as WWAPP_APPLICATION$, WWAPP_APPLICATION_DETAIL$, WWV_MODULES$, or WWV_MODULE_DETAILS$.
Action: Contact Oracle Support Services.
WWU-74407: Component %1 is in %2 state at the time of this export.
Cause: At the time of export, a production version was unavailable. This situation can arise if a component has only one version and that version is being edited, or if all the versions of the component are archive versions.
Action: Complete or cancel the edit operation before exporting. Ensure that the component has a production version.
WWU-74408: Incorrect data detected for component %1 in table %2.
Cause: Incorrect data due to the direct manipulation of system tables, such as WWAPP_APPLICATION$, WWAPP_APPLICATION_DETAIL$, WWV_MODULES$, or WWV_MODULE_DETAILS$ was detected.
Action: Contact Oracle Support Services.
WWU-74409: Metadata for LOV %1 is not available in %2.
Cause: Metadata is not available due to the direct manipulation of metadata tables for lists of values.
Action: Contact Oracle Support Services.
WWU-74410: More than one row was detected for LOV %1 in %2.
Cause: More than one row was detected for the list of values (LOVs) due to the direct manipulation of metadata tables for LOVs.
Action: Contact Oracle Support Services.
WWU-74411: Metadata for menu %1 is not available in %2.
Cause: Menu metadata is not available due to the direct manipulation of metadata tables for menus.
Action: Contact Oracle Support Services.
WWU-74412: Metadata for data component %1 is not available in %2.
Cause: Component metadata is not available due to the direct manipulation of metadata tables for data component.
Action: Contact Oracle Support Services.
WWU-74413: More than one row detected for data component %1 in %2.
Cause: More than one row was detected for data component due to the direct manipulation of metadata tables for data component.
Action: Contact Oracle Support Services.
WWU-74414: At the time of this export, DB Provider schema %1 is missing for DB Provider %2.
Cause: Direct user intervention could have dropped the DB Provider schema.
Action: Contact Oracle Support Services.
WWU-74415: Metadata for owner of %1 is not available in %2.
Cause: Owner metadata is not available due to the direct manipulation of system tables, such as WWAPP_APPLICATION$, WWAPP_APPLICATION_DETAIL$, WWV_MODULES$, or WWV_MODULE_DETAILS$.
Action: Contact Oracle Support Services.
WWU-74416: Provider ID is null, though the component %1 is exposed as a provider.
Cause: The provider ID is null due to the direct manipulation of system tables, such as WWAPP_APPLICATION$, WWAPP_APPLICATION_DETAIL$, WWV_MODULES$, or WWV_MODULE_DETAILS$.
Action: Contact Oracle Support Services.
WWU-74417: The value %1 is invalid for flag %2 in table %3 .
Cause: Value is invalid due to the direct manipulation of system tables, such as WWAPP_APPLICATION$, WWAPP_APPLICATION_DETAIL$, WWV_MODULES$, or WWV_MODULE_DETAILS$.
Action: Contact Oracle Support Services.
WWU-74418: The combination of values in columns EXPOSE_AS_PROVIDER and PROVIDER_ID for component %1 is incorrect in table WWAPP_APPLICATION$.
Cause: The combination of values is incorrect due to the direct manipulation of system tables, such as WWAPP_APPLICATION$, WWAPP_APPLICATION_DETAIL$, WWV_MODULES$, or WWV_MODULE_DETAILS$.
Action: Contact Oracle Support Services.
WWU-74419: Could not perform precheck due to insufficient data.
Cause: Direct manipulation of the system tables could have caused the unavailability of data.
Action: Contact Oracle Support Services.
WWU-74502: An error occurred while exporting data from web provider %1.
Cause: Export of personalization data from the web provider, or one of its portlets, failed.
Action: Check the debug messages for possible reasons for this failure, for example:

1) Web provider's application server may be down or inaccessible.

2) Underlying network error.

If you are unable to further diagnose the problem, contact Oracle Support Services.

WWU-74505: An error occurred while importing data to the web provider %1.
Cause: Import of personalization data to the web provider, or one of its portlets, failed.
Action: Check the debug messages for possible reasons for this failure, for example:

1) Web provider's application server may be down or inaccessible.

2) Underlying network error.

If you are unable to further diagnose the problem, contact Oracle Support Services.

WWU-74511: The version of the web provider you are trying to export from is not supported. Export cannot proceed for web provider %1.
Cause: The web provider is not version 10.1.2.0.0 or greater, or you are trying to export customizations from a Federated Portal Adapter provider.
Action: Contact the web provider's administrator to arrange for this web provider to be upgraded. Note that Federated Portal Adapter providers do not support export/import of customizations.
WWU-74512: The version of the web provider you are trying to import is not supported. Import cannot proceed for this web provider %1.
Cause: The web provider is not version 10.1.2.0.0 or greater, or you are trying to import customizations from a Federated Portal Adapter provider.
Action: Contact the web provider's administrator to arrange for this web provider to be upgraded. Note that Federated Portal Adapter providers do not support export/import of customizations.
WWU-74513: The version of the web provider you are trying to export/import is not supported. Export/Import will not proceed for this web provider.
Cause: Import of web provider or some of its portlets failed.
Action: It is possible that this version of the web provider is not supported by export and import. Refer to the documentation for supported versions. If you are still unable to export or import, contact Oracle Support Services.
WWU-74514: Failed to write to transport set.
Cause: An internal error occurred during the import/export operation.
Action: Examine other error messages for more information if available, or contact Oracle Support Services.
WWU-74515: An unexpected error occurred during import.
Cause: An internal error occurred during the import operation.
Action: Examine other error messages for more information if available, or contact Oracle Support Services.
WWU-74516: An unexpected error occurred during export.
Cause: An internal error occurred during the export operation.
Action: Examine other error messages for more information if available, or contact Oracle Support Services.
WWU-74517: Could not connect to web provider at %1.
Cause: Could not connect to the web provider to import or export customizations.
Action: Make sure that the web provider is available and that there are no network issues.
WWU-74518: Timed out after %1ms waiting for response from web provider at %2.
Cause: A timeout occurred during communication with the web provider to import or export customizations.
Action: Make sure that the web provider is available and that there are no network issues.
WWU-74519: Web provider does not implement data transport methods.
Cause: The specified web provider does not support import/export of customization data.
Action: Contact the web provider's administrator to enable this feature, or upgrade the web provider.
WWU-74520: HMAC authentication failed with provider %1 using shared key %2.
Cause: An internal error occurred during the import/export operation.
Action: Examine other error messages for more information if available, or contact Oracle Support Services.
WWU-74521: Web provider server error.
Cause: An internal error occurred on the remote web provider during the import/export operation.
Action: Examine the error stack for more information, or contact the web provider's administrator.
WWU-74522: Unable to create HMAC checksum for provider %1 using shared key %2.
Cause: An internal error occurred during the import/export operation.
Action: Examine other error messages for more information if available, or contact Oracle Support Services.
WWU-74523: An unexpected error occurred during the transport operation.
Cause: An internal error occurred during the import/export operation.
Action: Examine other error messages for more information if available, or contact Oracle Support Services.
WWU-74524: Unable to contact remote web provider: invalid URL %1.
Cause: Could not connect to the web provider to import or export customizations due to an invalid provider URL.
Action: Correct the web provider URL.
WWU-74525: Unable to interact with the database.
Cause: An internal error occurred during the import/export operation.
Action: Examine other error messages for more information if available, or contact Oracle Support Services.
WWU-74526: Failed to read from transport set for portlet instance %1, %2.
Cause: An internal error occurred during the import/export operation.
Action: Examine other error messages for more information if available, or contact Oracle Support Services.
WWU-74550: An unexpected error occurred while exporting providers.
Cause: An unexpected error occurred while exporting providers.
Action: Check the debug logs for further details. Contact Oracle Support Services before importing.
WWU-74551: An unexpected error occurred while exporting provider groups.
Cause: An unexpected error occurred while exporting providers groups.
Action: Check the debug logs for further details. Contact Oracle Support Services before importing.
WWU-74552: An unexpected error occurred while exporting proxies.
Cause: An unexpected error occurred while exporting proxies.
Action: Check the debug logs for further details. Contact Oracle Support Services before importing.
WWU-74553: Unexpected Error while exporting portlet preferences.
Cause: An unexpected error occurred while exporting portlet preferences.
Action: Check the debug logs for further details. Contact Oracle Support Services before importing.
WWU-74554: An unexpected error has occurred, which has caused the entire provider export to be rolled back.
Cause: An unexpected error has caused the entire provider export to be rolled back.
Action: Check the debug logs for further details and contact Oracle Support Services.
WWU-74555: An unexpected error occurred while importing proxies.
Cause: An unexpected error occurred while importing proxies.
Action: Check the debug logs for further details and contact Oracle Support Services.
WWU-74556: An unexpected error occurred while updating providers.
Cause: An unexpected error occurred while updating provider information on the target.
Action: Check the debug logs for further details and contact Oracle Support Services.
WWU-74557: Preference name %1 for the portlet with reference path %2 could not be created, due to an unexpected error.
Cause: An unexpected error occurred while importing portlet preferences.
Action: Check the debug logs for further details and contact Oracle Support Services.
WWU-74558: Unable to create the preference value for name %1 of the portlet with reference path %2, due to an unexpected error.
Cause: An unexpected error occurred while importing the portlet's preferences.
Action: Check the debug logs for further details and contact Oracle Support Services.
WWU-74559: An unexpected error occurred while setting edit defaults for the portlet with reference path %1.
Cause: An unexpected error occurred while setting edit defaults for the imported portlets.
Action: Check the debug logs for further details and contact Oracle Support Services.
WWU-74560: Unable to validate the portlet with reference path %1.
Cause: An error occurred while validating the portlet.
Action: Check the debug logs for further details and contact Oracle Support Services.
WWU-74561: An error occurred while executing the web provider with unique identifier %1 of the portlet with reference path %2.
Cause: An unexpected error occurred during web provider execution.
Action: Check the debug logs for further details and contact Oracle Support Services.
WWU-74562: An error was encountered while the portlet with reference path %1 was executing.
Cause: An unexpected error occurred during portlet execution.
Action: Check the debug logs for further details and contact Oracle Support Services.
WWU-74563: The portlet with reference path %1 could not be registered due to an unexpected error.
Cause: An unexpected error occurred while registering the portlet.
Action: Check the debug logs for further details and contact Oracle Support Services.
WWU-74564: The portlet with reference path %1 could not be de-registered due to an unexpected error.
Cause: An unexpected error occurred while de-registering the portlet.
Action: Check the debug logs for further details and contact Oracle Support Services.
WWU-74565: An unexpected error occurred while importing portlet preferences.
Cause: An unexpected error occurred while importing portlet preferences.
Action: Check the debug logs for further details and contact Oracle Support Services.
WWU-74566: A failure occurred while adding the provider with unique identifier %1 to the repository.
Cause: Provider refresh failed.
Action: Check the debug logs for further details and contact Oracle Support Services.
WWU-74567: Post-import massaging of provider objects failed due to an unexpected error.
Cause: An unexpected error occurred during post-import massage of providers.
Action: Check the debug logs for further details and contact Oracle Support Services.
WWU-74568: You do not have permission to register provider %1. If you proceed with the import, all portlets belonging to this provider will be deleted from your pages.
Cause: The user does not have sufficient privileges to register the provider.
Action: Ask the administrator to register the provider, or perform the import as a user who has privilege to register providers.
WWU-74569: Unable to validate information for provider %1. If you proceed with the import, all portlets belonging to this provider will be deleted from your pages.
Cause: The registration API is unable to validate provider information.
Action: Try to register the provider manually. If that fails, check the debug logs for further details and contact Oracle Support Services.
WWU-74570: Call to register provider %1 failed. If you proceed with the import, all portlets belonging to this provider will be deleted from your pages.
Cause: The call to the register provider has failed.
Action: Try to register the provider manually. If that fails, check the debug logs for further details and contact Oracle Support Services.
WWU-74571: An error occurred during provider %1 registration. If you proceed with the import, all portlets belonging to this provider will be deleted from your pages.
Cause: Provider registration failed.
Action: Try to register the provider manually. If that fails, check the debug logs for further details and contact Oracle Support Services.
WWU-74572: An unexpected error occurred during provider %1 registration. If you proceed with the import, all portlets belonging to this provider will be deleted from your pages.
Cause: An unexpected error occurred while registering the provider.
Action: Try to register the provider manually. If that fails, check the debug logs for further details and contact Oracle Support Services.
WWU-74573: Precheck for database provider %1 failed, as its schema %2 does not exist on the target.
Cause: The database provider cannot be registered because its schema does not exist on the target.
Action: Export/import the schema and try again.
WWU-74574: Precheck passed with a warning for database provider %1, as its schema %2 differs from the %3 specified on the target.
Cause: Schema registration details differ on the source and target.
Action: Ensure that the provider on the target is valid. If you want the same registration details on the target as on the source, deregister the provider on the target, migrate the necessary schema, and reimport.
WWU-74575: The URL specified during web provider %1 registration is different on the source and target. Import will assume that the providers are the same. Ensure that the provider has the same set of portlets on the source that it has on the target.
Cause: The provider may have been independently registered on the target, using the same name but a different URL.
Action: Ensure that the provider has the same set of portlets on the source as on the target.
WWU-74576: An unexpected error occurred during the provider precheck. Precheck has failed.
Cause: An unexpected error occurred during the provider precheck.
Action: Try to register the provider manually. If that fails, check the debug logs for further details and contact Services.
WWU-76778: There were some inconsistencies found and fixed. Check the debug log for further details.
Cause: Some inconsistencies may have occurred as a result of the import.
Action: Check the debug logs for further details on what the inconsistencies were and how they were corrected. Contact Oracle Support Services if the imported objects caused errors.
WWU-80000: All the explicit objects in the transport set have failed precheck. The import cannot proceed.
Cause: All the explicitly selected objects have failed the precheck, either due to missing dependent objects or missing shared references.
Action: Check the precheck log to determine the cause of failure. After correcting the errors, try importing again.
WWU-80001: Some of the explicit objects in the transport set have failed precheck. Proceed with import?
Cause: Some of the explicitly selected objects have failed precheck, either due to missing dependent objects or missing shared references.
Action: Check the precheck log to determine the cause of failure. After correcting the errors, try importing again.
WWU-80002: Some of the objects in the transport set have failed precheck with warnings/errors. Proceed with import?
Cause: Some of the objects have failed precheck, either due to missing dependent objects or missing shared references.
Action: Review the precheck log to determine the reason for the failure. After correcting the errors, try importing again, or contact Oracle Support Services.
  Previous
Previous 		Next
Next
  Go To Documentation Library
Home		 Go To Product List
Solution Area		 Go To Table Of Contents
Contents