naresh ghimire wrote:
The 'problem' is there in earlier releases - you just got lucky. Basically you cannot do this. Before making such copies you have to quiesce the database and sync to disk. There is a command in your version of jBASE that might help though: Try a script: #! /bin/ksh DB-PAUSE sync # command to do filesystem copy goes here DB-RESUME However, I am unfamiliar with the use of those commands (I don't think it is a good way to do things) so check with TEMENOS or others here that may have done this. Even with the above, while it should mean you don't get a corrupt file, it does nothing to protect against the fact that you might be half way through a transaction, so the target copy is still next to useless. You need to implement transaction journaling and jlogdup. Jim
--~--~---------~--~----~------------~-------~--~----~ Please read the posting guidelines at: http://groups.google.com/group/jBASE/web/Posting%20Guidelines IMPORTANT: Type T24: at the start of the subject line for questions specific to Globus/T24
To post, send email to [email protected]
|
- Jbase file curruption in AIX unix kumar
- RE: Jbase file curruption in AIX unix Jim Young
- Re: Jbase file curruption in AIX unix Jim Idle
- Re: Jbase file curruption in AIX unix naresh ghimire
- Re: Jbase file curruption in AIX u... Jim Idle
- Re: Jbase file curruption in A... Crusader Sterling Pensions
- Re: Jbase file curruption... Jim Idle
