Known issues in Audience Manager and Outbound E-mail
The following list describes issues that are known to exist in Audience Manager and Outbound E-mail.
- Maximum open cursors exceeded (JNDI only, and possibly only WebSphere)
- Problem:
'ORA-01000 Maximum open cursors exceeded'is regularly thrown by Audience Manager on the presentation side becauseResultSets are not explicitly closed. According to the JavaDoc forResultSet::it isn't necessary, although this seems to be only true when not using JNDI; when using JNDI it will leave the cursors open. - Cannot set number fields to a fixed value during import in Internet Explorer 8
- Problem: When importing Contacts into an Address Book using Internet Explorer 8, you cannot override integers using the [Set to a fixed value] option.
- Unable to move contacts in Internet Explorer 7, or in Internet Explorer 8 Compatibility View
- Problem: When you try to move Contacts in Internet Explorer 7, or in Internet Explorer 8 running in Compatibility View, you will see a blank dialog.
- Enforcing of the maximum length of Extended Detail Fields
- Problem: Audience Manager does not enforce the maximum length of Extended Detail Fields, so when saving a Contact with data exceeding 255 characters a database exception is thrown.
"ContactDoesNotExist"exception is always logged- Problem: The
"ContactDoesNotExist"exception is always logged and cannot be caught in .NET. Therefore, on busy Web sites where many people are continuously forgetting their login details, your log file will fill up with"ContactDoesNotExist"error messages. - Open database connection warning when upgrading Audience Manager database
- Problem: When you run the SDL Tridion Database Manager to upgrade your Audience Manager you get an open database connection warning even when there are no open connections.