Cisco Support Community
Showing results for 
Search instead for 
Did you mean: 

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. If you'd prefer to explore, try our test area to get started. And see here for current known issues.

aupair.exe pegged cpu on subscriber?

Anyone see this before and why is pegging my cpu?

ccm 4.1.3



Re: aupair.exe pegged cpu on subscriber?

Do you get any DCOM errors in event viewer ?

Have you tried restarting DBlayer monitor service ? (which is aupair)

Re: aupair.exe pegged cpu on subscriber?

no dcom errors.. from what I can find in google, it is linked directly to the sql database.

DBlayer? is this ok to restart during production hours?

Re: aupair.exe pegged cpu on subscriber?

I wouldnt recommend restarting it during production hours. Try doing it after hours..


Re: aupair.exe pegged cpu on subscriber?

Hi T,

What is your exact CCM version?

OS version?

The Cisco Database Layer Monitor service (aupair.exe) monitors aspects of the database layer as well as call detail records (CDR). The database layer comprises a set of dynamic link libraries (DLL) that provide a common access point for applications that need to access the database to add, retrieve, and change data. The Cisco Database Layer Monitor service performs functions such as determining whether the primary server is available during failover, deleting the oldest CDRs when the limit that is defined in the MaxCDRecords parameter is reached, and moving CDRs from a subscriber to the primary database at a given interval, if needed.

1. Please check that you have correct CDR settings on CCMAdmin Enterprise parameter page, it could be that aupair.exe stuck in a loop moving CDR's to the incorrect/un-existent destination.

2. Please set up and collect DETAILED DBL traces. Please refer to the following URL for detailed information on how to setup Callmanager traces:

DBL traces are usually available under following location: C:\Program Files\Cisco\Trace\DBL

3. Setup following perfmon counters

( and run for about 3 minutes while the symptom is present:

1) Process(Aupair)\ID Process

2) Process(Aupair)\% Processor Time

3) Process(_total)\% Processor Time

4) Process(Aupair)\Private Bytes

5) Process(_total)\Private Bytes

6) Process(Aupair)\Thread Count

7) Process(_total)\Thread Count

8) Process(Aupair)\Virtual Bytes

9) Process(_total)\Virtual Bytes

10) Process(Aupair)\Virtual Bytes Peak

11) Process(_total)\Virtual Bytes Peak

12) Process(Aupair)\Working Set

13) Process(_total)\Working Set

14) Process(Aupair)\Page Faults/sec

15) Process(_total)\Page Faults/sec

16) Thread(Aupair/ - all threads)\% Processor Time

17) Thread(Aupair/ - all threads)\ID Thread

18) Thread(Aupair/ - all threads)\Start Address

19) Thread(Aupair/ - all threads)\Priority Current

20) Thread(Aupair/ - all threads)\Thread State

21) Thread(Aupair/ - all threads)\Context Switches/Sec

22) Thread(Aupair/ - all threads)\Elapsed Time

4. Make sure CDRInsert is running only in the PUB, SQL services and Jobs.

5. Collect Application logs, DBL traces and perfmon counters- After logs are collected, please go ahead and restart the aupair.exe service to see if it changes the issue. If not I would open a TAC case for checking it deeper.