If -DIR is not specified, then a full path should be given. To achieve that, you must make two calls to OdiFileDelete. If a directory is moved -DIR , this parameter indicates the new name of the directory. If a file or several files are moved -FILE , this parameter indicates the target directory.
This parameter is: - The new name of the target file if one single file is moved no generic character - The mask of the new files names if several files are moved. The value no indicates that only the files contained in the directory to move not the sub-directories will be moved.
By default, all searched files are uppercases. This is the default behaviour. COPY : Renaming mask of the copied files. By default, the value is set to no Note that if this option is used with APPEND , then the target file will only have the contents of the latest file processed. By default, searched files are uppercase. If this number is reached, the command ends. The value 0 indicates that we wait for all files until the timeout is reached.
If this parameter is 0 and the timeout is also 0, this parameter is then forced implicitly to 1. Default is set to 1 second , which means that Oracle Data Integrator looks for new messages every second. Files written during the OdiFileWait are taken in account only after being closed File size unchanged during this interval. It is used to keep the header lines of the first file during the concatenation. The value No default indicates that no error must be generated if no file is found.
If no scenario exists yet, a new one is generated. This work repository must be defined in the connected master repository. If this parameter is not specified then the object is imported into the current master or work repository. For more information see Section Default is no.
For more information on the import modes, see Section This message should be provided on the line immediately following the OdiInvokeWebService call. See the table below. If no value is given, there is no timeout. This agent may be a local or remote agent.
It must be declared in the master repository. Default value is No. It defines a timeout in milliseconds after which the agent is killed regardless of the running sessions. Default is 0, meaning no timeout and the agent is killed after all its running sessions reach completion.
The following operating systems are supported: Windows 95, 98, ME, using "command. Arguments with spaces should be enclosed in quotes as appropriate for the command shell. If "no", the session continues immediately with error code 0. By default, it executes in Synchronous mode.
Its path may be absolute or relative to the execution agent location. If this parameter is not specified, the file is overwritten if it does exist. Defaults to 0A Unix line break. For a windows line break, the value should be 0D0A. The text can contain variables or substitution methods. Note: Load Plans and session in Running, waiting, or queued status are not purged. Default is session. Target directory for the export. Default is MSG. The original file names are kept.
If this waiting time is reached, the command ends. Default is 1 second. This option can be repeated to create multiple filters. Note: This command is suitable for journalized tables in simple or consistent mode. Journalized table name, mask or list to check. Note that this option works only for tables in a model journalized in simple mode. Name of the CDC Set to check. Note that this option works only for tables in a model journalized in consistent mode. If no context is specified, the execution context is used.
Notes: This command uses the same technique as the standard reverse-engineering, and depends on the capabilities of the JDBC driver used. Note: This command works for tables journalized using simple or consistent set modes. This user may be a system user. This command is deprecated. This parameter is taken into account if -FILE is not specified. If this parameter is omitted, all the files in -DIR are processed. Default is NO. Default is ODI. Default is EN. Default is 3. External Name used by the tRFC server.
Default is. At the end of this period the server stops automatically. If this timeout is set to zero, the server life span is infinite. Default is 0. If this timeout is set to zero, the timeout is infinite.
If this parameter is set to zero, the server expects an infinite number of requests. If the public key authentication fails then it falls back to the normal user password authentication.
Note that all sub-directories matching the remote file name will also be transferred to the local folder. If this argument is specified then public key authentication is done. If the authentication fails then it falls back to the normal user password authentication. The default value is YES.
Example: support mycompany. Example: Attach the files. Example: 0A. This date format is specified using the Java date and time format patterns. If this parameter is omitted, the Load Plan is started in the execution context of the calling session, if any. The privileges of this user will be used. If this parameter is omitted, the load plan is started with privileges of the user launching the parent session.
This password must be encoded. These keywords make load plan execution identification easier. The list is a comma-separated list of keywords. Note: The scenario that is started should be present in the repository into which the command is launched.
If you go to production with a scenario, make sure to take also all the scenarios called by your scenario using this command. The Solutions can help you grouping scenarios for this purpose. If the version specified is -1 , the last version of the scenario is executed.
If this parameter is omitted, the scenario is executed in the execution context of the calling session. If this parameter is omitted, the scenario is executed with privileges of the user launching the parent session. This password should be encoded. This parameter is required if the user is specified. The default value is maximal 5. If this parameter is omitted, the current agent executes this scenario. These keywords make session identification easier. If this parameter is not specified, the current session ID is used.
This parameter accepts three formats : Table Name. Table Names List: Comma separated list of table names. Masks as defined above are allowed. By default, only tables are checked. To take into account other objects, specify a comma-separated list of object types. This statement must be valid for the technology containing the checked tables.
If this value is equal to zero, the timeout is infinite. Defaults to 0. Defaults to Defaults to 1. If set to no , the count is performed in absolute row count mode. Defaults to no.
Possible values are: M : Memory. Defaults to M. This increment sequence is stored in the Repository. If this name is not specified, it takes the name of the table. Otherwise, it will signal an error. Defaults to Yes. Note: This command takes into account all journalized operations inserts, updates and deletes. The command is suitable for journalized tables only in simple or consistent mode.
Defaults to AUTO. Defaults to yes. If no Context is specified, the execution context is used. Note: XML Namespaces are not supported by this tool. This filter uses standard file wildcards?
It includes both file names and directory names. It is possible to take source files from a same folder or from different folders. You can use this parameter to create a customized XML prologue or root element. You can use this parameter to close a root element added in the header. Default is that the ZIP file is updated if it already exists. The value no indicates that only the files contained in the directory to copy without the sub-folders will be archived.
By default, Oracle Data Integrator searches files in uppercases. Interface that every Open Tool must implement. Abstraction of interface with some helper methods. Interface that parameters used by Open Tools must implement. Complete implementation of IOpenToolParameter. Exception class that should be thrown if necessary by Open Tool methods. A simple example of an Open Tool, that can be used as a starting point. Ant Buildfile. Displays the logging information without adornments.
Looks for the Ant Buildfile from the root of the file system and uses it. Path and filename of sound file to play. Location of the Data Quality batch file to execute. File to redirect standard output to leave blank for no redirection, use absolute path. File to redirect standard error to leave blank for no redirection, use absolute path. If set to YES, the tool waits for the quality process to complete before returning, with possible error code.
Directory into which the export files are created. If set to yes , existing export files are overwritten with no warning. ID of the project containing the scenarios to export. ID of the folder containing the scenarios to export. ID of the source package of the scenarios to export. If set to yes, all child objects schedules are exported with the scenarios. Target file encoding.
Indicates if the scenarios attached to packages should be exported. Indicates if the scenarios attached to interfaces should be exported. Indicates if the scenarios attached to procedures should be exported. Indicates if the scenarios attached to variables should be exported. It includes conceptual and background information on the features and functionalities of Oracle Data Integrator. This guide is aimed at developers and administrators who want to use Oracle Data Integrator as a development tool for their integration processes.
Chapter 1 - Concepts provides conceptual information about integration and introduces the general concepts of Oracle Data Integrator. Chapter 2 through 5 describe how to carry out common tasks with Oracle Data Integrator's graphic modules. No other rights are granted to the U. This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury.
If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.
Illustrations and examples in this guide are based on fictitious data. Some illustrations may look different than what you see on your screen. Their functionality is the same.
0コメント