Possible Problems
Analytic Services did not recognize the text file.
Possible Solutions
Make sure that the text file is valid.
If more than one record loaded, make sure that ranges in the data source are correctly formatted.
Thursday, November 15, 2007
1003005 Incorrect Number of Column Members in Asymmetric File After recordNumber Records Completed
Possible Problems
Analytic Services encountered either more or fewer columns than it expected while reading the data source.
Possible Solutions
Make sure that the data source is valid.
Are all members that might contain possible file delimiters (such as spaces or commas) surrounded by quotation marks in the data source?
Are all ranges set up correctly in the data source?
Analytic Services encountered either more or fewer columns than it expected while reading the data source.
Possible Solutions
Make sure that the data source is valid.
Are all members that might contain possible file delimiters (such as spaces or commas) surrounded by quotation marks in the data source?
Are all ranges set up correctly in the data source?
1003004 Incorrect Number of Column Members in Symmetric File After recordNumber Records Completed
Possible Problems
Analytic Services encountered either more or fewer columns than it expected while reading the data source.
Possible Solutions
Make sure that the data source is valid.
Are all members that might contain possible file delimiters (such as spaces or commas) surrounded by quotation marks in the data source?
Are all ranges set up correctly in the data source?
Analytic Services encountered either more or fewer columns than it expected while reading the data source.
Possible Solutions
Make sure that the data source is valid.
Are all members that might contain possible file delimiters (such as spaces or commas) surrounded by quotation marks in the data source?
Are all ranges set up correctly in the data source?
1003003 Unable to Continue Data Load After Item itemName, number Records Completed
Possible Problems
Analytic Services aborted the data load. This error message usually occurs after other error messages that describe why the data load failed.
Possible Solutions
Look through the data load error log to see why the data load failed.
If you have no data load error log, set up the load to create an error log and restart the data load.
Check the error messages that preceded this error message to determine what happened.
In the data source, make sure that all data fields are after the member name fields. In the rules file, make sure that you define the fields using dimension names instead of member names.
Analytic Services aborted the data load. This error message usually occurs after other error messages that describe why the data load failed.
Possible Solutions
Look through the data load error log to see why the data load failed.
If you have no data load error log, set up the load to create an error log and restart the data load.
Check the error messages that preceded this error message to determine what happened.
In the data source, make sure that all data fields are after the member name fields. In the rules file, make sure that you define the fields using dimension names instead of member names.
1003001 Duplicate Members From Same Dimension On Data Record, number Records Completed
Possible Problems
Analytic Services encountered more than one member from a dimension in a single record. Analytic Services will not load this record and will skip to the next record.
Possible Solutions
Make sure that the data source is valid.
Does each record contain only one member name for each dimension? For example, in the Time dimension you can have only the January member in a single record, not January and February. If you have columns containing duplicate members in a record, ignore those columns.
Is each member name mapped to the correct dimension? For example, in the Sample Basic database the January member should be mapped to the Time dimension and not to the Market dimension.
Are duplicate member or alias names under different dimensions? Member and alias names must be unique. For example, you cannot have a January member in both the Time dimension and the Market dimension. If you do have members or aliases with the same name in different dimensions, consider adding a prefix or suffix to the members or aliases in one dimension to make them unique.
Are ranges set up correctly?
Are all members that might contain numbers (such as "100") enclosed in quotation marks in the data source?
Are two members from the same dimension on one line in the data source?
If you are using a rules file, make sure that the rules file is valid.
Are extra member names ignored in the rules file?
Do you need to move columns around to ensure that each member is connected to the correct dimension?
Can you validate the rules file?
If you are using ESSCMD, make sure that the ESSCMD syntax is valid.
Check the error log in the ESSCMD script to determine where the duplicate member exists.
Are the parameters enclosed in quotation marks? For example:
IMPORT 2 "ACTUALS" 4 "Y" 2 "ACTUALS" "Y";
Are the parameters correct?
Do the files you are loading exist in the correct locations?
Can you run the data load using Administration Services?
If you are using Integration Services, try the following steps:
If the duplicate member is a shared member, make sure that it is tagged as a shared member.
If you have members with the same names in different dimensions, be sure to add prefixes or suffixes to the member names.
Map all members to the correct dimension.
Make sure that you are using the correct Intersolv drivers.
Launch Analytic Services Integration Services using a non-default value for the -B parameter.
In Hyperion OLAP Builder, select the Delete All Members First option.
Analytic Services encountered more than one member from a dimension in a single record. Analytic Services will not load this record and will skip to the next record.
Possible Solutions
Make sure that the data source is valid.
Does each record contain only one member name for each dimension? For example, in the Time dimension you can have only the January member in a single record, not January and February. If you have columns containing duplicate members in a record, ignore those columns.
Is each member name mapped to the correct dimension? For example, in the Sample Basic database the January member should be mapped to the Time dimension and not to the Market dimension.
Are duplicate member or alias names under different dimensions? Member and alias names must be unique. For example, you cannot have a January member in both the Time dimension and the Market dimension. If you do have members or aliases with the same name in different dimensions, consider adding a prefix or suffix to the members or aliases in one dimension to make them unique.
Are ranges set up correctly?
Are all members that might contain numbers (such as "100") enclosed in quotation marks in the data source?
Are two members from the same dimension on one line in the data source?
If you are using a rules file, make sure that the rules file is valid.
Are extra member names ignored in the rules file?
Do you need to move columns around to ensure that each member is connected to the correct dimension?
Can you validate the rules file?
If you are using ESSCMD, make sure that the ESSCMD syntax is valid.
Check the error log in the ESSCMD script to determine where the duplicate member exists.
Are the parameters enclosed in quotation marks? For example:
IMPORT 2 "ACTUALS" 4 "Y" 2 "ACTUALS" "Y";
Are the parameters correct?
Do the files you are loading exist in the correct locations?
Can you run the data load using Administration Services?
If you are using Integration Services, try the following steps:
If the duplicate member is a shared member, make sure that it is tagged as a shared member.
If you have members with the same names in different dimensions, be sure to add prefixes or suffixes to the member names.
Map all members to the correct dimension.
Make sure that you are using the correct Intersolv drivers.
Launch Analytic Services Integration Services using a non-default value for the -B parameter.
In Hyperion OLAP Builder, select the Delete All Members First option.
1003000 Unknown Item itemName in Data Load, number Records Completed
Possible Problems
Analytic Services encountered a field in the data source that it did not recognize.
Possible Solutions
Examine the data load log for any other messages that may help to identify the problem.
Make sure that the data source is valid. If no records loaded, either the first record is invalid or the entire data source is invalid.
Is the data source corrupt?
Is the data source in the correct location?
Is the data source correctly formatted?
Make sure that the record that caused the data load to fail is valid.
Is a member from each dimension specified in the data source or the rules file?
Is each member name in the record valid?
Is there more than one numeric data field in the record?
Did you try removing the record that caused the data load to fail and running the data load again?
If you are using a rules file, make sure that the rules file is valid.
Is the rules file in the correct location?
Is the rules file set up correctly?
Can you validate the rules file?
If you are using ESSCMD, make sure that the ESSCMD syntax is valid.
Check the error log in the ESSCMD script to determine where the unknown item exists.
Are the parameters enclosed in quotation marks? For example:
IMPORT 2 "ACTUALS" 4 "Y" 2 "ACTUALS" "Y";
Are the parameters correct?
Do the files you are loading exist in the correct locations?
Can you run the data load using Administration Services?
Analytic Services encountered a field in the data source that it did not recognize.
Possible Solutions
Examine the data load log for any other messages that may help to identify the problem.
Make sure that the data source is valid. If no records loaded, either the first record is invalid or the entire data source is invalid.
Is the data source corrupt?
Is the data source in the correct location?
Is the data source correctly formatted?
Make sure that the record that caused the data load to fail is valid.
Is a member from each dimension specified in the data source or the rules file?
Is each member name in the record valid?
Is there more than one numeric data field in the record?
Did you try removing the record that caused the data load to fail and running the data load again?
If you are using a rules file, make sure that the rules file is valid.
Is the rules file in the correct location?
Is the rules file set up correctly?
Can you validate the rules file?
If you are using ESSCMD, make sure that the ESSCMD syntax is valid.
Check the error log in the ESSCMD script to determine where the unknown item exists.
Are the parameters enclosed in quotation marks? For example:
IMPORT 2 "ACTUALS" 4 "Y" 2 "ACTUALS" "Y";
Are the parameters correct?
Do the files you are loading exist in the correct locations?
Can you run the data load using Administration Services?
Friday, November 9, 2007
Excel Addin - When in doubt, try this:
When utilizing the Excel Addin, and something all of a sudden looks weird (meaning your report has never acted in this manner) the best fix is to close down all excel applications and try again. Most of the time, the issue resides with a user having multiple instances of microsoft excel open. You can have multiple workbooks with multiple tabs open, but once you have multiple instances of excel, funky things can occur. Close down all excel instances and start over, this should fix your issue, if it does not then there is a potential that something is wrong with your report or application. So try this before you contact your admin team.
Wednesday, November 7, 2007
1006015 Not Enough Memory to Allocate the Data Buffer Cache. operation aborted
Possible Problems
Analytic Services cannot complete the listed operation because there was not enough memory.
Possible Solutions
Try any of the following to fix the problem. Once you fix the problem, check to see if the database is corrupt.
Check the physical memory on the server computer. In a Windows environment, 64 MB is the suggested minimum for one database. In a UNIX environment, 128 MB is the suggested minimum for one database. If the error keeps occurring, add more memory to the server computer.
If you are on a UNIX computer, check the user limit profile.
Check the block size of the database. If necessary, reduce the block size.
Check the data cache setting. If necessary, increase the data cache size.
Restart Analytic Server.
Restart the server computer.
Analytic Services cannot complete the listed operation because there was not enough memory.
Possible Solutions
Try any of the following to fix the problem. Once you fix the problem, check to see if the database is corrupt.
Check the physical memory on the server computer. In a Windows environment, 64 MB is the suggested minimum for one database. In a UNIX environment, 128 MB is the suggested minimum for one database. If the error keeps occurring, add more memory to the server computer.
If you are on a UNIX computer, check the user limit profile.
Check the block size of the database. If necessary, reduce the block size.
Check the data cache setting. If necessary, increase the data cache size.
Restart Analytic Server.
Restart the server computer.
1006010 Invalid block header: Block's numbers do not match
Possible Problems
Analytic Services cannot match the block header to the numbers of the block. The database is probably corrupt. The corruption could have been caused by a single anomalous event, such as a power failure, that caused Analytic Services to shut down incorrectly.
Possible Solutions
To fix the database:
Stop Analytic Server.
Delete the $ARBORPATH/app/applicationName/databaseName/ databaseName.ind file.
Start Analytic Server.
Start the application.
Check to see if the database is corrupt.
Analytic Services cannot match the block header to the numbers of the block. The database is probably corrupt. The corruption could have been caused by a single anomalous event, such as a power failure, that caused Analytic Services to shut down incorrectly.
Possible Solutions
To fix the database:
Stop Analytic Server.
Delete the $ARBORPATH/app/applicationName/databaseName/ databaseName.ind file.
Start Analytic Server.
Start the application.
Check to see if the database is corrupt.
1006006 Failed to bring block into the memory. Data cache is too small. Please increase the data cache size.
Possible Problems
Analytic Services cannot store the block in its memory.
Possible Solutions
Decrease the block size by changing the dense/sparse configuration.
Increase the data cache size to hold at least 100 blocks.
Increase the memory of the server computer.
Check to see if the database is corrupt.
Analytic Services cannot store the block in its memory.
Possible Solutions
Decrease the block size by changing the dense/sparse configuration.
Increase the data cache size to hold at least 100 blocks.
Increase the memory of the server computer.
Check to see if the database is corrupt.
1006004 Unable to Read Information From Page File
Possible Problems
Analytic Services cannot read the page file.
Possible Solutions
Is there a hardware problem? Check your Windows event log. If you do not know how to do this, consult the Windows documentation.
Are the index and page file corrupt? Check them by issuing the VALIDATE command in ESSCMD. If the index and page files are corrupt:
Delete the temporary files. The temporary files include:
$ARBORPATH/app/applicationName/databaseName/databaseName.inn
$ARBORPATH/app/applicationName/databaseName/essxxxxx.inn
$ARBORPATH/app/applicationName/databaseName/essxxxxx.pan
$ARBORPATH/app/applicationName/databaseName/databaseName.otn
$ARBORPATH/app/applicationName/databaseName/databaseName.esn
$ARBORPATH/app/applicationName/databaseName/databaseName.tcu
Restart Analytic Server.
Check to see if the database is corrupt.
Analytic Services cannot read the page file.
Possible Solutions
Is there a hardware problem? Check your Windows event log. If you do not know how to do this, consult the Windows documentation.
Are the index and page file corrupt? Check them by issuing the VALIDATE command in ESSCMD. If the index and page files are corrupt:
Delete the temporary files. The temporary files include:
$ARBORPATH/app/applicationName/databaseName/databaseName.inn
$ARBORPATH/app/applicationName/databaseName/essxxxxx.inn
$ARBORPATH/app/applicationName/databaseName/essxxxxx.pan
$ARBORPATH/app/applicationName/databaseName/databaseName.otn
$ARBORPATH/app/applicationName/databaseName/databaseName.esn
$ARBORPATH/app/applicationName/databaseName/databaseName.tcu
Restart Analytic Server.
Check to see if the database is corrupt.
1006002 Unable to Store Information In Page File
Possible Problems
Analytic Services did not have enough disk space to store the data in a page file.
Possible Solutions
If possible, add more disk space. If you cannot add more disk space, consider spanning disk volumes.
If an operation, such as a calculation, did not complete, perform recovery procedures.
Check to see if the database is corrupt.
Analytic Services did not have enough disk space to store the data in a page file.
Possible Solutions
If possible, add more disk space. If you cannot add more disk space, consider spanning disk volumes.
If an operation, such as a calculation, did not complete, perform recovery procedures.
Check to see if the database is corrupt.
Tuesday, November 6, 2007
1012052 Unable to unfix blocks after calculation encounters an error
Possible Problems
The data blocks that were changed by a calculation were left in an inconsistent state.
Possible Solutions
Stop and restart the database or contact Hyperion Technical Support. Analytic Services either reverted all values to their previous state or retained any values calculated before the error. How Analytic Services handles the cancellation depends on the Analytic Services kernel isolation level settings.
The data blocks that were changed by a calculation were left in an inconsistent state.
Possible Solutions
Stop and restart the database or contact Hyperion Technical Support. Analytic Services either reverted all values to their previous state or retained any values calculated before the error. How Analytic Services handles the cancellation depends on the Analytic Services kernel isolation level settings.
1012051 Batch calc error, FIX statement cannot contain Dynamic Calc member from dimension dimensionName
Possible Problems
Analytic Services tried to FIX on a Dynamic Calc member.
Possible Solutions
Make sure that you are not fixing on a member that is tagged as Dynamic Calc. Dynamic Calc members do not store data. They are calculated at query time if a query requests the value of the member. To FIX on the listed member, change the member from Dynamic Calc to store.
Analytic Services tried to FIX on a Dynamic Calc member.
Possible Solutions
Make sure that you are not fixing on a member that is tagged as Dynamic Calc. Dynamic Calc members do not store data. They are calculated at query time if a query requests the value of the member. To FIX on the listed member, change the member from Dynamic Calc to store.
1012050 Cannot DATACOPY on Attribute dimension member memberName
Possible Problems
Analytic Services tried to copy data into the listed attribute dimension using the DATACOPY command.
Possible Solutions
Make sure that you are not using the DATACOPY command to copy data into an attribute dimension. Attribute dimensions do not store data. They are calculated at query time if a query requests the value of the member.
Analytic Services tried to copy data into the listed attribute dimension using the DATACOPY command.
Possible Solutions
Make sure that you are not using the DATACOPY command to copy data into an attribute dimension. Attribute dimensions do not store data. They are calculated at query time if a query requests the value of the member.
1012049 Cannot clear data from Attribute dimension member memberName
Possible Problems
Analytic Services tried to clear data from the listed attribute dimension.
Possible Solutions
Attribute dimensions do not store data. They are calculated at query time if a query requests the value of the member. You cannot clear data from an attribute dimension or any member of an attribute dimension.
Analytic Services tried to clear data from the listed attribute dimension.
Possible Solutions
Attribute dimensions do not store data. They are calculated at query time if a query requests the value of the member. You cannot clear data from an attribute dimension or any member of an attribute dimension.
1012048 Calc Dim on Attribute Dimension attributeDimensionName is not supported
Possible Problems
Analytic Services tried to calculate the listed attribute dimension using the CALC DIM command.
Possible Solutions
Make sure that you are not using the CALC DIM command to calculate an attribute dimension. Attribute dimensions do not store data. They are calculated at query time if a query requests the value of the member.
Analytic Services tried to calculate the listed attribute dimension using the CALC DIM command.
Possible Solutions
Make sure that you are not using the CALC DIM command to calculate an attribute dimension. Attribute dimensions do not store data. They are calculated at query time if a query requests the value of the member.
1012047 Aggregating on Attribute Dimension attributeDimensionName is currently not supported
Possible Problems
Analytic Services tried to calculate the listed attribute dimension using the AGG command.
Possible Solutions
Make sure that you are not using the AGG command to calculate an attribute dimension. Attribute dimensions do not store data. They are calculated at query time if a query requests the value of the member.
Analytic Services tried to calculate the listed attribute dimension using the AGG command.
Possible Solutions
Make sure that you are not using the AGG command to calculate an attribute dimension. Attribute dimensions do not store data. They are calculated at query time if a query requests the value of the member.
Monday, November 5, 2007
1012043 Calculation is not allowed for virtual member memberName in the Calc script
Possible Problems
The calculation script tried to set the value of a Dynamic Calc member or request the calculation of a Dynamic Calc member.
Possible Solutions
Dynamic Calc members are calculated at query time if a query requests the value of the member. They cannot be calculated through calculation scripts. Make sure that the Dynamic Calc member is not on the left side of the equation; for example, if Qtr1 is Dynamic Calc, the following equation is incorrect:
Qtr1 = Jan + Feb + Mar;
If Qtr1 is Dynamic Calc, the following equation is also incorrect:
vbb Qtr1;
The following equation is correct, if Year is not Dynamic Calc, but Qtr1 and Qtr2 are Dynamic Calc:
Year = Qtr1 + Qtr2;
The calculation script tried to set the value of a Dynamic Calc member or request the calculation of a Dynamic Calc member.
Possible Solutions
Dynamic Calc members are calculated at query time if a query requests the value of the member. They cannot be calculated through calculation scripts. Make sure that the Dynamic Calc member is not on the left side of the equation; for example, if Qtr1 is Dynamic Calc, the following equation is incorrect:
Qtr1 = Jan + Feb + Mar;
If Qtr1 is Dynamic Calc, the following equation is also incorrect:
vbb Qtr1;
The following equation is correct, if Year is not Dynamic Calc, but Qtr1 and Qtr2 are Dynamic Calc:
Year = Qtr1 + Qtr2;
1012042 Substitution variable substitionVariableName doesn't exist
Possible Problems
The calculation script cannot find the listed substitution variable.
Possible Solutions
Make sure that you created the substitution variable correctly.
Make sure that the substitution variable was created at the correct level.
Substitution variables created at the database level are available to all calculation scripts within that database.
Substitution variables created at the application level are available to all calculation scripts within that application.
Substitution variables created at the server level are available to all calculation scripts on the Analytic Server.
The calculation script cannot find the listed substitution variable.
Possible Solutions
Make sure that you created the substitution variable correctly.
Make sure that the substitution variable was created at the correct level.
Substitution variables created at the database level are available to all calculation scripts within that database.
Substitution variables created at the application level are available to all calculation scripts within that application.
Substitution variables created at the server level are available to all calculation scripts on the Analytic Server.
1012041 memberName is not a valid currency type member
Possible Problems
Analytic Services tried to specify the currency type using a member that was not part of the dimension tagged as CurType in the Analytic Services database.
Possible Solutions
Make sure you are using the CCONV function correctly and that you have set up the currency database correctly.
Make sure that the listed member is defined as the currency type member.
Analytic Services tried to specify the currency type using a member that was not part of the dimension tagged as CurType in the Analytic Services database.
Possible Solutions
Make sure you are using the CCONV function correctly and that you have set up the currency database correctly.
Make sure that the listed member is defined as the currency type member.
1012040 Too many initial constants assigned to array variable arrayVariableName
Possible Problems
Analytic Services tried to assign more values to the array than there are members in the dimension with which it is associated.
Possible Solutions
Make sure that you are using the ARRAY command correctly.
Make sure that you are assigning the values to the correct dimension.
Analytic Services tried to assign more values to the array than there are members in the dimension with which it is associated.
Possible Solutions
Make sure that you are using the ARRAY command correctly.
Make sure that you are assigning the values to the correct dimension.
1012039 The constant constantName assigned to array variable arrayVariableName is not a number
Possible Problems
Analytic Services tried to assign a value that was not a number to the listed array variable. The listed array variable can accept only numeric values.
Possible Solutions
Make sure that you are assigning the array variable correctly.
Analytic Services tried to assign a value that was not a number to the listed array variable. The listed array variable can accept only numeric values.
Possible Solutions
Make sure that you are assigning the array variable correctly.
1012038 The constant constantName assigned to variable variableName is not a number
Possible Problems
Analytic Services tried to assign a value that was not a number to the listed variable. The listed variable can accept only numeric values.
Possible Solutions
Make sure that you are declaring the variable correctly.
Analytic Services tried to assign a value that was not a number to the listed variable. The listed variable can accept only numeric values.
Possible Solutions
Make sure that you are declaring the variable correctly.
Friday, November 2, 2007
1012037 Custom calculation is not allowed for kindOfShare share member sharedMemberName
Possible Problems
Analytic Services tried to calculate a formula on a shared member.
Possible Solutions
Because shared members do not store data, you cannot attach formulas to them.
Make sure that the listed member is not shared, either because the storage property of the member is explicitly tagged as shared or because the member is implicitly shared.
Analytic Services tried to calculate a formula on a shared member.
Possible Solutions
Because shared members do not store data, you cannot attach formulas to them.
Make sure that the listed member is not shared, either because the storage property of the member is explicitly tagged as shared or because the member is implicitly shared.
1012036 Calc Script block command blockCommandName does not end with blockEndCommandName
Possible Problems
Analytic Services encountered a block command that was not closed.
Possible Solutions
Make sure that each FIX command is closed by an ENDFIX command.
Make sure that each LOOP command is closed by an ENDLOOP command
Analytic Services encountered a block command that was not closed.
Possible Solutions
Make sure that each FIX command is closed by an ENDFIX command.
Make sure that each LOOP command is closed by an ENDLOOP command
1012035 Variable variableName must be of VAR type
Possible Problems
The variable listed must be of VAR type instead of ARRAY type.
Possible Solutions
Make sure that you are declaring the variable correctly.
The variable listed must be of VAR type instead of ARRAY type.
Possible Solutions
Make sure that you are declaring the variable correctly.
1012034 Variable variableName not declared
Possible Problems
The variable used in the calculation script is not declared.
Possible Solutions
Make sure that you are declaring the variable correctly before you use it.
The variable used in the calculation script is not declared.
Possible Solutions
Make sure that you are declaring the variable correctly before you use it.
1012033 Currency Conversion is not available with this server, calc command commandName is not supported
This command is available only if your company has purchased the Currency Conversion option for Analytic Services.
1012032 When CURPARTITION is tagged, DATACOPY command command can only be used to copy a whole Currency Partition
Possible Problems
Analytic Services tried to use the FIX command while using DATACOPY to copy a currency partition and this is not permitted.
Possible Solutions
Make sure that you are not using a FIX command in the DATACOPY command if you are copying a currency partition. Use the DATACOPY command to copy the entire currency partition.
Analytic Services tried to use the FIX command while using DATACOPY to copy a currency partition and this is not permitted.
Possible Solutions
Make sure that you are not using a FIX command in the DATACOPY command if you are copying a currency partition. Use the DATACOPY command to copy the entire currency partition.
1012031 DATACOPY command command is conflict with Range Fix
Possible Problems
Analytic Services tried to copy a range of members that was outside of the range you fixed on.
Possible Solutions
Make the DATACOPY range and FIX range compatible, either by making the ranges match or by making the DATACOPY range a subset of the FIX range.
Analytic Services tried to copy a range of members that was outside of the range you fixed on.
Possible Solutions
Make the DATACOPY range and FIX range compatible, either by making the ranges match or by making the DATACOPY range a subset of the FIX range.
1012030 DATACOPY command command cannot copy data to itself
Possible Problems
The DATACOPY command copies a range of members from a source range to a target range. The DATACOPY command cannot copy a range of members from a source range back onto the source range.
Possible Solutions
Make sure that the DATACOPY command is set to copy the correct range.
Compare the source and target ranges to make sure that the DATACOPY command is not copying the data back onto the source range.
The DATACOPY command copies a range of members from a source range to a target range. The DATACOPY command cannot copy a range of members from a source range back onto the source range.
Possible Solutions
Make sure that the DATACOPY command is set to copy the correct range.
Compare the source and target ranges to make sure that the DATACOPY command is not copying the data back onto the source range.
Subscribe to:
Posts (Atom)