serenity_now
Active Member
Hi All,
I remember a few years back there was talk of Virtual Batch queues being implemented by Oracle which would greatly help with the problem of 2 separate servers handling UBEs and not having single threaded jobs colliding on either server. I don't see anything mentioning this anywhere anymore other than some older threads on here.
We are looking at having 2 different Enterprise servers for timezones, preferably we would like each server (representing a timezone) to process its own UBEs so the timestamps and transaction dates/records are all correct to that timezone, etc. Currently the options are to hardcode all single threaded jobs to one server, which kind of defeats the purpose of the timezones in some cases, the other option is piecing together some kind of custom solution that may be a bit overkill.
Just curious if there is anything I am missing, or if this has just fallen by the wayside.
I remember a few years back there was talk of Virtual Batch queues being implemented by Oracle which would greatly help with the problem of 2 separate servers handling UBEs and not having single threaded jobs colliding on either server. I don't see anything mentioning this anywhere anymore other than some older threads on here.
We are looking at having 2 different Enterprise servers for timezones, preferably we would like each server (representing a timezone) to process its own UBEs so the timestamps and transaction dates/records are all correct to that timezone, etc. Currently the options are to hardcode all single threaded jobs to one server, which kind of defeats the purpose of the timezones in some cases, the other option is piecing together some kind of custom solution that may be a bit overkill.
Just curious if there is anything I am missing, or if this has just fallen by the wayside.