-999 | An internal error occurred. The OLAP Miner Server might not be running. This application will be shut down. |
Explanation: An error occurred within the OLAP Miner server.
User Response: Use the information in the message to diagnose the problem.
0 | The operation was successful. |
Explanation: The operation was successful.
User Response: No action is required.
2 | Invalid connection state |
Explanation: The OLAP Miner server received an invalid internal request.
User Response: Contact IBM Software Support.
3 | An OLAP Miner server I/O error occurred. Error message = <message>. |
Explanation: An internal error occurred in the OLAP Miner server. This error might occur if the data directory does not have write access. If you are using the OMRunDef program, it might be because the parameters you provided are not in the correct case.
User Response: Ensure that write access is available for the data directory and all of its subdirectories. If you are using OMRunDef, ensure that you provide all parameters in the correct case. If you cannot resolve the problem, contact IBM Software Support.
4 | A client side I/O error occurred. Error message = <message>. |
Explanation: An internal error occurred in the OLAP Miner client.
User Response: Use the information in the message to diagnose the problem. If you cannot resolve the problem, contact IBM Software Support.
5 | The requested resource <resource> is currently locked. |
Explanation: The resource that you tried to access is locked.
User Response: Ensure that the resource is unlocked. If you cannot resolve the problem, contact IBM Software Support.
6 | OLAP Miner server received an invalid internal request <request>. |
Explanation: The OLAP Miner server received an invalid internal request.
User Response: Contact IBM Software Support.
7 | The client cannot access the requested resource <resource>. |
Explanation: The client cannot access the requested resource.
User Response: Ensure that you have access authority to the object that you selected.
8 | Invalid client command: <command>. |
Explanation: An invalid command was issued internally by the OLAP Miner client.
User Response: Contact IBM Software Support.
9 | No server reply was received. |
Explanation: The OLAP Miner server did not reply to an internal client command.
User Response: Contact IBM Software Support.
50 | The connection initialized successfully. |
Explanation: The connection initialized successfully.
User Response: No action is required.
51 | The OLAP Miner internal connection initialization failed. |
Explanation: An internal connection to the OLAP Miner failed to initialize.
User Response: Ensure that the OLAP Miner server is running. If you cannot resolve the problem, contact IBM Software Support.
100 | Invalid OLAP server alias <alias>. |
Explanation: The specified OLAP server alias is invalid.
User Response: Check the OLAP server alias or create the specified OLAP Miner server alias in the server configuration file.
111 | The number of connections exceeds the server limit. |
Explanation: The number of connections exceeds the limit that is specified in the server configuration file.
User Response: Reduce the number of connections to the OLAP Miner server or increase the connection limit that is specified in the server configuration file.
121 | The connection already exists. |
Explanation: The client is already connected to the OLAP Miner server.
User Response: No action is required.
160 | No definitions were found. |
Explanation: There are no definitions.
User Response: Create a definition first and then retry the operation.
172 | Unable to create an empty mining run file. |
Explanation: The server did not receive any content information from the mining run file.
User Response: No action is required.
230 | The mining run is in progress. |
Explanation: The mining run is in progress.
User Response: Wait for the mining run to finish or interrupt the current mining run before starting another mining run.
231 | The mining run cannot start because the number of mining runs in progress exceeds the limit specified in the OLAP Miner server configuration file. |
Explanation: The number of mining runs in progress exceeds the limit specified in the OLAP Miner server configuration file.
User Response: Either increase the max_kernel_runs value in the server configuration file or stop one of the current mining runs.
233 | The output file <output file name> cannot be initialized. |
Explanation: Unable to create the output file on OLAP Miner server.
User Response: Check the file system on the server.
250 | The mining run is not in progress. |
Explanation: The specified mining run is not in progress. Therefore, it cannot be stopped.
User Response: No action is required.
251 | The mining run cannot be interrupted. |
Explanation: Interruption of the specified mining run failed
User Response: Try again or wait for the mining run to finish.
270 | No OLAP server aliases are defined. |
Explanation: There are no OLAP server aliases specified in the OLAP miner server configuration file.
User Response: Create alias entries in the OLAP miner server configuration file.
350 | The target definition already exists. |
Explanation: The target definition already exists.
User Response: Repeat the action with a different target definition name.
390 | The mining run is still in progress. |
Explanation: The mining run is still in progress.
User Response: Wait for the mining run to complete.
391 | The mining run failed during execution. |
Explanation: The mining run failed.
User Response: Inspect the error with the Show Progress window.
392 | The run was interrupted. |
Explanation: The mining run was interrupted before its completion.
User Response: No action is required.
500 | An internal error occurred while verifying the XML definition file. The error was<message>. |
Explanation: An error occurred while processing the XML definition file.
User Response: Contact IBM Software Support.
506 | The outline has more dimensions than specified in the definition. |
Explanation: The saved definition is outdated according to the error message.
User Response: Re-edit the definition and ensure that the saved definition is up to date with the current outline.
507 | The number of dimensions has changed. The current number = <number in outline>, definition number = <number in definition>. |
Explanation: The saved definition is outdated according to the error message.
User Response: Re-edit the definition and ensure that the saved definition is up to date with the current outline.
508 | Dimension <dimension name> no longer exists in the current outline. |
Explanation: The saved definition is outdated according to the error message.
User Response: Re-edit the definition and ensure that the saved definition is up to date with the current outline.
509 | Member <member name> no longer exists in the current outline. |
Explanation: The saved definition is outdated according to the error message.
User Response: Re-edit the definition and ensure that the saved definition is up to date with the current outline.
510 | Member <member name> is no longer a member of dimension <dimension name>. |
Explanation: The saved definition is outdated according to the error message.
User Response: Re-edit the definition and ensure that the saved definition is up to date with the current outline.
511 | An I/O error occurred. Information returned was <message>. |
Explanation: An I/O error occurred while processing, possibly because the server is unable to write data into the OM data path.
User Response: Ensure that the data path is not read-only and that write access is allowed for the path.
1200 | Type a new definition name. |
Explanation: The Name field is empty.
User Response: Type a new definition name in the Name field.
1201 | The definition <definition name> cannot be deleted. The file might be in use. |
Explanation: The definition cannot be deleted if it is currently in use.
User Response: Ensure that the definition is not in use. If you cannot resolve the problem, contact the system administrator.
1202 | The results file <results file name> cannot be deleted. The file might be in use. |
Explanation: The results file cannot be deleted if it is currently in use.
User Response: Ensure that the results file is not in use. If you are unable to resolve the problem, contact the system administrator.
1203 | You cannot delete a server, application, or database. |
Explanation: You cannot delete a server application or database by using OLAP Miner.
User Response: You can delete only definitions and results files if you have authorization.
1204 | Type a user name. |
Explanation: The User name field is empty.
User Response: Type a user name in the User name field.
1205 | Type a password. |
Explanation: The Password field is empty.
User Response: Type a password in the Password field.
1206 | Type a search string. |
Explanation: The Find string field is empty.
User Response: Type a string to search.
1208 | String <string> not found. |
Explanation: The string was not found.
User Response: Ensure that all words are spelled correctly. Try different keywords.
1209 | No deviations were found. |
Explanation: OLAP Miner did not find deviations in the data that you selected in your definition.
User Response: You can create another definition to search for deviations or edit the definition from which these results were obtained to extend the data to be analyzed.
1210 | Invalid encoding value. |
Explanation: The character encoding is not supported by Java
User Response: Use a computer that has Java supported character encoding. If you cannot resolve the problem, contact the system administrator.
1211 | The linked reporting objects (text notes) were successfully created. |
Explanation: The linked reporting objects (text notes) were successfully created.
User Response: No action is required.
1212 | The linked reporting objects (text notes) were successfully deleted. |
Explanation: The linked reporting objects (text notes) were successfully deleted.
User Response: No action is required.
1213 | No linked reporting objects (text notes) were found by OLAP Miner to delete. |
Explanation: No linked reporting objects were found by OLAP Miner to delete.
User Response: Linked reporting objects might not have been created for the object selected. Use the Create LROs option before trying to delete them.
1214 | The definition <definition name> is running. You can view the definition but any changes that you make to the definition will not be saved. |
Explanation: You are trying to edit the definition while it is running. The definition cannot be changed while it is running.
User Response: You can view the definition while it is running, but if you want to make changes to it, you must either wait for the run to finish or cancel the run before saving any changes to the definition.
1215 | The definition <definition name> is running. Any changes that you make will not be saved. |
Explanation: You are trying to save a definition while it is running. The definition cannot be changed while it is running.
User Response: You can view the definition while it is running, but if you want to make changes to it, you must either wait for the run to finish or cancel the run before saving any changes to the definition.
1300 | Are you sure that you want to delete definition <definition name>? |
Explanation: Do you want to delete this definition?
User Response: Click Yes to delete the definition permanently or click No to keep the definition.
1302 | Are you sure that you want to delete results file <results file>? |
Explanation: Do you want to delete this results file?
User Response: Click Yes to delete the results file or click No to keep the results file.
1303 | Definition <definition name> has changed. This might make the current results files invalid for this definition. Click Yes to delete the current results. Click No to keep the current results. |
Explanation: If you change the definition, any current results files will not be appropriate for the new definition. To avoid confusion in the future, you can delete the current results files.
User Response: Click Yes to delete the results files or click No to keep the results files.
1304 | The mining run that created the results file <results file> returned an error. Delete this results file? |
Explanation: The results file is empty because the mining run returned an error.
User Response: Click Yes to delete the results file or click No to keep it. Normally, you should delete the results file unless you want to keep a record of the failed mining run.
1305 | The mining run that created the results file <results file> was interrupted. Delete this results file? |
Explanation: The results file is empty because the mining run was interrupted.
User Response: Click Yes to delete the results file or click No to keep it. Normally, you should delete the results file unless you want to keep a record of the failed mining run.
1306 | Do you want to create one linked reporting object (text note) for each deviation from the selected results file? |
Explanation: Do you want to create one linked reporting object for each deviation?
User Response: Click Yes to create one linked reporting object (text note) in the source database for each deviation in the results file or click No to cancel.
1307 | Do you want to delete all linked reporting objects (text notes) added to the <database name> database by OLAP Miner for the <definition name> definition? |
Explanation: Do you want to delete all linked reporting objects that were added to this database?
User Response: Click Yes to delete all linked reporting objects (text notes) added to the database for the selected definition or click No to keep the linked reporting objects.
1308 | Do you want to delete all linked reporting objects (text notes) added to the <database name> database by OLAP Miner? |
Explanation: Do you want to delete all the linked reporting objects that were added to this database?
User Response: Click Yes to delete all linked reporting objects (text notes) added to the database or click No to keep the linked reporting objects.
1400 | Error in loading the client configuration file. Unable to start the parser. Information returned was <error information>. |
Explanation: An error has occurred while loading the client XML configuration file.
User Response: Correct the configuration file and retry.
1402 | Error in loading the client configuration file. Invalid value <value> for tag <tag >. |
Explanation: An error has occurred while loading the client XML configuration file.
User Response: Correct the configuration file and retry.
1500 | The default browser cannot be located in the registry. Ensure that you have registered a default browser for loading HTML files. |
Explanation: The registry does not contain information about the default browser. The key HKEY_CLASSES_ROOT.html in the registry does not contain the reference to the default browser.
User Response: Open up a browser and configure it to be the default browser.
1502 | The default browser command <command> located in the registry no longer exists. Reinstall the browser or configure another browser as the default browser. |
Explanation: A default browser executable was located in the registry, but it no longer exists.
User Response: Reinstall the browser or configure another browser as the default browser.
2000 | An internal error occurred while creating the Table Model for the Deviation Viewer. The error was <error name>. |
Explanation: Errors occurred during processing.
User Response: Contact IBM Software Support.
2001 | The spreadsheet failed to open. OLAP Miner could not find a spreadsheet program on your computer. Either install a spreadsheet or specify in the OMClient.cfg file the location of your spreadsheet. OLAP Miner issued the command <command>. |
Explanation: OLAP Miner failed to open the spreadsheet from the Deviation Viewer. Initially, OLAP Miner tries to run the spreadsheet command specified in the OMClient.cfg file. If a command is not specified in the file, OLAP Miner searches the Windows registry for either Excel or Lotus 1-2-3 and runs whichever program is found.
User Response: Ensure that Excel or Lotus 1-2-3 is installed or that the OMClient.cfg file is configured properly.
2002 | Report script returned no data for table <table name>. |
Explanation: The report script did not return any data.
User Response: The members associated with the deviation might not have any data associated with them, or the user has no access to the data. Ensure that your database is loaded with data and it is calculated, and that the user has access to the data.
2003 | A null deviation was passed to the Deviation Viewer. |
Explanation: An internal error occurred in the OLAP Miner Deviation Viewer.
User Response: Contact IBM Software Support.
2004 | The deviation value displayed in the report does not match the value contained in the results file. The data in the OLAP database might have been updated since the results were produced. Run the deviation definition again to create a new results file. |
Explanation: The deviation results value does not match that of the value extracted from the current database. The results file might be outdated.
User Response: Run the definition again to create new results.
2005 | Columns truncated. |
Explanation: The table displayed in the viewer truncated some data to make the information easier to view.
User Response: To view the truncated data, open the spreadsheet from the Deviation Viewer and zoom out and in again on the dimensions to retrieve the missing values.
2006 | Rows truncated. |
Explanation: The table displayed in the viewer truncated some data to make the information easier to view.
User Response: To view the truncated data, open the spreadsheet from the Deviation Viewer and zoom out and in again on the dimensions to retrieve the missing values.
2007 | Rows and columns truncated. |
Explanation: The table displayed in the viewer truncated some data to make the information easier to view.
User Response: To view the truncated data, open the spreadsheet from the Deviation Viewer and zoom out and in again on the dimensions to retrieve the missing values.
3000 | The wizard cannot start because initialization did not complete successfully. |
Explanation: Wizard initialization failed, possibly because the outline API failed to initialize.
User Response: Ensure that the application/database that you are accessing is running on a DB2 OLAP Server system that is at the same release level as your OLAP Miner system. Also, ensure that all DB2 OLAP Server environment variables are configured correctly.
3001 | The following dimension/member pair no longer exists in the current outline < outline name>. |
Explanation: The definition contains members that no longer exist in the database outline, possibly because the members were deleted from the outline. Any results files for the definition will now be obsolete.
User Response: Finish editing the definition and run it to create new results and remove the old results.
3002 | The following dimension/member pairs no longer exist in the current outline <outline name>. |
Explanation: The definition contains members that no longer exist in the database outline, possibly because the members were deleted from the outline. Any results files for the definition will now be obsolete.
User Response: Finish editing the definition and run it to create new results and remove the old results.
3003 | The outline does not have any dimensions. |
Explanation: The database outline does not contain any dimensions or members. OLAP Miner cannot be used to create a definition.
User Response: Either create dimensions and members in the database or create a definition with a different database.
3004 | Type a name in the Name field. |
Explanation: The definition Name field of the wizard is empty.
User Response: Type a new name in the Name field to continue.
3005 | Type a different name. <definition name> is already used. |
Explanation: The name entered for the definition is already used in the current database.
User Response: Type a different name that is not being used in the current database.
3006 | The file for the <definition name> definition did not initialize correctly. |
Explanation: The parser could not parse the XML definition file. The file might be corrupted or someone might have edited the file accidentally.
User Response: Check the XML file to ensure that it is a valid XML file. If the file cannot be corrected, delete the definition and create a replacement.
3007 | Definition name <definition name> contains an invalid character. Type a different name that does not contain any of these characters: \ / : * ? " < > |. |
Explanation: The definition Name field of the wizard contains at least one invalid character.
User Response: Enter a different name that does not contain one of these characters \ / : * ? " < > |.
3500 | Cannot select members from different generations. |
Explanation: Selection of members from different generations within a dimension is not allowed.
User Response: Select members only from the same generation within a dimension.
3502 | Make a selection from the outline displayed in the left pane. |
Explanation: The Member Only or Member and Descendants button was clicked without a member selected in the left pane.
User Response: Select a member from the left pane and click the button again.
3503 | Shared members cannot be selected. Select the first instance of this shared member instead. |
Explanation: Selection of shared members is not allowed.
User Response: Select only non-shared members to be included in your definition.
3504 | Warning: Member and Descendants selection in the Accounts dimension might produce an invalid analysis. |
Explanation: A Member and Descendants selection in the Accounts dimension is normally inappropriate because it can lead to a definition that compares different types of data, such as an analysis that compares dollar values and ratio values.
User Response: Make Member and Descendants selections in the Accounts dimension only when the member and all of its descendants contain data of a similar nature.
3506 | Please make a selection from the right pane before clicking Remove. |
Explanation: The Remove button was clicked without a member selected in the right pane.
User Response: Select a member from the right pane and click the button again.
3507 | Make at least one Member and Descendants and one Member Only selection. |
Explanation: The definition makes sense only if there is at least one Member and Descendants and one Member Only selection.
User Response: Make at least one Member and Descendants and one Member Only selection.
3508 | Make at least one Member Only selection. |
Explanation: The definition makes sense only if there is at least one Member and Descendants and one Member Only selection.
User Response: Make at least one Member and Descendants and one Member Only selection.
3509 | Make at least one Member and Descendants selection. |
Explanation: The definition makes sense only if there is at least one Member and Descendants and one Member Only selection.
User Response: Make at least one Member and Descendants and one Member Only selection.
3511 | Type some text to search. |
Explanation: The Find Next button on the Find Member window was clicked with no text entered in the Find What field.
User Response: Type some text in the Find What field.
3512 | Reached the end of the outline. Press Find Next button to search from the top of the outline. |
Explanation: Reached the end of the outline, but the search text cannot be found.
User Response: Click Find Next to start searching for the entered text from the top of the outline or click Cancel to cancel the search.
3513 | Text found. |
Explanation: The text string entered was found.
User Response: Click Find Next to look for the next occurrence of the text or click Cancel to cancel the search.
3514 | Warning: Either the selected member <member name> or one of its descendants contains a formula. When a member with a formula is selected, OLAP Miner can analyze only the lowest level data available, and it will not detect deviations with higher level members. You can choose to proceed with the analysis of just the lowest level data or choose not to proceed. If you choose not to proceed, you can edit your definition to remove selections of members with formulas. Do you want to proceed with the lowest level data analysis? |
Explanation: The current selections have at least one member that contains a formula itself, or it has a descendant that contains a formula. OLAP Miner supports only level-0 analysis for a subcube or definition that contains a formula.
User Response: Click Yes to continue to analyze only level-0 data or click No to remove selections that use formulas.
3515 | Member and Descendants button is disabled because member <member name> contains at least one non-additive member. |
Explanation: The selected member has at least one descendant that uses either the subtract (-), multiply (*), divide (/), or percent (%) operator. These members cannot be included in the definition, so the Member and Descendants selection has been disabled.
User Response: Use Member Only for the selected member or choose a different member.
3516 | Member and Descendants choice is disabled because member <member name> is Label-only or it has Label-only descendants. |
Explanation: The selected member is either a label-only or has at least one descendant that is label-only. The member cannot be used for analysis because it contains only the value of its first child and not the aggregation of all of its descendants.
User Response: Use Member Only for the selected member or select all of its children if possible.
4000 | Cannot connect to server <server name>. Error message returned was <error message>. |
Explanation: The progress monitor cannot connect to the server.
User Response: Verify that the server is running and that the max_connections value is not exceeded.
4001 | Cannot log on to the server as user <user name>. |
Explanation: The progress monitor cannot log on to the server.
User Response: Verify that the OLAP server is running.
4002 | The progress monitor cannot connect to OLAP server. |
Explanation: The progress monitor cannot connect to the OLAP server.
User Response: Verify that the OLAP server is running.
4003 | Unable to read the server error file. Information returned was <error information>. |
Explanation: An error has occurred, but the error file cannot be retrieved from the server.
User Response: No action is required.
4004 | Attempting to interrupt the mining run, please wait... |
Explanation: Interrupting the run.
User Response: Wait.
4005 | The mining run was interrupted. |
Explanation: The run was interrupted.
User Response: No action is required.
4006 | An error occurred while interrupting the mining run. Information returned was <error information>. |
Explanation: General error.
User Response: No action is required.
4007 | Unable to retrieve the status file from the server. |
Explanation: A communication error occurred while retrieving the status file from the server.
User Response: No action is required.
4008 | Waiting for mining run to start, please wait... |
Explanation: Waiting for the kernel to start on the server.
User Response: Wait.
4009 | The mining run ended. |
Explanation: The mining run ended.
User Response: No action is required.
5000 | No arguments were provided. |
Explanation: Requires augments
User Response: Supply arguments.
5001 | The command <command> was issued with <parameter count> parameters, expected <parameter count>. |
Explanation: The number of parameters for the command was not the expected number.
User Response: Ensure that the command was issued with the correct parameters.
5004 | The port <port name> is not numeric. |
Explanation: The port is not given in numeric format.
User Response: Specify a valid port number.
5007 | The arguments of -mode <argument> are unknown. Only "foreground" and "background" are supported. |
Explanation: The mode specified is unknown.
User Response: Specify only foreground or background.
5010 | Unknown argument <argument> issued. |
Explanation: An unknown argument was issued.
User Response: Check the spelling of the argument and ensure that it is a valid argument.
5011 | "-login" must be specified. |
Explanation: You must specify login information through -login.
User Response: Supply the -login switch and its arguments.
5012 | Both "-start" and "-stop" are specified. Specify only one. |
Explanation: You can only specify -start or -stop, not both
User Response: Specify either -start or -stop.
5013 | <parameter> is only applicable with "-start" as specified. |
Explanation: The parameter specified is only applicable to -start.
User Response: Specify -mode only with -start.
5014 | You must specify either "-start" or "-stop". |
Explanation: Neither -start nor -stop is specified.
User Response: Specify either -start or -stop.
5015 | There is an error in the given parameters. |
Explanation: There is an error in the given parameters.
User Response: Check the parameters.
5016 | Unable to connect to server. |
Explanation: Unable to connect to OLAP Miner server.
User Response: See the system administrator.
5017 | Starting the mining run... |
Explanation: Starting the mining run.
User Response: No action is required.
5018 | Starting the mining run and waiting for its completion... |
Explanation: Starting the mining run in the foreground.
User Response: No action is required.
5019 | Stopping the mining run... |
Explanation: Interrupting the mining run.
User Response: No action is required.
5020 | An error occurred. |
Explanation: An error occurred.
User Response: No action is required.
5021 | Completed. |
Explanation: The operation completed.
User Response: No action is required.
5023 | Unable to open the output file. |
Explanation: Unable to open the output file.
User Response: Check that the output file has write permission.
5024 | Command <command> was issued more than once. Remove all duplicates of the command. |
Explanation: A duplicate command was issued.
User Response: Remove all duplicates of the command.
8200 | Processing error: <error information>. |
Explanation: An internal processing error from the OLAP Miner server kernel occurred.
User Response: Contact IBM Software Support.
8210 | Wrong version of the parameter file. The version expected was <version>. |
Explanation: The version stored in the parameter file is not supported.
User Response: Contact IBM Software Support.
8211 | This algorithm is not supported <option>. |
Explanation: The OLAP Miner server kernel was called with an invalid option.
User Response: Contact IBM Software Support.
8212 | Command line option help requested. |
Explanation: The OLAP Miner server kernel was called to show the command line options.
User Response: No action is required.
8213 | This option is not supported <option>. |
Explanation: The OLAP Miner server kernel was called with an invalid option.
User Response: Contact IBM Software Support.
8214 | Not enough file space available. Ensure that the temporary file directory contains enough space. |
Explanation: There is not enough temporary file space available.
User Response: Please increase the available file space or select less data to analyze.
8215 | Cannot open the log file<log file>. Check the access rights. |
Explanation: Cannot open the log file.
User Response: Ensure that you have access rights to the specified directory, or if the log file already exists, ensure that it is read-only. Change the read/write permissions accordingly.
8216 | Explanations for this model type are not supported. |
Explanation: An unsupported model option was specified.
User Response: Contact IBM Software Support.
8217 | Not enough memory available. |
Explanation: Not enough memory available.
User Response: Increase the amount of available memory or select less data to analyze.
8218 | The following parameter <parameter> is missing. |
Explanation: A calling parameter is missing from an internal call.
User Response: Contact IBM Software Support.
8219 | These parameters <parameter> are not valid. |
Explanation: One or more unknown parameters were specified internally.
User Response: Contact IBM Software Support.
8220 | Cannot read parameter file <parameter file>. |
Explanation: Cannot read the given parameter file.
User Response: Ensure that you have access rights to the specified directory. Change the read permissions accordingly.
8221 | Cannot read data file<data name>. |
Explanation: Cannot read the given data file.
User Response: Ensure that you have access rights to the specified directory. Change the read permissions accordingly.
8222 | No data file is specified. |
Explanation: No data file is specified.
User Response: Contact IBM Software Support.
8223 | The data file <data file> is empty. |
Explanation: The data file is empty.
User Response: Alter the definition to specify more data. If you cannot resolve the problem, contact IBM Software Support.
8224 | Invalid record length of parameter file. Check the record length. |
Explanation: The parameter file does not have a fixed record length.
User Response: Contact IBM Software Support.
8300 | Cannot initialize conversion for encoding <encoding>. |
Explanation: The specified encoding is not supported by the OLAP Miner server kernel.
User Response: Contact IBM Software Support.
8301 | Cannot parse the XML definition file. The XML might be syntactically incorrect. |
Explanation: The OLAP Miner server kernel cannot parse the XML definition file.
User Response: Ensure that the definition file has not been modified manually. If it was modified, delete the definition, create a new definition, and run it again. If it was not modified, contact IBM Software Support.
8303 | Cannot find the <tag> tag in the XML definition file. |
Explanation: A required tag is missing from the XML definition file.
User Response: Ensure that the definition file has not been modified manually. If it was modified, delete the definition, create a new definition, and run it again. If it was not modified, contact IBM Software Support.
8304 | Cannot find required attribute <attribute> of tag <tag> in the XML definition file. |
Explanation: The specified attribute of the specified tag is missing from the XML definition file.
User Response: Ensure that the definition file has not been modified manually. If it was modified, delete the definition, create a new definition, and run it again. If it was not modified, contact IBM Software Support.
8305 | Number of <tag name> tags <number> does not match the expected number <number> specified in the XML definition file. |
Explanation: The number of the specified tags does not match the number that was provided in the enclosing tag.
User Response: Ensure that the definition file has not been modified manually. If it was modified, delete the definition, create a new definition, and run it again. If it was not modified, contact IBM Software Support.
8306 | Syntax error in the XML definition file. |
Explanation: The syntax of the XML definition file is not correct.
User Response: Ensure that the definition file has not been modified manually. If it was modified, delete the definition, create a new definition, and run it again. If it was not modified, contact IBM Software Support.
8307 | Value <value> of attribute <attribute> in tag <tag> is not allowed in the XML definition file. |
Explanation: An incorrect value was specified for an attribute of a tag in the XML definition file.
User Response: Ensure that the definition file has not been modified manually. If it was modified, delete the definition, create a new definition, and run it again. If it was not modified, contact IBM Software Support.
8308 | A dimension of type <dimension type> was specified in the XML definition file but could not be found in the database outline. |
Explanation: The XML definition file does not contain a dimension of a required type. For example, there might be no Measure dimension specified in the XML file.
User Response: Ensure that the definition file has not been modified manually. If it was modified, delete the definition, create a new definition, and run it again. If it was not modified, contact IBM Software Support.
8309 | More than one dimension of type <dimension type> was specified in the XML definition file. |
Explanation: The XML definition file includes more than one dimension of a type in which only one dimension is allowed. You probably specified more than one Measure dimension.
User Response: Ensure that the definition file has not been modified manually. If it was modified, delete the definition, create a new definition, and run it again. If it was not modified, contact IBM Software Support.
8310 | Incorrect value <value> specified for the version attribute in the XML file. Only XML files for version <version> are allowed. |
Explanation: The version number specified in the XML definition file is not supported.
User Response: Ensure that the definition file has not been modified manually. If it was modified, delete the definition, create a new definition, and run it again. If it was not modified, contact IBM Software Support.
8311 | Necessary arguments for <command> were missing. Correct usage information was written to <file name>. |
Explanation: Command line arguments for the kernel interface were insufficient.
User Response: Contact IBM Software Support.
8312 | Value of attribute <attribute> in tag <tag> in XML definition file is not an integer value. |
Explanation: An integer value was not specified for an attribute in the XML definition file.
User Response: Ensure that the definition file has not been modified manually. If it was modified, delete the definition, create a new definition, and run it again. If it was not modified, contact IBM Software Support.
8313 | Value of attribute <attribute> in tag <tag> in XML definition file is not a double value. |
Explanation: A double value was not specified for an attribute in the XML definition file.
User Response: Ensure that the definition file has not been modified manually. If it was modified, delete the definition, create a new definition, and run it again. If it was not modified, contact IBM Software Support.
8320 | OLAP Error Message <message>. |
Explanation: The OLAP Miner kernel had an internal error communicating with the OLAP server.
User Response: Contact IBM Software Support.
8390 | OLAP API error. Cannot fetch OLAP API handle. |
Explanation: OLAP API error. Cannot fetch OLAP API handle.
User Response: Contact IBM Software Support.
8321 | Cannot establish a connection to the OLAP server <server name> as user <user name>. OLAP server error message: <message>. |
Explanation: OLAP API error. Cannot fetch OLAP API handle.
User Response: Contact IBM Software Support.
8391 | Cannot establish a connection to the OLAP server <server name> as user <user name>. OLAP server error message: <message>. |
Explanation: The OLAP Miner server kernel cannot establish a connection to the specified OLAP server.
User Response: Ensure that the OLAP server is running correctly and check your network connections.
8322 | Cannot select database <database name> in application <application name> on the OLAP server <server name>. OLAP server error message: <message>. |
Explanation: The OLAP Miner server kernel could not select the specified database.
User Response: Ensure that the user from which you started the mining run has access to the database.
8392 | Cannot select database<database name> in application <application name> on the OLAP server <server name>. |
Explanation: The OLAP Miner server kernel could not select the specified database.
User Response: Ensure that the user from which you started the mining run has access to the database.
8323 | Cannot open the outline of database <database name> in application <application name> on the OLAP server <server name>. OLAP server error message <message>. |
Explanation: The OLAP Miner server kernel could not open the outline for the specified database.
User Response: Ensure that the user from which you started the mining run has access to the database.
8393 | Cannot open the outline of database <database name> in application <application name> on the OLAP server<server name>. |
Explanation: The OLAP Miner server kernel could not open the outline for the specified database.
User Response: Ensure that the user from which you started the mining run has access to the database.
8325 | No data from database <database name> of application <application name> is available. OLAP server error message <message>. |
Explanation: No data was returned by the OLAP server to the OLAP Miner server kernel.
User Response: Ensure that the database of the application that you want to mine is loaded with data for the members that you selected for analysis. You can check if data is loaded by issuing a report to the OLAP server or by viewing the database data in a spreadsheet application.
8395 | No data from database <database name> of application <application name> is available. |
Explanation: No data was returned by the OLAP server to the OLAP Miner server kernel.
User Response: Ensure that the database of the application that you want to mine is loaded with data for the members that you selected for analysis. You can check if data is loaded by issuing a report to the OLAP server or by viewing the database data in a spreadsheet application.
8327 | An error occurred while issuing a report. OLAP server error message <message>. |
Explanation: The OLAP server API had an error while the OLAP Miner server kernel was issuing a report.
User Response: If an OLAP server error message is displayed, follow the instructions in the message. If you cannot resolve the problem, contact IBM Software Support.
8397 | An error occurred while issuing a report. |
Explanation: The OLAP server API had an error while the OLAP Miner server kernel was issuing a report.
User Response: If an OLAP server error message is displayed, follow the instructions in the message. If you cannot resolve the problem, contact IBM Software Support.
8328 | Cannot write an OLAP report to file. |
Explanation: The OLAP server could not create a file while running the report that was used to extract the database values.
User Response: Ensure that your disk or partition is full. Create more disk space if necessary.
8329 | Error while fetching data from the OLAP server. OLAP server error message <message>. |
Explanation: The OLAP server could not create a file while running the report that was used to extract the database values.
User Response: Ensure that your disk or partition is full. Create more disk space if necessary.
8399 | Error while fetching data from the OLAP server. |
Explanation: The OLAP server could not create a file while running the report that was used to extract the database values.
User Response: Ensure that your disk or partition is full. Create more disk space if necessary.
8330 | The OLAP Miner server kernel had an interface processing error. |
Explanation: The OLAP Miner server kernel had an internal interface error.
User Response: Contact IBM Software Support.
8331 | The file <file name> could not be created. |
Explanation: A file could not be created. This is possibly because an incorrect path was specified.
User Response: Ensure that your user ID has sufficient privileges to create the file, and that there is sufficient disk space.
8332 | The file <file name> could not be closed. |
Explanation: A file could not be closed.
User Response: Contact IBM Software Support.
8333 | An I/O error occurred for file <file name>. |
Explanation: An I/O error occurred for the specified file.
User Response: Check the status of the file and the system. It is possible that your disk or partition is full.
8334 | File <file name> could not be opened. |
Explanation: The specified file could not be opened.
User Response: Check the status of the file and the system. It is possible that your disk or partition is full.
8335 | Cannot write to cleanup file <file name>. |
Explanation: Cannot write to the cleanup file.
User Response: Ensure that your user ID has sufficient privileges to create the file, and that there is sufficient disk space.
8336 | Cannot open XML definition file <definition name>. |
Explanation: Cannot open the XML definition file.
User Response: Check the status of the file and the system. It is possible that your disk or partition is full.
8337 | Cannot create results file <results file name>. |
Explanation: The specified results file could not be created, possibly because an incorrect path for the results file was specified.
User Response: Ensure that your user ID has sufficient privileges to create the file and that there is sufficient disk space.
8340 | Error while reading outline. |
Explanation: An error occurred while compiling the cube outline information, which is required by the deviation detection algorithm.
User Response: Check the status of the file and the system.
8341 | Multiple instances of <member name> were found in a selection. Ensure that at most one member which is shared is included. |
Explanation: Multiple instances of a member were found. This is due to the XML definition file, which is created by the deviation detection wizard, containing more than one instance of a shared member.
User Response: Ensure that your selections do not contain multiple instances of shared members. Remember that non-additive members are automatically excluded.
8350 | Cannot read result file <results file name> from kernel. |
Explanation: The OLAP Miner server kernel cannot read the results file specified.
User Response: Contact IBM Software Support.
8360 | Cannot create temporary directory <directory name>. |
Explanation: A temporary directory for the temporary files, which is created during the run of the kernel of the OLAP Miner server, could not be created.
User Response: Check the temporary file space and ensure that your user ID has access to that space. If you cannot resolve this problem, contact IBM Software Support.
1051005 | Incorrect password. |
Explanation: The password that the user typed is incorrect.
User Response: Ensure that the password is spelled correctly and that the Caps Lock is not on. If you cannot resolve the problem, contact the system administrator.
1051012 | The user ID does not exist. |
Explanation: The DB2 OLAP server does not recognize the user ID.
User Response: Ensure that the user ID is spelled correctly. If you cannot resolve the problem, contact the system administrator.
1060044 | The DB2 OLAP server API had an error trying to create temporary files. Ensure that your TMP and TEMP environment variables are set up correctly as documented in the DB2 OLAP Server documentation and release notes. |
Explanation: There was an error in creating temporary files.
User Response: Ensure that your TMP and TEMP environment variables are set up correctly as documented in the DB2 OLAP Server documentation and release notes.