The RA Informatica Agent will not start after a v2.0.0 to v3.0.0 upgrade in Applications Manager
Document ID :
Last Modified Date :
Show Technical Document Details
CA Automic Workload Automation
CA Automic Workload Automation:Release:2.0
CA Automic Workload Automation:Release:3.0
Details: ORA-20035: Could not find "Db login -"
After an upgrade from RA Informatica v2.0.0j or above to RA Informatica v3.0.0, the agent fails to start.
There were file transfer options added in special patch v2.0.0j and above, which have been removed in version 3.0.0 to improve performance. If a special patch was applied, the options would have been displayed on the Agent's Informatica tab as shown in the image below.
If a change is made to the Informatica Agent after upgrading to version 3.0.0, the Agent will not start and will display an error similar to the following:
INFO36_80RA:ErrorMsg: AwE-5102 Agent error (11/16/12 5:05 PM)
Details: java.sql.SQLException: ORA-20035: Could not find "Db login -"
ORA-06512: at "AM80.AWAPI2", line 473
ORA-06512: at "AM80.AWAPI2", line 446
ORA-06512: at "AM80.AWAPI", line 111
ORA-06512: at "AM80.AWAPI", line 1108
ORA-06512: at "AM80.AWAPI", line 1226
ORA-06512: at line 1
To fully remove the added options from the special patch, please perform the following instructions.
This is a two step process to remove the FTP login in the client and execute a sql script to update the Agent's XML in the database. After completing these steps, restart the Informatica Agent.
Step One: Removing the FTP login in the AM client (if it exists):
Log in to the Applications Manager Client
Open the Logins Selector Window (Object Admin->Administration->Logins)
Delete ALL of the Informatica FTP logins (if there is more than one).
To display Informatica FTP logins, sort the Description field (click on the column to sort) and find all with FTPConnection-InformaticaAgent as shown in this image.
Step Two: Updating the Agents' XML
Transfer the infa_ftp_migration.sql file to your Master server:
Login to sqlplus as the AM Oracle user and install the migration script by issuing the following:
3. Execute the remove_ftp_ref procedure for either a single agent or all agents to update their XML data.
4. Use one of the following options:
a. To Remove XML ftp information for a specific Informatica agent where agentname is your Informatica Agent name
SQL> execute remove_ftp_ref ('AGENT_NAME');
b.To Remove XML ftp information for all Informatica agents
SQL>execute remove_ftp_ref (null);
This SQL procedure will print out the Before and After XML update values.
You can verify the Agent's XML data to ensure it has successfully been updated by checking the SO_OPERATORS table to compare what is printed out by the procedure. To do this:
SQL> set long 1000
SQL> select so_xml from so_operators where so_oper_name='AGENT_NAME';
Example entry prior to FTP reference removal:
ftpConnection="dummyinfo" logFileIntervalTime="5" sessionLogMechanism="2"
<connection value="dummyinfo" xmlName="ftpConnection"/>
Example entry after FTP reference removal:
componentName="InformaticaAgent" connectionTimeout="20" logFileIntervalTime="5"
After completing these two steps, Restart the Informatica Agent.
Please contact Automic Product Support if you have any questions regarding this issue or the Resolution instructions
Was this information helpful?