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

4 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 export fails, contact Oracle Support Services.
WWU-52263: The object %1 was not added to the transport set either because it already exists as an explicit object or is a child of a container object that exists as an explicit object.
Cause: The object is already marked for export.
Action: Do nothing. The selected object will be exported.
WWU-52293: Unknown exception occurred while validating system tables. Hence, aborting the export.
Cause: Abnormal exception occurred while performing the schema validation and cleanup.
Action: Please check the schema-validation document to correct it and export again.
WWU-52294: Unknown exception occurred while validating system tables. Hence, exiting validation process. Any changes done by the validation phase will be reverted back.
Cause: Abnormal exception occurred while performing the schema validation and cleanup.
Action: Please check the schema-validation document to correct it.
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 re-import 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 re-import 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 re-import it.
WWU-52323: The source attribute %1 exists on the target with 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 re-import it, or import it in the 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 re-import 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 re-import 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 re-import 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 re-import 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 re-import 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 re-import 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 re-import 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 re-import 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 re-import 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 re-import it.
WWU-52338: The portlet instance having Unique Identifier(portlet_inst_guid): %1 will be deleted from the page in the transport set because its dependency does not exist on the target.
Cause: The portlet's dependency, such as its page, Web Provider, Database Provider, or the like, does not exist on the target.
Action: Promote the portlet's dependency to the transport set in the source, and re-import it. If the dependency is a Web Provider, register it on the target to make the portlet available in the Portlet Repository.
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: 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-52872: Mapping not found for Page ID %1 and Page Group ID %2 .
Cause: Attempt to find the object failed.
Action: Retry the import. If the retry 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: Export of the transport set is not complete.
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. It may be necessary to re-create the transport set.
WWU-52887: Transport Set %1 is currently unavailable either for export or import. Browse the Transport Set for more details.
Cause: 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: Logged-in user does not have MANAGE privilege on any transport sets.
Action: Ask your Oracle Application Server portal administrator to assign you this privilege.
WWU-52969: Transport set does not exist. Cannot pre-check search preferences.
Cause: Search preferences cannot be pre-checked 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 pre-check search preferences.
Cause: Search preferences cannot be pre-checked 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: Error when performing export pre-check of search portlet preferences.
Cause: An unexpected error occurred while pre-checking search preferences prior to export.
Action: Check that the customizations for the search portlets you are exporting are valid.
WWU-52973: Error 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: Error 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 pre-check.
Cause: An unexpected error occurred while pre-checking search preferences.
Action: Contact Oracle Support Services.
WWU-52980: Error while marking an object as 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 setting the page as failed pre-check.
Cause: An unexpected error occurred while attempting to mark a page as failed pre-check.
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 pre-check.
Cause: An error occurred while attempting to get the ID of an object in the target tables.
Action: Contact Oracle Support Services.
WWU-52985: Pre-check 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: Error 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: Error 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: Error 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: Error 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: Getting page path has 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: Getting page path has 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: Getting page path has 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: Getting page path has 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: Error 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: Getting category path has 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: Getting category path has 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: Getting category path has 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: Getting category path has 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: Error populating 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: Getting perspective path has 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: Getting perspective path has 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: Getting perspective path has 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: Getting perspective path has 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: Error populating 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 if the item types selected in 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 if the categories selected in 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 if the perspectives selected in 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 if the results attributes selected in 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 whilst 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 whilst 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 whilst 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-74100: Page %1, of the page group having unique identifier %2, uses user 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 having 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 getting the metadata of the attribute having 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 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 having 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 having 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: Do not find Page Type Definition for the page %1 in the page group having 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 having 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: Do not find Item Type definition for the item %1 in page group having 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 getting the item type of item %1 in the page group having 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 having 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 getting the category of page %1 in the page group having 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 having 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. A 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 getting 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 getting the style of the page %1 having page group identifier %2. An attempt to import this transport set could result in errors.
Cause: An unexpected error occurred while getting 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 having 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 getting 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 getting 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 having unique identifier %1, where 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 portlet having 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 having the unique identifier %1. An attempt to import this transport set could result in errors.
Cause: No data was found while getting 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 getting the provider details having 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 getting the provider associated with the page group having unique identifier %1. An attempt to import this transport set could result in errors.
Cause: An unexpected error occurred while getting 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 getting the page having unique identifier %1 and page group %2. This page is a page-link dependency of another page. Page link will get lost on import.
Cause: An unexpected error occurred while getting 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 having unique identifier %1 and page group %2. This page is page-link dependency of another page. 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. For example, the page link will get lost.
Action: Contact Oracle Support Services, and provide the export logs.
WWU-74128: Cannot find the template metadata having 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 getting the specified template metadata. The export proceeded without the template. Import of 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 getting the template metadata having 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 getting the specified template's metadata. The export proceeded without the template. Import of 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. Import of 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. Import of 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 having 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. Import of 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 having 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. Import of 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 having 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. Import of 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 having 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. Import of 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 having 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. Import of 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 that use this image that are imported from this transport set will use the target's default image, for example, 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 that use this script that are imported from this transport set 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. Import of 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 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-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. Import of 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 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-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. Import of 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 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-74147: Unable to add all the colors. Import of this transport set could result in errors.
Cause: An unexpected error occurred while adding all the colors. The export proceeded without the colors. Import of 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 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-74148: Unable to add all the fonts. Import of this transport set could result in errors.
Cause: An unexpected error occurred while adding all the fonts. The export proceeded without the fonts. Import of 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 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-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. Import of 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-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 re-import 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: Retry importing. 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: Retry importing. 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 having Internal Identifier %1, of the custom item of the page group having Internal Identifier %2.
Cause: Resolution of the item with the text attribute failed.
Action: Retry importing. If the retry fails, contact Oracle Support Services.
WWU-74210: Multiple records found pointing to the same text attribute having Internal Identifier %1, of the custom item of the page group having Internal Identifier %2.
Cause: More than one row was found for the text attribute of the custom item during resolution.
Action: Retry importing. If the retry fails, contact Oracle Support Services.
WWU-74211: Unable to resolve the URL having Internal Identifier %1, of the page group having Internal Identifier %2.
Cause: Resolution of the item with the URL attribute failed.
Action: Retry importing. If the retry fails, contact Oracle Support Services.
WWU-74212: Multiple records found pointing to the same URL having Internal Identifier %1, of the page group having Internal Identifier %2.
Cause: More than one row was found for the URL during resolution.
Action: Retry importing. If the retry fails, contact Oracle Support Services.
WWU-74213: Unable to find the page type function having Internal Identifier %1 of the page group having Internal Identifier %2.
Cause: The attempt to find the page type function failed.
Action: Retry importing. If the retry fails, contact Oracle Support Services.
WWU-74214: Unable to update the attribute %1.
Cause: The attribute update failed.
Action: Retry importing. If the retry fails, contact Oracle Support Services.
WWU-74215: Unable to update the style %1.
Cause: The style update failed.
Action: Retry importing. If the retry fails, contact Oracle Support Services.
WWU-74216: Unable to add translation for category %1 of the page group having 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 having Internal Identifier %2 .
Cause: Failed to add translation for perspective.
Action: Contact Oracle Support Services.
WWU-74218: Unable to add item %1 of the page group having Internal Identifier %2, due to create_item_DAV_err |Due to DAV error.
Cause: An unexpected DAV error occurred while creating the item on the target.
Action: Contact Oracle Support Services.
WWU-74219: Unable to add item %1 of the page group having Internal Identifier %2, due to an unexpected error.
Cause: An unexpected error occurred while creating the item on the target.
Action: Retry importing. If the retry fails, contact Oracle Support Services.
WWU-74220: Unable to update item %1 of the page group having Internal Identifier %2, due to DAV error.
Cause: An unexpected DAV error occurred while updating the item on the target.
Action: Contact Oracle Support Services.
WWU-74221: Unable to update item %1 of the page group having Internal Identifier %2, due to an unexpected error.
Cause: An unexpected error occurred while updating the item on the target.
Action: Retry importing. If the retry fails, contact Oracle Support Services.
WWU-74222: Unable to create the region attributes for the region having Unique Identifier %1 .
Cause: An unexpected error occurred while creating the region attributes.
Action: Retry importing. If the retry fails, contact Oracle Support Services.
WWU-74223: Unable to create region having Unique Identifier %1 for the page having 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: Retry importing. If the retry fails, contact Oracle Support Services.
WWU-74224: Unable to create region having Unique Identifier %1 for the page having 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 having Unique Identifier %1 for the page having 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 having 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 does not match with the target.
Cause: The default language of the target page group does not match the default language of the source page group.
Action: Delete the page group on the target, and re-import it.
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 re-import.
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 do, 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-74238: Precheck failed for database provider %1 as its schema %2 does not exist on the target.
Cause: The Database provider cannot be registered because its schema does not exist on target.
Action: Export/Import the schema and try again.
WWU-74239: Precheck passed with 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: The user must ensure that the provider on the target is valid. Incase he wants the same registration details as that on the source, then he should de-register the provider on the target, migrate the necessary schema and re-import.
WWU-74240: 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-74241: 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: Please contact your administrator to obtain that privilege and then perform the import.
WWU-74242: %1 %2 is an external object that does not exist on target and hence cannot be reused.
Cause: External Objects are supposed to exist on target and are meant to be reused.
Action: Promote the external object failing precheck on source and re-import.
WWU-74243: The URL specified in registration of web provider %1 differs from source to target. Import will assume that both the providers are the same. Please ensure that the provider has the same set of portlets on source as well as target.
Cause: The user must have registered the provider independently on the target with the same name and different URL.
Action: The user must ensure that the provider in question has the same set of portlets in source and target.
WWU-74244: Page Template %1 belonging to %2 page group is being imported in replace on import mode. Any changes done to the template object (items, portlets, etc) on the page(s) using the template will be overwritten by the template replication when the import operation completes.
Cause: Page 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 will remove any changes done at the page level for those template objects.
Action: If page template needs to under-go constant updates do not make changes to the pages' template objects. If template objects changes need to be preserved, bring the template in reuse mode (uncheck the Replace on Import check box in the manifest).
WWU-74245: Page 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 page template in 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 template on the target.
Action: Make sure the source and the target template are synchronized first by importing the page template in overwrite mode. Once this synchronization is done, pages using the template can be imported in replace on import mode with the template set to reuse mode.
WWU-74246: Deleting the text entries from text/plsql items for the null text handler.
Cause: Text ID is null for the item.
Action: Deleting the text entries automatically from text/plsql items for the null text handler.
WWU-74247: Deleting the text entries from pagetype attributes for the null text handler.
Cause: Text ID is null for pagetype attribute.
Action: Deleting the text entries automatically from pagetype attributes for the null text handler.
WWU-74248: Deleting the url entries from url-items for the null url handler.
Cause: Url ID is null for the item.
Action: Deleting the url entries automatically from url-items for the null url handler.
WWU-74249: Deleting the url entries from pagetype attributes for the null url handler.
Cause: Url ID is null for pagetype attribute.
Action: Deleting the url entries automatically from pagetype attributes for the null url handler.
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 re-import. Or bring in the required page separately and reconfigure it manually.
WWU-74251: 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 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-74252: The pagegroup configured for OIP summary portlet: %1 was not found on target. Therefore resetting the values to null.
Cause: The pagegroup configured for 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-74402: There has been metadata inconsistency.
Cause: Metadata inconsistency resulted from direct manipulation of system tables, such as WWAPP_APPLICATION$, WWAPP_APPLICATION_DETAIL$, WWV_MODULES$, or WWV_MODULE_DETAILS$, or incorrect state of the component during export.
Action: Contact Oracle Support Services.
WWU-74403: Metadata for %1 is not available in %2.
Cause: Metadata is not available due to 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 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 pre-checks 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 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 of the component 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 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 direct manipulation of metadata tables for lists of values.
Action: Contact Oracle Support Services.
WWU-74410: More than one row detected for lov %1 in %2.
Cause: More than one row was detected for the list of values (lovs) due to 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 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 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 detected for data component due to 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 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 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 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 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 pre-check due to insufficient data.
Cause: Direct manipulation of system tables could have caused the unavailability of data
Action: Contact Oracle Support Services. WEB MESSAGES
WWU-74502: An error occurred 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

  • Web provider's application server is down or unaccessible

  • Underlying network error

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

WWU-74505: An error occurred 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

  • Web provider's application server is down or unaccessible

  • 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.
Action: Contact the web provider's administrator to arrange for this web provider to be upgraded.
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.
Action: Contact the web provider's administrator to arrange for this web provider to be upgraded.
WWU-80000: All the explicit objects in the transport set have failed pre-check. Cannot proceed with import.
Cause: All the explicitly selected objects have failed pre-check either due to missing dependent objects or missing shared references
Action: Please check the pre-check log to know about the reason for the failure of these objects. After correcting the scenario, try importing again or contact support.
WWU-80001: Some of the explicit objects in the transport set have failed pre-check. Proceed with import anyways?
Cause: Some of the explicitly selected objects have failed pre-check either due to missing dependent objects or missing shared references
Action: Please check the pre-check log to know about the reason for the failure of these objects. After correcting the scenario, try importing again or contact support.
WWU-80002: Some of the objects in the transport set have failed pre-check with warnings/errors. Proceed with import anyways?
Cause: Some of the objects have failed pre-check either due to missing dependent objects or missing shared references
Action: Please check the pre-check log to know about the reason for the failure of these objects. After correcting the scenario, try importing again or contact support.
  Previous
Previous 		Next
Next
  Go To Documentation Library
Home		 Go To Product List
Solution Area		 Go To Table Of Contents
Contents