Concurrent Reports Failing With Errors REP-0004,REP-0082 and REP-0104

ISSUE:

Below error found in concurrent log

REP-0004: Warning: Unable to open user preference file.
REP-0082: Error executing SCA utility.
REP-0104: Unable to delete file '<Name.rdf>'.
scaba 5
REP-0069: Internal error
REP-57054: In-process job terminated:Terminated with error:
REP-159:

SOLUTION:

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

To resolve the warning, copy the prefs.ora file from your Reports Builder $ORACLE_HOME/tools/admin/ directory into the Applications $HOME directory.

cp /d01/oracle/apps/tech_st/10.1.2/tools/admin/prefs.ora to the directory /home/applmgr/

2. REP-0082: Error executing SCA utility.
    REP-0104: Unable to delete file '<Name.rdf>'.
    scaba 5
    REP-0069: Internal error
    REP-57054: In-process job terminated:Terminated with error:
    REP-159:

To implement the solution, please execute the following steps:

1. Stop the concurrent managers using adcmctl.sh.

2. Truncate the reports.log file in log directory (under $APPLCSF/$APPLLOG).

3. Restart the concurrent managers.

4. Submit Concurrent request of type RDF from Oracle Applications and ensure it completes normal.

Error copying the Forms Registry file to /d01/oracle/apps/apps_st/comn/java/classes/oracle/forms/registry/Registry.dat

ISSUE:

  Copying Registry.dat from the Forms Java directory to /d01/oracle/apps/apps_st/comn/java/classes ...

AutoPatch error:
Error copying the Forms Registry file to /d01/oracle/apps/apps_st/comn/java/classes/oracle/forms/registry/Registry.dat.


adogjf() Unable to copy Registry.Dat.

AutoPatch error:
Failed to generate the product JAR files

SOLUTION:

Please check ORACLE_HOME , did u have wrong ORACLE_HOME sourced before applying patch.

-bash-3.2$ echo $ORACLE_HOME
/d01/oracle/apps/tech_st/10.1.3
-bash-3.2$ cd
-bash-3.2$ . APPSPATCH_patchapp.env
-bash-3.2$ echo $ORACLE_HOME

/d01/oracle/apps/tech_st/10.1.2

Routine AFPCSQ encountered an ORACLE error. ORA-01017: invalid username/password; logon denied

ISSUE:

_ 1 _
Routine AFPCMT encountered an ORACLE error. ORA-01012: not logged on.

Review your error messages for the cause of the error. (=<POINTER>)
_ 2 _
Routine AFPCSQ encountered an ORACLE error. ORA-01017: invalid
username/password; logon denied
.
Review your error messages for the cause of the error. (=<POINTER>)

The issue is caused by enabling 11g password case sensitivity. 


SOLUTION:

To implement the solution, please execute the following steps:

1. Disable the case sensitive 11g feature 

 show parameter SEC_CASE_SENSITIVE_LOGON

NAME                           TYPE        VALUE
------------------------------------------------------------------

sec_case_sensitive_logon       boolean   TRUE

   alter system set sec_case_sensitive_logon=false;
   
2. Stop applications and database

3. Start Database and Applications.

(OR)

Need to apply Patch 12964564:R12.FND.B and follow the readme instruction.

ensure that your sqlnet_ifile.ora has the below line

SQLNET.ALLOWED_LOGON_VERSION_SERVER = 10 (if SEC_CASE_SENSITIVE_LOGON is set to TRUE)

Restart Database and listener.

Try to change password and Start applications. Now the Concurrent managers will run as expected.

Refer: 1581584.1

VKTM PROCESSES CONSUME LARGE AMOUNT OF CPU, UNSTABLIZE MACHINE

Issue:

VKTM PROCESSES CONSUME LARGE AMOUNT OF CPU, UNSTABLIZE MACHINE  

Solution:

There are bugs for the VKTM process malfunction. These Bugs are fixed in 12.2

So please download & apply patch 18499306, if its available on top of your database(11.2.0.3.0 - 12.1.0.1) version for your platform

Reference note: 1347586.1

Warning: VKTM detected a time drift in STANDBY Database on Linux 64 bit

Issue:

Warning: VKTM detected a time drift.
Time drifts can result in an unexpected behavior such as time-outs. Please check trace file for more details.

*** 2016-07-21 08:15:26.137
*** CLIENT ID:() 2016-07-21 08:15:26.137
*** SERVICE NAME:() 2016-07-21 08:15:26.137
*** MODULE NAME:() 2016-07-21 08:15:26.137
*** ACTION NAME:() 2016-07-21 08:15:26.137

ksesethighpri: (ksb.c:4201) Failed to elevate VKTM's priority from 0 to 1
Error Info: Category(-2), Opname(skgdism_create), Loc(sp.c:1553), ErrMsg(Error 0) Dism(16)
*** SESSION ID:(801.1) 2016-07-21 08:15:26.140
*** SERVICE NAME:() 2016-07-21 08:15:26.140
ghres_enabled
VKTM running at (100ms) precision
kstmrmtickcntkeeper: param _dbrm_quantum will not be effective

or 

*** 2016-07-20 22:40:57.760
VKTM running at (1)millisec precision with DBRM quantum (100)ms
[Start] HighResTick = 1469034657760082
kstmrmtickcnt = 0 : ksudbrmseccnt[0] = 1469034657
kstmchkdrift (kstmhighrestimecntkeeper:highres): Time jumped forward by (3530316)usec at (1469035949221501) whereas (1000000) is allowed

Solution:

The time drifts usually occurring less than 1sec and 5 sec for forward and backward respectively are permissible. Most of the times, during high loads, there would be issues with underlying OS due to virtual memory, network time protocol improper configuration etc.

The resource manager to take improper decisions and can lead to a hang in worst case.

To fix the issue, please download and apply patch 11837095 as available for your release/platform.

After applying the patch, enable event 10975 at level 2:

alter system set event="10795 trace name context forever, level 2" scope=spfile;

Then bounce the instance (shutdonw then startup) for the event to be applied.

The permanent fix is planned to be included in the 11.2.0.4 and 12.1 releases.