orcale restore问题：丢失数据库后恢复的时间：数据库暂时无法访问的主要问题。 [英] orcale restoration issue:Time to restore after loss of database: The main issue the database was inaccessible for a while.

问题描述

orcale restore问题：



1）我的应用程序是C＃.Net windows应用程序，它有多个insatnces并使用Oracle作为db。

2）位于巴黎网络的其他服务器中的Oracle数据库服务器。

3）我们也使用Tibco发送xml输入。



对于再现问题支持团队决定停止所有TFM实例以避免问题。

他们禁用tibco然后启动TFM一个接一个的实例。

它花了2个小时恢复数据库连接+ 2个小时恢复所有TFM实例。

这个想法是总结处理这种情况的最佳方法，并防止长时间恢复时间，如果发现问题也是任何可行性都可以通过TFM和Tibco重新启动进行恢复。

orcale restoration issue:

1) My application is C# .Net windows application and its having multiple insatnces and its using Oracle as db.
2)Oracle db server in other server in location Paris network.
3) we are also using Tibco for sending xml input.

For reproducing issue support team decided to stop all TFM instances to avoid issues.
They disable tibco then start TFM one instance after another.
It took 2 hours to restore the database connections + 2 hours restoring all TFM instances.
The idea is to summarize the best way to deal with this situation and prevent long restoring time in case of issue also find out is there any feasibility do the restoration with any restart of TFM and Tibco.

Questions: From the oldest TFM to the newest version:
-   Does TFM able to recover from this situation without restart?

-   Is it possible to disable tibco sending while database is down and then enable the tibco sending when the database is available without issue?

-   What is the best way to do it? Description step by step?

推荐答案

这篇关于orcale restore问题：丢失数据库后恢复的时间：数据库暂时无法访问的主要问题。的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！