How can I enforce a faster startup when the RDB Manager takes too long to establish a connection with the Oracle Server?

In the default configuration of WinCC OA the RDB tries to establish a connection to the Oracle Server during startup. This could take a few minutes in dependency of the actual state of the Oracle Server (stopped, currently starting up, heavy load and so on)

In this situation all following WinCC OA managers will not be started until the RDB got his connection to the Oracle Server.

To avoid this situation and to optimize the startup behavior it is possible to start the RDB Manager in an offline mode. In this mode the RDB Manager will begin buffer all of this values until it gets the command to establish a connection with the Oracle Server. This command could be triggered a few minutes after the complete startup of the WinCC OA project with a manual set of the _RDBArchive.connection.openDBConnection DPE.

With this configuration there is no need to be concerned about the actual state of the Oracle Server during the startup of the WinCC OA project because the startup is not interrupted by a RDB-Manager which tries to establish a connection with the Oracle Server.

For more information regarding this configuration please check chapter: “Details on data buffering” from RDB Manager in WinCC OA Online Help