-
Urgent: database is becoming inconsistent due to data service failure
I have one webservice in which i have done connection with oracle database
now suppose my webservice crashes due to power failure..it had submitted
some transactions say update on database;
now database is intact but my webservice failed..so locks are remaining on the database
now i create a new webservice, for recovering database. i am losing my previous long transaction (still not committed) because of power failure.
when transaction is executing if we do "alter system log switch", checkpoints
are taken..buffers are writted to disk..can these help me when after failure i am starting a new recovery service- My intension is i dont want to submit
whole transaction again...thru checkpoints i want to recovery transactions effect which i had submitted through my webservice(beacuse executing long
transaction from scratch takes too much time)..can checkpoint facility(inbuilt in oracle) help me solve this?
How?
thnx
-
I don’t want to be harsh, but you really need to review your manuals about Oracle database concepts and architecture.
---------------
-
Well, I support Ray.
The idea of transaction is to either succeed or fail as a whole module. Recovery a part of transaction is not an option
If you think that you loose too much info in case of failure, I would suggest to think about breakong the transaction into several smaller ones
Regards
-
I'm in full agreement with reydp and Bore.
Original poster might have also to review application design/architecture, web based apps usually process very small transactions.
Tip for the Oracle side research: review and understand COMMIT/ROLLBACK concept.
Pablo (Paul) Berzukov
Author of Understanding Database Administration available at amazon and other bookstores.
Disclaimer: Advice is provided to the best of my knowledge but no implicit or explicit warranties are provided. Since the advisor explicitly encourages testing any and all suggestions on a test non-production environment advisor should not held liable or responsible for any actions taken based on the given advice.
-
I'd like to point out that the topic title is incorrect -- the database is still consistent (ie entire transaction committed or rolled back).
-
That's why they are called transactions, you can either commit it or rollback it... nothing in between which, is what original poster appears is trying to achieve.
Pablo (Paul) Berzukov
Author of Understanding Database Administration available at amazon and other bookstores.
Disclaimer: Advice is provided to the best of my knowledge but no implicit or explicit warranties are provided. Since the advisor explicitly encourages testing any and all suggestions on a test non-production environment advisor should not held liable or responsible for any actions taken based on the given advice.
-
when transaction is executing if we do "alter system log switch", checkpoints
are taken..buffers are writted to disk..can these help me when after failure i am starting a new recovery service- My intension is i dont want to submit
whole transaction again...thru checkpoints i want to recovery transactions effect which i had submitted through my webservice(beacuse executing long
transaction from scratch takes too much time)..can checkpoint facility(inbuilt in oracle) help me solve this?
Checkpoint will not help you to solve the problem. The transaction recovery is done automatically by oracle.
Either your transaction is fully committed or rolledback. There is no stage inbetween them.
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
Click Here to Expand Forum to Full Width
|