This topic gives detailed description of command line switches and examples of their usage.
To get more information on switches related to schema comparison in the command line interface, you can type:
C:\Program Files\Devart\Compare Bundle for Oracle\dbForge Schema Compare for Oracle>schemacompare.com /schemacompare /?
Below all switches of this option are described, together with usage examples.
| Argument | Action and Usage |
|---|---|
| /compfile | This switch is used to load command line settings from the comparison project file, *.scomp. Command usage looks like: /compfile:<path> Example of using a file with comparison settings, saved earlier: C:\Program Files\Devart\Compare Bundle for Oracle\dbForge Schema Compare for Oracle>schemacompare.com /schemacompare /compfile:"D:\workDir\OSC1vsOSC2.scomp" |
| /groupby | This switch is used when generating comparison reports. use it to group objects in such report. Command usage looks like: /groupby:<none/status/objecttype> The following example shows how to compare schemas using settings from the file, generate comparison report, and group objects in the report by type: C:\Program Files\Devart\Compare Bundle for Oracle\dbForge Schema Compare for Oracle>schemacompare.com /schemacompare /compfile:"OSC1vsOSC2.scomp" /report:"report.txt" /reportformat:HTML /groupby:objecttype |
| /log | Use this switch if you want to generate comparison log file in a specified directory. Command usage looks like: /log:<filepath> The following example shows how to compare schemas using settings from the file and write log to the specified file: C:\Program Files\Devart\Compare Bundle for Oracle\dbForge Schema Compare for Oracle>schemacompare.com /schemacompare /compfile:"OSC1vsOSC2.scomp" /log:"D:\sync.log |
| options | You can specify some comparison and synchronization options directly in the command line interface. See the list of available options and learn how to use them in the Command Line Options for /schemacompare Operation topic. |
| /report and /reportformat | You can generate schema comparison report in .html or .xls format. If you specify file format in the output file name in the /report switch, it is not necessary to use the /reportformat switch. Commands usage looks like: /report:<filepath> ` /reportformat:<HTML|XLS|XML|XMLFOREXCEL> <br/> The following example shows how to compare schemas using settings from a file, generate report to the specified file in the HTML format: <br/> C:\Program Files\Devart\Compare Bundle for Oracle\dbForge Schema Compare for Oracle>schemacompare.com /schemacompare /compfile:”OSC1vsOSC2.scomp” /report:”report.txt” /reportformat:HTML` |
| /source | You can specify source database schema for comparison and synchronization in the command line. It is possible to use several options for defining the schema. To connect to a server via Oracle client, type: server:<server_alias> [home:<oracle_home_name>] user:<user_name> password:<pw> mode:[normal/sysdba/sysoper] To connect to a server without using Oracle client (direct connection), type: host:<machine_name> [port:<port_number>] SID:<oracle_service_ID> user:<user_name> password:<password> mode:[normal/sysdba/sysoper] To specify full connection string with additional parameters, type: connection:<connection_string> To specify a snapshot file path, type: snapshot:<filepath> |
| /target | You can specify target database schema for comparison and synchronization in the command line. It is possible to use several options for defining the schema. To connect to a server via Oracle client, type: server:<server_alias> [home:<oracle_home_name>] user:<user_name> password:<pw> mode:[normal/sysdba/sysoper] To connect to a server without using Oracle client (direct connection), type: host:<machine_name> [port:<port_number>] SID:<oracle_service_ID> user:<user_name> password:<password> mode:[normal/sysdba/sysoper] To specify full connection string with additional parameters, type: connection:<connection_string> To specify a snapshot file path, type: snapshot:<filepath> |
| /schemas | You can specify schemas to compare. If you don’t, schemas specified in /source and /target will be used. Command usage looks like: /schemas:<source_1>,<target_1>[;<source_2>,<target_2>;...] The following example shows how to compare schemas using connection through client. C:\Program Files\Devart\Compare Bundle for Oracle\dbForge Schema Compare for Oracle>schemacompare.com /schemacompare /source server:OraServer user:system password:pswd /target server:OraServer2 user:system password:pswd /schemas:OSC1,OSC2" |
| /sync | You can perform schema synchronization from the command line interface. If you specify output file for synchronization, only synchronization script will be generated. Command usage looks like: /sync[:path] The following example shows how to compare schemas using settings from the file saved before, and save synchronization script: C:\Program Files\Devart\Compare Bundle for Oracle\dbForge Schema Compare for Oracle>schemacompare.com /schemacompare /compfile:"OSC1vsOSC2.scomp" /sync:"D:\compare_result.sql" |
| /activate | This switch is used for product activation with the license key. |
| /deactivate | This switch is used for the product deactivation. |
/schemacompare /compfile:"D:\workDir\OSC1vsOSC2.scomp"
/schemacompare /source server:OraServer user:system password:pswd /target server:OraServer2 user:system password:pswd /schemas:OSC1,OSC2 /sync /log:"D:\sync.log"
/schemacompare /source host:oraHost port:1521 SID:orcl user:sys password:manager mode:sysdba /target server:OraServer user:system password:pswd /schemas:SC1,SC2;OSC1,OSC2 /sync:"D:\compare_result.sql"
/schemacompare /compfile:"OSC1vsOSC2.scomp" /icase:yes /IgnoreForeignKeys:yes /report:"report.txt" /reportformat:HTML /groupby:objecttype /incsettings:T /sync