Error in SSMA console

Question

Hi ,
I am getting the following vague error when i am executing the script using SSMA console application
SSMAforOracleConsole.exe –s "C:\Users\Arup\Desktop\SQL Server\Console Application\ConversionAndDataMigrationSample_New.xml"
FATALERR invalid argument used.
Any help is highly appreciated

Answer 1

Hi Lydia,
Thanks for your Reply.Pfb the code i am using for my ssma migration.
<?xml version="1.0" encoding="utf-8"?>
<!--
Script file for SSMA-v4.2 Console for Oracle.
Commands execution order - from top to bottom.
Command Processor distinguishes each command by element name.
The element name is invariable! Never modify it!
Use this file name as the parameter to SSMA-v4.2 Console for Oracle with mandatory
option -s[cript]. See the documentation for SSMA-v4.2 Console for more information.
-->
<ssma-script-file xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="C:\Microsoft SQL Server Migration Assistant for Oracle\Schemas\O2SSConsoleScriptSchema.xsd">
<!-- Variable values should mandatorily start and end with "$".
These values can be defined in a separate variable value file
(See :VariableValueFileSample.xml)
********** Set the variable values used by this sample **********
********** file in the corresponding Variables Value File **********
-->
<!-- The escape character for “$” is “$$”.If the value of a static value of a parameter begins with “$”,
then "$$" must be specified to treat it as a static value instead of a variable. -->
<!-- Optional section with console configuration options-->
<config>
<output-providers>
<!-- Command specific messages do not appear on console if value set to "true".
Attributes: destination="file" (optional)
file-name="<file-path>" (optional along with destination attribute)
By default destination="stdout" and suppress-messages="false" -->
<output-window suppress-messages="false"
destination="file"/>
<!-- Enables upgradation of project created from earlier version of SSMA to current version.
Available action attribute values
• yes - upgrades the project (default)
• no - displays an error and halts the execution
• ask-user - prompts user for input (yes or no). -->
<upgrade-project action="yes"/>
<!-- Enables upgradation of project created from earlier version of SSMA to current version.
Available action attribute values
• yes - upgrades the project (default)
• no - displays an error and halts the execution
• ask-user - prompts user for input (yes or no). -->
<upgrade-project action="yes"/>
<!--Enables creation of database during connection. By default, mode is error..
Available mode values
• ask-user - prompts user for input (yes or no).
• error - console displays error and halts the execution.
• continue - console continues the execution.-->
<!--<user-input-popup mode="continue" />-->
<!-- Data migration connection parameters
Specifies which source or target server to be considered for data migration
Attributes: source-use-last-used="true" (default) or source-server="source_servername"
target-use-last-used="true" (default) or target-server="target_servername" -->
<data-migration-connection source-use-last-used="false"
target-server="target_1"/>
<!-- Progress Reporting. By default progress reporting is disabled.
report-progress attribute values
• off
• every-1%
• every-2%
• every-5%
• every-10%
• every-20% -->
<progress-reporting enable="false"
report-messages="false"
report-progress="off"/>
<!-- Reconnect manager -->
<!-- Reconnection parameter settings incase of connection failure
Available reconnection modes
• reconnect-to-last-used-server - If the connection is not alive it tries to reconnect to last used server
• generate-an-error - If the connection is not alive it throws an error(default)
<reconnect-manager on-source-reconnect="reconnect-to-last-used-server"
on-target-reconnect="generate-an-error"/>-->
<!-- Prerequisites display options.
If strict-mode is true, an exception is thrown in case of prerequisite failures-->
<!--<prerequisites strict-mode="true"/>-->
<!-- Object overwrite during conversion.By default, action is overwrite
Available action values
• error
• overwrite
• skip
• ask-user -->
<object-overwrite action="skip" />
<!-- Sets log verbosity level. By default log verbosity level is "error"
Available logger level options:
• fatal-error - Only fatal-error messages are logged
• error - Only error and fatal-error messages are logged
• warning - All levels except debug and info messages are logged
• info - All levels except debug messages are logged
• debug - All levels of messages logged
Note: Mandatory messages are logged at any level-->
<!--<log-verbosity level="error"/>-->
<!-- Override encrypted password in protected storage with script file password
Default option: "false" - Order of search: 1) Protected storage 2) Script File / Server Connection File 3) Prompt User
"true" - Order of search: 1) Script File / Server Connection File 2) Prompt User -->
<!--<encrypted-password override="true"/>-->
</output-providers>
</config>
<!-- Optional section with server definitions -->
<!-- Note: Server definitions can be declared in a separate file
or can be embedded as part of script file in the servers section (below)-->
<servers>
<sql-server name="target_1">
<windows-authentication>
<server value="ARUP-MANISHA\SQLEXPRESS"/>
<database value="AdventureWorks2012"/>
<encrypt value="true"/>
<trust-server-certificate value="true"/>
</windows-authentication>
</sql-server>
<oracle name="source_1">
<standard-mode>
<connection-provider value ="OracleClient"/>
<host value="arup-manisha" />
<port value="1521" />
<instance value="XE" />
<user-id value="arup" />
<password value="arup"/>
</standard-mode>
</oracle>
<script-commands>
<!--Create a new project.
• Customize the new project created with project-folder and project-name attributes.
• overwrite-if-exists attribute can take values "true/false" with default as "false".
• project-type (optional attribute) can take values
sql-server-2005 - Creates SSMA 2005 project
sql-server-2008 - Creates SSMA 2008 project (default)
sql-server-2012 - Creates SSMA 2012 project
sql-server-2014 - Creates SSMA 2014 project
sql-azure - Creates SSMA Azure project -->
<create-new-project project-folder="C:\Users\Arup\Documents\SSMAProjects"
project-name="SqlMigration5"
overwrite-if-exists="true"
project-type="sql-server-2012"
/>
<!-- Connect to source database -->
<!-- • Server(id) needs to mandatorily be defined in the servers section of the
script file or in the Servers Connection File-->
<connect-source-database server="source_1" />
<!-- Connect to target database -->
<!-- • Server(id) needs to mandatorily be defined in the servers section of the
script file or in the Servers Connection File-->
<connect-target-database server="target_1" />
<!--Schema Mapping-->
<!-- • source-schema specifies the source schema we intend to migrate.
• sql-server-schema specifies the target schema where we want it to be migrated.-->
<map-schema source-schema="arup"
sql-server-schema="arup.dbo" />
<!--Refresh from database-->
<!-- Refreshes the source database
• object-name specifies the object(s) considered for refresh .
(can have indivdual object names or a group object name)
• object-type specifies the type of the object specified in the object-name attribute.
(if object category is specified then object type will be "category")
• on-error specifies whether to specify refresh errors as warnings or error.
Available options for on-error:
•report-total-as-warning
•report-each-as-warning
•fail-script
• report-errors-to specifies location of error report for the refresh operation (optional attribute)
if only folder path is given, then file by name SourceDBRefreshReport.XML is created -->
<!-- Example1: Refresh entire Schema (with all attributes)-->
<!--<refresh-from-database object-name="$OracleSchemaName$"
object-type ="Schemas"
on-error="fail-script"
report-errors-to="$RefreshDBFolder$" /> -->
<!-- Example2: Refresh a particular category say a procedure (other convention of the command with only mandatory attributes)-->
<!--<refresh-from-database>
<metabase-object object-name="$OracleSchemaName$.Testproc" object-type="Procedures"/>
</refresh-from-database>-->
<!-- Convert schema -->
<!-- • object-name specifies the object(s) considered for conversion .
(can have indivdual object names or a group object name)
• object-type specifies the type of the object specified in the object-name attribute.
(if object category is specified then object type will be "category")
• conversion-report-folder specifies folder where the conversion report can to be stored.(optional attribute)
• conversion-report-overwrite specifies whether to overwrite the conversion report folder if it already exists.
Default value: false. (optional attribute)
• write-summary-report-to specifies the path where the summary report will be generated.
If only the folder path is mentioned,then file by name SchemaConversionReport.XML is created. (optional attribute)
• Summary report creation has 2 further sub-categories
• report-errors (="true/false", with default as "false" (optional attributes))
• verbose (="true/false", with default as "true/false" (optional attributes))
-->
<!-- Example1: Convert entire Schema (with all attributes)-->
<convert-schema object-name="$OracleSchemaName$"
object-type="Schemas"
write-summary-report-to="$SummaryReports$"
verbose="true"
report-errors="true"
conversion-report-folder="$ConvertARReportsFolder$"
conversion-report-overwrite="true" />
<!-- Example2: Convert entire Schema (only with mandatory attributes)-->
<!--<convert-schema object-name="$OracleSchemaName$"
object-type="Schemas" />-->
<!-- alternate convention for ConvertSchema command-->
<!-- Example3: Convert a specific category(say Tables)-->
<!--<convert-schema>
<metabase-object object-name="$OracleSchemaName$.Tables"
object-type="category" />
</convert-schema>-->
<!-- Example4: Convert Schema for a specific object(say Table)
(with only a few optional attributes & write-summary-report-to with a file name)-->
<!--<convert-schema object-name="$OracleSchemaName$.TestTbl"
object-type="Tables"
write-summary-report-to="$SummaryReports$\ConvertSchemaReport1.xml"
report-errors="true"
/>-->
<!-- Synchronize target -->
<!-- • object-name specifies the object(s) considered for synchronization.
(can have indivdual object names or a group object name)
• object-type specifies the type of the object specified in the object-name attribute.
(if object category is specified then object type will be "category")
• on-error specifies whether to specify synchronization errors as warnings or error.
Available options for on-error:
•report-total-as-warning
•report-each-as-warning
•fail-script
• report-errors-to specifies location of error report for the synchronization operation (optional attribute)
if only folder path is given, then file by name TargetSynchronizationReport.XML is created.
-->
<!-- Example1: Synchronize target entire schema of Database with all attributes-->
<synchronize-target object-name="arup.dbo"
on-error="fail-script"
report-errors-to="$SynchronizationReports$" />
<!-- Example2: Synchronizing a particular category (say Procedures) of the schema alone -->
<!--<synchronize-target object-name="$SQLServerDb$.dbo.Procedures"
object-type="category" />-->
<!--(alternative convention for Synchronize target command)-->
<!-- Example3: Synchronization target of individual objects -->
<!--<synchronize-target>
<metabase-object object-name="$SQLServerDb$.dbo.TestTbl"
object-type="Tables" />
</synchronize-target>-->
<!-- Example4: Synchronization of individual objects with no object-type attribute-->
<!--<synchronize-target>
<metabase-object object-name="$SQLServerDb$.dbo.TestTbl" />
</synchronize-target>-->
<!-- Save As Script-->
<!-- Used to save the Scripts of the objects to a file mentioned
when metabase=target ,this is an alternative to synchronization command where in we get the scripts and execute the same on the target database.
• object-name specifies the object(s) whose scripts are to be saved .
(can have indivdual object names or a group object name)
• object-type specifies the type of the object specified in the object-name attribute.
(if object category is specified then object type will be "category")
• destination specifies the path or the folder where the script has to be saved, if the file name is not given then a file name in the format (object_name attribute value).out
• metabase specifies whether it ithe source or target metabase.
• overwrite if true then it overwrites if same filename exist , It can values (true/false) -->
<!-- Example1 : Save as script from source metabase-->
<!-- <save-as-script destination="$SaveScriptFolder$\Script1.sql"
metabase="source"
object-name="$OracleSchemaName$"
object-type="Schemas"
overwrite="true" />-->
<!-- Example2 : Save as script from target metabase-->
<!-- <save-as-script metabase="target" destination="$SaveScriptFolder$\Script2.sql" >
<metabase-object object-name="$SQLServerDb$" object-type ="Databases"/>
</save-as-script> -->
<!-- Data Migration-->
<!-- • object-name specifies the object(s) considered for data migration .
(can have indivdual object names or a group object name)
• object-type specifies the type of the object specified in the object-name attribute.
(if object category is specified then object type will be "category")
• write-summary-report-to specifies the path where the summary report will be generated.
If only the folder path is mentioned,then file by name DataMigrationReport.XML is created. (optional attribute)
• Summary report creation has 2 further sub-categories
• report-errors (="true/false", with default as "false" (optional attributes))
• verbose (="true/false", with default as "false" (optional attributes))
-->
<!--Example1: Data Migration of all tables in the schema (with all attributes)-->
<migrate-data object-name="arup.Tables"
object-type="category"
write-summary-report-to="$SummaryReports$"
report-errors="true"
verbose="true" />
<!--alternative convention for Data Migration Command-->
<!--Example2: Data Migration of specific tables with no object-type attribute & write-summary-report-to with a file name -->
<!--<migrate-data write-summary-report-to="$SummaryReports$\datamigreport.xml"
verbose="true">
<metabase-object object-name="$OracleSchemaName$.TestTbl" />
</migrate-data>-->
<!-- Save project -->
<save-project />
<!-- Close project -->
<close-project />
</script-commands>
</ssma-script-file>