Email notification does not work.

To make sure that email notification works with the DAC server, make sure that the following are true:

• To set up the email notification feature, you must bring up the DAC client on the same machine as the DAC server.
• The Email server settings (using the DAC client's server setup) point to a valid SMTP server.
• The SMTP server must be supporting Login Authentication. In the Exchange server, this amounts to enabling the Basic Authentication for SMTP module.

The DAC server does not start.

When trying to bring up the DAC server, make sure that the following are taken care of:

• The DAC System properties contain the name of the DAC Server Host machine. This specifies the machine on which the DAC server will be run. Make sure that this entry is correct, and points to where you are bringing up the DAC server. Furthermore, there is an entry for the DAC Server OS, which should specify the OS where the DAC server is running. Make sure that this entry is correct.
• Make sure that the $DAC_HOME/lib directory contains the needed JDBC libraries.
• You may want to edit the startserver.bat file temporarily, and run the DAC server in such a way that messages show in the command window. (Use JAVA rather than JAVAW for Windows OS). This will allow you to see a lot of run-time information, as the server boots up.

The DAC server does not start.

• In the DAC System properties, there is an entry called Logging Level. You can increase the amount of information logged by decreasing the logging-threshold. In other words, if the value currently is SEVERE, make it INFO. This will show more information. If you still cannot find the cause, you may want to change it to FINE or FINEST. These levels are the standard levels of Java's Logging API. (SEVERE, WARNING, INFO, CONFIG, FINE, FINER, FINEST).
  • Be aware that as you lower the logging threshold, a lot of run-time information will start getting logged. While this may be advantageous for troubleshooting, you do not want to leave it like this in production mode. Excessive logging will generate large log files quickly and use excessive disk space. There is also a modest performance hit with excessive logging.
• Make sure that there is no DAC server already running on the machine. Only one DAC server instance can exist per machine (and per DAC repository). Some non-visible forms of the DAC server may be running as a background process.
• Make sure that the DAC repository database instance is actually up and running. The DAC repository database being down or the loss of network connectivity to the database will cause the DAC server not to come up, or to go down if it was running.
• Make sure that the DAC repository database connection pool size is moderate. In other words, do not try to acquire an excessive number of connections when the database administrator may have put restrictions on how many a single application can request.

When starting the DAC client and server for the first time (after configuring the DAC server by using the DAC client), the DAC client's icon for the Server status stays red. In other words, it suggests the server is down, even though it is running.

This is expected behavior. The first time the DAC server comes up against a repository, it creates a Unique ID for itself, and the repository. Thereafter, when any client is started against the repository, it knows where to expect the DAC server to be, and furthermore, sends a valid identification token containing the Unique ID.

Therefore, after bringing up the DAC server the first time, you may want to close the existing open clients, and bring them up again. This problem is specific to bringing up the DAC client and server for the first time. Once Unique ID has been created, the behavior of the Server Monitor icon will be as expected.

When exporting the DAC repository against a DB2 database, failures occur. An error message may appear and the export.log file may have an entry similar to the following: "Error while moving to reading next record."

This problem is specific to DB2 databases and occurs only when the following tables are exported:

• WETL_DBCONN
• W_ETL_SYSPROP
• W_ETL_SERVER

This problem tends to occur when the database is under significant load. Therefore, it is recommended that you export these tables individually.

Running the DAC server on AIX machines.

Special care must be taken when bringing up the DAC server on AIX machines. For example, if the repository already contains database connection information entries, and Informatica Server entries, these must be modified if you are moving the DAC server to an AIX machine.

In particular, you need to delete all the password fields, and re-enter them. For more information, see Siebel Data Warehouse Installation and Configuration Process on UNIX.

The DAC client does not run on machines where PopChart Image Server from CORDA Technologies, Inc., is running.

Run the DAC client on a machine that does not have PopChart Image Server from CORDA Technologies, Inc., installed.