Skip navigation

Oracle Eloqua Apps Release: Version 213.1

 

 

The Eloqua Apps 'Version 213.1' Release is on its way. Your Eloqua instance will be seeing the new enhancements on Wednesday, September 2nd, 2015.

 

The Version 213.1 rollout begins on Wednesday, September 2nd, at 8 pm, and will conclude by 2 am on Thursday, September 3rd [All times EDT (UTC -4).]

 

Profiler and applications hosted at 'apps.secure.eloqua.com/' (for Pod 1) ,'apps.www02.secure.eloqua.com/' (for Pod 2), 'apps.p03.eloqua.com/' (for Pod 3) and 'apps.p04.eloqua.com/' (for Pod 4) will not be configurable during the maintenance window.

 

Please review the supporting resources available in the Topliners Release Resource Center and in the Recent Versions: What's New doc.

 

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

 

 

 

To determine if you are on Pod 1:

Log into Eloqua as you normally would.

Look at the browser URL once you are logged in.

The Pod 1 URL has the following format - www.secure.eloqua.com/

 

To determine if you are on Pod 2:

Log into Eloqua as you normally would.

Look at the browser URL once you are logged in.

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

 

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.

The Pod 3 URL has the following format - secure.p03.eloqua.com/

 

To determine if you are on Pod 4:

Log into Eloqua as you normally would.

Look at the browser URL once you are logged in.

The Pod 4 URL has the following format - secure.p04.eloqua.com/

Oracle Eloqua Apps Release: Version 213.1

 

 

The Eloqua Apps 'Version 213.1' Release is on its way. Your Eloqua instance will be seeing the new enhancements on Wednesday, September 2nd, 2015.

 

The Version 213.1 rollout begins on Wednesday, September 2nd, at 2 pm, and will conclude by 8 pm. [All times EDT (UTC -4).]

 

Profiler and applications hosted at ''apps.p06.eloqua.com/' will not be configurable during the maintenance window.

 

Please review the supporting resources available in the Topliners Release Resource Center and in the Recent Versions: What's New doc.

 

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

 

 

To determine if you are on Pod 6:

Log into Eloqua as you normally would.

Look at the browser URL once you are logged in.

The Pod 6 URL has the following format - secure.p06.eloqua.com/.

Oracle Eloqua Apps Release: Version 213.1

 

 

The Eloqua Apps 'Version 213.1' Release is on its way. Your Eloqua instance will be seeing the new enhancements on Wednesday, September 2nd, 2015.

 

The Version 213.1 rollout begins on Wednesday, September 2nd, at 6 am, and will conclude by 12 pm. [All times EDT (UTC -4).]

 

Profiler and applications hosted at ''apps.p07.eloqua.com/' will not be configurable during the maintenance window.

 

Please review the supporting resources available in the Topliners Release Resource Center and in the Recent Versions: What's New doc.

 

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

 

 

To determine if you are on Pod 7:

Log into Eloqua as you normally would.

Look at the browser URL once you are logged in.

The Pod 7 URL has the following format - secure.p07.eloqua.com/.

Both our Development Team and Cloud Operations Team are currently investigating an incident around performance degradation with our CRM Integration Services. At this time, we are unable to provide an ETA for this incident, but we will continue to provide updates. The next scheduled update will be today around 3:00 pm EDT (UTC-4).

 

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

**Update** Wednesday, August 28th, 2:35 pm EDT (UTC -4)

 

Integration Services look healthy and the Cloud Operations Team continue to monitor the situation. The next scheduled update will be around 5:00 pm EDT (UTC-4).

 

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

**Update** Wednesday, August 28th, 5:00 pm EDT (UTC -4)

 

Integration Services remain healthy and the Cloud Operations Team will continue to monitor the situation. The next scheduled update will be around 10:00 am EDT (UTC-4) on Monday, August 31st.

 

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

**Update** Monday, August 31st, 10:00 am EDT (UTC -4)

 

Integration Services remain healthy and the Cloud Operations Team will continue to monitor the situation. The next scheduled update will be around 4:00 pm EDT (UTC-4).

 

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

**Update** Monday, August 31st, 4:22 pm EDT (UTC -4)

 

This incident is now resolved.

 

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.  Once Product Engineering confirms they have a resolution to the issue, it will be deployed to the 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 performance of the BULK API on POD 2. We do not currently have an ETA for resolution. The next update will be at approximately 6:30 am EDT (UTC -4).

 

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

**Update** Wednesday, August 26th, 6:30 am EDT (UTC -4)

 

Our Cloud Operations Team continue to aggressively work on resolving this incident. The next scheduled update will be at approximately 7:30 am EDT (UTC-4).


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

**Update** Wednesday, August 26th, 7:10 am EDT (UTC -4)

 

This incident is now resolved.

 

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 Cloud Operations Team is currently investigating an incident impacting the ability to log into the Eloqua application for some clients. There is no issue with Eloqua services and servers.  This appears to be an issue with third party routing.  We do not currently have an ETA for resolution. The next update will be at approximately 4:00 pm EDT (UTC-4).

 

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

**Update** Tuesday, August 25th, 3:50 pm EDT (UTC -4)

 

Our Team is still troubleshooting this incident. We do not currently have an ETA for resolution.  The next scheduled update will be on Wednesday, August 26th around 11:00 am EDT (UTC-4).


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

**Update** Wednesday, August 26th, 10:50 am EDT (UTC -4)

 

Our Cloud Operations Team is still currently working in resolving this incident. We do not currently have an ETA for resolution.  The next scheduled update will be around 4:00 pm EDT (UTC-4).


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

**Update** Wednesday, August 26th, 2:50 pm EDT (UTC -4)

 

This incident is now resolved.

Our Development Team and Cloud Operations Team are currently investigating an incident where some customers are getting bootstrap error during log on to Eloqua Application.  There was a deployment error and some instances defined as sandboxes were impacted.  At this time, we are unable to provide an ETA for this incident, but we will continue to provide updates. The next scheduled update will be around 11:30 am EDT (UTC-4).

 

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

**Update** Monday, August 24th, 11:30 am EDT (UTC -4)

 

Both Teams continue to aggressively work on resolving this incident. The next scheduled update will be at approximately 12:30 pm EDT (UTC-4).

 

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

**Update** Monday, August 24th, 12:25 pm EDT (UTC -4)

 

Our Development Team and Cloud Operations Team are anticipating to resolve this incident within the next 2 hours.  The next scheduled update will be at approximately 2:30 pm EDT (UTC-4).


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

**Update** Monday, August 24th, 2:27 pm EDT (UTC -4)

 

Our Development Team and Cloud Operations Team are targeting to have this incident resolved by 5 pm EDT ( UTC-4).  The next scheduled update will be around 5:00 pm EDT (UTC-4).


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

**Update** Monday, August 24th, 4:15 pm EDT (UTC -4)

 

This incident is now resolved.

 

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

Both our Development Team and Cloud Operations Team are currently investigating an incident around performance degradation with our CRM Integration Services. At this time, we are unable to provide an ETA for this incident, but we will continue to provide updates. The next scheduled update will be Monday, August 24th, 2015 around 1:00 am EDT (UTC-4).

 

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

**Update** Monday, August 24th, 1:07 am EDT (UTC -4)

 

Our Cloud Operations Team continues to aggressively work on resolving this incident. The next scheduled update will be at approximately 1:30 am EDT (UTC-4).


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

**Update** Monday, August 24th, 1:30 am EDT (UTC -4)

 

Our Cloud Operations Team continues to aggressively work on resolving this incident. The next scheduled update will be at approximately 2:00 am EDT (UTC-4).


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

**Update** Monday, August 24th, 2:00 am EDT (UTC -4)

 

Our Cloud Operations Team continues to aggressively work on resolving this incident. The next scheduled update will be at approximately 2:30 am EDT (UTC-4).


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

**Update** Monday, August 24th, 2:30 am EDT (UTC -4)

 

Our Cloud Operations Team continues to aggressively work on resolving this incident. The next scheduled update will be at approximately 3:00 am EDT (UTC-4).


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

**Update** Monday, August 24th, 3:04 am EDT (UTC -4)

 

Our Cloud Operations Team continues to aggressively work on resolving this incident. The next scheduled update will be at approximately 3:30 am EDT (UTC-4).


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

**Update** Monday, August 24th, 3:30 am EDT (UTC -4)

 

Our Cloud Operations Team continues to aggressively work on resolving this incident. The next scheduled update will be at approximately 4:00 am EDT (UTC-4).


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

**Update** Monday, August 24th, 4:30 am EDT (UTC -4)

 

Our Cloud Operations Team continues to troubleshoot this incident. The next scheduled update will be at approximately 5:00 am EDT (UTC-4).


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

**Update** Monday, August 24th, 4:55 am EDT (UTC -4)

 

Our Cloud Operations team have identified the root cause of this incident. Corrective actions have been taken, and the backlog created during this incident is being processed. While we are still unable to provide an ETA, the next scheduled update will be around 10:00 am EDT (UTC-4).

 

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

**Update** Monday, August 24th, 10:09 am EDT (UTC -4)

 

Our Team has confirmed that calls are processing and the queue is improving. Cloud Operations Team will continue to monitor the situation. The next scheduled update will be at approximately 4:00 pm EDT (UTC-4).


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

**Update** Monday, August 24th, 3:30 pm EDT (UTC -4)

 

Our Cloud Operations team has confirmed that this incident is now resolved.

 

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

Scheduled Maintenance Advisory for Friday, August 28th, 2015


Eloqua will be performing scheduled maintenance on Friday, August 28th, 2015, between 6am and 12pm EDT (UTC -4).


Application processing will be suspended during portions of 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

  • Program Builder

 

We recommend that customers not attempt to use the application at this time as rolling outages are anticipated and 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.

/Scheduled Maintenance Advisory for Friday, August 28th, 2015


Eloqua will be performing scheduled maintenance on Friday, August 28th, 2015, between 2pm and 8pm EDT (UTC -4).


Application processing will be suspended during portions of 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

  • Program Builder

 

We recommend that customers not attempt to use the application at this time as rolling outages are anticipated and 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.

Scheduled Maintenance Advisory for Friday, August 28th, 2015


Eloqua will be performing scheduled maintenance on Friday, August 28th, 2015, between 8pm and 2am EDT (UTC -4).


Application processing will be suspended during portions of 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

  • Program Builder

 

We recommend that customers not attempt to use the application at this time as rolling outages are anticipated and 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.

Scheduled Maintenance Advisory for Sunday, August 30th, 2015


Eloqua will be performing scheduled maintenance on Sunday, August 30th, 2015, between 5am and 11am EDT (UTC -4).


Application processing will be suspended during portions of 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

  • Program Builder

 

We recommend that customers not attempt to use the application at this time as rolling outages are anticipated and 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.

Scheduled Maintenance Advisory for Tuesday, August 25th, 2015


Eloqua will be performing scheduled maintenance on Tuesday, August 25th, 2015, between 11pm and 5am EDT (UTC -4).


Application processing will be suspended during portions of 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

  • Program Builder

 

We recommend that customers not attempt to use the application at this time as rolling outages are anticipated and 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.

Both our Development Team and Cloud Operations Team are currently investigating an incident around performance degradation with our CRM Integration Services. At this time, we are unable to provide an ETA for this incident, but we will continue to provide updates. The next scheduled update will be Friday, August 21st, 2015 around 11:00 am EDT (UTC-4).

 

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

**Update** Friday, August 21st, 10:26 am EDT (UTC -4)

 

Our Teams have stabilized the Integration Services. While they continue to monitor, the next scheduled update will be around 5:00 pm EDT (UTC-4).

 

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

**Update** Friday, August 21st, 3:31 pm EDT (UTC -4)

 

Our Teams have confirmed that calls are processing and the queue is improving. Our Development Team will continue to monitor the situation. While we are still unable to provide an ETA, the next scheduled update will be around 11:00 am EDT (UTC-4) on Monday, August 24th.

 

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

**Update** Monday, August 24th, 11:10 am EDT (UTC -4)

 

This incident is 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.

Oracle Eloqua Apps Release: Version 213

 

 

The Eloqua Apps 'Version 213' Release is on its way. Your Eloqua instance will be seeing the new enhancements on Friday, August 21st, 2015.

 

The Version 213 rollout begins on Friday, August 21st, at 8 pm, and will conclude by 2 am on Saturday, August 22nd [All times EDT (UTC -4).]

 

Profiler and applications hosted at 'apps.secure.eloqua.com/' (for Pod 1) ,'apps.www02.secure.eloqua.com/' (for Pod 2), 'apps.p03.eloqua.com/' (for Pod 3) and 'apps.p04.eloqua.com/' (for Pod 4) will not be configurable during the maintenance window.

 

Please review the supporting resources available in the Topliners Release Resource Center and in the Recent Versions: What's New doc.

 

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

 

 

 

To determine if you are on Pod 1:

Log into Eloqua as you normally would.

Look at the browser URL once you are logged in.

The Pod 1 URL has the following format - www.secure.eloqua.com/

 

To determine if you are on Pod 2:

Log into Eloqua as you normally would.

Look at the browser URL once you are logged in.

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

 

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.

The Pod 3 URL has the following format - secure.p03.eloqua.com/

 

To determine if you are on Pod 4:

Log into Eloqua as you normally would.

Look at the browser URL once you are logged in.

The Pod 4 URL has the following format - secure.p04.eloqua.com/

Oracle Eloqua Apps Release: Version 213

 

 

The Eloqua Apps 'Version 213' Release is on its way. Your Eloqua instance will be seeing the new enhancements on Friday, August 21st, 2015.

 

The Version 213 rollout begins on Friday, August 21st, at 6 am, and will conclude by 12 pm. [All times EDT (UTC -4).]

 

Profiler and applications hosted at ''apps.p07.eloqua.com/' will not be configurable during the maintenance window.

 

Please review the supporting resources available in the Topliners Release Resource Center and in the Recent Versions: What's New doc.

 

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

 

 

To determine if you are on Pod 7:

Log into Eloqua as you normally would.

Look at the browser URL once you are logged in.

The Pod 7 URL has the following format - secure.p07.eloqua.com/.

Oracle Eloqua Apps Release: Version 213

 

 

The Eloqua Apps 'Version 213' Release is on its way. Your Eloqua instance will be seeing the new enhancements on Friday, August 21st, 2015.

 

The Version 213 rollout begins on Friday, August 21st, at 2 pm, and will conclude by 8 pm. [All times EDT (UTC -4).]

 

Profiler and applications hosted at ''apps.p06.eloqua.com/' will not be configurable during the maintenance window.

 

Please review the supporting resources available in the Topliners Release Resource Center and in the Recent Versions: What's New doc.

 

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

 

 

To determine if you are on Pod 6:

Log into Eloqua as you normally would.

Look at the browser URL once you are logged in.

The Pod 6 URL has the following format - secure.p06.eloqua.com/.

Our Development Team is currently investigating an incident impacting the availability of Insight for POD 1 clients. The next scheduled update will be at approximately 11:00 am EDT (UTC-4).


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

**Update** Thursday, August 13th, 11:00 am EDT (UTC -4)

 

Our Development Team continues to aggressively work on resolving this incident. The next scheduled update will be at approximately 12:00 pm EDT (UTC-4).


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

**Update** Thursday, August 13th, 11:29 am EDT (UTC -4)


Our Development Team has confirmed that this issue is now resolved.


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

**Update** Friday, August 14th, 4:02 pm EDT (UTC -4)


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

Our Development Team and Cloud Operations Team are currently investigating an incident around performance degradation with our CRM Integration Services. At this time, we are unable to provide an ETA for this incident, but we will continue to provide updates. The next scheduled update will be today around 11:00 am EDT (UTC-4).

 

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

**Update** Wednesday, August 12th, 11:12 am EDT (UTC -4)

 

Both teams continue to troubleshoot the incident. The next scheduled update will be around 1:00 pm EDT (UTC-4).

 

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

**Update** Wednesday, August 12th, 1:00 pm EDT (UTC -4)

 

Both teams continue to aggressively work on resolving this incident. The next scheduled update will be at approximately 3:00 pm EDT (UTC-4).

 

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

**Update** Wednesday, August 12th, 3:01 pm EDT (UTC -4)

 

Our Development Team and Cloud Operations Teams continue to aggressively work on resolving this incident. The next scheduled update will be at approximately 5:00 pm EDT (UTC-4).

 

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

**Update** Wednesday, August 12th, 5:00 pm EDT (UTC -4)

 

As our Development Team and Cloud Operations Team troubleshoot this incident, we are still unable to provide anything tangible at this time. While we are still unable to provide an ETA, the next scheduled update will be at approximately 7:00 pm EDT (UTC-4).

 

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

**Update** Wednesday, August 12th, 6:16 pm EDT (UTC -4)

 

The Development Team believes they have a path to resolution and are performing the required evaluations. In parallel, our Cloud Operations Team will continue to monitor the situation.  The next scheduled update will be around 10:00 am EDT (UTC-4) on Thursday, August 13th.

 

 

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

**Update** Thursday, August 13th, 10:26 am EDT (UTC -4)

 

Our Development Team and Cloud Operations Team have confirmed that calls are processing and the queue is improving. Our Cloud Operations team will continue to monitor the situation. While we are still unable to provide an ETA, the next scheduled update will be at approximately 12:00 pm EDT (UTC-4).

 

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

**Update** Thursday, August 13th, 11:46 am EDT (UTC -4)

 

Our Teams have stabilized the Integration Services. While they continue to monitor, the next scheduled update will be around 2:00 pm EDT (UTC-4)

 

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

**Update** Thursday, August 13th, 2:13 pm EDT (UTC -4)

 

Integration Services continue to be healthy and the Cloud Operations Team continue to monitor the situation. The next scheduled update will be around 5:30 pm EDT (UTC-4)

 

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

**Update** Thursday, August 13th, 5:09 pm EDT (UTC -4)

 

Integration Services remain healthy and the Cloud Operations Team continue to monitor the situation. The next scheduled update will be around 11:30 am EDT (UTC-4) on Friday, August 14th.

 

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

**Update** Friday, August 14th, 1:26 pm EDT (UTC -4)

 

Integration Services remain healthy and the Cloud Operations Team continue to monitor the situation. The next scheduled update will be around 11:30 am EDT (UTC-4) on Monday, August 17th.

 

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

**Update** Monday, August 17th, 11:05 am EDT (UTC -4)

 

Integration Services remain healthy and the Cloud Operations Team continue to monitor the situation. In parallel, Product Development continues to investigate the root cause. The next scheduled update will be around 11:30 am EDT (UTC-4) on Tuesday, August 18th.

 

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

**Update** Wednesday, August 19th, 10:54 am EDT (UTC -4)

 

This incident is resolved.

 

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.  Once Product Engineering confirms they have a resolution to the issue, it will be deployed to the 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 been aggressively troubleshooting an incident where some clients are receiving a "Secure Connection Failed" error. As of 2:50pm EDT (UTC-4), a configuration change was made and they are monitoring the situation. We currently do not have an ETA for resolution, however, the next scheduled update will be around 3:30pm EDT (UTC-4).

 

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

**Update** Tuesday, August 11th, 3:30 pm EDT (UTC -4)

 

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

 

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

**Update** Tuesday, August 11th, 4:00 pm EDT (UTC -4)

 

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

 

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

**Update** Tuesday, August 11th, 5:00 pm EDT (UTC -4)

 

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

 

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

**Update** Tuesday, August 11th, 5:50 pm EDT (UTC -4)

 

Cloud Operations will be performing additional configurations changes at 9:00pm EDT (UTC-4) and will be monitoring the incident. We are unable to provide an ETA at the moment. The next scheduled update will be at approximately 10:00 pm EDT (UTC-4).

 

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

**Update** Tuesday, August 11th, 10:02 pm EDT (UTC -4)

 

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

 

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

**Update** Tuesday, August 11th, 10:42 pm EDT (UTC -4)

 

As the Cloud Operations Team troubleshoot this incident, we are still unable to provide anything tangible at this time. While we are still unable to provide an ETA, we will provide another update on Wednesday, August 12th at approximately 10:00 am EDT (UTC-4).

 

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

**Update** Wednesday, August 12th, 10:00 am EDT (UTC -4)

 

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 11:00 am EDT (UTC-4).

 

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

**Update** Wednesday, August 12th, 11:09 am EDT (UTC -4)

 

Our Cloud Operations has reverted the configurations changes that did not have any affect. We are unable to provide an ETA at the moment. The next scheduled update will be at approximately 12:00 pm EDT (UTC-4).

 

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

**Update** Wednesday, August 12th, 12:25 pm EDT (UTC -4)

 

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

 

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

**Update** Thursday, August 13th, 1:11 pm EDT (UTC -4)

 

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.

Both our Development Team and Cloud Operations Team are currently investigating an incident around performance degradation with our CRM Integration Services. At this time, we are unable to provide an ETA for this incident, but we will continue to provide updates. The next scheduled update will be today around 4:00 pm EDT (UTC-4).

 

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

**Update** Monday, August 10th, 2:21 pm EDT (UTC -4)

 

The two teams continue to troubleshoot the incident. The next scheduled update will be Tuesday, August 11th, 2015 around 2:00 pm EDT (UTC-4).

 

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

**Update** Tuesday, August 11th, 10:54 am EDT (UTC -4)

 

The Development and Cloud Operations Team have isolated the incident. We are targeting to start pushing a hot-fix around 12:00 pm EDT (UTC-4) with the next scheduled update around 1:00 pm EDT (UTC-4).

 

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

**Update** Tuesday, August 11th, 12:43 pm EDT (UTC -4)

 

The Development and Cloud Operations Team are now targeting to start pushing a hot-fix around 3:00 pm EDT (UTC-4) with the next scheduled update around 4:00 pm EDT (UTC-4).

 

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

**Update** Tuesday, August 11th, 2:35 pm EDT (UTC -4)

 

The hot-fix has been successfully applied.

Eloqua 473 Release


The Eloqua 473 Release will roll out on Sunday, August 23rd, 2015 between 5am and 5pm EDT (UTC -4).

 

 

Please review the supporting resources available in the Release Resource Center. This includes Release Notes for both E9 and E10 with information on:


Release Overview

What's New in This Release

Known Issues

Fixed Issues

Technical Notes and Limitations

Supported Environments

Documentation

Troubleshooting and Technical Support

 

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

 

 

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


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

**Update** Friday, August 14th, 1:21 pm EDT (UTC -4)

 

The POD01 473 Release has been postponed. More information to follow.

 

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

**Update** Friday, August 14th, 2:17 pm EDT (UTC -4)

 

On Friday, August 14th, we are alerting our emergency contacts that the POD1 Release (473) originally planned for August 16th will be postponed. During our final release readiness testing and in response to customer feedback from POD3 users, we have identified a performance incident with CRM Integrations. As a result, we determined that delaying the release until this incident is resolved is in best interest of our customers.

 

Our Engineering and Operations Teams are working to resolve the incident and are targeting a new release date to POD1 for Sunday, August 23rd, 2015.

 

The next scheduled update will be around 11:00am EDT (UTC-4) on Monday, August 17th, 2015.

 

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

**Update** Monday, August 17th, 11:06 am EDT (UTC -4)

 

Product Development is aggressively working towards resolving this incident. We are still targeting a new release date to POD1 for Sunday, August 23rd, 2015.  The next scheduled update will be around 11:30am EDT (UTC-4) on Tuesday, August 18th, 2015.

 

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

**Update** Tuesday, August 18th, 11:05 am EDT (UTC -4)

 

Product Development is still working towards resolving this incident. While we are still targeting a new release date to POD1 for Sunday, August 23rd, 2015, we expect by the next update to have this finalized.  The next scheduled update will be around 11:30am EDT (UTC-4) on Wednesday, August 19th, 2015.

 

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

**Update** Wednesday, August 19th, 12:04 pm EDT (UTC -4)

 

Product Development has confirmed the new release date to POD1 for Sunday, August 23rd, 2015.

Our Cloud Operations Team is currently investigating an incident impacting the availability of Insight for some POD 3 clients. The next update will be on Monday, August 10th at approximately 10 am EDT (UTC-4).


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

**Update: Monday, August 10th, 8:52 am 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.

Eloqua 473 Release



The Eloqua 473 Release will roll out between 8pm Friday, August 14th and 2am, Saturday, August 15th, 2015 EDT (UTC -4).



 

Please review the supporting resources available in the Release Resource Center. This includes Release Notes for both E9 and E10 with information on:


Release Overview

What's New in This Release

Known Issues

Fixed Issues

Technical Notes and Limitations

Supported Environments

Documentation

Troubleshooting and Technical Support

 

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

 

 

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

Eloqua 473 Release


The Eloqua 473 Release will roll out on Sunday, August 9th, 2015 between 5am and 5pm EDT (UTC -4).

 

 

Please review the supporting resources available in the Release Resource Center. This includes Release Notes for both E9 and E10 with information on:


Release Overview

What's New in This Release

Known Issues

Fixed Issues

Technical Notes and Limitations

Supported Environments

Documentation

Troubleshooting and Technical Support

 

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

 

 

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

Filter Blog

By date: By tag: