Tuesday, 20 September 2016

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;

Wednesday, 7 September 2016

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)