DB : Could not execute auto check for display colors using command /usr/bin/xdpyinfo. Check if the DISPLAY variable is set. Failed

Error:
oratest@myserver database]$ ./runInstaller
Starting Oracle Universal Installer...

Checking Temp space: must be greater than 120 MB.   Actual 61931 MB    Passed
Checking swap space: must be greater than 150 MB.   Actual 19999 MB    Passed
Checking monitor: must be configured to display at least 256 colors
    >>> Could not execute auto check for display colors using command /usr/bin/xdpyinfo. Check if the DISPLAY variable is set.    Failed <<<<

Some requirement checks failed. You must fulfill these requirements before

continuing with the installation,

Continue? (y/n) [n] n

User Selected: No

Exiting Oracle Universal Installer, log for this session can be found at /d01/oracle/app/oraInventory/logs/installActions2015-06-24_10-03-30AM.log
[oratest@myserver database]$

Solution:

As a root user in VNC type xhost + to continue the installation
[root@myserver TEST]# xhost +
access control disabled, clients can connect from any host

DB : Installing oracle database fails with inventory owner permission denied

When installing new database as "oratest" new user on the existing server with other databases running in it the installation failed with below error

Error:

[oratest@myserver database]$ ./runInstaller
You do not have sufficient permissions to access the inventory '/d01/oracle/app/oraInventory'. Installation cannot continue. It is required that the primary group of the install user is same as the inventory owner group. Make sure that the install user is part of the inventory owner group and restart the installer.: Permission denied
[oratest@myserver database]$

Solution:
Change the oratest user group to same as the group of oraInventory

As a root user change the "oratest" group to "dba" as below

useradd -G dba oratest

EBS : dbTier autoconfig fails with afdbprf.sh adcrobj.sh

Error:

adcvmlog.xml renamed to /oradb/oracle/11.2.0.3/appsutil/log/TEST_drebsdb01/06080947/adcvmlog.xml.06080948


[AutoConfig Error Report]
The following report lists errors AutoConfig encountered during each
phase of its execution.  Errors are grouped by directory and phase.
The report format is:
      <filename>  <phase>  <return code where appropriate>

  [PROFILE PHASE]
  AutoConfig could not successfully execute the following scripts:
    Directory: /oradb/oracle/11.2.0.3/appsutil/install/TEST_drebsdb01
      afdbprf.sh              INSTE8_PRF         1

  [APPLY PHASE]
  AutoConfig could not successfully execute the following scripts:
    Directory: /oradb/oracle/11.2.0.3/appsutil/install/TEST_drebsdb01
      adcrobj.sh              INSTE8_APPLY       1


AutoConfig is exiting with status 2

AutoConfig execution completed on Mon Jun  8 09:48:27 2015

Time taken for AutoConfig execution to complete : 0 mins  49 secs


Solution:

Enter the correct apps password while running autoconfig and check whether APPS account is locked by connecting as SYSDBA
SQL> select USERNAME,ACCOUNT_STATUS,LOCK_DATE from dba_users where USERNAME='APPS';

USERNAME                       ACCOUNT_STATUS                   LOCK_DATE
------------------------------ -------------------------------- ---------------
APPS                           LOCKED                           08-JUN-15

SQL> alter user apps account unlock;

User altered.

SQL> select USERNAME,ACCOUNT_STATUS,LOCK_DATE from dba_users where USERNAME='APPS';

USERNAME                       ACCOUNT_STATUS                   LOCK_DATE
------------------------------ -------------------------------- ---------------
APPS                           OPEN

now re-run the autoconfig in dbTier

EBS : Login to application gets "unable to authenticate session" or "ORA-01403 error"

When we login to the application we get unable to authenticate session or ORA-01403 error

ERROR:

<PRE>Oracle error 1403: java.sql.SQLException: ORA-01403: no data found ORA-06512: at line 1 has been detected in FND_SESSION_MANAGEMENT.CHECK_SESSION. Your session is no longer valid. </PRE> 

Servlet error: An exception occurred. The current application deployment descriptors do

Solution 1

1. Execute the following scripts from $FND_TOP/patch/115/sql as apps user:
SQL> @AFICXSMS.pls %
SQL> @AFICXSMB.pls %
2. Bounce the server.
3. Retest the issue.

Reference :Login Page Throws Error 1403: Java.Sql.Sqlexception: Ora-01403: No Data Found Ora-06512: At Line 1 H (Doc ID 1336030.1)


Solution 2:

 "Unable to authenticate session"

1. Open a new explorer window using its own session cookie by selecting File -> New Session from the Menu Bar in an existing browser window. (IE9 Users may have to enable the Menu Bar first by right clicking the browser header frame and selecting Menu Bar.)
2. Run from the command line adding the -noframemerging parameter
    e.g. Start -> Run -> iexplore -noframemerging
3. Create a new IE icon adding the -noframemerging parameter
    e.g. Start -> Program Files
4. Right click on the Internet Explorer icon and select Properties

5. Add -noframemerging to the end of the link in the Target field
    e.g."C:\Program Files\Internet Explorer\iexplore.exe" -noframemerging
6. Click the OK button to close the window

Reference : R12: Using IE8 to access two EBS Instances runs in error "Unable To Authenticate Session" (Doc ID 1098563.1)

Solution 3:

1. Go to Control Panel
2. Select Java Control Panel from the list.
3. From the popup window (Java Control Panel), uncheck "Enable the next-generation Java Plug-in" option.
4. Click "Apply" and click "OK"
5. Clear browsing history (Internet Explorer Menu Bar: Tools --> Delete Browsing History) and close all the browser sessions.
6. Open IE browser and try to access Oracle Applications, if the issue still persists reboot the system.

Solution 4:

Disable Internet Explorer add-ons:

• Click "Tools" and select "Internet Options".
• Click "Advanced" tab on the right.
• Under "Browsing", remove/uncheck the "Enable third-party browser extensions" check box.
• Click "OK" and close all opened Internet Explorer.
• Open New Internet Explorer 

DB startup time sql query

SELECT TO_CHAR (startup_time, 'dd-mon-yyyy hh24:mi:ss') start_time from V$instance;

ORA-20002: 3825: Error '-24033 - ORA-24033: no recipients for message' encountered during execution of Rule function 'WF_RULE.ERROR_RULE' for event 'oracle.apps.fnd.cp.gsc.SvcComponent.stop' with key 'SVC:29-APR-2015'. FUNCTION_NAME=WF_EVENT_OJMSTEXT_QH.enqueue()

Error:
When we try to start/stop the Worflow mailer it shows this error,

ORA-20002: 3825: Error '-24033 - ORA-24033: no recipients for message' encountered during execution of Rule function 'WF_RULE.ERROR_RULE' for event 'oracle.apps.fnd.cp.gsc.SvcComponent.stop' with key 'SVC:29-APR-2015'. FUNCTION_NAME=WF_EVENT_OJMSTEXT_QH.enqueue()


Solution:

To resolve the issue try restarting the components

1. Workflow Mailer Service
2. Workflow Document Web Services
3. Workflow Agent Listener Service

Navigation to restart the components

• Login as SYSADMIN --> System Administrator --> Oracle Application Manager --> Workflow 
• Click on "Notification Mailer" --> Click "Workflow Mailer Services" Under Container Column --> Select "Workflow Mailer Services" --> Select "Start" --> "Go" button --> Ok
• Similary do the same for "Workflow Document Web Services" and "Workflow Agent Listener Service"

Now the workflow mailer will be Started/Stopped

EBS : Transparent Data Encryption (TDE) implementation

1. Add the below entry in the sqlnet.ora

ENCRYPTION_WALLET_LOCATION=
  (SOURCE= (METHOD=FILE)(METHOD_DATA=
    (DIRECTORY=/oradb/oracle/11.2.0.3/admin/<CONTEXT_NAME>/encryption_wallet/)
))


2. Create the directory to contain the encrypted key:

mkdir -p /oradb/oracle/11.2.0.3/admin/<CONTEXT_NAME>/encryption_wallet/


3. Creating the wallet with password "g00g1e": login as sysdba

Syntax:
ALTER SYSTEM SET ENCRYPTION KEY AUTHENTICATED BY <password>;

Eg:
ALTER SYSTEM SET ENCRYPTION KEY AUTHENTICATED BY "g00g1e";

4. Encrypting the columns of the table: login as sysdba

Syntax:
ALTER TABLE owner.table_name MODIFY(column_name ENCRYPT NO SALT);
ALTER TABLE owner.table_name MODIFY(column_name ENCRYPT);

Eg:
ALTER TABLE HR.PER_ALL_PEOPLE_F MODIFY(NATIONAL_IDENTIFIER encrypt no salt);
ALTER TABLE HR.PQP_EXT_CROSS_PERSON_RECORDS MODIFY(NATIONAL_IDENTIFIER encrypt no salt);
ALTER TABLE BEN.BEN_PL_F MODIFY(NAME  encrypt);

5. Once you added the columns to be encrypted close the wallet using below command: login as sysdba

Syntax:
ALTER SYSTEM SET ENCRYPTION WALLET CLOSE IDENTIFIED BY <password>;

Eg: 
ALTER SYSTEM SET ENCRYPTION WALLET CLOSE IDENTIFIED BY "g00g1e";

6. Opening the wallet: login as sysdba
Syntax: 
ALTER SYSTEM SET WALLET OPEN IDENTIFIED BY <password>;

Eg: 
ALTER SYSTEM SET WALLET OPEN IDENTIFIED BY "g00g1e";

7. How to check whether the wallet is open / closed : login as sysdba

SQL> COL WRL_PARAMETER FOR A65
SQL> SELECT * FROM V$ENCRYPTION_WALLET;

WRL_TYPE             WRL_PARAMETER                                                     STATUS
-------------------- ----------------------------------------------------------------- ------------------
file                 /oradb/oracle/11.2.0.3/admin/TEST_drebsdb01/encryption_wallet/    OPEN


8. SQL to check what are the table colums that are encrypted : login as sysdba

SQL> COL OWNER FOR A5
SQL> COL COLUMN_NAME FOR A20
SQL> COL ENCRYPTION_ALG FOR A16
SQL> SELECT * FROM DBA_ENCRYPTED_COLUMNS;

OWNER TABLE_NAME                     COLUMN_NAME          ENCRYPTION_ALG   SAL
----- ------------------------------ -------------------- ---------------- ---
HR    PER_ALL_PEOPLE_F               NATIONAL_IDENTIFIER  AES 192 bits key NO
HR    PQP_EXT_CROSS_PERSON_RECORDS   NATIONAL_IDENTIFIER  AES 192 bits key NO
BEN   BEN_PL_F                       NAME                 AES 192 bits key NO
BEN   BEN_OPT_F                      NAME                 AES 192 bits key NO
BEN   BEN_REPORTING                  NATIONAL_IDENTIFIER  AES 192 bits key YES
HR    GHR_MASS_ACTIONS_PREVIEW       NATIONAL_IDENTIFIER  AES 192 bits key YES
HR    GHR_RIF_REGISTERS              NATIONAL_IDENTIFIER  AES 192 bits key YES
HRI   EDW_HR_PERM_ASSIGN_LSTG        NATIONAL_IDENTIFIER  AES 192 bits key YES
HRI   EDW_HR_PERM_ASSIGN_LTC         NATIONAL_IDENTIFIER  AES 192 bits key YES
HR    HR_H2PI_EMPLOYEES              NATIONAL_IDENTIFIER  AES 192 bits key YES
BEN   BEN_PRTT_ENRT_RSLT_F           BNFT_AMT             AES 192 bits key YES

9. When the Wallet is close we cannot access the data from backend:
SQL> SELECT NATIONAL_IDENTIFIER FROM HR.PER_ALL_PEOPLE_F WHERE NATIONAL_IDENTIFIER IS NOT NULL;
SELECT NATIONAL_IDENTIFIER FROM HR.PER_ALL_PEOPLE_F WHERE NATIONAL_IDENTIFIER IS NOT NULL
                                   *
ERROR at line 1:
ORA-28365: wallet is not open

Note: We need to open the wallet in order to view the values of the columns table that are encrypted.