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 the 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 troubleshoot the Carte server failing to start due to missing or conflicting JARs

The Carte server might not start after deployment because the classpath does not include the required log4j JAR files. When this happens, Atrium Integrator jobs fail with ARERR 8753, and the diserver process terminates during initialization.

To resolve this issue, update the Carte process to include the required log4j JARs in the classpath.

1. Log in to the default platform-fts pod where the Carte server is running. 
2. Open the /opt/bmc/ARsystem/conf/armonitor.conf, carte startup configuration file.
3. Add the following JARs to the classpath:
   • /opt/bmc/ARSystem/diserver/data-integration/lib/log4j-core-2.24.1.jar
   • /opt/bmc/ARSystem/diserver/data-integration/lib/log4j-api-2.24.1.jar
4. Save the file and restart the Carte (diserver) process.  
5. Run the Atrium Integrator job again to verify successful job.
   If the platform pods restart, apply this update again to ensure the Carte server starts correctly.

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

Atrium Integrator jobs may not run according to schedule when the primary server is unavailable. To avoid this, you must update server connections to support automatic failover.

To support automatic failover for Atrium Integrator jobs, you must perform the following steps:

1. In the Atrium core, navigate to the UDM:RAppPassword form

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

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

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

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

5. 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