Skip navigation

Advisory Alert: Wednesday, January 28th, 2015


Some Eloqua users are getting intermittent bootstrap error on login using Firefox.

 

Our Development Team is currently working to address this issue; however no ETA for full resolution is currently available. The next update will be on Thursday, January 29th at 10:00 am EST (UTC -5)

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


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

**Update**

Thursday, January 29th, 10:00 am EST (UTC -5)

Our Development Team continues to investigate this incident. The next update will be at approximately 4:00 pm EST (UTC-5)


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

**Update**

Thursday, January 29th, 4:00 pm EST (UTC -5)

 

Our Development Team continues to aggressively work on resolving this incident. We are unable to provide an ETA but the next scheduled update will be on Friday, January 30th at 10:00 am EST (UTC -5)


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

**Update**

Monday, February 2nd, 3:45 pm EST (UTC -5)


Our Development Team has resolved this incident.




Emergency Hot Fix Advisory: Sunday, February 1st, 2015


Eloqua will be performing an emergency hot-fix on Sunday, February 1st, starting at 8 am EST. This will take approximately 3 hours.

 

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

 

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

 

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

 

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

 

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

Our Cloud Operations Team is currently investigating an incident that is impacting BULK API and Data Import/Export on POD 3.  We do not currently have an ETA for resolution, The next update will be at approximately 12:00 am EST (UTC -5)

 

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

**Update**

Wednesday, January 28th 12:00 am EST (UTC -5)

Our Cloud Operations Team is currently working to address this issue, however no ETA for full resolution is currently available. The next update will be at approximately 1:00 am EST (UTC -5)


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

**Update**

Wednesday, January 28th 12:17 am EST (UTC -5)

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

Our Cloud Operations Team is currently investigating an incident that is impacting the performance of BULK API on POD1.  We do not currently have an ETA for resolution. The next update will be at approximately 12 PM EST (UTC -5)


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

**Update**

Sunday, January 25th, 11:10 am EST (UTC -5)

Our Cloud Operations team has uncovered and resolved the root cause of this incident. Some delays can be expected while a small backlog that has formed is processed. The next update will be at approximately 2 pm EST (UTC -5)

 

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

**Update**

Sunday, January 25th, 1:20 pm EST (UTC -5)

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 overall performance of the application for some POD1 clients. We do not currently have an ETA for resolution. The next update will be at approximately 3:00 pm EST (UTC-5)

 

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

**Update**

Wednesday, January 21st, 3:00 pm EST (UTC -5)

Our Cloud Operations Team continues to investigate this incident. The next update will be at approximately 4:00 pm EST (UTC-5)


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

**Update**

Wednesday, January 21st, 3:05 pm EST (UTC -5)


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

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


The Cloud Operations Team requires additional time for our POD1 468 Release, as such the application remains unavailable. They estimate an additional hour is required and we will provide another scheduled update at approximately 11:45 am EST (UTC-5) today.

 

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

**Update**

Sunday, January 18th, 11:45 am EST (UTC-5).

 

Our Cloud Operations Team continues to aggressively work on resolving this incident. They have had to revise their earlier estimation and we are unable to provide an ETA at the moment. The next scheduled update will be at approximately 12:30 pm EST (UTC-5).

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

**Update**

Sunday, January 18th, 12:27 pm EST (UTC-5).

 

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

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

**Update**

Sunday, January 18th, 1:00 pm EST (UTC-5).

 

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

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

**Update**

Sunday, January 18th, 1:27 pm EST (UTC-5).

 

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

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

**Update**

Sunday, January 18th, 1:57 pm EST (UTC-5).

 

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

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

**Update**

Sunday, January 18th, 2:25 pm EST (UTC-5).

 

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

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

**Update**

Sunday, January 18th, 2:56 pm EST (UTC-5).

 

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

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

**Update**

Sunday, January 18th, 3:27 pm EST (UTC-5).

 

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

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

**Update**

Sunday, January 18th, 3:56 pm EST (UTC-5).

 

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

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

**Update**

Sunday, January 18th, 4:28 pm EST (UTC-5).

 

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

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

**Update**

Sunday, January 18th, 4:40 pm EST (UTC-5).

 

The application is now accessible.

The unplanned outage was a result of planned maintenance requiring additional time beyond the initially anticipated duration. The maintenance has been completed and your Eloqua service is available. Oracle is reviewing the events and issues that caused this extended maintenance. After these reviews are completed, additional appropriate corrective actions identified during the reviews will be taken.

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

**Update**

Sunday, January 18th, 11:07 am EST (UTC -5).

 

Because of Application Unavailable / POD1 Clients, the Cloud Operations Team has delayed the Emergency Hot Fix for POD3 until further notice.

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

**Update**

Sunday, January 18th, 1:00 pm EST (UTC-5).

 

Our Cloud Operations Team are currently rolling out the hotfixes for POD3. We can confirm that your Eloqua Services will not be suspended and will update this post upon completion.

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

**Update**

Sunday, January 18th, 1:30 pm EST (UTC-5).

 

Our Cloud Operations Team have completed the hot-fixes.

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

Emergency Hot Fix Advisory: Sunday, January 18th, 2015


Eloqua will be performing an emergency hot-fix on Sunday, January 18th, between 5 and 11 am EST (UTC -5).

 

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

 

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

 

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

 

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

 

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

Our development team is currently investigating an incident that is impacting the ability for some users to access Prospect Profiler. We do not currently have an ETA for resolution, however the next update will be January 16 at approximately 10:00 AM EST (UTC -5)

 

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

**Update**

Friday, January 16th, 10:00 AM EST (UTC -5)

 

Our development team is still currently investigating the incident and still working towards a resolution. The next update will be at approximately 4:00 pm EST (UTC-5)

 

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

**Update**

Friday, January 16th, 4:00 PM EST (UTC -5)

 

Our Development team is working to fully test a fix for this incident. We cannot at this time provide an ETA. The next update will be on Monday Jan 19th, 2015 at approximately 10:00 am EST (UTC -5)

 

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

**Update**

Friday, January 16th, 6:05 PM EST (UTC -5)

 

Our Cloud Operations Team will be pushing a hot-fix for customers on POD 1 and 3 for this incident on Sunday, January 18th, 2015. While we continue to plan for POD 2, the next scheduled update will be on Monday, January 19th, 2015 around 10:00 am EST (UTC-5).

 

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

**Update**

Monday, January 26th, 10:05 AM EST (UTC -5)

This issue is now fully resolved, the hotfix was pushed on January 18th.

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

**Update**

Sunday, January 18th, 10:15 am EST (UTC -5).

 

Our Cloud Operations Team has advised us that an estimated 2 more hours is required for them to complete the 468 Release. Another scheduled update will be provided around 11:00 am EST (UTC-5) today.

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

**Update**

Sunday, January 18th, 11:05 am EST (UTC -5).

 

We are now currently tracking the additional downtime via Application Unavailable / POD1 Clients. Please refer to the new system status post for updates.

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

**Update**

Sunday, January 18th, 4:45 pm EST (UTC -5).

 

The maintenance has now concluded.

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

 

Eloqua 468 Release


The Eloqua 468 Release will roll out on Sunday, January 18th, between 5 and 11 am EST (UTC -5).

 

Please review the supporting resources available in the Oracle Eloqua Release Center. This includes Release Notes for both Eloqua 9 Release Notes 2014 and Eloqua 10 Release Notes 2014, with information on:


Release Overview

What's New in This Release

Known Issues

Fixed Issues

Technical Notes and Limitations

Supported Environments

Documentation

Troubleshooting and Technical Support

 

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

 

During this maintenance, Eloqua will also be upgrading Insight for performance improvement and bug fixes.

NOTE: Due to this enhancement, there will be a freeze period in effect between 10 am (EST) on Friday, January 16th, and the completion of the 468 rollout, during which creation/modification of reports and new users created during the “freeze" period will not be reflected post-upgrade and will be lost.

 

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 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, January 11th, 12:00 pm EST (UTC -5).

 

The maintenance concluded on schedule and without incident.

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

Eloqua 468 Release


The Eloqua 468 Release will roll out on Sunday, January 11th, between 5 and 11 am EST (UTC -5).

 

Please review the supporting resources available in the Oracle Eloqua Release Center. This includes Release Notes for both Eloqua 9 Release Notes 2014 and Eloqua 10 Release Notes 2014, with information on:


Release Overview

What's New in This Release

Known Issues

Fixed Issues

Technical Notes and Limitations

Supported Environments

Documentation

Troubleshooting and Technical Support

 

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

 

During this maintenance, Eloqua will also be upgrading Insight for performance improvement and bug fixes.

NOTE: There is a freeze period now in effect, that will end with the completion of the maintenance, during which creation/modification of reports and new users created during the “freeze" period will not be reflected post-upgrade and will be lost.

 

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 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 Cloud Operations Team is currently investigating an incident impacting the availability of the Eloqua Application for some POD1 clients. The next update will be at approximately 12:00 pm EST (UTC-5)


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

**Update**

Wednesday, January 7th, 12:00 pm EST (UTC -5)

Our Cloud Operations Team continues to investigate this incident. The next update will be at approximately 1:00 pm EST (UTC-5)


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

**Update**

Wednesday, January 7th, 1:00 pm EST (UTC -5)

Our Cloud Operations Team continues to troubleshoot this incident. The next update will be at approximately 2:00 pm EST (UTC-5)


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

**Update**

Wednesday, January 7th, 2:00 pm EST (UTC -5)

 

Our Cloud Operations Team is still currently investigating the incident and still working towards a resolution. The next update will be at approximately 3:00 pm EST (UTC-5)

 

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

**Update**

Wednesday, January 7th, 2:43 pm EST (UTC -5)


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

After analysis by our support teams, it was determined that the incident was the result of a software 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 impacting the availability of the Eloqua Application for some POD1 clients. The next update will be at approximately 8:15 pm EST (UTC-5)


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

**Update**

Monday, January 5th, 8:20 pm EST (UTC-5)

After analysis by our support teams, it was determined that the event resulted from a database issue. The database 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, January 7th, 3:35 am EST (UTC -5).

 

The maintenance concluded on schedule and without incident.

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


Eloqua 468 Release


The Eloqua 468 Release will roll out between 11 pm, Tuesday, January 6th, and 5 am, Wednesday, January 7th, 2015 [all times EST (UTC -5)].

 

 

Please review the supporting resources available in the Oracle Eloqua Release Center. This includes Release Notes for both Eloqua 9 Release Notes 2014 and Eloqua 10 Release Notes 2014, with information on:


Release Overview

What's New in This Release

Known Issues

Fixed Issues

Technical Notes and Limitations

Supported Environments

Documentation

Troubleshooting and Technical Support

 

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

 

 

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

 

 

To determine if you are on Pod2:

Log into Eloqua as you normally would.

Look at the browser URL once you are logged in.

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

Filter Blog

By date: By tag: