TNS-01001: start (lamp;lt;lamp;nbsp;listener_namelamp;gt;( : start listener
Cause: Control program usage message.
Action: None.
Cause: Control program usage message.
Action: None.
TNS-01000: spawn (lamp;lt;lamp;nbsp;listener_namelamp;gt;( lamp;lt;lamp;nbsp;spawn_aliaslamp;gt; (lamp;lt;lamp;nbsp;(ARGUMENTS= arg0, arg1,... )lamp;gt;(
TNS-01000: spawn (lamp;lt;lamp;nbsp;listener_namelamp;gt;( lamp;lt;lamp;nbsp;spawn_aliaslamp;gt; (lamp;lt;lamp;nbsp;(ARGUMENTS= arg0, arg1,... )lamp;gt;(
Cause: Control program usage message.
Action: None.
Cause: Control program usage message.
Action: None.
TNS-00584: Valid node checking configuration error
TNS-00584: Valid node checking configuration error
Cause: Valid node checking specific Oracle Net configuration is invalid.
Action: Ensure the hosts specified in the invited_nodes and excluded_nodes are valid. For further details, turn on tracing and reexecute the operation.
Cause: Valid node checking specific Oracle Net configuration is invalid.
Action: Ensure the hosts specified in the invited_nodes and excluded_nodes are valid. For further details, turn on tracing and reexecute the operation.
TNS-00583: Valid node checking: unable to parse configuration parameters
TNS-00583: Valid node checking: unable to parse configuration parameters
Cause: Valid node checking was unable to parse the configuration due to syntactical errors.
Action: Ensure that the configuration syntax matches the Oracle reference manual documented syntax. For further details, turn on tracing and reexecute the operation.
Cause: Valid node checking was unable to parse the configuration due to syntactical errors.
Action: Ensure that the configuration syntax matches the Oracle reference manual documented syntax. For further details, turn on tracing and reexecute the operation.
TNS-00582: Receive failed due to timeout
TNS-00582: Receive failed due to timeout
Cause: The receive operation did not complete within the allowed time interval.
Action: Error is informational. Note, repeated receipt of this error could indicate an attempted Denial-Of-Service attack. Also, if the receipt of this error interferes w or a customer s normal operations, the customer may wish to lengthen the timeout.
Cause: The receive operation did not complete within the allowed time interval.
Action: Error is informational. Note, repeated receipt of this error could indicate an attempted Denial-Of-Service attack. Also, if the receipt of this error interferes w or a customer s normal operations, the customer may wish to lengthen the timeout.
TNS-00581: Send failed due to timeout
TNS-00581: Send failed due to timeout
Cause: The send operation did not complete within the allowed time interval.
Action: Error is informational. Note, repeated receipt of this error could indicate an attempted Denial-Of-Service attack. Also, if the receipt of this error interferes w or a customer s normal operations, the customer may wish to lengthen the timeout.
Cause: The send operation did not complete within the allowed time interval.
Action: Error is informational. Note, repeated receipt of this error could indicate an attempted Denial-Of-Service attack. Also, if the receipt of this error interferes w or a customer s normal operations, the customer may wish to lengthen the timeout.
TNS-00580: Read failed due to closed or invalid transport connection
TNS-00580: Read failed due to closed or invalid transport connection
Cause: Read attempt was made on a transport connection which was previously terminated or is somehow deemed to be invalid.
Action: Indicates a substantial transport level failure. Check the O or S configuration for the particular transport or contact the transport provider. For further details, turn on tracing and reexecute the operation.
Cause: Read attempt was made on a transport connection which was previously terminated or is somehow deemed to be invalid.
Action: Indicates a substantial transport level failure. Check the O or S configuration for the particular transport or contact the transport provider. For further details, turn on tracing and reexecute the operation.
TNS-00560: extraction of name from Entrust certificate failed
TNS-00560: extraction of name from Entrust certificate failed
Cause: An error occurred while attempting to extract a name from an Entrust certificate.
Action: This error is not normally visible to users. Enable Oracle Net tracing and attempt to reproduce the error. If it occurs, contact Oracle customer support.
Cause: An error occurred while attempting to extract a name from an Entrust certificate.
Action: This error is not normally visible to users. Enable Oracle Net tracing and attempt to reproduce the error. If it occurs, contact Oracle customer support.
TNS-00559: load of Entrust certificate failed
TNS-00559: load of Entrust certificate failed
Cause: An error occurred while attempting to validate the provided Entrust certificate.
Action: This error is not normally visible to users. Enable Oracle Net tracing and attempt to reproduce the error. If it occurs, contact Oracle customer support.
Cause: An error occurred while attempting to validate the provided Entrust certificate.
Action: This error is not normally visible to users. Enable Oracle Net tracing and attempt to reproduce the error. If it occurs, contact Oracle customer support.
TNS-00558: Entrust login failed
TNS-00558: Entrust login failed
Cause: Entrust failed to authenticate the username, password, and or or profile name that was presented.
Action: Specify correct values for the username, password or profile name. If no data was prompted for, contact Oracle support.
Cause: Entrust failed to authenticate the username, password, and or or profile name that was presented.
Action: Specify correct values for the username, password or profile name. If no data was prompted for, contact Oracle support.
TNS-00557: unsupported wallet retrieval method
TNS-00557: unsupported wallet retrieval method
Cause: The method specified for wallet retrieval is not supported. Currently, only files are supported for wallet retrieval.
Action: Specify FILE as the wallet retrieval method.
Cause: The method specified for wallet retrieval is not supported. Currently, only files are supported for wallet retrieval.
Action: Specify FILE as the wallet retrieval method.
TNS-00556: no method specified for wallet retrieval
TNS-00556: no method specified for wallet retrieval
Cause: A wallet resource locator was specified, but no method was given for the retrieval of the wallet.
Action: Specify the method by which the method is to be retrieved.
Cause: A wallet resource locator was specified, but no method was given for the retrieval of the wallet.
Action: Specify the method by which the method is to be retrieved.
TNS-00555: no directory specified for wallet resource locator
TNS-00555: no directory specified for wallet resource locator
Cause: It was specified that a file was to be used from which to retrieve a wallet, but no directory was specified for the wallet.
Action: Specify the directory where the wallet is located.
Cause: It was specified that a file was to be used from which to retrieve a wallet, but no directory was specified for the wallet.
Action: Specify the directory where the wallet is located.
TNS-00554: write failed
TNS-00554: write failed
Cause: The SSL adapter failed to send data over its connection.
Action: Examine the contents of sqlnet.log for more information. Enable Oracle Net tracing and try the connection again. If the connection fails, examine the trace file to determine the cause.
Cause: The SSL adapter failed to send data over its connection.
Action: Examine the contents of sqlnet.log for more information. Enable Oracle Net tracing and try the connection again. If the connection fails, examine the trace file to determine the cause.
TNS-00553: read failed
TNS-00553: read failed
Cause: The SSL adapter failed to read data from its connection.
Action: Examine the contents of sqlnet.log for more information. Enable Oracle Net tracing and try the connection again. If the connection fails, examine the trace file to determine the cause.
Cause: The SSL adapter failed to read data from its connection.
Action: Examine the contents of sqlnet.log for more information. Enable Oracle Net tracing and try the connection again. If the connection fails, examine the trace file to determine the cause.
TNS-00039: INTCTL: error while spawning a process
TNS-00039: INTCTL: error while spawning a process
Cause: An error was encountered while spawning a process due to an internal operating system dependent problem. Machine resources may be limited.
Action: Retry command. Check permissions on Interchange executables and the current setting of the search path. If necessary, terminate other applications to free up machine resources. If the error persists, contact Oracle Customer Support.
Cause: An error was encountered while spawning a process due to an internal operating system dependent problem. Machine resources may be limited.
Action: Retry command. Check permissions on Interchange executables and the current setting of the search path. If necessary, terminate other applications to free up machine resources. If the error persists, contact Oracle Customer Support.
TNS-00038: INTCTL: Poorly formed address or command string
TNS-00038: INTCTL: Poorly formed address or command string
Cause: An unacceptable string was encountered while attempting to send a message to either the Navigator or Connection Manager. The addresses provided for either the Navigator or Connection Manager may be incorrectly constructed.
Action: Check all address strings in configuration files (TNSNAMES.ORA, TNSNAV.ORA or TNSNET.ORA) and assure that they are properly formed. Regenerate the files, if possible. If all is correct, please contact Worldwide Customer Support.
Cause: An unacceptable string was encountered while attempting to send a message to either the Navigator or Connection Manager. The addresses provided for either the Navigator or Connection Manager may be incorrectly constructed.
Action: Check all address strings in configuration files (TNSNAMES.ORA, TNSNAV.ORA or TNSNET.ORA) and assure that they are properly formed. Regenerate the files, if possible. If all is correct, please contact Worldwide Customer Support.
TNS-00037: INTCTL: error opening Navigator or Connection Manager error files
TNS-00037: INTCTL: error opening Navigator or Connection Manager error files
Cause: Failed to open Navigator or Connection Manager error files when they have failed to start.
Action: Check that a Network Error directory exists and that all privileges on the directory are appropriate.
Cause: Failed to open Navigator or Connection Manager error files when they have failed to start.
Action: Check that a Network Error directory exists and that all privileges on the directory are appropriate.
TNS-00036: INTCTL: error reading from Navigator or Connection Manager error files
TNS-00036: INTCTL: error reading from Navigator or Connection Manager error files
Cause: Problem while reading from Navigator or Connection Manager error files generated by the Navigator or Connection Manager when they fail to start.
Action: Check that a standard Network Error directory exists and that all privileges on the directory are appropriate.
Cause: Problem while reading from Navigator or Connection Manager error files generated by the Navigator or Connection Manager when they fail to start.
Action: Check that a standard Network Error directory exists and that all privileges on the directory are appropriate.
TNS-00035: INTCTL: error while constructing full file name
TNS-00035: INTCTL: error while constructing full file name
Cause: Problem while constructing the full path for a file name because the path name to the file or the environment variables are incorrect. Files looked up include TNSNAMES.ORA, TNSNAV.ORA, INTCHG.ORA and the error files for the Navigator and Connection Manager.
Action: Check that all environment variables are defined correctly and that all configuration files exist in their correct places.
Cause: Problem while constructing the full path for a file name because the path name to the file or the environment variables are incorrect. Files looked up include TNSNAMES.ORA, TNSNAV.ORA, INTCHG.ORA and the error files for the Navigator and Connection Manager.
Action: Check that all environment variables are defined correctly and that all configuration files exist in their correct places.
TNS-00034: INTCTL: internal NR error
TNS-00034: INTCTL: internal NR error
Cause: Problem with internal Interchange routines.
Action: Normally not visible to the user. Try starting INTCTL again. If the error persists, check the product installation. If it is correct, contact Oracle Customer Support.
Cause: Problem with internal Interchange routines.
Action: Normally not visible to the user. Try starting INTCTL again. If the error persists, check the product installation. If it is correct, contact Oracle Customer Support.
TNS-00033: INTCTL: internal NL error
TNS-00033: INTCTL: internal NL error
Cause: Problem with internal TNS module NL.
Action: Normally not visible to the user. Try starting INTCTL again. If the error persists, check the product installation. If it is correct, contact Oracle Customer Support.
Cause: Problem with internal TNS module NL.
Action: Normally not visible to the user. Try starting INTCTL again. If the error persists, check the product installation. If it is correct, contact Oracle Customer Support.
TNS-00032: INTCTL: internal NS error
TNS-00032: INTCTL: internal NS error
Cause: Problem interfacing with TNS.
Action: Normally not visible to the user. Try starting INTCTL again. If the error persists, check the product installation. If it is correct, contact Oracle Customer Support.
Cause: Problem interfacing with TNS.
Action: Normally not visible to the user. Try starting INTCTL again. If the error persists, check the product installation. If it is correct, contact Oracle Customer Support.
TNS-00031: INTCTL: internal NT error
TNS-00031: INTCTL: internal NT error
Cause: Problem interfacing to the protocol adapters installed.
Action: Normally not visible to the user. Try starting INTCTL again. If the error persists, check the product installation. If it is correct, contact Oracle Customer Support.
Cause: Problem interfacing to the protocol adapters installed.
Action: Normally not visible to the user. Try starting INTCTL again. If the error persists, check the product installation. If it is correct, contact Oracle Customer Support.
TNS-00028: INTCTL: Could not resolve Connection Manager s name or address
TNS-00028: INTCTL: Could not resolve Connection Manager s name or address
Cause: The Connection Manager s name does not have a definition that the Navigator knows about, nor is the name or address available in the TNSNAMES.ORA file. The name may also be incorrect in the INTCHG.ORA file.
Action: Verify that the Connection Manager s name is in the TNSNET.ORA file read by the Navigator or in the TNSNAMES.ORA file. Be sure that INTCHG.ORA is correct.
Cause: The Connection Manager s name does not have a definition that the Navigator knows about, nor is the name or address available in the TNSNAMES.ORA file. The name may also be incorrect in the INTCHG.ORA file.
Action: Verify that the Connection Manager s name is in the TNSNET.ORA file read by the Navigator or in the TNSNAMES.ORA file. Be sure that INTCHG.ORA is correct.
TNS-00027: INTCTL: Could not resolve Navigator s name or address
TNS-00027: INTCTL: Could not resolve Navigator s name or address
Cause: The Navigator s name to address definition is missing.
Action: Check TNSNAMES.ORA file and make sure to include a definition for the name specified.
Cause: The Navigator s name to address definition is missing.
Action: Check TNSNAMES.ORA file and make sure to include a definition for the name specified.
TNS-00026: INTCTL: TNS_ADMIN directory set, and is being used
TNS-00026: INTCTL: TNS_ADMIN directory set, and is being used
Cause: The TNS_ADMIN environment variable is set properly. INTCTL will use the TNS_ADMIN directory. This is only an informative message. If you do not want it to be used, and want the default directory to be used instead, then unset TNS_ADMIN and reexecute.
Action: None.
Cause: The TNS_ADMIN environment variable is set properly. INTCTL will use the TNS_ADMIN directory. This is only an informative message. If you do not want it to be used, and want the default directory to be used instead, then unset TNS_ADMIN and reexecute.
Action: None.
TNS-00025: INTCTL: The ORACLE environment is not set up correctly
TNS-00025: INTCTL: The ORACLE environment is not set up correctly
Cause: The ORACLE environment is incorrectly set up.
Action: Refer to the Oracle operating system specific documentation for your platform for information on how the ORACLE environment should be set. Correct it and rerun INTCTL. Make sure the ORACLE environment includes the correct directories.
Cause: The ORACLE environment is incorrectly set up.
Action: Refer to the Oracle operating system specific documentation for your platform for information on how the ORACLE environment should be set. Correct it and rerun INTCTL. Make sure the ORACLE environment includes the correct directories.
TNS-00024: INTCTL: Unable to contact Navigator to obtain Connection Manager address
TNS-00024: INTCTL: Unable to contact Navigator to obtain Connection Manager address
Cause: The Navigator is not running.
Action: Verify that the Navigator is running by doing a status request on the Navigator (use the Interchange Control Utility command STATUS). If necessaary, start the Navigator using the Interchange Control Utility. Verify that the network is properly configured; if the error persists, contact Worldwide Customer Support.
Cause: The Navigator is not running.
Action: Verify that the Navigator is running by doing a status request on the Navigator (use the Interchange Control Utility command STATUS). If necessaary, start the Navigator using the Interchange Control Utility. Verify that the network is properly configured; if the error persists, contact Worldwide Customer Support.
TNS-00023: INTCTL: missing ADDRESS(es) in config files
TNS-00023: INTCTL: missing ADDRESS(es) in config files
Cause: Configuration files do not contain an ADDRESS or ADDRESS_LIST component.
Action: Define the Connection Manager ADDRESS(es) in the TNSNET.ORA file and check the Navigator ADDRESS(es) in the TNSNAV.ORA file, then restart the INTCTL program.
Cause: Configuration files do not contain an ADDRESS or ADDRESS_LIST component.
Action: Define the Connection Manager ADDRESS(es) in the TNSNET.ORA file and check the Navigator ADDRESS(es) in the TNSNAV.ORA file, then restart the INTCTL program.
TNS-00022: INTCTL: missing CMANAGER_NAME in INTCHG.ORA
TNS-00022: INTCTL: missing CMANAGER_NAME in INTCHG.ORA
Cause: INTCHG.ORA does not contain a CMANAGER_NAME component.
Action: Define the correct name for the CMANAGER_NAME, then restart the INTCTL program.
Cause: INTCHG.ORA does not contain a CMANAGER_NAME component.
Action: Define the correct name for the CMANAGER_NAME, then restart the INTCTL program.
TNS-00021: INTCTL: missing INTERCHANGE_DATA in INTCHG.ORA
TNS-00021: INTCTL: missing INTERCHANGE_DATA in INTCHG.ORA
Cause: INTCHG.ORA does not contain an INTERCHANGE_DATA component.
Action: Define the correct data for the Connection Manager, then restart the INTCTL program.
Cause: INTCHG.ORA does not contain an INTERCHANGE_DATA component.
Action: Define the correct data for the Connection Manager, then restart the INTCTL program.
TNS-00020: INTCTL: missing NAVIGATOR_DATA in TNSNAV.ORA
TNS-00020: INTCTL: missing NAVIGATOR_DATA in TNSNAV.ORA
Cause: TNSNAV.ORA does not contain the NAVIGATOR_DATA component.
Action: Define the ADDRESS(es) for the Navigator, then restart the INTCTL program.
Cause: TNSNAV.ORA does not contain the NAVIGATOR_DATA component.
Action: Define the ADDRESS(es) for the Navigator, then restart the INTCTL program.
TNS-00019: INTCTL: error initializing the national language interface
TNS-00019: INTCTL: error initializing the national language interface
Cause: The message file could not be found.
Action: Make sure that the ORACLE environment is set and that the message file is in the correct place.
Cause: The message file could not be found.
Action: Make sure that the ORACLE environment is set and that the message file is in the correct place.
TNS-00018: INTCTL: TNS_ADMIN not defined
TNS-00018: INTCTL: TNS_ADMIN not defined
Cause: The TNS_ADMIN pointer is improperly set.
Action: No action necessary; TNS_ADMIN need only be set if you want to use a different network environment.
Cause: The TNS_ADMIN pointer is improperly set.
Action: No action necessary; TNS_ADMIN need only be set if you want to use a different network environment.
TNS-00017: INTCTL: error while performing NS receive command
TNS-00017: INTCTL: error while performing NS receive command
Cause: Internal NS error. Connection may be lost.
Action: If the error persists contact Oracle Customer Support.
Cause: Internal NS error. Connection may be lost.
Action: If the error persists contact Oracle Customer Support.
TNS-00016: INTCTL: error while performing NS send command
TNS-00016: INTCTL: error while performing NS send command
Cause: Internal NS error. Connection may be lost.
Action: If the error persists contact Oracle Customer Support.
Cause: Internal NS error. Connection may be lost.
Action: If the error persists contact Oracle Customer Support.
TNS-00015: INTCTL: error while closing terminal input channel
TNS-00015: INTCTL: error while closing terminal input channel
Cause: Could not close terminal input channel. Internal error.
Action: Normally not visible to the user. Restart the INTCTL program. If error persists, contact Oracle Customer Support.
Cause: Could not close terminal input channel. Internal error.
Action: Normally not visible to the user. Restart the INTCTL program. If error persists, contact Oracle Customer Support.
AMD-00117: input file string not found
AMD-00117: input file string not found
Cause: The input text file was not found in the specified location.
Action: Copy the input text file to the specified location, then retry.
Cause: The input text file was not found in the specified location.
Action: Copy the input text file to the specified location, then retry.
AMD-00116: PROCEDURE string, read error
AMD-00116: PROCEDURE string, read error
Cause: UTL_FILE.READ_ERROR: Possible software or hardware problem when accessing a file.
Action: Verify that hardware is functioning normally, then retry. Contact Oracle Support Services if needed.
Cause: UTL_FILE.READ_ERROR: Possible software or hardware problem when accessing a file.
Action: Verify that hardware is functioning normally, then retry. Contact Oracle Support Services if needed.
AMD-00115: PROCEDURE string, invalid file handle
AMD-00115: PROCEDURE string, invalid file handle
Cause: UTL_FILE.INVALID_FILEHANDLE: Possible software or hardware problem when accessing a file.
Action: Verify that hardware is functioning normally, then retry. Contact Oracle Support Services if needed.
Cause: UTL_FILE.INVALID_FILEHANDLE: Possible software or hardware problem when accessing a file.
Action: Verify that hardware is functioning normally, then retry. Contact Oracle Support Services if needed.
AMD-00114: PROCEDURE string, internal error
AMD-00114: PROCEDURE string, internal error
Cause: UTL_FILE.INTERNAL_ERROR: Possible hardware or software problem when accessing a file.
Action: Verify that hardware is functioning normally, then retry. Contact Oracle Support Services if needed.
Cause: UTL_FILE.INTERNAL_ERROR: Possible hardware or software problem when accessing a file.
Action: Verify that hardware is functioning normally, then retry. Contact Oracle Support Services if needed.
AMD-00113: PROCEDURE string, invalid operation
AMD-00113: PROCEDURE string, invalid operation
Cause: UTL_FILE.INVALID_OPERATION: An error occurred when accessing a file.
Action: Check that the file being accessed is not already opened by another program, then retry.
Cause: UTL_FILE.INVALID_OPERATION: An error occurred when accessing a file.
Action: Check that the file being accessed is not already opened by another program, then retry.
AMD-00112: PROCEDURE string, invalid mode
AMD-00112: PROCEDURE string, invalid mode
Cause: UTL_FILE.INVALID_MODE: An error occurred when accessing a file.
Action: Check that files being accessed have correct permissions, then retry.
Cause: UTL_FILE.INVALID_MODE: An error occurred when accessing a file.
Action: Check that files being accessed have correct permissions, then retry.
AMD-00111: PROCEDURE string, invalid directory: string
AMD-00111: PROCEDURE string, invalid directory: string
Cause: Directory name provided to a procedure was found to be invalid.
Action: Ensure that the directory name represents a valid directory.
Cause: Directory name provided to a procedure was found to be invalid.
Action: Ensure that the directory name represents a valid directory.
AMD-00110: parameter string of string not valid
AMD-00110: parameter string of string not valid
Cause: A parameter was found to be invalid.
Action: Ensure that the parameter is correctly formed and valid.
Cause: A parameter was found to be invalid.
Action: Ensure that the parameter is correctly formed and valid.
AMD-00109: Parent metadata entity has too many child entities. string string has more than string string
AMD-00109: Parent metadata entity has too many child entities. string string has more than string string
Cause: A metadata entity was found to have too many dependent entities of another type.
Action: Add the required mapping.
Cause: A metadata entity was found to have too many dependent entities of another type.
Action: Add the required mapping.
AMD-00108: Dimension string is improperly mapped; the dimension has string hierarchies mapped, but hierarchy level string has string columns mapped
AMD-00108: Dimension string is improperly mapped; the dimension has string hierarchies mapped, but hierarchy level string has string columns mapped
Cause: Dimension table columns could not be accessed, because dimension hierarchies were incorrectly mapped.
Action: Add or remove dimension hierarchies or hierarchy level mappings. The number of dimension hierarchies must equal the number of hierarchy level columns.
Cause: Dimension table columns could not be accessed, because dimension hierarchies were incorrectly mapped.
Action: Add or remove dimension hierarchies or hierarchy level mappings. The number of dimension hierarchies must equal the number of hierarchy level columns.
AMD-00107: no root level in hierarchy: string
AMD-00107: no root level in hierarchy: string
Cause: A hierarchy was found to have no root level.
Action: Use the ADD_LEVEL_TO_HIERARCHY procedure to add a level to the hierarchy. Specify the root level in the child parameter and leave the parent parameter blank.
Cause: A hierarchy was found to have no root level.
Action: Use the ADD_LEVEL_TO_HIERARCHY procedure to add a level to the hierarchy. Specify the root level in the child parameter and leave the parent parameter blank.
AMD-00106: parent string string must be removed before child string string can be removed
AMD-00106: parent string string must be removed before child string string can be removed
Cause: A metadata entity could not be removed, because it was the child of another metadata entity.
Action: Remove the parent metadata entity. All the dependent entities will be removed with the parent.
Cause: A metadata entity could not be removed, because it was the child of another metadata entity.
Action: Remove the parent metadata entity. All the dependent entities will be removed with the parent.
AMD-00105: Level string cannot be added to the hierarchy; the specified parent level string is already the parent of string
AMD-00105: Level string cannot be added to the hierarchy; the specified parent level string is already the parent of string
Cause: The level specified as the parent in the ADD_LEVEL_TO_HIERARCHY procedure could not be used, because it was the parent of another level within the hierarchy.
Action: In the ADD_LEVEL_TO_HIERARCHY procedure, specify a parent that is not already a parent of another level within a hierarchy.
Cause: The level specified as the parent in the ADD_LEVEL_TO_HIERARCHY procedure could not be used, because it was the parent of another level within the hierarchy.
Action: In the ADD_LEVEL_TO_HIERARCHY procedure, specify a parent that is not already a parent of another level within a hierarchy.
AMD-00104: Level string cannot be added to the hierarchy; parent and child parameters represent the same level
AMD-00104: Level string cannot be added to the hierarchy; parent and child parameters represent the same level
Cause: The same level name was specified for both the parent and the child parameters of the ADD_LEVEL_TO_HIERARCHY procedure.
Action: Determine which level should be the parent of the new level being added to the hierarchy. Specify the parent in the parent parameter and the new level in the child parameter of the ADD_LEVEL_TO_HIERARCHY procedure. Re-run the procedure.
Cause: The same level name was specified for both the parent and the child parameters of the ADD_LEVEL_TO_HIERARCHY procedure.
Action: Determine which level should be the parent of the new level being added to the hierarchy. Specify the parent in the parent parameter and the new level in the child parameter of the ADD_LEVEL_TO_HIERARCHY procedure. Re-run the procedure.
AMD-00103: %s string does not have a string
AMD-00103: %s string does not have a string
Cause: A required child entity was not found for a metadata entity.
Action: Refer to the Oracle9i OLAP User s Guide to determine which metadata entities require dependent entities.
Cause: A required child entity was not found for a metadata entity.
Action: Refer to the Oracle9i OLAP User s Guide to determine which metadata entities require dependent entities.
AMD-00102: invalid metadata entity: string string
AMD-00102: invalid metadata entity: string string
Cause: An OLAP metadata entity was found to be invalid.
Action: Check the mapping to columns in your data warehouse tables or views.
Cause: An OLAP metadata entity was found to be invalid.
Action: Check the mapping to columns in your data warehouse tables or views.
AMD-00101: cannot create string string ; metadata entity already exists
AMD-00101: cannot create string string ; metadata entity already exists
Cause: A metadata entity could not be created, because it already exists in the OLAP Catalog.
Action: When creating a new metadata entity, specify an entity name that is unique for the entity owner. Refer to the OLAP Catalog union views (named with the OLAP2U prefix) for existing OLAP metadata entity names.
Cause: A metadata entity could not be created, because it already exists in the OLAP Catalog.
Action: When creating a new metadata entity, specify an entity name that is unique for the entity owner. Refer to the OLAP Catalog union views (named with the OLAP2U prefix) for existing OLAP metadata entity names.
AMD-00100: not found: string string
AMD-00100: not found: string string
Cause: A metadata entity could not be found in the OLAP Catalog.
Action: Check that the metadata entity name and owner are properly specified. Refer to the OLAP Catalog union views named with the OLAP2U prefix) for existing OLAP metadata entity names.
Cause: A metadata entity could not be found in the OLAP Catalog.
Action: Check that the metadata entity name and owner are properly specified. Refer to the OLAP Catalog union views named with the OLAP2U prefix) for existing OLAP metadata entity names.
PLW-07204: conversion away from column type may result in sub-optimal query plan
PLW-07204: conversion away from column type may result in sub-optimal query plan
Cause: The column type and the bind type do not exactly match. This may result in the column being converted to the type of the bind variable. This type conversion may prevent the SQL optimizer from using any index the column participates in. This may adversely affect the execution performance of this statement.
Action: To make use of any index for this column, make sure the bind type is the same type as the column type.
Cause: The column type and the bind type do not exactly match. This may result in the column being converted to the type of the bind variable. This type conversion may prevent the SQL optimizer from using any index the column participates in. This may adversely affect the execution performance of this statement.
Action: To make use of any index for this column, make sure the bind type is the same type as the column type.
PLW-07203: parameter string may benefit from use of the NOCOPY compiler hint
PLW-07203: parameter string may benefit from use of the NOCOPY compiler hint
Cause: The mode of the specified parameter was IN OUT or OUT. Use of the NOCOPY compiler hint may speed up calls to this subprogram.
Action: Change the mode of the parameter to explicitly use the NOCOPY compiler hint. For example, if your subprogram declaration is: PROCEDURE proc(p1 IN OUT CLOB); you can change it to: PROCEDURE proc(p1 IN OUT NOCOPY clob); to get the benefit of the NOCOPY hint. For member procedures or functions in object types, you may have to explicitly declare the SELF parameter as illustrated in the following: MEMBER PROCEDURE proc(SELF IN OUT NOCOPY MY_TYPE);
Cause: The mode of the specified parameter was IN OUT or OUT. Use of the NOCOPY compiler hint may speed up calls to this subprogram.
Action: Change the mode of the parameter to explicitly use the NOCOPY compiler hint. For example, if your subprogram declaration is: PROCEDURE proc(p1 IN OUT CLOB); you can change it to: PROCEDURE proc(p1 IN OUT NOCOPY clob); to get the benefit of the NOCOPY hint. For member procedures or functions in object types, you may have to explicitly declare the SELF parameter as illustrated in the following: MEMBER PROCEDURE proc(SELF IN OUT NOCOPY MY_TYPE);
PLW-07202: bind type would result in conversion away from column type
PLW-07202: bind type would result in conversion away from column type
Cause: The column type and the bind type do not exactly match. This will result in the column being converted to the type of the bind variable. This type conversion may prevent the SQL optimizer from using any index the column participates in. This may adversely affect the execution performance of this statement.
Action: To make use of any index for this column, make sure the bind type is the same type as the column type.
Cause: The column type and the bind type do not exactly match. This will result in the column being converted to the type of the bind variable. This type conversion may prevent the SQL optimizer from using any index the column participates in. This may adversely affect the execution performance of this statement.
Action: To make use of any index for this column, make sure the bind type is the same type as the column type.
PLW-06003: unknown inquiry directive string
PLW-06003: unknown inquiry directive string
Cause: An unknown inquiry directive was used. The inquiry directive is neither predefined nor user-defined.
Action: Use a predefined inquiry directive or define the inquiry directive.
Cause: An unknown inquiry directive was used. The inquiry directive is neither predefined nor user-defined.
Action: Use a predefined inquiry directive or define the inquiry directive.
Subscribe to:
Posts (Atom)