Search for existing answers to your product and support questions.
Familiarize yourself with our support site and learn best practices in working with our team.
Manage Service Requests, View and update service requests submitted by you and others in your organization.
Submit a new issue to our technical support team.
Oracle B2C Service insights from our Technical Support team subject matter experts
Browse resources to assist you in launching your implementation and ensure a successful go-live.
Access your OCI account.
Find product documentation for supported versions of B2C and documentation libraries for related service solutions.
You will have the tools to improve your customers' experience when you learn about all the things our products can do.
Find links for API documentation, Custom Processes, Customer Portal, and Agent Browser UI Extensibility Framework.
Explore how accelerators are designed to demonstrate how an integration scenario could be built using the public integration and extension capabilities of the Oracle B2C Service.
Prepare for a successful transition by reviewing upcoming release changes and enhancements.
Explore webinars, events, and feature kits to learn about B2C Service features, functionality, and best practices from the technical experts.
Oracle MyLearn offers a portfolio of free and paid subscription-based learning resources to help you gain valuable skills, accelerate cloud adoption, increase productivity, and transform your business.
Empower your team with the skills to implement, configure, manage, and use your applications with Customer Experience Cloud Training.
Our goal is to facilitate a friendly, supportive environment where members can easily collaborate with each other on solutions and best practices.
Ask and answer questions specific to B2C.
This is an exciting resource intended to help with your Oracle Service Cloud Analytics.
Share product improvement ideas and enhancement requests with Oracle Development, while collaborating with other Oracle customers and partners.
Update your phone number, email notification preferences, and severity 1 and severity 2 contact preferences.
View the contact managers within your organization.
Find contact information of the Technical Account Manager (TAM) and Client Success Manager (CSM) for your organization.
Environment:
File Attachments, Mailboxes Oracle B2C Service
Resolution:
A number of factors affect what size file attachments can be attached within your Oracle B2C Service application. This applies to files attached to your records from the administration pages, such as a staff member attaching a file to an incident, answer, or sales opportunity. This also applies to files attached to incidents that are submitted from the Ask a Question page and Chat.
The FATTACH_MAX_SIZE configuration setting specifies the maximum size in bytes of files which can be uploaded to the Oracle B2C Service Server. Maximum is 125829120 (120 MB). Default value for Oracle hosted mailboxes is 20971520 (20 MB) and the highest(server side limit) value is 30MB. However, several other variables also affect the maximum size. The FATTACH_MAX_SIZE is also used to restrict the size of a report being forwarded.
Path to setting(s): Select Configuration from the navigation area > Site Configuration > Configuration Settings > and search by Key.
All web servers supported by Oracle contain a time-out setting that terminates connections after a set period. All sites have this set to 5 minutes as a security precaution. In general, this time period has the biggest effect on the maximum allowed file attachment size. This is also applicable when attaching files for a service request in the Oracle B2C Service Support site.
With average bandwidth, most users can attach files of about 5.5 to 8 MB in 5 minutes. So, for all practical purposes, this is the limit. Keep in mind, circumstances exist when you would not be able to attach a 6 MB file to an incident -- primarily due to your connection speed to your Web server (or our hosting facilities if applicable). If a user is running via a modem or other slower connection, they might only be able to attach small files to an incident. Users with exceptionally high bandwidth, however, might be able to attach files larger than 8 MB. The maximum size file attachment you can submit through the end-user pages is constrained primarily by a 5 minute limit on submission time.
In addition, some networks and firewalls have limits on the file sizes that can be passed through a connection. In some cases this setting is the limiting factor in attachment size.
Sites which were originally created on versions older than August 2015 may require an adjustment to the PHP.INI file to reflect some large file attachment size settings. If you make changes to your attachment size, your site was created prior to August 2015, and your changes do not appear to be working please create a service request with support asking for an an adjustment to the PHP.INI file on our servers.
File attachments arriving in your Oracle B2C Service site in emails are impacted by mail server allowance and mailbox configuration settings. For Oracle-managed mailboxes our mail servers accept emails up to a total size of 30 MB regardless of any settings within your site / mailbox. This 30 MB limit is firm and cannot be changed. Total email size depends on many factors, but even a simple HTML email with little email body content can be large enough to trigger a 30 MB size limit rejection with 24 MB of attachments. Emails with embedded images, even small images in signatures also contribute to email size. Because total email size depends on many factors we are unable to provide a specific limit just for the attached files. Emails rejected by mail servers have a bounce or reject message that includes "SMTP 552 size limit exceeded". The mail server is the first point of entry for emails into Oracle-managed mailboxes. Email accounts not hosted by Oracle may not have this same size limitation. Check with your mail administrator or provider for details in this case.
After the mail server, emails are then processed by techmail utility. At this point the following settings come into play:
For larger files that you want to attach to an answer or incident, consider storing your file on your web server. These files would be stored in a location along with the other pages for your corporate web site.
You can then use the URL for that file as either a link in an answer or provide the URL in a response to an incident to allow access to the file or document. This allows you to avoid the attachment size consideration. To use this method, work with your IT group or your webmaster to determine where the file should be stored and how to access it.