Memory warnings in alert log

Hi,
We are using Oracle Enterprise 11.2.0.3 and the dba is reporting memory warnings in the alert log on continual nightly basis over last week.
No difference in volume of data being processed or programs so not sure why this is the case - aplogioes don't have details of error to hand.
We run many processees in parallel - database set for auto-parallelism (PARALLEL_DEGREE_POLICY=AUTO) and 3rd party reporting tool relies on this for spped of reports aganist partitoned tables.
Our data loads complete fine despite these messages.
Dba has asked if we can reduce what being done during these times or reduce the number of proceses
Are there any database parameters which can be set to manage memory such that database doesn't exhaust available memory in this way.
We want the database to manage the workload automatically ( would hope via parameter tuning in partciluar of the parameters related to parallel query this would be possible).
Thanks

user5716448 wrote:
Hi,
Aplogies for delya.
Here is the message from alert log
ORA-04031: unable to allocate 512024 bytes of shared memory ("large pool","unknown object","large pool","PX msg pool")
And this is repeated many times in the log.
On IBM Power Series 7 hardware AIX operating system.
Oracle version 11.2.0.3
Any ideas to allow database to manage memory more effectively when many paralllel queries runing - tuning of parallel-related parameters - which ones?
Thanksresults when reasoning is as follows
Parallel must be faster than no parallel
higher degree of parallel must be faster than lower value.
if/when you reduce parallel activities, then this error no longer occurs.

Similar Messages

  • Memory errors in alert log

    Working on following environment:
    Platform -> Windows Server 2003 Version V5.2 Service Pack 2 32-bit
    Oracle Database -> 10.2.0.1
    My database was going to shutdown(auto) after 5 minutes of database startup. When I investigate alert log got following messages in it:
    Memory Notification: Library Cache Object loaded into SGA
    Heap size 2210K exceeds notification threshold (2048K)
    KGL object name :XDB.XDbD/PLZ01TcHgNAgAIIegtw==
    Errors in file d:\oracle10g\product\10.2.0\admin\ndb\bdump\ndb_ckpt_7024.trc:
    ORA-04030: out of process memory when trying to allocate 8716 bytes (pga heap,Get krha asynch mem)
    CKPT: terminating instance due to error 4030
    Mon Mar 14 11:05:30 2011
    Errors in file d:\oracle10g\product\10.2.0\admin\ndb\bdump\ndb_q001_5816.trc:
    ORA-04030: out of process memory when trying to allocate bytes (,)
    Then I follow metalink note 330239.1 and got the issue resolved related to "shutdown" but getting some new error messages in alert log. Please see the below error messages:
    Thread 1 cannot allocate new log, sequence 77933
    Private strand flush not complete
    Current log# 2 seq# 77932 mem# 0: D:\ORACLE10G\PRODUCT\10.2.0\ORADATA\NDB\REDO0_02.LOG
    Thread 1 advanced to log sequence 77933
    Current log# 1 seq# 77933 mem# 0: D:\ORACLE10G\PRODUCT\10.2.0\ORADATA\NDB\REDO0_01.LOG
    Mon Mar 14 12:34:08 2011
    Errors in file d:\oracle10g\product\10.2.0\admin\ndb\bdump\ndb_smon_7300.trc:
    ORA-00604: error occurred at recursive SQL level 2
    ORA-04030: out of process memory when trying to allocate 404 bytes (Typecheck,seg:kggfaAllocSeg)
    Mon Mar 14 12:49:00 2011
    Errors in file d:\oracle10g\product\10.2.0\admin\ndb\bdump\ndb_j000_7060.trc:
    ORA-12012: error on auto execute of job 27
    ORA-04030: out of process memory when trying to allocate 16428 bytes (pga heap,kgh stack)
    Mon Mar 14 12:49:34 2011
    Process startup failed, error stack:
    Mon Mar 14 12:49:35 2011
    Errors in file d:\oracle10g\product\10.2.0\admin\ndb\bdump\ndb_psp0_6908.trc:
    ORA-27300: OS system dependent operation:spcdr:9261:4200 failed with status: 997
    ORA-27301: OS failure message: Overlapped I/O operation is in progress.
    ORA-27302: failure occurred at: skgpspawn
    Mon Mar 14 12:49:35 2011
    Process J001 died, see its trace file
    Mon Mar 14 12:49:35 2011
    kkjcre1p: unable to spawn jobq slave process
    Mon Mar 14 12:49:36 2011
    Errors in file d:\oracle10g\product\10.2.0\admin\ndb\bdump\ndb_cjq0_6280.trc:
    Mon Mar 14 12:53:51 2011
    Errors in file d:\oracle10g\product\10.2.0\admin\ndb\bdump\ndb_j000_7060.trc:
    ORA-07445: exception encountered: core dump [ACCESS_VIOLATION] [unable_to_trans_pc] [PC:0x603F1A55] [ADDR:0xBB] [UNABLE_TO_READ] []
    Mon Mar 14 12:53:53 2011
    Errors in file d:\oracle10g\product\10.2.0\admin\ndb\bdump\ndb_j000_7060.trc:
    ORA-04030: out of process memory when trying to allocate 753120 bytes (pga heap,kco buffer)
    ORA-07445: exception encountered: core dump [ACCESS_VIOLATION] [unable_to_trans_pc] [PC:0x603F1A55] [ADDR:0xBB] [UNABLE_TO_READ] []
    Mon Mar 14 12:54:53 2011
    Errors in file d:\oracle10g\product\10.2.0\admin\ndb\bdump\ndb_q000_5424.trc:
    ORA-04030: out of process memory when trying to allocate 123404 bytes (QERHJ hash-joi,kllcqas:kllsltba)
    Mon Mar 14 13:21:24 2011
    Errors in file d:\oracle10g\product\10.2.0\admin\ndb\bdump\ndb_mmon_7444.trc:
    ORA-00600: internal error code, arguments: [kspcsetsp3], [], [], [], [], [], [], []
    Mon Mar 14 13:21:27 2011
    Errors in file d:\oracle10g\product\10.2.0\admin\ndb\bdump\ndb_mmon_7444.trc:
    ORA-00600: internal error code, arguments: [kmgs_parameter_update_timeout_1], [600], [], [], [], [], [], []
    ORA-00600: internal error code, arguments: [kspcsetsp3], [], [], [], [], [], [], []
    Mon Mar 14 13:22:26 2011
    Restarting dead background process MMON
    MMON started with pid=11, OS id=7304
    Mon Mar 14 13:44:51 2011
    Thread 1 advanced to log sequence 77934
    Current log# 3 seq# 77934 mem# 0: D:\ORACLE10G\PRODUCT\10.2.0\ORADATA\NDB\REDO0_03.LOG
    Mon Mar 14 13:51:20 2011
    Thread 1 advanced to log sequence 77935
    Current log# 2 seq# 77935 mem# 0: D:\ORACLE10G\PRODUCT\10.2.0\ORADATA\NDB\REDO0_02.LOG
    kindly help me out in this, as this is PRODUCTION database.
    Regards,

    Please see the parameter values extracted from the alert log:
    Adjusting the default value of parameter parallel_max_servers
    from 160 to 135 due to the value of parameter processes (150)
    Mon Mar 14 12:18:53 2011
    Starting ORACLE instance (normal)
    LICENSE_MAX_SESSION = 0
    LICENSE_SESSIONS_WARNING = 0
    Picked latch-free SCN scheme 2
    Using LOG_ARCHIVE_DEST_10 parameter default value as USE_DB_RECOVERY_FILE_DEST
    Autotune of undo retention is turned on.
    IMODE=BR
    ILAT =18
    LICENSE_MAX_USERS = 0
    SYS auditing is disabled
    ksdpec: called for event 13740 prior to event group initialization
    Starting up ORACLE RDBMS Version: 10.2.0.1.0.
    System parameters with non-default values:
    processes = 150
    sga_max_size = 1577058304
    __shared_pool_size = 125829120
    __large_pool_size = 8388608
    __java_pool_size = 8388608
    __streams_pool_size = 0
    sga_target = 1258291200
    control_files = D:\ORACLE10G\PRODUCT\10.2.0\ORADATA\NDB\CONTROL01.CTL, D:\ORACLE10G\PRODUCT\10.2.0\ORADATA\NDB\CONTROL02.CTL, D:\ORACLE10G\PRODUCT\10.2.0\ORADATA\NDB\CONTROL03.CTL
    db_block_size = 8192
    __db_cache_size = 1107296256
    compatible = 10.2.0.1.0
    db_files = 600
    db_file_multiblock_read_count= 16
    db_recovery_file_dest = d:\oracle10g\product\10.2.0/flash_recovery_area
    db_recovery_file_dest_size= 2147483648
    undo_management = AUTO
    undo_tablespace = UNDOTBS2
    kgllarge_heap_warning_threshold= 8388608
    remote_login_passwordfile= EXCLUSIVE
    db_domain =
    dispatchers = (PROTOCOL=TCP) (SERVICE=ndbXDB)
    job_queue_processes = 10
    audit_file_dest = D:\ORACLE10G\PRODUCT\10.2.0\ADMIN\NDB\ADUMP
    background_dump_dest = D:\ORACLE10G\PRODUCT\10.2.0\ADMIN\NDB\BDUMP
    user_dump_dest = D:\ORACLE10G\PRODUCT\10.2.0\ADMIN\NDB\UDUMP
    core_dump_dest = D:\ORACLE10G\PRODUCT\10.2.0\ADMIN\NDB\CDUMP
    db_name = ndb
    open_cursors = 300
    pga_aggregate_target = 838860800
    Regards,
    Edited by: user12194837 on Mar 14, 2011 3:55 AM

  • Just i notice a heap memory notification in alert.log file

    Hi,
    i notice that whenever a user exectuing a qurey this heap memory notification is coming in alert.log file.
    Memory Notification: Library Cache Object loaded into SGA
    Heap size 2294K exceeds notification threshold (2048K).
    what it is actully tell me plz.

    Duplicate post. Seems you don't want to read the replies to your previous similar question.
    geting error in alert log file
    Jaffar

  • Memory notification in Alert Log

    I'm seeing the following in my alert log. Does this mean i am running out of SGA memory? if so, How do i increase it?
    Wed Oct 22 10:10:29 2008
    Memory Notification: Library Cache Object loaded into SGA
    Heap size 2507K exceeds notification threshold (2048K)
    KGL object name :Select status from ALL_OBJECTS where object_name = :objname and object_type = :objtype and owner = :ownere
    Wed Oct 22 11:39:10 2008
    Thread 1 advanced to log sequence 11479
    Current log# 3 seq# 11479 mem# 0: /u03/oradata/psrdev/onlinelog/redo03a.log
    Current log# 3 seq# 11479 mem# 1: /u03/oradata/psrdev/onlinelog/redo03b.log
    Wed Oct 22 12:39:37 2008
    Memory Notification: Library Cache Object loaded into SGA
    Heap size 2543K exceeds notification threshold (2048K)
    KGL object name :Select owner, object_type from all_objects where object_name = :ObjName
    order by 2 DESC
    Wed Oct 22 13:46:38 2008
    Thread 1 advanced to log sequence 11480
    Current log# 1 seq# 11480 mem# 0: /u01/oradata/psrdev/onlinelog/redo01a.log
    Current log# 1 seq# 11480 mem# 1: /u01/oradata/psrdev/onlinelog/redo01b.log

    I've seen this before. Search MetaLink on "Heap size exceeds notification threshold" or "Memory Notification: Library Cache Object loaded into SGA" (both copied straight from your alert log) and see note Note:330239.1
    Metalink has an amazingly rich search. I've often found the solution to problems like this simply by copying relevant text from my alert log and pasting it into the MetaLink search field.

  • Iowait time out warnings in my alert log…

    New sqlplus connections were failing when
    Checked the alert log I see warnings…
    And some wait events in v$session_wait…
    So what could be the reason… will this be resolved if I add more redo log groups…. Or is the problem some where else if so what should I look more.
    WARNING: aiowait timed out 5 times
    Tue Feb 21 06:41:23 2006
    WARNING: aiowait timed out 4 times
    Tue Feb 21 06:48:36 2006
    WARNING: aiowait timed out 6 times
    COUNT(*) EVENT MAX(SECONDS_IN_WAIT)
    2 SQL*Net message from client 5280
    1 SQL*Net message to client 0
    4 buffer busy waits 864
    1 db file parallel write 9994
    4 enqueue 3983
    3 log file switch (checkpoint incomplete) 1393
    1 pmon timer 3
    5 rdbms ipc message 1829858

    There seems to be a serious problem with your I/O system. Check for disk corruption or known OS issues. Have you patched the OS?
    For less ideal solutions, you could try out following options:
    1-
    Set this parameter, and restart the instance
    disk_asynch_io = false
    dbwr_io_slaves=10
    2- Increase the size of Buffer cache and sort area size
    3- restart the instance
    regards.

  • Error in the alert Log

    Hi There,
    Recently I started seeing these errors in the alert log for one of the databases:
    Tue Aug 04 05:05:00 2009
    Errors in file c:\oracle\product\10.2.0\admin\xxxxxx\bdump\xxxxxx_j000_6104.trc:
    ORA-12012: error on auto execute of job 130961
    ORA-27370: job slave failed to launch a job of type EXECUTABLE
    ORA-27300: OS system dependent operation:accessing execution agent failed with status: 109
    ORA-27301: OS failure message: The pipe has been ended.
    ORA-27302: failure occurred at: sjsec 9
    ORA-27303: additional information: The pipe has been ended.
    So, I tried looking at the trace file associated with the error, and here is what I get:
    $ cat ebcd01_j000_6104.trc
    Dump file c:\oracle\product\10.2.0\admin\xxxxxx\bdump\xxxxxx_j000_6104.trc
    Tue Aug 04 05:05:00 2009
    ORACLE V10.2.0.3.0 - Production vsnsta=0
    vsnsql=14 vsnxtr=3
    Oracle Database 10g Release 10.2.0.3.0 - Production
    Windows Server 2003 Version V5.2 Service Pack 1
    CPU : 4 - type 586, 2 Physical Cores
    Process Affinity : 0x00000000
    Memory (Avail/Total): Ph:1095M/4095M, Ph+PgF:7747M/12110M, VA:1367M/2047M
    Instance name: ebcd01
    Redo thread mounted by this instance: 1
    Oracle process number: 53
    Windows thread id: 6104, image: ORACLE.EXE (J000)
    *** ACTION NAME:(DEL_ARCH_EBCP01) 2009-08-04 05:05:00.191
    *** MODULE NAME:(DBMS_SCHEDULER) 2009-08-04 05:05:00.191
    *** SERVICE NAME:(SYS$USERS) 2009-08-04 05:05:00.191
    *** SESSION ID:(871.15642) 2009-08-04 05:05:00.191
    *** 2009-08-04 05:05:00.191
    ORA-12012: error on auto execute of job 130961
    ORA-27370: job slave failed to launch a job of type EXECUTABLE
    ORA-27300: OS system dependent operation:accessing execution agent failed with status: 109
    ORA-27301: OS failure message: The pipe has been ended.
    ORA-27302: failure occurred at: sjsec 9
    ORA-27303: additional information: The pipe has been ended.
    I'm not sure what job is causing this as there is no reference and also not sure how to resolve this issue!! How can I properly trace back these errors? Any ideas or tips to what should I do?
    I'm running 10.2.0.3 database on windows 2003 server.
    Thanks

    I found the problem.. the executable job was referring to a none existing batch file..
    I have refreshed the database from production some time ago and the jobs I have setup are referring to production scripts and paths (which we didnt have on dev)..
    This is now resolved.
    Thanks

  • Oracle troubleshooting when I have no info in the alert log

    Hello everyone,
    I'm running Oracle 10g on Solaris 10. I performed a restore yesterday, and my DB instance was running smoothly. This morning I discovered that Oracle died on me "silently", that is, nothing was recorded in the alert log - the last entry in the alert log was the end of the restore.
    No Oracle processes were running anymore on the machine, trying to log in via sqlplus issued the expected
    ORA-01034: ORACLE not available
    ORA-27101: shared memory realm does not exist
    The instance is running again after rebooting the machine.
    Can I find clues about the crash, as the alert log hasn't anything for me?
    Thank you,
    Adrian

    Thank you all for your ideas.
    I looked in the /var/adm/messages (there's also /var/log/sysmsg which might be of some help) and found out that the machine was rebooted. Apparently, the Oracle instance hasn't been started properly afterwards.
    The alert log mentions (before the crash) that 'alter database open resetlogs' was performed successfully, and I ran some applications after restore that accessed the DB - the instance was indeed running.
    There is no other alert log (my attempts to bring up the DB the next day are recorded in the same file).

  • "Error in the alert log file " - please help

    Hi ALL,
    I am getting following errors in the alert log frequently.
    My database version is:
    Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - 64bi
    PL/SQL Release 10.2.0.1.0 - Production
    CORE 10.2.0.1.0 Production
    TNS for IBM/AIX RISC System/6000: Version 10.2.0.1.0 - Productio
    NLSRTL Version 10.2.0.1.0 - Production
    Thu Aug 30 16:58:19 2007
    Memory Notification: Library Cache Object loaded into SGA
    Heap size 2172K exceeds notification threshold (2048K)
    KGL object name :select object_name from all_objects where object_name='TOAD_PROFILER' and object_type='PACKAGE'
    Thu Aug 30 17:09:36 2007
    ************************************************************************************

    Additionally you can visit here:
    Alert Error from trc files--Heap size 5236K exceeds notification threshold
    geting error in alert log file
    Adith

  • Errors in alert log

    Hi,
    we have Oracle 11.2.0 standard running under Windows Xp 32
    At last time alert log is full of error? like
    Tue Dec 18 11:14:26 2012
    Errors in file c:\oracle\diag\rdbms\ \trace\ratik_j000_4448.trc:
    Errors in file c:\oracle\diag\rdbms\ \trace\ratik_j000_4448.trc:
    and Db is open and in read/write mode
    each trace file is over 4 GB size and new trace files appear and they all are like <sid>j000<>.trc
    all trace files contains following messages
    Trace file c:\oracle\diag\rdbms\ \trace\<sid>j0003300.trc
    Oracle Database 11g Release 11.2.0.1.0 - Production
    Windows XP Version V5.1 Service Pack 3
    CPU : 4 - type 586, 4 Physical Cores
    Process Affinity : 0x0x00000000
    Memory (Avail/Total): Ph:705M/2986M, Ph+PgF:3533M/6914M, VA:978M/2047M
    Instance name: ratik
    Redo thread mounted by this instance: 1
    Oracle process number: 19
    Windows thread id: 3300, image: ORACLE.EXE (J000)
    *** 2013-03-12 09:07:08.906
    *** SESSION ID:(192.5) 2013-03-12 09:07:08.906
    *** CLIENT ID:() 2013-03-12 09:07:08.906
    *** SERVICE NAME:(SYS$USERS) 2013-03-12 09:07:08.906
    *** MODULE NAME:(EM_PING) 2013-03-12 09:07:08.906
    *** ACTION NAME:(AGENT_STATUS_MARKER) 2013-03-12 09:07:08.906
    --------Dumping Sorted Master Trigger List --------
    Trigger Owner : SYSMAN
    Trigger Name : MGMT_JOB_EXEC_UPDATE
    --------Dumping Trigger Sublists --------
    trigger sublist 0 :
    trigger sublist 1 :
    Trigger Owner : SYSMAN
    Trigger Name : MGMT_JOB_EXEC_UPDATE
    trigger sublist 2 :
    trigger sublist 3 :
    trigger sublist 4 :
    what it can be and whow can I fix it?
    Thank's

    There are no ora-00600 errors not in aler not in treace file. And it is not a standby, it is a standalone Db server
    full trace files are over 4GB
    so again the alert log
    Starting ORACLE instance (normal)
    LICENSE_MAX_SESSION = 0
    LICENSE_SESSIONS_WARNING = 0
    Picked latch-free SCN scheme 2
    Using LOG_ARCHIVE_DEST_1 parameter default value as USE_DB_RECOVERY_FILE_DEST
    Autotune of undo retention is turned on.
    IMODE=BR
    ILAT =27
    LICENSE_MAX_USERS = 0
    SYS auditing is disabled
    Starting up:
    Oracle Database 11g Release 11.2.0.1.0 - Production.
    Using parameter settings in server-side spfile C:\ORACLE\PRODUCT\11.2.0\DBHOME_1\DATABASE\SPFILERATIK.ORA
    System parameters with non-default values:
    processes = 150
    nls_language = "AMERICAN"
    nls_territory = "AMERICA"
    memory_target = 1200M
    control_files = "C:\ORACLE\ORADATA\RATIK\CONTROL01.CTL"
    control_files = "C:\ORACLE\FLASH_RECOVERY_AREA\ \CONTROL02.CTL"
    Wed Mar 13 11:32:52 2013
    db_block_size = 8192
    compatible = "11.2.0.0.0"
    db_recovery_file_dest = "C:\oracle\flash_recovery_area"
    db_recovery_file_dest_size= 3852M
    undo_tablespace = "UNDOTBS1"
    max_enabled_roles = 148
    remote_login_passwordfile= "EXCLUSIVE"
    db_domain = ""
    dispatchers = "(PROTOCOL=TCP) (SERVICE=ratikXDB)"
    utl_file_dir = "*"
    job_queue_processes = 100
    audit_file_dest = "C:\ORACLE\ADMIN\ \ADUMP"
    audit_trail = "DB"
    db_name = " SID "
    open_cursors = 300
    optimizer_mode = "ALL_ROWS"
    query_rewrite_enabled = "TRUE"
    query_rewrite_integrity = "TRUSTED"
    aq_tm_processes = 1
    diagnostic_dest = "C:\ORACLE"
    Deprecated system parameters with specified values:
    Wed Mar 13 11:33:02 2013
    max_enabled_roles
    End of deprecated system parameter listing
    Wed Mar 13 11:33:03 2013
    PMON started with pid=2, OS id=2484
    Wed Mar 13 11:33:03 2013
    MMAN started with pid=9, OS id=2176
    Wed Mar 13 11:33:04 2013
    DBW0 started with pid=10, OS id=2896
    Wed Mar 13 11:33:04 2013
    SMON started with pid=13, OS id=2380
    Wed Mar 13 11:33:03 2013
    GEN0 started with pid=4, OS id=1056
    Wed Mar 13 11:33:03 2013
    DBRM started with pid=6, OS id=2188
    Wed Mar 13 11:33:04 2013
    RECO started with pid=14, OS id=3452
    Wed Mar 13 11:33:04 2013
    MMNL started with pid=16, OS id=2588
    Wed Mar 13 11:33:03 2013
    VKTM started with pid=3, OS id=2492 at elevated priority
    starting up 1 dispatcher(s) for network address '(ADDRESS=(PARTIAL=YES)(PROTOCOL=TCP))'...
    Wed Mar 13 11:33:03 2013
    DIA0 started with pid=8, OS id=2180
    starting up 1 shared server(s) ...
    Wed Mar 13 11:33:04 2013
    MMON started with pid=15, OS id=1640
    VKTM running at (10)millisec precision with DBRM quantum (100)ms
    Wed Mar 13 11:33:03 2013
    PSP0 started with pid=7, OS id=2504
    Wed Mar 13 11:33:04 2013
    CKPT started with pid=12, OS id=2544
    Wed Mar 13 11:33:04 2013
    LGWR started with pid=11, OS id=3228
    ORACLE_BASE from environment = C:\oracle
    Wed Mar 13 11:33:03 2013
    DIAG started with pid=5, OS id=2488
    Wed Mar 13 11:33:10 2013
    alter database mount exclusive
    Successful mount of redo thread 1, with mount id 327119926
    Database mounted in Exclusive Mode
    Lost write protection disabled
    Completed: alter database mount exclusive
    alter database open
    Wed Mar 13 11:33:21 2013
    Beginning crash recovery of 1 threads
    Started redo scan
    Completed redo scan
    read 463 KB redo, 146 data blocks need recovery
    Started redo application at
    Thread 1: logseq 517, block 72654
    Recovery of Online Redo Log: Thread 1 Group 1 Seq 517 Reading mem 0
    Mem# 0: C:\ORACLE\ORADATA\RATIK\REDO01.LOG
    Completed redo application of 0.35MB
    Completed crash recovery at
    Thread 1: logseq 517, block 73581, scn 11916940
    146 data blocks read, 146 data blocks written, 463 redo k-bytes read
    Wed Mar 13 11:33:32 2013
    Thread 1 advanced to log sequence 518 (thread open)
    Thread 1 opened at log sequence 518
    Current log# 2 seq# 518 mem# 0: C:\ORACLE\ORADATA\RATIK\REDO02.LOG
    Successful open of redo thread 1
    Wed Mar 13 11:33:35 2013
    SMON: enabling cache recovery
    Wed Mar 13 11:33:36 2013
    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 CL8MSWIN1251
    No Resource Manager plan active
    replication_dependency_tracking turned off (no async multimaster replication found)
    Starting background process QMNC
    Wed Mar 13 11:33:45 2013
    QMNC started with pid=20, OS id=4012
    Wed Mar 13 11:33:49 2013
    Completed: alter database open
    Wed Mar 13 11:33:56 2013
    Starting background process CJQ0
    Wed Mar 13 11:33:56 2013
    CJQ0 started with pid=22, OS id=2540
    Wed Mar 13 11:33:57 2013
    db_recovery_file_dest_size of 3852 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.
    Wed Mar 13 11:34:23 2013
    Errors in file c:\oracle\diag\rdbms\\trace\_j000_632.trc:
    Wed Mar 13 11:34:29 2013
    Trace dumping is performing id=[cdmp_20130313113429]
    Errors in file c:\oracle\diag\rdbms\\trace\_j000_632.trc:
    Wed Mar 13 11:34:39 2013
    Errors in file c:\oracle\diag\rdbms\\trace\_j000_632.trc:
    Wed Mar 13 11:34:41 2013
    Trace dumping is performing id=[cdmp_20130313113441]
    Errors in file c:\oracle\diag\rdbms\\trace\_j000_632.trc:
    Trace dumping is performing id=[cdmp_20130313113448]
    Wed Mar 13 11:34:53 2013
    Errors in file c:\oracle\diag\rdbms\k\trace\_j000_632.trc:
    Errors in file c:\oracle\diag\rdbms\\trace\_j000_632.trc:
    Wed Mar 13 11:35:01 2013
    Trace dumping is performing id=[cdmp_20130313113501]
    Errors in file c:\oracle\diag\rdbms\\trace\_j000_632.trc:
    Wed Mar 13 11:35:07 2013
    Errors in file c:\oracle\diag\rdbms\\trace\_j000_632.trc:
    Trace dumping is performing id=[cdmp_20130313113509]
    Errors in file c:\oracle\diag\rdbms\ratik\ratik\trace\ratik_j000_632.trc:
    Wed Mar 13 11:35:20 2013
    Errors in file c:\oracle\diag\rdbms\\trace\_j000_632.trc:
    Errors in file c:\oracle\diag\rdbms\\trace\_j000_632.trc:
    Errors in file c:\oracle\diag\rdbms\\trace\_j000_632.trc:
    Wed Mar 13 11:36:20 2013
    Errors in file c:\oracle\diag\rdbms\\trace\_j000_632.trc:
    Errors in file c:\oracle\diag\rdbms\\trace\_j000_632.trc:
    Errors in file c:\oracle\diag\rdbms\\trace\_j000_632.trc:
    Errors in file c:\oracle\diag\rdbms\\trace\_j000_632.trc:
    and this message goes on till server is restarted after server is up that message appear again
    in trace file
    Trace file c:\oracle\diag\rdbms\ \trace\<sid>j0003300.trc
    Oracle Database 11g Release 11.2.0.1.0 - Production
    Windows XP Version V5.1 Service Pack 3
    CPU : 4 - type 586, 4 Physical Cores
    Process Affinity : 0x0x00000000
    Memory (Avail/Total): Ph:705M/2986M, Ph+PgF:3533M/6914M, VA:978M/2047M
    Instance name: ratik
    Redo thread mounted by this instance: 1
    Oracle process number: 19
    Windows thread id: 3300, image: ORACLE.EXE (J000)
    *** 2013-03-12 09:07:08.906
    *** SESSION ID:(192.5) 2013-03-12 09:07:08.906
    *** CLIENT ID:() 2013-03-12 09:07:08.906
    *** SERVICE NAME:(SYS$USERS) 2013-03-12 09:07:08.906
    *** MODULE NAME:(EM_PING) 2013-03-12 09:07:08.906
    *** ACTION NAME:(AGENT_STATUS_MARKER) 2013-03-12 09:07:08.906
    --------Dumping Sorted Master Trigger List --------
    Trigger Owner : SYSMAN
    Trigger Name : MGMT_JOB_EXEC_UPDATE
    --------Dumping Trigger Sublists --------
    trigger sublist 0 :
    trigger sublist 1 :
    Trigger Owner : SYSMAN
    Trigger Name : MGMT_JOB_EXEC_UPDATE
    trigger sublist 2 :
    trigger sublist 3 :
    trigger sublist 4 :
    *** 2013-03-12 09:07:14.046
    oer 8102.3 - obj# 86174, rdba: 0x00810e2c(afn 2, blk# 69164)
    kdk key 8102.3:
    ncol: 8, len: 47
    key: (47):
    01 80 05 41 44 4d 34 36 02 c1 02 0b 78 70 0a 10 08 2c 32 28 f2 c9 c0 02 c1
    04 01 80 01 80 10 c0 89 b8 fe e0 85 45 5a 8d 44 5f 2f 1c b6 ea bb
    mask: (2048):
    05 09 80 54 00 00 00 00 00 4c 00 00 00 88 70 9e 3e 00 00 00 00 00 00 00 00
    40 00 00 00 c8 78 34 0d 94 d1 aa 06 a0 03 8d 0b 00 00 00 00 ed d4 aa 06 9c
    70 9e 3e 00 00 00 00 38 00 00 00 0d 00 00 00 01 00 00 00 03 00 00 00 01 00
    00 00 00 00 00 00 00 00 00 00 00 00 00 00 a0 79 9e 3e 00 00 00 00 ed d4 aa
    06 e8 70 9e 3e 00 00 00 00 38 00 00 00 00 00 00 00 38 00 00 00 00 00 00 00
    4c 00 00 00 00 00 00 00 9c 70 9e 3e 00 00 00 00 00 00 00 00 14 00 00 00 00
    40 00 00 00 00 00 00 a0 79 9e 3e 6c 00 00 00 c8 1c e4 3e 68 b6 3d 0d 7c 79
    34 0d fc f5 c4 62 a0 03 8d 0b a0 79 9e 3e 38 00 00 00 ff ff ff 7f 00 00 00
    00 00 00 00 00 00 40 00 01 00 00 00 00 38 ca f4 62 00 00 00 00 00 00 00 00
    00 00 00 00 02 00 00 00 02 00 00 00 02 00 00 00 00 00 00 00 00 00 00 00 00
    00 00 00 c4 b0 3d 0d 08 76 9e 3e 16 00 00 00 f0 1c e4 3e 00 00 00 00 64 81
    34 0d 00 00 00 00 44 79 34 0d 8c 2c 20 07 17 00 00 00 c4 b0 3d 0d 4c 79 34
    0d 28 23 ea 06 5c 79 34 0d 8c 2c 20 07 17 00 00 00 c4 b0 3d 0d 64 79 34 0d
    28 23 ea 06 b4 79 34 0d a5 d2 ec 62 5c 88 34 0d 80 79 34 0d 8c 2c 20 07 17
    00 00 00 6c 00 00 00 88 79 34 0d 28 23 ea 06 ac 79 34 0d 58 14 cd 62 08 76
    9e 3e a0 03 8d 0b 00 00 00 00 00 00 00 00 02 00 00 00 0c 7e 34 0d c4 b0 3d
    0d 80 ff 8c 0b 6c 00 00 00 d4 79 34 0d 36 a4 c2 62 c8 1c e4 3e 06 00 00 00
    0c 7e 34 0d 02 00 00 00 84 00 00 00 c4 b0 3d 0d 10 7e 34 0d ef 5f 3b 02 c8
    1c e4 3e 06 00 00 00 0c 7e 34 0d 02 00 00 00 84 00 00 00 c4 b0 3d 0d 06 00
    00 00 40 7e 34 0d 02 00 00 00 84 00 00 00 c4 b0 3d 0d 44 7e 34 0d ef 5f 3b
    and those memory blocks till the end of log file
    NO SR is raised.

  • Oracle errors in alert.log

    Hello guys,
    I have the following Oracle Release 10.2.0.1.0 server configuration:
    - Windows 2003 Server SP2
    - 3,25 GB RAM (I think that is a 4 GB but this is a windows 2003 standard edition)
    - 2 Intel Xeon Quad core
    - 3 disk partitions (C -> 40GB, 25 GB free / E -> 100 GB 85 GB free / F 300 GB -> 270 GB free)
    The PRISM instance configuration is:
    Archivelog: TRUE
    SGA Size: 584 MB
    Actual PGA Size: 40 MB
    Services running (OracleDBConsolePRISM, OracleOraDb10g_home1TNSListener, OracleServeicePRISM)
    The problem is that there are just 5 users that use this database, but there are a lot of errors in the alert.log that makes the database not available, the error messages are like this:
    Mon Feb 16 16:31:24 2009
    Errors in file e:\oracle\product\10.2.0\admin\prism\bdump\prism_j001_11416.trc:
    ORA-12012: error on auto execute of job 42567
    ORA-00376: file ORA-00376: file 3 cannot be read at this time
    ORA-01110: data file 3: 'E:\ORACLE\PRODUCT\10.2.0\ORADATA\PRISM\SYSAUX01.DBF'
    ORA-06512: at "EXFSYS.DBMS_RLMGR_DR", line 15
    ORA-06512: at line 1
    cannot be read at this timeThe content of prism_j001_11416.trc is:
    Dump file e:\oracle\product\10.2.0\admin\prism\bdump\prism_mmon_4620.trc
    Mon Feb 16 11:07:33 2009
    ORACLE V10.2.0.1.0 - Production vsnsta=0
    vsnsql=14 vsnxtr=3
    Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Production
    With the Partitioning, OLAP and Data Mining options
    Windows Server 2003 Version V5.2 Service Pack 2
    CPU                 : 8 - type 586, 2 Physical Cores
    Process Affinity    : 0x00000000
    Memory (Avail/Total): Ph:1981M/3325M, Ph+PgF:3612M/5221M, VA:1278M/2047M
    Instance name: prism
    Redo thread mounted by this instance: 1
    Oracle process number: 11
    Windows thread id: 4620, image: ORACLE.EXE (MMON)
    *** SERVICE NAME:(SYS$BACKGROUND) 2009-02-16 11:07:33.480
    *** SESSION ID:(161.1) 2009-02-16 11:07:33.480
    KEWRCTLRD: OCIStmtFetch Error. ctl_dbid= 1515633963, sga_dbid= 1515633963
    KEWRCTLRD: Retcode: -1, Error Message: ORA-00376: file 3 cannot be read at this time
    ORA-01110: data file 3: 'E:\ORACLE\PRODUCT\10.2.0\ORADATA\PRISM\SYSAUX01.DBF'
      *** SQLSTR: total-len=328, dump-len=240,
          STR={select snap_interval, retention,most_recent_snap_time, most_recent_snap_id, status_flag, most_recent_purge_time, most_recent_split_id, most_recent_split_time, mrct_snap_time_num, mrct_purge_time_num, snapint_num, retention_num, swrf_version}
    *** kewrwdbi_1: Error=13509 encountered during run_once
    keaInitAdvCache: failed, err=604
    02/16/09 11:07:33 >ERROR: exception at dbms_ha_alerts_prvt.post_instance_up308: SQLCODE -13917,ORA-13917: Posting system
    alert with reason_id 135 failed with code [5] [post_error]
    02/16/09 11:07:33 >ERROR: exception at dbms_ha_alerts_prvt.check_ha_resources637: SQLCODE -13917,ORA-13917: Posting syst
    em alert with reason_id 136 failed with code [5] [post_error]
    02/16/09 11:07:33 >parameter dump for dbms_ha_alerts_prvt.check_ha_resources
    02/16/09 11:07:33 > - local_db_unique_name (PRISM)
    02/16/09 11:07:33 > - local_db_domain (==N/A==)
    02/16/09 11:07:33 > - rows deleted (0)
    02/16/09 11:07:33 >ERROR: exception at dbms_ha_alerts_prvt.check_ha_resources637: SQLCODE -13917,ORA-13917: Posting syst
    em alert with reason_id 136 failed with code [5] [post_error]
    02/16/09 11:07:33 >parameter dump for dbms_ha_alerts_prvt.check_ha_resources
    02/16/09 11:07:33 > - local_db_unique_name (PRISM)
    02/16/09 11:07:33 > - local_db_domain (==N/A==)
    02/16/09 11:07:33 > - rows deleted (0)
    *** 2009-02-16 11:07:41.293
    ****KELR Apply Log Failed, return code 376
    *** 2009-02-16 11:08:35.294
    ****KELR Apply Log Failed, return code 376
    *** 2009-02-16 11:09:38.294
    ****KELR Apply Log Failed, return code 376
    *** 2009-02-16 11:10:41.295
    ****KELR Apply Log Failed, return code 376
    *** 2009-02-16 11:11:44.296
    ****KELR Apply Log Failed, return code 376
    *** 2009-02-16 11:12:29.328And this is an extract from listener.log file:
    TNSLSNR for 32-bit Windows: Version 10.2.0.1.0 - Production on 16-FEB-2009 11:05:44
    Copyright (c) 1991, 2005, Oracle.  All rights reserved.
    System parameter file is e:\oracle\product\10.2.0\db_1\network\admin\listener.ora
    Log messages written to e:\oracle\product\10.2.0\db_1\network\log\listener.log
    Trace information written to e:\oracle\product\10.2.0\db_1\network\trace\listener.trc
    Trace level is currently 0
    Started with pid=9212
    Listening on: (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=akscl-mfs15.am.enterdir.com)(PORT=1521)))
    Listener completed notification to CRS on start
    TIMESTAMP * CONNECT DATA [* PROTOCOL INFO] * EVENT [* SID] * RETURN CODE
    16-FEB-2009 11:07:25 * service_register * prism * 0
    16-FEB-2009 11:07:31 * service_update * prism * 0
    16-FEB-2009 11:07:34 * service_update * prism * 0
    16-FEB-2009 11:07:37 * service_update * prism * 0
    16-FEB-2009 11:07:57 * (CONNECT_DATA=(SERVER=DEDICATED)(SERVICE_NAME=PRISM)(CID=(PROGRAM=\\akscl-mfs15\PRISMPM\PRISMPM.EXE)(HOST=xx-W20972)(USER=CSC3157))) * (ADDRESS=(PROTOCOL=tcp)(HOST=144.180.225.7)(PORT=1607)) * establish * PRISM * 0
    16-FEB-2009 11:07:58 * service_update * prism * 0
    16-FEB-2009 11:07:58 * (CONNECT_DATA=(SERVER=DEDICATED)(SERVICE_NAME=PRISM)(CID=(PROGRAM=\\akscl-mfs15\PRISMPM\PRISMPM.EXE)(HOST=xx-W20972)(USER=CSC3157))) * (ADDRESS=(PROTOCOL=tcp)(HOST=144.180.225.7)(PORT=1608)) * establish * PRISM * 0
    16-FEB-2009 11:07:58 * (CONNECT_DATA=(SERVER=DEDICATED)(SERVICE_NAME=PRISM)(CID=(PROGRAM=\\akscl-mfs15\PRISMPM\PRISMPM.EXE)(HOST=xx-W20972)(USER=CSC3157))) * (ADDRESS=(PROTOCOL=tcp)(HOST=144.180.225.7)(PORT=1612)) * establish * PRISM * 0
    16-FEB-2009 11:07:59 * (CONNECT_DATA=(SERVER=DEDICATED)(SERVICE_NAME=PRISM)(CID=(PROGRAM=\\akscl-mfs15\PRISMPM\PRISMPM.EXE)(HOST=xx-W20972)(USER=CSC3157))) * (ADDRESS=(PROTOCOL=tcp)(HOST=144.180.225.7)(PORT=1613)) * establish * PRISM * 0
    16-FEB-2009 11:07:59 * (CONNECT_DATA=(SERVER=DEDICATED)(SERVICE_NAME=PRISM)(CID=(PROGRAM=\\akscl-mfs15\PRISMPM\PRISMPM.EXE)(HOST=xx-W20972)(USER=CSC3157))) * (ADDRESS=(PROTOCOL=tcp)(HOST=144.180.225.7)(PORT=1614)) * establish * PRISM * 0
    16-FEB-2009 11:08:01 * service_update * prism * 0
    16-FEB-2009 15:05:26 * (CONNECT_DATA=(SERVICE_NAME=PRISM)(CID=(PROGRAM=C:\Program Files\Microsoft Office\OFFICE11\EXCEL.EXE)(HOST=xx-W21498)(USER=csc2682))) * (ADDRESS=(PROTOCOL=tcp)(HOST=144.180.227.131)(PORT=1999)) * establish * PRISM * 0
    16-FEB-2009 15:05:27 * (CONNECT_DATA=(SERVICE_NAME=PRISM)(CID=(PROGRAM=C:\Program Files\Microsoft Office\OFFICE11\EXCEL.EXE)(HOST=xx-W21498)(USER=csc2682))) * (ADDRESS=(PROTOCOL=tcp)(HOST=144.180.227.131)(PORT=2000)) * establish * PRISM * 0
    16-FEB-2009 17:33:26 * (CONNECT_DATA=(CID=(PROGRAM=)(HOST=__jdbc__)(USER=))(SERVICE_NAME=PRISM)) * (ADDRESS=(PROTOCOL=tcp)(HOST=144.180.227.18)(PORT=2513)) * establish * PRISM * 0
    16-FEB-2009 17:33:26 * (CONNECT_DATA=(CID=(PROGRAM=)(HOST=__jdbc__)(USER=))(SERVICE_NAME=PRISM)) * (ADDRESS=(PROTOCOL=tcp)(HOST=144.180.227.18)(PORT=2514)) * establish * PRISM * 0
    16-FEB-2009 17:33:27 * (CONNECT_DATA=(CID=(PROGRAM=)(HOST=__jdbc__)(USER=))(SERVICE_NAME=PRISM)) * (ADDRESS=(PROTOCOL=tcp)(HOST=144.180.227.18)(PORT=2515)) * establish * PRISM * 0
    16-FEB-2009 17:33:27 * (CONNECT_DATA=(CID=(PROGRAM=)(HOST=__jdbc__)(USER=))(SERVICE_NAME=PRISM)) * (ADDRESS=(PROTOCOL=tcp)(HOST=144.180.227.18)(PORT=2516)) * establish * PRISM * 0
    16-FEB-2009 17:33:27 * (CONNECT_DATA=(CID=(PROGRAM=)(HOST=__jdbc__)(USER=))(SERVICE_NAME=PRISM)) * (ADDRESS=(PROTOCOL=tcp)(HOST=144.180.227.18)(PORT=2517)) * establish * PRISM * 0
    16-FEB-2009 17:33:27 * (CONNECT_DATA=(CID=(PROGRAM=)(HOST=__jdbc__)(USER=))(SERVICE_NAME=PRISM)) * (ADDRESS=(PROTOCOL=tcp)(HOST=144.180.227.18)(PORT=2518)) * establish * PRISM * 0
    16-FEB-2009 17:33:27 * (CONNECT_DATA=(CID=(PROGRAM=)(HOST=__jdbc__)(USER=))(SERVICE_NAME=PRISM)) * (ADDRESS=(PROTOCOL=tcp)(HOST=144.180.227.18)(PORT=2519)) * establish * PRISM * 0
    16-FEB-2009 17:33:27 * (CONNECT_DATA=(CID=(PROGRAM=)(HOST=__jdbc__)(USER=))(SERVICE_NAME=PRISM)) * (ADDRESS=(PROTOCOL=tcp)(HOST=144.180.227.18)(PORT=2520)) * establish * PRISM * 0
    16-FEB-2009 17:33:27 * (CONNECT_DATA=(CID=(PROGRAM=)(HOST=__jdbc__)(USER=))(SERVICE_NAME=PRISM)) * (ADDRESS=(PROTOCOL=tcp)(HOST=144.180.227.18)(PORT=2521)) * establish * PRISM * 0
    16-FEB-2009 17:33:27 * (CONNECT_DATA=(CID=(PROGRAM=)(HOST=__jdbc__)(USER=))(SERVICE_NAME=PRISM)) * (ADDRESS=(PROTOCOL=tcp)(HOST=144.180.227.18)(PORT=2523)) * establish * PRISM * 0
    16-FEB-2009 17:33:27 * (CONNECT_DATA=(CID=(PROGRAM=)(HOST=__jdbc__)(USER=))(SERVICE_NAME=PRISM)) * (ADDRESS=(PROTOCOL=tcp)(HOST=144.180.227.18)(PORT=2524)) * establish * PRISM * 0
    16-FEB-2009 17:33:27 * (CONNECT_DATA=(CID=(PROGRAM=)(HOST=__jdbc__)(USER=))(SERVICE_NAME=PRISM)) * (ADDRESS=(PROTOCOL=tcp)(HOST=144.180.227.18)(PORT=2525)) * establish * PRISM * 0
    16-FEB-2009 17:33:27 * (CONNECT_DATA=(CID=(PROGRAM=)(HOST=__jdbc__)(USER=))(SERVICE_NAME=PRISM)) * (ADDRESS=(PROTOCOL=tcp)(HOST=144.180.227.18)(PORT=2526)) * establish * PRISM * 0
    16-FEB-2009 17:33:27 * (CONNECT_DATA=(CID=(PROGRAM=)(HOST=__jdbc__)(USER=))(SERVICE_NAME=PRISM)) * (ADDRESS=(PROTOCOL=tcp)(HOST=144.180.227.18)(PORT=2527)) * establish * PRISM * 0
    16-FEB-2009 17:33:27 * (CONNECT_DATA=(CID=(PROGRAM=)(HOST=__jdbc__)(USER=))(SERVICE_NAME=PRISM)) * (ADDRESS=(PROTOCOL=tcp)(HOST=144.180.227.18)(PORT=2528)) * establish * PRISM * 0
    16-FEB-2009 17:33:27 * (CONNECT_DATA=(CID=(PROGRAM=)(HOST=__jdbc__)(USER=))(SERVICE_NAME=PRISM)) * (ADDRESS=(PROTOCOL=tcp)(HOST=144.180.227.18)(PORT=2529)) * establish * PRISM * 0
    16-FEB-2009 17:33:27 * (CONNECT_DATA=(CID=(PROGRAM=)(HOST=__jdbc__)(USER=))(SERVICE_NAME=PRISM)) * (ADDRESS=(PROTOCOL=tcp)(HOST=144.180.227.18)(PORT=2530)) * establish * PRISM * 0
    16-FEB-2009 17:33:29 * service_update * prism * 0Please need help to solve this issue, best regards.

    Hello guys,
    Thanks for the tips, after checking the tablespaces the results are:
    SQL> select tablespace_name,status from dba_tablespaces;
    TABLESPACE_NAME                STATUS
    SYSTEM                         ONLINE
    UNDOTBS1                       ONLINE
    SYSAUX                         ONLINE
    TEMP                           ONLINE
    USERS                          ONLINE
    PRISM                          ONLINEThe datafiles:
    SQL> select file#,name,status,enabled from v$datafile;
    FILE#         NAME                                        STATUS  ENABLED
             1     E:\ORACLE\PRODUCT\10.2.0\ORADATA\PRISM\SYSTEM01.DBF          SYSTEM  READ WRITE
             2     E:\ORACLE\PRODUCT\10.2.0\ORADATA\PRISM\UNDOTBS01.DBF          ONLINE  READ WRITE
             3     E:\ORACLE\PRODUCT\10.2.0\ORADATA\PRISM\SYSAUX01.DBF          *RECOVER* READ WRITE
             4     E:\ORACLE\PRODUCT\10.2.0\ORADATA\PRISM\USERS01.DBF          ONLINE  READ WRITE
             5     F:\ORACLE\PRISM\PRISM.ORA                         ONLINE  READ WRITESo, following the metalink guide:
    SQL> recover datafile 'E:\ORACLE\PRODUCT\10.2.0\ORADATA\PRISM\SYSAUX01.DBF';  -->Here the system ask for the log file, I select AUTO
    SQL> alter database datafile 'E:\ORACLE\PRODUCT\10.2.0\ORADATA\PRISM\SYSAUX01.DBF' online; Now the datafiles are all ONLINE, I will wait some time to check the database behavior after this change and back with the results and correct answer, best regards.

  • Database Generating Errors in Alert Log

    Hie,
    my db is generating errors in the alert log
    Errors in file /export/home/app/oracle/diag/rdbms/ORACLE_SID/ORACLE_SID/trace/ORACLE_SID_j000_15845.trc (incident=44144):
    ORA-00600: internal error code, arguments: [kdsgrp1], [], [], [], [], [], [], [], [], [], [], []
    ORA-00001: unique constraint (SYSMAN.PK_MGMT_JOB_EXECUTION) violated
    DDE: Problem Key 'ORA 600 [13011]' was completely flood controlled (0x4)
    Further messages for this problem key will be suppressed for up to 10 minutes
    looking forward to your assistance
    Mike

    Tue May 22 12:55:56 2012
    Adjusting the default value of parameter parallel_max_servers
    from 960 to 285 due to the value of parameter processes (300)
    Starting ORACLE instance (normal)
    Tue May 22 13:00:16 2012
    Adjusting the default value of parameter parallel_max_servers
    from 960 to 285 due to the value of parameter processes (300)
    Starting ORACLE instance (normal)
    LICENSE_MAX_SESSION = 0
    LICENSE_SESSIONS_WARNING = 0
    Shared memory segment for instance monitoring created
    Picked latch-free SCN scheme 3
    Using LOG_ARCHIVE_DEST_1 parameter default value as /export/home/app/oracle/product/11.2.0/dbhome_1/dbs/arch
    Autotune of undo retention is turned on.
    IMODE=BR
    ILAT =52
    LICENSE_MAX_USERS = 0
    SYS auditing is disabled
    Starting up:
    Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production
    With the Partitioning, OLAP, Data Mining and Real Application Testing options.
    ORACLE_HOME = /export/home/app/oracle/product/11.2.0/dbhome_1
    System name:     SunOS
    Node name:     server_1
    Release:     5.10
    Version:     Generic_141445-09
    Machine:     i86pc

  • Multiple ORA-27300, ORA-27301 and ORA-27302 in alert log

    Hello all,
    Looking for some guidance with a 10.2.0.1 database on Windows 2003 Enterprise Edition server. I have an SR open with Oracle, but getting the usual run-around and no conclusive explanations.
    A couple of weeks ago, the database started throwing the following in the alert log:
    Errors in file d:\oracle\admin\hdprd\bdump\hdprd_cjq0_404.trc:
    ORA-27300: OS system dependent operation:WaitForSingleObject failed with status: 0
    ORA-27301: OS failure message: The operation completed successfully.
    ORA-27302: failure occurred at: sssxcpttcs5
    Checking the trace file shows:
    *** 2011-03-22 17:37:21.391
    *** SERVICE NAME:(SYS$BACKGROUND) 2011-03-22 17:36:53.890
    *** SESSION ID:(327.1) 2011-03-22 17:36:53.890
    Waited for process J000 to initialize for 60 seconds
    *** 2011-03-22 17:37:21.391
    Dumping diagnostic information for J000:
    OS tid = 3620
    Memory (Avail/Total): Ph:6548M/8190M, Ph+PgF:10684M/12074M, VA:994M/2047M
    CPU Load: 5%
    ------------------- Call Stack Trace ---------------------
    calling location entry point arg #1 arg #2 arg #3 arg #4
    7C82847C 00000000 00000000 00000000 00000000 00000000
    77E41A89 77E64849 00000000 00000000 00000000 00000000
    _slxefo+154                                                      00000000                                                         00000000 00000000 00000000 00000000
    slxcfot+805                                                     slxefo+0 00000000 00000000 00000000 00000000
    lxlfopn+128                                                     slxcfot+0 412dd744 412dd98c 60b2c20c 60b2c208
    lxldlod+56                                                      lxlfopn+0 60b382dc 412dd98c 00000000 00000000
    _lxdlobj+79                                                      00000000                                                         60b382dc 412dd98c 0a4957f0 00000001
    lxdgetobj+187                                                   lxdlobj+0 00000001 00000000 0a49df34 00000000
    lxplset+49                                                      lxdgetobj+0 00000000 00000000 00000000 00000000
    lxhLaToId+146                                                   lxplset+0 00000001 0a49dd14 0a49df34 00000000
    lxhenvquery+197                                                 lxhLaToId+0 00000000 00000000 00000000 00000000
    lxhLangEnv+352                                                  lxhenvquery+0 00000000 00000000 00000000 00000000
    62747F74 62765084 0a49dd14 00000000 0a49df34 0a49df34
    60987803 60A35104 00000000 00000000 00000000 00000000
    60986EEE 60986EFC 3b512c78 412df6b4 412dfd84 00000100
    6098798C 60986ED8 3b512c78 412df6b4 412dfd84 00000100
    npinli+78                                                       nlstdgo+0 00000000 00000000 00000000 00000000
    opiinit+142                                                     npinli+0 00000001 00000000 00000000 00000000
    opimaireal+194 _opiinit+0                                                       00000000 00000000 00000000 00000000
    opimai+92                                                       opimai_real+0 00000003 412dfeec 00000000 00000000
    BackgroundThreadStart@4+422                                     opimai+0 00000000 00000000 00000000 00000000
    77E6482C 00000000 00000000 00000000 00000000 00000000
    ---------------- End of Call Stack Trace -----------------
    Call stack acquisition performance stats:
    setup time (lock acquis., memory alloc.): 0 ms
    frame get time (time the target proc was suspended): 0 ms
    symbol translation time: 157 ms
    total time: 157 ms
    The database remains functional while this is happening, but we are no longer able to establish new sessions to the database. The only remedy so far, as is the case with most Windows issues, is to reboot the server. The support analyst has recommended that we add the "/3gb" switch to the boot.ini as he feels we are hitting the 2GB limitation for a single process. My concern is that in looking at the trace file, it would appear that there's only around 1.6GB of memory consumed in total on the server (8190M - 6548M = 1642M), so there should be no single process that's coming even close to the 2GB limitation. I've been watching the oracle.exe process for the last week, and it always hovers around 700M. The total SGA size is about 600M.
    Interestingly enough, we're in the process of downgrading the database from Enterprise Edition to Standard edition and on the development server, we've currently got the old 10.2.0.1 EE database and the new 10.2.0.5 SE database running concurrently. The EE version has encountered the same issue described above, while the SE version has not.
    My other problem is that I work in the pharmaceutical industry and this is a heavily regulated database and I cannot make arbitrary changes to databases/servers without evidence to support the change.
    Any Oracle/Windows experts out there that can shed some light on this problem?
    Thanks

    Thanks to both of you for the speedy response. I have already seen that article, as well as 790397.1 - PROCESS J000 And M000 Die [ID 790397.1]. I'm just a little confused as to why Oracle is saying it's an out of memory condition when there's nothing in the log or trace files (other than the condition matches a couple of articles they have) that support the conclusion. Don't get me wrong, I'm certainly not an Oracle on Windows expert, most of my stuff revolves around Linux/UNIX and I avoid anything windows like the plague, other than starting a putty session.
    My understanding is that each process in a windows 32bit environment gets a 4GB Virtual Address Space, which is split into a lower 2GB application space and an upper 2GB kernel space. If the trace file is showing that only 1.6GB of physical memory has been consumed, wouldn't this indicate that there isn't a single process on the server that is even close to reaching it's 2GB limitation?

  • "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.

  • Thread 1 cannot allocate new log -- from alert log

    in my alert log file, I have noticed occasionally that this message was showing out during the business hour (8 am ~ 8 pm). Not often , maybe 3 or 4 times, but there are more during the midnight when system run some administration process such as KGL object name :SELECT /*+rule*/ SYS_XMLGEN(VALUE(KU$), XMLFORMAT.createFormat2('VIEW_T', '7')), KU$.OBJ_NUM ,K
    U$.SCHEMA_OBJ.NAME ,KU$.SCHEMA_OBJ.NAME ,'VIEW' ,KU$.SCHEMA_OBJ.OWNER_NAME FROM SYS.KU$_VIEW_VIEW KU$ WHERE KU$
    .OBJ_NUM IN (SELECT * FROM TABLE(DBMS_METADATA.FETCH_OBJNUMS(200001)))
    . My question is : Do I have to add another redo log file to system? and how much is proper?
    I also noticed there where message of "Memory Notification: Library Cache Object loaded into SGA
    Heap size 2829K exceeds notification threshold (2048K)" during that hours. Appreciate any advice. my system is 10g r2 on AIX 5.3 L.

    The "Thread cannot allocate new log" occurs more often off the regular hours due to system run process. It seems more regular occurring at evry 20 minutes. By OEM, I noticed thate there some system processes run at 2 am, 8 am, 2 pm, 8pm. for examples
    1) EMD_MAINTENANCE.EXECUTE_EM_DBMS_JOB_PROCS();
    2) MGMT_ADMIN_DATA.EVALUATE_MGMT_METRICS;
    3) SELECT /*+ USE_HASH(f a) */ SUM(NVL(F.BYTES - NVL(A.BYTES, 0), 0)/1024/1024), SUM(NVL(F.BYTES, 0)/1024/1024) FROM (SELECT DISTINCT TABLESPACE_NAME FROM USER_TABLES) U, (SELECT TABLESPACE_NAME, SUM(BYTES) BYTES FROM DBA_DATA_FILES GROUP BY TABLESPACE_NAME) F, (SELECT TABLESPACE_NAME, SUM(BYTES) BYTES FROM DBA_FREE_SPACE GROUP BY TABLESPACE_NAME) A WHERE A.TABLESPACE_NAME = U.TABLESPACE_NAME AND F.T...
    I wonder why they are necessary? or I have to ad one more redo log.

  • Alert log ---Thread 1 cannot allocate new log, sequence 1697

    数据库环境为:AIX 6.1,Oracle 10.2.0.1 64位,今天在查看oracle alert log时发现如下信息
    Sun Apr 29 16:03:43 2012
    Thread 1 cannot allocate new log, sequence 8
    Checkpoint not complete
    Current log# 3 seq# 7 mem# 0: /oradata/hb/redo03.log
    Thread 1 advanced to log sequence 8
    Current log# 1 seq# 8 mem# 0: /oradata/hb/redo01.log
    Sun Apr 29 17:28:02 2012
    Thread 1 advanced to log sequence 9
    Current log# 2 seq# 9 mem# 0: /oradata/hbbredo02.log
    Sun Apr 29 19:10:39 2012
    Thread 1 advanced to log sequence 10
    Current log# 3 seq# 10 mem# 0: /oradata/hb/redo03.log
    Sun Apr 29 21:23:34 2012
    Thread 1 advanced to log sequence 11
    Current log# 1 seq# 11 mem# 0: /oradata/hb/redo01.log
    Sun Apr 29 22:09:31 2012
    Thread 1 cannot allocate new log, sequence 12
    Private strand flush not complete
    Current log# 1 seq# 11 mem# 0: /oradata/hb/redo01.log
    Thread 1 advanced to log sequence 12
    Current log# 2 seq# 12 mem# 0: /oradata/hb/redo02.log
    Thread 1 advanced to log sequence 13
    Current log# 3 seq# 13 mem# 0: /oradata/hb/redo03.log
    Mon Apr 30 06:15:20 2012
    Thread 1 advanced to log sequence 14
    Current log# 1 seq# 14 mem# 0: /oradata/hb/redo01.log
    Mon Apr 30 10:04:39 2012
    Memory Notification: Library Cache Object loaded into SGA
    Heap size 2919K exceeds notification threshold (2048K)
    SQL> select * from v$logfile;
    GROUP# STATUS TYPE
    MEMBER
    IS_
    1 ONLINE
    /oradata/hb/redo01.log
    NO
    2 ONLINE
    /oradata/hb/redo02.log
    NO
    GROUP# STATUS TYPE
    MEMBER
    IS_
    3 ONLINE
    /oradata/hb/redo03.log
    NO
    数据库当前运行正常,请教一下,
    1. 频繁出现的类似
    Thread 1 cannot allocate new log, sequence 12
    Private strand flush not complete
    Current log# 1 seq# 11 mem# 0: /oradata/hb/redo01.log 是怎么造成的?是否需要处理,如果处理,该怎么做?
    2。 Memory Notification: Library Cache Object loaded into SGA
    Heap size 2919K exceeds notification threshold (2048K)显示heap 值超过设定的阀值,heap起什么作用,是否需要修改阀值,以消除这一"Memory Notification"?

    Thread 1 cannot allocate new log, sequence 12
    Private strand flush not complete
    由"Private strand flush not complete"引起的 cannot allocate new log一般可以忽略, Private strand是10g引入的新特性
    Heap size 2919K exceeds notification threshold (2048K)
    该信息是由于 10.2.0.1 这个版本的默认 "_kgl_large_heap_warning_threshold" 参数过小, 一般可以忽略。
    调整个 "_kgl_large_heap_warning_threshold" 参数和 升级到10.2.0.1 版本均可以 让该"Heap size 2919K exceeds notification threshold (2048K)"信息不再出现, 当然一般也可以忽略该问题

Maybe you are looking for

  • Error message from libreoffice

    If I launch Libreoffice from a terminal, I get tons of messages like that: Lookup Table Format4: specific interpretation needed! It does not seems to affect the functioning of Libreoffice at all but anyway does anybody has an idea of what is it about

  • Need help in customizing an identity provider using SPI

    We are customizing the sample identity provider in note 1194815.1 . We were able to assign tasks to users but the problem is whenever we assign a task to a group, the task does not appear in group members job basket. No exceptions or errors thrown.

  • HT201335 I can only get audio when using airplay through sky go on my apple tv on iphone 4

    I cn only get audio when using airplay through sky go on my apple tv on iphone4. Any ideas?

  • Workflow to be set to ERROR Mode

    Hi, We have a requirement where we should set the STATUS of the current workflow to ERROR mode explicitly based on certain Condition. Actually I am using a EXPRESSION as the agent for an ACTIVITY STEP which contains the POSITION ID. Well, now, if I a

  • Printing process in background

    hi is there any way of printing an open document in acrobat in background like indesign has export to pdf so i dont have to watch the cancel button? regards