We had issue with our production environment where server was generating huge amount of Archive logs and causing archive logs to fill frequently, which eventually cause shows unexpected error on application server.
As an solution, refer below notes from Oracle support.
- P6 Global Scheduled Services Are Stuck In A “Running” State (Doc ID 1400104.1)
- Master Note For Primavera P6 Services (Doc ID 1612845.1)
- How To Restart Project Scheduled Services That Are “Stuck” In A Running State (Doc ID 1418876.1)
Many times we faced an issue where messages piling up in resequencer and from mediator container id lease table we found that there is one container ID which is not getting refreshed (renewal) and holding messages. Now in order to fix this we first need to track that bad container ID belongs to which specific soa server in order to take appropriate action on that server only.
This can be identified by increasing TRACE log level of mediator. Below are the steps;
- Login to EM console.
- Go to Log Configuration of SOA Infra
- Put TRACE 32 at oracle.soa.mediator.dispatch and save the changes.
Note: It does not require restart of the server.
Check soa server diagnostic logs where below string starts coming by which we can identify this is the container ID.
Renew container id [BC0S40987623G43K12368TY243P321]
Though you might be finding this post silly but trust me I had to struggle a lot to find this issue in one of my team machine.
We had installed Jdev 11117 and for SOA Extension Plugin, we was having a download zip file, so used that but that caused issue mismatch. Though Jdev did not prompt me any warning for version mismatch but later while using DBAdapter, we found that we were unable to import the table or other things were not working properly.
To fix this issue, we installed the SOA extension plugin from the update which was compatible with Jdev11117.
So my learning is, always download the plugin from updates 🙂
While running the Oracle installer on unix box, you might see below error message. This is normally come when UI display on machine is disabled.
Error: – Checking monitor: must be configured to display at least 256 colors >>> Could not execute auto check for display colors using command /usr/bin/X11/xdpyinfo. Check if the DISPLAY variable is set.
Failed <<<< Some requirement checks failed. You must fulfill these requirements before.
Follow below setups to fix this issue
Download Xming setup to your local directory and Launch Xming using XLaunch.exe
You will see Xming server running on your task bar.
Setup putty to configure X11–>Enable X11 forwarding; also provide value at X display location as
Log-In server in same session and now you will be able to see installer UI screen.
I have came across a requirement in my project where I need to renew the existing SSL certificates of OHS. Same steps can also be used in case of replacing the default SSL certificates. Below are the major steps which needs to be done;
1. Open Oracle Wallet Manager GUI and create an empty wallet.
2. Create certificate request by adding certificate to that wallet. It will ask for many details but most important is common name which is the server name and can be found in httpd.conf file.
3. After wallet is created with Export that wallet and it will act as CSR (certificate signing request) which needs to be send to CA (certificate authority).
4. Once CA approves then signed certificates will be given by CA. Import those certificates using OWM in the above created wallet.
5. Save the wallet as cwallet.sso file in <instance_home>/config/OHS/<instance_name> directory.
6. Update the new wallet created above in OHS config files i.e. httpd.conf and ssl.conf files.
7. Restart OHS.
This is a very common error you will be seeing while importing an OSB project.
You will be seeing this error when you will try to import a higher version of jar file in your OSB which is installed on lower version. Like a jar file which was created on OSB 11.1.7 and you are trying to import in OSB 11.1.6 or lower version of installation.
To fix this issue, open the jar file using 7-zip or some other tool and edit your ExportInfo file (as highlited in below screen shot) by providing a OSB version you are running with.
Save the change and you will be all set to import the file.
Blackouts allow Enterprise Manager administrators to suspend all data collection activity on one or more monitored targets. The primary reason for blacking out targets is to allow Enterprise Manager administrators to perform scheduled maintenance on those targets.
Login in OEM 12c and click on Enterprise à Monitoring à Blackouts
Click on “Create” to have a new blackout. If you have already existing blackouts and want a copy of same, you can use “Create like” too.
Fill blackout details and click on Add target. From the popup, select the target for which blackout needed.
Select the blackout options.
Select the scheduling options.
Review the information and you are all set.