Skip navigation

The Development and Cloud Operations teams are currently investigating an issue related to the import purpose of "link opportunities to contacts through accounts" causing data imports to stall.  We are currently unable to provide an ETA and the next update will be around 10:00 am EDT (UTC-4) today.


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

**Update**

Monday, March 31st, 10:06 am EDT (UTC -4)

 

The Development Team continues to investigate the incident related to the imports with "link opportunities to contacts through accounts" while our Cloud Operations Team continues to monitor the overall queue. We are unable to expedite the consumption of the backlog as well as provide an ETA for full resolution. The next scheduled update will be around 11:30 am EDT (UTC-4).

 

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

**Update**

Monday, March 31st, 11:34 am EDT (UTC -4)

 

The Development Team believes they have identified the root cause and are working on building a solution. We are targeting a hot-fix for later today. Please note, this incident also impacts users are on POD3. The next scheduled update will be around 1:30 pm EDT (UTC-4).


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

**Update**

Monday, March 31st, 1:30 pm EDT (UTC -4)

 

The Development Team continues on building a solution with the target of hot-fixing the incident later today. The next scheduled update will be around 3:30 pm EDT (UTC-4).


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

**Update**

Monday, March 31st, 3:35 pm EDT (UTC -4)

 

The Development Team encountered additional complexities to the incident and the initial solution failed testing. They continue to investigate alternative solutions, however, in the interim, they are applying two specific data fixes to help improve the backlog situation. The next scheduled update will be around 5:00 pm EDT (UTC-4).


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

**Update**

Monday, March 31st, 4:54 pm EDT (UTC -4)

 

The Development Team continues to investigate alternative solutions for the root cause. Cloud Operations Team continues to monitor the overall queue as we can confirm items in the queue are being executed. The next scheduled update will be around 9:30 am EDT (UTC-4), Tuesday, April 1st, 2014.


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

**Update**

Monday, March 31st, 10:25 pm EDT (UTC -4)

 

The QA team is testing the proposed fix. Cloud Operations Team continues to monitor the overall queue as we can confirm items in the queue are being executed. The next scheduled update will be no later than 9:30 am EDT (UTC-4), Tuesday, April 1st, 2014.


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

**Update**

Monday, March 31st, 11:30 pm EDT (UTC -4)

 

The issue was resolved at 11:20 pm EDT. The backlog of data imports is processing.


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

**Update**

Tuesday, April 1st, 9:46 am EDT (UTC -4)

 

After analysis by our support teams, it was determined that the incident was the result of a software bug in Eloqua. 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.

Eloqua Winter '14 Release



The Winter '14 Release rollout completed at 8:25 pm EDT.

 

 

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.

 

 

 

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

Sunday, March 30th, 12:20 PM EDT (UTC -4)

 

The Winter '14 Release code rollout has still not concluded.

 

The next update will be provided by 1:20 PM EDT (UTC -4).

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

**Update**

Sunday, March 30th, 1:20 PM EDT (UTC -4)

 

The Winter '14 Release code rollout is still ongoing.

 

The next update will be provided by 2:20 PM EDT (UTC -4).

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

**Update**

Sunday, March 30th, 2:20 PM EDT (UTC -4)

 

The Winter '14 Release code rollout is still ongoing.

 

The next update will be provided by 3:45 PM EDT (UTC -4).

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


**Update**

Sunday, March 30th, 3:45 PM EDT (UTC -4)

 

The Winter '14 Release code rollout is still ongoing.

 

The next update will be provided by 5:15 PM EDT (UTC -4).

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

**Update**

Sunday, March 30th, 5:35 PM EDT (UTC -4)

 

The Winter '14 Release code rollout is still ongoing.

 

The next update will be provided by 6:45 PM EDT (UTC -4).

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

**Update**

Sunday, March 30th, 6:45 PM EDT (UTC -4)

 

The Winter '14 Release code rollout is still ongoing.

 

The next update will be provided by 7:30 PM EDT (UTC -4).

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

**Update**

Sunday, March 30th, 7:30 PM EDT (UTC -4)

 

The Winter '14 Release code rollout is still ongoing.

 

The next update will be provided by 8:30 PM EDT (UTC -4).

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

**Update**

Sunday, March 30th, 8:30 PM EDT (UTC -4)

 

The Winter '14 Release rollout completed at 8:25 pm EDT.

 

Note that there may be delays in outgoing email as the backlog processes.

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


Eloqua Winter '14 Release - Service Pack 3



Service Pack 3 of the Winter '14 Release successfully rolled out between 5 and 11 am EDT (UTC -4), on Sunday, March 30th, 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.

 

 

 

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)

The Cloud Operations Team is currently investigating an intermittent issue affecting a small number of POD 1 clients. We are currently unable to provide an ETA, the next scheduled update is 11:00 AM EDT (UTC-4) today.

 

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

**Update**

Friday March 28th, 11:24 AM EDT (UTC -4)

 

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.

 

 

The issue will be marked as resolved once the affected hardware has been fully replaced, however the affected clients should no longer experience this issue.

 

The next update will be provided at 2 PM EDT (UTC-4) today.

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


**Update**

Friday March 28th, 2:04 PM EDT (UTC -4)

This issue is now fully resolved.


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

Eloqua will be performing an emergency hot-fix on Wednesday, March 26th starting at 8:00 pm EDT (UTC-4).


The impact of the Eloqua Service will be moderate, the service that we need to redeploy is related Bulk API imports and exports. There will be a Bulk API service outage during this hot-fix. We estimate the hot-fix will take around 30 minutes to complete, however, our System Status page on Topliners 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**

Wednesday, March 26th, 8:11 pm EDT (UTC -4)

 

The hot-fix completed at 8.07 pm EDT (UTC-4)

The Development and Cloud Operations teams are currently investigating the performance incident on POD 1 and POD 3 related to Bulk API. While we are unable to provide an ETA and the next scheduled update will be around 12:30pm EDT (UTC-4) today.


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

**Update**

Tuesday, March 25th, 11:50 am EDT (UTC -4)

 

The Development and Cloud Operations continues to investigate and monitor the situation. We are unable to provide an ETA, but the next scheduled update will be around 2:30pm EDT (UTC-4). Please note we have split the alerts so future updates are respective of the specific PODs.


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

**Update**

Tuesday, March 25th, 1:55 pm EDT (UTC -4)

 

This was resolved at 1.00 pm EDT. 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.

The Development and Cloud Operations teams are currently investigating the performance incident on POD 1 and POD 3 related to Bulk API. While we are unable to provide an ETA and the next scheduled update will be around 12:30pm EDT (UTC-4) today.


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

**Update**

Tuesday, March 25th, 11:50 am EDT (UTC -4)

 

The Development and Cloud Operations continues to investigate and monitor the situation. We are unable to provide an ETA, but the next scheduled update will be around 2:30pm EDT (UTC-4). Please note we have split the alerts so future updates are respective of the specific PODs.

 

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

**Update**

Tuesday, March 25th, 2:33 pm EDT (UTC -4)

 

The Development and Cloud Operations continues to investigate and monitor the situation. We are unable to provide an ETA, but the next scheduled update will be around 5:30pm EDT (UTC-4).


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

**Update**

Wednesday, March 26th, 12:20 am EDT (UTC -4)

 

The Development and Cloud Operations were able to restore services, however they continue monitor the situation. We are unable to provide an ETA, but the next scheduled update will be around 11:30 am EDT (UTC-4) today.


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

**Update**

Wednesday, March 26th, 11:39 am EDT (UTC -4)

 

The Development and Cloud Operations continue monitor the situation. We are unable to provide an ETA, but the next scheduled update will be around 4:00 pm EDT (UTC-4) today.


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

**Update**

Wednesday, March 26th, 3:57 pm EDT (UTC -4)

 

The Development and Cloud Operations continue monitor the situation. We are unable to provide an ETA, but the next scheduled update will be around 11:30am EDT (UTC-4) on Thursday, March 27th, 2014.


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

**Update**

Thursday, March 27th, 12:26 pm EDT (UTC -4)

 

This incident is now resolved. The Development and Cloud Operations will continue monitor the situation. 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.

Eloqua will be performing an emergency hot-fix on Monday, March 24th starting at 8:00 pm EDT (UTC-4).


The impact of the Eloqua Service will be moderate, the service that we need to redeploy is related Bulk API imports and exports. There will be a Bulk API service outage during this hot-fix. We estimate the hot-fix will take around 30 minutes to complete, however, our System Status page on Topliners 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**

Monday, March 24th, 8:39 pm EDT (UTC -4)

 

The hot-fix completed at 8.36 pm EDT (UTC-4)

Eloqua will be performing maintenance on Sunday, March 23rd, between 5 and 11 am EDT (UTC -4).

 

While the application may remain accessible during this time, web application performance will be effected.

 

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

 

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

 

**UPDATE**

Sunday, March 23rd, 2014.

 

Maintenance concluded on time and without issues.

 

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

The Development and Cloud Operations teams are currently working on a solution to resolve the performance incident on POD 2 related to Bulk API. We are currently targeting a hot-fix for later this evening. While we are unable to provide a granular ETA and the next scheduled update will be around 10:00am EDT (UTC-4) on Friday, March 21st, 2014.

 

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

**Update**

Friday, March 21st, 9:54 am EDT (UTC -4)

 

The hot-fix we were targeting for last night didn't pass our tests with QA. The Development and Cloud Operations teams continue to review alternative solutions. We are unable to provide an ETA, but the next scheduled update will be around 3:00pm EDT (UTC-4) today.

 

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

**Update**

Friday, March 21st, 2:41 pm EDT (UTC -4)

 

The Development and Cloud Operations teams are working through this issue. They are working in tandem with our Development Operations in an effort to resolve this quickly. We are unable to provide an ETA, but the next scheduled update will be around 10:00am EDT (UTC-4) on Monday, March 24th, 2014.

 

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

**Update**

Monday, March 24th, 10:00 am EDT (UTC -4)

 

The Development and Cloud Operations teams are working through this issue. Over the weekend, we were able to apply configuration changes to help improve the performance. The teams continue to monitor the situation. We are unable to provide an ETA, but the next scheduled update will be around 2:00pm EDT (UTC-4) today.

 

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

**Update**

Monday, March 24th, 2:45 pm EDT (UTC -4)

 

The Development and Cloud Operations continues to monitor the situation. We are unable to provide an ETA, but the next scheduled update will be around 11:00am EDT (UTC-4) on Tuesday, March 25th, 2014.


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

**Update**

Tuesday, March 25th, 9:38 am EDT (UTC -4)

 

The Development and Cloud Operations continues to monitor the situation. We are unable to provide an ETA, but the next scheduled update will be around 2:00pm EDT (UTC-4) on Tuesday, March 25th, 2014.


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

**Update**

Tuesday, March 25th, 11:50 am EDT (UTC -4)

 

The Development and Cloud Operations continues to investigate and monitor the situation. We are unable to provide an ETA, but the next scheduled update will be around 2:30pm EDT (UTC-4).


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

**Update**

Tuesday, March 25th, 2:33 pm EDT (UTC -4)

 

The Development and Cloud Operations continues to investigate and monitor the situation. We are unable to provide an ETA, but the next scheduled update will be around 5:30pm EDT (UTC-4).


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

**Update**

Wednesday, March 26th, 12:20 am EDT (UTC -4)

 

The Development and Cloud Operations continues to investigate and monitor the situation. We are unable to provide an ETA, but the next scheduled update will be around 11:30am EDT (UTC-4).


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

**Update**

Wednesday, March 26th, 11:39 am EDT (UTC -4)

 

The Development and Cloud Operations continue monitor the situation. We are unable to provide an ETA, but the next scheduled update will be around 4:00 pm EDT (UTC-4) today.


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

**Update**

Wednesday, March 26th, 3:57 pm EDT (UTC -4)

 

The Development and Cloud Operations continue monitor the situation. We are unable to provide an ETA, but the next scheduled update will be around 11:30am EDT (UTC-4) on Thursday, March 27th, 2014.


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

**Update**

Thursday, March 27th, 12:28 pm EDT (UTC -4)

 

This incident is now resolved. The Development and Cloud Operations will continue monitor the situation. After analysis by our support teams, it was determined that the incident was the result of a software bug in Eloqua.  Information related to the incident has been passed on to our Product Engineering team.  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.

We have received reports that Insight on POD 3 is currently unavailable. We have also been informed that there may be performance issues when accessing the Eloqua application. We are investigating this issue and will provide an update at 5:30pm EDT (UTC -4) or as soon as we have any additional information.

 

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

Wednesday, March 19th, 5:24 pm EDT (UTC -4)

 

This issue was resolved at 5:00 pm 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.

 

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

We have received reports that Insight on POD 3 is currently unavailable. We are investigating this issue and will provide an update at 2:30pm EDT (UTC -4)

 

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

Wednesday, March 19th, 2:40 pm EDT (UTC -4)

 

This issue was resolved at 2:09pm 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.

 

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

Eloqua Winter '14 Release - POSTPONED



The Winter '14 Release on Pod 1 is now tentatively scheduled for Sunday, March 30th, 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.


 

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, March 19th, 4:14 pm EDT (UTC -4)

 

On Saturday, March 15th, we alerted our emergency contacts of the postponed Winter Release for customers on POD 1. The decision came as we identified an issue in final release verification.  The issue is related to new software infrastructure that is used in processing large scale Bulk API requests.  The scalability of our APIs continue to be a core investment area of our releases.  As a result, we determined that it was in the best interest of our customers to delay the release until this issue is resolved.

Our engineering and operations teams are working to resolve this issue for a target date, for the Winter Release to Pod 1, of Sunday, March 30th, 2014. Please note, POD 2 and 3 users are independent of this impact.

Eloqua Winter '14 Release - Service Pack 2



Service Pack 2 of the Winter '14 Release will roll out between 11 pm EDT (UTC -4), on Tuesday, March 11th, 2014, and 12 am EDT, on Wednesday, March 12th.



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

 

Maintenance concluded on time and without issues.

 

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

Our Cloud Operations is currently investigating an incident where some functions of Bulk API are unavailable to our clients. We currently don't have an ETA, but the next update will be 3:00 pm EDT (UTC-4).

 

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

**Update**

Tuesday, March 11th, 3:07 pm EDT (UTC -4)

 

Both Cloud Operations and the Development Team are still investigating the incident. In the interim, the teams are manually working the Bulk API queues to assist in minimizing impact. While we still don't have an ETA, the next update will be around 4:00 pm EDT (UTC-4).

 

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

**Update**

Tuesday, March 11th, 3:58 pm EDT (UTC -4)

 

Cloud Operations and the Development Team continue to work at this incident. The incident has improved with their efforts and we are now facing performance degradation. Cloud Operations continues to monitor the situation as we also work in parallel to hot-fix aspects of the overall incident. While we still don't have an ETA, the next update will be around 5:00 pm EDT (UTC-4).


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

**Update**

Tuesday, March 11th, 5:03 pm EDT (UTC -4)

 

Cloud Operations and the Development Team continue to work at this incident aggressively. They are working through identifying the root cause. While we still don't have an ETA, the next update will be around 7:30 pm EDT (UTC-4).


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

**Update**

Tuesday, March 11th, 7:27 pm EDT (UTC -4)

 

Cloud Operations and the Development Team are still investigating the root cause. Users will continue to see performance degradation when using the Bulk API. As we are unable to provide an ETA, the next update will be around 10:15 am EDT (UTC-4) Wednesday, March 12th, 2014.


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

**Update**

Wednesday, March 12th, 10:01 am EDT (UTC -4)

 

Cloud Operations and the Development Team continue to investigate this incident. Client will continue to see performance degradation when using the Bulk API and Cloud Operations continues to monitor and manually work the Bulk API queues to assist in minimizing impact. As we are unable to provide an ETA, the next update will be around 11:15 am EDT (UTC-4) today.


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

**Update**

Wednesday, March 12th, 11:15 am EDT (UTC -4)

 

Cloud Operations and the Development Team continue to investigate this incident. Client will continue to see performance degradation when using the Bulk API and Cloud Operations continues to monitor and manually work the Bulk API queues to assist in minimizing impact. As we are unable to provide an ETA, the next update will be around 12:15 pm EDT (UTC-4) today.


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

**Update**

Wednesday, March 12th, 12:25 pm EDT (UTC -4)


Cloud Operations and the Development Team continue to work at this incident. Cloud Operations continues to monitor the situation as the Development Team continue work to hot-fix aspects of the overall incident. While we still don't have an ETA, the next update will be around 2:15 pm EDT (UTC-4).


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

**Update**

Wednesday, March 12th, 2:25 pm EDT (UTC -4)


Cloud Operations and the Development Team continue to work at this incident. Cloud Operations continues to monitor the situation as the Development Team continues work to hot-fix aspects of the overall incident. We are targeting to have the hot-fixes ready within the next two business days, the next update will be around 4:15 pm EDT (UTC-4).


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

**Update**

Wednesday, March 12th, 4:17 pm EDT (UTC -4)

 

Cloud Operations continues to monitor the situation as the Development Team continues work to hot-fix aspects of the overall incident. We are targeting to have the hot-fixes ready for tomorrow, the next update will be around 11:00 am EDT (UTC-4) tomorrow Thursday, March 13th, 2014.


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

**Update**

Thursday, March 13th, 10:44 am EDT (UTC -4)

 

Cloud Operations continues to monitor the situation as the Development Team continues work to hot-fix aspects of the overall incident. We are currently working through our hot-fix process, the next update will be around 2:00 pm EDT (UTC-4) today.

 

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

**Update**

Thursday, March 13th, 1:25 pm EDT (UTC -4)

 

Cloud Operations continues to monitor the situation as the Development Team continues work to hot-fix aspects of the overall incident. We are still working through our hot-fix process, we are still not able to provide an ETA, but the next update will be around 4:00 pm EDT (UTC-4) today.

 

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

**Update**

Thursday, March 13th, 3:43 pm EDT (UTC -4)

 

Cloud Operations continues to monitor the situation. The Development Team continues to work through our hot-fix process and we are now collaborating with the QA Team as we test our solutions. We are still unable to provide an ETA, but the next update will be around 7.30 pm EDT (UTC-4).


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

**Update**

Thursday, March 13th, 6:49 pm EDT (UTC -4)

 

The Cloud Operations Team continues to monitor the situation. The Development Team continues to work through our hot-fix process and we are now working with our Change Advisory Board to identify when we are able to hot-fix POD 1. During our QA process, POD 2 and 3 failed certain tests and our Development Team will be evaluating next steps. We are still unable to provide an ETA, but the next update will be around 10.30 am EDT (UTC-4) tomorrow, Friday, March 14th, 2014.


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

**Update**

Friday, March 14th, 9:23 am EDT (UTC -4)

 

The Cloud Operations Team continues to monitor the situation. We were able to hot-fix POD 1 last night around 7:45 pm EDT (UTC-4). The Development Team continues to evaluate the POD 2 and 3 failed tests. We are unable to provide an ETA, but the next update will be around 1.30 pm EDT (UTC-4) today.


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

**Update**

Friday, March 14th, 1:21 pm EDT (UTC -4)

 

The Cloud Operations Team continues to monitor the situation. We are now working with our Change Advisory Board to identify when we are able to hot-fix POD 2 and 3. We are unable to provide an ETA, but the next update will be around 4.30 pm EDT (UTC-4).


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

**Update**

Friday, March 14th, 3:23 pm EDT (UTC -4)

 

We were able to hot-fix POD 2 and 3 around 2:50 pm EDT (UTC-4). After analysis by our support teams, it was determined that the incident was the result of a software bug in Eloqua. Information related to the incident has been passed on to our Product Engineering team. 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.

Eloqua Winter '14 Release - Service Pack 2



Service Pack 2 of the Winter '14 Release will roll out on Sunday, March 9th, 2014, 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.


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)

 

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

 

**UPDATE**

Sunday, March 9th, 2014.

 

Maintenance concluded on time and without issues.

 

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

Data Import service restarts will be occurring. This can potentially affect any inflight imports. The next scheduled run will complete successfully.

 

 

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

Sunday, March 9th, 2014.

 

Maintenance concluded on time and without issues.

 

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

Eloqua will be performing a software update on the Deliverability testing functionality on Wednesday, March 5th, 2014, at 5 pm EST (UTC -5).

 

There should be little or no downtime during this maintenance. If you experience any problems, please contact Eloqua Support.

 

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

 

**UPDATE**

Wednesday, March 5th, 2014.

 

Maintenance concluded on time and without issues.

 

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

We have received reports that clients are receiving an error message when logging into the Eloqua Application on POD3. We are currently investigating this issue and will provide an update once we have more information. Our next scheduled update will be around 3:00pm EST (UTC-5).

 

To determine if you are on POD 3:

Log into Eloqua as you normally would.

Look at the browser URL once you are logged in.

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

 

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

**Update**

Sunday, March 3rd, 2:00 pm EST (UTC -5)

 

The issue was resolved as of 1:47 pm EST. 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.

Filter Blog

By date: By tag: