Informatica Workflow Succeeded But Session Failed

Sometime it happens like Informatica session got failed but Workflow will show as succeeded. If you are running mappings though DAC , DAC will not stop execution as Workflow got succeeded. So in that case it is very difficult to find out the failed mappings. So to control the DAC and to get the actual status of mapping we need to enable a option , "Fail parent if this task failed" in session level.

Open session and enable the below showed options.

Enjoy and stay well !! :)

DAC : Login Error - Couldn't Store Login Data

Sometime we used to get an error after installation of DAC when we are trying to login to DAC.
It shows like - "Couldn't Store Login Data"

Reason for this error is : The cwallet.sso file does not have the full permissions for these DAC user.

Solution : Check the permissions and give Full Permissions to this file to all your DAC Users.

(Path of cwallet.ssp file: C:\dac11g\dac\conf\security\cwallet.sso )


Enjoy and stay well !! :)


  

DAC Encryption key Change

Today we will discuss how to create a new Encryption key for DAC repository. Sometime we used to get an error while trying to start/stop the DAC server. Error description will be like  “Encryption key in authentication file doesn't match the repository. Please use the correct authentication file to connect.”

 To change the DAC encryption key

1.       In the DAC Client, on the Tools menu, select DAC Repository Management, and then select Change Encryption Key.

 

2.       Click Generate Random Encryption Key to generate an encryption key. The key is displayed in the Key field. Alternatively, you can enter a key in the Key field. The key must be at least 24 characters long.

 

3.       Distribute the updated authentication file (cwallet.sso) to all users that connect to this repository.

 

Enjoy & Stay Well !! :)

 

 

 

DAC Repository Backup in LINUX

To take backup of DAC repository using Unix/Linux command, you  need to configure two files of DAC server.

1.    automationutils.properties

2.      automationUtils.sh 

automationutils.properties file configuration:

automationutils.properties is the connection file where you need to specify the connection details of the database and DAC server.

File structure will be as below:

#Database information - for DAC and DW operations JDBCDriver=oracle.jdbc.driver.OracleDriver JDBCUrl=jdbc:oracle:thin:@<host>:<port>/<instance name> DatabaseCredentialsFile=<path to db credentials cwallet> #Authentication information - for DAC operations UserCredentialsCWalletPath=<path to user credentials cwallet>

 

DatabaseCredentialsFile should point to authentication file (the one we use for DAC client login, the same one in /dac/conf-client/connections/ in an installation where DAC server connects to a desired repository). If you want an automated way of creating such files (doesn't seem to be the case here), use automationUtils dbCredentials command.

UserCredentialsCWalletPath should point to a cwallet.sso file /dac/conf-client/connections/ that contains DAC user name and password. Create this file using automationUtils cmdCredentials command.

Note: it can be a different file or you can use cmdCrentials to inject user credentials into the same authentication file, it will not conflict with db credentials that file contains. 

Make sure authentication file (same one used by DAC client to log into repository) in available in the environment where you want to run command line from.

Point DatabaseCredentialsFile and UserCredentialsCWalletPath in automationutils.properties to this file.

E.g. :

DatabaseCredentialsFile = /dac/conf-client/connections /cwallet.sso

           

         UserCredentialsCWalletPath = /dac/conf-client/connections /cwallet.sso

Once the file has been configured then run it using the below commands:

./automationUtils.sh cmdCredentials <path to authentication file> <username>

E.g.

automationUtils.sh cmdCredentials /dac/conf-client/connections Administrator

You will be prompted to enter password for Administrator User.

automationUtils.sh file configuration:

You need to configure this file If you will get some issue while exporting the DAC repository like

SEVERE: MESSAGE:::GC overhead limit exceeded

EXCEPTION CLASS::: java.lang.OutOfMemoryError

In this case we need to increase the JAVA heap memory size in ./automationUtils.sh file as mentioned below.

For example, if it's at 256MB right now (-Xmx256m) increase it to 512MB (-Xmx512m). 

Commands to Export DAC Repository:

./automationUtils.sh  automationutils.properties  export  <Path to Export the DAC Repository>