Nov
5
It may happen that, during an HFM copy application process (through the appropriate util “HFMCopyApplication.exe”), the application quits unexpectedly or that, on certain table, some errors show up.
Unfortunately the utility supplied with the version 9.3.1 does not write a log while it is running the copy, but allows you to view and possibly save the log only after the operation has ended (whether it is successful or not ).
In this case advice is to check the instances of DB and the destination and origin: just today I found that although in theory one should only read from the source data, a tablespace has brought out the strange behavior mentioned above.
P.S.
about the logfiles: Oracle Hyperion official documentation says that the logs are saved in “% HYPERION_HOME% \ logs \ hfm” folder by default. If the HYPERION_HOME%% environment variable is not set, then the log will be created in “C: \ Documents and Settings \% username% \ Local Settings \ Temp” ”
Unfortunately this is not always true, as indeed happened in my case where there was no trace of the log into any of the above two paths. It is likely that this feature has been implemented starting from rel. 11