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:
Utilities, Agedatabase, Configuration Settings
Resolution:
The agedatabase utility compares the time_respond field in the database to the value in the CI_HOURS configuration setting to determine if the incident has been in the waiting state long enough to be set to solved. If incidents set to Waiting are not getting set to Solved, there are a few things to consider:
If NO Waiting incidents are getting set to Solved:
Check the Site Tools > Utility Stats page to confirm agedatabase is running. If errors are encountered, submit a service request to Ask Technical Support to investigate further.
If only SOME Waiting incidents are not getting set to Solved:
If you have a multi-interface site, verify that the CI_HOURS setting for the interface associated with the incidents has a positive value. Setting CI_HOURS in an interface to zero turns off the feature in that interface. Incidents are set to Solved based on the CI_HOURS of the assigned interface. Therefore, if CI_HOURS is set to zero in an interface, waiting incidents assigned to that interface do not automatically get set to solved.
In addition, review the status that the incidents are being set to and verify that the status type is set to Waiting. For example, if staff members set incidents to a custom status, make sure that the custom status is a Waiting status type. To check the status type, use the steps below.
1. The path is Configuration > Application appearance > Customizable Menus > System Menus
2. Select Incident Statuses to see a list of current statuses and their status types
If the status type is not Waiting, you must create a new custom status to replace the existing one. It is not possible to edit the status type of an existing incident status.
If incidents are getting set to solved after more hours have passed than is configured in CI_HOURS:
The agedatabase utility only runs once a day. Incidents are closed at the time the 'utility runs' are processed and it runs if the incident has been in a waiting status for more than CI_HOURS. Depending on when the incident was set to waiting, the incident might be set to Solved almost 24 hours after the CI_HOURS setting. CI_HOURS works in conjunction with CI_WAITING_CALC_DAYS. This setting defines the days that agedatabase will include when calculating how long an incident has been in the Waiting state. The format is "SuMTuWThFSa." If left blank, agedatabase will include all days. Default is SuMTuWThFSa.
Path to setting(s): Select Configuration from the navigation area > Site Configuration > Configuration Settings > and search by Key.