Skip navigation

**UPDATE**

Sunday, December 1st

 

Maintenance concluded within the scheduled timeframe and without issues.


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


Maintenance Advisory for Sunday, December 1st, 2013

 

 

Eloqua will be performing maintenance and hardware upgrades on Sunday, December 1st, between 6 and 9 AM EST (UTC -5).

 

During this maintenance period:

 

• All inbound activity will be lost (e.g. page views, email responses)

• Forms and email responses will be lost during hardware reboots (5-10 minutes)

• Application processing will be paused, and resumed after maintenance completes

 

You are advised to avoid using the application during this window.

 

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

**UPDATE**

Sunday, November 20th, 1:00 am EST (UTC -5)

 

Service Pack 4 of the Eloqua Fall '13 Release concluded within the scheduled timeframe and without issues.


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


Eloqua Fall '13 - SP4

 

Service Pack 4 of the Fall '13 Release will begin at 11 pm EST (UTC -5), Tuesday, November 19th, 2013, and will conclude by 5 am EST, Wednesday, November 20th.



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 window. 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).

**UPDATE**

Sunday, November 17th, 11:30 am EST (UTC -5)

 

Service Pack 4 of the Eloqua Fall '13 Release concluded within the scheduled timeframe and without issues.


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



Eloqua Fall '13 - SP4

 

Please review the supporting resources available in the Oracle Eloqua Release Center.

 

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.


Service Pack 4 of the Fall '13 Release will roll out between 5 and 11 am EST (UTC -5), Sunday, November 17th, 2013.

 

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 window. You are advised to avoid using the application during this window.

 

To determine if you are on Pod1:

Log into Eloqua as you normally would.

Look at the browser URL once you are logged in.

Pod1 URL has the following format - www.secure.eloqua.com/...  (note:  no number included in URL).

 

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 Production Team is currently investigating an incident where POD 1 clients are unable to access Eloqua Insight.

 

To determine if you are on Pod1:

Log into Eloqua as you normally would.

Look at the browser URL once you are logged in.

Pod1 URL has the following format - www.secure.eloqua.com/...  (note:  no number included in URL).

 

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

**Update**

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


The Eloqua Services has been restored as of 10:16 pm EST (UTC-5).

 

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

**Update**

Wednesday, November 13th, 10:36 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.

Our Development Team identified an intermittent issue where transactional (notifications) emails were not being sent. We currently don’t have an ETA to share, but our next schedule update on this incident will be Thursday, November 21st around 4:00 pm EST (UTC -5).

 

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

**Update**

Monday, November 25th, 11:12 am EST (UTC -5)

 

Our Development Team is still working on this incident. We currently don’t have an ETA to share, but our next schedule update on this incident will be Friday, November 29th around 2:00 pm EST (UTC -5).

 

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

**Update**

Friday, November 29th, 1:14 pm EST (UTC -5)

 

Our Development Team has implemented additional logging to help diagnose this incident. Unfortunately we have still not been able to determine the root cause, and an ETA is not yet available. Our next update will be on Friday, December 6th around 2:00 pm EST (UTC -5).

 

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

**Update**

Friday, December 12th, 10:46 am EST (UTC -5)

 

Our Development Team continues to investigate this incident, but we have not identified anything tangible yet. We are not able to provide an ETA and our next update will be on Friday, December 13th around 2:00 pm EST (UTC -5).

 

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

**Update**

Monday, December 16th, 10:18 am EST (UTC -5)

 

Our Development Team continues to investigate this incident. We are not able to provide an ETA and our next update will be on Friday, December 20th around 2:00 pm EST (UTC -5).

 

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

**Update**

Monday, January 6th, 10:14 am EST (UTC -5)

 

Our Development Team continues to investigate this incident. We are not able to provide an ETA and our next update will be on Friday, January 10th around 2:00 pm EST (UTC -5).

 

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

**Update**

Monday, January 10th, 10:14 am EST (UTC -5)

 

Our Development Team continues to investigate this incident. We are not able to provide an ETA and our next update will be on Friday, January 17th around 2:00 pm EST (UTC -5).

 

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

**Update**

Sunday, January 19th, 7:36 am EST (UTC -5)

 

Our Development Team identified 4 hot-fixes that should help improve this incident. Today, starting at 7:00 am EST (UTC-5), our Production Team started the hot-fix process. In the new few days, we will re-scope this incident given this change and identify our next steps.  Our next update will be on Wednesday, January 22nd around 2:00 pm EST (UTC -5).

 

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

**Update**

Sunday, January 27th, 10:53 am EST (UTC -5)

 

The Development and Production Team were able to hot-fix the 4 incidents. We continue to monitor our logs. Our next update will be on Friday, January 31st around 2:00 pm EST (UTC -5).

 

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

**Update**

Friday, January 31st, 9:08 am EST (UTC -5)

 

The Development and Production Team continue to monitor our logs. The hot-fixes introduced did assist in minimizing the overall impact of this incident, but not 100%. Our next update will be on Friday, February 7th around 2:00 pm EST (UTC -5).

 

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

**Update**

Friday, January 31st, 9:08 am EST (UTC -5)

 

The Development and Cloud Operation Team continues to monitor situation. We have not received any net new reports of this incident since the hot-fix was introduced.

We are aware the Eloqua Application is inaccessible for all clients and our Production Team is currently working to resolve this. The next scheduled update will be at 9:00 pm EST (UTC-5).

 

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

**Update**

Monday, November 11th, 8:17 pm EST (UTC -5)


The Eloqua Services has been restored.

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

**Update**

Monday, November 11th, 8:24 pm 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.

**Update**

Wednesday, November 6th, 11:40 pm EST (UTC -5)


Insight maintenance successfully concluded at 11:24 pm EST.

 

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


Insight Reporting Maintenance Advisory for Wednesday, November 6th, 2013

 

Emergency Insight maintenance will take place tonight (November 6th) between 9:30 pm and 11:30 pm EST (UTC -5).

 

During this maintenance period:

 

• Non-Insight functionality will not be impacted

• Insight will be intermittently unavailable during the maintenance window

• Please avoid using Insight during the maintenance window to avoid losing work

 

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

On November 4th, between 12:33 PM EST and 1:16 PM EST, you may have experienced performance issues with Eloqua Insight.

 

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

Wednesday, November 6th, 12:30 am EST (UTC -5)


The SP3 rollout concluded successfully at 12:05 am EST.

 

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


Eloqua Fall '13 - SP3

 

Please review the supporting resources available in the Oracle Eloqua Release Center.

 

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.

 

Service Pack 3 of the Fall '13 Release will begin at 11 pm EST (UTC -5), Tuesday, November 5th, 2013, and will conclude by 5 am EST, Wednesday, November 6th.

 

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 window. 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).

During the Fall Service Pack 2 Release, our BETA editors were enabled for all Eloqua 10 clients. Our Development Team is working aggressively to reverse this change. At this time we are unable to provide an ETA, but the next scheduled update will be on Monday, November 4th, 2013 around 1:30 pm EDT (UTC-5).

 

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

**Update**

Monday, November 4th, 10:44 am EDT (UTC -5)


The Development Team is still working on a path to resolution. At this time, we cannot provide an ETA, but our next schedule update on this incident will be Tuesday, November 5th around 1:30 pm EDT (UTC -5)

 

We also recognize not everyone would want to participate in this beta as it may have unforeseen impacts on your content creation/management experience. For those clients asking to stay on the BETA, please contact our Support Team. Once this incident has been reverted, those who have asked explicitly to stay on, will be.

 

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

**Update**

Tuesday, November 5th, 11:17 am EDT (UTC -5)


The Development Team is aggressively targeting to resolve this incident this week. At this time, we cannot provide an ETA, but our next schedule update on this incident will be Wednesday, November 6th around 1:30 pm EDT (UTC -5)

 

We also recognize not everyone would want to participate in this beta as it may have unforeseen impacts on your content creation/management experience. For those clients asking to stay on the BETA, please contact our Support Team. Once this incident has been reverted, those who have asked explicitly to stay on, will be.

 

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

**Update**

Wednesday, November 6th, 2:05 pm EDT (UTC -5)


The Development Team is aggressively targeting to resolve this incident. At this time, we cannot provide an ETA, but our next schedule update on this incident will be Friday, November 8th around 1:30 pm EDT (UTC -5)

 

We also recognize not everyone would want to participate in this beta as it may have unforeseen impacts on your content creation/management experience. For those clients asking to stay on the BETA, please contact our Support Team. Once this incident has been reverted, those who have asked explicitly to stay on, will be.

 

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

**Update**

Monday, November 11th, 9:21 am EDT (UTC -5)


The Development Team is aggressively targeting to resolve this incident. At this time, we cannot provide an ETA, but our next schedule update on this incident will be Tuesday, November 12th around 1:30 pm EDT (UTC -5)


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

**Update**

Tuesday, November 12th, 1:23 pm EST (UTC -5)


The Development Team is still aggressively targeting to resolve this incident. At this time, we cannot provide an ETA, but our next schedule update on this incident will be around 4:00 pm EST (UTC -5)

 

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

**Update**

Tuesday, November 12th, 3:52 pm EST (UTC -5)


The Development Team is still aggressively targeting to resolve this incident. At this time, we cannot provide an ETA, but our next schedule update on this incident will be around 7:00 pm EST (UTC -5)


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

**Update**

Tuesday, November 12th, 6:40 pm EST (UTC -5)


The Development Team is targeting to resolve this incident. At this time, we cannot provide an ETA, but our next schedule update on this incident will be Thursday, November 14th around 1:30 pm EST (UTC -5)


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

**Update**

Tuesday, November 12th, 8:06 pm EST (UTC -5)


We were able to hot-fix this incident against all PODs completing at 7.55 pm EST (UTC-5) tonight. This incident is now resolved.

Maintenance Advisory: Sunday, November 3rd, 2013


Eloqua will be performing maintenance and hardware upgrades on Sunday, November 3rd, between 5:00 AM and 6:00 AM EDT (UTC -5).

 

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 (application processing will be paused and resumed after downtime ends)

• All inbound activity will be lost (e.g. page views, email responses)

• Forms will captured in offline mode and re-processed after downtime ends

 

There will also be intermittent downtime during this window. You are advised to avoid using the application during this window.

 

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

 

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)

 

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

**Update**

Sunday, November 3rd, 6:07 am EDT (UTC -5)


The maintenance was completed on time.

Eloqua Fall '13 - SP3

 

Please review the supporting resources available in the Oracle Eloqua Release Center.

 

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.

 

Service Pack 3 of the Fall '13 Release will roll out between 5 and 11 am EDT (UTC -5), Sunday, November 3rd, 2013.

 

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 window. You are advised to avoid using the application during this window.

 

To determine if you are on Pod1:

Log into Eloqua as you normally would.

Look at the browser URL once you are logged in.

Pod1 URL has the following format - www.secure.eloqua.com/...  (note:  no number included in URL).

 

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)

 

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

**Update**

Sunday, November 3rd, 11:05 am EDT (UTC -5)


The roll out was completed on time.

Between 10:43 am EDT and 11:04 am EDT today, some clients on POD1 would have experienced some performance issues.

 

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

 

To determine if you are on Pod1:

Log into Eloqua as you normally would.

Look at the browser URL once you are logged in.

Pod1 URL has the following format - www.secure.eloqua.com/...  (note:  no number included in URL).

Filter Blog

By date: By tag: