Version 1.

4 7/28/2011 Page 1 of 20


Financial Management Application Copy Utility

This document will cover the most commonly asked Financial Management copy application utility
questions and issues as well as covering the utilitys basic usage and functionality. All the utility
screens will be shown and all options will be explained for the most current utility version, which as of
this writing comes from the 11.1.1.3.500 and 11.1.2.1.101.

Known Bugs ...............................................................................................................................................................2
Common Questions, Issues and Recommendations ...................................................................................................2
Preparing to Run the Utility .......................................................................................................................................5
Running the Utility .....................................................................................................................................................5
Welcome screen ..................................................................................................................................................5
Source UDL selection .........................................................................................................................................6
Source Application selection ..............................................................................................................................6
Target UDL file selection ...................................................................................................................................6
Select Destination application ............................................................................................................................7
Options ...............................................................................................................................................................8
Advanced Options ..............................................................................................................................................9
Data Options .....................................................................................................................................................10
Database Options ..............................................................................................................................................11
Confirmation screen .........................................................................................................................................12
Copying ............................................................................................................................................................13
Task Entry Log Screen .....................................................................................................................................13
Completed Tasks ..............................................................................................................................................13
Failed Tasks ......................................................................................................................................................14
Restart Task screen ...........................................................................................................................................14
Finished ............................................................................................................................................................15
Command Line Interpreter .......................................................................................................................................16
Log review ................................................................................................................................................................18




Version 1.4 7/28/2011 Page 2 of 20


Known Bugs

When the Source is MS SQL Server, releases 9.3.1 through 11.1.1.1.0 of the copy utility may
incorrectly create the indexes on Target tables. There is an Index Update utility provided in
Oracle patch 8523209 (Oracles Hyperion Financial Management System 9 Release
11.1.1.3.09) that can identify and correct the indexes on affected tables. Instructions for using
the Index Update utility are included in this download.

When running against an Oracle database, releases 11.1.1.3.000 through 11.1.1.3.500 and
11.1.2.0.00 through 11.1.2.1.101 will improperly drop sequences in the Target environment if
the application being copied has an application name that is a substring of other existing
applications. For example, if the Target environment has an application named Comma11 and
the copied application name is Comma then the sequences on Comma11 will be dropped and
issues will arise in this application, the new Comma application will have its sequences and will
function properly. If the Target application name is changed to Comma2 then this issue is not
seen. Once the sequences are dropped, contact Support for assistance in recreating the
Sequences, reference unpublished bug 12698058. Until a PSE is released it is recommend that
care be taken with application names so that this issue is not encountered.

Copy utilities from 11.1.2.0.000 through 11.1.2.1.101 should only be run from an HFM
application server. This is being addressed in unpublished bug 10415221 and should be
corrected in the upcoming 11.1.2.2.000 release.

Common Questions, Issues and Recommendations

The copy utility is useful when you need to copy a single application either in its entirety or just a portion
between environments such as between Production and Test, QA or Development. The primary use of
these copied applications is to allow the Financial Management administrator to thoroughly test new
application changes in a controlled environment before applying changes to Production. The Source
environment refers to the application you want to copy and the Target environment refers to the
location you are copying the application to. The Source and Target environments may or may not refer
to the same physical RDBMS environment. The following bullet points cover the most common
questions and issues generated about using this utility as well as a few best practice recommendations:

The copy utility allows for application renaming so the copied application can have the same or
different name in the Target environment. When the Target and Source environment are the
same then you must enter a new name for the Target application.

The copy utility from a newer Financial Management release is backwards compatible to as far
back as version 9.2. It is typically recommended to use the most current commercial release of
the utility to take advantage of fixes and new features.

When running against an Oracle database using the 64-bit copy utility from releases
11.1.1.3.500+ and 11.1.2.1+, the Oracle Provider for OLE DB must be the same major version
as the database. If running against a 10.2.0.4 or 11R1 Oracle database then the Oracle
Provider for OLE DB must be patched to 10.2.0.4.21+ or 11.1.0.7.33+. Note that the 11.2.0.1
Oracle Provider for OLE DB does not require patching. This requirement is documented in the
HFM Readme for these releases but is easily over looked when a newer copy utility version is
used in an older release environment that may not be patched.

Except for releases 11.1.2.0.000 through 11.1.2.1.101, the copy utility can be run on any server
or workstation that has a properly configured UDL file(s) with access to Source and Target
databases. Releases 11.1.2.0.000 through 11.1.2.1.101 should only be run from an HFM

Version 1.4 7/28/2011 Page 3 of 20


application server.

The utility will work with an encrypted UDL.

All 11.1.2 releases require you to manually create a UDL file. Prior to this release, UDL files
were created as part of the HFM application server configuration process however starting with
11.1.2 the connection details are stored in HIT registry and no UDL file is created during
application server configuration.

The utility can copy between RDBMS versions and vendors: Oracle, MS SQL and DB2.

The utility can be used to copy an older versioned application into a newer versioned
environment to allow the Schema Upgrade utility to upgrade the newly copied application:
o Example: Copying an application from an older release in Production to a newer release
in a Test environment. The application can be refreshed from production into test and
schema upgrade utility run again.

For System 9 and 11 releases, the copied application must be registered with Shared Services
in the Target Environment after the application has been successfully copied. A Security extract
must be made in the Source environment and loaded in the newly copied application before
user provisioning is properly setup. For cases where the Target application is being replaced,
meaning the copied application uses the same name of an existing application in the Target
environment, it is not required to re-register the application but security should still be loaded to
ensure user provisioning is properly updated. If Native users or groups are used for provisioning
then these must be created in the Target environment if they do not already exist before loading
security. The CSSImportExportUtility can be used to ensure these are created as they exist in
the Source environment - see the Shared Service Security Guide for details on using the
CSSImportExportUtility utility.

A new feature in the 11 releases is the inclusion of a command line interpreter called
Hfmcopyappcmd.exe or Hfmcopyappcmd_x64.exe. The command line interpreter allows for
scheduling of copy jobs using the operating system or third party scheduling utilities.

Task Flows are not copied along with the Financial Management application; Task Flows are
stored in the Shared Services database. Use Life cycle management introduced in 11.1.1.0 to
export and import Task Flows between environments. Task Flows must be manually created in
earlier releases.

Starting with 11.1.1.3.050, the utility can copy EPM Architect enabled applications. The Target
application will be converted to a Classic application. If the Target application already exists
then it must be deleted prior to copying. After the copy is complete, the application can be
upgraded again to re-enable EPM Architect or it can be left as a Classic application.

Do not copy over an existing application when the Target application is currently running.
o Example: Copy an application from Production to Test and replacing an application in
Test while the application is open. This will cause the application tables to be out of
sync with the metadata and data loaded in memory in the HsvDataSource process
resulting in any number of application related errors. When this happens the copied
application in the Target environment must be shut down and the copy run again.

It is not required that you delete a Classic application from the UI in the Target environment
before running the utility to copy over an existing application. The utility provides options to
drop all tables related to an application being copied in the Target environment. However,
deleting an application from the UI in the Target environment is an effective way to ensure the

Version 1.4 7/28/2011 Page 4 of 20


application is shutdown in the Target environment while the application is being copied.

The log file created during the application copy is now located in the
%HYPERION_HOME%\logs\hfm folder.

Do not copy an application when users are active in the Source application. The utility copies a
number of tables at a time, 1 table for every thread configured in the Advanced Options tab.
When users are active in an application, updates are made to the application tables; therefore, if
active users are updating tables in the Source application while the copy is running, then this
will result in the copied application having tables that are not in a consistent state.

Do not attempt to copy between environments separated by a WAN. The utility processes
multiple tables at a time and tables are copied row by row. This generates a great deal of
network traffic and the added latency of a WAN often makes the entire copy process take an
excessively long time. Use the RDBMS vendors recommended backup and restore utilities to
restore into a temporary database or schema and then run the utility to copy an application into
the desired Target environment.

No assertions are made about the utilitys performance. Due to the nature of the utility copying
many tables, typically with millions of rows per table, high database loads are expected on
Source and Target environments and performance will be directly related to the infrastructures
ability to handle the load.

The copy utility is not meant to replace the RDBMS vendor backup and restore utilities to
recover from catastrophic failures. The RDBMS backup and restore software will always be
faster and more secure and should be used whenever possible.

The copy utility will cause a great deal of transaction log / redo log activity. Each row copied will
generate a transaction record. For MS SQL databases, the DBA can change the Target
database recovery model to Simple and create a full database backup after the copy is
complete. Another consideration for MS SQL is to shrink the transaction logs after the copy is
complete. For Oracle, if the instance is configured for Archiving, the DBA should consider the
impact on the redo logs and the archive process. The amount of redo generated by the copy
will impact the Mean Time To Recover.



Version 1.4 7/28/2011 Page 5 of 20


Preparing to Run the Utility

The Financial Management Application Copy Utility is a standalone utility, except for releases
11.1.2.0.00 through 11.1.2.1.101, which can be run from any machine that has a valid UDL file(s) to
access the Source and Target RDBMS environments. The database user configured in the UDL files
must have the same database privileges as documented in the Financial Management installation
guide. If the Source and Target environments are the same database then the amount of network
traffic generated will be much lower than when the Source and Target databases are separate*. The
location of the machine running the copy utility should be as close as possible to the Source and Target
RDBMS environments. The added latency introduced when running over a WAN or over multiple
network hoops will have a negative impact of the overall time to complete the copy. Also, the number
of CPUs on the machine running the utility will have a direct impact on the copy process. The utility will
spawn a number of worker threads, one thread copies one table. This value can be increased or
decreased from the advanced options tab.

*New to the 11 releases is the ability to perform direct database copies. If the Target application is in
the same database for the same schema (user), then the data will not be brought out prior to copying to
the new tables. Instead, a database INSERT INTO SELECT FROM will be executed. This will
increase performance for the application copy.

The log file created during the application copy is now located in the %HYPERION_HOME%\logs\hfm
folder. If %HYPERION_HOME% environment variable is not set then the log will be created in
%Temp%.

Running the Utility

The Financial Management Application Copy Utility is installed on the Financial Management
Application server by default. In releases 11.1.2+ the location is %EPM_ORACLE_HOME%\Products\
FinancialManagement \Utilities. For all prior 11.1.1+ releases the location is
%Hyperion_Home%\FinancialManagement\Server. On 32-bit installations, the file is named
HfmCopyApplication.exe and on 64-bit the file is named HfmCopyApplication_x64.exe. The following
shows the screens presented when this utility is run:
Welcome screen


Version 1.4 7/28/2011 Page 6 of 20


Source UDL selection


Select the >> button to navigate to the proper UDL file for the Source environment.

Source Application selection


The list of applications is retrieved from the Hsx_DataSources table in the Source environment.

Target UDL file selection



Version 1.4 7/28/2011 Page 7 of 20


Select the >> button to browser to the UDL file configured to access the Target environment. This UDL
file can be the same as the Source UDL or it can point to a different UDL.

Select Destination application


For the Target destination, the utility will read the Windows registry and populate the drop down with
the names of applications that were previously copied. If this is the first time running the utility then it
will show only the Source application name. The registry key read is user specific,
HKEY_CURRENT_USER\Software\Hyperion Solutions\HfmCopyApplication\Settings or
HKEY_CURRENT_USER\Software\Hyperion Solutions\HfmCopyApplication_x64\Settings, and the
values read to populate the drop down are DestApp00 DestAppXX. You may select an existing
application name from the drop down or manually type a new application name. The Target application
name must adhere to the naming convention as covered in the Financial Management Administrators
guide.

Version 1.4 7/28/2011 Page 8 of 20


Options


Copy Application Data: This box is typically checked to generate an identical copy of the Source
application. Clear this check box to create a shell application. Application metadata tables will be
copied and populated while data tables are only created but are not populated.

Copy Audit data: This box can be cleared if Task and Data audit trails are not required to be
maintained in the Target environment. Often the Task and Data audit tables are very large tables and
should not be copied unless required.

Copy Cluster Settings: This check box should normally not be checked. This will copy the Financial
Management Cluster related tables only if the Source environment has a cluster defined. Copying this
information between Production and Test can cause cross over connections where Test environments
connecting to a cluster actually connect to the Production application servers.

Overwrite existing Application (if it exists): In general always select Drop All Application tables prior
to copy. It is possible for the Target application to have Scenario and Year data populated that the
Source application does not have and not dropping these tables would introduce variances in the newly
copied application compared to the Source application. The circumstances in which Only drop tables
that are being copied would be a valid option would be rare.


*Note that the HFM_Errorlog table is not copied by this utility regardless of the options selected.

Version 1.4 7/28/2011 Page 9 of 20


Advanced Options

The Advanced Options dialog is broken up in to three pages. It would typically not be required to make
any changes to any selections on these tabs unless directed by Support to address a specific situation.



Use Client-Side Cursors: This option will bring all row data to the client from the RDBMS server. The
server will cache no data. All caching will occur on the client, meaning the client will require more
memory and the server will require less memory. Reduce the number of threads to 2 x Number of
CPUs if this option is selected. Use this option if Server-Side cursors fail.

Use Server-Side Cursors: This option will run faster and require less memory on the client. The data
set will be cached on the server (requiring more resources on the server). This is the default option.

SQL Binding: This option specifies how the SQL statement is executed on the server. The default is
to use SQL binding. Change this option to not use SQL binding if excessive errors occur or Multi-Step
OLE DB Errors occur. It is best to leave this option on and then restart any failed processes with this
option disabled (if the error is a Multi-Step error).

Thread Usage: This option allows the user to specify the number of processing threads. The
minimum is one and the maximum is twenty. This option basically controls how many current tables
are being processed and has an impact on the amount of network traffic and the load placed on Source
and Target RDBMS servers.

Log SQL Errors: This option specifies whether to output every SQL error to the log file. Please note,
some errors are expected. You may see errors for the attempt to drop tables that do not exist or the
defaulting of sequence values. This is acceptable. Do not use the presence of SQL errors in the log to
gauge whether the processing succeeded. This option is not checked by default to reduce confusion
when reviewing the log.

Number of Task retries: This option specifies the number of times a query should be re-executed in
the event of a failure. This is to resolve possible deadlock issues when inserting data in the database.


Version 1.4 7/28/2011 Page 10 of 20


Data Options

The Data Options tab allows you to control what data is actually copied. The Copy Application Data
check box must be checked on the Options screen before any data will be copied. The screen shot
below shows non-default selections where the utility would only copy data in years 2006 and 2007 for
the Actual Scenario:



Year Options

Limit Data to one or more Years: Select this option when you need to copy a subset of
historical data. Be careful to consider the impact Rules may have when previous Year data is
not copied.

Scenario Options

Limit data to one or more Scenarios: Select this option to copy only a subset of the overall
application. Be care to consider the impact Rules may have when Scenarios are not copied

Data Options

Do not export Numeric Data: When this option is selected the numeric data is not copied but
cell text and line item detail information is copied.

Do not export User data (grids, forms, reports, etc): This is information maintained in the
USERPARAMS.


Version 1.4 7/28/2011 Page 11 of 20


Invalid Records Options

Note the warning that these options will impact performance and require more database sort area. The
utility does a join on the DCN and DCE tables with the metadata ITEM tables.

Filter invalid Calc Status Records: Invalid Calc status records are the result of Meta Data
changes. This option selects only the rows for which the entity and value exist in the database.

Filter invalid Data Records: Invalid Data status records are the result of Meta Data changes.
This option selects only the rows where the entity, account, ICP, custom1-4 exist.

Filter Zero value data records: Zeros in the application can impact application performance.
The utility does not copy rows found to have zeros for all periods.

Database Options
The Database Options tab allows for control over where the data is stored in the database. Multiple
tablespaces can be configured based on database table types.



Data Table: consist of all Scenario/Year tables (DCN, DCE, CSN, CSE, LID, TXT, RTD, etc). These
tables are generally written to and read from quite frequently. They generally have large amounts of
relatively small rows.

Metadata Tables: consist of all of the metadata based tables (DESC, LAYOUT, HEADER, ITEM).
These tables are read from and written to fairly infrequently. They have small numbers of small rows.

System Tables: are read from rather frequently (HSV, HSX, HFM). Excluding the HFM_ERRORLOG
table (which is not read or written to by the Copy App utility) these tables have small row counts.

Audit Tables: generally have large numbers of rows of medium sized data. They are written to rather
frequently and read from infrequently.


Version 1.4 7/28/2011 Page 12 of 20


BLOB Tables: (the current option shows LOB tables but will be changed to read BLOB in the next
release) have BLOB columns that are broken up to 2Kb chunks. These tables are read from more
frequently than written to.

Data Tablespace: Allows you to control where data objects are created by copy utility. Change from
<Default> is only needed in environments where DBA wants to separate data and index objects. Note
that the HFM application server(s) should also be configured to use the same tablespace options so
new tables are created in the expected location. When the Target database is MS SQL Server, you will
see all File groups configured for the specific database configured in the Target UDL. When the Target
database is Oracle, you will see a list of all tablespaces that the user has quota to create objects.

Index Tablespace: Allows you to control where index objects are created by copy utility. Change from
<Default> is only needed in environments where DBA wants to separate data and index objects. Note
that the HFM application server(s) should also be configured to use the same tablespace options so
new indexes are created in the expected location. When the Target database is MS SQL Server, you
will see all File groups configured for the specific database configured in the Target UDL. When the
Target database is Oracle, you will see a list of all tablespaces that the user has quota to create
objects.




Confirmation screen


This screen allows you to verify all settings before selecting Next to start the copy process.


Version 1.4 7/28/2011 Page 13 of 20


Copying


The processing status screen displays the current status of each task. To see the log entries for any
given task at any time during processing, simply double-click on the task row to display the Task Entry
Log screen.

Note that when the Source and Target are the same database and the same schema (user) the utility
does not process each table row by row, instead an INSERT INTOSELECT FROM statement is
used. As a result of this, the utility will not display a row count showing the number of rows that have
been processed but the log still will show the number of rows copied.

Task Entry Log Screen
Completed Tasks


Version 1.4 7/28/2011 Page 14 of 20


Failed Tasks


To see the log entries for any task, running or completed, double click on the entry in the Task Status
window. If the Display SQL Errors option has been selected, the error generated by the RDBMS will
also be displayed in the log.

If the Task Entry Log screen is displayed after all processing has completed, you will have the option of
restarting the task.
Restart Task screen




Once all processing has completed, you can go to any task in the list, double-click on the entry and
activate the Restart Task page. From this page you can change task options and select the Restart
Task button. The task will then be re-executed with the new options (if any). The task entry in the
Processing Status screen will be updated with current Task progress.


Version 1.4 7/28/2011 Page 15 of 20




Finished



If all tables have successfully copied then select OK to see the Finish screen.



From the Finished screen, you can review the log file.


Version 1.4 7/28/2011 Page 16 of 20


Command Line Interpreter

New in the 11 releases is a copy application utility that accepts command line input. This utility allows
for scheduling of copy operations using third party scheduling utilities like the built in Windows
Scheduler. In release 11.1.2+, the HFM Copy App Command Line Utility is located in
%EPM_ORACLE_HOME%\Products\ FinancialManagement \Utilities. For all prior 11.1.1+ releases the
location is %Hyperion_Home%\FinancialManagement\Server. The utility is named
HfmCopyAppCmd.exe or HfmCopyAppCmd_x64.exe.

The command line utility has the same options as the GUI based utility with the exception being that
there is no progress window to look at competed tasks and no option to retry a failed task. In order to
run the command line utility, the machine running the utility must have installed the Microsoft Visual
C++ 2005 SP1 Redistributable Package. This is installed by the 11 release installer but it may also be
downloaded from Microsoft directly:

http://www.microsoft.com/downloads/details.aspx?FamilyID=200b2fd9-ae1a-4a14-984d-389c36f85647 for x86
http://www.microsoft.com/downloads/details.aspx?familyid=EB4EBE2D-33C0-4A47-9DD4-B9A6D7BD44DA for x64.


Usage:

HfmCopyAppCmd.exe -S="<source UDL>" -s=<source app> -D="<destination UDL>" -d=<destination
app>

Optional Parameters:
-o="<log file path>" Default is HYPERION_HOME\logs\hfm\HfmCopyApp.log
-cd=Y/N Copy data (default is Y)
-cdt=Y/N Copy data tables (default is Y) see notes
-ca=Y/N Copy Audit data (default is N)
-cc=Y/N Copy Cluster information (default is N)
-r=Y/N Replace destination app if it exists (default is Y)
-da=Y/N If Replace Existing is true, this flag specifies whether to drop all tables prior to copy
(default Y) or only drop tables being copied (N)
-e=Y/N Log and SQL errors generated during copy (default is N)
-ss=Y/N Use server-side cursors (default is Y)
-sb=Y/N Use SQL binding (default is Y)
-fn=Y/N Filter numeric data (default is N)
-fu=Y/N Filter user data (default is N)
-ic=Y/N Filter invalid Calc Status records (default is N)
-id=Y/N Filter invalid data records (default is N)
-z=Y/N Filter zero value data records (default is N)
-t=<Num> Number of processing threads (default is num CPUs x 2)
-c=<Num> SQL Command Timeout setting (default is zero. no timeout)
-Y="<years>" Semi-colon delimited list of one or more years
-SC="<scenarios>" Semi-colon delimited list of one or more scenario ID's. You must specify the
HFM Scenario ID and not the label.
-dts="<data tablespaces>" Semi-colon delimited list of data tablespaces to use (see notes)
-its="<index tablespaces>" Semi-colon delimited list of index tablespaces to use (see notes)

-f="<parameter file>" Path to parameter file to use instead of command line settings. Parameter file
settings override command line settings

Version 1.4 7/28/2011 Page 17 of 20


Notes:
Place quotes around all parameters that contain spaces.

In order to disable creation of data tables (cdt), you must disable data copy (cd). The option -cd=N must
appear before the -cdt=N. If this order is not correct, tables will be created anyway.

Tablespaces (index and data) must be listed in the following order. If you do not wish to provide a
tablespace for a given type, simply omit it but leave its semi-colon delimiter.

-dts="DEFAULT;DATA;METADATA;SYSTEM;AUDIT;LOB;"

where
DEFAULT = The tablespace where all un-specified tables or indexes will reside
DATA = The tablespace where Data table (DCN,DCE,CSE,CSE, etc) data or indexes will reside
METADATA = The tablespace where all Metadata tables or indexes will reside
SYSTEM = The tablespace where all system tables or indexes will reside
AUDIT = The tablespace where all audit table data or indexes will reside
LOB = The tablespace where the BINARYFILES and USERPARAMS tables or indexes will
reside

Parameter file usage:

All parameters must be listed on a separate line. Parameters can be in any order. Use command
HfmCopyAppCmd.exe -cf="<filename>" to create a blank parameter file.


Example command string run from directory where HfmCopyAppCmd_x64.exe resides (the following is
typed on 1 line):

hfmcopyappcmd_x64.exe -S="D:\oracle\Middleware\EPMSystem11R1\products\FinancialManagement\hfm.udl" -
s=Comma11 -D="D:\oracle\Middleware\EPMSystem11R1\products\FinancialManagement\hfm.udl" -
d=Comma112 -r=Y -da=Y

The output from the above command should look the following:

Parsing command line parameters...
Command line parameter parsing completed.
Starting application copy process...Log File:
D:\Oracle\Middleware\EPMSystem11R1\logs\hfm\HFMCopyAppCmdLog.log

Application copy process completed.
Review the process log for results.
(D:\Oracle\Middleware\EPMSystem11R1\logs\hfm\HFMCopyAppCmdLog.log)
Processing completed.

Version 1.4 7/28/2011 Page 18 of 20


Log review

Starting with the 11 releases, the log file created by the copy application utility is located in the
%HYPERION_HOME%\logs\hfm folder. The log file name of the last copy will be HFMCopyApp.log.
When the utility has been run multiple times, the existing HFMCopyApp.log file is renamed using the
format HFMCopyApp-MMDDYYYYHHMMSS.log where MMDDYYYYHHMMSS is based on the Date
and time the original file was created. The log created by HfmCopyAppCmd.exe and
HfmCopyAppCmd_x64.exe is named HFMCopyAppCmdLog and follows the same renaming rules.

The following shows what the top section of a log looks like:




Version 1.4 7/28/2011 Page 19 of 20


The following shows the next section in the log which is the initialization:





One step in the initialization is the creation of 2 cache tables in the Source environment named
HFMCAU_COLUMN_INFO and HFMCAU_INDEX_INFO. These 2 tables contain the table and index
Data Definition Language (DDL) to use when creating the new tables in the Target environment. The
cache tables are dropped when the copy utility successfully completes. An error in the initializing
section related to these 2 cache tables usually either means the RDBMS user in the Source UDL file
does not have the rights to create tables or that these 2 cache tables already exist but were created
from an older version of the utility. DBA can check and drop these 2 tables if they are found to exist
when the copy utility is not running. The information contained in these 2 tables allows the utility to
create the Target tables faster as the DDL can be retrieved faster from the tables rather than
generating the DDL one table at a time while the utility is running. If the cache tables are not able to be
created for any reason the Target application can still be successfully copied.

Next is an example of an error caused when a newer version of the copy utility tries to update
preexisting cache tables left over from a failed copy attempt started from an older utility version.
Manually dropping these 2 tables prevents the error from happening the next time the utility is run:




Version 1.4 7/28/2011 Page 20 of 20


The next log snippet shows the entries for 1 table that has been successfully copied:



The next log snippet shows an error occurring while copying a table when the database ran out of
space: