Troubleshooting data transfer issues

When you encounter issues while transferring data in Atrium Integrator, use the following information to resolve the issue.

To create data store connection with an Oracle service name

Prefix your database name with slash (/) when you open the database connection in Atrium Integrator Console.

Alternatively, you can perform the following steps:

1. Create a new data store connection for Oracle database in Atrium Integrator Spoon.  
2. To work with SERVICE_NAME instead of Oracle SID:
   • In the Access list, select Native (JDBC).
   • Leave the Host Name field and the Port Number field blank.
   • Enter service description in the Database Name field.
     For example, 
     (DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(HOST=PRIMARY_NODE_HOSTNAME)(PORT=1521))(ADDRESS=(PROTOCOL=TCP)(HOST=SECONDARY_NODE_HOSTNAME)(PORT=1521))) (CONNECT_DATA=(SERVICE_NAME=DATABASE_SERVICENAME)))
3. Enter DB Username and Password. 
4. Click OK. 

To troubleshoot data population on a remote Atrium Integrator carte server

CSV or XML data may not get populated with remote Atrium Integrator carte server due to the following reasons:

• Job_FileMetaLoader is not started. To troubleshoot, see Troubleshooting-jobs-running-in-the-Atrium-Integrator-console. 
• Source files are not present on the configured server.

To resolve Atrium Integrator jobs not failing over to the secondary server

Some Atrium Integrator jobs might not run according to schedule when the primary server becomes unavailable because the server connections used in the jobs do not support automatic failover.

1. Identify database connections that reference the following fixed server names:

   • platform-fts-0
   • platform-admin-0

   • platform-admin-ext

2. Replace these server names with platform-fts-ext.
   
   
   The platform-fts-ext endpoint automatically routes the connection to any available fts pod, ensuring high-availability and enabling failover.

3. If platform-fts-ext is missing from the UDM:RAppPassword form, create the entry manually.

4. Save the job and rerun your scheduled execution.

Related topics

Transferring data from external data stores to BMC Helix CMDB 

Best practices when configuring Atrium Integrator