Cjq process related entries in alert log

Hi,
I have recently set up 10g (10.2.0.4) database on solaris 10. In the alert log of the db , there are entries like this;
Mon May 25 02:31:56 2009+
Starting background process CJQ0+
CJQ0 started with pid=15, OS id=18484+
Mon May 25 03:12:47 2009+
Stopping background process CJQ0+
the database is up and it is running but in alert log several such messages are there...not sure why the CJQ processes should start and shut down. can you suggest regarding possible cause for it.
thanks
Edited by: orausern on May 25, 2009 7:22 AM
Edited by: orausern on May 25, 2009 7:22 AM

From the documentation you get the following:
This is the Oracle’s dynamic job queue coordinator. It periodically selects jobs that need to be run, scheduled by the Oracle job queue. The coordinator process dynamically spawns job queue slave processes (J000…J999) to run the jobs. These jobs could be PL/SQL statements or procedures on an Oracle instance. Please note that this is not a persistent process. It comes and goes.
Regards, Gerwin

Similar Messages

Which background process writes date into alert log file in oralce

which background process writes date into alert log file in oralce

Hi,
AFAIK, all the background process are eligible for writing information to alert log file. As the file name indicates to show the alerts, so background process have the access rights in terms of packages (dbms), to write to alert log.
I might be wrong also..
- Pavan Kumar N

Corrupt block relative dba: in alert log

hi,
In our recovery database,I've found following error in alert log.
Thu Mar 27 07:05:57 2008
Hex dump of (file 3, block 30826) in trace file /u01/app/oracle/admin/catdb/bdump/catdb_m000_21795.trc
Corrupt block relative dba: 0x00c0786a (file 3, block 30826)
Bad check value found during buffer read
Data in bad block:
type: 6 format: 2 rdba: 0x00c0786a
last change scn: 0x0000.0013ed4d seq: 0x1 flg: 0x06
spare1: 0x0 spare2: 0x0 spare3: 0x0
consistency value in tail: 0xed4d0601
check value in block header: 0x937c
computed block checksum: 0x8000
Reread of rdba: 0x00c0786a (file 3, block 30826) found same corrupted data
Thu Mar 27 07:05:59 2008
Corrupt Block Found
TSN = 2, TSNAME = SYSAUX
RFN = 3, BLK = 30826, RDBA = 12613738
OBJN = 8964, OBJD = 8964, OBJECT = WRH$_ENQUEUE_STAT, SUBOBJECT =
SEGMENT OWNER = SYS, SEGMENT TYPE = Table Segment
Now, how solve this error?
Thanks in advance.
Leo

Refer to metalink Note:77587.1. You may need to do further sanity block checking by placing the following parameters in the database instance init.ora parameter file:
db_block_checking=true
db_block_checksum=true
dbblock_cache_protect= true
Consult Oracle support before changing hidden parameters.

How to initiating entry in alert.log?

Hallo,
i want initiate an entry in the alert.log by myself.
how can i do that?
thanks in advance

just make a archive log switch or shut down startup or any parameter changes which will effect alert.log file and there are many more

New Archived log entry in alert log after cpu patch 19 applied

Has anyone applied October critical patch for 11.1.0.7? I applied the cpu Patch 19 (8892977) for 11.1.0.7 on several windows2008 servers and after the patch the alert log displays a new message everytime a redo log transfers. This only happens on servers that have archivelog on. It looks like there is some kind of trace set. Anyone know know what the message is?
Thanks,
Kathie
Archived Log entry 10937 added for thread 1 sequence 10938 ID 0xa96e3908 dest 10:

Hi Mark!
Yes, Oracle informed me that this message is normal and is only used for formational purposes. I should just ignore it.
Did you apply patch19? I have also found issues with a high amount of "waits" of type of "other". Some jobs are running slightly slower also. Also, if you check your "database health link" on dbconsole home page you will see consistant "non-critical" alerts. I don't have these alerts on servers not yet patched. This alerts appear to be caused by wait events of "other".
Kathie

Question about the Initialization Parameters Information in the Alert.log

Hi, All -
What is the correct answer for the following question.
Specifically, what information does Oracle provide you with in the alert.log regarding initialization parameters?
a. Values of all initialization parameters at startup
b. Values of initialization parameters modified since last startup
c. Values of initialization parameters with non-default values
d. Only values of initialization parameters that cannot be modified dynamically.
I think the answer should be B, but I would like to confirm.

The answer is C
http://download.oracle.com/docs/cd/B19306_01/server.102/b14220/process.htm#sthref1633
The alert log is a special trace file. The alert log of a database is a chronological log of messages and errors, and includes the following items:
All internal errors (ORA-600), block corruption errors (ORA-1578), and deadlock errors (ORA-60) that occur
Administrative operations, such as CREATE, ALTER, and DROP statements and STARTUP, SHUTDOWN, and ARCHIVELOG statements
Messages and errors relating to the functions of shared server and dispatcher processes
Errors occurring during the automatic refresh of a materialized view
The values of all initialization parameters that had nondefault values at the time the database and instance start
Kamran Agayev A. (10g OCP)
http://kamranagayev.wordpress.com

Online viewing of alert log

I know that there is a switch for online using the less command. does any one know the exact syntax to enable viewing entries of alert log as and when they are written? Some thing like autoscroll of the alert log entries so we can monitor the entries..
RGDS,
BMP

So far the less command displays in a pg like manner contents from any text file, but the controls it provides are for browsing/editting.
~ Madrid

Most Recent Alert Log Entries - Error processing Alert Log

Hi..
Can someone help me?
When I want to check the log of alerts the following thing goes out for me:
"This shows the last 100,000 bytes of the alert log. The log is constantly growing, so select the browser's Refresh button to see the most recent log entries.
Number of Lines Displayed Error processing Alert Log"
Since I can solve it?

Number of Lines Displayed Error processing Alert Log"
check ur alert.log file content any data.
bcoz if ur alert.log file entries is null then above error is show. ( happen with me when i am purge alert.log file and try to view content of alert.log then above error received so may be problem is null contents ( empty alert.log file)).
HTH

Removed standby but getting interesting alert log entry

So, we had multiple set ups of primary database in our local data center, standby in remote location.
We're in the process of shutting down our remote location and have shut down our standbys gracefully, i.e., shutdown managed standby mode, removed archive_log_dest, changed archive_log_dest_state, etc. However, in some primary databases, I'm seeing a weird entry in the alert log:
Changing destination 2 from remote to local during archival of log#: 2 sequence#: 48708 thread#: 1
If I check my local destination, the archive log is created fine. In the remote location, no archives are being created.
I've not found anything on Google, Metalink, anywhere! Has anyone else seen this before, and if so, do I need to worry about it?
Oracle version is 11.1.0.7

Hello;
Its just information. You can ignore it.
Went back to some 2010 alert logs and found :
network reconnect abandoned
Attempting destination LOG_ARCHIVE_DEST_2 network reconnect
Setting 'active' archival for destination LOG_ARCHIVE_DEST_2Not much chance of finding here as all old version of Oracle are gone and a SAN move makes old alert logs rare. Still it just information or Oracle would throw an error.
Best Regards
mseberg
Edited by: mseberg on Jul 31, 2012 11:32 AM
Later
Tried to recreate message using several combinations of the parameters you listed. Unable to recreate, but only have 11.2.0.3.0 to test on.
Edited by: mseberg on Jul 31, 2012 12:44 PM

"unable to spawn jobq slave process" in alert.log

I had these errors in my alert.log Sunday morning right after the oracle export pump. It had detail in two trace files
ORA-00610: Internal error code
ORA-00610: Internal error code
Died during process startup with error 447 (seq=94168)
OPIRIP: Uncaught error 447. Error stack:
ORA-00447: fatal error in background process
and
Dumping diagnostic information for J000:
OS pid = 815310
loadavg : 0.20 0.29 0.39
swap info: free_mem = 0.00M rsv = 24.50M
alloc = 2489.02M avail = 6272.00M swap_free = 3782.98M
F S UID PID PPID C PRI NI ADDR SZ WCHAN STIME TTY TIME CMD
240001 A oracle 815310 1 1 60 20 10682400 87756 01:34:44 - 0:00 ora_j000_BAAN
open: The file access permissions do not allow the specified action.
procstack: 815310 is not a process
From several online informations I found, it seems that there is a problem of memory in my Oracle 10g R2 (10.2.0.1) on AIX5.3L. The server has 4 G memory, 4 CPU. I allocated 1904 M for the SGA, 512M for PGA.
How do I handle this problem? It happened before but not quite often.

If this error is reproducible, and constant, the reason is under control. You state this error shows up when a backup task is performed.
Is this task programmed using the enterprise manager job frame? Increase the value of job_queue_processes parameter. And check the value of processes parameter.
It could be that when the export task is lauched it exhausts the maximum number of instance processes and a new job queue process can't be launched, or the number of job queue processes has reached a top limit and a new task cannot be started.

Alert log display"Log actively being archived by another process"

In my Production database(9i) alert log display me "Log actively being archived by another process".
I want to know why this show,reason and how can i solve it.
Wed Dec 05 00:01:35 2007
Thread 1 advanced to log sequence 30174
Current log# 21 seq# 30174 mem# 0: K:\ORACLE\ORADATA\APR2\REDO21A.LOG
Current log# 21 seq# 30174 mem# 1: K:\ORACLE\ORADATA\APR2\REDO21B.LOG
Wed Dec 05 00:01:35 2007
ARC1: Completed archiving log 19 thread 1 sequence 30172
Wed Dec 05 00:01:35 2007
ARC0: Evaluating archive log 20 thread 1 sequence 30173
Wed Dec 05 00:01:35 2007
ARC1: Evaluating archive log 20 thread 1 sequence 30173
ARC1: Unable to archive log 20 thread 1 sequence 30173
Wed Dec 05 00:01:35 2007
ARC0: Beginning to archive log 20 thread 1 sequence 30173
Wed Dec 05 00:01:35 2007
Log actively being archived by another process
Wed Dec 05 00:01:35 2007
Creating archive destination LOG_ARCHIVE_DEST_2: '(DESCRIPTION=(ADDRESS_LIST = (ADDRESS=(PROTOCOL=tcp)(HOST=mtm2stdb)(PORT=1521)))(CONNECT_DATA=(SID=APR2)(ORACLE_HOME=d:\oracle\ora92)(SERVER=DEDICATED)))'
Creating archive destination LOG_ARCHIVE_DEST_1: 'L:\ORACLE\ORADATA\APR2\ARCHIVE\APR2T001S30173.ARC'
ARC0: Completed archiving log 20 thread 1 sequence 30173
Thanks for any help

You can ignore this error as long as you see that completed archiving of the logsequence
you can see ARCO and ARC1 in the log
you get this error message say ARC1 when ARCO is archivhing the log

Errror in Alert.log - ksvcreate: Process() creation failed

The below error message repeats in alert.log everyday:
ksvcreate: Process() creation failed
The trace file for MMON is getting update whenever this error is reported in the alert.log. Below is the error message from the trace file:
Unable to schedule a MMON slave at: Auto Flush Main 1
Attempt to create slave process failed.
Can happen for several reasons:
- No process state objects
- Reached OS set limits
- A shutdown was going on
Check alert log for more details.
***KELR Apply Log: unable to schedule MMON Slave, error 3
I have checked the process utilisation of the database and the utilisation is well below the max. Checked on OS limits and that also is set to a high value.
Is there anyone who have received similar error message and got a resolution handy.
DB Version: 10.2.0.1
OS Version: Linux 2.6.18

hi,
do the following
SQL> show parameter process
NAME TYPE VALUE
processes integer 3000
SQL> show parameter session
NAME TYPE VALUE
sessions integer 3305
SQL> select count(*) from v$session;
COUNT(*)
2994
SELECT COUNT(*) FROM v$process;
COUNT(*)
2990
Solution
- kill processes which generates the processes ( usually from http)
- restart database

ACTIVE PROCESS PREVENTS SHUTDOWN OPERATION IN ALERT LOG

Shutdown immediate seems to be hanged for few hours.............
Alert log said that...........
ACTIVE PROCESS PREVENTS SHUTDOWN OPERATION ..........
Extract of alert_log:
SHUTDOWN: Active processes prevent shutdown operation
Thu Aug 12 11:52:59 2010
SHUTDOWN: Active processes prevent shutdown operation
Thu Aug 12 11:58:00 2010
SHUTDOWN: Active processes prevent shutdown operation
Thu Aug 12 12:03:01 2010
SHUTDOWN: Active processes prevent shutdown operation
Thu Aug 12 12:08:03 2010
SHUTDOWN: Active processes prevent shutdown operation
Thu Aug 12 12:13:04 2010
SHUTDOWN: Active processes prevent shutdown operation
Thu Aug 12 12:18:05 2010
SHUTDOWN: Active processes prevent shutdown operation
Thu Aug 12 12:23:07 2010
SHUTDOWN: Active processes prevent shutdown operation
Thu Aug 12 12:28:08 2010
SHUTDOWN: Active processes prevent shutdown operation
Thu Aug 12 12:33:09 2010
SHUTDOWN: Active processes prevent shutdown operation
Thanks in advance.......
Regards,
New2DBA

Connect sqlplus "/as sysdba" then shutdown abort Refer below metalink doc
*Getting Shutdown: Active Processes Prevent Shutdown Operation [ID 780167.1]*

Checkpoint entries in my alert log - needhelp to decipher

hi guys,
I have the following in my alert log. Can someone please help decipher to let me know why Checkpoint is not being complete?
thanks
Beginning log switch checkpoint up to RBA [0x240.2.10], SCN: 0x0000.00255e4d
Thread 1 advanced to log sequence 576
Current log# 2 seq# 576 mem# 0: /ora2/oradata/9.2.0.7/TESTDB/redoTESTDB.2a.log
Current log# 2 seq# 576 mem# 1: /ora3/oradata/9.2.0.7/TESTDB/redoTESTDB.2b.log
Thread 1 cannot allocate new log, sequence 577
Checkpoint not complete
Current log# 2 seq# 576 mem# 0: /ora2/oradata/9.2.0.7/TESTDB/redoTESTDB.2a.log
Current log# 2 seq# 576 mem# 1: /ora3/oradata/9.2.0.7/TESTDB/redoTESTDB.2b.log
Tue Sep 2 16:22:39 2008
Completed checkpoint up to RBA [0x240.2.10], SCN: 0x0000.00255e4d
Tue Sep 2 16:22:39 2008
Beginning log switch checkpoint up to RBA [0x241.2.10], SCN: 0x0000.00255ed6
Thread 1 advanced to log sequence 577
Current log# 1 seq# 577 mem# 0: /ora2/oradata/9.2.0.7/TESTDB/redoTESTDB.1a.log
Current log# 1 seq# 577 mem# 1: /ora3/oradata/9.2.0.7/TESTDB/redoTESTDB.1b.log
Tue Sep 2 16:22:46 2008
Completed checkpoint up to RBA [0x241.2.10], SCN: 0x0000.00255ed6
Tue Sep 2 16:22:48 2008
Beginning log switch checkpoint up to RBA [0x242.2.10], SCN: 0x0000.00255f57
Thread 1 advanced to log sequence 578
Current log# 2 seq# 578 mem# 0: /ora2/oradata/9.2.0.7/TESTDB/redoTESTDB.2a.log
Current log# 2 seq# 578 mem# 1: /ora3/oradata/9.2.0.7/TESTDB/redoTESTDB.2b.log
Thread 1 cannot allocate new log, sequence 579
Checkpoint not complete
Current log# 2 seq# 578 mem# 0: /ora2/oradata/9.2.0.7/TESTDB/redoTESTDB.2a.log
Current log# 2 seq# 578 mem# 1: /ora3/oradata/9.2.0.7/TESTDB/redoTESTDB.2b.log
Tue Sep 2 16:22:51 2008
Completed checkpoint up to RBA [0x242.2.10], SCN: 0x0000.00255f57

Aman.... wrote:
Oracleguy,
You switched in 3 minutes only,
Tue Sep 2 16:22:48 2008*
Beginning log switch checkpoint up to RBA http://0x242.2.10, SCN: 0x0000.00255f57
Thread 1 advanced to log sequence 578
Current log# 2 seq# 578 mem# 0: /ora2/oradata/9.2.0.7/TESTDB/redoTESTDB.2a.log
Current log# 2 seq# 578 mem# 1: /ora3/oradata/9.2.0.7/TESTDB/redoTESTDB.2b.log
Thread 1 cannot allocate new log, sequence 579
Checkpoint not complete
Current log# 2 seq# 578 mem# 0: /ora2/oradata/9.2.0.7/TESTDB/redoTESTDB.2a.log
Current log# 2 seq# 578 mem# 1: /ora3/oradata/9.2.0.7/TESTDB/redoTESTDB.2b.log
Tue Sep 2 16:22:51 2008+
Completed checkpoint up to RBA http://0x242.2.10, SCN: 0x0000.00255f57
Its pretty small time for log checkpoint to get complete. You need to make your log files bigger and add new members in them so that thereis sufficient time for checkpoint to get complete.
What's your current redo log configuration?
Aman....hi aman, did you mean 3 minutes, or 3 seconds?
I have two groups, and the log files are at 10M
thanks

Errors in alert log and listener log and "alter database mount exclusive"

Hello!
I need a help.
Database 11R2 works under MS Windows Server.
Whwn I start it using Services, according alert log it is started by command "alter database mount exclusive".
Next - alter database open.
After this, it seams that program, which should put data into database, can not work with it, because I see errors in alert log: ora-12537, 12560, 12535, 12570, 12547.
What does itmean and what to do?
This is extract from alert_log
ORACLE_BASE from environment = C:\Oracle
Mon Feb 04 14:54:53 2013
alter database mount exclusive
Successful mount of redo thread 1, with mount id 1458539517
Database mounted in Exclusive Mode
Lost write protection disabled
Completed: alter database mount exclusive
alter database open
Thread 1 opened at log sequence 3105
Current log# 3 seq# 3105 mem# 0: C:\ORACLE\ORADATA\xxx\REDO03.LOG
Successful open of redo thread 1
MTTR advisory is disabled because FAST_START_MTTR_TARGET is not set
SMON: enabling cache recovery
Successfully onlined Undo Tablespace 2.
Verifying file header compatibility for 11g tablespace encryption..
Verifying 11g file header compatibility for tablespace encryption completed
SMON: enabling tx recovery
Database Characterset is AL32UTF8
No Resource Manager plan active
Mon Feb 04 14:55:04 2013
replication_dependency_tracking turned off (no async multimaster replication found)
Starting background process QMNC
Mon Feb 04 14:55:06 2013
QMNC started with pid=20, OS id=2860
Completed: alter database open
Mon Feb 04 14:55:11 2013
Starting background process CJQ0
Mon Feb 04 14:55:11 2013
CJQ0 started with pid=25, OS id=2000
Mon Feb 04 14:55:11 2013
db_recovery_file_dest_size of 4977 MB is 0.00% used. This is a
user-specified limit on the amount of space that will be used by this
database for recovery-related files, and does not reflect the amount of
space available in the underlying filesystem or ASM diskgroup.
Mon Feb 04 15:00:29 2013
Starting background process SMCO
Mon Feb 04 15:00:29 2013
SMCO started with pid=32, OS id=3212
Edited by: kogotok1 on Feb 4, 2013 4:54 PM

Thank you.
But in the same time - when I see in alert log those error messages ora -12560, 12537,12535,12570 and so on - clients programs, whiie try to connect, hang up.
For sql plus takes 20 minutes to connect.
lsnrctl status gives the following
LSNRCTL for 64-bit Windows: Version 11.2.0.1.0 - Production on 04-FEB-2013 16:01
:46
Copyright (c) 1991, 2010, Oracle. All rights reserved.
Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=xxx-BD.mosxxx
.elektra.net)(PORT=1521)))
STATUS of the LISTENER
Alias LISTENER
Version TNSLSNR for 64-bit Windows: Version 11.2.0.1.0 - Produ
ction
Start Date 01-FEB-2013 10:22:48
Uptime 3 days 5 hr. 39 min. 54 sec
Trace Level off
Security ON: Local OS Authentication
SNMP OFF
Listener Parameter File C:\Oracle\listener.ora
Listener Log File c:\oracle\diag\tnslsnr\xxx-BD\listener\alert\l
og.xml
Listening Endpoints Summary...
(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=xxx-BD.mosxxx.elektra.net)
(PORT=1521)))
(DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(PIPENAME=\\.\pipe\EXTPROC1521ipc)))
Services Summary...
Service "CLRExtProc" has 1 instance(s).
Instance "CLRExtProc", status UNKNOWN, has 1 handler(s) for this service...
Service "XXX" has 2 instance(s).
Instance "XXX", status UNKNOWN, has 1 handler(s) for this service...
Instance "xxx", status READY, has 1 handler(s) for this service...
Service "XXXDB" has 1 instance(s).
Instance "xxx", status READY, has 1 handler(s) for this service...
The command completed successfully
To tell the truth I am confuse - I thought I have only 1 service "XXXDB" and 1 instance - "xxx".
May be I have wrong entries in tnslsnr.ora?

Cjq process related entries in alert log

Similar Messages

Maybe you are looking for