Category Archives: ERP - Page 5

ORA-00604, ORA-01882 While Connecting With SQL Developer

Problem:

While trying to connect to an Oracle 9.2.0.3 database on EBS 11.5.9 (running on Red Hat Enterprise Linux AS release 4) using SQL Developer 3.0.04, the following message appears:

An error was encountered performing the requested operations:
ORA-00604: error occurred at recursive SQL level 1
ORA-01882: timezone region not found
OO604. 00000 - "error occurred at recursive SQL level %s"
*Cause: An error occurred while processing a recursive SQL statement 
(a statement applying to internal dictionary tables).
*Action: If the situation described in the next error on the stack 
can be corrected, do so; otherwise contact Oracle Support
Vendor code 604

Solution:

Change the timezone variable in sqldeveloper.conf to a valid one for the database.

Read more »

Oracle Installer Not Detecting Packages

Problem:

While installing 11gR2 64-bit version on Oracle Linux 5.7 64-bit, the installer states that certain RPMs (libaio-devel-0.3.106 and unixODBC-devel-2.2.11)  are missing. After installing the missing RPMs using the ‘rpm -Uvh’ command, the installer still does not detect the newly applied RPMs.

Solution:

Exit the 11gR2 installer, apply the RPMs and then rerun the installer.

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 »

error while loading shared libraries: libc.so.6 while patching

Problem:

After unsetting LD_ASSUME_KERNEL, began applying patch 5903765. The following errors appeared:

Removing $FND_TOP/$APPLBIN from PATH …
uname: error while loading shared libraries: libc.so.6: cannot open shared object file: No such file or directory
grep: error while loading shared libraries: libc.so.6: cannot open shared object file: No such file or directory
tr: error while loading shared libraries: libc.so.6: cannot open shared object file: No such file or directory

Solution:

Apply patch 6365595: 11IEBS CERT ON OEL5|RH5|SLES10:UNSET LD_ASSUME_KERNEL IN ADGETLNXVER.SH.

This patch fixes all references to the LD_ASSUME_KERNEL environment variable.

Read more »