Forum Stats

  • 3,678,175 Users
  • 7,778 Discussions
  • 13,052 Comments

Discussions

GREEN / Some Functions of Bulk API are Unavailable / All Clients / RESOLVED

Anirude-Oracle
Anirude-Oracle Posts: 118 Employee
edited Mar 14, 2014 6:19PM in Eloqua System Status

Our Cloud Operations is currently investigating an incident where some functions of Bulk API are unavailable to our clients. We currently don't have an ETA, but the next update will be 3:00 pm EDT (UTC-4).

====================================

**Update**

Tuesday, March 11th, 3:07 pm EDT (UTC -4)

Both Cloud Operations and the Development Team are still investigating the incident. In the interim, the teams are manually working the Bulk API queues to assist in minimizing impact. While we still don't have an ETA, the next update will be around 4:00 pm EDT (UTC-4).

====================================

**Update**

Tuesday, March 11th, 3:58 pm EDT (UTC -4)

Cloud Operations and the Development Team continue to work at this incident. The incident has improved with their efforts and we are now facing performance degradation. Cloud Operations continues to monitor the situation as we also work in parallel to hot-fix aspects of the overall incident. While we still don't have an ETA, the next update will be around 5:00 pm EDT (UTC-4).


====================================

**Update**

Tuesday, March 11th, 5:03 pm EDT (UTC -4)

Cloud Operations and the Development Team continue to work at this incident aggressively. They are working through identifying the root cause. While we still don't have an ETA, the next update will be around 7:30 pm EDT (UTC-4).


====================================

**Update**

Tuesday, March 11th, 7:27 pm EDT (UTC -4)

Cloud Operations and the Development Team are still investigating the root cause. Users will continue to see performance degradation when using the Bulk API. As we are unable to provide an ETA, the next update will be around 10:15 am EDT (UTC-4) Wednesday, March 12th, 2014.


====================================

**Update**

Wednesday, March 12th, 10:01 am EDT (UTC -4)

Cloud Operations and the Development Team continue to investigate this incident. Client will continue to see performance degradation when using the Bulk API and Cloud Operations continues to monitor and manually work the Bulk API queues to assist in minimizing impact. As we are unable to provide an ETA, the next update will be around 11:15 am EDT (UTC-4) today.


====================================

**Update**

Wednesday, March 12th, 11:15 am EDT (UTC -4)

Cloud Operations and the Development Team continue to investigate this incident. Client will continue to see performance degradation when using the Bulk API and Cloud Operations continues to monitor and manually work the Bulk API queues to assist in minimizing impact. As we are unable to provide an ETA, the next update will be around 12:15 pm EDT (UTC-4) today.


====================================

**Update**

Wednesday, March 12th, 12:25 pm EDT (UTC -4)


Cloud Operations and the Development Team continue to work at this incident. Cloud Operations continues to monitor the situation as the Development Team continue work to hot-fix aspects of the overall incident. While we still don't have an ETA, the next update will be around 2:15 pm EDT (UTC-4).


====================================

**Update**

Wednesday, March 12th, 2:25 pm EDT (UTC -4)


Cloud Operations and the Development Team continue to work at this incident. Cloud Operations continues to monitor the situation as the Development Team continues work to hot-fix aspects of the overall incident. We are targeting to have the hot-fixes ready within the next two business days, the next update will be around 4:15 pm EDT (UTC-4).


====================================

**Update**

Wednesday, March 12th, 4:17 pm EDT (UTC -4)

Cloud Operations continues to monitor the situation as the Development Team continues work to hot-fix aspects of the overall incident. We are targeting to have the hot-fixes ready for tomorrow, the next update will be around 11:00 am EDT (UTC-4) tomorrow Thursday, March 13th, 2014.


====================================

**Update**

Thursday, March 13th, 10:44 am EDT (UTC -4)

Cloud Operations continues to monitor the situation as the Development Team continues work to hot-fix aspects of the overall incident. We are currently working through our hot-fix process, the next update will be around 2:00 pm EDT (UTC-4) today.

====================================

**Update**

Thursday, March 13th, 1:25 pm EDT (UTC -4)

Cloud Operations continues to monitor the situation as the Development Team continues work to hot-fix aspects of the overall incident. We are still working through our hot-fix process, we are still not able to provide an ETA, but the next update will be around 4:00 pm EDT (UTC-4) today.

====================================

**Update**

Thursday, March 13th, 3:43 pm EDT (UTC -4)

Cloud Operations continues to monitor the situation. The Development Team continues to work through our hot-fix process and we are now collaborating with the QA Team as we test our solutions. We are still unable to provide an ETA, but the next update will be around 7.30 pm EDT (UTC-4).


====================================

**Update**

Thursday, March 13th, 6:49 pm EDT (UTC -4)

The Cloud Operations Team continues to monitor the situation. The Development Team continues to work through our hot-fix process and we are now working with our Change Advisory Board to identify when we are able to hot-fix POD 1. During our QA process, POD 2 and 3 failed certain tests and our Development Team will be evaluating next steps. We are still unable to provide an ETA, but the next update will be around 10.30 am EDT (UTC-4) tomorrow, Friday, March 14th, 2014.


====================================

**Update**

Friday, March 14th, 9:23 am EDT (UTC -4)

The Cloud Operations Team continues to monitor the situation. We were able to hot-fix POD 1 last night around 7:45 pm EDT (UTC-4). The Development Team continues to evaluate the POD 2 and 3 failed tests. We are unable to provide an ETA, but the next update will be around 1.30 pm EDT (UTC-4) today.


====================================

**Update**

Friday, March 14th, 1:21 pm EDT (UTC -4)

The Cloud Operations Team continues to monitor the situation. We are now working with our Change Advisory Board to identify when we are able to hot-fix POD 2 and 3. We are unable to provide an ETA, but the next update will be around 4.30 pm EDT (UTC-4).


====================================

**Update**

Friday, March 14th, 3:23 pm EDT (UTC -4)

We were able to hot-fix POD 2 and 3 around 2:50 pm EDT (UTC-4). After analysis by our support teams, it was determined that the incident was the result of a software bug in Eloqua. Information related to the incident has been passed on to our Product Engineering team. Oracle is also reviewing the monitoring, alerting and standard operating procedures related to the incident. After these reviews are completed, additional appropriate corrective actions identified during the reviews will be taken, including deployment of the appropriate patch or release when available.

Post edited by Unknown User on
Tagged: