Unable to run CDR reports after upgrade due to "Migration in progress"

Unanswered Question
Mar 20th, 2012

 Hello,


 


We are unable to run CDR reports.  When we try, a window pops up saying "Migration in Progress".  This issue is documented in CSCtt17946 Bug.  I'm not sure how to apply the workaround.  From what I get, we need to enter commands in CLI.  I've tried different variations of the commands provided.  If anyone has encountered this issue or know how to apply the workaround please let me know.


 


Thanks,


 

<TABLE style="PADDING-BOTTOM: 10px" border=0 cellSpacing=0 cellPadding=0 width="100%" mcestyle="padding-bottom: 10px;">



CSCtt17946 Bug Details

<TH style="PADDING-LEFT: 10px; COLOR: #666666; FONT-WEIGHT: normal; BORDER-RIGHT: #cccccc 1px solid" align=right mcestyle="padding-left: 10px; color: #666666; font-weight: normal; border-right: #cccccc 1px solid;">Bug #21 of 30 | &lt; <A style="FONT-SIZE: 100%" href="http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&bugId=CSCts89659&from=summary" mcehref="http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&bugId=CSCts89659&from=summary" mcestyle="font-size: 100%;">Previous</A> | <A style="FONT-SIZE: 100%" href="http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&bugId=CSCtt31632&from=summary" mcehref="http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&bugId=CSCtt31632&from=summary" mcestyle="font-size: 100%;">Next<!--

.showForJs.showInlineForJs.hideForJs

--></mce:style>

<STYLE mcebogus="1"><!--

.showForJs.showInlineForJs.hideForJs

-->



<TD style="PADDING-BOTTOM: 8px; PADDING-LEFT: 8px; PADDING-RIGHT: 8px; FONT-SIZE: 88%; PADDING-TOP: 8px" colSpan=2 mcestyle="font-size: 88%; padding: 8px;">Unable to run CDR reports after upgrade due to "Migration in progress"

<TD style="PADDING-BOTTOM: 8px; PADDING-LEFT: 8px; PADDING-RIGHT: 8px; FONT-SIZE: 88%" vAlign=top mcestyle="padding-bottom: 8px; padding-left: 8px; padding-right: 8px; font-size: 88%;">Symptom:

<BR type="_moz" mozdirty>

Unable to generate CDR reports after upgrade to 8.6.1.20000-1. The following
message is observed after logging into CAR tool:

<BR type="_moz" mozdirty>

"Migration in progress"

<BR type="_moz" mozdirty>

Conditions:

<BR type="_moz" mozdirty>

Problem is intermittent.
Problem has only been known to occur after an upgrade to CUCM 8.6.1
Fresh installs of CUCM 8.6.1 do not experience this issue.

<BR type="_moz" mozdirty>


Additional Notes

<BR type="_moz" mozdirty>

The issue is under investigation. To facilitate further investigation, please
collect CAR Scheduler traces (set to 'Debug' trace level) that cover the
timeframe of migration.

<BR type="_moz" mozdirty>


<BR type="_moz" mozdirty>

< Workaround>

<BR type="_moz" mozdirty></P>***It is recommended that you do not use PUTTY to execute the workaround <BR>steps. PUTTY can truncate some lines.***

<BR type="_moz" mozdirty>

i) Check if 'migration_status.log' file is present at '/common/log'.
ii) Check if there is any data in 'tbl_generated_report.csv' present at

<BR type="_moz" mozdirty>

'/usr/local/cm/db/car/migration'.

<BR type="_moz" mozdirty>


<BR type="_moz" mozdirty>


Condition 1 :

<BR type="_moz" mozdirty>

If 'migration_status.log' IS PRESENT and NO data is there in
'tbl_generated_report.csv'

<BR type="_moz" mozdirty>

(present at '/usr/local/cm/db/car/migration') i.e. 'tbl_generated_report.csv'
does not

<BR type="_moz" mozdirty>

contain any data apart from th column names, then follow the below workaround.

<BR type="_moz" mozdirty>

Workaround - Set 'CAR Scheduler logs' at 'DEBUG' level. Empty the 'marker' file
i.e. delete the

<BR type="_moz" mozdirty>

contents of the 'marker' file (present at '/usr/local/cm/db/car/migration' )
and then RESTART 'CAR

<BR type="_moz" mozdirty>

Scheduler Service.'

<BR type="_moz" mozdirty>

If migration fails still then contact CAR team with Scheduler logs and

<BR type="_moz" mozdirty>

'migration_status.log' file.

<BR type="_moz" mozdirty>


<BR type="_moz" mozdirty>


<BR type="_moz" mozdirty>


Condition 2 :

<BR type="_moz" mozdirty>

If 'migration_status.log' is NOT present then first we have to create this log
file at

<BR type="_moz" mozdirty>

'/common/log' location and give it write permissions.

<BR type="_moz" mozdirty>

If there is NO data is there in 'tbl_generated_report.csv' (present at

<BR type="_moz" mozdirty>

'/usr/local/cm/db/car/migration') i.e. 'tbl_generated_report.csv' does not
contain any

<BR type="_moz" mozdirty>

data apart from th column names, then follow the below workaround.

<BR type="_moz" mozdirty>

Workaround - Set 'CAR Scheduler logs' at 'DEBUG' level. Empty the 'marker' file
i.e. delete the

<BR type="_moz" mozdirty>

contents of the 'marker' file (present at '/usr/local/cm/db/car/migration' )
and then RESTART 'CAR

<BR type="_moz" mozdirty>

Scheduler Service.'

<BR type="_moz" mozdirty>

If migration fails still then contact CAR team with Scheduler logs and

<BR type="_moz" mozdirty>

'migration_status.log' file.

<BR type="_moz" mozdirty>


<BR type="_moz" mozdirty>


<BR type="_moz" mozdirty>

Condition 3 :

<BR type="_moz" mozdirty>

If 'migration_status.log' file is not present then we have to create it else
not.

<BR type="_moz" mozdirty>

If there is data in 'tbl_generated_report.csv' (present at

<BR type="_moz" mozdirty>

'/usr/local/cm/db/car/migration') then we have to manually load this data in
CAR DB using

<BR type="_moz" mozdirty>

informix's 'load' command.
Copy this csv to '/' path. Remove the rows which indicate column names. There
should be only data in
that csv (present at '/' path). For ex. consider lets say below is the content
of this csv file.

<BR type="_moz" mozdirty>

[root@machine]# cat tbl_generated_report.csv
seq_id,repname,reportdate,expected_date_of_deletion,
serial ,varchar(32) ,date ,date ,
1,DailyTrafficSummary,05/01/2008,08/01/2008,
2,GatewaySummaryReport,05/01/2008,08/01/2008,

<BR type="_moz" mozdirty>

Here the first 2 rows are column names. We can delete these rows by putting
cursor in first row and
pressing 'dd'. Same way for second row. After removing rows of column names,
there would only be
data in that csv. Below are the content for the above csv after deleting rows
for column names.

<BR type="_moz" mozdirty>

[root@machine]# cat tbl_generated_report.csv
1,DailyTrafficSummary,05/01/2008,08/01/2008,
2,GatewaySummaryReport,05/01/2008,08/01/2008,

<BR type="_moz" mozdirty>


Now, we have to load this to CAR DB. For this, we have to go to CAR DB.
Following steps are there to
go to CAR DB.
a) source /usr/local/cm/db/informix/local/carect 'New'. There we need to run this
command.

<BR type="_moz" mozdirty>

Run this informix command.
load from /tbl_generated_report.csv delimiter ',' insert into
tbl_generated_report

<BR type="_moz" mozdirty>

After this command executed successfully, in the bottom we should be able to
see that 'x' number of
data loaded.
Now, we can delete the csv present at '/' path containing data only.

<BR type="_moz" mozdirty>

Now as the data for this table is loaded, we need to delete the content of csv
file from
'/usr/local/cm/db/car/migration' as the content has already been loaded.

<BR type="_moz" mozdirty>

While deleting few rows would be indicating the column names. We have to make
sure that we

<BR type="_moz" mozdirty>

delete data only, NOT the rows of columns names. For deleting rows containing
data, same steps

<BR type="_moz" mozdirty>

can be executed as explained above accordingly.

<BR type="_moz" mozdirty>


<BR type="_moz" mozdirty>

Finally, again the same procedure -- Set 'CAR Scheduler logs' at 'DEBUG' level.
Empty the 'marker'

<BR type="_moz" mozdirty>

file i.e. delete the contents of the 'marker' file (present at
'/usr/local/cm/db/car/migration' ) and then

<BR type="_moz" mozdirty>

RESTART 'CAR Scheduler Service.'

<BR type="_moz" mozdirty>

If migration fails still then contact CAR team with Scheduler logs and

<BR type="_moz" mozdirty>

'migration_status.log' file.

<BR type="_moz" mozdirty>


<BR type="_moz" mozdirty>


<BR type="_moz" mozdirty>

This process will start migration of records. This will take 20-30 mins to
start the process. Migration
of records can be verified by going to 'System ->Database -> Manual Purge ->
Table Information'.
There the number of records should be increasing.
Time while migrating the data completely depends on the size of the csv files
(data remaining from
previous version). We have seen cases where it can take from 30 minutes to more
than 10 hours.
Migration of data for each table will be recorded in 'migration_status.log'
file. After the migration gets
completed , we can see 'Completion' message in this file. And after that if we
login to CAR, we should
be able to see 'migration complete' message in the pop up.

<BR type="_moz" mozdirty>


 


 


 


 

I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Average Rating: 0 (0 ratings)
Turion307 Fri, 03/23/2012 - 12:38

Issue has been resolved.  Access to the root is necessary wich only Cisco has.  I opened up a TAC case and the engineer was able to implement workaround.

Nelsonmejia09 Thu, 05/24/2012 - 15:25

Hi Ayaz Khan, i have the same issue.

I have upgrated CUCM from 7.1.5 to 8.6.1.20000-1, after that i can´t run CDR reports.

I hahe the following questions?

- how can i get root access to CUCM, or it is not possible.

- this issue is fix it if I upgrade from 8.6.1.20000-1 to 8.6(2.22024.1).

- is necesary to open a Cisco TAC Case to fix the issue?.

Joe Martini Thu, 05/24/2012 - 16:10

Only TAC has access to root on CUCM.  An update will not fix the problem, the workaround has to be done.  Yes please open a TAC case to have this fixed.  Thank you.

joshua.gertig Thu, 07/19/2012 - 10:40

Just to add, it looks like we've hit this bug after upgrading to 8.6.2.21900-5.

We use a third party call-accounting server and CDR records seem be going through just fine. I didn't notice until I tried to run a manual cdr search in cucm

Actions

Login or Register to take actions

This Discussion

Posted March 20, 2012 at 7:55 AM
Stats:
Replies:6 Avg. Rating:
Views:1148 Votes:0
Shares:0
Tags: No tags.

Discussions Leaderboard

Rank Username Points
1 21,026
2 15,047
3 10,314
4 7,999
5 4,856
Rank Username Points
140
95
72
66
55