Critical Patch for Oracle Preventative Controls Governor - PCG

MOS Document: 
                        How to find Oracle GRC - AACG/CCG and PCG version And Last Upgraded Patchlevel (Doc ID 2082278.1)

How to find Oracle GRC - AACG/CCG and PCG version And Patch level

GOAL

How to to find out the existing version for Oracle GRC - AACG/CCG/PCG products applications ?

SOLUTION

A) For AACG : 8.6.4.x and above releases

Front End:
- Login to the AACG Application
- Click on the Idle Icon on the right top corner
- a pop-up message will contains the version

                            Or

Backend :
- Run : select * from grc_sys_version;


For CCG : 5.5.x and above

Front End:
- Login to the CCG Application
- Click on Help > About Products
- Release Number will give you the version details, and the Patch history will give the list of critical patches which are applied on the instance

                     Or

Backend :
- Run : select * from am_product_patches order by patch_start_date desc; 


For PCG : 7.x and above

Front End:
- Login to the EBS Application
- GRC Controls Responsibility, Navigator select Administration, and then Install History. 

                        Or 

Backend :
- Run : select * from la_install_history order by install_time desc;

Oracle CCG Installation Steps Overview - EGRC

High Level Steps:

Install Database
Install Weblogic Server
Install Fusion Middleware
Create Weblogic Domain
Install CCG 

Installation & Configuration Steps:

Install Database
Install Weblogic Server
Create Repository using RCU
Install Fusion Middleware
Create Weblogic Domain
Install CCG 

Post Installation Steps:

1) Deploy CCG war file 
2) Creation of datasource from weblogic console using "jdbc/amhome" as name of jndi name
3) Update amhome.conf
4) Update quartz.properties ( Provide values according to your instance details)
5) Add the following two lines just below the initial comments in the file startWebLogic.sh file 
-Djava.awt.headless=true -Djava.security.auth.login.config=web-application-path/WEB-INF/jaas.config -XmsInitial -XmxMaximum
6) Start your weblogic console
7) CCG URL will be like "hostname.com:port/ccg/jsp/amloginframe.jsp"
8) Default username & password is amadmin - amadmin

Oracle Siebel Blank Page Issue

File Synchronization Not Happening Between sweapp and siebsrvr, Causing OpenUI Application Blank Page

APPLIES TO:

Siebel Sales Version
8.1.1.14 [IP2014] and later
Information in this document applies to any platform.

SYMPTOMS

On : 8.1.1.14 [IP2014] version, System Admin
Open UI application not working fine after upgrade from Siebel 8.1.1.11 to 8.1.1.14. IRM, upgrep and upgphys completed
successfully.

ACTUAL BEHAVIOR

OpenUI application displaying blank page after entering login credentials.

EXPECTED BEHAVIOR

Home Page should be displayed after successful login.

STEPS

The issue can be reproduced at will with the following steps:
1. Enter the Siebel application URL
2. Enter the credentials in Login page
3. Blank page is displayed

CAUSE

The issue is caused due to synchronization not happening between Web Server's SWSE_HOME/PUBLIC/ENU folder and the Siebel server's SIEBEL_HOME\siebsrvr\WEBMASTER folder.
File synchronization should be successful, when QuickFix / FIxPack is applied, upgrade of server or any changes at SWSE level. Files were not updated on Web Server which resulted in Blank Page being displayed.

SOLUTION

To implement the solution, please execute the following steps:
1. Stop Web server, Stop Siebel Services
2. Create blank <23044> folder under SWSE_HOME/PUBLIC/ENU
3. Set the permissions to full.
4. Copy '$SIEBEL\siebsrvr\WEBMASTER\siebel_build' contents to 'SWSE_HOME/PUBLIC/ENU/23044 folder'
5. Start Web server, Start siebel services
6. Clear the browser history and delete the cache.
7. Launch the OpenUI client and verify

MOS ID : 2009448.1

Siebel Server is Not Started up And Getting SBL-SEC-10018 Error in namesrvr.log

SYMPTOMS:

Siebel server is not getting started and gateway server is already started. In the namesrvr.log there is the following error:

1 000000024f061e2c:0 2012-01-06 11:24:26 (secmgr.cpp (2679) err=4597538 sys=0) SBL-SEC-10018: data source connect string or table owner is empty.

GenericLog GenericError 1 000000024f061e2c:0 2012-01-06 11:24:26 (secmgr.cpp (2751) err=4597521 sys=0) SBL-SEC-10001: An internal error has occurred within the authentication subsystem for the Siebel application. Please contact your System Administrator.

CAUSE:

After further investigation found that, gateway service file got corrupted and below are the entries in svc.gtwyns and here gateway.cfg file is missing in below line.

siebsvc -s gtwyns -a "/f /siebel/gtwysrvr/sys/siebns.dat /t 2320 "

SOLUTION:

Recreate gateway service file again with the below command.

1. Stop Gateway server.
2. siebctl -S gtwyns -a -g "/f /siebel/gtwysrvr/sys/siebns.dat /t 2320 /c /siebel/gtwysrvr/bin/gateway.cfg"
3. Restart the gateway server and siebel server services.

MOS ID: (Doc ID 1394293.1)

Connect Via SCAN Intermittently Fails With ORA-12516: TNS:listener Could Not Find Available Handler With Matching Protocol Stack

SYMPTOMS:

• multinode (3+) RAC  cluster
• application using SCAN and a dedicated service (here serv1) to connect to the database
• service is configured to run on instances 1 & 2 (preferred)
• intermittently connect attempts fail with error ORA-12516: TNS:listener could not find available handler with matching protocol Stack

CAUSE:

The status of the service used to connect to the database shows online on instances 1 & 2:

ora.racdb1.serv1.svc
  1 ONLINE ONLINE racdb11
  2 ONLINE ONLINE racdb12

however the node listener on node 2 is having some problem, 'crsctl stat res -t' shows:

ora.LISTENER.lsnr
  ONLINE ONLINE racnode1
  ONLINE INTERMEDIATE racnode2 CHECK TIMED OUT
  ONLINE ONLINE racnode3

Running 'lsnrctl status LISTENER' shows that the listener has no TCP endpoints open:

Listening Endpoints Summary...
  (DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(KEY=LISTENER)))
The listener supports no services
The command completed successfully

It is unclear how the listener got into this state., it prevents the instance(s) on node racnode2 to register their services with the node listener, since the instance connects to the listener via the TCP port 1525.

The instances can however register their services with the SCAN listeners, so the ORA-12516 error seems to be reported whenever a SCAN listener tries to hand off a connect request to the listener on node racnode2.

SOLUTION:

1. Find the PID of the node listener - e.g.:

$ ps -ef | grep tns
oracle 18135 1 0 Oct 3 ? 348:26 /u01/app/grid/11203/bin/tnslsnr LISTENER_SCAN1 -inherit
oracle 21652 1 0 Feb 18 ? 96:44 /u01/app/grid/11203/bin/tnslsnr LISTENER -inherit

2. Kill the listener using:

kill -9 21652

3. Restart the listener using:

srvctl start listener -n racnode2

4. Make sure the listener is now listening on TCP endpoints

lsnrctl status LISTENER

5. One minute after the listener has been started check if it shows services:

lsnrctl services LISTENER

Reference: Connect Via SCAN Intermittently Fails With ORA-12516: TNS:listener Could Not Find Available Handler With Matching Protocol Stack (Doc ID 1638175.1)

ORA-12516: TNS:listener could not find available handler with matching protocol stack

CAUSE

 This is an issue with the number of database process/sessions. There are some bugs that reduce the processes/sessions required, and the fixes are included in Patch:19197270 AD:R12.AD.C.DELTA.6 PATCH and later.

SOLUTION


As a workaround, bouncing the database, and raising the number of processes/sessions should let you complete the patch (you will need to restart the patch after you do the workaround). (NOTE: Simply bouncing the database might allow you to continue.)

Reference: adop fails with "ORA-12516: TNS:listener could not find available handler with matching protocol stack" (Doc ID 2105049.1)