Overweight job queue process

Hi,
I've got a production batch processing setup where my j000 job grows to over 2Gb of memory. It doesn't seem to share with the other job queue processes. I have a setting of 10.
oracle 31082 0.3 6.4 2483684 2112444 ? Ss May16 57:32 ora_j000_conp
oracle 11029 0.0 1.6 2480352 543160 ? Ss May23 0:26 ora_j002_conp
oracle 11136 0.0 0.8 2479332 290672 ? Ss May23 0:09 ora_j003_conp
oracle 28657 0.0 0.3 2479316 102932 ? Ss May24 0:01 ora_j004_conp
At this point I have to reset the jobs with alter system set job_queue_processes=0
- wait a minute or two - then alter system set job_queue_processes=10
Anyone have any suggestions of limiting or sharing resources. It's Oracle 10.1.0.5 on Linux? ta

I've got a production batch processing setup where my
j000 job grows to over 2Gb of memory. It doesn't seem
to share with the other job queue processes. I have a
setting of 10.Its depend on how you submitting job and how many job you submitting at a time.
Check dba_jobs_running and find out what job j000 is running , run same job manually and check processes memory usage.
Virag

Similar Messages

Error 472 in job queue process + ORA-472: PMON process terminated with err

Hi,
I've an Oracle Database 11g Release 11.1.0.6.0 - 64bit Production With the Real Application Clusters option.
Yesterday instance on node1 crashed.
This is the extract of alert log:
Errors in file /u01/app/oracle/diag/rdbms/evodb/EVODB1/trace/EVODB1_pmon_9297.trc (incident=195198):
ORA-00600: internal error code, arguments: [17183], [0x14E251C38], [], [], [], [], [], []
Incident details in: /u01/app/oracle/diag/rdbms/evodb/EVODB1/incident/incdir_195198/EVODB1_pmon_9297_i195198.trc
Sat Jan 22 16:24:47 2011
Trace dumping is performing id=[cdmp_20110122162447]
Sat Jan 22 16:24:50 2011
Sweep Incident[195198]: completed
Sat Jan 22 16:25:00 2011
Errors in file /u01/app/oracle/diag/rdbms/evodb/EVODB1/trace/EVODB1_pmon_9297.trc (incident=195199):
ORA-00600: internal error code, arguments: [17183], [0x14E251C38], [], [], [], [], [], []
Incident details in: /u01/app/oracle/diag/rdbms/evodb/EVODB1/incident/incdir_195199/EVODB1_pmon_9297_i195199.trc
Sat Jan 22 16:25:10 2011
Trace dumping is performing id=[cdmp_20110122162510]
Sat Jan 22 16:25:12 2011
Errors in file /u01/app/oracle/diag/rdbms/evodb/EVODB1/trace/EVODB1_pmon_9297.trc (incident=195200):
ORA-00600: internal error code, arguments: [17183], [0x14E251C38], [], [], [], [], [], []
Incident details in: /u01/app/oracle/diag/rdbms/evodb/EVODB1/incident/incdir_195200/EVODB1_pmon_9297_i195200.trc
Sat Jan 22 16:25:23 2011
DBRM (ospid: 9310): terminating the instance due to error 472
Sat Jan 22 16:25:23 2011
System state dump is made for local instance
System State dumped to trace file /u01/app/oracle/diag/rdbms/evodb/EVODB1/trace/EVODB1_diag_16320.trc
Sat Jan 22 16:25:23 2011
ORA-1092 : opiodr aborting process unknown ospid (3724_47445977853072)
Sat Jan 22 16:25:23 2011
SUCCESS: diskgroup ARCHIVELOG was dismounted
Sat Jan 22 16:14:22 2011
DDE: Problem Key 'ORA 600 [17183]' was completely flood controlled (0x6)
Further messages for this problem key will be suppressed for up to 10 minutes
Sat Jan 22 16:15:56 2011
Thread 1 advanced to log sequence 171322
Current log# 18 seq# 171322 mem# 0: +ONLINELOG/evodb/onlinelog/group_18.264.729348055
Sat Jan 22 16:15:56 2011
SUCCESS: diskgroup ARCHIVELOG was mounted
Sat Jan 22 16:16:15 2011
SUCCESS: diskgroup ARCHIVELOG was dismounted
Sat Jan 22 16:20:52 2011
Thread 1 advanced to log sequence 171323
Current log# 12 seq# 171323 mem# 0: +ONLINELOG/evodb/onlinelog/group_12.267.729333861
Sat Jan 22 16:20:53 2011
SUCCESS: diskgroup ARCHIVELOG was mounted
Sat Jan 22 16:21:14 2011
SUCCESS: diskgroup ARCHIVELOG was dismounted
Sat Jan 22 16:24:23 2011
DDE: Problem Key 'ORA 600 [17183]' was completely flood controlled (0x2)
Further messages for this problem key will be suppressed for up to 10 minutes
Sat Jan 22 16:24:38 2011
Errors in file /u01/app/oracle/diag/rdbms/evodb/EVODB1/trace/EVODB1_pmon_9297.trc (incident=195198):
ORA-00600: internal error code, arguments: [17183], [0x14E251C38], [], [], [], [], [], []
Incident details in: /u01/app/oracle/diag/rdbms/evodb/EVODB1/incident/incdir_195198/EVODB1_pmon_9297_i195198.trc
Sat Jan 22 16:24:47 2011
Trace dumping is performing id=[cdmp_20110122162447]
Sat Jan 22 16:24:50 2011
Sweep Incident[195198]: completed
Sat Jan 22 16:25:00 2011
Errors in file /u01/app/oracle/diag/rdbms/evodb/EVODB1/trace/EVODB1_pmon_9297.trc (incident=195199):
ORA-00600: internal error code, arguments: [17183], [0x14E251C38], [], [], [], [], [], []
Incident details in: /u01/app/oracle/diag/rdbms/evodb/EVODB1/incident/incdir_195199/EVODB1_pmon_9297_i195199.trc
Sat Jan 22 16:25:10 2011
Trace dumping is performing id=[cdmp_20110122162510]
Sat Jan 22 16:25:12 2011
Errors in file /u01/app/oracle/diag/rdbms/evodb/EVODB1/trace/EVODB1_pmon_9297.trc (incident=195200):
ORA-00600: internal error code, arguments: [17183], [0x14E251C38], [], [], [], [], [], []
Incident details in: /u01/app/oracle/diag/rdbms/evodb/EVODB1/incident/incdir_195200/EVODB1_pmon_9297_i195200.trc
Sat Jan 22 16:25:23 2011
DBRM (ospid: 9310): terminating the instance due to error 472
Sat Jan 22 16:25:23 2011
System state dump is made for local instance
System State dumped to trace file /u01/app/oracle/diag/rdbms/evodb/EVODB1/trace/EVODB1_diag_16320.trc
Sat Jan 22 16:25:23 2011
ORA-1092 : opiodr aborting process unknown ospid (3724_47445977853072)
Sat Jan 22 16:25:23 2011
ORA-1092 : opiodr aborting process unknown ospid (3650_47673206152336)
Sat Jan 22 16:25:23 2011
ORA-1092 : opiodr aborting process unknown ospid (19709_47962498952336)
Sat Jan 22 16:25:23 2011
ORA-1092 : opiodr aborting process unknown ospid (3715_47239602621584)
Sat Jan 22 16:25:23 2011
ORA-1092 : opiodr aborting process unknown ospid (3718_47120460606608)
Sat Jan 22 16:25:23 2011
ORA-1092 : opiodr aborting process unknown ospid (3646_47899813694608)
Sat Jan 22 16:25:23 2011
ORA-1092 : opiodr aborting process unknown ospid (3671_47700480982160)
Sat Jan 22 16:25:23 2011
ORA-1092 : opiodr aborting process unknown ospid (3637_47223057443984)
Sat Jan 22 16:25:23 2011
ORA-1092 : opiodr aborting process unknown ospid (3695_47109627223184)
Sat Jan 22 16:25:23 2011
ORA-1092 : opiodr aborting process unknown ospid (3679_47262512999568)
Sat Jan 22 16:25:23 2011
ORA-1092 : opiodr aborting process unknown ospid (3733_46976527121552)
Sat Jan 22 16:25:23 2011
ORA-1092 : opiodr aborting process unknown ospid (3667_47474016554128)
Sat Jan 22 16:25:23 2011
ORA-1092 : opiodr aborting process unknown ospid (3669_47585103858832)
Sat Jan 22 16:25:23 2011
ORA-1092 : opiodr aborting process unknown ospid (3658_47992462539920)
Sat Jan 22 16:25:23 2011
ORA-1092 : opiodr aborting process unknown ospid (3654_47736794324112)
Sat Jan 22 16:25:23 2011
ORA-1092 : opiodr aborting process unknown ospid (3686_47295241862288)
Sat Jan 22 16:25:23 2011
ORA-1092 : opiodr aborting process unknown ospid (3706_47055349939344)
Sat Jan 22 16:25:23 2011
ORA-1092 : opiodr aborting process unknown ospid (3630_47331091332240)
Sat Jan 22 16:25:23 2011
ORA-1092 : opiodr aborting process unknown ospid (3713_47194150415504)
Sat Jan 22 16:25:23 2011
ORA-1092 : opiodr aborting process unknown ospid (3726_47289949199504)
Sat Jan 22 16:25:23 2011
ORA-1092 : opiodr aborting process unknown ospid (3677_47842172337296)
Sat Jan 22 16:25:23 2011
ORA-1092 : opiodr aborting process unknown ospid (19131_47557370236048)
Sat Jan 22 16:25:23 2011
ORA-1092 : opiodr aborting process unknown ospid (27091_47096969530512)
Sat Jan 22 16:25:23 2011
ORA-1092 : opiodr aborting process unknown ospid (3688_47422639070352)
Sat Jan 22 16:25:23 2011
ORA-1092 : opiodr aborting process unknown ospid (3652_47944422886544)
Sat Jan 22 16:25:23 2011
ORA-1092 : opiodr aborting process unknown ospid (3648_47426149817488)
Sat Jan 22 16:25:24 2011
Errors in file /u01/app/oracle/diag/rdbms/evodb/EVODB1/trace/EVODB1_j005_9360.trc:
ORA-00472: PMON process terminated with error
ORA-1092 : opidrv aborting process J005 ospid (9360_47420959304848)
Sat Jan 22 16:25:24 2011
ORA-1092 : opiodr aborting process unknown ospid (18393_47566684101776)
Sat Jan 22 16:25:24 2011
Errors in file /u01/app/oracle/diag/rdbms/evodb/EVODB1/trace/EVODB1_j003_7054.trc:
ORA-00472: PMON process terminated with error
ORA-1092 : opidrv aborting process J003 ospid (7054_47244451724432)
Sat Jan 22 16:25:24 2011
ORA-1092 : opiodr aborting process unknown ospid (19719_47840732109968)
Sat Jan 22 16:25:24 2011
ORA-1092 : opiodr aborting process unknown ospid (22184_47575322619024)
Sat Jan 22 16:25:24 2011
ORA-1092 : opiodr aborting process unknown ospid (19721_47679094451344)
Sat Jan 22 16:25:24 2011
ORA-1092 : opiodr aborting process unknown ospid (30170_47106572815504)
Sat Jan 22 16:25:24 2011
ORA-472 : opidrv aborting process S000 ospid (9367_46990649617552)
Sat Jan 22 16:25:24 2011
Errors in file /u01/app/oracle/diag/rdbms/evodb/EVODB1/trace/EVODB1_j002_7052.trc:
ORA-00472: PMON process terminated with error
ORA-1092 : opidrv aborting process J002 ospid (7052_47411695402128)
Sat Jan 22 16:25:24 2011
ORA-1092 : opiodr aborting process unknown ospid (18493_47469336738960)
Sat Jan 22 16:25:24 2011
Errors in file /u01/app/oracle/diag/rdbms/evodb/EVODB1/trace/EVODB1_j006_10011.trc:
ORA-00472: PMON process terminated with error
ORA-1092 : opidrv aborting process J006 ospid (10011_47836408102032)
Sat Jan 22 16:25:24 2011
ORA-1092 : opiodr aborting process unknown ospid (19714_47958179912848)
Sat Jan 22 16:25:24 2011
Errors in file /u01/app/oracle/diag/rdbms/evodb/EVODB1/trace/EVODB1_j007_10289.trc:
ORA-00472: PMON process terminated with error
ORA-1092 : opidrv aborting process J007 ospid (10289_47356480347280)
Sat Jan 22 16:25:24 2011
ORA-1092 : opiodr aborting process unknown ospid (9076_47765392362640)
Sat Jan 22 16:25:24 2011
ORA-1092 : opitsk aborting process
Sat Jan 22 16:25:25 2011
ORA-1092 : opiodr aborting process unknown ospid (22167_47949919177872)
Sat Jan 22 16:25:25 2011
ORA-1092 : opiodr aborting process unknown ospid (24320_47408077532304)
Sat Jan 22 16:25:25 2011
ORA-1092 : opiodr aborting process unknown ospid (22130_47998542101648)
Sat Jan 22 16:25:25 2011
ORA-472 : opidrv aborting process N000 ospid (14774_47466200525968)
Sat Jan 22 16:25:25 2011
Errors in file /u01/app/oracle/diag/rdbms/evodb/EVODB1/trace/EVODB1_q000_14701.trc:
ORA-00472: PMON process terminated with error
ORA-1092 : opidrv aborting process Q000 ospid (14701_47693688122512)
Sat Jan 22 16:25:25 2011
ORA-1092 : opiodr aborting process unknown ospid (18386_47900707175568)
Sat Jan 22 16:25:25 2011
ORA-1092 : opiodr aborting process unknown ospid (27553_46921398619280)
Sat Jan 22 16:25:26 2011
Errors in file /u01/app/oracle/diag/rdbms/evodb/EVODB1/trace/EVODB1_j001_7050.trc:
ORA-00472: PMON process terminated with error
ORA-1092 : opidrv aborting process J001 ospid (7050_47290016251024)
Sat Jan 22 16:25:26 2011
Errors in file /u01/app/oracle/diag/rdbms/evodb/EVODB1/trace/EVODB1_o001_5297.trc:
ORA-00472: PMON process terminated with error
ORA-1092 : opidrv aborting process O001 ospid (5297_47702958673040)
Sat Jan 22 16:25:26 2011
Errors in file /u01/app/oracle/diag/rdbms/evodb/EVODB1/trace/EVODB1_o000_5277.trc:
ORA-00472: PMON process terminated with error
ORA-1092 : opidrv aborting process O000 ospid (5277_47599668255888)
Sat Jan 22 16:25:26 2011
ORA-1092 : opiodr aborting process unknown ospid (19745_47560156560528)
Sat Jan 22 16:25:26 2011
ORA-1092 : opiodr aborting process unknown ospid (27044_47388543339664)
Sat Jan 22 16:25:26 2011
Errors in file /u01/app/oracle/diag/rdbms/evodb/EVODB1/trace/EVODB1_j004_7061.trc:
ORA-00472: PMON process terminated with error
ORA-1092 : opidrv aborting process J004 ospid (7061_47341656689808)
Sat Jan 22 16:25:27 2011
ORA-1092 : opiodr aborting process unknown ospid (14431_47662297960112)
Sat Jan 22 16:25:27 2011
ORA-1092 : opiodr aborting process unknown ospid (14433_47826608635568)
Sat Jan 22 16:25:31 2011
ORA-1092 : opitsk aborting process
Sat Jan 22 16:25:32 2011
License high water mark = 269
Instance terminated by DBRM, pid = 9310
USER (ospid: 10539): terminating the instance
Instance terminated by USER, pid = 10539
Sat Jan 22 16:25:49 2011
Starting ORACLE instance (normal)
This is the trace /u01/app/oracle/diag/rdbms/evodb/EVODB1/incident/incdir_195200/EVODB1_pmon_9297_i195200.trc
(the one regarding the error DBRM (ospid: 9310): terminating the instance due to error 472)
Oracle Database 11g Release 11.1.0.6.0 - 64bit Production
With the Real Application Clusters option
ORACLE_HOME = /u01/app/oracle/product/11.1.0/db1
System name:    Linux
Node name:      dcsrv-evodb01
Release:        2.6.18-164.10.1.el5
Version:        #1 SMP Wed Dec 30 18:35:28 EST 2009
Machine:        x86_64
Instance name: EVODB1
Redo thread mounted by this instance: 1
Oracle process number: 2
Unix process pid: 9297, image: oracle@dcsrv-evodb01 (PMON)
*** 2011-01-22 16:25:12.984
*** SESSION ID:(884.1) 2011-01-22 16:25:12.984
*** CLIENT ID:() 2011-01-22 16:25:12.984
*** SERVICE NAME:(SYS$BACKGROUND) 2011-01-22 16:25:12.984
*** MODULE NAME:() 2011-01-22 16:25:12.984
*** ACTION NAME:() 2011-01-22 16:25:12.984
Dump continued from file: /u01/app/oracle/diag/rdbms/evodb/EVODB1/trace/EVODB1_pmon_9297.trc
ORA-00600: internal error code, arguments: [17183], [0x14E251C38], [], [], [], [], [], []
+========= Dump for incident 195200 (ORA 600 [17183]) ========+
----- Beginning of Customized Incident Dump(s) -----
And this is the trace /u01/app/oracle/diag/rdbms/evodb/EVODB1/trace/EVODB1_j005_9360.trc
(the one regarding the error ORA-00472: PMON process terminated with error)
Trace file /u01/app/oracle/diag/rdbms/evodb/EVODB1/trace/EVODB1_j005_9360.trc
Oracle Database 11g Release 11.1.0.6.0 - 64bit Production
With the Real Application Clusters option
ORACLE_HOME = /u01/app/oracle/product/11.1.0/db1
System name:    Linux
Node name:      dcsrv-evodb01
Release:        2.6.18-164.10.1.el5
Version:        #1 SMP Wed Dec 30 18:35:28 EST 2009
Machine:        x86_64
Instance name: EVODB1
Redo thread mounted by this instance: 1
Oracle process number: 95
Unix process pid: 9360, image: oracle@dcsrv-evodb01 (J005)
*** 2011-01-22 16:25:24.057
*** SESSION ID:(649.45863) 2011-01-22 16:25:24.057
*** CLIENT ID:() 2011-01-22 16:25:24.057
*** SERVICE NAME:(SYS$USERS) 2011-01-22 16:25:24.057
*** MODULE NAME:() 2011-01-22 16:25:24.057
*** ACTION NAME:() 2011-01-22 16:25:24.057
error 472 in job queue process
ORA-00472: PMON process terminated with error
My questions are:
- how can I discover the nature of the ORA-00600: internal error code, arguments: [17183], [0x14E251C38], [], [], [], [], [], []?
- what does error 472 in job queue proces mean?
- is it normal the the error 472 in job queue proces crash the instance?
Thanks in advanca for any kind of help!
Samuel

>
how can I discover the nature of the ORA-00600: internal error code, arguments: [17183], [0x14E251C38], [], [], [], [], [], []?
>
ORA-00600 should be reported to oracle. Only they know the meaning.
Regards,
- wiZ

I Cannot See Job Queue Processes (Jnnn) in v$session

Hello,
My Oracle environment is 9.2.0.8 on IBM AIX platform.
I found that I cannot see any job queue process (Jnnn) in v$session.
However, the program of the relative process in v$session is null value.
Does anybody know what is going wrong?
Thank you.

not sure...
I have used 10g RAC.... I find programs .....: os_user@hostname (J00x)
select inst_id,action ,username ,program from gv$session where program like upper('%j00%')

Simple Queue-Queue Failing with : kwqjaq: Only job queue slave can run prop

I know this is a simple problem, but I can't get by it.
I have two DB servers and I just want to queue a message on a local queue and have it propagated to a remote queue.
Here are my steps:
I do this on both databases:
grant dba to johnb identified by johnb ;
connect johnb/johnb
create type my_type as object ( a number, b varchar2(2000), c varchar2(2000)) ;
--- multi consumer queue
Begin
/* This queue table should already exist */
dbms_aqadm.create_queue_table( queue_table => 'MY_QUEUE_TAB',
queue_payload_type => 'MY_TYPE',
multiple_consumers => TRUE,
comment => 'Test MultiConsumer OAQ',
compatible => '8.1.0' );
DBMS_AQADM.CREATE_QUEUE (
queue_name => 'MY_QUEUE'
, queue_table => 'MY_QUEUE_TAB' );
dbms_aqadm.start_queue('MY_QUEUE') ;
End;
-- on "Local DB" I do the following:
DECLARE
subscriber sys.aq$_agent;
BEGIN
subscriber := sys.aq$_agent( 'subscriber1' , 'JOHNB.MY_QUEUE@otmdmz2' , null);
DBMS_AQADM.ADD_SUBSCRIBER(queue_name => 'JOHNB.MY_QUEUE', subscriber => subscriber);
END;
-- scheduling propagation
BEGIN
DBMS_AQADM.SCHEDULE_PROPAGATION( queue_name => 'JOHNB.MY_QUEUE' , destination => 'otmdmz2' , destination_queue => 'JOHNB.MY_QUEUE');
END;
BEGIN
DBMS_AQADM.ALTER_PROPAGATION_SCHEDULE( queue_name => 'JOHNB.MY_QUEUE' , destination => 'otmdmz2' , destination_queue => 'JOHNB.MY_QUEUE' , latency => 1 );
END;
-- I queue with this
-- enqueue local
DECLARE
enqueue_options DBMS_AQ.enqueue_options_t;
enqueue_properties DBMS_AQ.message_properties_t;
enqueue_handle RAW(16) ;
enqueue_message JOHNB.MY_TYPE;
BEGIN
enqueue_message := JOHNB.MY_TYPE(1, 'an aq test','sending to remote db' ) ;
dbms_aq.enqueue(queue_name => 'JOHNB.MY_QUEUE',
enqueue_options => enqueue_options,
message_properties => enqueue_properties,
payload => enqueue_message,
msgid => enqueue_handle) ;
commit ;
end;
No messages move to remote DB.
I can see the message in the local queue table.
Both databases have the same init.ora parameters : job_queue_processes=1000, aq_tm_processes=1.
If I attempt to run the job I get the message in the subject line in a trace file:
kwqjaq: Only job queue slave can run propagation job, exiting
Though I am sure simple configuration issue, I cannot find a relevant note.
Thanks,
John

Another case of the documentation being less than precise - it happens.
Without personally having investigated, that's my understanding as well bearing in mind the following observation/explanation in the same article which seems to apply for all except 11gR2:
Although you typically use the JOB_QUEUE_PROCESSES initialization parameter to limit
the number job queue processes for DBMS_JOB and you use the Scheduler attribute
max_job_slave_processes to limit the number of job slave processes for the Scheduler,
the Scheduler is affected by the JOB_QUEUE_PROCESSES parameter.
The maximum number of job slave processes for Scheduler is determined by the lesser
of the values of JOB_QUEUE_PROCESSES and max_job_slave_processes. For example:
If JOB_QUEUE_PROCESSES is set to 10 and max_job_slave_processes is set to 20,
the job coordinator will start no more than 10 job slave processes to be shared
between DBMS_JOB and the Scheduler.
If JOB_QUEUE_PROCESSES is 20 and max_job_slave_processes is 10, the coordinator
will start up to 20 job slave processes. The Scheduler can use only 10 of these,
but DBMS_JOB can use all 20.
If JOB_QUEUE_PROCESSES is 0, DBMS_JOB is disabled, and the maximum number of
job slave processes for Scheduler is controlled by the max_job_slave_processes
Scheduler attribute.

FBU Internal Job Queue Full for Synchronous Processing of Print Requests

Hello All,
We are getting a lot of errors in system log (SM21) with the
Error : FBU Internal Job Queue Full for Synchronous Processing of Print Requests
User :SAPSYS
MNO:FBU
=============================================================
Documentation for system log message FB U :
If a spool server is to process output requests in the order they were
created using multiple work processes, the processing of requests for a
particular device can only run on one work process. To do this an
internal queue (limited size) is used.
If too many requests are created for this device too quickly, the work
process may get overloaded. This is recognized when, as in this case,
the internal queue is exhausted.
This can only be solved by reducing the print load or increasing
processor performance or, if there is a connection problem to the host
spooler, by improving the transfer of data to the host spooler.
Increasing the number of spool work processes will not help, as
requests for one device can only be processed by one work process. If
processing in order of creation is not required, sequential request
processing can be deactivated (second page of device configuration in
Transaction SPAD). This allows several work processes to process
requests from the same device thus alleviating the bottleneck.
Enlarging the internal queue will only help if the overload is
temporary. If the overload is constant, a larger queue will eventually
also be overloaded.
===========================================================
Can you please tell me how to proceed.
Best Regards,
Pratyusha

Solution is here:
412065 - Incorrect output sequence of output requests
Reason and Prerequisites
The following messages appear in the developer trace (dev_trc) of the SPO processes or in the syslog:
S *** ERROR => overflow of internal job queue [rspowunx.c 788]
Syslog Message FBU:
Internal job queue for synchronous request processing of output requests full
The "request processing sequence compliance" on a spool server with several SPO processes only works provided the server-internal job queue (see Note 118057) does not overflow. The size of this request queue is prepared using the rspo/global_shm/job_list profile parameter. The default value is 50 requests. However, if more output requests arrive for the spool server than can be processed (and the internal request queue is full as a result), more SPO processes are used to process the requests (in parallel), and the output sequence of the requests is no longer guaranteed.
Solution
Increase the rspo/global_shm/job_list profile parameter to a much larger value. Unfortunately, the value actually required cannot be found by "trial and error" because this queue contains all the incoming output requests on a spool server, not just the "sequence compliant" requests. A practical lower limit for this value represents the maximum sequence-compliant output requests for the above generated output device. If, for example, 1000 documents that should be output in sequence are issued from an application program to an output device, the queue must be able to hold 1000 entries so that it does not overflow if the SPO process processes the requests at a maximum low-speed.

Err:Internal Job Queue full for synchronous processing of print requests

Hi,
We are getting a lot of errors in system log with the
error :
Internal Job Queue full for synchronous processing of print requests.
User :SAPSYS
MNO:FBU.
When we check the document in syslog it states it can be solved by reducing the print load or increasing performance or if there is a connection problem to host spooler , by improving the transfer of data to host spooler..
But not by increasing the no of spool workprocess..
I think any of the one stated cannot be implemented ..
Pls provide your valuable answers and if any of the above can be implemented from your end..
Regds,
Satyanarayana N

Hi Vamshi,
Thanks for your response but would also like to confirm how we can say that spool queue is full and what may be the Max size of spool queue..
When we say Internal queue is full does it mean spool queue...
And also when I run the TEmse consistency check it is giving some errors..
When I check Spool requests there are some waiting process,but when I check Output requests there are only 1 or 2..
Please provide me your valuable solution regd this..
Regds,
Satyanarayana N.
Regds,
Satyanarayana N.

Can I create a table in a procedure submitted to job queue?

I have created a package (with AUTHID CURRENT_USER) where some of the procedures create temporary tables to facilitate processing. These procedures run just fine when executed directly from within an anonymous block at the SQL*PLUS level. However, when I submit the procedures to the job queue (via DBMS_JOB.SUBMIT), the job is submitted successfully but fails when run. Investigating the Alert Log shows an error of insufficient privilege on the CREATE TABLE command in the procedure.
QUESTION:
Can I create a table from a procedure running in the Job Queue? If so, then how to get it to work? Does the job run in a different environment that needs Create Table privileges set to my schema?
Thanks for any info you can provide.
John

FYI: Found the problem. In the Administrator's Guide (of course not in the supplied packages documentation about DBMS_JOB) I found:
"How Jobs Execute
SNP background processes execute jobs. To execute a job, the process creates a session to run the job.
When an SNP process runs a job, the job is run in the same environment in which it was submitted and with the owner's default privileges.
When you force a job to run using the procedure DBMS_JOB.RUN, the job is run by your user process. When your user process runs a job, it is run with your default privileges only. Privileges granted to you through roles are unavailable."
And of course we had set up our users to get all privileges through Roles, so CREATE TABLE wasn't one of my DEFAULT PRIVILEGES!
It sure would be nice if Oracle documentation could get its act together and provide ALL information about a topic in a logical place. The effort to find the information about privileges occurred after it took me 1/2 hour to figure out why my submissions were failing - I didn't have the ';' included in the quoted string for the procedure to be called - which I only figured out after looking at the code for DBMS_JOB where it made the note to make sure you include the ';'. Wouldn't it be good to have that MINOR DETAIL mentioned in the description of DBMS_JOB.SUBMIT?????

Job to process messages in Ready Status in SMQ2 ECC

Hello friends,
I am sending out messages from SAP ECC to PI using proxy . The messages are getting stuck in SMQ2 in READY status. I have to each time manually go and activate the queue to send the message out of SAP ECC.
Is there any job to process them automatically that needs to be set up in SAP ECC ?
Thank you,
Teresa

Hi,
Investigate why messages were strucked in Queues, there could be some reason, i suggest you too deregister and register queues once again.
if possible assign sepprate queue for proxy interface.
Regards,
Raj

Networked OJ 8500 that is extremely slow in job queuing.

We recently installed an OJ 8500 and the job queuing is extremely slow. The printer is networked (wired) and all users have the same problem. We run a combination of XP, Vista and Windows7. We have no problem getting the printer to print. Its just painfully slow. Job to job delays are 30 sec to 1 min. The first job is slow to start. Multiple copies of the same page print with this long delay between pages. The OJ 5400 we had previously did not have this problem. Can this be fixed?

Once the job hits the printer it prints immediately. It's right after you tap Print on the iPad that takes a long time. There is a box that pops up saying that the job is being processed (don't remember the wording exactly). Once the box disappears it also takes a bit of time for the job to hit the printer.
The actual process of the printer printing is normal.
Also, in some cases the iPad won't even see that there is a printer connected to the network even though the printer is powered on, online and the iPad is connected to the home network. Usually a reboot of the printer fixes this problem.
Thanks

Why job queue can't start?

DB: Oracle 9i Enterprise Edition Release 9.2.0.5.0
Platform: Windows 2003 Server
I imported several job queues from another oracle DB, after submit them, it seems everything is ok. But it can't start automatically upon reach time. (Should be run every 2 minutes)
I check the dba_jobs view, BROKEN = N, INTERVAL = ‘sysdate + 2/60/24’,FAILUERS=0. And I can successfully execute the job by DBMS_JOB.RUN(job_no), but it won't start again after next time reach.
CONNECT, RESOURCE and SELECT_CATALOG_ROLE privilege were granted to job owner, and JOB_QUEUE_PROCESSES parameter was set to 10. JOB_QUEUE_INTERVAL wasn't set in init.ora file.
no relative error was found in alter.log file.
Thanks.

even there's no job runing you should still see this process after you set
JOB_QUEUE_PROCESSES
if you select from v$process you should see some process like this
oracle@yourhost (J000)
I don't have a Window platform to test this, because in windows Oracle is threaded instead of having seperate processes
How Jobs Execute
Jnnn processes execute jobs. To execute a job, the process creates a session to run the job. When a Jnnn process runs a job, the job is run in the same environment in which it was submitted and with the owner's default privileges. The owner must be explicitly granted the necessary object privileges for all objects referenced within the job definition.
When you force a job to run using the procedure DBMS_JOB.RUN, the job is run by your user process and with your default privileges only. Privileges granted to you through roles are unavailable. You must be explicitly granted the necessary object privileges for all objects referenced within the job definition.
http://download-west.oracle.com/docs/cd/B10501_01/server.920/a96521/jobq.htm#991

Missing AW Maintenance Details When Submitting to Oracle Job Queue

Is there a way to know the number of added/deleted members or the processed/ rejected records of a dimension/cube maintenance that was submitted to the Oracle Job Queue?
The following is the log of my recent maintenance task that was submitted to the Oracle Job Queue:
18:59:03 Attached AW OLAP_TEST.AW_TEST in RW Mode.
18:58:27 Completed Build(Refresh) of OLAP_TEST.AW_TEST Analytic Workspace.
18:58:27 Finished Parallel Processing.
18:58:21 Running Jobs: AWXML$_2534_1. Waiting for Tasks to Finish...
18:58:21 Started 1 Finished 0 out of 1 Tasks.
18:58:21 Running Jobs: AWXML$_2534_1.          Usually, there would be a line in the XML_LOAD_LOG table where the added/deleted members or processed/rejected records can be found. In this case, there is none.

Usually the entries you want are before these lines (time-wise). The parallel processing only handles aggregating fact partitions in parallel, not loading the base level data.

How to find out the user from the Jobs queue in Report server

Hello All!
I have a doubt about finding out the user from the scheduled jobs queue. Say I go ahead and schedule a report on Reports Server how can I find out the user name. When I view the jobs using showjobs I could see that the DBMS_JOBS table has a column under "Job Owner". But it invariantly shows it is "rwuser". So is there a way to find out which user has scheduled which job?
Regards
Shobha

hi,
The below tables will give only the name .
USER_ADDRS
USER_ADDR
USER_ADDRP
USR02
i think you need email address .
you can use this Tcode : su01d
and give the user name and excute it
i hope it will help you.
Ram
Edited by: Ram velanati on Jun 30, 2008 6:57 PM

Triggering Process chain based on execution of R3 job and Process Chain

Hi All,
I need your help in arriving at a solution for a reqirement.
Scenario is., I need to trigger a process chain B based on successful execution of Process chain A and an R3 job. If both conditions(Completion of R3 job and Process Chain A) are met then only it has to trigger process Chain B.
I know that we can use events to trigger a process chain using R3 job.But my case is differenet I need to consider the success message from both process chain and R3 job.Is there any way to solve it ?
Please provide me with your valuable inputs.
Thanks,
Bindu

Hi Hima,
You can use the 'AND' variant for both, If both are success then trigger the process chain.
Regards,
Ravi Kanth
Edited by: Ravi kanth on Apr 30, 2009 3:36 PM

Thunderbird won't print, even though Firefox will. Job queued, but seems to think printer is offline?

Thunderbird won't print, even though Firefox will. Print preview works fine. Job queued, but seems to think printer is offline? Port is not listed when look at print job. (USB connection) Wasn't getting an error message... job just never printed or leaves the queue. Restarting job does not help.
Setting details below.
Application Basics
Name: Thunderbird
Version: 24.4.0
User Agent: Mozilla/5.0 (Windows NT 6.2; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.4.0
Profile Folder: Show Folder
(Local drive)
Application Build ID: 20140316131045
Enabled Plugins: about:plugins
Build Configuration: about:buildconfig
Crash Reports: about:crashes
Memory Use: about:memory
Mail and News Accounts
account1:
INCOMING: account1, , (pop3) mail.comcast.net:110, alwaysSTARTTLS, passwordCleartext
OUTGOING: smtp.comcast.net:587, alwaysSTARTTLS, passwordCleartext, true
account2:
INCOMING: account2, , (none) Local Folders, plain, passwordCleartext
Extensions
Test Pilot for Thunderbird, 1.3.9, true, [email protected]
Important Modified Preferences
Name: Value
accessibility.typeaheadfind.flashBar: 0
browser.cache.disk.capacity: 358400
browser.cache.disk.smart_size.first_run: false
browser.cache.disk.smart_size.use_old_max: false
browser.cache.disk.smart_size_cached_value: 358400
extensions.lastAppVersion: 24.4.0
font.name.monospace.el: Consolas
font.name.monospace.tr: Consolas
font.name.monospace.x-baltic: Consolas
font.name.monospace.x-central-euro: Consolas
font.name.monospace.x-cyrillic: Consolas
font.name.monospace.x-unicode: Consolas
font.name.monospace.x-western: Consolas
font.name.sans-serif.el: Calibri
font.name.sans-serif.tr: Calibri
font.name.sans-serif.x-baltic: Calibri
font.name.sans-serif.x-central-euro: Calibri
font.name.sans-serif.x-cyrillic: Calibri
font.name.sans-serif.x-unicode: Calibri
font.name.sans-serif.x-western: Calibri
font.name.serif.el: Cambria
font.name.serif.tr: Cambria
font.name.serif.x-baltic: Cambria
font.name.serif.x-central-euro: Cambria
font.name.serif.x-cyrillic: Cambria
font.name.serif.x-unicode: Cambria
font.name.serif.x-western: Cambria
font.size.fixed.el: 14
font.size.fixed.tr: 14
font.size.fixed.x-baltic: 14
font.size.fixed.x-central-euro: 14
font.size.fixed.x-cyrillic: 14
font.size.fixed.x-unicode: 14
font.size.fixed.x-western: 14
font.size.variable.el: 17
font.size.variable.tr: 17
font.size.variable.x-baltic: 17
font.size.variable.x-central-euro: 17
font.size.variable.x-cyrillic: 17
font.size.variable.x-unicode: 17
font.size.variable.x-western: 17
mail.openMessageBehavior.version: 1
mail.winsearch.firstRunDone: true
mailnews.database.global.datastore.id: 3e3245e7-bdfc-4ebf-98fb-abc47a5f973
network.cookie.prefsMigrated: true
places.database.lastMaintenance: 1395283212
places.history.expiration.transient_current_max_pages: 104858
plugin.importedState: true
print.printer_Brother_MFC-9970CDW.print_bgcolor: false
print.printer_Brother_MFC-9970CDW.print_bgimages: false
print.printer_Brother_MFC-9970CDW.print_colorspace:
print.printer_Brother_MFC-9970CDW.print_command:
print.printer_Brother_MFC-9970CDW.print_downloadfonts: false
print.printer_Brother_MFC-9970CDW.print_duplex: 0
print.printer_Brother_MFC-9970CDW.print_edge_bottom: 0
print.printer_Brother_MFC-9970CDW.print_edge_left: 0
print.printer_Brother_MFC-9970CDW.print_edge_right: 0
print.printer_Brother_MFC-9970CDW.print_edge_top: 0
print.printer_Brother_MFC-9970CDW.print_evenpages: true
print.printer_Brother_MFC-9970CDW.print_footercenter:
print.printer_Brother_MFC-9970CDW.print_footerleft:
print.printer_Brother_MFC-9970CDW.print_footerright:
print.printer_Brother_MFC-9970CDW.print_headercenter:
print.printer_Brother_MFC-9970CDW.print_headerleft:
print.printer_Brother_MFC-9970CDW.print_headerright:
print.printer_Brother_MFC-9970CDW.print_in_color: true
print.printer_Brother_MFC-9970CDW.print_margin_bottom: 0.5
print.printer_Brother_MFC-9970CDW.print_margin_left: 0.5
print.printer_Brother_MFC-9970CDW.print_margin_right: 0.5
print.printer_Brother_MFC-9970CDW.print_margin_top: 0.5
print.printer_Brother_MFC-9970CDW.print_oddpages: true
print.printer_Brother_MFC-9970CDW.print_orientation: 0
print.printer_Brother_MFC-9970CDW.print_page_delay: 50
print.printer_Brother_MFC-9970CDW.print_paper_data: 1
print.printer_Brother_MFC-9970CDW.print_paper_height: 11.00
print.printer_Brother_MFC-9970CDW.print_paper_name:
print.printer_Brother_MFC-9970CDW.print_paper_size_type: 0
print.printer_Brother_MFC-9970CDW.print_paper_size_unit: 0
print.printer_Brother_MFC-9970CDW.print_paper_width: 8.50
print.printer_Brother_MFC-9970CDW.print_plex_name:
print.printer_Brother_MFC-9970CDW.print_resolution: 93725024
print.printer_Brother_MFC-9970CDW.print_resolution_name:
print.printer_Brother_MFC-9970CDW.print_reversed: false
print.printer_Brother_MFC-9970CDW.print_scaling: 0.90
print.printer_Brother_MFC-9970CDW.print_shrink_to_fit: false
print.printer_Brother_MFC-9970CDW.print_to_file: false
print.printer_Brother_MFC-9970CDW.print_unwriteable_margin_bottom: 0
print.printer_Brother_MFC-9970CDW.print_unwriteable_margin_left: 0
print.printer_Brother_MFC-9970CDW.print_unwriteable_margin_right: 0
print.printer_Brother_MFC-9970CDW.print_unwriteable_margin_top: 0
print.printer_Brother_MFC-9970CDW_Printer.print_bgcolor: false
print.printer_Brother_MFC-9970CDW_Printer.print_bgimages: false
print.printer_Brother_MFC-9970CDW_Printer.print_colorspace:
print.printer_Brother_MFC-9970CDW_Printer.print_command:
print.printer_Brother_MFC-9970CDW_Printer.print_downloadfonts: false
print.printer_Brother_MFC-9970CDW_Printer.print_duplex: 0
print.printer_Brother_MFC-9970CDW_Printer.print_edge_bottom: 0
print.printer_Brother_MFC-9970CDW_Printer.print_edge_left: 0
print.printer_Brother_MFC-9970CDW_Printer.print_edge_right: 0
print.printer_Brother_MFC-9970CDW_Printer.print_edge_top: 0
print.printer_Brother_MFC-9970CDW_Printer.print_evenpages: true
print.printer_Brother_MFC-9970CDW_Printer.print_footercenter:
print.printer_Brother_MFC-9970CDW_Printer.print_footerleft:
print.printer_Brother_MFC-9970CDW_Printer.print_footerright:
print.printer_Brother_MFC-9970CDW_Printer.print_headercenter:
print.printer_Brother_MFC-9970CDW_Printer.print_headerleft:
print.printer_Brother_MFC-9970CDW_Printer.print_headerright:
print.printer_Brother_MFC-9970CDW_Printer.print_in_color: true
print.printer_Brother_MFC-9970CDW_Printer.print_margin_bottom: 0.5
print.printer_Brother_MFC-9970CDW_Printer.print_margin_left: 0.5
print.printer_Brother_MFC-9970CDW_Printer.print_margin_right: 0.5
print.printer_Brother_MFC-9970CDW_Printer.print_margin_top: 0.5
print.printer_Brother_MFC-9970CDW_Printer.print_oddpages: true
print.printer_Brother_MFC-9970CDW_Printer.print_orientation: 0
print.printer_Brother_MFC-9970CDW_Printer.print_page_delay: 50
print.printer_Brother_MFC-9970CDW_Printer.print_paper_data: 1
print.printer_Brother_MFC-9970CDW_Printer.print_paper_height: 11.00
print.printer_Brother_MFC-9970CDW_Printer.print_paper_name:
print.printer_Brother_MFC-9970CDW_Printer.print_paper_size_type: 0
print.printer_Brother_MFC-9970CDW_Printer.print_paper_size_unit: 0
print.printer_Brother_MFC-9970CDW_Printer.print_paper_width: 8.50
print.printer_Brother_MFC-9970CDW_Printer.print_plex_name:
print.printer_Brother_MFC-9970CDW_Printer.print_resolution: 93725024
print.printer_Brother_MFC-9970CDW_Printer.print_resolution_name:
print.printer_Brother_MFC-9970CDW_Printer.print_reversed: false
print.printer_Brother_MFC-9970CDW_Printer.print_scaling: 1.00
print.printer_Brother_MFC-9970CDW_Printer.print_shrink_to_fit: false
print.printer_Brother_MFC-9970CDW_Printer.print_to_file: false
print.printer_Brother_MFC-9970CDW_Printer.print_unwriteable_margin_bottom: 0
print.printer_Brother_MFC-9970CDW_Printer.print_unwriteable_margin_left: 0
print.printer_Brother_MFC-9970CDW_Printer.print_unwriteable_margin_right: 0
print.printer_Brother_MFC-9970CDW_Printer.print_unwriteable_margin_top: 0
Graphics
Adapter Description: Intel(R) HD Graphics 4000
Vendor ID: 0x8086
Device ID: 0x0166
Adapter RAM: Unknown
Adapter Drivers: igdumd64 igd10umd64 igd10umd64 igdumd32 igd10umd32 igd10umd32
Driver Version: 8.982.6.0
Driver Date: 8-1-2012
Direct2D Enabled: Blocked for your graphics driver version.
DirectWrite Enabled: false (6.2.9200.16581)
ClearType Parameters: ClearType parameters not found
WebGL Renderer: false
GPU Accelerated Windows: 0
AzureCanvasBackend: skia
AzureFallbackCanvasBackend: cairo
AzureContentBackend: none
JavaScript
Incremental GC: 1
Accessibility
Activated: 1
Prevent Accessibility: 0
Library Versions
Expected minimum version
Version in use

gabri21 wrote: I have a very similar problem with my PSC1510 but only the colour cartridge light is blinking. I am also unable to find any useful information to set up printing in back up mode. Can anyone assist in resolving this problem for us?
With only one cartridge light blinking I would suspect the cartridge, they do rarely fail (much more often for reman cartridges, see here). Clean the cartridge contascts as shown here. If that fails and the cartridge is an original HP then check the warranty date as shown here. If the cartridge is in warranty return it to your dealer for a warranty replacement.
The printer will automatically switch to backup mode if the black (or color in some printers) cartridge is removed. I do not know if this works with the PSC 1510, some all-in-on devices insist on having both cartridges present.
Bob Headrick, HP Expert
I am not an employee of HP, I am a volunteer posting here on my own time.
If your problem is solved please click the "Accept as Solution" button ------------V
If my answer was helpful please click the "Thumbs Up" to say "Thank You"--V

Not clearing the job queue

Hello everyone,
We've been experiencing some oddities in our database and we hope to find some help around here. The scenario is as follows:
Our job queue shows 13 pages of jobs, updated in the last 5 days, in which we find lots of jobs - actually most of them from 3 days ago - with the progress showing "transcoding clip" and the status as "RUN".
When we try to cancel any of those jobs we get an error message that says: "Error cancelling - this job is currently not running".
We have tried flushing the event queue from Terminal using the following commands:
fcsvr_client flushresponsequeue
fcsvr_run psql px pxdb -c "vacuum analyze verbose;"
but none of them solved our problem. We cannot clear the event tables in the db (pxevent and pxeventresponse). We have even tried a more desperate solution by accessing the db via Navicat and manually deleting each and every row (!!!), visually clearing the tables.
BUT on the next day they did reappear and on the day after double in quantity (i.e. empty table --next day--> 4K rows --next day--> +4K rows and so on...).
So now we have 18,826 entries in our table which seems to grow indefinitely (and for no apparent reason).
We fear that our problem may get worse and cause us bigger problems. Any help would be very appreciated.
Details of the system: FCS V1.5.2 / Mac OS X (10.5.8)
Thank you in advance,

Hey guys, thanks for the replies.
the issues with the "pxevent" and "pxeventresponse" tables seems to have been solved BUT the issue with the Job queue remains the same.
Old (1 day old or more) jobs are showing status as RUN although when you try to delete it you get an error message which says "error cancelling - this job is currently not running" despite the fact it is shown as running. When you "get info" on any of those, you can see in the logs that it has failed and retried, then failed again (on the retry). This condition should make the status change from RUN to FAIL but it is not what's happening.
All this ends up putting some recently added jobs on a WAIT status which ends up kind of locking my queue (therefore preventing jobs from running, timming them out and, consequently, failing them). If I go to the "pxjobs" table and delete all entries it solves the symptom (as it was well said by one of you) but the problem doesn't cease to happen.
I can force the waiting jobs to run now but they end up failing too.
Any thoughts on that? I have some print screens but don't know if I can post them here (newbie on this forum, sorry ).
Thanks for your attention

Overweight job queue process

Similar Messages

Maybe you are looking for