|
Did you search the documentation that comes with
Cache for <Disk>? Right click the cube and select
documentation.
Giving simple directions to run Integrity and
what to do with the findings is not possible.
If you are just setting up for the first time,
then I would suggest you delete the cache.dat and a get a new copy from wherever
you got it in the first place. If this is a system that you absolutely
must fix, then I would suggest you contact Intersystems and see what they would
charge to fix your Cache.dat. We had a database corruption once.
Even though I am experienced with fixing such things, it was more economical and
much, much safer to have Intersystems do it. We sent then the
Cache.dat. They fixed it and returned it to us. Of course, your
system will be down until you get it back. This is the very reason that
both Intersystems and GT.M highly recommend that one set up journaling and
backups. With those properly set up you can virtually eliminate this type
of problem. The problem could still occur, but then you would have the
possibility of doing a restore and dejournal to get your system back.
Since ours was a development account, we had the occurrence because we were lazy
like many people and did not have journaling set up. Even this protection
will not always save you. If you get such a database problem and do not
know if for some time then your backups will also have this database problem
thus making it nearly impossible to perform recovery as mentioned.
Note to all - do not use an OS or third party
backup tool when Cache is still running. If you choose to do so, then you
must shut cache down prior to performing the OS level backup of the
Cache.dat. Then it is safe to perform that backup without corrupting
the Cache.dat.
|
Title: Newbie installation
- Re: [Hardhats-members] Newbie installation steven mcphelan
- Re: [Hardhats-members] Newbie installation Steve Owen
- Re: [Hardhats-members] Newbie installation rgaber
- Re: [Hardhats-members] Newbie installation Ruben Safir
