060814  3:52:28  InnoDB: Page checksum 1609278306, prior-to-4.0.14-form checksum 2224417534
InnoDB: stored checksum 1282737563, prior-to-4.0.14-form stored checksum 2224417534
InnoDB: Page lsn 56 1568513452, low 4 bytes of lsn at page end 1568513452
InnoDB: Page number (if stored to page already) 67259,
InnoDB: space id (if created with >= MySQL-4.1.1 and stored already) 362
InnoDB: Page may be an index page where index id is 0 1291
InnoDB: (index schedule_detail_idx1 of table ccms/schedule_detail)
060814  3:52:28InnoDB: rec offset 99, cur1 offset 9937, cur2 offset 15970
060814  3:52:28InnoDB: Assertion failure in thread 2117860272 in file page0page.c line 519
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: http://dev.mysql.com/doc/mysql/en/Forcing_recovery.html
InnoDB: about forcing recovery.
mysqld got signal 11;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.
We will try our best to scrape up some info that will hopefully help diagnose
the problem, but since we have already crashed, something is definitely wrong
and this may fail.

key_buffer_size=8388608
read_buffer_size=258048
max_used_connections=4
max_connections=510
threads_connected=1
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 658948 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

thd=(nil)
Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
terribly wrong...
Cannot determine thread, fp=0x7e3be8ac, backtrace may not be correct.
Stack range sanity check OK, backtrace follows:
0x817b8f2
0x306888
0x314e
0x82e0dcf
0x82bb620
0x82bc8bb
0x8310a18
0x8337009
0x82a085a
0x300371
0xcd29be
New value of fp=(nil) failed sanity check, terminating stack trace!
Please read http://dev.mysql.com/doc/mysql/en/Using_stack_trace.html and follow instructions on how to resolve the stack trace. Resolved
stack trace is much more helpful in diagnosing the problem, so please do
resolve it
The manual page at http://www.mysql.com/doc/en/Crashing.html contains
information that should help you find out what is causing the crash.
Writing a core file