Informatica support, 24/7

Informatica Support for PowerCenter Domains, Integration Services and IDMC Secure Agents

Informatica support from AceMQ is independent, 24/7 operational cover for PowerCenter and IDMC Secure Agent environments, delivered by AceMQ engineers with partner data-integration specialists. It runs beside your Informatica Global Customer Support contract or without one. Informatica alone supplies patches, product-defect fixes, licences and the cloud service.

24/7 across Americas, EMEA and APAC, with response targets from 15 minutes, by plan, and a written root cause analysis on every P1.

Support quotes answered within 1 hour, by a senior engineer.

Planning a build, upgrade or migration instead? See AceMQ Informatica consulting and services.

160+
Customers supported
10+
Years in production support
40+
Sev 1 incidents handled a year
24/7
Americas, EMEA and APAC
1hour
Quote reply

Customers

  • Microsoft
  • Henry Schein
  • Enbridge
  • Gojek

Partners

  • Broadcom
  • Redis
  • VMware Tanzu
  • OSSeva

Incident Triage

Informatica problems we work every week

Failed workflows, stuck runs, repository and domain problems and Secure Agent faults, each paired with the status, log or command an engineer reads first.

Common Informatica production problems and how AceMQ resolves them
Symptom you're seeingWhat we check firstTypical resolution
A workflow shows Failed and the team asks to recover itThe status in Workflow Monitor or pmcmd getworkflowdetails, then the session and workflow logs. Informatica's documentation says a Failed workflow cannot be recovered, while Suspended, Stopped, Aborted and Terminated ones can (the last three only if the workflow is enabled for recovery). Which targets already committed rows.Choose between a rerun from the start, a task restart and pmcmd recoverworkflow, after a target check so a rerun does not load rows twice.
A recovered session loads duplicate or missing rowsThe session's recovery strategy (a Session task defaults to fail task and continue workflow), whether it was set to resume from the last checkpoint, and whether the source returns the same rows in the same order. A resume needs repeatable data, and the checkpoints sit in $PMStorageDir.Switch the session to restart with a clean target load, or make the source query repeatable; clear stale recovery state.
Workflows sit in Preparing to Run or Waiting when the batch window opensPreparing to Run means the Integration Service is waiting for an execution lock on the workflow; Waiting means it is waiting for resources, such as the limit on concurrent Session and Command tasks per Integration Service process on the node. pmcmd getrunningsessionsdetails and getworkflowdetails, with the run instance name or run ID for concurrent runs.Find the run holding the lock or the limit that is full, then stagger the schedule or raise the limit on purpose.
Workflow Monitor shows Unknown Status, or pmcmd cannot connectpmcmd pingservice and infacmd isp Ping against the Integration Service and its node; whether the service process is running on the node; the resilience timeout, since Workflow Monitor shows Unknown Status when it cannot connect within it (pmcmd waits 180 seconds by default).Restore the service process or node, then set client timeouts that match the measured failover time.
Developers cannot open folders, or pmrep commands failRepository Service status in the Administrator tool; reachability of the repository database; Database Pool Size and Database Connection Timeout in the service properties; whether the service was left in Exclusive mode after maintenance, which admits one user and gives repository clients no resilience.Restore the database connection, size the pool, set a connection timeout that allows the database time to return after a failover, and switch back to Normal mode.
Disk fills on the Integration Service nodeSession log retention (Save Session Log For These Runs, $PMSessionLogCount) and Save Session Log By, since timestamped logs accumulate; and recovery state in $PMStorageDir.Set a retention count that fits the disk, archive what audit needs, and clear recovery state that no longer belongs to a live run.
A node or the domain is down, or services will not startNode status in the Administrator tool; the Logs tab in the Domain and Service views and the message code on each error; the master gateway node, where the Log Manager runs; infacmd isp Ping, ListServices and GetServiceStatus.Bring the gateway node back first, start services in dependency order and confirm each one with GetServiceStatus.
A session that used to finish overnight now runs for hoursThread statistics in the session log: the busy percentage of the reader, transformation and writer threads shows where the time goes. pmcmd getsessionstatistics for the run, and the row counts against last month's.Fix the stage that is busiest: the source query, a transformation cache or the target load, in that order of evidence.
An IDMC Secure Agent is inactive after a start, or tasks fail on one agentinfaagent.log (startup and shutdown) and agentcore.log in the agentcore folder; proxy settings if the host reaches the internet through one; the Windows Event Viewer on Windows hosts. The status refreshes every 5 seconds and can take a few minutes. For task failures, the Data Integration Server tomcat log under apps/Data_Integration_Server/logs/tomcat.Correct the proxy or host fault, restart the agent, and read the Data Integration Server log for the failing task.
A Secure Agent always shows Agent Core Upgrading in Administratoragentcore.log for the error "Authentication failed due to IO error". Informatica's documentation ties it to an agent that missed one or more major upgrades, because automatic upgrade supports only the previous major version. The Details tab shows the agent version.Reregister or reinstall the agent, as Informatica's documentation directs, and add a check so an idle agent does not fall that far behind again.

Every P1 comes with a written cause naming the workflow, service, node or agent involved.

A workflow failed or a service is down? Ask for a quote and an engineer replies within the hour.

Contact Us

Deployment coverage

Which Informatica deployments does AceMQ support, and who covers what?

AceMQ works the operations side: incidents, configuration, runbooks and upgrade planning. Informatica supplies its software, its fixes and its cloud service.

DeploymentWhat AceMQ coversWhat Informatica coversExcluded
PowerCenter domain, nodes and Integration Services24/7 incident response for failed, hung and slow workflows, Integration Service and node problems, session log and recovery settings, runbooks, written RCA on P1sReleases and product-defect fixes under its support planA patched PowerCenter binary
PowerCenter Repository Service and repository databaseService state, database pool and connection timeout, exclusive-mode checks, pmrep backup and a restore rehearsalThe Repository Service softwareDatabase engine faults and storage
IDMC Secure Agents on your hostsInstall, start and status problems, agent logs, proxy settings, runtime environment health, task failures that trace to the agentOperates the IDMC cloud service and ships the agent softwareIDMC service-side faults and org or entitlement changes
Schedules and dependencies outside PowerCenterHow an external scheduler calls pmcmd, exit-code handling, dependency order across schedulersPowerCenter's own scheduler and command-line toolsDefects in a third-party scheduler
Sources, targets and connectionsConnection objects, reader and writer failures, network paths, commit and load behaviorInformatica connectors and PowerExchange as productsFaults inside the source or target system
Upgrades and version movesInventory, rehearsal, change window and rollback plan for an upgrade you chooseInstallers, release notes and upgrade guidanceLicence, entitlement and contract questions, which stay with Informatica
Mappings and transformation logicFinding which mapping a failure traces to and whyProduct behavior and defects in the transformations it shipsRewriting or redesigning mapping logic

Informatica's software, fixes, licences and cloud service stay with Informatica in every row. AceMQ is not an Informatica partner or reseller, issues no patches and gives no licensing advice.

Informatica and independent support

Who provides Informatica support? Informatica Global Customer Support and AceMQ compared

Informatica provides support for its own products through Global Customer Support, in three programs: Basic, Premium and Signature Select Success. AceMQ adds independent operational support for the estate, beside that contract or without it. Only Informatica can fix a defect in its software.

Informatica Global Customer Support
AceMQ independent support
What it coversInformatica products and cloud services you hold support for, including PowerCenter and IDMC
What it coversPowerCenter domains, Integration and Repository Services, IDMC Secure Agents on your hosts, and the schedulers and platforms around them
HoursBasic Success: 8x5. Premium Success: 24x7 for P1 only. Signature Select: 24x7 for all priorities (Informatica success offerings data sheet, read 19 November 2026). Regional teams work Monday to Friday, 9:00 a.m. to 5:30 p.m. local, and support outside those hours is in English only (informatica.com contact page, read 19 November 2026)
Hours24/7 across Americas, EMEA and APAC
P1 responsePremium Success: 1 hour. Signature Select: 15/30 minutes. Basic Success: 2 business days (data sheet, read 19 November 2026)
P1 responseFrom 15 minutes, by plan
P2 responsePremium Success: 4 hours. Signature Select: 2 hours (data sheet, read 19 November 2026)
P2 response1 hour, with P3 at 4 hours and P4 on the next business day
Product defects and fixesInformatica supplies the fix. Prioritized emergency bug fixes and an emergency response team are listed for Signature Select only (data sheet, read 19 November 2026)
Product defects and fixesWe gather the logs, versions and a reproduction for your team to open the case with Informatica, and apply the fix once it ships
Licences and entitlementsInformatica
Licences and entitlementsNot in scope; no licensing advice
IDMC cloud serviceInformatica operates it
IDMC cloud serviceThe agent, your hosts and your side of the connection
Other platforms in the estateInformatica products only
Other platforms in the estateAirflow, NiFi, Spark, Databricks and others under one contract
PriceBasic Success is included with a subscription; Premium and Signature Select prices are not published (data sheet, read 19 November 2026)
Price$24,000 to $72,000 a year (USD), set by SLA, scope and deployment. Quote reply within 1 hour

Figures come from Informatica's published success-offerings data sheet, and your contract governs what you hold. Response time alone is rarely the reason to add an independent contract. The gaps are scope and hours: Premium Success covers P1 only outside local business hours, and a workflow that failed at 02:00 usually needs an engineer who already knows your Integration Service settings, not a defect ticket.

Why AceMQ

What Informatica teams gain from AceMQ

After a failed run

Recover, restart or rerun: how we decide after a failed PowerCenter workflow

The first question on most overnight calls is whether to recover the workflow. Informatica's documentation answers it by status, and the answer changes what has to be checked on the targets.

A Session task defaults to fail task and continue workflow

Informatica lists three task recovery strategies: restart task, fail task and continue workflow, and resume from the last checkpoint. A Session task defaults to fail and continue, so recovery does nothing for a session nobody configured. Resume from the last checkpoint needs repeatable data, and the Integration Service keeps the checkpoints in $PMStorageDir.

Worklets are not recovered, and email can repeat

The Integration Service does not recover a worklet; the session inside it is recovered by expanding the worklet in Workflow Monitor and choosing Recover Task. A restarted Email task might send duplicate email, which matters when it pages a team.

What the call produces

A written decision for each failed task: recover, restart or rerun, with the target check behind it, and a runbook line so the next overnight failure takes minutes. Mapping logic is not changed in an incident.

Recover, restart or rerun: how we decide after a failed PowerCenter workflow
Workflow statusRecoverable, per InformaticaWhat we check before choosing
FailedNo. A failed workflow cannot be recoveredWhich targets committed rows, whether the load truncates or appends, and a rerun plan that cannot double-load
SuspendedYes. Set by the Suspend on Error option when a task fails and nothing else is runningThe cause in the session log, then recoverworkflow or Recover Task once it is fixed
Stopped or AbortedYes, if the workflow is enabled for recoveryWhether it was stopped on purpose, and each session's recovery strategy
TerminatedYes, if the workflow is enabled for recovery. The Integration Service shut down unexpectedlyWhy the service or node went down, before the workflow is touched
Unknown StatusNot a final stateWhether the Integration Service answers a ping; the workflow itself may be fine

Escalation Path

Your first hour of an Informatica outage

A batch window closes on a clock. The engineer on the line starts with the workflow status and the session log, not with questions about what Informatica is.

  1. From 15 min (by plan)first responseEmergencyThe Integration Service or Repository Service is down in the batch window, or every workflow is stuck in Preparing to Run, so no load can start
  2. 1 hourfirst responseCriticalA nightly load failed and was recovered twice with duplicate rows; an IDMC Secure Agent inactive for the runtime environment that carries finance tasks; a node lost from the domain
  3. 4 hoursfirst responseHighSession logs filling a node's disk; one workflow much slower after data growth; a Secure Agent stuck on Agent Core Upgrading
  4. Next Dayfirst responseStandardSession log retention settings, a restart-or-recover runbook, an upgrade planning question

Your plan sets the clock: a stuck production batch is treated differently from a log retention question.

Want an engineer who already knows your Integration Service settings and schedules? Request a quote or contact us.

Contact Us

Pricing

What does AceMQ Informatica support cost?

Informatica support is usually priced from $24,000 to $72,000 a year. The number of domains and Integration Services, PowerCenter versus IDMC Secure Agents, how many workflows run in the batch window and your response plan shape where you fall.

Prices are in US dollars (USD). Response targets start at 15 minutes by plan, 24/7, and quote requests are answered within 1 hour. A contract that also covers other data platforms earns a discount. Informatica licences and Informatica's own support plan are priced by Informatica.

Typical engagements

Typical Informatica support engagements

Two typical Informatica support engagements: what the work covers and what it delivers. They describe the service, not past results.

  • Assessment

    Informatica PowerCenter Health Check Assessment

    Data Platform Team

    A typical engagement for a data team that runs Informatica PowerCenter nightly and has never had the repository, the Integration Service settings, the session logs and the schedules reviewed together: a ranked list of findings, with nothing changed.

    Informatica PowerCenterRepository ServiceIntegration Servicepmcmdpmrep
  • Support

    Informatica Workflow Failure Triage Support

    Data Platform Team

    A typical 24/7 support engagement for failed or hung PowerCenter workflows: a live engineer on the incident, a status-first decision to recover, restart or rerun, a check of what the targets hold, and a written root-cause analysis.

    Informatica PowerCenterIntegration ServiceWorkflow Monitorpmcmd
All use cases

Support options

Four tiers of Informatica support.

AceMQ offers Informatica support in four tiers, each handing more of the day-to-day work to AceMQ: 24/7 support and incident management for PowerCenter domains and IDMC Secure Agents your team runs, proactive reviews that catch log retention, recovery settings and agent drift first, and managed tiers that are scoped per estate in a conversation. Informatica keeps its patches, product-defect fixes, licences and cloud service in every tier.

  • Tier 1

    Informatica 24/7 Support & Incident Management

    Your data team runs Informatica, we assist

    Best for: Teams that run PowerCenter or IDMC Secure Agents themselves and want an engineer reachable for failed workflows and service problems.

  • Tier 2

    Informatica 24/7 Support with Proactive Monitoring

    Planned reviews of repositories, logs and recovery settings

    Best for: Teams that want log retention, recovery strategies and agent versions examined before a failure exposes them.

  • Tier 3

    Managed Informatica on Your Infrastructure

    Scoped per estate in a conversation

    Best for: Enterprises that want AceMQ to run PowerCenter or Secure Agent operations day to day on their own hosts; the scope is agreed on the first call.

  • Tier 4

    Fully Managed Informatica on AceMQ Infrastructure

    Scoped per estate in a conversation

    Best for: Teams that want AceMQ to carry the operational work; whether it applies to an Informatica estate is agreed on the first call.

FAQ

Informatica support questions

Still have questions about Informatica? Email an Expert

Is AceMQ an Informatica partner, and can it open Informatica support cases?

No. AceMQ is not an Informatica partner or reseller, issues no Informatica patches and gives no Informatica licensing advice. Cases are opened by the contacts on your own Informatica contract. We prepare the logs, versions and a reproduction so the case is complete when it is opened, and we apply the fix once Informatica ships it.

Do we still need Informatica support if we hire AceMQ for Informatica?

If you want product-defect fixes or new releases, yes: only Informatica supplies those, and the entitlement is a question for Informatica. AceMQ supports the operations around the product: incidents, configuration, runbooks and upgrade planning. Teams that hold an Informatica plan add us for the hours and the configuration questions it does not cover.

A PowerCenter workflow failed overnight. Can we just recover it?

It depends on the status. Informatica's documentation says a Failed workflow cannot be recovered, while Suspended, Stopped, Aborted and Terminated ones can be (the last three only if the workflow is enabled for recovery). Before anyone recovers or reruns, we check what the targets already hold, so the fix does not load the same rows twice.

Why does our IDMC Secure Agent show inactive or Agent Core Upgrading?

An agent can take a few minutes to start, and a proxy that is set wrongly keeps it inactive; infaagent.log shows startup and shutdown. A permanent Agent Core Upgrading status usually means the agent missed one or more major upgrades, and Informatica's documentation says the fix is to reregister or reinstall it. We read the agent logs first.

What does an Informatica health check include?

The repository, the Integration Service configuration, session and log retention, the history of failed workflows, and a review of schedules and the dependencies between them, with a ranked list of findings. Nothing is changed during the assessment. For migration planning off PowerCenter, see Informatica migration to an open data stack. Quotes are answered within 1 hour.

Can we use AceMQ for Informatica without changing our Informatica contract?

Yes. Many teams keep their Informatica contract and add AceMQ for the gaps, such as overnight workflow failures, recovery decisions or advice across several data platforms. AceMQ gives no licensing advice and issues no patches. You can also hire us for one piece of work, like a health check, with no annual commitment.

What drives the price of Informatica support?

Annual contracts typically run $24,000 to $72,000 (USD). Inputs are the number of PowerCenter domains and Integration Services, whether IDMC Secure Agents are in scope, the size of the nightly batch and your response plan. Describe the estate in a quote request and we respond within 1 hour. Informatica's own plan is bought from Informatica.

Let's talk

Know Whether to Recover, Restart or Rerun Before the Batch Window Closes

Send us your PowerCenter or IDMC versions, how workflows are scheduled and the workflows that carry your critical loads. We reply to quote requests within 1 hour.

A senior Informatica engineer, not a sales queueQuote requests answered within 1 hourAd hoc engagements or an annual partnership

Production incident right now?Email an Informatica Architect