Skip navigation

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

**Update**

Wednesday, April 1st, 2:30 am EDT (UTC -4).

 

The maintenance concluded on schedule and without incident.

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

Eloqua 470 Release


The Eloqua 470 Release will roll out between 11 pm, Tuesday, March 31st, and 5 am, Wednesday, April 1st, 2015 [all times EDT (UTC -4)].

 

 

Please review the supporting resources available in the Oracle Eloqua Release Center. This includes Release Notes for both E9 and E10 with information on:


Release Overview

What's New in This Release

Known Issues

Fixed Issues

Technical Notes and Limitations

Supported Environments

Documentation

Troubleshooting and Technical Support

 

If you're not already an Eloqua Insiders, you'll need to request access to that group before you can access the Release Resource Center.

 

 

While the application may remain accessible during this time, some features such as file and image uploads, program builder and emails will be paused as they are upgraded. There will also be intermittent downtime during this period. You are advised to avoid using the application during this window.

 

 

To determine if you are on Pod2:

Log into Eloqua as you normally would.

Look at the browser URL once you are logged in.

Pod2 URL has the following format - www02.secure.eloqua.com/... (note:  02 included in URL).

Our Cloud Operations Team is currently investigating an incident where clients are experiencing slow load times when logging into the Eloqua Application as well as slowness in UI navigation. We do not currently have an ETA for resolution. The next update will be at approximately 12:30 pm EDT (UTC -4).


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

**Update: Tuesday, March 31st 12:00 pm EDT (UTC-4)**

 

Our Cloud Operations Team has confirmed that this issue is now resolved.


After analysis by our support teams, it was determined that the incident resulted from a configuration issue. The configuration 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.

Our Cloud Operations Team is currently investigating an incident where clients are experiencing slow load times when logging into the Eloqua Application as well as slowness in UI navigation. We do not currently have an ETA for resolution. The next update will be at approximately 6:00 am EDT (UTC -4).


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

**Update: Tuesday, March 31st 6:00 am EDT (UTC-4)**

 

Our Cloud Operations Team continues to aggressively work on resolving this incident. We are unable to provide an ETA at the moment. The next scheduled update will be at approximately 7:00 am EDT (UTC-4).

 

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

**Update: Tuesday, March 31st 6:30 am EDT (UTC-4)**

 

Our Cloud Operations Team believe they have corrected the incident. They will continue to monitor this incident. The next update will be at approximately 10:00 am EDT (UTC -4).


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

**Update: Tuesday, March 31st 8:45 am EDT (UTC-4)**


After analysis by our support teams, it was determined that the incident resulted from a network issue. The network 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.

Our Cloud Operations Team is currently investigating an incident where clients are experiencing slow load times when logging into the Eloqua Application as well as slowness in UI navigation. We do not currently have an ETA for resolution. The next update will be at approximately 11:00 am EDT (UTC -4).


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

**Update: Monday, March 30th 11:00 am EDT (UTC -4)**

 

Our Cloud Operations Team believe they have corrected the incident. They will continue to monitor this incident. The next update will be at approximately 12:00 pm EDT (UTC -4).


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

**Update: Monday, March 30th 12:00 pm EDT (UTC -4)**

 

Our Cloud Operations Team continues to monitor the incident. The next update will be at approximately 2 pm EDT (UTC -4).

 

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

**Update: Monday, March 30th 2:00 pm EDT (UTC -4)**

 

Our Cloud Operations team has put in place measures to resolve this incident. They will continue to monitor the situation. The next update will be at approximately 10 pm EDT (UTC-4).

 

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

**Update: Monday, March 30th 10:03 pm EDT (UTC -4)**

 

Our Cloud Operations Team has confirmed that this issue is now resolved.

 

After analysis by our support teams, it was determined that the incident resulted from a network issue. The network 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.

Our Cloud Operations Team is currently investigating an incident where clients are experiencing slow load times when logging into the Eloqua Application. We do not currently have an ETA for resolution. The next update will be at approximately 5:00 pm EDT (UTC -4).

 

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

**Update**

Sunday, March 29th, 4:14 pm EDT (UTC -4).

 

Our Cloud Operations Team has confirmed that this issue is now resolved.


After analysis by our support teams, the root cause of the incident was not determined. At this time, production use of your Eloqua service has been restored. Oracle is 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.

Our Cloud Operations Team is currently investigating an incident relating to email sending delays on POD 1, 2 & 3. We do not currently have an ETA for resolution. The next update will be at approximately 4:00 pm EDT (UTC -4)

 

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

**Update: Sunday, March 29th 3:18 pm EDT (UTC -4)**

 

Our Cloud Operations Team has confirmed that this issue is now resolved.

 

After analysis by our support teams, it was determined that the incident resulted from a configuration issue. The configuration 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.

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

 

**Update**

 

Sunday, March 29th, 11:09 am EDT (UTC -4).

 

Our Cloud Operations Team has completed the maintenance.

 

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

**Update: Thursday, April 2nd 2:05 pm EDT (UTC -4)**

 

The Oracle Cloud Support Team would like to make a correction on this advisory. During this maintenance, inbound web tracking and form data were not captured based on the scope of the maintenance performed by our Cloud Operations Team.

 

The related standard operating procedure has been reviewed for improvement and for additional safeguards to avoid this miscommunication in the future. Oracle is also reviewing the monitoring and alerting 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, March 29th, 2015

 

 

Eloqua will be performing a scheduled maintenance on Sunday, March 29th, 2015, between 5 am and 11 am EDT (UTC -4).

 

All application processing will be suspended during this window and resumed after downtime ends.

 

Downtime effect as follows. During portions of this maintenance period, the following platform features will be unavailable:

 

  • Email Sending (all types)
  • Inbound/Outbound CRM Integrations
  • Bulk API
  • Lead Scoring
  • Data Import/Exports
  • Campaign Processing

 

We recommend that customers not attempt to use the application at this time as rolling outages are anticipated. Inbound web tracking and form data will be captured, however, agent use of the platform can potentially result in work being lost. Once the maintenance is complete, all processing will resume and any work items scheduled to execute during the maintenance window will begin processing.

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

**Update**

Wednesday, March 25th, 2:07 am EDT (UTC -4).

 

The hot-fix completed at 12.36 am EDT (UTC-4).

 

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



Emergency Maintenance Advisory for Tuesday, March 24th, 2015

 

 

Eloqua will be performing an emergency maintenance on Tuesday, March 24th, 2015, between 11 pm and 4 am EDT (UTC -4).

 

All application processing will be suspended during this window and resumed after downtime ends.

 

Downtime effect as follows. During portions of this maintenance period, the following platform features will be unavailable:

 

  • Email Sending (all types)
  • Inbound/Outbound CRM Integrations
  • Bulk API
  • Lead Scoring
  • Data Import/Exports
  • Campaign Processing

 

We recommend that customers not attempt to use the application at this time as rolling outages are anticipated. Inbound web tracking and form data will be captured, however, agent use of the platform can potentially result in work being lost. Once the maintenance is complete, all processing will resume and any work items scheduled to execute during the maintenance window will begin processing.

Our Cloud Operations Team is currently investigating an incident relating to email sending delays on POD 1 & 3 clients. We do not currently have an ETA for resolution. The next update will be on Monday March 23rd at approximately 10:00 am EDT (UTC -4).

 

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

**Update: Sunday, March 22nd 9:32 pm EDT (UTC -4)**

 

Our Cloud Operations Team has confirmed that this issue is now resolved.

 

After analysis by our support teams, it was determined that the incident resulted from a standard operating procedure error. The production use of your Eloqua service has been restored. The related standard operating procedure has been reviewed for improvement and for additional safeguards to avoid this issue in the future. Oracle is also reviewing the monitoring and alerting procedures related to the incident. After these reviews are completed, additional appropriate corrective actions identified during the reviews will be taken

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

**Update**

Sunday, March 22nd, 11:00 am EDT (UTC -4).

 

Our Cloud Operations Team has advised us that an estimated 1 more hour is required for them to complete the maintenance. Another scheduled update will be provided around 12:00 pm EST (UTC-5) today.

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

 

**Update**

Sunday, March 22nd, 11:43 am EDT (UTC -4).

 

Our Cloud Operations Team has completed the hot-fixes.

 

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



Emergency Maintenance Advisory for Sunday, March 22nd, 2015

 

 

Eloqua will be performing an emergency maintenance on Sunday, March 22nd, 2015, between 5 and 11 am EDT (UTC -4).

 

All application processing will be suspended during this window and resumed after downtime ends.

 

Downtime effect as follows. During portions of this maintenance period, the following platform features will be unavailable:

 

  • Email Sending (all types)
  • Inbound/Outbound CRM Integrations
  • Bulk API
  • Lead Scoring
  • Data Import/Exports
  • Campaign Processing

 

We recommend that customers not attempt to use the application at this time as rolling outages are anticipated. Inbound web tracking and form data will be captured, however, agent use of the platform can potentially result in work being lost. Once the maintenance is complete, all processing will resume and any work items scheduled to execute during the maintenance window will begin processing.

Our Cloud Operations Team and Development Team are currently investigating an incident impacting the performance of email bounce back processing queue for POD1 and POD 2 clients. We do not currently have an ETA for resolution, the next update is scheduled for Wednesday, March 18th, 10:00 am EDT (UTC -4).

 

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

**Update: Wednesday, March 18th 9:57 am EDT (UTC -4)**

 

Our Cloud Operations and Development Teams were able to resolve this incident fully as of 9:42 am EDT.

 

After analysis by our support teams, the root cause of the incident was not  determined.  At this time, production use of your Eloqua service has been  restored. Oracle is 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.

Our Cloud Operations Team is currently investigating an incident relating to email sending delays on POD 1. We do not currently have an ETA for resolution. The next update will be at approximately 6:30 pm EDT (UTC -4)

 

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

**Update: Tuesday, March 10th 6:27 pm EDT (UTC -4)**

 

Our Cloud Operations Team continues to aggressively work on resolving this incident. We are unable to provide an ETA at the moment. The next scheduled update will be at approximately 7:30 pm EDT (UTC-4).

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

**Update: Tuesday, March 10th 7:22 pm EDT (UTC -4)**

 

Our Cloud Operations Team continues to aggressively work on resolving this incident. We are unable to provide an ETA at the moment. The next scheduled update will be at approximately 8:30 pm EDT (UTC-4).

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

**Update: Tuesday, March 10th 8:39 pm EDT (UTC -4)**

 

Our Cloud Operations Team has confirmed that this issue is now resolved.

 

After analysis by our support teams, the root cause of the incident was not determined. At this time, production use of your Eloqua service has been restored. Oracle is 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.

Our Cloud Operations Team is currently investigating an incident where some clients are experiencing intermittent timeouts when logging into the Eloqua Application on POD3. We do not currently have an ETA for resolution. The next update will be at approximately 4:30 pm EST (UTC -5).


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

**Update**

Thursday, March 5th, 4:30 pm EST (UTC -5)


Our Cloud Operations Team has confirmed the incident is now resolved.


After analysis by our support teams, it was determined that the incident resulted from a configuration issue. The configuration 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.

Our Cloud Operations Team is currently investigating an incident relating to email sending delays on POD 3. We do not currently have an ETA for resolution. The next update will be at approximately 6:30 pm EST (UTC -5)

 

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

**Update: Wednesday, March 4th 6:37 pm EST (UTC -5)**

 

Our Cloud Operations Team continues to aggressively work on resolving this incident. We are unable to provide an ETA at the moment. The next scheduled update will be at approximately 7:30 pm EST (UTC-5).

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

**Update: Wednesday, March 4th 7:32 pm EST (UTC -5)**

 

Our Cloud Operations Team continues to aggressively work on resolving this incident. We are unable to provide an ETA at the moment. The next scheduled update will be at approximately 8:30 pm EST (UTC-5).

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

**Update: Wednesday, March 4th 8:28 pm EST (UTC -5)**

 

Our Cloud Operations Team continues to aggressively work on resolving this incident. We are unable to provide an ETA at the moment. The next scheduled update will be at approximately 9:30 pm EST (UTC-5).

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

**Update: Wednesday, March 4th 9:25 pm EST (UTC -5)**

 

Our Cloud Operations Team continues to aggressively work on resolving this incident. We are unable to provide an ETA at the moment. The next scheduled update will be at approximately 11:30 pm EST (UTC-5).

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

**Update: Wednesday, March 4th 11:25 pm EST (UTC -5)**

 

Our Cloud Operations Team reports that the email backlog is being consumed and the delay is diminishing. We do not have an ETA for resolution. The next update will be Thursday March 5th, at approximately 7:00 am EST (UTC -5).

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

**Update: Wednesday, March 5th 3:09 am EST (UTC -5)**

 

Our Cloud Operations Team has confirmed that this issue is now resolved.

 

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.

Eloqua will be performing an emergency hot-fix on Monday, March 2nd starting at 11:00 pm EST (UTC-5).


The impact of the Eloqua Service will be low, the service that we need to redeploy is related to Segmentation. There will be no outage during this hot-fix. We estimate the hot-fix will take around 3 hours to complete, however, our System Status page will be updated with our progress during the hot-fix.


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


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

**Update**

Tuesday, March 3rd, 12:33 am EST (UTC -5)

 

The hot-fix completed at 12:23 am EST (UTC-5)

Filter Blog

By date: By tag: