Table 11. DAC System Properties
|
|
Analyze Frequency (in days) |
For the DAC repository table, the frequency (in days) the DAC client automatically updates the table and index statistics for the DAC repository. The value must be numerical. |
|
For the data warehouse schema tables, indicates whether during the ETL process the DAC server automatically issues analyze table statements when a table is truncated and loaded. Possible values are True and False. |
|
When the DAC server abnormally terminates during the execution of an ETL, the status remains as Running. The status of an ETL is updated only by the DAC server. When this property is set to True, the server automatically continues running the ETL process. When set to False, the run statuses are updated to Failed. In this case, the administrator needs to restart the failed ETL manually. |
CreateQueryIndexesAtTheEnd |
During the ETL process, the DAC server automatically drops and creates indices. When set to True, this property groups all query type indices and runs them after the ETL is complete. Possible values are True and False. |
|
Host name or IP address of the machine where the DAC server resides. Note: The DAC server and a given DAC repository have a one-to-one mapping. That is, you can only run one DAC server against any given DAC repository. Thus, in the repository you must specify the network host name of the machine where the DAC sever is to be run. Note: This property also takes the value localhost. However, this value is provided for development and testing purposes and should not be used in a production environment. |
|
Operating system of the machine where the DAC server resides. Possible values are Windows, Solaris, or AIX. Note: If you move the DAC server from another operating system to AIX, you need to change the DAC server host to the appropriate value, restart the DAC client, and reenter all the password fields for the Informatica servers and database connections, and reconfigure the DAC server on the AIX machine by running the serverSetupPrompt.sh. |
|
Network port to which the DAC server binds in order to listen to client requests. The default value is 3141. If this port has been assigned to another process, you can enter any numerical port value greater than 1024. |
|
Indicates whether, during the ETL process, the DAC server automatically drops and creates indices. Possible values are True and False. |
|
Indicates whether tasks are executed without invoking Informatica workflows. The following processes are executed: change capture, truncation of tables, drop and creation of indices, and analyze statements. Possible values are True and False. Note: This option should be used for debugging purposes only and not used in a production environment. |
Generic Task Concurrency Limit |
Determines how many tasks with execution types other than Informatica can be run concurrently. The value must be numerical. |
|
Frequency (in seconds) the DAC server checks on the health of the database connections. The value must be numerical. For example, a value of 300 (the default value) indicates the system will perform subsystem diagnostics and recovery procedures every 300 seconds. |
|
Indicates whether logging information and standard output and errors are redirected to files in the log directory (when property is set to True). The file containing standard output starts with out_ and ends with the .log extension. The standard error messages are in the file starting with err_ and ending with the .log extension. If this property is set to False, the logging information is directed to the machine's standard output and error files, which typically defaults to the console from which the DAC server was launched if the server was launched in a visible console mode. If the server is launched as a Windows service, the logging information is directed to the service log. If the server is launched with the command shell not visible, all logging information is deleted. |
|
Maximum number of connections to the DAC repository the DAC server will maintain. The value must be numerical. Note: As the DAC server runs it needs to perform transactions and queries on the DAC repository. In order for it to do so efficiently, it internally maintains a pool of preexisting database connections. This reduces latency and leads to better use of resources through connection sharing. However, for this to happen, you need to specify the maximum size of the connection pool. This setting should be determined in consultation with the database administrator of the database where the DAC repository resides. |
|
Frequency (in seconds) the DAC server polls for changes in the schedule configuration. |
|
The name of the script or executable to be run before every execution plan. For example, before running an execution plan, you might want to run a process or perform certain tasks. These can be contained in a script or executable. This file should be placed in the scripts subdirectory of the DAC server. The execution plan runs only after the external process has finished. Therefore, it is important that the script or executable does not fail. |
|
The name of the script or executable to be run after every execution plan. For more information, see the description of the property Script Before Every ETL. |
|
Output logging level. Possible values are Finest, Finer, Fine, Config, Info, Warning, and Severe. The Severe value produces minimal log details, and Finest produces the most extensive amount of reporting. |
|
Indicates whether the SQL statements to the DAC repository and database connections are added to the log file. Possible values are True and False. The True value hints the database connectivity layer of the DAC server to enable SQL tracing; thus, every SQL statement that is run by the DAC server is spooled to the appropriate output log file. It is recommended that you set this property to False. |
