CDR error 40042 Migration is running, so you cant generate any of the report.

[tony199919]

I`m currently facing a issue regarding pulling cdr reports after a upgrade fro Call Manager 8.5.2 to Call Manager 8.6, i get the error 40042 looks like CDR migration is happening of some sort and just keep on getting the error, has anyone got an idea how i can fix this as we need to generate reports...

Sent from Cisco Technical Support iPad App

[gnanem]

Hi Tony,

Look like you are hitting the bug CSCtt17946 and this fixed in 8.6.2.

http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&bugId=CSCtt17946

Regards,

Gnaneswaran.M

[tony199919]

Thanks for the quick reply, excellent looks like the problem will try resolution...

Thanks a mill

Sent from Cisco Technical Support iPad App

[binu.john]

Hi Gnaneswaran,

Iam also facing the same issue, my CUCM version is 8.6.1(20000-1). I would like to know is there any workaround to fix this issue, rather going for an SR Upgrade?

Thanks

John

[tony199919]

Hi thanks, i got the issue resolved with following the workaround in the bug document, we will also be upgrading the cluster soon to prevent any further issues regarding this...

Sent from Cisco Technical Support iPad App

[binu.john]

Hi Tony,

I had done upgrade for my CUCM to 8.6.2 SU2, and the issue is got resolved.

[sajish kumar Ramakrishanan]

I do have this issue on the 8.6.2 SU2 as well...any one know how to fix this issue.

I tried re-stating the services...but no luck.

Regards,

Sajish

[binu.john]

For me issue happened after my upgrade from 6.1 to 8.6.2a, knowing its a bug, i done an SR upgrade to 8.6.2.22900(9)

and the issue got fixed.

rgds

Binu John

[sajish kumar Ramakrishanan]

Binu,

Thanks for your response.

Is there any other Work around for this issue, i have CUCM 8.6.2.21900-5 running.

Regards,

Sajish

[binu.john]

Sajish,

There is a workaround which is (posted above), Infact i didnt tried that. I done the upgrade since i was also had other issues on my CUCM, moreover 8.6.2.22900(9) looks very stable.

Take care.

Binu

[jassenlogo]

I'm running 8.6.2.22900-9 and I'm getting hitting this bug as well.  Performed upgrade mid-october from 8.5.1.  I'm creating a TAC case to see what they say.

[jassenlogo · Accepted solution]

Here's TAC response:

TAC CASE# 623934773

Problem Description :

-----------------------------

After the upgrade from 8.5.1 to 8.6.2, the system encountered 
the defect : CSCtt17946. In this defect, the CDR data gets 
stuck in a migration phase and is not pushed to the DB  for CAR 
and thus cannot be accessed. The defect lists that the version 
we are running should have this fixed. 

However, as we saw that was not the case. 

Resolution Summary:

-----------------------------

Instead of following the workaround for the defect, which lists 
that we move the data from the migration file to the DB, in this 
case we had to delete the Migration file to get that going. 

The Exact steps followed were:

Set 'CAR Scheduler logs' at 'DEBUG' level. Empty the 'marker' file 

i.e. delete the 

'marker' file (present at '/usr/local/cm/db/car/migration' ) 

and then RESTART 'CAR 

Scheduler Service.'

If migration fails still then contact CAR team with Scheduler 
logs and 'migration_status.log' file.

[Rob Huffman]

Hi Jassen,

Thanks for updating this thread with your TAC resolution +5

Would you mind linking the TAC case# for reference just in case

someone else hits this.

Cheers!

Rob

"And if I should fall behind
Wait for me" - Springsteen

[jassenlogo]

The TAC Case# is 623934773

[Rob Huffman]

Thanks my friend +5

Cheers!

Rob

"And if I should fall behind
Wait for me" - Springsteen