ICal Corrupt Database

I think my iCal database or to be specific, the todo's, has become corrupted. Initially it wasn't showing any todo's. I checked my Entourage and Palm and they show 71 todo's (I sync these). I did a database backup then restore and now 51 todo's show. However strangely, if I search for the ones missing they show in the search. From what I can make out, the only way to fix a corrupted iCal DB is to delete its folder. I could then sync everything back from Entourage but that takes hours. I do have daily backups and am wondering if I revert to a backup if that might be sufficient. However I'm not sure if it would throw out all my sync'd systems. Any thoughts/suggestions.

John,
I managed to fix it. I simply rebooted in Safe Mode as I figured this would rebuild the font cache. Which it did, or at least it did something as both iCal and iPhoto are now working fine again.
Thanks for your help!
All best,
Hunter
PS Anyone else with this problem? Here's how to reboot in Safe Mode: http://support.apple.com/kb/HT1455

Similar Messages

Possible Corrupt Database?

I've been synching my Palm Treo 700p, iCal, and Entourage calendars on my MacBookPro, OS 10.4.8, and I think I may have a corrupt database. All the calendars have been set to delete events/meetings more than one year old, and none show any events earlier than one year ago, yet iSync keeps coming up and telling me I have hundreds of synch conflicts (most from 2004 and 2005). Can I delete the database without losing everything currently in my calendars? If so, which database do I delete?
Thanks,
Claude

You cannot delete anything without forcing a corresponding deletion of matching records elsewhere on all of your applications, devices and servers.
Given your brief description, it's likely that Entourage is the culprit. Isolate it from the remainder of your synchronization pool by temporarily disabling its connection to Sync Services, and see if the conflicts disappear. By reconfiguring sync clients, but not deleting sync records, you should be able to determine what is driving this conflict resolution process. Only by temporarily disabling or reconfiguring devices can you isolate the issue and resolve it.

Corrupted Database Problem

Greetings,
I'm getting the following error running the base system installer:
root@archiso ~ # pacstrap -i /mnt base
==> Creating install root at /mnt
==> Installing packages to /mnt
error: GPGME error: No data
:: Synchronizing package databases..
core is up to date
extra is up to date
community is up to date
error: database 'extra' is not valid (invalid or corrupted database (PGP signature))
==> ERROR: Failed to install packages to new root
I've already tried updating the keyring:
pacman-key --init && pacman-key --populate archlinux
As well as changing around the mirrors in my mirrorlist and re-syncing with:
pacman -Syy
Running out of ideas and been scowering Google for an hour now with no result. Any help is appreciated. Cheers.

bjornoslav wrote:Check the system time. Incorrect time and date cause problems with pacman because it can't verify the GPG keys properly.
System time is fine.
Also tried deleting the extra DB file, same error persists.

Replay logfiles on corrupt database

I've got a machine here that has not been maintained very well. Someone with little knowledge of MaxDB has only kept Windows backups and no database backups. Also, there has been no LOG backups, everytime the log was full, someone just added another one :). Now one of the DATAvolumes is corrupt (it shows 0 kb) and the database won't come up. Everyone here is convinced that it won't come up ever again. Also, on top of all, the Windows backups aren't available anymore either. People feel sorry for it and just move on
So now I've got some spare time and I want to take a closer look at it. I've got a corrupt database, and I've got a lot of LOG volumes (not backups). I'm not a MaxDB guru either, so I've got the following questions:
Isn't it true that if you do not backup the database or the logfiles at all, all the database transactions committed after the installation still reside in the logfile(s)?
With this in mind, couldn't it be possible to install the system just as it was right after the installation, and after that replay the existing logfiles? I've created a copy of the system where I can fool around. I've found lots of ways to recover a database with logbackups, but not with the logfiles itself.
Isn't there anything I can do at all with the existing logfiles, with all the precious data in it? It has been a portal and there are (or were ) a lot of documents in it.
Who can help me out?

>Only thing is that the general idea was to build it again (by installing the system again) and replay all the later on added information (by replaying the existing logfiles).
>I still find it strange that in fact all the data is there ( in the logfiles), but I cannot get to it.
>Or I'm misinterpreting the whole logfile mechanism.
Well - half and half I'd say.
It's true, all changes to the database are logged to the log area.
BUT (yes, a big BUT here), the critical point here is the starting point.
To have all changes correctly applied, the database must be sure that the database is really in the exact state like it was, when the log information starts.
This synchronization is done via the restart_record and the log_info_page.
In theory, if we would be able to generate a completely identical data area as it was, back then, when the history of log information began, then we would be able to recover the data.
Just creating a new database won't do, since the db_create itself is not covered by redologs and ends up with a different data area each time (e.g. for each database a DB-Identifier with the timestamp of its creation is generated and saved).
So, technically the only way I can think of would be to create a empty data area and than hack into the restart_record to fake the MaxDB into a recovery.
If you are a MaxDB kernel developer you might be able to do that...
regards,
Lars

BerkeleyDB hangs trying to read corrupted database

The provided corrupted database file causes reproducible hang in db->get method of Berkeley DB.
Reproduced with Berkeley DB 4.8.30 and 4.3.29 under Linux.
Corrupted database file: https://cfengine.com/bugtracker/file_download.php?file_id=123&type=bug
Testcase:
#include <db.h>
int main()
DB *dbp;
DBT key, value;
key.data = "x86_64";
key.size = 6;
db_create(&dbp, NULL, 0);
dbp->open(dbp, NULL, "bdbtest.db", NULL, DB_BTREE, 0, 0644);
dbp->get(dbp, NULL, &key, &value, 0);
return 0;
gdb backtrace:
(gdb) bt
#0 __memp_fget (dbmfp=0x602120, pgnoaddr=0x7fffffffe2ec, ip=<value optimized out>, txn=0x0,
flags=<value optimized out>, addrp=<value optimized out>) at ../dist/../mp/mp_fget.c:293
#1 0x00007ffff7aa94dc in __bam_search (dbc=0x603880, root_pgno=<value optimized out>,
key=<value optimized out>, flags=<value optimized out>, slevel=<value optimized out>,
recnop=<value optimized out>, exactp=0x7fffffffe41c) at ../dist/../btree/bt_search.c:753
#2 0x00007ffff7a967a6 in __bamc_search (dbc=0x603880, root_pgno=<value optimized out>,
key=<value optimized out>, flags=27, exactp=<value optimized out>)
at ../dist/../btree/bt_cursor.c:2785
#3 0x00007ffff7a98027 in __bamc_get (dbc=0x603880, key=<value optimized out>, data=0x7fffffffe5d0,
flags=27, pgnop=<value optimized out>) at ../dist/../btree/bt_cursor.c:1088
#4 0x00007ffff7b3e27f in __dbc_iget (dbc=0x0, key=<value optimized out>, data=0x7fffffffe5d0,
flags=27) at ../dist/../db/db_cam.c:934
#5 0x00007ffff7b4b250 in __db_get (dbp=<value optimized out>, ip=<value optimized out>,
txn=<value optimized out>, key=0x7fffffffe600, data=0x7fffffffe5d0, flags=27)
at ../dist/../db/db_iface.c:779
#6 0x00007ffff7b4b57b in __db_get_pp (dbp=0x601a60, txn=0x0, key=0x7fffffffe600,
data=0x7fffffffe5d0, flags=0) at ../dist/../db/db_iface.c:694
#7 0x00000000004005df in main () at bdbtest.c:13
--------

Hi,
Your database is corrupted, hence there is no surprise you cannot retrieve successfully from it:
# db_verify -o cf_classes.db.duff
db_verify: Page 4: btree or recno page is of inappropriate type 0
db_verify: Page 4: totally zeroed page
db_verify: Page 4: Btree level incorrect: got 0, expected 1
db_verify: Page 3: unterminated leaf chain
db_verify: cf_classes.db.duff: DB_VERIFY_BAD: Database verification failed
Verification of cf_classes.db.duff failed.
Dumping the database with db_dump -da shows the following where page 4 should have been:
page 0: invalid: LSN [0][0]: level 0
prev: 0 next: 0 entries: 0 offset: 0
and a verification with a hex editor over the 4KB's of page 4, shows that this page is all 0s (zeros).
You need to run recovery over this database. For backup and recovery procedures review the followings:
- chapter 11 in the Berkeley DB Reference Guide, Berkeley DB Transactional Data Store Applications;
- in the Getting Started with Berkeley DB Transaction Processing, the sections on Backup Procedures and Recovery Procedures.
If your application is not using transactions (it is not set up as TDS, Transactional Data Store), you should review the section on Handling failure in Data Store and Concurrent Data Store applications.
Regards,
Andrei

Corrupted Database in Lightroom 3 Beta

Can anyone offer any help how to recover from a "corrupted
database" error on startup? It gives an option to repair, but it is unsuccessful. I was one who disregarded al the warnings about not using the beta for production, but I liked it so much that I just completed a huge wedding. Luckily, all my chosen files were exported as Jpegs but I have lost many, many hours of work. I also have LR2 which I had always used previously.

Try your catalog back up file, just click to open the most recent and hopefully that will work and as long as you made regular back ups you should be OK. If all else fails import the files into a new catalog using the Beta and then update the files from the metadata (this will obviously only work if you save out the metadata. You can also do the same with LR 2 although if you used the new process version in LR 3 this will be lost.
Using a Beat for production work is not a good idea, but at least if you backed up catalogs and wrote data out as xmp side car or directly to file if you converted to DNG you can always recover. If you did none of these things and used a Beta then you really are in trouble!

New mail messages not visible--"detected corrupt database" related?

I am using Mail.app and an iPod Touch with an Exchange server (Intermedia). All of a sudden in the last few days, recent mail on the server is not visible using Mail.app or the iPod Touch. I have deleted the mail accounts on both devices twice and done an entirely fresh download of all mail on both, and the problem persists.
Mail in the Inbox is visible. However, if I move an Inbox message to, say, Archive or Travel, then it becomes invisible--even though it is intact on the server and in its proper location there.
I have also repaired permissions and run sudo daily/weekly/monthly maintenance processes, to no avail.
In the console, I see the following error message. Could this be related and is there a way to fix it?
Jul 17 11:14:36 xxx-xxxx-macbook Mail[108]: ISyncDataDirectoryCorruptedException: detected corrupt database while executing delete from Record
Thanks for any help.
Message was edited by: RKNYC

Update: all messages are viewable in Entourage Exchange Web Services 2008, but not in Apple Mail, or in Mail on my iPod Touch, or after a new download of all mail on another Mac in Mail.app. Why is Entourage able to see all the messages while all the Apple Mail clients are missing them?

DBF corrupted database

Hey friends, I'm in great trouble here.
I'm using Microsoft Visual FoxPro 9.0 on my Windows 7 machine. I had some DBF files which was created in MS Visual FoxPro. The files were undoubtedly valuable since they contained my crucial data related to my office work. The files are now invalid
therefore, inaccessible. I can't access any of my database files. Whenever I try to open one of them this comes in front of me: "File filename.dbf does not exist".
According to me this must be a file corruption error states the file is corrupted. I don't know how did it get corrupted. I'm dying to get these files back. Please help in this.
Thanks in advance.

It is not necessary to rebuild a corrupt database. All corrupt databases can fixed in less than one minute.
The solution is: Open database to main screen
Copy the database but only one record(just pick a not recent record number at random; include "all", I usually name this database "FixMMDD" (( month Day))
Open original database to mainscreen and append the FIXMMDD.dbf.
You're done.
Occassionally you may have to update indexes. Very rarely are any records lost and when it happens those few records are clearly garbled.
I've been doing this for three years with no problems.
If you have fields that increment you'll have to adjust that for your last valid value.
OTHERWISE
I think those files of your which seem unreadable are corrupt. Just one thing always keep in your mind that corruption can make a file unreadable or useless. And due to this file becomes inaccessible. Any corrupt or damaged file can't be accessed
until it gets fully repaired. All you need just remove the error from your DBF files and after doing this you can access those corrupt files. The data inside those files will be readable right after you repair them. You just need to consider
about a software program or shall I suggest you about a tool which I have used?
Check this one: DBF Repair Kit
It will help you as it helped me. Just try its demo version
http://www.dbf.repair/ to see the preview of the content of the files which are unreadable.

Is there any way to restore or rebuild a corrupted database?

I'm trying to get information from a database, but it's corrupted and not allowing me to see any availbable traces. If there any way to restore or rebuild a corrupted database?
Solved!
Go to Solution.

Here are a few screen captures of what I'm looking at. The 3rd capture is of the files making up the database.
Attachments:
max_screen_capture.JPG ‏71 KB
max_screen_capture2.JPG ‏67 KB
max_screen_capture3.JPG ‏142 KB

Python + Miro from testing lead to corrupted database

This update today was a killer. Miro just blew up and took all my channel metadata along with it to the tune of 'corrupted database'.
It doesn't work even when I delete the .miro folder from my home. The thing errors out when I try to close it and stays open...
OT: I've had a fair share of problems with Miro so I think it's time to look for something less bloated and less fragile. Any ideas?

user3006396 wrote:
Hi Experts,
On one of the servers with Windows Server 2008, we have 5 Oracle 11g databases installed for our dev & testing environments.
With the help of oracle client we are connecting to those server db's.
Last Friday,for one of the db's, I have populated a million records to few tables and everything was fine on that day.
Suddenly on this Monday, one of the front-end users complained that the db was not working. We are not able to connect to that db, but able to connect to one of the other db's on the same server.
Message thrown was :
" ORA-12514: TNS:listener does not currently know of service requested in connect
descriptor "
I connected to server and tried to login from there..the same message was thrown, but able to connect to other db's.
Finally I set the oracle_home path to the db to which i was not able to login and connected using
something like....
conn /as sysdbaidle instance
startup;database mounted
database started
After that i was able to connect to that db as well as all other db's on the server.
My doubt is, why suddenly that stopped working and it didn't work until i use "startup" command ?
Also, how DBA's maintain server's with multiple oracle_home's?(though recommended to have multiple schema's instead of multiple db's)
I'm the only Oracle guy in the team and need to take care of everything(basically i'm developer and new to DBA related tasks)
My lead's warned me to make sure that it won't happen again !!
Thanks guys.. you are always awesome in giving nice suggestions.find alert_SID.log file post excerpt showing entries from period just prior to the DB STARTUP.
it appears the instance went missing.
Hopefully the log file will have clues as to why it went away.

Can't revert to ical backup database

I backed up my ical database, when I tried to open it up again it on a different computer it doesn't open up. It gives me a massage Revert failed.
I've started to save my address book on a yearly bases and i need to look up appointment from last year. this is very important for my work...and i'm very frustrated...XXX

I do not know if current iCal will open older iCal files. iCal comes with the OS, so I don't think there is a trial version you can try. How large is the backup file and will it drag to an outgoing email message? Try dragging the file over every Application you have. There is little chance, but perhaps something you have will open it enough to read the data.

Applying transaction log corrupted database?

Hi experts,
Symptoms:
I built a standby system this Monday and I completed a full DB restore without errors. I used log shipping to apply logs but an error occurred: SQL Server detected a logical consistency-based I/O error: incorrect pageid (expected 20:5746350; actual 0:0). It occurred during a read of page (20:5746350) in database ID 5 at offset 0x00000af5d5c000 in file 'l:\TCPDATA4\TCPDATA19.ndf'.
I run dbcc page and found page(20:5746350) did corrupt on standby system. However, I ran dbcc page on production and it is ok. I restored this full db to another standby and ran dbcc page and it is ok. Also, Checkalloc, Checkcatalog, Checktable on production are ok.
Questions:
Does checktable detect secondary indexes corruption? I am re-compressing COSP indexes and running full checkdb on production right now to find out what's going on in our DB. How do I fix this issue? Any information will be really appreciated.
Error message:
2011-08-23 17:26:00.19 spid52      The log shipping secondary database TCCDBM1.TCP has restore threshold of 45 minutes and is out of sync. No restore was performed for 1 minutes. Restored latency is 720 minutes. Check agent log and logshipping monitor information.
2011-08-23 17:26:39.62 Backup      Log was restored. Database: TCP, creation date(time): 2011/07/03(05:36:16), first LSN: 184193:4075900:1, last LSN: 184193:7288500:1, number of dump devices: 1, device information: (FILE=1, TYPE=DISK: {'w:\LogB\TCP_20110822213010.trn'}). This is an informational message. No user action is required.
2011-08-23 17:28:00.88 spid52      Error: 14421, Severity: 16, State: 1.
2011-08-23 17:28:00.88 spid52      The log shipping secondary database TCCDBM1.TCP has restore threshold of 45 minutes and is out of sync. No restore was performed for 2 minutes. Restored latency is 716 minutes. Check agent log and logshipping monitor information.
2011-08-23 17:28:34.03 Backup      Log was restored. Database: TCP, creation date(time): 2011/07/03(05:36:16), first LSN: 184193:7288500:1, last LSN: 184193:10880343:1, number of dump devices: 1, device information: (FILE=1, TYPE=DISK: {'w:\LogB\TCP_20110822213511.trn'}). This is an informational message. No user action is required.
2011-08-23 17:28:53.06 spid65      Error: 824, Severity: 16, State: 2.
2011-08-23 17:28:53.06 spid65      SQL Server detected a logical consistency-based I/O error: incorrect pageid (expected 20:5746350; actual 0:0). It occurred during a read of page (20:5746350) in database ID 5 at offset 0x00000af5d5c000 in file 'l:\TCPDATA4\TCPDATA19.ndf'. Additional messages in the SQL Server error log or system event log may provide more detail. This is a severe error condition that threatens database integrity and must be corrected immediately. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information, see SQL Server Books Online.
2011-08-23 17:30:00.54 spid52      Error: 14421, Severity: 16, State: 1.
2011-08-23 17:30:00.54 spid52      The log shipping secondary database TCCDBM1.TCP has restore threshold of 45 minutes and is out of sync. No restore was performed for 2 minutes. Restored latency is 713 minutes. Check agent log and logshipping monitor information.
2011-08-23 17:30:35.94 spid53      Error: 824, Severity: 16, State: 2.

Hi Dennis!
I understand your reasonable doubt, but think that physical corruptions are 99,999...% caused by a hardware failure e.g. a defective RAM module, or a related, low-level failure as e.g. an outdated NIC driver, etc.
Then, in this case it is clear that you have a platform problem only on your standby system, and not in the one running productively right now.
Maybe you already checked your platform, but you should take into account that in most cases just reading the logs is not enough; stress tests on all of the components are usually necessary. Most of the time, when we analyze hardware related problems, the problem is only reproduced when special tests are performed. Furthermore it is possible that more than one component is weak or broken.
My recommendation is that you check the components in this order:
   - disks (complete surface) (while SAP and SQL Server are shut down)
   - disk controller
   - Memory (stress test)
   - CPU
   - all other components
Consider that restoring a backup and running in a damaged platform would imply further problems. You would be waiting until the next problem arises and that would imply a system halt or corruptions, maybe even with data loss.
Once the hardware checked and -if necessary- fixed, you can proceed as explained in SAP notes 142731 and 1420452. Of course you can also restore in a different hardware, but remember checking the platform as it is also exposed to hardware failures.
Cheers!!
--Jesú

Any hope for corrupted database?

I keep a membership directory for our organization with names, addresses, etc., as well as pictures, in an Appleworks database. One of the records has become corrupt. I have tried deleting that record, saving into Appleworks 5 and re-opening, saving copies of the DB and using those, etc., but the corruption seems to stick with the file no matter what I've tried.
The database contains only about 60 entries, so it would not be a huge deal to put the information and pictures back in, but the layouts took A LOT of time and I'd like to avoid re-creating these.
Any other suggestions?

Hello
Each time I was able to repair a database, the problem was not with the layouts.
It was with corrupted records or fields.
So, I used a script to transfer the contents of fields one by one filtering those with problems.
I don't remember a DB whose layout itself was odd, but maybe my memory fails.
Send the empty DB, I will try to see if something is wrong but I can't give any guarantee.
In fact I will use a script trying to fill a lot of records to see if all works well.
It would be useful to have at least one record available so it would be easier to understand what is every field resembling to.
If I am able to return a clean empty DB, using the old one to fill the new one will certainly give odd results.
To work on safe basis the minimal path is:
copy the contents of the base into the clipboard
paste in an empty word processor document
save as a text file
Open the empty base
import from the text file.
Take care of RETURN characters which may be embedded in some fields
They would destruct the structure of the records giving odd results.
Yvan KOENIG (from FRANCE lundi 18 février 2008 14:03:44)

Data recovery from Datafiles of corrupted database ?

Hi all
Actullay one of my databse(Oracle 9i) is corrupted and i dnt have .dmp files . so i inatlled the new databse.
before that i copied the oradata folder from prevous database( Is not running right now)
is there any way to restore the prevoius data from the files that i have in oradata folder to the new instance.
thanks & regards
Vivek

Has the database - even when it was corrupted - been shutdown cleanly ?
If yes, and only if you have all the files, it should be startable.
If any of the datafiles is corrupted and it prevents database startup, you can always try following:
startup mount
alter database datafile <filename> offline drop;
If the database is/was in archivelog mode you can omit the "drop" and only put it offline.
As soon as all corrupted datafiles are put offline, including all not corrupted from the same tablespace, the database should be able to open.
Keep in mind that this is only true for datafiles not belonging to SYSTEM/SYSAUX or other Instance dependant tablespaces;
I don't think you can restore data from corrupted datafiles, unless you're able to recover them

Filter corrupts database

Hi - has anyone had issues creating a filter (on total float of a baseline specifically) that has corrupted / locked out the database?

You can try the following solution. We had this happen at a client a few months ago. Not sure what version you're on, so solution could be different.
Open the layout known not to cause the error and choose View, Layout, Save As.
Provide a new name, different from the name of corrupt layout.
Set the layout up to look the same as the original layout based on the previously noted settings
Delete the corrupt layout

ICal Corrupt Database

Similar Messages

Maybe you are looking for