Skip navigation

We have an emergency Eloqua Insight maintenance for POD1 clients. During this maintenance, clients will not be able to use Eloqua Insight.  We will be starting the work at 11:00 am EDT (UTC-4) and we anticipate this to be completed by 11:30 am EDT (UTC-4). The next scheduled update will be around 11:30 am EDT (UTC-4).

 

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

Thursday, October 31st, 11:38 am EDT (UTC -4)


The Production requires an additional hour for this maintenance to be completed. The next scheduled update will be around 1:00 pm EDT (UTC-4).


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

**Update**

Thursday, October 31st, 12:26 pm EDT (UTC -4)


The maintenance is completed.

We are currently tracking an incident where Eloqua Engage Emails with Dynamic Content are showing multiple times on send. Our Development Team is working on a resolution, but our Support Team has identified a workaround. In the interim, please contact our Support Team for assistance.

 

At this time, we don't have an ETA, but the next scheduled update will be Thursday, October 31st around 2:00 pm EDT (UTC -4).

 

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

**Update**

Thursday, October 31st, 3:35 pm EDT (UTC -4)


Our Development Team was able to resolve this incident. We are looking into hot-fixing this and at this time, we don't have an ETA.  Our next schedule update on this incident will be Friday, November 1st around 1:00 pm EDT (UTC -4)


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

**Update**

Friday, November 1st, 12:02 pm EDT (UTC -4)


We are still looking into hot-fixing this and at this time, we don't have an ETA.  Our next schedule update on this incident will be Monday, November 4th around 1:00 pm EDT (UTC -5)


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

**Update**

Monday, November 4th, 11:54 am EDT (UTC -5)


We are still looking into hot-fixing this and at this time, we don't have an ETA.  Our next schedule update on this incident will be around 3:00 pm EDT (UTC -5)


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

**Update**

Monday, November 4th, 3:07 pm EDT (UTC -5)


We are still looking into hot-fixing this and at this time, we don't have an ETA.  Our next schedule update on this incident will be around 6:00 pm EDT (UTC -5)


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

**Update**

Monday, November 4th, 6:01 pm EDT (UTC -5)


We are still looking into hot-fixing this and at this time, we don't have an ETA.  Our next schedule update on this incident will be Tuesday, November 5th around 1:00 pm EDT (UTC -5)


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

**Update**

Tuesday, November 5th, 9:33 am EDT (UTC -5)


This incident was hot-fixed at 9.10 am EDT (UTC-5) on POD 1 and POD 3. Our next schedule update on this incident will be Wednesday, November 6th around 1:00 pm EDT (UTC -5)


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

**Update**

Wednesday, November 6th, 10:54 am EDT (UTC -5)


This incident was hot-fixed on POD 2 as part of the scheduled roll-out and is now considered resolved.

Between 3:06 pm EDT and 3:44 pm EDT today, some clients on POD1 would have experienced some performance issues.

 

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.

 

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

We will be pausing lead scoring execution temporarily while we perform emergency maintenance, estimated time of completion 10:00 pm EDT (UTC -4), contacts who have performed activities during this time will be scored appropriately once maintenance is complete.

 

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

Tuesday, October 29th, 8:01 pm EDT (UTC -4)


The Production Team was able to complete the emergency maintenance ahead of schedule. Lead Scoring has been re-enabled. 

We are currently tracking an incident where private Eloqua Engage Templates are now public (visible) to all users in each instance. The Development Team is working on a resolution, but we are unable to provide an ETA. The next scheduled update will be on October 30th, around 11:00 am EDT (UTC -4).

 

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

**Update**

Wednesday, October 30th,10:51 am EDT (UTC -4)


The Development Team is working with select clients and our QA Team on a potential fix. The next scheduled update will be around 2:00 pm EDT (UTC -4).

 

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

**Update**

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


We are still working towards a resolution. We are targeting to have this resolved today. The next scheduled update will be around 4:00 pm EDT (UTC -4).

 

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

**Update**

Wednesday, October 30th,4:18 pm EDT (UTC -4)


The Development Team requires additional testing before we can full resolve this incident. The next scheduled update will be on Thursday, October 31st, 2013 around 10:30 am EDT (UTC -4).

 

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

**Update**

Thursday, October 31st, 9:54 am EDT (UTC -4)


We are targeting to hot-fix this incident today. The next scheduled update will be on around 11:00 am EDT (UTC -4) with the expected ETA.

 

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

**Update**

Thursday, October 31st, 2:12 pm EDT (UTC -4)


We are still going through our hot-fix process. The next scheduled update will be on around 4:30 pm EDT (UTC -4).

 

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

**Update**

Thursday, October 31st, 3:35 pm EDT (UTC -4)


We are looking into hot-fixing this and at this time, we don't have an ETA.  Our next schedule update on this incident will be Friday, November 1st around 11:00 am EDT (UTC -4)

 

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

**Update**

Friday, November 1st, 10:02 am EDT (UTC -4)


We are still looking into hot-fixing this and at this time, we don't have an ETA.  Our next schedule update on this incident will be around 2:00 pm EDT (UTC -4)


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

**Update**

Friday, November 1st, 11:54 am EDT (UTC -4)


This incident has been hot-fixed.

Following yesterday's Eloqua Insight Incident, the Development team is continuing towards a path to resolution. While only users created prior to 28/10/2013 @ 5:30 pm EDT have access to Eloqua Insight, if users require access and created after the aforementioned date, or need to modify their Eloqua Insight access level (such as moving from Eloqua Reporting to Eloqua Analyzer) – please contact our Eloqua Support Team and they will be able to assist in the interim.

 

Our next schedule update on this incident will be Thursday, October 31st around 4:00 pm EDT (UTC -4)

 

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

Thursday, October 31st, 9:50 am EDT (UTC -4)


The Development Team has been working with both our QA Team and Production Team. We are targeting to hot-fix this incident today at 11:00 am EDT (UTC-4). After the hot-fix process is complete, we will provide another update around 11:45 am EDT (UTC-4)

 

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

**Update**

Thursday, October 31st, 12:30 pm EDT (UTC -4)


The Development Team is continuing to work with both our QA Team and Production Team. The hot-fix scheduled for 11:00 am EDT (UTC-4) was unsuccessful. We don't have an ETA to offer, but our next schedule update on this incident will be around 4:30 pm EDT (UTC -4)


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

**Update**

Thursday, October 31st, 3:17 pm EDT (UTC -4)


We were able to split the original hot-fix into three phases. We are currently working on hot-fixing phase 1; phase 2 and 3 have yet to be scheduled.  Our next schedule update on this incident will be Friday, November 1st around 11:00 am EDT (UTC -4)

 

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

**Update**

Friday, November 1st, 10:02 am EDT (UTC -4)


We are looking into hot-fixing phase 2 as part of our Service Pack release this weekend, Sunday, November 3rd, 2013.  Our next schedule update on this incident will be Monday, November 4th around 11:30 am EDT (UTC -5)

 

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

**Update**

Monday, November 4th, 10:02 am EDT (UTC -5)


We are targeting to complete phase 2 and 3 this week.  At this time, we cannot provide an ETA, but our next schedule update on this incident will be Tuesday, November 5th around 11:30 am EDT (UTC -5)


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

**Update**

Monday, November 6th, 2:03 pm EDT (UTC -5)


We are targeting to complete phase 2 in the next day.  Our next schedule update on this incident will be Thursday, November 7th around 1:30 pm EDT (UTC -5)


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

**Update**

Thursday, November 7th, 1:14 pm EST (UTC -5)


In lieu of the recent Eloqua Insight maintenance that went out last night, we are targeting to complete phase 2 on Friday, November 8th, 2013. Our next schedule update on this incident will be Friday, November 8th around 1:30 pm EST (UTC -5)


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

**Update**

Friday, November 8th, 10:20 am EST (UTC -5)


We are re-targeting to complete phase 2 on Monday, November 11th, 2013. Our next schedule update on this incident will be Monday, November 11th around 2:00 pm EST (UTC -5)


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

**Update**

Monday, November 11th, 12:09 pm EST (UTC -5)


We are currently patching phase 2 to all PODs, the next update will be around 4:00 pm EST (UTC -5)


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

**Update**

Monday, November 11th, 2:36 pm EST (UTC -5)


Phase 2 has been pushed to production. Our next schedule update on this incident will be Thursday, November 14th around 2:00 pm EST (UTC -5) with respects to Phase 3.


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

**Update**

Friday, November 15th, 12:48 pm EST (UTC -5)


We are looking to hot fix Phase 3. At this time, we cannot provide an ETA, but our next schedule update on this incident will be Monday, November 18th around 2:00 pm EST (UTC -5).


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

**Update**

Tuesday, November 26th, 12:48 pm EST (UTC -5)


Phase 3 was hot-fixed on November 18th around 5.30 pm EST (UTC-5). This issue is considered resolved.

**Update**

Monday, October 28th, 7:00 pm EDT (UTC -4)


The issue was resolved at 5:40 pm

 

NOTE: Insight is only available for users that have been created prior to 28/10/2013 @ 5:30 pm EDT. In the short term, any user created after that who requires access to Insight will need to contact Eloqua Support.

 

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

**Update**

Monday, October 28th, 5:50 pm EDT (UTC -4)

 

We continue to work on a resolving this issue as a top priority.


Unless there's anything new to report on this matter, the next update will be provided tomorrow morning at ~9:30 am.

 

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

**Update**

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

 

We continue to work on a resolving this issue as a top priority.


The next update will be provided by 6:00 pm.

 

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

**Update**

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

 

We continue to work on a resolving this issue as a top priority.


The next update will be provided by 4:30 pm.

 

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

**Update**

Monday, October 28th, 11:30 am EDT (UTC -4)


We are currently experiencing an issue where Insight does not load for Pod 1 users and eventually times out or returns an error.


We are working on a resolution as a top priority.


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

 

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

There is currently a delay on first login to Insight - it can take 35 to 45 seconds. Once logged in to Insight, navigation and running reports occur normally.

 

This will happen with every new session.

 

We are working on correcting this issue.

**Update**


The Fall '13 Release concluded at 12:20 pm EDT (UTC -4).


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


**Update**


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

 

The Fall '13 Release has not yet concluded. This Advisory will be updated as more information comes in.


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

 

 

Eloqua Fall '13 Release

 

 

Please review the supporting resources available in the Oracle Eloqua Release Center.

 

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.

 

The Fall '13 Release will roll out between 5 and 11 am EDT (UTC -4), Sunday, October 27th, 2013.

 

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.

 

 

Insight Reporting Maintenance Advisory for Friday, October 25th, 2013

 

 

Insight maintenance will begin at 08:00 AM EDT (UTC -4) on Friday, October 25th, 2013, and will conclude by 11:00 AM EDT on Sunday, October 27th, 2013.

 

This will NOT affect access to reporting functionality. The application will remain available, and reports can be run, however any attempt to save, create or edit any reports will result in an error.

 

 

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

We are currently experiencing a delay with Test Sending emails. There may be a delay of approximately 15 minutes before emails which have been Test Sent are received. We are expecting this issue to be resolved at approximately 4:00 pm EDT (UTC -4). We will provide another update at that time.

 

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

**Update**

Thursday, October 24st, 2:44 pm EDT (UTC -4)

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

 

This issue has now been resolved. Test sends should now deploy without delay.

Between 9:11 am EDT and 11:27 am EDT today, some clients would have experienced some performance issues.

 

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, October 23rd, 01:10 am EDT (UTC -4)

 

Service Pack 2 of the Fall '13 Release concluded within the established window and without issues.


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




Eloqua Fall '13 - SP2

 

 

Please review the supporting resources available in the Oracle Eloqua Release Center.

 

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.

 

Service Pack 2 of the Fall '13 Release rollout starts at 11 pm EDT (UTC -4), Tuesday, October 22nd, 2013, and will conclude by 05:00 am EDT, Wednesday, October 23rd.

 

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

Sunday, October 20th, 11:50 am EDT (UTC -4)

 

The Fall '13 Release concluded within the established window and without issues.


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

 


Eloqua Fall '13 - SP2

 

 

Please review the supporting resources available in the Oracle Eloqua Release Center.

 

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.

 

Service Pack 2 of the Fall '13 Release will roll out between 5 and 11 am EDT (UTC -4), Sunday, October 20th, 2013.

 

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)

Between 3:49 pm EDT and 5:09 pm EDT today, clients on POD3 would have experienced some performance issues.

 

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.

 

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)

We have identified an incident where the Kapost Calendar App is not generating updates. The Development has been engaged and are working on a path to resolution. At this time, we are unable to give an ETA, but the next scheduled update will be Monday, October 21st around 10 am EDT.

 

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

**Update**

Monday, October 21st, 10:19 am EDT (UTC -4)


The Development Team is still investigating possible paths to resolution. The next scheduled update will be around 4pm EDT.

 

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

**Update**

Monday, October 21st, 4:07 pm EDT (UTC -4)


The Development Team has been working the Production Team. They believe they have identified a solution and are working on resolving this. The next scheduled update will be around 10am EDT on October 22nd, 2013.

 

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

**Update**

Monday, October 21st, 5:43 pm EDT (UTC -4)


The Development Team has resolved this issue. The team has identified Segment refreshing might be impacted for customers using the Kapost Calendar App,  but as a workaround, we recommend you re-open your assets affected to get an updated count. For example, on a newly created Segment, close out the segment and re-open it back, you should then see an update count. If you would like further viability for this incident, please contact support.

We have been experiencing significant delays in Data Imports (imports/uploads). The Import Service has been cycled, and the imports are processing. Some time will be necessary before the queue clears out completely. At this time we cannot offer an ETA, but the next scheduled update will be around 10 am EDT.

 

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

**Update**

Wednesday, October 18th, 8:42 am EDT (UTC -4)


We've upgraded this incident back to Red as we have identified the our previous attempts to resolve this hasn't worked. Our Production Team is still investigating the issue and the next scheduled update will be around 9.30 am EDT.

 

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

**Update**

Wednesday, October 18th, 9:31 am EDT (UTC -4)


Our Production Team is still investigating the issue and the next scheduled update will be around 10.30 am EDT.

 

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

**Update**

Wednesday, October 18th, 10:20 am EDT (UTC -4)


Our Production Team has confirmed the Data Imports are now processing and working through the current backlog in the queue. The next scheduled update will be around 12 pm EDT.

 

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

**Update**

Wednesday, October 18th, 11:08 am EDT (UTC -4)

 

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


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

**Update**

Wednesday, October 18th, 11:56 am EDT (UTC -4)


Our Production Team has confirmed the Data Imports are still processing and working through the current backlog in the queue. They anticipate the queue to be caught up within the next 3-4 hours. The next scheduled update will be around 2 pm EDT.

 

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

**Update**

Wednesday, October 18th, 2:25 pm EDT (UTC -4)


Our Production Team has confirmed the Data Imports are still processing and working through the current backlog in the queue. They anticipate the queue to be caught up within the next 2 hours. The next scheduled update will be around 4 pm EDT.

 

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

**Update**

Wednesday, October 18th, 3:52 pm EDT (UTC -4)


Our Production Team has revised their estimates, they now anticipate the queue to be caught up within the next 1 hour. The next scheduled update will be around 5:15 pm EDT.

 

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

**Update**

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


This incident is resolved.

We are currently experiencing an incident where campaigns or segments are taking an inordinate amount of time to either save or be refreshed. Our Production Team is working with our Development Team on investigating this incident. At this time we cannot offer an ETA, but the next scheduled update will be around 10 am EDT.

 

To determine if you are on Pod1:

Log into Eloqua as you normally do

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, October 18th, 9:34 am EDT (UTC -4)


Our Production Team is still investigating the issue and the next scheduled update will be around 10.30 am EDT.

 

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

**Update**

Wednesday, October 18th, 10:15 am EDT (UTC -4)


We have identified that assets are being saved, however there is still an issue with the Eloqua Application refreshing by itself. As a workaround, we recommend you re-open your assets affected to get an updated count. For example, on a newly created Segment, close out the segment and re-open it back, you should then see an update count. The Development Team has been contacted and were working towards a resolution. We are still not able to give an ETA, but the next scheduled update will be around 12 pm EDT.

 

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

**Update**

Wednesday, October 18th, 10:59 am EDT (UTC -4)

 

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

We are currently experiencing issues with Eloqua for some clients. Our Production Team has been notified and were currently investigating, the next scheduled update will be around 10 am EDT.


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

**Update**

Wednesday, October 16th, 9:57 am EDT (UTC -4)


The production team has identified the hardware failure and is in the process to resolve the incident. We estimate by 1.30 pm EDT we should be operational. The next scheduled update will be around 1 pm EDT.


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

**Update**

Wednesday, October 16th, 12:10 pm EDT (UTC -4)


All emergency contacts affected by this incident have been notified. The Production Team has revised their ETA based on our current progress, they now anticipate this will be completed by 3 pm EDT. The next scheduled update will be around 2:30 pm EDT.


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

**Update**

Wednesday, October 16th, 2:12 pm EDT (UTC -4)


The Production Team is still working to resolve this incident, they are still aiming to get this completed by 3 pm EDT. The next scheduled update will be around 2:45 pm EDT.


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

**Update**

Wednesday, October 16th, 2:45 pm EDT (UTC -4)


The Production Team is still aiming to get this completed by 3 pm EDT. The next scheduled update will be around 3:15 pm EDT.


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

**Update**

Wednesday, October 16th, 2:49 pm EDT (UTC -4)


The Production Team is still aiming to get this completed by 4 pm EDT. The next scheduled update will be around 3:45 pm EDT.


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

**Update**

Wednesday, October 16th, 3:50 pm EDT (UTC -4)


The Production Team is still working on this incident, but is forced to revise their ETA. They are now targeting 5 pm EDT. The next scheduled update will be around 5:30 pm EDT.


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

**Update**

Wednesday, October 16th, 5:40 pm EDT (UTC -4)


The Production Team has resolved this incident as of 5:28 pm EDT. 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.


With Salesforce.com’s Winter 2014 release, we are seeing incidents with authentication. More specifically, the incident appears to only affect customers who have configured Eloqua to use Salesforce as its identity provider, and who have configured Salesforce to use an external system as its identity provider, chaining authentication from one system to the next:

 

Eloqua -> Salesforce -> (an external identity provider)

 

In this configuration, Eloqua will ask Salesforce to authenticate the user, and Salesforce will in turn ask the external identity provider to authenticate the user. The point of failure appears to be in the communication between Salesforce and the external identity provider.

 

If you are affected by this incident, please contact our Support Team and we will  work with you on next steps.

 

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

**Update**

Wednesday, October 18th, 5:40 pm EDT (UTC -4)


We have worked with all our clients regarding this incident on path to resolutions. This is now considered resolved.

**Update**

Thursday, October 10th,12:40 am EDT (UTC -4).

 

This issue was fully resolved at 12:33 pm EDT (UTC -4).

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

Insight has become intermittently inaccessible for Pod 1 clients.

 

We are working on resolving this issue.

 

We expect the problem to be resolved momentarily.

 

 

To determine if you are on Pod1:

Log into Eloqua as you normally do

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

Monday, October 7th.

 

Import queues have cleared. There should be no delays.


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

 

 

We have been experiencing significant delays in Data Imports (imports/uploads). The Import Service has been cycled, and the imports are processing. Some time will be necessary before the queue clears out completely.

**Update**

Wednesday, October 9th,11:30 am EDT (UTC -4).

 

This issue has been resolved.

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

This issue is  affecting Eloqua 10 users who:

 

  • are using non-English versions of their browser
  • are using non-English versions of their operating system
  • have configured their browser to advertise a preference for a non-English language

 

If you are in this situation, you may see randomly generated words or phrases in that language in the application.

 

Affected users can work around the problem by changing the first URL they access to include the URL parameter “culture=en-US” (examples below):

 

o   https://login.eloqua.com/?culture=en-US

o   https://secure.eloqua.com/Main.aspx?culture=en-US

o   https://www02.secure.eloqua.com/Main.aspx?culture=en-US

o   https://secure.p03.eloqua.com/Main.aspx?culture=en-US

 

 

This will fix a preference for U.S. English for the remainder of the user’s session ONLY.


We are working to resolve this issue as soon as possible.

**Update**

Sunday, October 6th.

 

The Fall '13 Release concluded within the established window and without issues.


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

 


Eloqua Fall '13 Release

 

 

Please review the supporting resources available in the Oracle Eloqua Release Center.

 

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.

 

The Fall '13 Release will roll out between 5 and 11 am EDT (UTC -4), Sunday, October 6th, 2013.

 

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, October 6th.

 

Maintenance concluded without issues.

 

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

 


Insight Reporting Maintenance Advisory for Friday, October 4th, 2013

 

 

Insight maintenance will begin at 10:00 AM EDT (UTC -4) on Friday, October 4th, 2013, and will conclude by 11:00 AM EDT Sunday, October 6th, 2013.

 

This will NOT affect access to reporting functionality. The application will remain available, and reports can be run, however any attempt to save, create or edit any reports will result in an error.

 

 

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 Fall '13 Release - Service Pack 1

 

 

Please review the supporting resources available in the Topliners Release Resource Center.

 

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.

 

The Fall '13 SP1 rollout starts at 11:00 pm EDT (UTC -4), Tuesday, October 1st, 2013, and will conclude by 5:00 am EDT on Wednesday, October 2nd.

 

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, October 2nd,12:10 am EDT (UTC -4)

 

SP1 rollout concluded without issues.


Actual rollout period: Tuesday, October 1st, 11 – 11:50 pm EDT.

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

Filter Blog

By date: By tag: