Skip to Main Content
Forums

Enterprise Manager

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

Position data Update changes the Standard hours of incumbents

User_S8BJTSep 10 2018

Hello,

We are in 9.2.25 with tools version of 8.56.07

Right now when we are adding a new row in Postion Data and change the Jobcode with reason as UPD, the STD_HOURS of the incumbents attached is getting updated to whatever std_hours is there in JOb code.The client requirement is that Job data should get updated with Salary Plan and Grade however, should not update their std_hours.To meet the first part we are checking the flag, Include Salary Plan/Grade and Update incumbents.

However it seems for the std_hours we might need to do some customizations. I have found one function copy_job in FUNCLIB_HR.UPdate_incumbents.field formula where this code needs to be modified. BUt that alone is not helping us. Has anyone else had this requirement, can you please let me know - Is there any other place where we might need to make modifications?

Any help here is appreciated.

Thanks, Pooja.

Comments

sb92075
Does Java application utilize connection pooling?
I suspect it does not.
Is process high water count at or near PROCESSES limit?
758670
Yes - the app uses connection pooling. It is very multithreaded, so there may be 50+ threads inserting to the database at once.

Here are some statistics, let me know if there is more that would be useful.
SQL> select name, value from v$sysstat where name like '%logon%';

NAME                                                                  VALUE
---------------------------------------------------------------- ----------
logons cumulative                                                       919
logons current                                                           31

SQL> select sessions_current, sessions_highwater from v$license;

SESSIONS_CURRENT SESSIONS_HIGHWATER
----------------   ------------------
               8                 80

SQL> show parameter sessions

NAME                                 TYPE        VALUE
------------------------------------ ----------- ------------------------------
java_max_sessionspace_size           integer     0
java_soft_sessionspace_limit         integer     0
license_max_sessions                 integer     0
license_sessions_warning             integer     0
sessions                             integer     328
shared_server_sessions               integer
SQL> show parameter processes;

NAME                                 TYPE        VALUE
------------------------------------ ----------- ------------------------------
aq_tm_processes                      integer     0
db_writer_processes                  integer     1
gcs_server_processes                 integer     0
global_txn_processes                 integer     1
job_queue_processes                  integer     1000
log_archive_max_processes            integer     4
processes                            integer     200
Thank you for the help.
1 person found this helpful
932095
In our application also we are facing the same issue.

We are using the DBCP datasource for the connection pool. It is not happening all the times. randomly seeing this error.

===========
Caused by: oracle.net.ns.NetException: Socket read timed out
at oracle.net.ns.Packet.receive(Packet.java:321)
at oracle.net.ns.NSProtocol.connect(NSProtocol.java:287)
at oracle.jdbc.driver.T4CConnection.connect(T4CConnection.java:1054)
at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:308)
========


Can i know what is the solution for this issue.

Edited by: 929092 on 20-Apr-2012 08:54
I would assume it may be a OS IP layer or firewall or some "smart" network device that detects connections inactive more than specific time and force closes them.

So either to configure your connection pool to close idle connections before that network layer does it, or configure "keep alive" in it.
1 person found this helpful
1 - 4
Locked Post
New comments cannot be posted to this locked post.

Post Details

Locked on Oct 8 2018
Added on Sep 10 2018
0 comments
76 views