Copyright © 2004, Oracle. All rights reserved.
- Cause:
- Normal exit.
- Action:
- None.
- Cause:
- The message identified by its type/name combination was not found in the system message table.
- Action:
- This is an internal error. Contact Oracle Customer Support.
- Cause:
- The message identified by its ID was not found in the system message table.
- Action:
- This is an internal error. Contact Oracle Customer Support.
- Cause:
- A process encountered a low-level, unexpected condition. This is the generic internal error number for program exceptions.
- Action:
- Report this error to Oracle Customer Support and include the attempted operations that led to the error, any unusual circumstances that occurred before receiving this error message, and the complete stack trace produced by this error.
- Cause:
- User sessions are cleaned up by a background job after a specified time interval. An attempt was made to access a session that did not exist.
- Action:
- Close all browser instances to ensure that the session cookie is removed. Re-open the browser and login to the Single Sign-On Server again.
- Cause:
- An error was encountered while decrypting the Portal session cookie.
- Action:
- Close all browser instances to make sure that the session cookie is removed. Re-open the browser and login to the Single Sign-On Server again.
- Cause:
- An unexpected exception occurred. The error message may provide further details.
- Action:
- Review the information in the error message and take appropriate corrective action.
- Cause:
- The parameters specified to locate the proxy were not correct.
- Action:
- Check the parameters and provide the correct value.
- Cause:
- A proxy with the specified name already exists.
- Action:
- Either use the existing proxy or specify a different proxy name.
- Cause:
- The session cookie contained a session reference marked as inactive.
- Action:
- Close all browser instances to make sure that the session cookie is removed. Re-open the browser and login to the Single Sign-On Server again.
- Cause:
- The session cookie is not consistent with the user session in the repository.
- Action:
- Close all browser instances to make sure that the session cookie is removed. Re-open the browser and login to the Single Sign-On Server again.
- Cause:
- An attempt was made to call an API from a browser session but the API is designated to be called from a SQL session.
- Action:
- Check whether the API being called is meant for SQL sessions only. Do not call such APIs from a browser session.
- Cause:
- The language abbreviation specified was invalid.
- Action:
- Specify a correct language abbreviation.
- Cause:
- The territory specified was invalid.
- Action:
- Specify a correct territory.
- Cause:
- One of the following occurred:
- An error occurred when a invalidation message was sent. This can occur when OracleAS Web Cache goes down, or is stopped while OracleAS Portal writes an invalidation message to the OracleAS Web Cache invalidation port.
- Some other unexpected exception occurred while processing an invalidation message.
- Action:
- Check that OracleAS Web Cache is running and that the invalidation port is accepting connections.
- Cause:
- OracleAS Portal was not able to send the invalidation message to OracleAS Web Cache. This can happen if OracleAS Web Cache is enabled in OracleAS Portal and one or more of the following occurred:
- OracleAS Web Cache was not running. It might have been stopped on purpose in order to front-end with the Oracle HTTP server, instead of OracleAS Web Cache. Alternatively, OracleAS Web Cache might have crashed, or been restarted at the time when the invalidation messages were sent from OracleAS Portal or providers.
- OracleAS Web Cache invalidation port problems. This can happen if the OracleAS Web Cache invalidation port value specified in OracleAS Portal is different from the actual OracleAS Web Cache invalidation port. Alternatively, the invalidation port value supplied to OracleAS Portal using the "-cport_i" parameter during installation could also have been wrong, or the OracleAS Web Cache invalidation port was changed in OracleAS Web Cache after the OracleAS Portal install.
- Another process used the OracleAS Web Cache invalidation port before OracleAS Web Cache started listening on it.
- Issues with the OracleAS Web Cache invalidation password. Either the OracleAS Web Cache invalidator password value in Portal is different from the actual OracleAS Web Cache invalidator password, or the invalidator password value supplied to OracleAS Portal using the "-wc_inv_pwd" parameter during installation was wrong.
- Security setting changes in OracleAS Web Cache require the OracleAS Web Cache administrator password, instead of the invalidator password.
- Issues with the OracleAS Web Cache hostname. Either the OracleAS Web Cache hostname value in the Portal is different from the actual OracleAS Web Cache hostname, or the hostname value supplied to portal using the "-host" and "-chost" parameter during the install was wrong.
- OracleAS Web Cache moved to a different server after the Portal installation and the host on which OracleAS Web Cache runs is inaccessible from OracleAS Portal.
- Hostname specified did not include the entire domain name.
- OracleAS Web Cache was not properly disabled. OracleAS Portal can work without OracleAS Web Cache front-ending the middle-tier. To do this the "enable_wc_caching" flag in OracleAS Portal should be turned "Off". If this is not done any operation which attempts to send an invalidation message fails with exceptions such as "Portal Web Cache settings is On while Web Cache may be down".
- Action:
- Verify the cause of this behavior and take the appropriate corrective action.
- Cause:
- The connection parameters required for connecting to the OID server were not available.
- Action:
- Use the APIs wwsec_oid.get_oid_host and wwsec_oid.get_oid_port to verify that the preference store values for OID parameters exist and are valid. If necessary, run the command line script ptlasst in MIDTIER mode to configure the OID connection parameters: ptlasst.csh -mode MIDTIER -type OID
- Cause:
- An attempt was made to perform an action with insufficient privileges.
- Action:
- Contact the portal administrator and request the necessary privileges be granted to perform this task.
- Cause:
- No user name was provided.
- Action:
- Enter a valid user name in the Username field.
- Cause:
- An error occurred while setting the default group for a given user.
- Action:
- Verify that the specified default group exists and the user has the necessary privileges to access this group.
- Cause:
- The group name field was empty.
- Action:
- Enter a group name.
- Cause:
- An attempt was made to perform a task on a Group but the user did not have ownership, or the privilege to perform that task.
- Action:
- Contact the portal administrator. Either request to be added to the group's OWNER list, or that the necessary privileges be granted to perform the task.
- Cause:
- An attempt was made to access a Group but the specified Group was not found.
- Action:
- Check the name of the Group.
- Cause:
- An attempt was made to perform a task but the user had insufficient privileges to perform the action.
- Action:
- Contact the portal administrator. Request the necessary privileges be granted to perform the task.
- Cause:
- An attempt was made to perform a task on a Group but the user did not have ownership, or the privilege to perform that task.
- Action:
- Contact the portal administrator. Either request to be added to the group's OWNER list, or that the necessary privileges be granted to perform the task.
- Cause:
- One of the following occurred:
- An attempt was made to delete a special group such as the DBA or PORTAL_ADMIN group.
- The specified Group Profile does not exist in OID.
- Action:
- Check the details of the Group to be deleted.
- Cause:
- An attempt was made to delete the schema owner but the schema owner may not be deleted.
- Action:
- Check the details of the user to be deleted.
- Cause:
- An attempt was made to add a group but a group with the specified name already exists.
- Action:
- Either use the existing group, or specify a different group name.
- Cause:
- An attempt was made to access a group that does not exist.
- Action:
- Check the name of the group required. If available, use the popup list to specify the group name.
- Cause:
- The manager specified for a given user does not exist.
- Action:
- Check that the manager name specified for the given user is correct. If available, use the popup list to specify the manager's name.
- Cause:
- An attempt was made to add a user (or group) to a given group but the specified user (or group) is already a member of that group.
- Action:
- Check the name of the user (or group) being added.
- Cause:
- An attempt was made to access a user that does not exist.
- Action:
- Check the specified name of the user. If available, use the popup list to specify the user's name.
- Cause:
- There are no objects on which the specified privilege(s) have been granted to the given user.
- Action:
- Verify that the criteria specified is correct.
- Cause:
- An attempt was made to call the API with invalid parameter values.
- Action:
- Check the values for the parameters.
- Cause:
- An attempt was made to access a site but the specified site ID does not exist.
- Action:
- Check the ID of the site specified.
- Cause:
- An attempt was made to access a user but the specified user ID does not exist.
- Action:
- Check the ID of the user specified.
- Cause:
- An attempt was made to perform an operation but the user did not have sufficient privileges. This error message is displayed in OracleAS Portal when viewing pages, or editing page, layout or style.
- Action:
- Login to OracleAS Portal as a user with permissions to perform the operation. Alternatively, contact the portal administrator to request that the necessary privileges be granted.
- Cause:
- An attempt was made to login with incorrect password or username details.
- Action:
- Login again using a valid username and password combination. If your password is case-sensitive. enter the correct case for your password.
- Cause:
- While creating or editing a page, an invalid user or group name was specified when attempting to set access privileges for the page.
- Action:
- Check that the name for the user or group is valid. If available, use the popup list to specify the user or group name.
- Cause:
- An attempt was made to add a group as a member to itself.
- Action:
- Verify that the group being added as a member, is different from the group to which it is being added.
- Cause:
- An attempt was made to enter a group name but the specified name was invalid.
- Action:
- Verify that the specified group name is less than 50 characters in length, or less than 255 bytes in length (for multibyte character set databases).
- Cause:
- The Group Description specified was too long
- Action:
- Enter a Group Description that is less than 500 characters in length.
- Cause:
- When editing a user, an attempt was made to assign a database schema to the user's account but the specified database schema has not been granted connect privileges to the Portal schema.
- Action:
- Use the Schema portlet to create a new schema that can be assigned to users. Check the box that indicates "Use this Schema for Portal Users". To edit an existing schema for this purpose, select Edit Schema in the Schema portlet.
- Cause:
- OracleAS Portal was unable to construct the URL required to re-direct to the Single Sign-On Server. Partner application information may not configured correctly.
- Action:
- Contact the portal administrator and request that OracleAS Portal is re-registered with the OracleAS Single Sign-On Server.
- Cause:
- One or both of the following occurred:
- An alias defined in the Apache configuration caused Apache to translate host.domain.com to just host. If this is the case, the Login link only shows host:port (dropping the domain).
- The default domain was not set in the Apache configuration. When this occurs, only the hostname is shown in the Login link and the domain is not included.
- Action:
- Do one or both of the following:
- Remove all such aliases from your Apache configuration.
- Include the domain in the ServerName parameter.
- Cause:
- A login request was made using a very long URL.
- Action:
- Check the URL and reduce its length if it appears to be too long. There is no theoretical limit for the length of the URLs.
- Cause:
- The login URL was not constructed successfully. The reason is unknown. This problem can occur if OracleAS Portal was unable to communicate with another component.
- Action:
- Ensure all components in the system are configured properly, up and running, and functioning correctly.
- Cause:
- The option 'Allow User to Log On' was not checked for this user. The user may login to OracleAS Single Sign-On, but not OracleAS Portal.
- Action:
- Contact your portal administrator. Request that the 'Allow User to Log On' option is set for this user.
- Cause:
- The OracleAS Single Sign-On Server may not be operational.
- Action:
- Check whether the OracleAS Single Sign-On Server is up and running.
- Cause:
- The OracleAS Single Sign-On Server may not be operational.
- Action:
- Check whether the OracleAS Single Sign-On Server is up and running.
- Cause:
- An invalid or null argument was passed into this routine.
- Action:
- Check that valid parameter values are passed into this routine.
- Cause:
- There was no external application username mapping for the given user and the given application.
- Action:
- Login to the external application and save the login credentials in the password store by selecting the "Remember My Login Information" check box on the application login screen.
- Cause:
- The system has IP address checking enabled and the IP address from the client does not match the IP address associated with the original authentication. Using a proxy server can cause this problem.
- Action:
- Disable IP address checking if a proxy server is being used.
- Cause:
- The OracleAS Single Sign-On Server does not support the version of the URLC token specified in the partner application configuration.
- Action:
- Contact the portal administrator. Request that OracleAS Portal be re-registered with the OracleAS Single Sign-On Server.
- Cause:
- The URLC token received from the OracleAS Single Sign-On Server was not decrypted.
- Action:
- Contact the portal administrator to ensure that the OracleAS Portal configuration is correct. Request that OracleAS Portal be re-registered with the OracleAS Single Sign-On Server if required.
- Cause:
- The OID Server may not be operational.
- Action:
- Ask the portal administrator whether the OID server is operational.
- Cause:
- Multiple groups with the given name were found in the directory.
- Action:
- Use the popup list next to the name field to find the group name.
- Cause:
- This API has been deprecated.
- Action:
- Check the latest API documentation for alternatives to this API.
- Cause:
- The OID Server may not be operational.
- Action:
- Check whether the OID port is operational and that the Portal configuration is referring to the correct hostname and port. Use the command-line script 'ldapbind' to check if the LDAP port is up and running.
- Cause:
- The list of External Applications returned from the OracleAS Single Sign-On Server was too large.
- Action:
- Try reducing the character length of External Application names by renaming them.
- Cause:
- The Partner Application domain was not correctly set in the OracleAS Single Sign-On Server configuration.
- Action:
- Run the command line script 'ptlasst' in MIDTIER mode to configure the OracleAS Single Sign-On Server: ptlasst.csh -mode MIDTIER -type SSO
- Cause:
- The number of attempts to login with an incorrect password, exceeds the maximum number allowed (default is 10).
- Action:
- Contact your portal administrator to verify your password. Wait for the lockout duration to expire and attempt to login again.
- Cause:
- One or both of the following occurred:
- OracleAS Single Sign-On was using a stale user entry from its cache when transmitting user data to the Portal repository.
- The user profile for the specified username already existed in the Portal schema but it contains an incorrect Globally Unique Identifier.
- Action:
- Contact the Portal administrator to restart OracleAS Single Sign-On after disabling its cache. If the problem persists then request the Portal administrator to delete the existing local user profile using the wwsec_api.delete_portal_user API. Then login using that user's credentials.
- Cause:
- An attempt was made to access the Oracle Internet Directory.
- Action:
- Refer to the additional information displayed with this error message (if any) and take the appropriate action. Contact the portal administrator if additional information is not available.
- Cause:
- An action was attempted in the Oracle Internet Directory without sufficient access privileges.
- Action:
- Contact the portal administrator and request the necessary privileges be granted to perform this task.
- Cause:
- An attempt was made to access an OID entry that does not exist.
- Action:
- Check the value of the OID entry being accessed.
- Cause:
- An attempt was made to search for an attribute value that does not exist in the specified directory entry.
- Action:
- Check that the name of the attribute being searched is correct.
- Cause:
- Multiple matches were found for the specified criteria in the Oracle Internet Directory.
- Action:
- Verify that the specified search criteria is correct.
- Cause:
- An attempt was made to do one of the following:
- Add a user or group entry in OID which already exists.
- Add a owner/member to a group which has already been added.
- Action:
- Check the name of the user or group that is being added. Check it either as an owner, or as a member of a group.
- Cause:
- An attempt was made to call a portlet with an invalid reference.
- Action:
- Remove the portlet and then add it again.
- Cause:
- No external applications existed.
- Action:
- Add an external application. Portal administrators with single sign-on administrator privileges can add external applications.
- Cause:
- One of the following occurred:
- The portlet was customized to hide all external applications.
- No external application existed.
- Action:
- Do one of the following:
- Display one or more applications in the portlet.
- Add an external application. Portal administrators with single sign-on administrator privileges can add external applications.
- Cause:
- One of the following occurred:
- You tried to assign a group as your default group but you are not a member of that group.
- You do not have sufficient privileges.
- An error occurred while accessing the Oracle Internet Directory.
- Action:
- Make sure that you are already a member of the group when you assign it as your default group. Report the error to the Portal administrator and request that appropriate privileges be granted if needed.
- Cause:
- An attempt was made to set the default page but the specified page does not exist.
- Action:
- Specify a valid default page name.
- Cause:
- The name of the OracleAS Single Sign-On schema is not available in the preference store.
- Action:
- Re-register OracleAS Portal as a partner application.
- Cause:
- An attempt was made to construct the URL required to access the OracleAS Single Sign-On Server but the enabler configuration was not found. This can occur if the host and/or port information stored in the enabler configuration is removed after the user logged in.
- Action:
- Contact the portal administrator. Request that OracleAS Portal be re-registered with the OracleAS Single Sign-On Server.
- Cause:
- A null value was provided for a required attribute.
- Action:
- Specify an appropriate value for the attribute.
- Cause:
- An action was attempted but the user had insufficient privileges to perform the task.
- Action:
- Contact the portal administrator and request the necessary privileges be granted to perform this task.
- Cause:
- A message was sent to OracleAS Web Cache to invalidate an object, but the object was not found.
- Action:
- No action required.
- Cause:
- An attempt was made to register a provider but the name specified has already been used.
- Action:
- Specify a different provider name.
- Cause:
- A name for the provider was not specified.
- Action:
- Specify a provider name.
- Cause:
- The provider name specified was too long.
- Action:
- Enter a provider name that is less that 200 characters long.
- Cause:
- An implementation owner was not specified. This field is mandatory for database providers.
- Action:
- Enter an implementation owner.
- Cause:
- The implementation name was not specified. This field is mandatory for database providers.
- Action:
- Enter an implementation name.
- Cause:
- The implementation name specified was too long.
- Action:
- Enter an implementation name that is less than 2000 characters in length.
- Cause:
- The timeout specified was a negative value.
- Action:
- Either leave the timeout blank or enter a positive value.
- Cause:
- An invalid value for the login frequency was specified.
- Action:
- Set the login frequency to one of: Once, Always, Never, or Public.
- Cause:
- It was not possible to find the local portal node record.
- Action:
- Contact the portal administrator and report this error. This error indicates data corruption in the portal instance.
- Cause:
- A PL/SQL package implementing a provider had an 'INVALID' state. For example, the PL/SQL package may contain a syntax error, or reference a missing or invalid object.
- Action:
- Re-compile the PL/SQL package. If the compilation fails, resolve the errors reported.
- Cause:
- A PL/SQL package or package body implementing a provider was not found.
- Action:
- Ensure the schema and package name specified for the provider is correct and that the PL/SQL package has been created in the specified schema.
- Cause:
- An attempt was made to register a provider.
- Action:
- Ensure the provider is operational and that the registration details are correct.
- Cause:
- The URL specified for the Web provider is not valid, or null.
- Action:
- Enter the correct Web provider URL.
- Cause:
- It was specified that this provider required a proxy but the proxy definition provided was invalid.
- Action:
- Verify the proxy settings in the Global Settings page.
- Cause:
- The Web provider had an invalid value for the HTTP application type.
- Action:
- Ensure that the HTTP application type is one of EXTERNAL_SECURED, PORTAL or null. Constants are defined for these values in the public API package named WWPRO_API_PROVIDER_REGISTRY.
- Cause:
- The external application ID specified was not valid.
- Action:
- Use the list of values provided to select a valid value, or leave this field blank.
- Cause:
- An attempt was made to convert a string into a number.
- Action:
- Review the reported error and take the appropriate action.
- Cause:
- An attempt was made to convert a string into a date.
- Action:
- Review the reported error and take the appropriate action.
- Cause:
- The portlet content type specified was invalid.
- Action:
- Ensure that the portlet's content type is one of text/html or text/xml.
- Cause:
- The shared key specified was not valid.
- Action:
- Enter a key that is 10-30 characters in length.
- Cause:
- A call to the Web provider failed with the specified error.
- Action:
- Review the reported error and take the appropriate action.
- Cause:
- You have entered an invalid name.
- Action:
- Enter a name that contains only letters, numbers, and underscores.
- Cause:
- The URL specified was either incorrect or the provider was not running. The portal could not contact the provider using the specified URL.
- Action:
- Verify that the URL specified during provider registration is correct and that the provider is up and running. One way to verify this for a Web provider is to enter its URL in a browser. If the provider information is correct and the provider is up, the provider's test page is displayed. If the URL is correct, and the provider is up, then there may be some problem with the configuration of the portal repository. Contact your portal administrator to enable debug logging in the portal repository and view the log information.
- Cause:
- An attempt was made to register a provider that contains portlets and where the portlet names or portlet IDs are not unique within that provider.
- Action:
- Contact the developer responsible for the provider and request that this issue be resolved.
- Cause:
- A portlet ID was invalid or null.
- Action:
- Contact the developer responsible for the provider and request that this issue be resolved.
- Cause:
- A portlet ID was not in a valid range.
- Action:
- Contact the developer responsible for the provider and request that this issue be resolved.
- Cause:
- A portlet name was null.
- Action:
- Contact the developer responsible for the provider and request that this issue be resolved.
- Cause:
- A portlet name contained space characters.
- Action:
- Contact the developer responsible for the provider and request that this issue be resolved.
- Cause:
- Cookies created by this provider are forwarded to the user's browser and managed by the browser instead of OracleAS Portal. Once managed by the browser, the cookies are sent to any other Web server that:
- is accessed within the same browser session,
- falls within the relaxed scope specified when the cookie was created.
- Action:
- This can result in cookie collisions and errors/loss of sessions in unrelated Web applications. To minimize the possibility of cookie collisions, ensure that:
- Any custom cookies created by the Web provider have names that are unique to that Web provider.
- All portal instances accessed using the Federated Portal Adapter are configured with different DAD names.
- PDK-Java release 1 (JServ) Web providers requiring this setting are installed in uniquely named JServ servlet zones.
- PDK-Java release 2 (OC4J) Web providers do not use this setting if they use servlet sessions. This is because the cookie used to identify the session is always called "JSESSIONID". This name is specified in the Servlet 2.3 specification. Relaxing the scope of a JSESSIONID cookie almost certainly causes session related problems to occur in other, unrelated, Web applications.
- Cause:
- Ensure that the show mode for the request is one of: MODE_SHOW, MODE_SHOW_ABOUT, MODE_SHOW_EDIT, MODE_SHOW_HELP, MODE_SHOW_EDIT_DEFAULTS, MODE_SHOW_DETAILS, MODE_PREVIEW or MODE_LINK. Note that these constants are defined in the public API package named WWPRO_API_PROVIDER.
- Action:
- A show request was made to a portlet with an invalid show mode.
- Cause:
- The portlet returned an invalid implementation type.
- Action:
- Ensure that the portlet implementation type is one of: PLSQL_IMPL or HTTP_IMPL. These constants are defined in the public API package named WWPRO_API_PROVIDER_REGISTRY.
- Cause:
- A Web provider portlet was called by the PL/SQL API that was created to show PL/SQL portlets.
- Action:
- Contact the portal administrator. This message indicates data corruption.
- Cause:
- Either an attempt was made to update the portlet's access control list (ACL), or the portlet is offline.
- Action:
- Contact the portal administrator. Ask to be granted the required privileges, or ensure that the portlet is online.
- Cause:
- The specified portlet was not found in the Portlet Metadata Repository. This error suggests data corruption.
- Action:
- Refresh the provider that contains this portlet and attempt the operation again.
- Cause:
- An attempt was made to access the portlet but the current user had insufficient privileges.
- Action:
- Contact the portal administrator. Ask to be granted access to the portlet.
- Cause:
- An attempt was made to access a portlet but its provider was offline.
- Action:
- Ensure that the provider is online and attempt the operation again.
- Cause:
- The specified provider group was not found in the portal repository.
- Action:
- Check that the name of the provider group requested is correct.
- Cause:
- The provider group specified is already registered with the OracleAS Portal.
- Action:
- This error suggests data corruption. Contact the portal administrator.
- Cause:
- An attempt was made to register a provider group but a provider group with the same details has already been registered with Oracle Portal.
- Action:
- Use the provider group previously registered with these details.
- Cause:
- An attempt was made to specify a page name that already exists.
- Action:
- Specify a different name or the page.
- Cause:
- A display name was not specified when creating a style or when copying a style.
- Action:
- Ensure that a display name is specified for the style.
- Cause:
- An attempt was made to split a region that has already been split.
- Action:
- Specify a different region, that is, one which is not already split.
- Cause:
- An attempt was made to create a region but a region with the specified name already exists.
- Action:
- Specify a unique name for the region.
- Cause:
- An attempt was made to delete, split, edit, or copy a region but the specified region could not be found.
- Action:
- Specify a valid region.
- Cause:
- An attempt was made to delete the main region of a page but the main region can not be deleted unless the page is deleted.
- Action:
- Specify a different region for deletion.
- Cause:
- An attempt was made to edit the width of a region but a non-numeric value was provided.
- Action:
- Ensure that the width value is an integer value (preferably between 1 and 100). If the width is a relative width, specify the % symbol (e.g. 65%). If the width is an absolute width, then specify only the numeric value (e.g. 35).
- Cause:
- Name and display name values were not provided for a page.
- Action:
- Ensure that name and display name values are provided for the page. These values may not be null.
- Cause:
- An attempt was made to modify a style but the user did not have sufficient privileges.
- Action:
- Login to OracleAS Portal as a user with permissions to perform the operation. Alternatively, contact the portal administrator to request that the necessary privileges be granted.
- Cause:
- An attempt was made to set the default page for a user or page group but the operation failed.
- Action:
- Attempt this task again. If the problem persists, contact the portal administrator.
- Cause:
- An attempt was made to access a style but the specified style name and page group ID does not exist.
- Action:
- Provide a valid style name and page group ID.
- Cause:
- A display name was not specified when creating or copying a layout.
- Action:
- Enter a display name for the layout.
- Cause:
- The value specified for a URL attribute did not begin with a valid protocol such as http://, https://, or ftp://.
- Action:
- Correct the URL, entering a valid protocol.
- Cause:
- An attempt was made to view or edit an OracleAS Portal page but the specified page did not exist.
- Action:
- Check that the specified page name or page ID is correct.
- Cause:
- An attempt was made to delete a system default page. Such pages can not be deleted.
- Action:
- Do not attempt to delete this page.
- Cause:
- An attempt was made to set a page group's default navigation page but the specified navigation page did not exist.
- Action:
- Select a different navigation page to be the page group's default navigation page.
- Cause:
- An attempt to access a portlet failed because the provider and/or portlet was not found.
- Action:
- Ensure the provider is online, the portlet is available and that the user has permission to access the provider/portlet.
- Cause:
- When editing a region, an attempt was made to specify a non-numeric value for the "Space between Portlets" property.
- Action:
- Ensure that this value is an integer value (preferably between 1 and 100). If no space between portlets is required, set this value to '0' or 'null'.
- Cause:
- When editing a region, an attempt was made to specify a non-numeric value for the "Space around Portlets" property.
- Action:
- Ensure that this value is an integer value (preferably between 1 and 100). If no space around portlets is required, set this value to '0' or 'null'.
- Cause:
- An attempt to create a tab failed. Either the specified tab name was invalid, or the user did not have permission to add a tab.
- Action:
- If the logged on user has permission to perform the operation, check that the specified tab name is valid.
- Cause:
- An attempt to edit a tab failed. Either the specified tab name was invalid, or the user did not have permission to edit a tab.
- Action:
- If the logged on user has permission to perform the operation, check that the specified tab name is valid.
- Cause:
- An attempt to create a page parameter failed.
- Action:
- Refresh the screen and verify that the page is still available.
- Cause:
- An attempt to re-order page parameters failed.
- Action:
- Refresh the screen and verify that both the page and page parameter are still available.
- Cause:
- An attempt to delete a page parameter failed.
- Action:
- Refresh the screen and verify that both the page and page parameter are still available.
- Cause:
- An attempt to edit the value of a page parameter failed.
- Action:
- Refresh the screen and verify that the page parameter is still available.
- Cause:
- The specified page parameter name was invalid.
- Action:
- Enter a valid page parameter name. Refer to the Page Properties Parameter tab for a list of valid page parameter names.
- Cause:
- An attempt to edit the value of a portlet parameter failed.
- Action:
- Refresh the screen and verify that the portlet parameter is still available.
- Cause:
- An attempt to customize a page parameter failed.
- Action:
- Refresh the screen and verify that the page parameter is still available.
- Cause:
- An attempt to reset page parameter to default values failed.
- Action:
- Refresh the screen and verify that the customization screen is still available.
- Cause:
- An attempt to fetch portlet parameters failed.
- Action:
- Refresh the screen and verify that the portlet is still available.
- Cause:
- An attempt to edit the value of an event parameter failed.
- Action:
- Refresh the screen and verify that the event parameter is still available.
- Cause:
- An attempt to link an event to a page failed.
- Action:
- Refresh the screen and verify that both the event and the page are still available.
- Cause:
- An attempt to remove a link from an event failed.
- Action:
- Refresh the screen and verify that the event is still available.
- Cause:
- An attempt to update the target page for an event failed.
- Action:
- Refresh the screen and verify that both the event and the page are still available.
- Cause:
- The specified event output name was invalid.
- Action:
- Enter a valid event output name.
- Cause:
- The name specified has already been used.
- Action:
- Specify a different, unique name.
- Cause:
- An attempt to create a parameter failed.
- Action:
- Refresh the screen and verify that the parent object is still available.
- Cause:
- An attempt to edit a parameter failed.
- Action:
- Refresh the screen and verify that the parent object is still available.
- Cause:
- An attempt to customize a parameter failed. The parameter can not be customized.
- Action:
- Refresh the screen and verify that the parameter is not customizable.
- Cause:
- An attempt to delete a parameter failed.
- Action:
- Refresh the screen and verify that the parent object and the parameter are still available.
- Cause:
- The specified parameter was not found.
- Action:
- Refresh the screen, verify that the parent object is still available and that the user has access permissions.
- Cause:
- An attempt to search for a parameter failed.
- Action:
- Refresh the screen, verify that the object is still available and that and that the user has access permissions.
- Cause:
- An attempt to create a parameter map failed.
- Action:
- Refresh the screen and verify that the parent object is still available.
- Cause:
- An attempt to edit a parameter map failed.
- Action:
- Refresh the screen and verify that the parent object is still available.
- Cause:
- The source object type specified is not supported.
- Action:
- Select a different source object.
- Cause:
- An attempt was made to move a parameter up in the display order even though it is first in the list.
- Action:
- Refresh the screen and verify that the parameter is first in the list.
- Cause:
- An attempt to move a parameter up in the display order failed.
- Action:
- Refresh the screen and verify that the parameter is still available.
- Cause:
- The specified flow element was not found.
- Action:
- Refresh the screen and verify that the dependent object is still available.
- Cause:
- An attempt to create a flow link failed.
- Action:
- Refresh the screen and verify that the parent page is still available.
- Cause:
- An attempt to delete a flow link failed.
- Action:
- Refresh the screen and verify that the parent page is still available.
- Cause:
- The specified flow link was not found.
- Action:
- Refresh the screen and verify that the parent page is still available.
- Cause:
- The parent object did not have a valid type.
- Action:
- Refresh the screen and verify that the parent object is still available.
- Cause:
- An attempt was made to specify a parent object that was not a portlet.
- Action:
- Specify a portlet.
- Cause:
- The specified event name already exists.
- Action:
- Enter a different, unique event name.
- Cause:
- An attempt to create an event failed.
- Action:
- Refresh the screen and verify that the parent object is still available.
- Cause:
- An attempt to delete an event failed.
- Action:
- Refresh the screen and verify that the event is still available.
- Cause:
- An attempt to delete events failed.
- Action:
- Refresh the screen and verify that the events are still available.
- Cause:
- The specified event was not found.
- Action:
- Refresh the screen and verify that the parent object is still available.
- Cause:
- The specified event was not found.
- Action:
- Refresh the screen and verify that the parent object is still available.
- Cause:
- The specified events were not found.
- Action:
- Refresh the screen and verify that the parent objects are still available.
- Cause:
- An attempt to create an event map failed.
- Action:
- Refresh the screen and verify that the event is still available.
- Cause:
- An attempt to delete an event map failed.
- Action:
- Refresh the screen and verify that the event map is still available.
- Cause:
- The specified event map was not found.
- Action:
- Verify that the parent object is still available.
- Cause:
- The specified parameter map was not found.
- Action:
- Refresh the screen, verify that the parent object is still available and that the user has access permissions.
- Cause:
- An attempt to duplicate an event map failed.
- Action:
- Edit or delete the existing event map, or create a new event map.
- Cause:
- An attempt to fetch portlet events failed.
- Action:
- Refresh the screen and verify that the portlet is still available.
- Cause:
- An attempt to retrieve a link from an event failed.
- Action:
- Refresh the screen and verify that the event is still available.
- Cause:
- An attempt to retrieve the target page for an event failed.
- Action:
- Refresh the screen and verify that the event is still available.
- Cause:
- An attempt to write parameter map metadata failed.
- Action:
- Refresh the screen and verify that the parameter map is still available.
- Cause:
- An attempt to add a display name or description for an event failed.
- Action:
- Refresh the screen and verify that the event is still available.
- Cause:
- An attempt to edit an event failed.
- Action:
- Refresh the screen and verify that the event is still available.
- Cause:
- An attempt to create a page event from a portlet event failed.
- Action:
- Refresh the screen and verify that the portlet event is still available.
- Cause:
- An attempt to invalidate the page cache after updating an event failed.
- Action:
- Refresh the screen and verify that the event or dependent object is still available.
- Cause:
- The parent object (portlet, page, or event) for the parameter was not valid.
- Action:
- Refresh the screen and verify that the parent object still exists.
- Cause:
- An attempt to update a parameter failed.
- Action:
- Refresh the screen and verify that the parameter and/or dependent object are still available.
- Cause:
- The specified page was not found.
- Action:
- Verify that the page exists and that the details of the specified page are correct.
- Cause:
- An attempt was made to specify a template for the page but the specified template was not found.
- Action:
- Specify a valid template.
- Cause:
- An invalid system variable was provided.
- Action:
- Enter a valid system variable, one of USER_NAME, USER_ID, COMPANY_NAME, SUBSCRIBER_ID, NLS_LANG, NLS_TERRITORY
- Cause:
- An attempt to update a parameter map failed.
- Action:
- Refresh the screen and verify that the parameter map and/or the dependent objects are still available.
- Cause:
- An attempt to delete children of a flow link failed.
- Action:
- Refresh the screen and verify that the dependent objects are still available.
- Cause:
- An attempt to delete parameter maps failed.
- Action:
- Refresh the screen and verify that the dependent objects are still available.
- Cause:
- An attempt was made to download a JSP file from a non-JSP page.
- Action:
- Choose a JSP page to download.
- Cause:
- An attempt was made to download a JSP file of a JSP page but the user did not have the correct permissions.
- Action:
- Login to OracleAS Portal as a user with permissions to perform the operation.
- Cause:
- The selected template does not have an item region or a portlet region for the items or portlets on the page.
- Action:
- Choose another template. Ensure that the template contains the region type(s) required.
- Cause:
- An attempt was made to create a navigation page but the display name was not specified.
- Action:
- Specify a valid display name.
- Cause:
- An attempt to refresh the portlet repository failed.
- Action:
- This page is published as a portlet. Refresh the repository manually.
- Cause:
- An attempt was made to access a portlet with a given portlet ID and provider ID, using the API call 'wwsbr_folder_portlet.describe_parameters'. The specified portlet was not found.
- Action:
- Ensure that both the specified provider ID and portlet ID are correct.
- Cause:
- An attempt was made to access a document that does not exist, or is no longer accessible.
- Action:
- Verify that the specified URL is still valid, if applicable. Visit the parent page to check that the item still exists.
- Cause:
- An attempt was made to upload a file that exceeds the maximum size allowed per file.
- Action:
- Reduce the size of the file, or contact the portal administrator and request that the maximum permitted file size is increased.
- Cause:
- An attempt was made to upload a file that would exceed the allocated space quota.
- Action:
- Create some free space by deleting other documents, or contact the portal administrator and request that the quota allocation be increased.
- Cause:
- An attempt to access the Oracle Internet Directory failed.
- Action:
- Wait for a while and attempt the operation again. Contact the portal administrator if the problem persists.
- Cause:
- Invalid values were specified for input parameters.
- Action:
- Check the specified input parameter values.
- Cause:
- The user specified was not a member of any group.
- Action:
- Check the specified user name.
- Cause:
- An attempt was made to access a subscriber that does not exist in the directory.
- Action:
- Check the name of the subscriber required.
- Cause:
- The user specified does not exist in the directory.
- Action:
- Check the specified name of the user.
- Cause:
- The root Oracle Context was not found in the directory.
- Action:
- Check the OID Server configuration and ensure the root Oracle Context information is loaded properly.
- Cause:
- Multiple subscriber entries with the same subscriber nickname were found in the Oracle Internet Directory.
- Action:
- Ensure that the nickname attribute of subscribers in the Oracle Internet Directory are unique.
- Cause:
- The root Oracle Context level was not found.
- Action:
- Check the OID Server configuration and make sure that the root Oracle Context information is loaded properly.
- Cause:
- Oracle Context was not found for the subscriber.
- Action:
- Check the OID Server configuration and make sure the subscriber Oracle Context information is loaded properly.
- Cause:
- Oracle Context for the subscriber was invalid.
- Action:
- Check the OID Server configuration and make sure the subscriber Oracle Context information is loaded properly.
- Cause:
- Multiple users with the given name were found in the directory.
- Action:
- Use the popup list next to the name field to specify the user name.
- Cause:
- An attempt was made to access a group that does not exist in the directory.
- Action:
- Check the name of the group required.
- Cause:
- Multiple groups with the given name were found in the directory.
- Action:
- Check that group name is valid. Use the popup list next to the name field to specify the group name.
- Cause:
- The number of failed login attempts exceeds the maximum number allowed, as specified by the password policy. The user account has been locked.
- Action:
- Contact the portal administrator and request that the password be reset. Alternatively, wait for the lockout period to expire.
- Cause:
- Notification that password details must be updated.
- Action:
- Change password details, as requested.
- Cause:
- An attempt was made to authenticate but the login credentials were incorrect.
- Action:
- Enter the correct login credentials.
- Cause:
- Notification that a password has expired.
- Action:
- Contact the portal administrator and request that the password be reset.
- Cause:
- An unexpected condition was encountered.
- Action:
- Report this error to Oracle Customer Support. Include the attempted operations that led to the error, any unusual circumstances that occurred before receiving this error message, and the complete stack trace produced by this error.
- Cause:
- An unexpected condition was encountered.
- Action:
- Report this error to Oracle Customer Support. Include the attempted operations that led to the error, any unusual circumstances that occurred before receiving this error message, and the complete stack trace produced by this error.
- Cause:
- Notification that a password is about to expire.
- Action:
- Change the password before it expires.
- Cause:
- A specified password was less than the minimum required size for a password.
- Action:
- Specify a password that is equal to, or greater than, the minimum required password size. If necessary, contact the portal administrator to establish the minimum required size of passwords.
- Cause:
- A specified password did not contain the minimum number of numeric characters required.
- Action:
- Specify a password that contains at least the minimum number of numeric characters. If necessary, contact the portal administrator to establish the minimum number of numeric characters required for passwords.
- Cause:
- A null value was specified for a password.
- Action:
- Specify a valid password value.
- Cause:
- An attempt was made to change a user password but the new password specified was the same as the previous password.
- Action:
- Specify a new password value that is different from the previous password.
- Cause:
- An attempt was made to specify a password containing one or more illegal characters.
- Action:
- Specify a password value that does not contain any illegal characters.
- Cause:
- Notification that the user password has just expired. The user has been given the chance to login and change the password.
- Action:
- Change the password as soon as possible.
- Cause:
- Notification that the user password has expired.
- Action:
- Contact the portal administrator to change the password.
- Cause:
- An unexpected condition was encountered.
- Action:
- Report this error to Oracle Customer Support. Include the attempted operations that led to the error, any unusual circumstances that occurred before receiving this error message, and the complete stack trace produced by this error.
- Cause:
- Notification that an account has been disabled.
- Action:
- Contact the portal administrator and request that the account be enabled.
- Cause:
- An unexpected condition was encountered.
- Action:
- Report this error to Oracle Customer Support. Include the attempted operations that led to the error, any unusual circumstances that occurred before receiving this error message, and the complete stack trace produced by this error.
- Cause:
- The connection parameters specified were not available.
- Action:
- Run the command line script 'ptlasst' in MIDTIER mode to configure the OID connection parameters: ptlasst.csh -mode MIDTIER -type OID
- Cause:
- An attempt to configure a page group failed.
- Action:
- Refresh the screen and verify that the page group is still available.
- Cause:
- An attempt to write parameter metadata failed.
- Action:
- Refresh the screen and verify that the parameter is still available.
- Cause:
- The parent object ID was not valid.
- Action:
- Refresh the screen and verify that the parent object is still available.
- Cause:
- An attempt to update a flow link failed.
- Action:
- Refresh the screen and verify that the dependent pages are still available.
- Cause:
- The format of the portlet instance reference path was incorrect. The correct format is "<id>_<portletname>_<providerid>".
- Action:
- Enter correct values and use the correct reference path format.
- Cause:
- The write operation of the file completed, but the comments for it failed.
- Action:
- Check the WebDAV error file in your Personal Page for possible reasons why this has occurred.
- Cause:
- A redirect required to get to the requested collection has failed.
- Action:
- Check that the re-directed URL is valid and WebDAV is setup correctly for this portal.
- Cause:
- The requested document does not exist in the location specified.
- Action:
- In OracleAS Portal, check whether the document is accessible. If it is accessible, there is an internal error. Contact Oracle Customer Support.
- Cause:
- No lock was associated with this resource.
- Action:
- To create a lock, check it out using the lock command.
- Cause:
- An attempt was made to perform an operation but the user does not have the necessary privileges to perform the task.
- Action:
- If applicable, contact the portal administrator and request that privileges be granted to perform such operations.
- Cause:
- The version of the OraDAV module on the middle-tier and its database counterpart do not match.
- Action:
- Check your installation.
- Cause:
- The version of the OraDAV module on the middle-tier and its database counterpart do not match.
- Action:
- Check your installation.
- Cause:
- The argument value specified is not valid.
- Action:
- Check that the values supplied for all arguments are valid.
- Cause:
- An attempt to perform an operation on a document failed.
- Action:
- Check the permissions of the user, security on the document and the status of the document.
- Cause:
- The version of the OraDAV module on the middle-tier does not match the drivers in the database.
- Action:
- Check the installation and that all necessary patches have been applied.
- Cause:
- The document requested was checked out.
- Action:
- Check in or undo the check out for the document to release the lock.
- Cause:
- The document found was a file when a directory was expected. Or, the document found was a directory when a file was expected.
- Action:
- Check that the operation attempted is valid for this type of resource.
- Cause:
- The document specified is already exposed to the client.
- Action:
- None.
- Cause:
- The directory specified exists and is not empty.
- Action:
- Check the WebDAV error file in your Personal Page for possible reasons why this error occurred.
- Cause:
- One of the internal WebDAV tables contains invalid data.
- Action:
- Use the DAV Loader utility (wwdav_loader) to repopulate the WebDAV tables with the latest data available from OracleAS Portal.
- Cause:
- An attempt to open a log file failed as it was already open.
- Action:
- If necessary, close the log file.
- Cause:
- An attempt was made to drop repository objects but some of the objects do not exist.
- Action:
- Check your installation.
- Cause:
- The specified resource already exists.
- Action:
- Check the WebDAV error file in your Personal Page for possible reasons why the error occurred.
- Cause:
- The specified resource was not found.
- Action:
- Check the WebDAV error file in your Personal Page for possible reasons why this error occurred.
- Cause:
- An attempt to delete a resource failed as the requested resource was open and in use elsewhere.
- Action:
- Ensure that the resource is not in use before attempting to delete it.
- Cause:
- An internal error has occurred.
- Action:
- Check the WebDAV error file in your Personal Page for possible reasons why this error occurred.
- Cause:
- An error occurred while trying to return a multistatus response for the requested operation.
- Action:
- Check the WebDAV error file in the user's personal page and the Oracle HTTP Server error log file.
- Cause:
- An attempt to upload a document failed. The size quota permitted was exceeded.
- Action:
- Check the page group quota and if necessary, free up some space.
- Cause:
- An attempt to perform an operation failed.
- Action:
- Check the permissions of the user and also whether this operation is permitted.
- Cause:
- No Personal Page was found for the logged in user.
- Action:
- Create a Personal Page (for this user) into which the WebDAV error log file can be placed.
- Cause:
- No item region was available on the Personal Page for the logged in user.
- Action:
- Create an item region on the Personal Page for this user, in which the WebDAV error log file can be placed.
- Cause:
- A WebDAV error log file item does not exist.
- Action:
- Create the WebDAV error log file item in the user's Personal Page.
- Cause:
- An internal error occurred.
- Action:
- Check the WebDAV error log file in the user's Personal Page. for possible reasons why this error occurred. Also check the Apache error log file.
- Cause:
- The preference required for the WebDAV error log file was not created.
- Action:
- Check the Apache error log file for possible reasons why this error occurred.
- Cause:
- It was not possible to place a file type in the default page region.
- Action:
- Check the value of the region type. Ensure it allows file types to be uploaded.
- Cause:
- An attempt to write to the WebDAV error log file failed. Either the WebDAV error log file does not exist, can not be found, or can not be created.
- Action:
- Check whether the WebDAV error log exists.
- Cause:
- No item types were specified for the page group.
- Action:
- Select some allowable item types for the page group.
- Cause:
- An internal error occurred.
- Action:
- Check the WebDAV error file in the user's Personal Page for possible reasons why this error occurred.
- Cause:
- It was not possible to create the WebDAV error log file as the user name was not supplied.
- Action:
- Check the Apache error log file for possible reasons why this error occurred.
- Cause:
- The attempted operation failed to complete.
- Action:
- Check the WebDAV error file in the user's Personal Page for possible reasons why this error occurred.
- Cause:
- The attempted operation failed to complete.
- Action:
- Check the WebDAV error file in the user's Personal Page for possible reasons why this error occurred.
- Cause:
- The attempted operation failed to complete.
- Action:
- Check the WebDAV error file in the user's Personal Page for possible reasons why this error occurred.
- Cause:
- The attempted operation failed to complete.
- Action:
- Check the WebDAV error file in the user's Personal Page for possible reasons why this error occurred.
- Cause:
- It was not possible to update the last modified date as it is not a directory.
- Action:
- Check the WebDAV error file in the user's Personal Page for possible reasons why this error occurred.
- Cause:
- An attempt was made to delete the top level directory but this is not allowed.
- Action:
- None.
- Cause:
- An attempt was made to update the top level directory but this is not allowed.
- Action:
- None.
- Cause:
- The attempted operation is not permitted.
- Action:
- None.
- Cause:
- The attempted operation is not permitted.
- Action:
- None.
- Cause:
- The attempted operation is not permitted.
- Action:
- None.
- Cause:
- The attempted operation failed to complete.
- Action:
- Check the WebDAV error file in the user's Personal Page for possible reasons why this error occurred.
- Cause:
- The document specified is checked out.
- Action:
- Check in, or undo the check out for the document to release the lock.
- Cause:
- An attempt was made to check out a directory but this is not supported.
- Action:
- None.
- Cause:
- An attempt was made to modify a directory but the user did not have sufficient privileges.
- Action:
- If applicable, contact the portal administrator and request that privileges be granted to perform this operation.
- Cause:
- The resource cannot be found in the underlying tables.
- Action:
- Check the WebDAV error file in the user's Personal Page for possible reasons why this error occurred.Also check the Apache error log file.
- Cause:
- It was not possible to check for locks at the given level in the directory hierarchy
- Action:
- Check the WebDAV error file in the user's Personal Page for possible reasons why this error occurred.Also check the Apache error log file.
- Cause:
- The attempted operation failed. It is not possible to perform any operations on this resource until it has been submitted to the approval system.
- Action:
- To allow modifications, submit it to the approval system and approve it, if the user is not an approver or owner of the document.
- Cause:
- The attempted operation failed. It is not possible to perform any operations on this resource until it has been submitted to the approval system.
- Action:
- Wait until the document has been submitted to the approval system.
- Cause:
- The attempted action required (implicitly or explicitly) that a DAV resource be moved or removed, for example, a file or image item. The operation failed because the resource was locked, either by a DAV client, or it has been checked out. When a resource is locked it indicates that someone is actively using the resource and therefore it is not appropriate to move or remove the resource.
- Action:
- Determine why the item is locked (or checked out) and, if safe to do so, unlock (or check-in)the item and attempt the operation again.
- Cause:
- The menu action specified in the request is not supported by this portal.
- Action:
- Verify the Portal WebDAV URL and make sure it is pointing to the correct address.
- Cause:
- Item Level Security is not enabled on this document.
- Action:
- Contact your portal administrator. Request that Item Level Security is enabled on the document for which access control is required.
- Cause:
- An internal error occurred.
- Action:
- Contact Oracle Customer Support.
- Cause:
- An attempt was made to update a resource that is pending approval. . The version in the approval process remains locked until it is either rejected or approved.
- Action:
- Wait for the resource to be approved or rejected and attempt the operation again.
- Cause:
- The item cannot be approved or rejected because it has already been approved.
- Action:
- Refresh your browser window to update your notifications. The item you were trying to approve or reject will no longer be listed.
- Cause:
- The item cannot be approved or rejected because it has already been rejected.
- Action:
- Refresh your browser window to update your notifications. The item you were trying to approve or reject will no longer be listed.
- Cause:
- Viewing the item required an appropriate privilege.
- Action:
- Ask the page group administrator or page manager to grant you the appropriate privilege.
- Cause:
- The change was rejected because the approval process definition had items pending approval.
- Action:
- Wait until all the pending items are approved, then try again.
- Cause:
- A non-numeric value was entered.
- Action:
- Enter a valid number value.
- Cause:
- The value that was entered was not one of the values from the LOV.
- Action:
- Enter a valid value from the LOV.
- Cause:
- An action was attempted on an item that no longer exists.
- Action:
- Refresh the page so that it displays the current content.
- Cause:
- The PL/SQL code associated with the current page executed with errors.
- Action:
- Check the validity of the PL/SQL code that executes when the current page is viewed.
- Cause:
- No value was found for the custom attribute associated with the current page.
- Action:
- Edit the properties for the current page, and provide values for the custom attributes associated with it.
- Cause:
- A search (submission) portlet submitted a search to a search (results) portlet. The results portlet was customized to show results from a specific set of page groups that did not include any of the page groups chosen in the submission portlet.
- Action:
- Change the list of page groups chosen for the submission portlet or those chosen for the results portlet so that both portlets refer to a common set of page groups.
- Cause:
- A search (submission) portlet submitted a search to a search (results) portlet. The page groups selected for the results portlet were not all the same as those selected for the submission portlet. Only those page groups common to the submission portlet and the results portlet were searched.
- Action:
- Change the list of page groups chosen for the submission portlet or those chosen for the results portlet so that both portlets refer to a common set of page groups.
- Cause:
- A search (submission) portlet submitted a search to a search (results) portlet. The submission portlet searched a list of page groups that were chosen as the defaults for that portlet. The results portlet was customized to show results from a specific set of page groups, none of which were common to the submission portlet.
- Action:
- Change the default list of page groups for the submission portlet, or change the customizations in the Edit Defaults of the results portlet, so that both portlets refer to a common set of page groups.
- Cause:
- A search (submission) portlet submitted a search to a search (results) portlet. The page groups identified for the submission portlet were not all the same as those identified for the results portlet. Only the page groups common to the submission portlet's default page groups and the result portlet's customizations were searched.
- Action:
- Change the default list of page groups for the submission portlet, or change the customizations in the Edit Defaults of the results portlet, so that both portlets refer to a common set of page groups.
- Cause:
- An expiry time was specified that is not an integer between 1 and 1440 minutes.
- Action:
- Enter an expiry time that is an integer between 1 and 1440 minutes.
- Cause:
- Searching capabilities could not be used because not all the Oracle Text indexes were present and valid.
- Action:
- Ensure that the Oracle Text indexes are present and valid. If necessary, create or recreate the indexes.
- Cause:
- Oracle Text encountered an error when trying to create the preference or section group.
- Action:
- Review the diagnostics logs for other messages. Correct the errors, and try again.
- Cause:
- Oracle Text encountered an error when trying to remove the preference or section group.
- Action:
- Review the diagnostics logs for other messages. Correct the errors, and try again.
- Cause:
- Oracle Text encountered an attribute it does not find in its indexes.
- Action:
- Oracle Text indexes must be updated to include the new attribute. Oracle Text indexes are updated automatically. Either wait until the indexes are updated, or use a different search attribute.
- Cause:
- No value was specified for the Oracle Text Base URL.
- Action:
- Specify a value for the Oracle Text Base URL. This should normally be the URL to the portal instance, up to and including the portal DAD. For example, http://hostname.domain:port/pls/dad/
- Cause:
- A URL was specified for the Internet Search Engine preference, but Link Text was not specified.
- Action:
- Specify Link Text for the Interent Search Engine.
- Cause:
- The item specified was not a valid image.
- Action:
- Choose an item that is a valid image.
- Cause:
- A value specified for the results-per-page was not an integer greater than zero.
- Action:
- Specify a value for the results-per-page that is an integer greater than zero.
- Cause:
- The page that this item belongs to does not exist.
- Action:
- Refresh the page, and try to edit the item again.
- Cause:
- This item does not exist.
- Action:
- Refresh the page, and try to edit the item again.
- Cause:
- This error occurs when an internal API is called to retrieve a style setting value and the setting name or its type are not provided.
- Action:
- Provide the setting name and type.
- Cause:
- An attempt was made to make a page the subpage of itself.
- Action:
- Choose another page as the parent of the page.
- Cause:
- This error occurs when one user attempts to update page group properties while another user is doing so.
- Action:
- Close the page group properties screen, and reload it.
- Cause:
- A page group name was not supplied during the creation or edit of a page group.
- Action:
- Provide a valid name for the page group.
- Cause:
- A display name was not specified.
- Action:
- Specify a display name.
- Cause:
- No name was specified for the perspective.
- Action:
- Enter a unique name for the perspective. The name must not already be used in this page group nor the Shared Objects page group.
- Cause:
- The category name cannot be null.
- Action:
- Enter a unique name for the category. The name must not already be used in this page group nor the Shared Objects page group.
- Cause:
- This operation could not be performed because the user did not have the required privilege.
- Action:
- Ask the page group administrator or page manager to grant you the required privilege.
- Cause:
- A perspective with this name already exists in this page group or in the Shared Objects page group. The perspective name must be unique within its own page group and the Shared Objects page group.
- Action:
- Enter a unique perspective name. The name must not already be used in this page group nor the Shared Objects page group.
- Cause:
- A category with this name already exists in this page group or in the Shared Objects page group. The category name must be unique within its own page group and the Shared Objects page group.
- Action:
- Enter a unique category name. The name must not already by used in this page group nor the Shared Objects page group.
- Cause:
- The value entered for the TEXT attribute exceeds 32K.
- Action:
- Enter a text value that does not exceed 32K.
- Cause:
- The name specified for the item was not unique.
- Action:
- Specify a name that is unique across all the items on this page as well as all the tabs and subpages of this page.
- Cause:
- A style name was not provided during the creation or edit of the style.
- Action:
- Provide a valid style name.
- Cause:
- An invalid value was entered for a number attribute. It is possible that the LOV associated with the attribute returns incorrect values.
- Action:
- Request that the owner of the LOV change it to return the correct type of values.
- Cause:
- The style name entered was not unique.
- Action:
- Enter a unique style name, one that is not used in the current page group nor in the Shared Objects page group.
- Cause:
- The date entered was invalid.
- Action:
- Enter a valid date.
- Cause:
- An invalid value was entered in the style's color field.
- Action:
- Enter a valid color value.
- Cause:
- No language was specified in the internal API that creates translation for the page group. One way to avoid this is to create translations through the user interface.
- Action:
- Specify a language for translation.
- Cause:
- Invalid characters were entered for the page group name.
- Action:
- Enter a valid page group name.
- Cause:
- No name or display name was specified on creation or edit of a custom page type.
- Action:
- Specify a valid name and display name for the custom page type.
- Cause:
- An attempt was made to remove a page group's default language. This action is not permitted.
- Action:
- Some translation languages can be removed. For a list of these, go to the Translations tab of page group properties.
- Cause:
- An invalid page group ID was entered.
- Action:
- Enter a valid page group ID.
- Cause:
- The page group name entered was already in use.
- Action:
- Enter a unique page group name.
- Cause:
- An invalid date value was entered for the search attribute.
- Action:
- Enter a valid date value.
- Cause:
- An invalid number value was entered for the search attribute.
- Action:
- Enter a valid number value.
- Cause:
- A value was not entered for the Procedure Call or the Link Text.
- Action:
- Enter values for both fields. If you do not want to add a procedure call to the page type, ensure that both fields are null.
- Cause:
- The URL for a URL page was not specified.
- Action:
- Specify a URL for the URL page.
- Cause:
- The PL/SQL code for a PL/SQL page was not specified.
- Action:
- Specify PL/SQL code for the PL/SQL page.
- Cause:
- The name given for the saved search already exists.
- Action:
- Specify a unique name for the saved search.
- Cause:
- The category name contained invalid characters.
- Action:
- Specify a valid name.
- Cause:
- The perspective name contained invalid characters.
- Action:
- Specify a valid name.
- Cause:
- Nothing was entered in the Display Name field.
- Action:
- Enter a valid Display Name.
- Cause:
- An attempt was made to move an item to a nonexistent page group.
- Action:
- Pass in a valid page group name to the move item API.
- Cause:
- One or more numeric values greater than zero were required but not entered in page group properties.
- Action:
- Provide all the required number values.
- Cause:
- A display name was not provided for a perspective.
- Action:
- Specify a display name for the perspective.
- Cause:
- An attempt was made to provide access to user that does not exist.
- Action:
- Provide a valid user name.
- Cause:
- The specified page name contained spaces or special characters.
- Action:
- Remove the the spaces and special characters from the page name.
- Cause:
- An invalid user name or group name was entered.
- Action:
- Enter a valid user name or group name. If you are not sure of the name, click the Browse Users or Browse Groups icon and select from the list provided.
- Cause:
- The CGI environment variables were not initialized.
- Action:
- Check the middle-tier log files.
- Cause:
- A schema name was not specified.
- Action:
- Specify a valid schema name.
- Cause:
- The database schema specified does not exist.
- Action:
- Specify a valid database schema.
- Cause:
- The item is set to expire on a future date, but an expiration date was not specified.
- Action:
- Specify the expiration date.
- Cause:
- The item is set to expire in a certain number of days, but the number of days was not specified.
- Action:
- Specify the number of days from the publish date when the item should expire.
- Cause:
- The publish date was entered in an invalid format.
- Action:
- Enter the publish date in the format specified.
- Cause:
- An attempt was made to publish this item before the current date, or an attempt was made to create a sub-item with a publish date that precedes the publish date of the parent item.
- Action:
- Change the publish date of the item to a future date, or set the publish date of the sub-item to the same or a later date than the publish date of the parent item.
- Cause:
- The expiration date was entered in an invalid format.
- Action:
- Enter the expiration date in the format specified.
- Cause:
- An expiration date was entered for the item that was not later than the current date.
- Action:
- The item can be expired only in the future. Specify an expiration date that is later than the current date.
- Cause:
- The item has expired and cannot be edited.
- Action:
- Un-expire the item, then try again.
- Cause:
- An invalid number was entered for the expiration period.
- Action:
- Specify a valid number.
- Cause:
- An attempt was made to enter a publish date that precedes the item's creation date.
- Action:
- Enter a publish date that is either the same or later than the current date.
- Cause:
- Portal was unable to refresh a portlet provider or the Portlet Repository.
- Action:
- Check the refresh log to determine the provider that throws error, then verify that the provider registration for that provider is correct. Make sure the provider is up and running during refresh.
- Cause:
- An invalid style name was provided during style creation or edit.
- Action:
- Provide a valid style name.
- Cause:
- A display name was not provided for the style.
- Action:
- Provide a valid display name.
- Cause:
- The document or image could not be uploaded because the page group quota has been exceeded.
- Action:
- Contact the portal administrator.
- Cause:
- An attempt was made to enter an item expiration date that precedes the item publish date.
- Action:
- Enter an expiration date that is later than the publish date.
- Cause:
- The registration information for some provider is corrupted, or an internal error occurred in the provider subsystem.
- Action:
- Verify that registration information for all providers is valid.
- Cause:
- An attempt was made to specify an invalid date format.
- Action:
- Specify a valid date format.
- Cause:
- An attempt was made to enter an invalid e-mail address format.
- Action:
- Enter the e-mail address in a valid format, for example, name@oracle.com.
- Cause:
- Another user has checked the item out. The edit icon was displayed because the page has not been refreshed since the other user checked the item out.
- Action:
- Refresh the page to show the current status of its content. As soon as the other user checks the item in, you will be able to edit it.
- Cause:
- The choice to specify an Advanced Search Link was made, but the advanced search link value was not specified. The Advanced Search Link is specified either by selecting a page or specifying a URL.
- Action:
- Specify an Advanced Search Link value.
- Cause:
- The choice was made to specify an Advanced Search Page, but the Advanced Search value was not specified. The Advanced Search Page is specified either by selecting a page or specifying a URL.
- Action:
- Specify an Advanced Search Page value.
- Cause:
- Fewer than two search terms were specified for the near operator. The near operator requires two search terms.
- Action:
- Specify two search terms when using the near operator. The search will return results that have near with a high score.
- Cause:
- More than two search terms were specified for the near operator. The near operator requires two search terms.
- Action:
- Specify two search terms when using the near operator. The search will return results that have near with a high score.
- Cause:
- An attempt was made to unzip an item that is pending approval. Items pending approval cannot be unzipped.
- Action:
- Unzip after the item is approved.
- Cause:
- One or both search results pages were not specified.
- Action:
- Choose search results pages for basic and advanced searches.
- Cause:
- A search was submitted containing no valid search criteria. Either no criteria were specified, or the criteria specified were not relevant to the type of results being sought. For example, only a category criteria is specified, and the search is for categories. Categories do not belong to categories, so the criteria is not valid and is ignored.
- Action:
- Ensure that the search contains valid search criteria.
- Cause:
- Portal URLs have changed, the old URL format is no longer valid.
- Action:
- Wait to be redirected to the new URL, or click on the link displayed.
- Cause:
- A page group that had some data corruption was deleted.
- Action:
- No further action required. The page group has been deleted. You can look at the logs for additional details on the data corruption.
- Cause:
- This is usually caused when the category page template has been modified and the region in which the portlets are to be placed has been removed.
- Action:
- If the category template is deleted, it will be recreated with the correct regions the next time a category is created. However, existing categories will not be based on the new template. See the OracleAS Portal Configuration Guide, available on Portal Center, for information on how to remove and recreate all of the category pages based on a recreated template.
- Cause:
- This is usually caused when the perspective page template has been modified and the region in which the portlets are to be placed has been removed.
- Action:
- If the perspective template is deleted, it will be recreated with the correct regions the next time a perspective is created. However, existing perspectives will not be based on the new template. See the OracleAS Portal Configuration Guide, available on Portal Center, for information on how to remove and recreate all of the perspective pages based on a recreated template.
- Cause:
- There may be a problem with an unsupported file format. To search file content and Themes and Gist, and view as HTML, the file must be filtered and converted to plain text. This is not always possible because some file formats are not supported. This error might also be caused by a problem with the setup and configuration of Oracle Text.
- Action:
- Ensure that the document is in a format supported by Oracle Text. See the OracleAS Portal Configuration Guide, available on Portal Center, for information on how to work with Oracle Text.
- Cause:
- The combination of operator and search term were used to create a list of potential search terms that is too large. This can occur when using the "partially match (%term%)" operator with a non-specific search term.
- Action:
- Enter a more specific search term, or use a different operator.
- Cause:
- The Knowledge Base supplied with Oracle Text was not installed.
- Action:
- Complete the installation of Oracle Text.
- Cause:
- An operation was attempted by a user without the required privilege.
- Action:
- Ask the page group administrator or page manager to grant you the appropriate privilege.
- Cause:
- A page name was required but not entered.
- Action:
- Enter a valid name.
- Cause:
- A display name was required but not entered.
- Action:
- Enter a valid display name.
- Cause:
- An invalid page group ID was passed to a function getting the default language of a page group.
- Action:
- Pass a valid page group ID.
- Cause:
- This portlet does not support the specified display mode.
- Action:
- Choose either the Show or Edit display mode.
- Cause:
- A display name was not entered for the perspective.
- Action:
- Specify a display name for the perspective.
- Cause:
- Unknown exception occurred during export-import operation.
- Action:
- Do nothing, selected object will be exported. If export fails, contact Oracle Customer Support.
- Cause:
- Object already marked for export.
- Action:
- Do nothing, selected object will be exported.
- Cause:
- The source attribute has been promoted, but the target attribute belongs to a local page group.
- Action:
- Promote the local attribute on the target, and re-import it.
- Cause:
- The source attribute belongs to a local page group, but the target attribute has been promoted.
- Action:
- Promote the local attribute on the source, and re-import it.
- Cause:
- A different attribute on the target uses the same name.
- Action:
- Delete the attribute on the target, and re-import it.
- 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.
- 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.
- Cause:
- The length of a text attribute on the target is less than the lenght 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 the overwrite mode.
- Cause:
- The source style has been promoted, but the target style belongs to a local page group.
- Action:
- Promote the local style on the target, and re-import it.
- Cause:
- The source style belongs to a local page group, but the target style has been promoted.
- Action:
- Promote the local style on the source, and re-import it.
- Cause:
- A different style on the target uses the same name.
- Action:
- Delete the style on the target, and re-import it.
- 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.
- 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.
- Cause:
- A different item type on the target uses the same name.
- Action:
- Delete the item type on the target, and re-import it.
- Cause:
- The source item type has been promoted, but the target item type belongs to a local page group.
- Action:
- Promote the local item type on the target, and re-import it.
- Cause:
- The source item type belongs to a local page group, but the target item type has been promoted.
- Action:
- Promote the local item type on the source, and re-import it.
- 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.
- Cause:
- A different page type on the target uses the same name.
- Action:
- Delete the page type on the target, and re-import it.
- Cause:
- The source page type has been promoted, but the target page type belongs to a local page group.
- Action:
- Promote the local page type on the target, and re-import it.
- Cause:
- The source page type belongs to a local page group, but the target page type has been promoted.
- Action:
- Promote the local page type on the source, and re-import it.
- 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.
- Cause:
- An unexpected error occurred while calculating the dependencies of the object.
- Action:
- Retry the import. If the retry fails, contact Oracle Customer Support.
- Cause:
- Import failed for the object in the transport set.
- Action:
- Retry the import. If the retry fails, contact Oracle Customer Support.
- Cause:
- An unexpected error occurred while creating the color on the target.
- Action:
- Retry the import. If the retry fails, contact Oracle Customer Support.
- Cause:
- An unexpected error occurred while creating the font on the target.
- Action:
- Retry the import. If the retry fails, contact Oracle Customer Support.
- Cause:
- An unexpected error occurred while creating the image on the target.
- Action:
- Retry the import. If the retry fails, contact Oracle Customer Support.
- Cause:
- An unexpected error occurred while creating the template on the target.
- Action:
- Retry the import. If the retry fails, contact Oracle Customer Support.
- Cause:
- Attempt to find the object failed.
- Action:
- Retry the import .If the retry fails, contact Oracle Customer Support.
- Cause:
- No name has been specified for the transport set.
- Action:
- Specify a name for the transport set.
- Cause:
- The transport set has already been exported.
- Action:
- If the export was successful, the transport set can now be used for import.
- Cause:
- Export of the transport set is not complete.
- Action:
- Export the transport set.
- 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.
- Cause:
- Transport set status is neither EXTRACT_COMPLETE nor AVAILABLE.
- Action:
- Browse the list of transport sets to determine the status.
- Cause:
- More than one transport set with the same name was found.
- Action:
- The list of values with the user/timestamp helps to identify the right transport set.
- Cause:
- The transport set has already been exported or imported.
- Action:
- Browse the list of transport sets to determine the status.
- Cause:
- The transport set is empty.
- Action:
- Add at least one object to the transport set in order to access it.
- Cause:
- Logged-in user does not have MANAGE privilege on any transport sets.
- Action:
- Contact your administrator to acquire this privilege.
- Cause:
- The specified transport set does not exist.
- Action:
- Verify the transport set name, or re-create the transport set.
- Cause:
- Could not obtain information about the given transport set.
- Action:
- Verify the transport set name, or re-create the transport set.
- Cause:
- The preference for a search portlet marked for export does not exist in the system tables.
- Action:
- Contact Oracle Customer Support.
- 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.
- Cause:
- The exporting of search preferences has failed.
- Action:
- Contact Oracle Customer Support.
- 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.
- Cause:
- Could not obtain information about the given transport set.
- Action:
- Verify the transport set name, or re-create the transport set.
- Cause:
- An unexpected error occurred while attempting to export search portlet preferences.
- Action:
- Contact Oracle Customer Support.
- Cause:
- The dependencies in the search portlet preferences to be exported could not be obtained.
- Action:
- Contact Oracle Customer Support.
- Cause:
- The dependencies in the search portlet preferences to be exported could not be obtained.
- Action:
- Contact Oracle Customer Support.
- Cause:
- An unexpected error occurred while pre-checking search preferences.
- Action:
- Contact Oracle Customer Support.
- Cause:
- An error occurred while marking a search portlet preference dependency included in the transport set.
- Action:
- Contact Oracle Cutomer Support.
- Cause:
- An unexpected error occurred while attempting to mark a page as failed pre-check.
- Action:
- Contact Oracle Customer Support.
- Cause:
- Dependencies in the search preferences are not in the search dependency table.
- Action:
- Contact Oracle Customer Support.
- Cause:
- An unexpected error occurred while checking if a search preference has missing dependencies.
- Action:
- Contact Oracle Customer Support.
- Cause:
- An error occurred while attempting to get the ID of an object in the target tables.
- Action:
- Contact Oracle Customer Support.
- Cause:
- The information in the search preferences does not match information in the search dependency table.
- Action:
- Contact Oracle Customer Support.
- Cause:
- An unexpected error occurred while attempting to resolve search preference information.
- Action:
- Contact Oracle Customer Support.
- Cause:
- An unexpected error occurred while attempting to determine the import action of search portlet preferences.
- Action:
- Contact Oracle Customer Support.
- Cause:
- An unexpected error occurred while attempting to resolve a search portlet's reference path.
- Action:
- Contact Oracle Customer Support.
- Cause:
- The object type of a search preference dependency is not valid.
- Action:
- Contact Oracle Customer Support.
- Cause:
- An unexpected error occurred while attempting to update the dependency table with the new IDs.
- Action:
- Contact Oracle Customer Support.
- Cause:
- An unexpected error occurred when attempting to obtain the ID of a search preference dependency from the target tables.
- Action:
- Contact Oracle Customer Support.
- Cause:
- An unexpected error occurred when attempting to obtain the ID of a search preference dependency from the transport tables.
- Action:
- Contact Oracle Customer Support.
- Cause:
- An unexpected error occurred while attempting to determine the new IDs of search preference dependencies.
- Action:
- Contact Oracle Customer Support. search import
- Cause:
- An unexpected error occurred when attempting to import search portlet preferences.
- Action:
- Contact Oracle Customer Support.
- Cause:
- An unexpected error occurred when attempting to insert new search portlet preferences into the target tables.
- Action:
- Contact Oracle Customer Support.
- Cause:
- An unexpected error occurred when obtaining the page group dependencies from the search portlets being exported.
- Action:
- Contact Oracle Customer Support.
- Cause:
- An unexpected error occurred when obtaining the image dependencies from the search portlets being exported.
- Action:
- Contact Oracle Customer Support.
- Cause:
- An unexpected error occurred when obtaining the style dependencies from the search portlets being exported.
- Action:
- Contact Oracle Customer Support.
- Cause:
- An unexpected error occurred when obtaining the attribute dependencies from the search portlets being exported.
- Action:
- Contact Oracle Customer Support.
- Cause:
- An unexpected error occurred when obtaining the item type dependencies from the search portlets being exported.
- Action:
- Contact Oracle Customer Support.
- 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 Customer Support.
- 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 Customer Support.
- Cause:
- An unexpected error occurred while obtaining the path of the page selected to display search results. The domain is invalid.
- Action:
- Contact Oracle Customer Support.
- 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 Customer Support.
- Cause:
- An unexpected error occurred while obtaining the page dependencies from the search portlets being exported.
- Action:
- Contact Oracle Customer Support.
- Cause:
- An unexpected error occurred while obtaining the path of the category selected as search criteria. The category cannot be found.
- Action:
- Contact Oracle Customer Support.
- Cause:
- An unexpected error occurred while obtaining the path of the category selected as search criteria. The language can not be found.
- Action:
- Contact Oracle Customer Support.
- Cause:
- An unexpected error occurred while obtaining the path of the category selected as search criteria. The domain is invalid.
- Action:
- Contact Oracle Customer Support.
- Cause:
- An unexpected error occurred while obtaining the path of the category selected as search criteria. The object type is invalid.
- Action:
- Contact Oracle Customer Support.
- Cause:
- An unexpected error occurred while obtaining the category dependencies from the search portlets being exported.
- Action:
- Contact Oracle Customer Support.
- Cause:
- An unexpected error occurred while obtaining the path of the perspective selected as search criteria. The object cannot be found.
- Action:
- Contact Oracle Customer Support.
- Cause:
- An unexpected error occurred while obtaining the path of the perspective selected as search criteria. The language cannot be found.
- Action:
- Contact Oracle Customer Support.
- Cause:
- An unexpected error occurred while obtaining the path of the perspective selected as search criteria. The domain is invalid.
- Action:
- Contact Oracle Customer Support.
- Cause:
- An unexpected error occurred while obtaining the path of the perspective selected as search criteria. The object type is invalid.
- Action:
- Contact Oracle Customer Support.
- Cause:
- An unexpected error occurred while obtaining the perspective dependencies from the search portlets being exported.
- Action:
- Contact Oracle Customer Support.
- Cause:
- An unexpected error occurred while removing dangling references from the preferences of the search portlets being exported.
- Action:
- Contact Oracle Customer Support.
- 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 Customer Support.
- Cause:
- Obtaining the page on which the search portlet resides failed because the page does not exist in the transport set.
- Action:
- Contact Oracle Customer Support.
- Cause:
- Obtaining the page on which the search portlet resides failed because too many pages were returned from the query.
- Action:
- Contact Oracle Customer Support.
- Cause:
- An unexpected error occurred when attempting to get the object ID of the page on which the search portlet resides.
- Action:
- Contact Oracle Customer Support.
- 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 Customer Support.
- 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 Customer Support.
- 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 Customer Support.
- 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 Customer Support.
- 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 Customer Support.
- 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 Customer Support.
- 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 Customer Support.
- 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 Customer Support.
- 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 Customer Support.
- 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 Customer Support.
- Cause:
- An unexpected error occurred while replacing source IDs with target IDs for the image option in the search portlet customizations.
- Action:
- Contact Oracle Customer Support.
- Cause:
- An unexpected error occurred while replacing source IDs with target IDs for the style option in the search portlet customizations.
- Action:
- Contact Oracle Customer Support.
- 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 Customer Support.
- 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 Customer Support.
- 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 Customer Support.
- 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 Customer Support.
- 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 Customer Support.
- Cause:
- The search preferences for the portlets being imported cannot be resolved because the transport set does not exist.
- Action:
- Contact Oracle Customer Support.
- Cause:
- The search preferences for the portlets being imported cannot be resolved because the transport set information cannot be obtained.
- Action:
- Contact Oracle Customer Support.
- Cause:
- An unexpected error occurred while the preferences for the search portlets being imported were being updated.
- Action:
- Contact Oracle Customer Support.
- Cause:
- The search preferences for the portlets being imported cannot be imported because the transport set does not exist.
- Action:
- Contact Oracle Customer Support.
- Cause:
- The search preferences for the portlets being imported cannot be imported because the transport set information cannot be obtained.
- Action:
- Contact Oracle Customer Support.
- 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 item.
- 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.
- 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 attribute.
- Cause:
- The list of values does not exist on the target.
- Action:
- Bring in the list of values seperately, and re-associate or promote it to the transport set in the source. Then re-import it.
- 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.
- Cause:
- The Internal Identifier of the page group did not get resolved.
- Action:
- Retry importing. If the retry fails, contact Oracle Customer Support.
- Cause:
- An unexpected error occurred while updating the page group properties.
- Action:
- Retry importing. If the retry fails, contact Oracle Customer Support.
- Cause:
- The Internal Identifier of the page group was not updated to all of the page group objects.
- Action:
- Contact Oracle Customer Support.
- Cause:
- Resolution of the item with the text attribute failed.
- Action:
- Retry importing. If the retry fails, contact Oracle Customer Support.
- 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 Customer Support.
- Cause:
- Resolution of the item with the URL attribute failed.
- Action:
- Retry importing. If the retry fails, contact Oracle Customer Support.
- Cause:
- More than one row was found for the URL during resolution.
- Action:
- Retry importing. If the retry fails, contact Oracle Customer Support.
- Cause:
- The attempt to find the page type function failed.
- Action:
- Retry importing. If the retry fails, contact Oracle Customer Support.
- Cause:
- The attribute update failed.
- Action:
- Retry importing. If the retry fails, contact Oracle Customer Support.
- Cause:
- The style update failed.
- Action:
- Retry importing. If the retry fails, contact Oracle Customer Support.
- Cause:
- Failed to add translation for category.
- Action:
- Contact Oracle Customer Support.
- Cause:
- Failed to add translation for perspective.
- Action:
- Contact Oracle Customer Support.
- Cause:
- An unexpected DAV error occurred while creating the item on the target.
- Action:
- Contact Oracle Customer Support.
- Cause:
- An unexpected error occurred while creating the item on the target.
- Action:
- Retry importing. If the retry fails, contact Oracle Customer Support.
- Cause:
- An unexpected DAV error occurred while updating the item on the target.
- Action:
- Contact Oracle Customer Support.
- Cause:
- An unexpected error occurred while updating the item on the target.
- Action:
- Retry importing. If the retry fails, contact Oracle Customer Support.
- Cause:
- An unexpected error occurred while creating the region attributes.
- Action:
- Retry importing. If the retry fails, contact Oracle Customer Support.
- Cause:
- Could not create region because it already exists on the target system.
- Action:
- Retry importing. If the retry fails, contact Oracle Customer Support.
- Cause:
- An unexpected error occurred while creating the region on the target.
- Action:
- Contact Oracle Customer Support.
- Cause:
- An unexpected error occurred while updating the region on the target.
- Action:
- Contact Oracle Customer Support.
- Cause:
- Region exists on another page.
- Action:
- Contact Oracle Customer Support.
- Cause:
- An unexpected error occurred while creating the page on the target.
- Action:
- Contact Oracle Customer Support.
- Cause:
- An unexpected error occurred while updating the page on the target.
- Action:
- Contact Oracle Customer Support.
- Cause:
- Failed to share the portlet instance on the target.
- Action:
- Contact Oracle Customer Support.
- Cause:
- 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.
- 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.
- 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.
- 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 Customer Support.
- Cause:
- An unexpected error occurred while merging approval-related infrastructure on the target.
- Action:
- Manually recreate the approval process on the target.
- 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 Customer Support.
- 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.
- 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.
- Cause:
- Metadata corruption 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 Customer Support.
- 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 Customer Support.
- 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 Customer Support.
- Cause:
- Export time pre-checks have failed.
- Action:
- Contact Oracle Customer Support.
- 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 Customer Support.
- 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.
- 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 Customer Support.
- Cause:
- Metadata is not available due to direct manipulation of metadata tables for lists of values.
- Action:
- Contact Oracle Customer Support.
- 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 Customer Support.
- Cause:
- Menu metadata is not available due to direct manipulation of metadata tables for menus.
- Action:
- Contact Oracle Customer Support.
- Cause:
- Component metadata is not available due to direct manipulation of metadata tables for data component.
- Action:
- Contact Oracle Customer Support.
- Cause:
- More than one row detected for data component due to direct manipulation of metadata tables for data component.
- Action:
- Contact Oracle Customer Support.
- Cause:
- Direct user intervention could have dropped the DB Provider schema.
- Action:
- Contact Oracle Customer Support.
- 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 Customer Support.
- 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 Customer Support.
- 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 Customer Support.
- 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 Customer Support.
- Cause:
- Direct manipulation of system tables could have caused the unavailability of data
- Action:
- Contact Oracle Customer Support.
- Cause:
- Some attributes of the report were not saved, possibly because they are invalid.
- Action:
- Contact Oracle Customer Support.
- Cause:
- Some attributes were not saved, possibly because they are invalid.
- Action:
- Contact Oracle Customer Support.
- Cause:
- Some attributes of the report were not saved, possibly because they are invalid.
- Action:
- Contact Oracle Customer Support.
- Cause:
- Some attributes were not saved, possibly because they are invalid.
- Action:
- Contact Oracle Customer Support.
- Cause:
- A component with the same id already exists, possibly because the table WWAPP_APPLICATION_DETAIL$ was directly manipulated.
- Action:
- Datafix scripts can help resolve this error. Contact Oracle Customer Support for assistance.
- Cause:
- The component was not deleted from the Portal DB Provider for some reason.
- Action:
- Contact Oracle Customer Support.
- Cause:
- The application on which the component is built does not exist, possibly because it was removed from the application metadata table.
- Action:
- Check to see if the underlying application exists in the Navigator. If it does not, contact Oracle Customer Support.
- Cause:
- Either you do not have privileges to run this package or the package does not exist.
- Action:
- Check your privilege level, then see if the package exists in the schema.
- Cause:
- The SQL INSERT statement could not be parsed due to incorrect syntax or usage, or reference to inaccessible objects.
- Action:
- Contact Oracle Customer Support.
- Cause:
- The SQL SELECT statement could not fetch any rows.
- Action:
- Contact Oracle Customer Support.
- Cause:
- An unexpected error was encountered while generating the SELECT statement.
- Action:
- Contact Oracle Customer Support.
- Cause:
- An unexpected error was encountered during code generation.
- Action:
- Contact Oracle Customer Support.
- Cause:
- An unexpected error was encountered during code generation.
- Action:
- Contact Oracle Customer Support.
- Cause:
- Design time metadata for an image chart could not be fetched.
- Action:
- Contact Oracle Customer Support.
- Cause:
- The rows could not be fetched.
- Action:
- Contact Oracle Customer Support.
- Cause:
- No columns were defined in the query.
- Action:
- Contact Oracle Customer Support.
- Cause:
- The query could not be parsed.
- Action:
- Contact Oracle Customer Support.
- Cause:
- Either the object you are searching for does not exist, or you do not have sufficient privileges to retrieve it.
- Action:
- Check to see if the object exists and, if it does, that you have the appropriate privileges.
- Cause:
- The source for the requested object could not be contacted.
- Action:
- Contact Oracle Customer Support.
- Cause:
- Design time metadata for this calendar component could not be fetched.
- Action:
- Contact Oracle Customer Support.
- Cause:
- An obsolete banner tag was used in the template, so the template could not be saved.
- Action:
- Remove the tag that is no longer supported. Refer to the Portal User's Guide for a list of tags that are supported in templates.
- Cause:
- An obsolete banner tag was used in the template, so the template could not be created.
- Action:
- Remove the tag that is no longer supported. Refer to the Portal User's Guide for a list of tags that are supported in templates.
- Cause:
- The job was not submitted, possibly because the HTTP cookie is too long.
- Action:
- Close all browser windows and try again.
- Cause:
- Deletion from the batch submissions table could not occur, possibly because the table does not exist or because of an underlying database problem.
- Action:
- Ensure that your database is not experiencing a rollback segment problem, then contact Oracle Customer Support.
- Cause:
- The SQL statement could not be parsed due to incorrect syntax or usage, or because it referred to inaccessible objects.
- Action:
- Contact Oracle Customer Support.
- Cause:
- You are editing a dynamic page that contains more than 32K of HTML code.
- Action:
- Avoid writing more than 32K of HTML code in a dynamic page.
- Cause:
- A limit has been exceeded, such as using more than 15 check boxes in an HTML page.
- Action:
- As this is a design time issue, contact Oracle Customer Support.
- Cause:
- A limit has been exceeded, such as using more than 15 check boxes in an HTML page.
- Action:
- As this is a design time issue, contact Oracle Customer Support.
- Cause:
- The component metadata could not be loaded, so the component attributes were not initialized.
- Action:
- Contact Oracle Customer Support and ask them to see if the component metadata is intact.
- Cause:
- The component metadata could not be deleted, possibly because there are some dependencies that have not been eliminated.
- Action:
- Contact Oracle Customer Support and ask them to see if the component metadata is intact.
- Cause:
- This component is already locked by another user.
- Action:
- Unlock the component before attempting to edit it.
- Cause:
- The component metadata could not be loaded, so the attribute for this component was not initialized.
- Action:
- Contact Oracle Customer Support and ask them to see if the component metadata is intact.
- Cause:
- An error occurred while saving the component metadata.
- Action:
- Contact Oracle Customer Support.
- Cause:
- An error occurred while saving the component metadata.
- Action:
- Contact Oracle Customer Support.
- Cause:
- An error occurred while saving the component metadata.
- Action:
- Contact Oracle Customer Support.
- Cause:
- An error occurred while saving the component metadata.
- Action:
- Contact Oracle Customer Support.
- Cause:
- The component type does not exist, possibly because it was removed from the master table.
- Action:
- Contact Oracle Customer Support.
- Cause:
- Either the component id or the module id is unavailable.
- Action:
- Check to see if a component with this id exists.
- Cause:
- The components table could not be cleaned up because there are dependencies that have not been cleaned up.
- Action:
- Contact Oracle Customer Support.
- Cause:
- The component could not be created, possibly because there was an error while inserting into the component metadata table.
- Action:
- See if this component already exists, or contact Oracle Customer Support.
- Cause:
- Something went wrong while executing a function in the Component Builder.
- Action:
- Contact Oracle Customer Support.
- Cause:
- The module attributes were not initialized because the component metadata could not be loaded.
- Action:
- Ask Oracle Customer Support if the component metadata is intact.
- Cause:
- Certain attributes of the component could not be saved, possibly because the attribute is invalid .
- Action:
- Contact Oracle Customer Support.
- Cause:
- Certain attributes of the component could not be saved, possibly because the attribute is invalid .
- Action:
- Contact Oracle Customer Support.
- Cause:
- Metadata may be corrupted.
- Action:
- Contact Oracle Customer Support.
- Cause:
- Builder attributes could not be initialized because design time metadata for the component could not be fetched.
- Action:
- Contact Oracle Customer Support.
- Cause:
- The report cannot be rendered, either because you do not have the appropriate privileges to select from the wwlog_activity$ table or because the table does not exist.
- Action:
- Verify that the table exists and that you have the appropriate privileges.
- Cause:
- This component does not exist in the component metadata.
- Action:
- Check to see if the component appears in the Navigator.
- Cause:
- This component version does not exist in the component metadata.
- Action:
- Ensure that the component version exists.
- Cause:
- The package cannot be dropped, either because you do not have the appropriate privileges or because the package does not exist.
- Action:
- Make sure that the package exists in the schema and that you have the appropriate privileges.
- Cause:
- A data component with this name already exists.
- Action:
- Select a new name for the component.
- Cause:
- An error occurred in the user preference storage subsystem.
- Action:
- Contact Oracle Customer Support.
- Cause:
- A table with this name does not exist or there are not enough privileges to access it.
- Action:
- Make sure the table exists, or grant appropriate privileges on the table.
- Cause:
- An unexpected error occurred while a frame driver component's package body was being generated or compiled.
- Action:
- Contact Oracle Customer Support.
- Cause:
- An unexpected error occured while fetching the value of this attribute, possibly as a result of corrupted metadata.
- Action:
- Contact Oracle Customer Support.
- Cause:
- An unexpected error occurred while generating PL/SQL code for portlet caching.
- Action:
- Regenerate the component. If the error persists, contact Oracle Customer Support.
- Cause:
- An unexpected error occurred while trying to invoke the Oracle Reports generator.
- Action:
- Contact Oracle Customer Support.
- Cause:
- A SQL or PL/SQL statement could not be parsed due to incorrect syntax or usage, or because it referred to an inaccessible object.
- Action:
- Contact Oracle Customer Support.
- Cause:
- The component could not be unlocked.
- Action:
- Contact Oracle Customer Support.
- Cause:
- An unexpected error occurred while trying to add an image.
- Action:
- Contact Oracle Customer Support.
- Cause:
- The image name cannot be blank.
- Action:
- Assign an appropriate name to the image, then try again.
- Cause:
- An unexpected error occurred while updating an image.
- Action:
- Contact Oracle Customer Support.
- Cause:
- The image id of the image you are trying to update is null.
- Action:
- Ensure that the image exists.
- Cause:
- An unexpected error occurred.
- Action:
- Contact Oracle Customer Support.
- Cause:
- You must select a link on the 'Column Formatting' tab and give it a value before you can edit it.
- Action:
- Select a link from the combo box.
- Cause:
- The attribute was not saved.
- Action:
- Contact Oracle Customer Support.
- Cause:
- The design time metadata for this link component could not be fetched.
- Action:
- Contact Oracle Customer Support.
- Cause:
- An LOV with this name already exists.
- Action:
- Assign a unique name to the LOV, then try the action again.
- Cause:
- The LOV type is invalid.
- Action:
- Identify the LOV type as either STATIC or DYNAMIC, then try the action again.
- Cause:
- The ORA error in the error message.
- Action:
- Contact Oracle Customer Support.
- Cause:
- The ORA error in the error message.
- Action:
- Contact Oracle Customer Support.
- Cause:
- The ORA error in the error message.
- Action:
- Contact Oracle Customer Support.
- Cause:
- The ORA error in the error message.
- Action:
- Contact Oracle Customer Support.
- Cause:
- The ORA error in the error message.
- Action:
- Contact Oracle Customer Support.
- Cause:
- An unexpected error occurred while trying to update the menu.
- Action:
- Contact Oracle Customer Support.
- Cause:
- An unexpected error occurred while trying to delete the menu.
- Action:
- Contact Oracle Customer Support.
- Cause:
- An unexpected error occurred while trying to delete the sub menu.
- Action:
- Contact Oracle Customer Support.
- Cause:
- An unexpected error occurred while trying to insert the menu.
- Action:
- Contact Oracle Customer Support.
- Cause:
- An unexpected error occurred while trying to insert metadata for the menu.
- Action:
- Contact Oracle Customer Support..
- Cause:
- An unexpected error occurred while trying to update the metadata for the menu.
- Action:
- Contact Oracle Customer Support..
- Cause:
- An error was encountered while trying to compile a package for the menu component.
- Action:
- Try re-generating the component. If the error persists, contact Oracle Customer Support.
- Cause:
- An error was encountered while trying to compile a package body for the menu component.
- Action:
- Try re-generating the component. If the error persists, contact Oracle Customer Support.
- Cause:
- The SQL statement could not be parsed due to incorrect syntax or usage, or because it referenced an inaccessible object.
- Action:
- Contact Oracle Customer Support.
- Cause:
- The SQL statement could not be parsed due to incorrect syntax or usage or because it referenced an inaccessible object.
- Action:
- Contact Oracle Customer Support.
- Cause:
- The preference path may be missing.
- Action:
- Contact Oracle Customer Support.
- Cause:
- The preference path may be missing.
- Action:
- Contact Oracle Customer Support.
- Cause:
- The database object type is invalid.
- Action:
- Check to see if an object of this type exists.
- Cause:
- You are attempting to view a synonym on a remote table, which is not supported.
- Action:
- This is not supported.
- Cause:
- The design time metadata for this QBE component could not be fetched.
- Action:
- Contact Oracle Customer Support.
- Cause:
- The object may not exist, or the permissions may not be sufficient.
- Action:
- Check to see if the object exists, and the object's permissions.
- Cause:
- Either the query is improperly written, or the permissions on the query object are not sufficient.
- Action:
- Check the syntax of the query and the permissions on the object.
- Cause:
- Either the query is improperly written, or the permissions on the query object are not sufficient.
- Action:
- Check the syntax of the query and the permissions on the object.
- Cause:
- Either the query is improperly written, or the permissions on the query object are not sufficient.
- Action:
- Check the syntax of the query and the permissions on the object.
- Cause:
- The dynamic SQL statement could not be parsed due to incorrect syntax or usage, or because it referenced an inaccessible object.
- Action:
- Contact Oracle Customer Support.
- Cause:
- Either the query is improperly written, or the permissions on the query object are not sufficient.
- Action:
- Check the query and the permissions on the object.
- Cause:
- Either the query is improperly written, or the permissions on the query object are not sufficient.
- Action:
- Check the query and the permissions on the object.
- Cause:
- Either the query is improperly written, or the permissions on the query object are not sufficient.
- Action:
- Check the query and the permissions on the object.
- Cause:
- An error has occurred while calculating the sum of a column.
- Action:
- Make sure the column is numeric.
- Cause:
- An error has occurred while fetching the column value.
- Action:
- Contact Oracle Customer Support.
- Cause:
- An unexpected error occurred.
- Action:
- Contact Oracle Customer Support.
- Cause:
- Either the user does not have permission to perform this action, or the user/group to which the privilege is assigned does not exist.
- Action:
- If the user/group does not exist, create it. If the user does not have sufficient privileges to grant access, assign them before the user re-attempts this action.
- Cause:
- Either the target user/group does not exist, or the current user does not have permission to perform this action.
- Action:
- If the user/group does not exist, create it. If the user does not have sufficient privileges to grant access, assign them before the user re-attempts this action.
- Cause:
- An inappropriate value was supplied for a label usage ID.
- Action:
- Contact Oracle Customer Support.
- Cause:
- An inappropriate value was supplied for a text block usage ID.
- Action:
- Contact Oracle Customer Support.
- Cause:
- An inappropriate value was supplied for a label usage ID.
- Action:
- Contact Oracle Customer Support.
- Cause:
- An inappropriate value was supplied for a text block usage ID.
- Action:
- Contact Oracle Customer Support.
- Cause:
- The LOV may have been removed.
- Action:
- Check to see if the LOV appears in the Navigator. If it does not, either re-create it or contact Oracle Customer Support.
- Cause:
- The LOV may have been removed.
- Action:
- Check to see if the LOV appears in the Navigator. If it does not, either re-create it or contact Oracle Customer Support.
- Cause:
- The LOV has been dropped or has been manually removed from the LOV tables.
- Action:
- If this is a user defined LOV, check to see if it appears in the Navigator. If it is a system LOV, contact Oracle Customer Support.
- Cause:
- The user settings could not be modified.
- Action:
- Contact Oracle Customer Support.
- Cause:
- An unexpected error occurred while trying to create a user.
- Action:
- Contact Oracle Customer Support.
- Cause:
- An unexpected error occurred while trying to drop a user.
- Action:
- Contact Oracle Customer Support.
- Cause:
- An unexpected error occurred while trying to drop a user.
- Action:
- Contact Oracle Customer Support.
- Cause:
- The new application component you are attempting to create has the same name as another component within this database schema.
- Action:
- Create the new component using a different name or within a different schema.
- Cause:
- The design time metadata for this component could not be fetched.
- Action:
- Contact Oracle Customer Support.
- Cause:
- Some attributes could not be saved, possibly because they are invalid.
- Action:
- Contact Oracle Customer Support.
- Cause:
- The design time metadata could not be saved, either because there were one or more invalid attributes or because the component was not in an appropriate state.
- Action:
- Contact Oracle Customer Support.
- Cause:
- Some attributes could not be saved, possibly because they are invalid.
- Action:
- Contact Oracle Customer Support.
- Cause:
- The design time metadata could not be saved, either because there were one or more invalid attributes or because the component was not in an appropriate state.
- Action:
- Contact Oracle Customer Support.
- Cause:
- The server could not be reached.
- Action:
- Check to see if the URL is valid, and ensure that you have the correct proxy settings.
- Cause:
- The URL could not be reached.
- Action:
- Check to see if the URL is valid, and ensure that you have the correct proxy settings.
- Cause:
- Something occurred within a wizard while moving from one section to another, possibly while executing the section level pre and post functions.
- Action:
- Contact Oracle Customer Support.
- Cause:
- Something occurred while loading the component metadata for editing, possibly because the metadata has been removed or an inconsistency exists.
- Action:
- Contact Oracle Customer Support.
- Cause:
- Something occurred while saving the component metadata for editing, possibly because there is some inconsistency in the metadata or there is a problem in the underlying database.
- Action:
- Look at the Oracle error. If you cannot resolve it, contact Oracle Customer Support.
- Cause:
- Something occurred while saving the component metadata for editing, possibly because there is some inconsistency in the metadata or there is a problem in the underlying database.
- Action:
- Look at the Oracleerror. If you cannot resolve it, contact Oracle Customer Support.
- Cause:
- Something occurred while creating a new version of a component, possibly because there is already a version with this number, or because there is a problem writing to the database.
- Action:
- Look at the Oracle error. If you cannot resolve it, contact Oracle Customer Support.
- Cause:
- This happens while creating a new copy of a component. It could be because there is some problem while writing to the database.
- Action:
- Look at the Oracle error. If you cannot resolve it, contact Oracle Customer Support.
- Cause:
- It is possible that the schema on which the application is built has been removed.
- Action:
- Try to recreate the schema. If you still get the same error, contact Oracle Customer Support.
- Cause:
- It is possible that the component metadata has been removed inconsistently.
- Action:
- Contact Oracle Customer Support.
- Cause:
- It is possible that the component metadata has been removed inconsistently.
- Action:
- Contact Oracle Customer Support.
- Cause:
- It is possible that the component metadata has been removed inconsistently.
- Action:
- Contact Oracle Customer Support.
- Cause:
- It is possible that the component metadata has been removed inconsistently.
- Action:
- Contact Oracle Customer Support.
- Cause:
- It is possible that the component metadata has been removed inconsistently, or that there is a problem writing to the database table.
- Action:
- Check the Oracle error or contact Oracle Customer Support.
- Cause:
- It is possible that the component metadata has been removed inconsistently, or that there is a problem writing to the database table.
- Action:
- Check the Oracle error or contact Oracle Customer Support.
- Cause:
- It is possible that the component metadata has been removed inconsistently.
- Action:
- Contact Oracle Customer Support.
- Cause:
- It is possible that the component metadata has been removed inconsistently.
- Action:
- Contact Oracle Customer Support.
- Cause:
- It is possible that the component metadata has been removed inconsistently, or that there is a problem writing to the database table.
- Action:
- Check the Oracle error or contact Oracle Customer Support.
- Cause:
- It is possible that the component metadata has been removed inconsistently, or that there is a problem writing to the database table.
- Action:
- Check the Oracle error or contact Oracle Customer Support.
- Cause:
- It is possible that the component metadata has been removed inconsistently, or that there is a problem writing to the database table.
- Action:
- Check the Oracle error or contact Oracle Customer Support.
- Cause:
- It is possible that the component metadata has been removed inconsistently, or that there is a problem writing to the database table.
- Action:
- Check the Oracle error or contact Oracle Customer Support.
- Cause:
- It is possible that the component metadata has been removed inconsistently, or that there is a problem writing to the database table.
- Action:
- Check the Oracle error or contact Oracle Customer Support.
- Cause:
- See the ORA error in the error message.
- Action:
- Contact Oracle Customer Support.
- Cause:
- See the ORA error in the error message.
- Action:
- Contact Oracle Customer Support.
- Cause:
- See the ORA error in the error message.
- Action:
- Contact Oracle Customer Support.
- Cause:
- See the ORA error in the error message.
- Action:
- Contact Oracle Customer Support.
- Cause:
- It is possible that the component metadata has been removed inconsistently, or that there is a problem writing to the database table.
- Action:
- Check the Oracle error or contact Oracle Customer Support.
- Cause:
- It is possible that a user ID for this username does not exist, possibly because it was removed.
- Action:
- Contact Oracle Customer Support.
- Cause:
- Either the user does not have permissions on the table named in the query, or the table does not exist.
- Action:
- Check to see if the table exists. If it doesn't exist, create it, and be sure to grant the appropriate privileges to the user.
- Cause:
- Either the user does not have permissions on the table named in the query, or the table does not exist.
- Action:
- Check to see if the table exists. If it doesn't exist, create it, and be sure to grant the appropriate privileges to the user.
- Cause:
- The SQL statement in the error message could not be parsed due to incorrect syntax or usage, or because it referenced an inaccessible object.
- Action:
- Contact Oracle Customer Support.
- Cause:
- Either the user does not have permissions on the table named in the query, or the table does not exist.
- Action:
- Check to see if the table exists. If it doesn't exist, create it, and be sure to grant the appropriate privileges to the user.
- Cause:
- Either the user does not have permissions on the table named in the query, or the table does not exist.
- Action:
- Check to see if the table exists. If it doesn't exist, create it, and be sure to grant the appropriate privileges to the user.
- Cause:
- Either the user does not have permissions on the table named in the query, or the table does not exist.
- Action:
- Check to see if the table exists. If it doesn't exist, create it, and be sure to grant the appropriate privileges to the user.
- Cause:
- See the ORA error referenced in this error message.
- Action:
- Contact Oracle Customer Support.
- Cause:
- Something may have occurred while executing functions in the component builder.
- Action:
- Contact Oracle Customer Support.
- Cause:
- An unexpected error occurred while inserting menu data.
- Action:
- Contact Oracle Customer Support.
- Cause:
- Design time metadata for the menu component could not be fetched.
- Action:
- Contact Oracle Customer Support.
- Cause:
- The current node is the top-most node, which means it does not have a parent.
- Action:
- Choose another child node.
- Cause:
- Some attributes could not be saved, possibly because they are invalid.
- Action:
- Contact Oracle Customer Support.
- Cause:
- Design time metadata for an image chart could not be fetched.
- Action:
- Contact Oracle Customer Support.
- Cause:
- There may not be enough permissions on the tables used in the form.
- Action:
- Check the error. If tables are mentioned, grant the appropriate privileges, or contact Oracle Customer Support.
- Cause:
- An error occurred while exporting the components listed.
- Action:
- Refer to the specific error message for each component.
- Cause:
- The database object may be invalid.
- Action:
- Check the status of the database object.
- Cause:
- There may be an error in the username, password, or connect string used to create the database link, or the server may not be ready for a connection.
- Action:
- See if the database is up and verify that all connection information is correct.
- Cause:
- The default value and the column are different datatypes.
- Action:
- Change the datatypes to match.
- Cause:
- The database object may be invalid.
- Action:
- Check the status of the database object.
- Cause:
- The user may not have privileges for all the objects referenced in the view.
- Action:
- Ensure that the user has the necessary privileges on all objects referenced by the view.
- Cause:
- The name for the new constraint is already in use.
- Action:
- Select a different name.
- Cause:
- It is possible that there are no permissions to disable the trigger, or that the trigger was dropped during this operation.
- Action:
- Check to see if the trigger exists and if the appropriate privileges have been granted.
- Cause:
- It is possible that there are no permissions to drop the trigger, or that the trigger was dropped during this operation.
- Action:
- Check to see if the trigger exists and if the appropriate privileges have been granted.
- Cause:
- You have not specified a name for the constraint you are creating.
- Action:
- Name the constraint.
- Cause:
- You are trying to edit an index from a unique/primary key.
- Action:
- Change the integrity constraints from the table instead of the unique/primary key.
- Cause:
- The constraint was not added to the table.
- Action:
- Click the Add to List button to add the constraint to the table.
- Cause:
- The remote database or listener could be down, or the connect information supplied could be wrong.
- Action:
- Verify the connect information. If the connect still does not occur, make sure the remote database and listener are up.
- Cause:
- A schema by this name might already exist or the user may not have sufficient privileges to create a schema.
- Action:
- Ensure that the name provided for the schema is unique and that the user has the necessary privileges.
- Cause:
- A schema by this name might already exist or the user may not have sufficient privileges to create a schema.
- Action:
- Ensure that the name provided for the schema is unique and that the user has the necessary privileges.
- Cause:
- The user may not have sufficient privilege to do GRANT ROLE.
- Action:
- Ensure that the user has the necessary privileges.
- Cause:
- The user may not have sufficient privilege to do REVOKE ROLE.
- Action:
- Ensure that the user has the necessary privileges.
- Cause:
- The user may not have sufficient privilege to do GRANT ROLE.
- Action:
- Ensure that the user has the necessary privileges.
- Cause:
- The user may not have sufficient privilege to do REVOKE ROLE.
- Action:
- Ensure that the user has the necessary privileges.
- Cause:
- The process of creating a role has failed, possibly due to insufficient privileges.
- Action:
- Ensure that the user has the appropriate privileges to create a role.
- Cause:
- It is possible that the proper permissions to kill the session are not in place, or that it was killed by somebody else in the process of this operation.
- Action:
- Check to see if the session still exists, then grant the appropriate privileges.
- Cause:
- See the ORA error in the error mesage.
- Action:
- Contact Oracle Customer Support.
- Cause:
- See the ORA error in the error mesage.
- Action:
- Contact Oracle Customer Support.
- Cause:
- See the ORA error in the error mesage.
- Action:
- Contact Oracle Customer Support.
- Cause:
- See the ORA error in the error mesage.
- Action:
- Contact Oracle Customer Support.
- Cause:
- See the ORA error in the error mesage.
- Action:
- Contact Oracle Customer Support.
- Cause:
- Some attributes were not saved, possibly because they are invalid.
- Action:
- Contact Oracle Customer Support.
- Cause:
- An error occurred while saving the component metadata.
- Action:
- Contact Oracle Customer Support.
- Cause:
- An error occurred in the user preference storage subsystem.
- Action:
- Contact Oracle Customer Support.
- Cause:
- Design time metadata could not be fetched.
- Action:
- Contact Oracle Customer Support.
- Cause:
- A blank Survey, Poll or Test Name was entered.
- Action:
- Enter a valid Survey, Poll or Test Name.
- Cause:
- A survey by that name already exists.
- Action:
- Enter a different Survey Name.
- Cause:
- More than one answer has been selected.
- Action:
- Select only one answer.
- Cause:
- A blank Last Name was entered.
- Action:
- Enter a valid Last Name.
- Cause:
- A blank First Name was entered.
- Action:
- Enter a valid First Name.
- Cause:
- A blank E-mail Address was entered.
- Action:
- Enter a valid E-mail Address.
- Cause:
- The E-mail Address that was entered might not be valid.
- Action:
- If the E-mail Address is not valid, change it. Otherwise no action is required.
- Cause:
- A blank Employee Number was entered.
- Action:
- Enter a valid Employee Number.
- Cause:
- A blank or invalid Start Date was entered.
- Action:
- Enter a valid Start Date in the format MM/DD/YYYY.
- Cause:
- An invalid End Date was entered.
- Action:
- Enter a valid End Date in the format MM/DD/YYYY.
- Cause:
- No answer was supplied for a question that required an answer.
- Action:
- Provide an answer for the question.
- Cause:
- The Number of Questions entered was either blank, not in the range of 01-99, or not All.
- Action:
- Enter either a number from 1 to 99, or All.
- Cause:
- The Other category checkbox was checked, but this option does not apply to the selected display style.
- Action:
- Uncheck the Other Category checkbox.
- Cause:
- The Allow Multiple Responses checkbox was checked, but this option does not apply to the selected display style.
- Action:
- Uncheck the Allow Multiple Responses checkbox.
- Cause:
- A Survey, Poll or Test by the specified name could not be found.
- Action:
- An Administrator must run Edit Defaults and select a valid Survey, Poll, or Test.
- Cause:
- A blank Company Name was entered.
- Action:
- Enter a valid Company Name.
- Cause:
- The Survey system could not add responses into the table OPC_SURVEY_RESPONSES.
- Action:
- A Database Administrator must investigate this problem.
- Cause:
- Table WWSUB_MODEL$ could not be read.
- Action:
- A Database Administrator must investigate this problem.
- Cause:
- Profile information for the user could not be read from the system context.
- Action:
- A Database Administrator must investigate this problem.
- Cause:
- The End Date for the Survey, Poll or Test has passed.
- Action:
- No action is necessary. No further responses will be accepted.
- Cause:
- An invalid special character was entered into the name.
- Action:
- Re-enter the name without special characters.
- Cause:
- While trying to place the Survey Form portlet on the specified page, it was discovered that the page is missing.
- Action:
- A Portal Administrator must investigate this problem.
- Cause:
- An error occured when trying to add a text item to the selected page group.
- Action:
- A Portal Administrator must investigate this problem.
- Cause:
- An error occurred when trying to update a text item in the selected page group.
- Action:
- A Portal Administrator must investigate this problem.
- Cause:
- A question that does not have the 'Response is optional' check box checked does not have any answers.
- Action:
- Enter at least one answer for the question.
- Cause:
- The page group specified could not be found.
- Action:
- Select a different page group.
- Cause:
- The Start Date for the Survey, Poll or Test has not occurred yet.
- Action:
- Wait until the Start Date before attempting to take the Survey, Poll, or Test.
- Cause:
- No Start Date was found for the selected Survey, Poll, or Test.
- Action:
- An Administrator must run Edit Defaults on the Form portlet for the specified Survey, Poll, or Test and specify a Start Date.
- Cause:
- A Triggers Section was selected for a TEXT question display type.
- Action:
- Select -- none -- for Triggers Section for a TEXT question display type.
- Cause:
- No answers have been entered.
- Action:
- If the display type is TEXT, no action is necessary. Otherwise, enter valid answer choices.
- Cause:
- No Survey, Poll, or Test with the specified name was found in the system.
- Action:
- Verify that the correct category - Survey, Poll or Test - was selected and that the correct name was entered, or browse names for the selected category.
- Cause:
- Table OPC_SURVEY_HEADER could not be accessed.
- Action:
- A Database Administrator must investigate this problem.
- Cause:
- Scoring can only be performed on a Test, not on a Survey or Poll.
- Action:
- Select a Test to be scored.
- Cause:
- Scoring can only be performed on a Test, not on a Survey or Poll.
- Action:
- Select a Test to be scored.
- Cause:
- A button was pressed, but no Survey, Poll, or Test name was entered.
- Action:
- Select a valid Survey, Poll or Test, then press the button.
- Cause:
- The reports server object that was specified does not exist.
- Action:
- Register the reports server, or specify the correct server name.
- Cause:
- The reports calendar object that was specified does not exist.
- Action:
- Register the reports calendar, or specify the correct reports calendar name.
- Cause:
- There was an internal error while rendering the calendar.
- Action:
- Contact Oracle Customer Support.
- Cause:
- A value was entered that contains non-numeric characters.
- Action:
- Enter only numeric characters.
- Cause:
- The operation to save parameters failed.
- Action:
- This is an internal error. Contact Oracle Customer Support.
- Cause:
- Initialization of the specified Builder attributes failed.
- Action:
- Refer to the relevant builder error message, and take the appropriate action.
- Cause:
- Initialization of the specified Server failed.
- Action:
- Check that the server is properly registered.
- Cause:
- The application was unable to delete the specified object.
- Action:
- This is an internal error. Contact Oracle Customer Support.
- Cause:
- An invalid error ID was specified.
- Action:
- This is an internal error. Contact Oracle Customer Support.
- Cause:
- The server is not accessible because the security check failed.
- Action:
- Contact your portal administrator to get access to the server.
- Cause:
- The printer is not accessible because the security check failed.
- Action:
- Contact your portal administrator to get access to the printer.
- Cause:
- The module is not accessible because the security check failed.
- Action:
- Contact your portal administrator to get access to the module.
- Cause:
- The output type (destype) is not accessible because the security check failed.
- Action:
- Contact your portal administrator to get access to the destype.
- Cause:
- The output format (desformat)is not accessible because the security check failed.
- Action:
- Contact portal administrator to get access to the desformat.
- Cause:
- The calendar check failed. The report cannot be run at this time.
- Action:
- Check the availability calendar to see when the report can be run.
- Cause:
- The calendar check failed. The report cannot be run on this server at this time.
- Action:
- Check the availability calendar to see when the server can be used to run the report.
- Cause:
- The calendar check failed. Printing on this printer is not possible at this time.
- Action:
- Check the availability calendar to see when the report can be printed on this printer.
- Cause:
- This generic access error indicates that you do not have the access privileges to perform this task.
- Action:
- Ask your portal administrator for the required privileges.
- Cause:
- The LOV access check failed. You currently do not have the privileges required to access this LOV.
- Action:
- Ask your portal administrator for the required privileges.
- Cause:
- The value specified was less than lower limit.
- Action:
- Specify a value within the valid range.
- Cause:
- The value specified was higher than high limit.
- Action:
- Specify a value within the valid range.
- Cause:
- The validation trigger failed.
- Action:
- Contact your portal administrator.
- Cause:
- A report name was not specified.
- Action:
- Specify a valid report name.
- Cause:
- A server name was not specified.
- Action:
- Specify a valid server name.
- Cause:
- The report name and the module name are conflicting.
- Action:
- Ensure that the module name and the report name are the same.
- Cause:
- An exception occurred when sending a request to the reports server. The report was not sent.
- Action:
- Contact Oracle Customer Support.
- Cause:
- Th Oracle Reports Web gateway URL was not specified.
- Action:
- Edit the server component, and specify the Oracle Reports Web gateway.
- Cause:
- The browser version is not supported. The Reports portlet could not be displayed in this version of the browser.
- Action:
- Upgrade the browser version. Refer to the product documentation for the supported browser versions.