24
Jan

After Upgrading From 12.2.0 to 12.2.x Apache Does Not Start And Errors With Could not open configuration file

Error:

/u02/oracle/ERPPROD/fs1/FMW_Home/webtier/ohs/bin/apachectl startssl: execing httpd
 
Killedworker: Syntax error on line 1039 of /u02/oracle/ERPPROD/fs1/FMW_Home/webtier/instances/EBS_web_ERPPROD_OHS1/config/OHS/EBS_web_ERPPROD/httpd.conf: Syntax error on line 115 of /u02/oracle/EBS_web_ERPPROD_OHS1/config/OHS/EBS_web_ERPPROD/ssl.conf: Could not open configuration file
You have new mail in /var/spool/mail/applprod
 

[applprod@erpapp01 ~]$ ls -ltr
/u02/oracle/ERPPROD/fs1/FMW_Home/webtier/instances/EBS_web_ERPPROD_OHS1/OHS/EBS_web_ERPPROD/oracle_apache_ssl.conf: No such file or directory

Cause:

In the runfilesystem xml file the value of variable s_ohs_installed is set to False.
This will stop the configuration file from getting generated.

Hence the file oracle_apache_ssl.conf was not created and the services are not starting.


[applprod@erpapp01 ~]$ grep -i s_ohs_installed $CONTEXT_FILE
false

Read more...

5
Dec

On Oracle Applications 12.2 version, Online Enablement patch fails on APPS.AD_ZD_PREP package

Symptoms:

On Oracle Applications 12.2 version, online enablement patch 13543062 fails with:


begin
*
ERROR at line 1:
ORA-04063: package body "APPS.AD_ZD_PREP" has errors
ORA-06508: PL/SQL: could not find program unit being called: "APPS.AD_ZD_PREP"
ORA-06512: at line 4

 
Try to compile the package:

SQL> alter package apps.AD_ZD_PREP compile body;

Warning: Package Body altered with compilation errors.
 
SQL> show error
Errors for PACKAGE BODY APPS.AD_ZD_PREP:

LINE/COL ERROR
-------- -----------------------------------------------------------------
308/6 PL/SQL: Statement ignored
308/6 PLS-00201: identifier 'SYS.DBMS_OBJECTS_APPS_UTILS' must be
declared

670/4 PL/SQL: Statement ignored
670/4 PLS-00201: identifier 'SYS.DBMS_OBJECTS_APPS_UTILS' must be
declared

753/6 PL/SQL: Statement ignored
753/6 PLS-00201: identifier 'SYS.DBMS_OBJECTS_APPS_UTILS' must be
declared

LINE/COL ERROR
-------- -----------------------------------------------------------------

1152/4 PL/SQL: Statement ignored
1152/17 PLS-00201: identifier 'SYS.DBMS_OBJECTS_APPS_UTILS' must be
declared

Read more...

8
Nov

Error occurred while Executing txkADOPValidation script when running fs_clone

While running fs_clone, it fails with the following error:


[applprod@erpapp01 ~]$ adop phase=fs_clone

Enter the APPS password:
Enter the SYSTEM password:
Enter the WLSADMIN password:

Validating credentials.

Initializing.
Run Edition context : /u01/oracle/ERPPROD/fs1/inst/apps/ERPPROD_erpapp01/appl/admin/ERPPROD_erpapp01.xml
Patch edition context: /u01/oracle/ERPPROD/fs2/inst/apps/ERPPROD_erpapp01/appl/admin/ERPPROD_erpapp01.xml
Patch file system free space: 355.97 GB

Validating system setup.
Node registry is valid.
[WARNING] ETCC: The following required database fixes have not been applied to node dx
12608451
21286665
Refer to My Oracle Support Knowledge Document 1594274.1 for instructions.

Checking for existing adop sessions.
No pending session exists.
Starting new adop session.

===========================================================================
ADOP (C.Delta.8)
Session ID: 3
Node: erpapp01
Phase: fs_clone
Log: /u02/oracle/ERPPROD/fs_ne/EBSapps/log/adop/3/20170807_123036/adop.log
===========================================================================
Read more...

2
Oct

REP-0004: Warning: Unable to open user preference file

Symptoms:

Concurrent request logfiles have the below error:

REP-0004: Warning: Unable to open user preference file

 

Cause:

The prefs.ora is either missing or non-accessible.

 

Solution:

1. No prefs.ora file in HOME directory:

Oracle Reports will look into the user's HOME directory for the prefs.ora preferences file.  If a prefs.ora file does not exist in your HOME directory, you can copy the prefs.ora file that came with the Oracle Tools.

Read more...

5
Sep

Enforcing password complexity for database users

It is recommended to enforce checks and response actions for failed logins, password complexity, password expiration and password reuse.
 
Password complexity can be implemented through profiles.
 
The script for password management implementation utlpwdmg.sql can be used to create a new function to verify password complexity rules.
 
Verify Function is a quick and easy way to enforce quality of database passwords—for example, they should contain a certain number of characters, should not be identical to the username, and so on.
 
By executing this script utlpwdmg.sql, it will attach the function to the profile DEFAULT, which is the default profile for all users.
 

The following password complexity is set with the 'utlpwdmg.sql' script.
 

  • Password length less than 8
  • Password same as or similar to user
  • Password same as username reversed
  • Password same as or similar to server name
  • Password too simple
  • Password must contain at least one digit, one character
  • Password must contain at least one digit, and one character
  • Password should differ from the old password by at least 3 characters
  • Read more...

    Back to Top