Skip navigation
1 2 3 4 5 Previous Next

Eloqua System Status

116 Posts authored by: Anirude-Oracle

Our Cloud Operations Team is currently investigating an incident where the Bulk API service for our POD 3 Clients is not working. At this time, we are unable to provide an ETA, but the next scheduled update will be around 11:15 am EDT (UTC-4) today.

 

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

**Update**

Tuesday, July 29th, 11:09 am EDT (UTC -4)

 

The Cloud Operations Team continues to investigate the incident. While we don't have anything tangible to report, the next scheduled update will be around 12:15 pm EDT (UTC-4).

 

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

**Update**

Tuesday, July 29th, 12:18 pm EDT (UTC -4)

 

The Cloud Operations Team continues to investigate the incident. While we don't have anything tangible to report, the next scheduled update will be around 1:15 pm EDT (UTC-4).

 

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

**Update**

Tuesday, July 29th, 1:05 pm EDT (UTC -4)

 

Additional teams have been brought in to assist our Cloud Operations Team as they continue to investigate the incident. We can confirm this incident is also affecting Lead Scoring for POD 3 clients. The next scheduled update will be around 2:15 pm EDT (UTC-4).

 

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

**Update**

Tuesday, July 29th, 2:13 pm EDT (UTC -4)


Our Cloud Operations Team resolved this incident around 1:55 pm EDT (UTC-4).


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

**Update**

Tuesday, July 29th, 2:17 pm EDT (UTC -4)


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

Both our Development Team and Cloud Operations Team are currently investigating an incident where contacts are not being scored for POD 1 clients. At this time, we are not able to provide an ETA, but the next schedule update will be around 5.15 pm EDT (UTC-4).

 

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

**Update**

Sunday, July 27th, 5:08 pm EDT (UTC -4)

 

The Cloud Operations Team continue to the investigate the incident. Through their efforts, we have now confirmed this is a performance degradation incident as contacts are being scored. We are still unable to provide an ETA, but the next schedule update will be around 6:15 pm EDT (UTC-4).

 

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

**Update**

Sunday, July 27th, 6:22 pm EDT (UTC -4)

 

The Cloud Operations Team continues to the investigate the incident. We are still unable to provide an ETA, but the next schedule update will be around 7:15 pm EDT (UTC-4).

 

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

**Update**

Sunday, July 27th, 7:12 pm EDT (UTC -4)

 

Both our Development Team and Cloud Operations Team continues to the investigate the incident. We are still unable to provide an ETA, but the next schedule update will be around 8:15 pm EDT (UTC-4).

 

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

**Update**

Sunday, July 27th, 8:15 pm EDT (UTC -4)

 

Both our Development Team and Cloud Operations Team continues to the investigate the incident. We are still unable to provide an ETA, but the next schedule update will be around 9:15 pm EDT (UTC-4).

 

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

**Update**

Sunday, July 27th, 9:17 pm EDT (UTC -4)

 

Both our Development Team and Cloud Operations Team continues to the investigate the incident. We are still unable to provide an ETA, but the next schedule update will be on Monday, July 28th, 2014 around 10:00 am EDT (UTC-4).

 

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

**Update**

Monday, July 28th, 8:02 am EDT (UTC -4)

 

The incident was resolved today around 2:45 am EDT (UTC-4). After analysis by our support teams, it was determined that the incident resulted from a configuration issue.  The configuration issue has been resolved and production use of your Eloqua service has been restored.  Oracle is also reviewing the monitoring, alerting and standard operating procedures related to the incident.  After these reviews are completed, additional appropriate corrective actions identified during the reviews will be taken.

Eloqua Summer '14 Release - Service Pack 2 - CONCLUDED

 

Service Pack 2 of the Summer '14 Release will roll out between 5 and 11 am EDT (UTC -4), Sunday, July 27th, 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.

 

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


To determine if you are on Pod1:

Log into Eloqua as you normally would.

Look at the browser URL once you are logged in.

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

 

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

**Update**

Sunday, July 27th, 10:20 am EDT (UTC -4)

 

The Cloud Operations Team anticipates they will require additional down time to complete the POD1 Summer '14 Service Pack 2 Release. While we are unable to provide tangible ETAs at this moment, we will continue to provide updates. The next scheduled update will be today around 11:45 am EDT (UTC -4).

 

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

**Update**

Sunday, July 27th, 11:10 am EDT (UTC -4)

 

The Cloud Operations Team continues to push forward with the Summer '14 Release. We are unable to provide an ETA, but the next scheduled update will be today around 11:45 am EDT (UTC -4).

 

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

**Update**

Sunday, July 27th, 11:45 am EDT (UTC -4)

 

Both the Development Operations Team and the Quality Assurance Team are on standby as the Cloud Operations Team continues to push forward with the Summer '14 Release. We are still unable to provide an ETA, but the next scheduled update will be today around 12:30 pm EDT (UTC -4).

 

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

**Update**

Sunday, July 27th, 12:28 pm EDT (UTC -4)

 

The Cloud Operations Team continues to push forward with the Summer '14 Release. The next scheduled update will be today around 1:15 pm EDT (UTC -4).


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

**Update**

Sunday, July 27th, 1:08 pm EDT (UTC -4)

 

The Cloud Operations Team has completed the Summer '14 Release push to POD1.

Both our Development Team and Cloud Operations Team are currently investigating an incident around performance degradation with our CRM Integration Services. In parallel, our Cloud Operations Team is monitoring the services to ensure a hard stop does not occur. 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 6:00 pm EDT (UTC-4).

 

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

**Update**

Thursday, July 24th, 5:16 pm EDT (UTC -4)

 

The two teams continue to troubleshoot the incident, however, we have nothing tangible to report. The next scheduled update will be Friday, July 25th, 2014 around 12:00 pm EDT (UTC-4).

 

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

**Update**

Friday, July 25th, 11:39 pm EDT (UTC -4)

 

The Development Team and Cloud Operations Team were able to identify the root cause and have already executed on immediate corrective measures.

 

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.

In the recent Eloqua Summer Release, there were 2 new flags available with email groups that should not be used as they were released ahead of availability of a future email privacy add on:


  • The “Use Secure Channel” flags an email group as secure.  If this option is checked, emails will only be delivered to contacts who are part of this group via a secure communications channel.  This functionality will only work with an upcoming service pack add on. Customers are advised not to check this flag at this time as emails will not be delivered if the option is checked.


  • The “Require Opt-In” flag when checked provides the ability to flag an email group as requiring contacts to explicitly subscribe to the group in order to receive emails in the group.  If this option is checked, emails will be delivered only to contacts who explicitly subscribe to the group. Customers should not to check this flag at this time as this functionality is tied to a future service pack.

 

Remember, your emails will not be delivered if you check these boxes. Please do not use them at this time. These flags will be removed in an upcoming Summer Release Service Pack and we will update this advisory accordingly.

 

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

**Update**

Tuesday, August 26th, 2:08 pm EDT (UTC -4)

 

This has been corrected and these options should no longer be visible.

Our Cloud Operations Team identified an incident impacting campaign execution for some clients on POD1. This was discovered at 11:23 AM EDT (UTC-4) and fully resolved at 12:40 PM EDT (UTC-4)


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.

Eloqua Summer '14 Release - Service Pack 2 - SUCCESSFULLY CONCLUDED

 

Service Pack 2 of the Summer '14 Release will roll out between 5 am and 11 am EDT (UTC -4), Sunday, July 20th, 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.

 

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)

Eloqua Summer '14 Release - Service Pack 2 - SUCCESSFULLY CONCLUDED

 

Service Pack 2 of the Summer '14 Release will roll out between 11 pm, Tuesday, July 15th, and 5 am, Wednesday, July 16th, 2014 (all times EDT (UTC -4)).

 

 

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


Release Overview

What's New in This Release

Known Issues

Fixed Issues

Technical Notes and Limitations

Supported Environments

Documentation

Troubleshooting and Technical Support

 

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

 

While the application may remain accessible during this time, some features such as file and image uploads, program builder and emails will be paused as they are upgraded. There will also be intermittent downtime during this 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**

Wednesday, July 16th, 1:28 am EDT (UTC -4)

 

The release completed without incident.

As of 11:05 AM EDT (UTC -4) We are experiencing an intermittent failure in login on POD 3.

 

Our Operations and development teams are working to resolve the issue and we will update this post again before 1 PM EDT (UTC-4)

 

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

 

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

**** Update: 11:57 AM EDT (UTC -4) ****

 

As of 11:45 AM EDT (UTC -4) this issue has been resolved.

Eloqua Summer '14 Release - Service Pack 1 - SUCCESSFULLY CONCLUDED



Service Pack 1 of the Summer '14 Release concluded at 11:45 AM EDT (UTC -4 ), on Sunday, July 6th 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.

 

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)

Emergency Maintenance Advisory for Thursday, June 26th, 2014



Eloqua will be performing Emergency Maintenance on Thursday, June 26th, between 9:00 pm -11:00 pm EDT (UTC -4).

 

Downtime affect as follows. During parts of the maintenance:

 

•         Inbound activity will be lost (page views, email responses).

•         Form submissions will not be captured.

•         Application processing will be paused and resumed after downtime ends.

 

You are advised not to use the application during this period to avoid loss of work. Please contact Eloqua Support if you require additional details.

 

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

**Update**

Thursday, June 26th, 11:26 pm EDT (UTC -4)

 

The maintenance concluded successfully at 11:05 pm EDT (UTC-4) without incidents.

Between 3:55 AM EDT (UTC-4) and 4:40 AM EDT (UTC-4) Some POD1 clients may have experienced problems logging into their database. The issue is now resolved.


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.

Our Cloud Operations Team is currently investigating the cause of an incident that is affecting the responsiveness of the BULK API on POD 2.  While we do not at this time have an ETA for resolution, we will continue to monitor this issue and update this post as to the current status. The next scheduled update will be around 10:00 am EDT (UTC-4).

 

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

**Update** Wednesday June 18th 9:53 AM EDT (UTC-4)

 

Our operations team continues to investigate the incident, no ETA is available as of yet. We will continue to update this post with the current status, the next update will be around 12:00 PM EDT (UTC-4)

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

**Update** Wednesday June 18th 12:02 PM EDT (UTC-4)

 

Our operations team continues to investigate the incident. We will continue to update this post as to the current status. The next update will be around 2 PM EDT (UTC-4)

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

**Update** Wednesday June 18th 2:05 PM EDT (UTC-4)

 

Our operations team continues to investigate the incident. We will continue to update this post as to the current status. The next update will be around 4 PM EDT (UTC-4)

 

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

**Update** Wednesday June 18th 4:00 PM EDT (UTC-4)

 

Our Cloud Operations Team, Development Team and Oracle DB Support continue to aggressively work towards a resoultion for this incident. While we are unable to provide an ETA, the teams have had some successes in troubleshooting and getting closer to the root cause. The next scheduled update will be around 6:00 pm EDT (UTC-4).

 

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

 

Update: Wednesday June 18th 4:07 PM EDT (UTC-4)

 

After analysis by our support teams, it was determined that the incident was the result of a software bug of an Oracle Program. Information related to the incident has been passed on to our Product Engineering team. Once Product Engineering confirms they have a resolution to the issue, it will be deployed to the applicable Oracle Programs for your Eloqua service. No ETA for resolution is available at this time. Oracle is also reviewing the monitoring, alerting and standard operating procedures related to the incident. After these reviews are completed, additional appropriate corrective actions identified during the reviews will be taken, including deployment of the appropriate patch or release when available.

Our Cloud Operations Team is currently investigating an incident related to assets not saving for POD 2 clients.  This incident roughly started at 8:00 am EDT (UTC -4) and the next update will be around 12:00 pm EDT (UTC -4).

 

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

**Update**

Monday, June 16th, 12:44 pm EDT (UTC -4)

 

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.

Emergency Maintenance Advisory for Sunday, June 15th, 2014



Eloqua will be performing Emergency Maintenance on Sunday, June 15th, between 5:00 am -11:00 am EDT (UTC -4).

 

Downtime affect as follows. During parts of the maintenance:

 

•         Inbound activity will be lost (page views, email responses).

•         Form submissions will not be captured.

•         Application processing will be paused and resumed after downtime ends.

 

You are advised not to use the application during this period to avoid loss of work.

 

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

**Update**

Sunday, June 15th, 8:25 am EDT (UTC -4)

 

The maintenance concluded successfully at 6:45 am EDT (UTC-4) without incidents.

Filter Blog

By date: By tag: