Requests Remain In ‘Posting’ Distribution Status

Problem:

When a new request is submitted in PeopleSoft (Main Menu > PeopleTools > Process Scheduler > System Process Requests), the request’s ‘Run Status’ completes with status ‘Success’, but the ‘Distribution Status’ remains at ‘Posting’.

Solution:

Ensure that the Process Scheduler Report Node and Distribution Details for the Server are correctly set up.

Read more »

java.lang.ClassNotFoundException: oracle.apps.per.DataInstall

Problem:

After applying patch 9239090 (ORACLE E-BUSINESS SUITE 12.1.3 RELEASE UPDATE PACK), DataInstall must be run. However, after sourcing the environment and running the DataInstall command, the following error appears:

java.lang.ClassNotFoundException: oracle.apps.per.DataInstall

Solution:

Source the application tier environment (not the database tier environment) and then run DataInstall.

Read more »

FAILED: file OKLTXRBKUG.sql on worker while running patch 9239090

Problem:

While running patch 9239090, the following error appears:

ATTENTION: All workers either have failed or are waiting:

           FAILED: file OKLTXRBKUG.sql on worker  1.
           FAILED: file OKLTXRBKUG.sql on worker  2.
           FAILED: file OKLTXRBKUG.sql on worker  3.
           FAILED: file OKLTXRBKUG.sql on worker  4.
           FAILED: file OKLTXRBKUG.sql on worker  5.
           FAILED: file OKLTXRBKUG.sql on worker  6.
           FAILED: file OKLTXRBKUG.sql on worker  7.
           FAILED: file OKLTXRBKUG.sql on worker  8.
           FAILED: file OKLTXRBKUG.sql on worker  9.
           FAILED: file OKLTXRBKUG.sql on worker 10.
           FAILED: file OKLTXRBKUG.sql on worker 11.
           FAILED: file OKLTXRBKUG.sql on worker 12.

ATTENTION: Please fix the above failed worker(s) so the manager can continue.

Solution:

The OKL_TRANSACTION_PVT package was invalid. When this was compiled, the OKL_SECURITIZATION_PVT was invalid. In this way, a number of OKL packages were invalid and the error was cascading. In order to resolve the issue, I logged on to SQL*Plus as sysdba and ran the following commands:

alter package APPS.OKL_TXL_ASSETS_PVT compile;
alter package APPS.OKL_TXL_ASSETS_PVT compile body;
alter package APPS.OKL_TXL_ASSETS_PUB compile;
alter package APPS.OKL_TXL_ASSETS_PUB compile body;
alter package APPS.OKL_SPLIT_ASSET_PVT compile;
alter package APPS.OKL_SPLIT_ASSET_PVT compile body;
alter package APPS.OKL_SECURITIZATION_PVT compile;
alter package APPS.OKL_SECURITIZATION_PVT compile body;
alter package APPS.OKL_TRANSACTION_PVT compile;
alter package APPS.OKL_TRANSACTION_PVT compile body;

OKL_TRANSACTION_PVT now compiles without issue.

To resolve this in future, use adadmin to compile APPS schema. Afterwards, issue the following SQL statement in SQL*Plus to get the number of invalid objects:

select count(*) from dba_objects where status = ‘INVALID’;

Continue compiling APPS schema with adadmin and checking the number of invalid objects until that number no longer decreases.

FAILED: file OKLTXRBKUG.sql on worker 1

Problem:

While running patch 9239090, the following error appears:

ATTENTION: All workers either have failed or are waiting:

           FAILED: file OKLTXRBKUG.sql on worker  1.
           FAILED: file OKLTXRBKUG.sql on worker  2.
           FAILED: file OKLTXRBKUG.sql on worker  3.
           FAILED: file OKLTXRBKUG.sql on worker  4.
           FAILED: file OKLTXRBKUG.sql on worker  5.
           FAILED: file OKLTXRBKUG.sql on worker  6.
           FAILED: file OKLTXRBKUG.sql on worker  7.
           FAILED: file OKLTXRBKUG.sql on worker  8.
           FAILED: file OKLTXRBKUG.sql on worker  9.
           FAILED: file OKLTXRBKUG.sql on worker 10.
           FAILED: file OKLTXRBKUG.sql on worker 11.
           FAILED: file OKLTXRBKUG.sql on worker 12.

ATTENTION: Please fix the above failed worker(s) so the manager can continue.

Solution:

The OKL_TRANSACTION_PVT package was invalid. When this was compiled, the OKL_SECURITIZATION_PVT was invalid. In this way, a number of OKL packages were invalid and the error was cascading. In order to resolve the issue, I logged on to SQL*Plus and ran the following commands:

alter package APPS.OKL_TXL_ASSETS_PVT compile;
alter package APPS.OKL_TXL_ASSETS_PVT compile body;
alter package APPS.OKL_TXL_ASSETS_PUB compile;
alter package APPS.OKL_TXL_ASSETS_PUB compile body;
alter package APPS.OKL_SPLIT_ASSET_PVT compile;
alter package APPS.OKL_SPLIT_ASSET_PVT compile body;
alter package APPS.OKL_SECURITIZATION_PVT compile;
alter package APPS.OKL_SECURITIZATION_PVT compile body;
alter package APPS.OKL_TRANSACTION_PVT compile;
alter package APPS.OKL_TRANSACTION_PVT compile body;

OKL_TRANSACTION_PVT now compiles without issue.

To resolve this in future, use adadmin to compile APPS schema. Afterwards, issue the following SQL statement in SQL*Plus to get the number of invalid objects:

select count(*) from dba_objects where status = ‘INVALID’;

Continue compiling APPS schema with adadmin and checking the number of invalid objects until that number no longer decreases.

mth_pre_upgrade.sql Failed While Rerunning Patch 9239090

Problem:

When rerunning patch 9239090, the following error appears:

ATTENTION: All workers either have failed or are waiting:

           FAILED: file mth_pre_upgrade.sql on worker  1.

ATTENTION: Please fix the above failed worker(s) so the manager can continue.

Checked worker log file:
C:oracleTEST1appsapps_stappladminTEST1logadwork001.log

The following errors appeared:

Time when worker started job: Mon Jan 30 2012 09:42:06

Start time for file is: Mon Jan 30 2012 09:42:06

sqlplus -s MTH/***** @C:oracleTEST1appsapps_stapplmth12.0.0patch115sqlmth_pre_upgrade.sql 

Error:
Program exited with status 1

Cause: The program terminated, returning status code 1.

Action: Check your installation manual for the meaning of this code on this operating system.DECLARE
*
ERROR at line 1:
ORA-00955: name is already used by an existing object
ORA-06512: at line 59

Time when worker failed: Mon Jan 30 2012 09:42:06

Time when worker started job: Mon Jan 30 2012 09:42:06

Start time for file is: Mon Jan 30 2012 09:42:06

sqlplus -s MTH/***** @C:oracleTEST1appsapps_stapplmth12.0.0patch115sqlmth_pre_upgrade.sql 

Error:
Program exited with status 1

Cause: The program terminated, returning status code 1.

Action: Check your installation manual for the meaning of this code on this operating system.DECLARE
*
ERROR at line 1:
ORA-00955: name is already used by an existing object
ORA-06512: at line 59

Time when worker failed: Mon Jan 30 2012 09:42:06

Solution:

1. Edit C:oracleTEST1appsapps_stapplmth12.0.0patch115sqlmth_pre_upgrade.sql  and uncomment SQL code for Exception. Then restart worker (did not try this solution).

2. Use adctrl (option 8) to skip and restart this step (tried this solution).

Reference:

https://forums.oracle.com/forums/thread.jspa?messageID=9224027

[amazon asin=0070077290&template=iframe image&chan=default]     [amazon asin=1453742735&template=iframe image&chan=default]     [amazon asin=0615238440&template=iframe image&chan=default]

RW-50004: Error code received when running external process, Running Database Install Driver

Problem:

When running Rapid Install, the following error appears:

RW-50004: Error code received when running external process. Check log file for details.
Running Database Install Driver for TEST1 instance

In the ‘Rapid Install base window – do not close’ window, the following appears:

Configuration file written to: C:oracleTEST1instappsTEST1_ittl-hrmstestconf_TEST1.txt
Configuration file written to: C:oracleTEST1dbtech_st11.1.0appsutilconf_TEST1.txt
Database logfile - C:oracleTEST1dbtech_st11.1.0appsutillogTEST1_ittl-hrmstest1260950.log
uploadConfig() : Exception : TDU

Rapid Wizard completes with the following error:

RW-10001: Rapidinstall wizard has detected that your configuration has errors. You must resolve these issues before continuing.

The log file C:oracleTEST1dbtech_st11.1.0appsutillogTEST1_ittl-hrmstest1260950.log showed the following:

    RW-50010: Error: - script has returned an error:   1
RW-50004: Error code received when running external process

Solution:

Change the NUMBER_OF_PROCESSORS environment variable from 16 to 12 and restart installation.

Read more »

Error: Could not resolve environment variable(s) in %PS_SERVDIR%logsPeopleTools.trc.

Problem:

When launching Application Designer on the PeopleSoft server, the following error appears:

Error: Could not resolve environment variable(s) in %PS_SERVDIR%logsPeopleTools.trc.

Note that PeopleTools 8.50 is running on this machine.

Solution:

Set the PS_SERVDIR environment variable to point to the process scheduler location.

Read more »

Viewing Default Oracle Database Properties

Problem:

How do I view the default settings, parameters or properties of the Oracle database?

Solution:

As sys or system user:

select * from database_properties;

 

ORA-20100: File o0150175.tmp creation for FND_FILE failed

Problem:

When running the Diagnostics: Apps Check from the Purchasing responsibility in Oracle Applications E-Business Suite 11i, the concurrent request completes in error and following error appears at the bottom of the output log:

declare
*
ERROR at line 1:
ORA-20100: File o0150175.tmp creation for FND_FILE failed.
You will find more information on the cause of the error in request log.
ORA-06512: at “APPS.FND_FILE”, line 407
ORA-06512: at “APPS.FND_FILE”, line 581
ORA-06512: at line 120

Solution:

Ran out of disk space on the db machine. The temp directory used by EBS is in the /var directory, which is only 1GB in size. The /var directory is being filled by yum updates.

As root user, execute the command ‘yum clean all’. Stop the yum updates by issuing the command ‘/etc/init.d/yum-updatesd stop’.

AC-30202: Unrecognized action specified, Context Value Management Failed

Problem:

After sourcing APPSORA.env on and 11.5.10.2 environment and running AutoConfig, the following error appeared:

$ ./adautocfg.sh appspass=password

The log file for this session is located at: /u01/test3/test3appl/admin/TEST3_uttoratestapp03/log/12070801/adconfig.log

AutoConfig is configuring the Applications environment...

AutoConfig will consider the custom templates if present.
        Using APPL_TOP location     : /u01/test3/test3appl
        Classpath                   : /u01/test3/test3comn/util/java/1.4/j2sdk1.4.2_04/jre/lib/rt.jar:/u01/test3/test3comn/util/java/1.4/j2sdk1.4.2_04/lib/dt.jar:/u01/test3/test3comn/util/java/1.4/j2sdk1.4.2_04/lib/tools.jar:/u01/test3/test3comn/java/appsborg2.zip:/u01/test3/test3comn/java

promptmsg=hide - AC-30202: Unrecognized action specified. Exiting.

ERROR: Context Value Management Failed.
Terminate.

The logfile for this session is located at:
    /u01/test3/test3appl/admin/TEST3_uttoratestapp03/log/12070801/adconfig.log
$

Solution:

After unsetting LD_ASSUME_KERNEL and applying patch 6365595, applied patch 5903765 (Applications Technology 11i.ATG_PF.H.delta.6). After patch completed, ran AutoConfig without problems.