Skip navigation

Emergency Maintenance Advisory for Thursday, June 26th, 2014



Eloqua will be performing Emergency Maintenance on Thursday, June 26th, between 9:00 pm -11:00 pm EDT (UTC -4).

 

Downtime affect as follows. During parts of the maintenance:

 

•         Inbound activity will be lost (page views, email responses).

•         Form submissions will not be captured.

•         Application processing will be paused and resumed after downtime ends.

 

You are advised not to use the application during this period to avoid loss of work. Please contact Eloqua Support if you require additional details.

 

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

**Update**

Thursday, June 26th, 11:26 pm EDT (UTC -4)

 

The maintenance concluded successfully at 11:05 pm EDT (UTC-4) without incidents.

Between 3:55 AM EDT (UTC-4) and 4:40 AM EDT (UTC-4) Some POD1 clients may have experienced problems logging into their database. The issue is now resolved.


After analysis by our support teams, it was determined that the incident resulted from a hardware issue. The hardware identified as faulty has been replaced and production use of your Eloqua service restored. 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.


Scheduled Maintenance Advisory for Sunday, June 22nd, 2014

 

 

Eloqua will be performing scheduled maintenance on Sunday, June 22nd, 2014, between 5 and 11am EDT (UTC -4).

 

Downtime effect as follows. During portions of this maintenance period:

 

  • Client installs will be inaccessible
  • Inbound activity will be lost (page views, email responses)
  • Form submissions will not be captured
  • Application processing will be paused and resumed after downtime ends.

 

You are advised not to use the application during this period to avoid loss of work.

 

Should you require more information or have any questions, please feel free to contact our Support specialists.

-------------------------------------------------------------------------------------------------------------------------------------------------------

**Update**

Monday, June 23rd, 8:20 am EDT (UTC -4)

 

The maintenance concluded successfully on Sunday, June 22nd at 9:01 am EDT (UTC-4) without incidents.

Our Cloud Operations Team is currently investigating the cause of an incident that is affecting the responsiveness of the BULK API on POD 2.  While we do not at this time have an ETA for resolution, we will continue to monitor this issue and update this post as to the current status. The next scheduled update will be around 10:00 am EDT (UTC-4).

 

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

**Update** Wednesday June 18th 9:53 AM EDT (UTC-4)

 

Our operations team continues to investigate the incident, no ETA is available as of yet. We will continue to update this post with the current status, the next update will be around 12:00 PM EDT (UTC-4)

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

**Update** Wednesday June 18th 12:02 PM EDT (UTC-4)

 

Our operations team continues to investigate the incident. We will continue to update this post as to the current status. The next update will be around 2 PM EDT (UTC-4)

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

**Update** Wednesday June 18th 2:05 PM EDT (UTC-4)

 

Our operations team continues to investigate the incident. We will continue to update this post as to the current status. The next update will be around 4 PM EDT (UTC-4)

 

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

**Update** Wednesday June 18th 4:00 PM EDT (UTC-4)

 

Our Cloud Operations Team, Development Team and Oracle DB Support continue to aggressively work towards a resoultion for this incident. While we are unable to provide an ETA, the teams have had some successes in troubleshooting and getting closer to the root cause. The next scheduled update will be around 6:00 pm EDT (UTC-4).

 

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

 

Update: Wednesday June 18th 4:07 PM EDT (UTC-4)

 

After analysis by our support teams, it was determined that the incident was the result of a software bug of an Oracle Program. Information related to the incident has been passed on to our Product Engineering team. Once Product Engineering confirms they have a resolution to the issue, it will be deployed to the applicable Oracle Programs for your Eloqua service. No ETA for resolution is available at this time. 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.

Our Cloud Operations Team is currently investigating an incident related to assets not saving for POD 2 clients.  This incident roughly started at 8:00 am EDT (UTC -4) and the next update will be around 12:00 pm EDT (UTC -4).

 

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

**Update**

Monday, June 16th, 12:44 pm EDT (UTC -4)

 

After analysis by our support teams, it was determined that the incident was the result of a software issue, which has been corrected by our Product Engineering Team and deployed to the Eloqua Platform. 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.

Emergency Maintenance Advisory for Sunday, June 15th, 2014



Eloqua will be performing Emergency Maintenance on Sunday, June 15th, between 5:00 am -11:00 am EDT (UTC -4).

 

Downtime affect as follows. During parts of the maintenance:

 

•         Inbound activity will be lost (page views, email responses).

•         Form submissions will not be captured.

•         Application processing will be paused and resumed after downtime ends.

 

You are advised not to use the application during this period to avoid loss of work.

 

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

**Update**

Sunday, June 15th, 8:25 am EDT (UTC -4)

 

The maintenance concluded successfully at 6:45 am EDT (UTC-4) without incidents.

Between Tuesday, June 10th at 11:00 am EDT (UTC-4) and Wednesday, June 11th at 3:40 pm EDT (UTC-4) our Cloud Operations Team identified that Synch Bouncebacks were not being properly processed on POD3. 

 

After analysis by our support teams, it was determined that the event resulted from a database issue. The database issue has been resolved and production use of your Eloqua service has been restored. 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.

Emergency Maintenance Advisory for Monday, June 9th, 2014

 

 

Eloqua will be performing emergency maintenance on Monday, June 9th, between 10 and 11 pm EDT (UTC -4).

 

During this maintenance period:

 

There should be no impact to clients during this maintenance.

 

Should you require more information or have any questions, please feel free to contact our Support specialists.

 

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

**Update**

Monday, June 9th, 11:30 pm EDT (UTC -4)

 

The maintenance concluded successfully and without incidents.

Eloqua will be performing an emergency hot-fix on Sunday, June 8th starting at 3:35 pm EDT (UTC-4).


The impact of the Eloqua Service will be moderate, the service that we need to redeploy is related to CRM Integrations. There will be an overall performance decrease using the Eloqua Application while we are deploying this hot-fix. We estimate the hot-fix will take around 1 hour to complete, however, our System Status page on Topliners will be updated with our progress during the hot-fix.


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

**Update**

Sunday, June 8th, 4:28 pm EDT (UTC -4)

 

The hot-fix concluded at 4:27 pm EDT without incident.

Filter Blog

By date: By tag: