Forum Stats

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

Discussions

GREEN / Bulk API Performance Affected / POD 2 / RESOLVED

Anirude-Oracle
Anirude-Oracle Posts: 118 Employee
edited Mar 27, 2014 12:28PM in Eloqua System Status

The Development and Cloud Operations teams are currently working on a solution to resolve the performance incident on POD 2 related to Bulk API. We are currently targeting a hot-fix for later this evening. While we are unable to provide a granular ETA and the next scheduled update will be around 10:00am EDT (UTC-4) on Friday, March 21st, 2014.

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

**Update**

Friday, March 21st, 9:54 am EDT (UTC -4)

The hot-fix we were targeting for last night didn't pass our tests with QA. The Development and Cloud Operations teams continue to review alternative solutions. We are unable to provide an ETA, but the next scheduled update will be around 3:00pm EDT (UTC-4) today.

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

**Update**

Friday, March 21st, 2:41 pm EDT (UTC -4)

The Development and Cloud Operations teams are working through this issue. They are working in tandem with our Development Operations in an effort to resolve this quickly. We are unable to provide an ETA, but the next scheduled update will be around 10:00am EDT (UTC-4) on Monday, March 24th, 2014.

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

**Update**

Monday, March 24th, 10:00 am EDT (UTC -4)

The Development and Cloud Operations teams are working through this issue. Over the weekend, we were able to apply configuration changes to help improve the performance. The teams continue to monitor the situation. We are unable to provide an ETA, but the next scheduled update will be around 2:00pm EDT (UTC-4) today.

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

**Update**

Monday, March 24th, 2:45 pm EDT (UTC -4)

The Development and Cloud Operations continues to monitor the situation. We are unable to provide an ETA, but the next scheduled update will be around 11:00am EDT (UTC-4) on Tuesday, March 25th, 2014.


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

**Update**

Tuesday, March 25th, 9:38 am EDT (UTC -4)

The Development and Cloud Operations continues to monitor the situation. We are unable to provide an ETA, but the next scheduled update will be around 2:00pm EDT (UTC-4) on Tuesday, March 25th, 2014.


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

**Update**

Tuesday, March 25th, 11:50 am EDT (UTC -4)

The Development and Cloud Operations continues to investigate and monitor the situation. We are unable to provide an ETA, but the next scheduled update will be around 2:30pm EDT (UTC-4).


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

**Update**

Tuesday, March 25th, 2:33 pm EDT (UTC -4)

The Development and Cloud Operations continues to investigate and monitor the situation. We are unable to provide an ETA, but the next scheduled update will be around 5:30pm EDT (UTC-4).


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

**Update**

Wednesday, March 26th, 12:20 am EDT (UTC -4)

The Development and Cloud Operations continues to investigate and monitor the situation. We are unable to provide an ETA, but the next scheduled update will be around 11:30am EDT (UTC-4).


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

**Update**

Wednesday, March 26th, 11:39 am EDT (UTC -4)

The Development and Cloud Operations continue monitor the situation. We are unable to provide an ETA, but the next scheduled update will be around 4:00 pm EDT (UTC-4) today.


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

**Update**

Wednesday, March 26th, 3:57 pm EDT (UTC -4)

The Development and Cloud Operations continue monitor the situation. We are unable to provide an ETA, but the next scheduled update will be around 11:30am EDT (UTC-4) on Thursday, March 27th, 2014.


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

**Update**

Thursday, March 27th, 12:28 pm EDT (UTC -4)

This incident is now resolved. The Development and Cloud Operations will continue monitor the situation. 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: