Skip navigation

Our Cloud Operations Team is currently investigating an incident that is impacting the availability of Insight on POD 1. We do not currently have an ETA for resolution, the next update is scheduled for 2:00 PM EDT (UTC -4).


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

**Update**

Friday, October 31st, 1:00 pm EDT (UTC -4)


Our Cloud Operations Team has restored access to Insight.

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 where clients are receiving an error message when logging into the Eloqua Application on POD1. We do not currently have an ETA for resolution. The next update will be at approximately 6:30 am EDT (UTC -4)

 

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

**Update**

Thursday, October 30th, 6:30 am EDT (UTC -4)


Our Cloud Operations Team continues to investigate this incident. The next update will be around 7:30 am EDT (UTC-4)


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

**Update**

Thursday, October 30th, 7:30 am EDT (UTC -4)


Upon further investigation, only some clients on POD 1 are impacted. Our Cloud Operations Team continues to investigate this incident. The next update will be around 8:30 am EDT (UTC-4)


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

**Update**

Thursday, October 30th, 8:23 am EDT (UTC -4)


Our Cloud Operations Team continues to aggressively troubleshoot this incident. The next scheduled update will be around 9:30 am EDT (UTC-4)


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

**Update**

Thursday, October 30th, 9:23 am EDT (UTC -4)


Our Cloud Operations Team continues to troubleshoot this incident. The next scheduled update will be around 10:30 am EDT (UTC-4)


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

**Update**

Thursday, October 30th, 10:13 am EDT (UTC -4)


Our Cloud Operations Team continues to troubleshoot this incident. The next scheduled update will be around 11:30 am EDT (UTC-4)


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

**Update**

Thursday, October 30th, 11:20 am EDT (UTC -4)


Upon further investigation, it has been confirmed that the incident still exists. Our Cloud Operations Team continues to troubleshoot this incident. The next scheduled update will be around 12:30 pm EDT (UTC-4)


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

**Update**

Thursday, October 30th, 12:28 pm EDT (UTC -4)


Our Cloud Operations Team have identified the incident and working towards a resolution. The next scheduled update will be around 1:30 pm EDT (UTC-4)


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

**Update**

Thursday, October 30th, 1:25 pm EDT (UTC -4)


Our Cloud Operations Team have identified the incident and still working towards a resolution. The next scheduled update will be around 2:30 pm EDT (UTC-4)


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

**Update**

Thursday, October 30th, 2:25 pm EDT (UTC -4)


Our Cloud Operations and Development Team are currently investigating the incident and still working towards a resolution. The next scheduled update will be around 3:30 pm EDT (UTC-4)


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

**Update**

Thursday, October 30th, 3:30 pm EDT (UTC -4)


Our Cloud Operations and Development Team are currently investigating the incident and still working towards a resolution. The next scheduled update will be around 5:30 pm EDT (UTC-4)


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

**Update**

Thursday, October 30th, 5:00 pm EDT (UTC -4)


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

Upon further investigation, the root cause of the incident was found to be the result of an event within the Customer's control authority. We recommend that the Customer work with Oracle Support to remediate the situation and put a long term corrective action in place.

Our Cloud Operations Team is currently investigating an incident that has resulted in a backlog of BULK API Exports. The next update will be at approximately 9:30 pm EDT (UTC -4)

 

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

**Update**

Tuesday, October 28th, 9:40 pm EDT (UTC -4)


Our Cloud Operations team has resolved this incident. Bulk Exports should now be processing normally.

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

**Update**

Sunday, November 2nd, 11:15 am EST (UTC -5).

 

The maintenance concluded on schedule and without incident.

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

 

Eloqua Fall '14 Release - Sunday, November 2nd, 2014

 

The Eloqua Fall '14 Release will roll out between 5 and 11 am EST (UTC -5), on Sunday, November 2nd, 2014.

 

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.

 

 

NOTE: Please check out our new product documentation site.

 

 

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

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 4:00 pm EDT (UTC -4)

 

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

**Update: Tuesday, October 28th 3:55 pm EDT (UTC -4)**

 

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 at approximately 5:00 pm EDT (UTC -4)

 

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

**Update: Tuesday, October 28th 4:36 pm EDT (UTC -4)**

 

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

Upon further investigation, the root cause of the incident was found to be the result of an event within the Customer's control authority. We recommend that the Customer work with Oracle Support to remediate the situation and put a long term corrective action in place.

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

**Update**

Wednesday, October 29th, 12:10 am EDT (UTC -4).

 

The maintenance concluded on schedule and without incident.

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

 

Eloqua Fall '14 Release - Service Pack 2


Service Pack 2 of the Eloqua Fall '14 Release will roll out between 11 pm, Tuesday, October 28th, and 5 am, Wednesday, October 29th, 2014

[all times EDT (UTC -4)].

 

 

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.

 


NOTE: Please check out our new product documentation site.

 

 

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 impacting the ability for some clients utilizing IP restrictions to log in to the application.  We do not currently have an ETA for resolution. The next update is scheduled for 9:30 am EDT (UTC - 4)

 

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

**Update: Monday, October 27th 9:39 am EDT (UTC -4)**

 

Our Cloud Operations Team is currently still investigating the root cause of this issue. The Next update will be around 10:30 am EDT (UTC -4)

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

**Update: Monday, October 27th 10:35 am EDT (UTC -4)**

 

Our Cloud Operations Team is currently working on implementing a fix for this incident. The next update will be around 11:30 am EDT (UTC - 4)

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

**Update: Monday, October 27th 11:07 am EDT (UTC -4)**

 

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 Development and  Cloud Operations Teams are currently working to resolve an incident that is impacting Bulk Imports and Exports, Lead Scoring and Firehose. We do not currentlty have an ETA for resolution. The next update is scheduled for 10:45 pm EDT ( UTC -4).

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

**Update**

Sunday, October 26th, 10:45 pm EDT (UTC -4)

 

Our development and Cloud Operations teams continue to work towards a resolution. Actions have been taken to alleviate the symptoms for Bulk Imports and Exports, Lead Scoring and Firehose in the interim. The next update will be around 11:45 pm EDT (UTC -4)

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

**Update**

Sunday, October 26th, 11:50 pm EDT (UTC -4)

 

The actions taken by our Development and Cloud Operations Teams have stabilized these services. Work is being done to correct the root cause of this incident. The next update will be Monday October 27th at 10:00 AM EDT (UTC -4)

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

**Update**

Monday, October 27th, 10:05 am EDT (UTC -4)

 

The services remain stabilized, however our Cloud Operations Team is working to determine the root cause of the incident. The next update will be around 12:00 pm EDT (UTC -4)

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

**Update**

Monday, October 27th, 12:00 pm EDT (UTC -4)

 

Our Cloud Operations Team is currently working to determine the root cause of the incident. The next update will be around 2:00 pm EDT (UTC -4)

 

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

**Update**

Monday, October 27th, 2:00 pm EDT (UTC -4)

 

Our Cloud Operations team is monitoring changes to confirm the resolution of this incident. The next update will be around 4:00 pm EDT (UTC -4)

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

**Update**

Monday, October 27th, 3:58 pm EDT (UTC -4)

 

Our Cloud Operations Team is currently still monitoring the affect of modifications made to confirm the resolution of this incident. The next update will be around 6:00 pm EDT (UTC -4)

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

**Update**

Monday, October 27th, 4:35 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 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.

Our Cloud Operations Team is currently investigating an incident that is impacting the sending of emails on POD 3. We do not currently have an ETA for resolution, the next update is scheduled for 6:00 PM EDT (UTC -4).

 

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

**Update**

Friday, October 24th, 5:00 pm EDT (UTC -4)

 

Our cloud operations team was able to resolve this issue as of 5:00 PM EDT (UTC -4) October 24th 2014.

Upon further investigation, the root cause of the incident was found to be the result of an event within the Customer's control authority. We recommend that the Customer work with Oracle Support to remediate the situation and put a long term corrective action in place.

We are currently experiencing intermittent timeouts and connection errors with Eloqua Insight. Our Cloud Operations Team is currently working alongside a vendor to resolve the underlying cause of the long load time on first connection.

Our teams have put in place additional monitoring and have taken measures to limit the length of these occurrences while we work towards a definitive resolution.

 

We are committed to providing daily updates until a resolution is found.

 

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

**Update**

Thursday, October 23rd, 12:45 pm EDT (UTC -4)

Our Cloud Operations Team continues to work alongside our vendor to come to a resolution. We will update this post again tomorrow with further information.

 

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

**Update**

Monday, October 27th, 2:10 pm EDT (UTC -4)

Our Cloud Operations Team has worked with the vendor to put in place measures to alleviate the root cause. Users should no longer be experiencing slow load on initial opening of Eloqua Insight.

 

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

**Update**

Tuesday, October 28th, 1:55 pm EDT (UTC -4)

Our Cloud Operations Team continues to work with a vendor to diagnose and correct the cause of these occurrences on POD 3. To clarify yesterday's update, on POD 1 changes have been put in place that do not resolve the root cause but do greatly reduce the occurrence and duration of incident.

 

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

**Update**

Wednesday, October 29th, 4:00 pm EDT (UTC -4)

Our Cloud Operations Team has made further changes to help alleviate the delays felt on POD 3. They continue to work alongside a vendor to find a resolution to the root cause of these issues.

 

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

**Update**

Thursday, October 30th, 3:00 pm EDT (UTC -4)

Our Cloud Operations Team continues to work with a vendor to diagnose and find a resolution to the root cause of these issues.

 

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

**Update**

Friday, October 31st, 2:45 pm EDT (UTC -4)

Our Cloud Operations Team continues to work alongside a vendor to find a resolution to the root cause of these issues.

 

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

**Update**

Tuesday, November 4th, 9:15 am EST (UTC -5)

Our Cloud Operations Team continues to monitor the workarounds put in place to ensure better stability on PODs 1 and 3, and continue to work alongside our vendors to find a resolution to the root cause.

 

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

**Update**

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

Our Cloud Operations Team continues to work with our vendor to come to a resolution of the root cause of these incidents.

 

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

**Update**

Thursday, November 6th, 2:40 pm EST (UTC -5)

Our Cloud Operations and Development Teams continue to collaborate with our vendor to identify and fix the root cause of these incidents, however at this time we cannot provide an ETA for resolution.

 

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

**Update**

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

Our Cloud Operations Team continues to work alongside our vendor to diagnose and rectify the cause of these incidents. We do not currently have an ETA for resolution.

 

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

**Update**

Monday, November 10th, 5:20 pm EST (UTC -5)

Our Cloud Operations Team continues to collaborate with development and our vendor to determine the root cause of these incidents. We do not currently have an ETA for resolution to provide.

 

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

**Update**

Tuesday, November 11th, 5:10 pm EST (UTC -5)

Our Cloud Operations Team continues to monitor the measures already implemented, and continue to work alongside our vendors to find a resolution to the root cause.


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

**Update**

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

Our Cloud Operations Team continues to work with our vendor to come to a resolution of the root cause of these incidents.


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

**Update**

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

Our Cloud Operations and Development Teams continue to collaborate with our vendor to identify and fix the root cause of these incidents, however at this time we cannot provide an ETA for resolution.

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

**Update**

Friday, November 14th, 4:55 pm EST (UTC -5)

Our Cloud Operations Team continues to work alongside our vendor to diagnose and rectify the cause of these incidents. We do not currently have an ETA for resolution.


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

**Update**

Monday, November 17th, 6:47 pm EST (UTC -5)

Our Cloud Operations Team continues to collaborate with development and our vendor to determine the root cause of these incidents. We do not currently have an ETA for resolution to provide.


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

**Update**

Tuesday, November 18th, 3:05 pm EST (UTC -5)

Our Cloud Operations Team continues to work with our vendor to come to a resolution of the root cause of these incidents.


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

**Update**

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

Our Cloud Operations Team continues to work alongside our vendor to diagnose and rectify the cause of these incidents. We do not currently have an ETA for resolution.


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

**Update**

Thursday, November 20th, 3:12 pm EST (UTC -5)

Our Cloud Operations Team continues to monitor the measures already implemented, and continue to work alongside our vendors to find a resolution to the root cause.


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

**Update**

Tuesday, November 25th, 9:08 am EST (UTC -5)

The measures put in place by our Cloud Operations Team have put in place have resolved the incidents of Eloqua Insight long load times. We will continue to monitor the situation, however at this time long load times with Insight are no longer being experienced.


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

**Update**

Sunday, October 26th, 9:45 pm EDT (UTC -4).

 

Our Development and  Cloud Operations Teams are currently working to resolve an incident that is impacting Bulk Imports and Exports, Lead Scoring and Firehose. We do not currentlty have an ETA for resolution.


Please follow GREEN / Bulk Import/Export, Lead Scoring, Firehose Impacted / POD 3 / RESOLVED for details on these issues.


No more updates will be provided via this Release Advisory post.

 

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

**Update**

Sunday, October 26th, 5:30 pm EDT (UTC -4).

 

One of the new Fall '14 Release features 'Inbound API logs' has been causing issues with retrieving API logs (inbound and outbound are timing out). As such, we are looking into rolling back this feature.

 

Lead Scoring – we're encountering an issue where scoring has not been updating since the rollout. We have not yet determined the scope or nature of this issue, but are working on it.

 

Another update will be provided later today.

 

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

**Update**

Sunday, October 26th, 3:15 pm EDT (UTC -4).

 

We are still investigating an issue with Cloud Actions and Cloud Decisions.

 

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

**Update**

Sunday, October 26th, 11 am EDT (UTC -4).

 

The maintenance concluded on schedule. We are currently investigating an issue with Cloud Actions and Cloud Decisions.

 

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

 

 

Eloqua Fall '14 Release - Sunday, October 26th, 2014

 

The Eloqua Fall '14 Release to Pod 3 has been pushed back 1 week. It is now confirmed for Sunday, October 26th, between 5 and 11 am EDT (UTC -4).


 

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.

 

 

NOTE: Please check out our new product documentation site.

 

 

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 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 affecting the use of email signature layouts within Eloqua Engage. This is currently affecting POD 2 customers and will affect POD 3 customers as of this Sunday, October 19th. We do not currently have an ETA for resolution but daily updates will be provided throughout this investigation.

 

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

**Update**

Friday, October 17th, 2:30 pm EDT (UTC -4)


Our Development Team has developed and tested a fix which will resolve the incident impacting signature layouts in Eloqua Engage. This fix will be deployed to POD 3 during our scheduled maintenance Sunday, October 19th. POD 2 will be resolved on Tuesday, October 21st, 2014.


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

**Update**

Monday, October 20th, 1:33 pm EDT (UTC -4)

 

The revised date for POD 3 is tentatively scheduled for Sunday, October 26th. POD 2 is still scheduled for Tuesday, October 21st.

 

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

**Update**

Tuesday, October 21th, 1:17 pm EDT (UTC -4)

 

We will be introducing the fix to POD 2 as part of our scheduled maintenance tonight and we have tentatively scheduled to deploy to POD 3 on Sunday, October 26th.

 

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

**Update**

Wednesday, October 22nd, 1:55 pm EDT (UTC -4)

 

The revised date for POD 2 is scheduled for Tuesday, October 28th. POD 3 is tentatively scheduled for Sunday, October 26th.

 

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

**Update**

Thursday, October 23rd, 11:26 am EDT (UTC -4)

 

The fix is scheduled for POD 2 for Tuesday, October 28th and is tentatively scheduled to be deployed to POD 3 on Sunday, October 26th.

 

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

**Update**

Friday, October 24th, 4:27 pm EDT (UTC -4)

 

POD 2 is scheduled for Tuesday, October 28th. The fix will be deployed to POD 3 which is tentatively scheduled for Sunday, October 26th.

 

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

**Update**

Monday, October 27th, 1:07 pm EDT (UTC -4)

 

The fix is currently scheduled to be deployed on POD 2 for Tuesday, October 28th.

 

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

**Update**

Tuesday, October 28th, 2:52 pm EDT (UTC -4)

 

The fix will be deployed on POD 2 tonight for Tuesday, October 28th.

 

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

**Update**

Wednesday, October 29th, 1:45 pm EDT (UTC -4)

 

The fix has been applied to POD 2 last night and is now resolved.

Our Cloud Operations Team is currently investigating an incident that is impacting the availability of Insight on POD 1. We do not currently have an ETA for resolution, the next update is scheduled for 7:00 AM EDT (UTC -4).


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

**Update**

Thursday, October 16th, 7:00 am EDT (UTC -4)


Our Cloud Operations Team has restored access to Insight.

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.



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

**Update**

Wednesday, October 15th.

 

The maintenance concluded on schedule and without incident.

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

 

Eloqua Fall '14 Release - Service Pack 1


Service Pack 1 of the Eloqua Fall '14 Release will roll out between 11 pm, Tuesday, October 14th, and 5 am, Wednesday, October 15th, 2014

[all times EDT (UTC -4)].

 

 

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.

 

NOTE: Please check out our new product documentation site.

 

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 impacting Bulk API Exports on POD1.  We do not currently have an ETA for resolution. The next update is scheduled for 10:00 am EDT (UTC -4)

 

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

**Update**

Tuesday, October 14th, 9:59 am EDT (UTC -4)


Our Cloud Operations Team is still actively investigating this incident, but we do not have an ETA at this time. The next update will be around 11:00 am EDT (UTC-4)


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

**Update**

Tuesday, October 14th, 11:00 am EDT (UTC -4)


Our Cloud Operations Team continues to investigate this incident. The next update will be around 12:00 pm EDT (UTC-4)


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

**Update**

Tuesday, October 14th, 12:00 pm EDT (UTC -4)


Our Cloud Operations Team is still currently investigating the incident. The next update will be around 1:00 pm EDT (UTC-4)


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

**Update**

Tuesday, October 14th, 1:00 pm EDT (UTC -4)


Our Cloud Operations Team continues to investigate this incident. The next update will be around 2:00 pm EDT (UTC-4)


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

**Update**

Tuesday, October 14th, 2:00 pm EDT (UTC -4)


Our Cloud Operations Team have identified the problem and are currently working towards a resolution. The next update will be around 3:00 pm EDT (UTC-4)


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

**Update**

Tuesday, October 14th, 3:00 pm EDT (UTC -4)


Our CloudOps Team have applied a fix which is currently decreasing the backlog. While we currently do not have an ETA for when the backlog will be completed, the next update will be around 4pm EDT (UTC -4)


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

**Update**

Tuesday, October 14th, 4:00 pm EDT (UTC -4)


Our CloudOps Team have applied the fix which is still currently decreasing the backlog queue. While we currently do not have an ETA for when the backlog will be completed, the next update will be around 5pm EDT (UTC -4)


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

**Update**

Tuesday, October 14th, 4:17 pm EDT (UTC -4)


This incident was fully resolved as of 4:17 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 that is impacting the availability of Insight on PODs 1 and 3. We do not currently have an ETA for resolution, the next update is scheduled for 5:30 AM EDT (UTC -4).


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

**Update**

Tuesday, October 14th, 5:29 am EDT (UTC -4)


Our Cloud Operations Team is currently still investigating the incident impacting POD3, however, Insight is now available for all POD1 clients. The next update will be around 6:30 am EDT (UTC -4)


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

**Update**

Tuesday, October 14th, 5:44 am EDT (UTC -4)


Our Cloud Operations Team was able to restore services for POD3 clients.


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 where Eloqua Insight is unavailable on POD 1 and 3. While we do not currently have an ETA, the next update is scheduled for 9:30 am EDT (UTC -4).


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

**Update**

Friday, October 10th, 8:53 am EDT (UTC -4)


Our Cloud Operations Team was able to restore services for our POD 3 customers and they are still aggressively working on POD 1. While we do not currently have an ETA, the next update is scheduled for 10:00 am EDT (UTC -4).


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

**Update**

Friday, October 10th, 9:14 am EDT (UTC -4)


Our Cloud Operations Team was able to restore services for our POD 1 customers as well.


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 that is impacting the availability of Insight on PODs 1 and 3. We do not currently have an ETA for resolution, the next update is scheduled for 7:00 AM EDT (UTC -4).


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

**Update**

Thursday, October 9th 6:22 AM EDT (UTC-4)


This incident was fully resolved as of 6:15 AM 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 Development Team is actively investigating an incident where Segments containing the Form Submits criteria are incorrectly calculating. We recommend clients review any campaigns that may be configured with this. While we currently do not have an ETA, we will provide another update around 1:00 pm EDT (UTC-4).

 

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

**Update**

Wednesday, October 8th, 11:38 am EDT (UTC -4)


Our Development Team has crafted a hot-fix for this incident. While it is currently making it way through our hot-fix process, the team is targeting to get this pushed to production within the next few hours. We will provide another update around 1:00 pm EDT (UTC-4).


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

**Update**

Wednesday, October 8th, 12:51 pm EDT (UTC -4)


Our Development and Development Operations Team are still working though the hot-fix process. We will provide another update around 2:30 pm EDT (UTC-4).


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

**Update**

Wednesday, October 8th, 2:26 pm EDT (UTC -4)


Our Development and Development Operations Team continue to work through the hot-fix process. We are still targeting to get this completed before the end of the day. We will provide another update around 4:30 pm EDT (UTC-4).


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

**Update**

Wednesday, October 8th, 4:19 pm EDT (UTC -4)


Our Cloud Operations Team is currently working through the final steps of the hot-fix process. We will provide another update around 6:30 pm EDT (UTC-4).


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

**Update**

Wednesday, October 8th, 5:00 pm EDT (UTC -4)


This incident has been hot-fixed to Production and considered resolved.

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

**Update**

Wednesday, October 8th, 3:30 am EDT (UTC -4)

 

The maintenance concluded on schedule.

 

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


Eloqua Fall '14 Release


The Eloqua Fall '14 Release will roll out between 11 pm, Tuesday, October 7th, and 5 am, Wednesday, October 8th, 2014 [all times EDT (UTC -4)].

 

 

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.

 

 

NOTE: Please join us for a Fall ’14 Release Review and Q&A with Product Management at noon EDT on Friday, Oct 10th. Download the calendar meeting here: http://goo.gl/K2BKqP.

 

 

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

As of 03-OCT-2014, Oracle Cloud Team has completed applying patches for vulnerability CVE-2014-7169 against those systems that were determined to be vulnerable in Oracle Eloqua. Customers should refer to the published Security Alert Advisory for more information about the technical content of these patches.  Oracle continues to monitor reports of additional CVEs related to Bash, and will address vulnerabilities in accordance with its vulnerability handling policies.

 

For More Information:

 

The advisory for Security Alert CVE-2014-7169 is located at http://www.oracle.com/technetwork/topics/security/alert-cve-2014-7169-2303276.html


More information has also been published at http://www.oracle.com/technetwork/topics/security/bashcve-2014-7169-2317675.html


The Oracle Software Security Assurance web site is located at http://www.oracle.com/us/support/assurance

Our Cloud Operations Team is currently investigating an incident that is intermittently impacting the availability of Insight on PODs 1 and 3. We do not currently have an ETA for resolution, the next update is scheduled for 9:30 AM EDT (UTC -4).


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

Update: Monday, October 6th 2014 9:34 EDT (UTC -4)


Our Cloud Operations Team is currently still investigating the cause of this incident. The next update will be around 10:30 AM EDT (UTC -4)


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

**Update**

Monday, October 6th 10:10 AM EDT (UTC-4)


This incident was fully resolved as of 10:10 AM 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 has identified a backlog with the Data Import Queues for POD1. We are estimating within 2 hours the queues should be cleared up.

 

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

**Update**

Thursday, October 2nd, 9:25 am EDT (UTC -4)

 

Our Cloud Operations Team has confirmed the Data Import Queues are now healthy.

Our Cloud Operations Team investigated and resolved an incident where Emails Sends from POD 1 were impacted. There is currently a backlog and the queues are processing. We estimate the queues should clear up within the next hour.

 

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

**Update**

Thursday, October 2nd, 2:17 am EDT (UTC -4)


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**

Thursday, October 2nd, 9:26 am EDT (UTC -4)

 

Our Cloud Operations Team has confirmed our Email Queues are now healthy.

Our Cloud Operations Team is currently investigating an incident that is impacting the availability of Insight on PODs 1 and 3. We do not currently have an ETA for resolution, the next update is scheduled for 6:30 AM EDT (UTC -4).


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

**Update**

Wednesday, October 1st 6:30 AM EDT (UTC-4)

 

Our cloud operations team is still currently investigating the incident. The next update will be around 7:30 AM EDT (UTC -4)


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

**Update**

Wednesday, October 1st 6:45 AM EDT (UTC-4)


This incident was fully resolved as of 6:45 AM 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.


Filter Blog

By date: By tag: