Skip navigation


Eloqua Fall '14 Release


The Eloqua 467 Release will roll out between 11 pm, Tuesday, December 2nd, and 5 am, Wednesday, December 3rd, 2014 [all times EST (UTC -5)].

 

 

Please review the supporting resources available in the Oracle Eloqua Release Center. This includes Release Notes for both Eloqua 9 Release Notes 2014 and Eloqua 10 Release Notes 2014, 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 that is impacting the ability to log into the application on POD1. We do not currently have an ETA for resolution. We will update this post at approximately 11:30 am EST (UTC-5)

 

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

**Update**

Wednesday, November 19th, 10:54 am EST (UTC-5)


Our Cloud Operations Team continues to investigate this incident. The impact of this extends past login and is causing landing pages and forms to be unreachable. The next update will be at approximately 11:30 am EST (UTC-5)


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

**Update**

Wednesday, November 19th, 11:31 am EST (UTC-5)


Our Cloud Operations Team continues to investigate this incident. We do not currently have an ETA for resolution. The next update will be at approximately 12:30 pm EST (UTC-5)


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

**Update**

Wednesday, November 19th, 12:30 pm EST (UTC-5)


Our Cloud Operations team has put in place measures to resolve this incident. Performance is returning to normal, however we will continue to monitor the situation. The next update will be at approximately 1:30 pm EST (UTC-5)


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

**Update**

Wednesday, November 19th, 1:30 pm EST (UTC-5)


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.

 

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

**Update**

Thursday, November 20th, 10:32 am EST (UTC-5)


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.

Please be advised, due to an unrecoverable hardware failure, an immediate migration of clients on a specific Database is currently underway by our Cloud Operations Team. We estimate the migration to take around 90 minutes and the next scheduled update will be around 7:00pm EST (UTC-5).

 

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

**Update**

Thursday, November 13th, 6:57 pm EST (UTC-5)


Our Cloud Operations Team continues to work on the migration. The original estimate was not sufficient and we are unable to provide an ETA at this time. For the clients affected by this incident, it should be noted that all application processing was paused during this window and inbound form data will be captured. Once the migration is complete, all processing will resume and any work items scheduled to execute during the migration window will begin processing. The next scheduled update will be around 7:45 pm EST (UTC-5).


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

**Update**

Thursday, November 13th, 7:11 pm EST (UTC-5)


Our Cloud Operations Team is targeting to have the migration completed by 8:00 pm EST (UTC-5). The next scheduled update will be around 8:10 pm EST (UTC-5).


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

**Update**

Thursday, November 13th, 8:06 pm EST (UTC-5)


Our Cloud Operations Team is completing the final phases of the migration. The next scheduled update will be around 8:30 pm EST (UTC-5).


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

**Update**

Thursday, November 13th, 8:25 pm EST (UTC-5)


Our Cloud Operations Team have completed the migration. 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.

With the pending change Salesforce.com is making to disable SSL 3.0 in favour of TLS 1.0 or higher (https://help.salesforce.com/apex/HTViewSolution?urlname=Salesforce-disabling-SSL-3-0-encryption&language=en_US), testing has shown this does not affect our client's Eloqua to Salesforce.com integration. The integration will continue to function normally.

Scheduled Maintenance Advisory for Sunday, November 9th, 2014

 

 

Eloqua will be performing scheduled maintenance on Sunday, November 9th, 2014, between 8 and 10 am EST (UTC -5).

 

Downtime effect as follows:

 

  • No major blackout is expected during this software upgrade, but very short term traffic interruptions may possibly occur.

 

 

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

 

 

To determine if you are on Pod3:

Log into Eloqua as you normally would.

Look at the browser URL once you are logged in.

Pod3 URL has the following format - secure.p03.eloqua.com...... (note:  03 included in URL)

Our Development Team is currently investigating an incident that is causing a server error to appear on landing pages containing cloud applications. We have no ETA for resolution at this time. The next update will be at approximately 10:00 pm EST (UTC -5).

 

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

**Update**

Wednesday, November 5th, 10:00 pm EST (UTC-5)

Our Development and Cloud Operations Teams are working together to investigate this incident and work towards a resolution. The next update will be at approximately 11:00 pm EST (UTC -5).


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

**Update**

Wednesday, November 5th, 10:25 pm EST (UTC-5)


Our Development and Cloud Operations Teams have resolved this incident as of 10:20 pm EST (UTC -5).

We are currently tracking an incident where some users are receiving a permission error while saving a segment. Our Development Team is working on a path to resolution and are targeting to hot-fix this incident by end of day today. We will provide another update around 3:00 pm EST (UTC-5).

 

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

**Update**

Monday, November 3rd, 3:20 pm EST (UTC-5)


Our Development Team continues to work on this resolution and are still targeting to deploy this hot-fix by end of day. The next scheduled update will be around 6:00 pm EST (UTC-5).


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

**Update**

Monday, November 3rd, 6:20 pm EST (UTC-5)


Our Cloud Operations Team confirmed the hot-fix was applied to our Production Environment.

 

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

**Update**

Monday, November 3rd, 7:04 pm EST (UTC-5)


Our Cloud Operations Team has identified a false positive and a small percentage of clients failed deployment of the hot-fix. Our Development Team is closely working with them to resolve this in full. We are unable to provide an ETA, but the next scheduled update will be 10:00 am EST (UTC-5) on Tuesday, November 4th, 2014.

 

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

**Update**

Tuesday, November 4th, 10:00 am EST (UTC-5)


Our Cloud Operations and Development Team continue to work towards resolution, however no ETA is available. The next scheduled update will be around 1:00 pm EST (UTC-5).

 

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

**Update**

Tuesday, November 4th, 1:00 pm EST (UTC-5)


Our Development Team continue to work on a hot-fix that will address the small percentage of clients still experiencing the issue. There is no ETA available but the next scheduled update will be around 4:00 pm EST (UTC-5).

 

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

**Update**

Tuesday, November 4th, 4:00 pm EST (UTC-5)


Our Development Team continues to work on this resolution. We are unable to provide an ETA, but the next scheduled update will be around 10:00 am EST (UTC-5) on Wednesday, November 5th, 2014.

 

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

**Update**

Wednesday, November 5th, 10:10 am EST (UTC-5)

Our Development Team is currently reviewing a fix for this incident. We are currently unable to provide an ETA for when this fix will be applied. The next update will be at approximately 1:00 pm EST (UTC -5)


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

**Update**

Wednesday, November 5th, 12:55 pm EST (UTC-5)

Our Development Team is still reviewing a fix for this incident. We are currently unable to provide an ETA for when this fix will be applied. The next update will be at approximately 4:00 pm EST (UTC -5)


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

**Update**

Wednesday, November 5th, 4:00 pm EST (UTC-5)

Our Development Team continues to review the fix for this incident. We are currently unable to provide an ETA for when this fix will be applied. The next update will be around 10:00 am EST (UTC-5) on Thursday, November 6th, 2014.


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

**Update**

Thursday, November 6th, 10:00 am EST (UTC-5)

Our Development Team is working to fully test a fix for this incident. We cannot at this time provide an ETA. The next update will be at approximately 1:00 pm EST (UTC -5)


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

**Update**

Thursday, November 6th, 1:00 pm EST (UTC-5)

Our Development Team is still testing a fix for this incident. We cannot at this time provide an ETA. The next update will be at approximately 4:00 pm EST (UTC -5)


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

**Update**

Thursday, November 6th, 4:00 pm EST (UTC-5)

Our Development Team continues to test a fix for this incident. We cannot at this time provide an ETA. The next update will be at approximately 10:00 am EST (UTC-5) on Friday, November 7th, 2014.


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

**Update**

Friday, November 7th, 10:00 am EST (UTC-5)

Our Development Team is still working to fully test the fix for this incident. We cannot at this time provide an ETA. The next update will be at approximately 1:00 pm EST (UTC-5)


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

**Update**

Friday, November 7th, 1:00 pm EST (UTC-5)

Our Clouds Operations Team is targeting to hot-fix this incident by end of day today. We will provide another update at approximately 4:00 pm EST (UTC-5)


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

**Update**

Friday, November 7th, 3:00 pm EST (UTC-5)

Our Cloud Operations Team has confirmed that the fix has been applied to our Production Environment and the issue is now resolved.

Filter Blog

By date: By tag: