DAC System Properties Tab
The DAC System Properties tab
enables you to configure various properties that determine the behavior of the
DAC Server.
When set to True, this property
enables the DAC clients to remember the user's password when the user logs into
the DAC repository. User passwords are encrypted and stored in the client
machine's file system
For DAC repository tables, this
property specifies the frequency (in days) the DAC Client automatically updates
the table and index statistics for the DAC repository. The value must be
numerical.
The DAC repository tables need to
have table and index statistics kept up to date to maintain the health of the
repository.
Possible values are True and False.
If this property is set to True,
tables will be analyzed after the Query type indexes have been created (even if
the Analyze check box for the target table is deselected).
If this property is set to False,
the table is not analyzed (as long as the Analyze check box for the target
table is deselected).
Possible values are True and False.
When this property is set to True,
an ETL process that is running when the DAC Server abnormally terminates will
continue running when the DAC Server is restarted.
When set to False, an ETL process
that is running when the DAC Server abnormally terminates will not
automatically restart when the DAC Server restarts. The ETL status will be
updated to Failed. An administrator will have to manually restart the ETL.
The maximum number of ETL processes
that can run in parallel. When this property is set to 1 (the default), the ETL
process runs in the same process space with the DAC Server. When this property
is set to more than 1, the ETL processes run as separate OS processes. DAC
interprets invalid values as 1.
Possible values are True and False.
When set to True (the default
value), the DAC Server drops and creates change capture views every time it
performs a change capture process, including for both full and incremental
loads.
When set to False, the DAC Server
will drop and create views selectively, using the following rules:
Ø In full
mode:
v During the change capture phase, views will be dropped and
created as full views.
v During the change capture sync process, incremental views
will be generated.
Ø In
incremental mode:
v If the view exists, it will not be dropped and created.
v If the view does not exist, the incremental view will be
created.
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 indexes, and analyze
statements.
This option should be used for
debugging purposes only and not used in a production environment.
When the execution plan includes
several tasks with the execution type of SQL or Stored Procedure, this property
controls how many of such tasks will be run concurrently at any given time. The
value should be numerical. The changes will be effective for the next ETL.
Restarting the DAC Server is not required.
Determines how many tasks with
execution types other than Informatica can be run concurrently. The value must
be numerical.
To set this value, you should
consider what the external tasks do. For example, if the tasks open connections
to a database, you should consider how this would affect the predefined tasks.
The value must be numerical.
The frequency (in seconds) the DAC
Server polls all subsystems, including database connections, to check whether
they are in a consistent state. If the subsystems are not in a consistent
state, recovery and correction mechanisms are triggered. The value must be
numerical. For example, a value of 900 (the default value) indicates the system
will perform subsystem diagnostics and recovery procedures every 900 seconds.
Directory where the Informatica
parameter files are stored. This is the directory in which the DAC Server
creates the Informatica parameter files and from which Informatica reads the
files.
Possible values are True and False.
When this property is set to True,
tasks are generated in the Task Details subtab of the Current Runs tab, but the
tasks are not executed and the refresh dates are not updated. Use this property
for debugging purposes only.
Possible values are True and False.
When set to True, logging
information and standard output and errors are redirected to files in the log
directory. 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 DAC Server was launched with the command shell not visible,
all logging information is deleted.
Indicates the maximum number of
connections to the DAC Repository that the DAC Server will maintain.
The idle DAC Server maintains a
small spool of pre-existing database connections to the DAC Repository for
efficiency and resource optimization. It increases the pool size to the value
specified in this property when running a regular ETL process and reverts to
the default on completion of the ETL process.
You should consult with the DBA for
the DAC Repository database when setting this property.
Unique name for the DAC Repository.
This name is displayed on the title bar.
Possible values are True and False.
When set to True, the DAC Repository
cannot be upgraded to a newer version.
Possible values are True and False.
When set to True, a hint is sent to
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, because enabling SQL tracing causes the log files to grow
extremely large in a short period.
Frequency (in seconds) the DAC
Server polls for changes in the schedule configuration.
The name of the script or executable
to be run after every execution plan. The file must be placed in the
DAC\scripts directory. For example, after running an execution plan, you might
want to run a process or perform certain tasks. These can be contained in a
script or executable.
The name of the script or executable
to be run before every execution plan. The file must be placed in the
DAC\scripts directory. 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.
The execution plan will run only
after the external process has finished. Therefore, it is important that the
script or executable does not fail.
The output logging level. Possible
values are the following:
Ø FINEST
Ø FINER
Ø FINE
Ø CONFIG
Ø INFO
Ø WARNING
Ø SEVERE
The values are case sensitive. The
values produce varying degrees of output reporting detail, with the Severe
value producing minimal log details, and the Finest value producing the most
extensive amount of reporting.
The recommended value for production
environments is INFO.
Possible values are True and False.
When set to True, the execution plan
will not stop on errors.
Possible values are True and False.
When set to True, indexes defined in
the DAC Repository will be automatically created in the data warehouse database
during an incremental load.
Note: When this system property is
set to True, the DAC Server verifies whether indexes defined in the DAC
Repository are also defined in the data warehouse database. This verification
process can delay the execution of an execution plan.
Frequency (in seconds) the DAC
Client polls the DAC Server for its status when the DAC Server is running in
Web mode.
The number of worker threads
available in the worker pool.
The worker threads do operations
such as:
Ø drop and create indexes
Ø truncate and analyze tables
Ø execute SQL scripts and Informatica workflows
The value for this property should
correspond to the number of task details that are anticipated to run in
parallel.
No comments:
Post a Comment