Message in alert log file during the startup of the DB

Hi,
i have two instances, i have the same warning in the alert log file during the startup of the DB:
Oracle instance running on a system with low open file descriptor limit.
Tune your system to increase this limit to avoid severe performance degradation.
The db_files parameter was at 1024 for the two instances, i have set it to 300 for the first instance and 550 for second, the message for the first instance was droped(it's ok), but the message was there in the alert log for the second instance.
The two instance are on the same machine.
The number of the open file limit on the linux machine is equal to 1024.
I have shutdown the first instance (with db_files=300) the problem persits for the second instance (with db_files=550).
My question is how to determinate the right value of db_files parameter to avoid this message.
Regards.
Message was edited by:
learn

Increase the max number of open file on Linux or decrease db_files.
f the OS limit is 1024 db_files would have to be >= 472 for the message to be printed. t is printed if an instance is configured to access more datafiles than the OS-specific limit on the number of files that can be open in a single process. In this case the server will re-cycle the file descriptors.
Vadim Bobrov
Oracle Database Tools
http://www.fourthelephant.com

Similar Messages

  • Re-locate Alert log file

    My alert log files seems to be generating somewhere else.
    I am using a PFile to startup. Seems someone played around with the PFile.
    I need to generate the alert logs in a folder as specified by me:
    I have set the following parameters as such, but yet the alert log file doesn't generate in the bdump folder.
    background_dump_dest=C:\oracle\admin\db1\bdump
    core_dump_dest=C:\oracle\admin\db1\cdump
    user_dump_dest=C:\oracle\admin\db1\udump
    Is there any other parameter I need to fidget with?

    I am not using an SPfile. The Pfile is definetely being used for starting the instance.
    background_dump_dest=C:\oracle\admin\db1\bdump
    The other background trace files are being generated here, except for the alert log.
    Alert log is being generated in: C:\oracle\admin\practice\bdump.
    Now just so that i am not makin any human blunders I checked the following to be double sure:
    SQL> select distinct isspecified from V$spparameter;
    ISSPEC
    FALSE
    This means the Pfile is being used.
    SQL> show parameter background_dump
    NAME TYPE VALUE
    background_dump_dest string C:\oracle\admin\db1\bdump
    This verifies the destination folder.
    PLEASE HELP!

  • 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

  • Prevent message to go to the alert.log file

    Hi
    How can I prevent any message (for exm. SHUTDOWN IMMEDIATE) to be written to alert.log file? Is it possible?
    Thanks
    John

    Of course this can be done with some scripting, but alot of work and totaly worthless, why dont you want it to be shown in your alert log?
    if shutdown immediate present
    then cache alert log, rewrite it to new alert log without the text shutdown immediate, but as i said earlier, useless. :)

  • Ora-07445 reported in the alert log file

    Hi all,
    We are using the following platform:-
    OS: Solaris Operating System (SPARC 32-bit)
    Oracle Server - Enterprise Edition / Product Version: 9.2.0.5.0
    We encountered the following problem:-
    There is Ora-07445 reported in the alert log file.
    "ORA-07445: exception encountered: core dump [kgghash()+308] [SIGSEGV] [Address not mapped to object] [0x3222
    000] [] []reported in the database."
    These errors are signaled in more than 3 independent, unexplained, occurrences every day.
    When this error occurred while User was accessing the application system, by right the case will be shown on the system, but they were no case found.
    alert log are as below:-
    Fri Jul 27 09:12:30 2007
    Errors in file /disc3/oracle9205/RFDB/udump/rfdb_ora_27371.trc:
    ORA-07445: exception encountered: core dump [kgghash()+340] [SIGSEGV] [Address not mapped to object] [0x3184000] [] []
    Fri Jul 27 09:22:10 2007
    Thread 1 advanced to log sequence 10730
    Current log# 2 seq# 10730 mem# 0: /disc3/oracle9205/RFDB/RDO/logRFDB2a.rdo
    Current log# 2 seq# 10730 mem# 1: /disc3/oracle9205/RFDB/RDO/logRFDB2b.rdo
    Fri Jul 27 09:29:26 2007
    Errors in file /disc3/oracle9205/RFDB/udump/rfdb_ora_27372.trc:
    ORA-07445: exception encountered: core dump [kgghash()+296] [SIGSEGV] [Address not mapped to object] [0x3182000] [] []
    The applications have encountered ora-3113 after a short period of time followed by ora-3114.
    application log:-
    RF0120-1 2007-Jul-27 09:46:57] Load m[RF0120-1 2007-Jul-27 09:29:30] SQLCODE: -3113
    [RF0120-1 2007-Jul-27 09:29:30] Error Code -4105 returning from get score pan no.
    [RF0120-1 2007-Jul-27 09:29:30] Message type :120
    [RF0120-1 2007-Jul-27 09:29:30] Primary Account Number(PAN) DE0
    02 :5440640155262702
    [RF0120-1 2007-Jul-27 09:29:30] Processing code DE003 :003000
    [RF0120-1 2007-Jul-27 09:29:30] Transaction amount DE004 :000000000001
    [RF0120-1 2007-Jul-27 09:29:30] Settlement amount DE005 :000000000000
    [RF0120-1 2007-Jul-27 09:29:30] Transmission Date and time
    DE007 :0727092717
    [RF0120-1 2007-Jul-27 09:29:30] Settlement conversion rate DE009 :60263158
    [RF0120-1 2007-Jul-27 09:29:30] System trace audit no. DE011 :754710
    [RF0120-1 2007-Jul-27 09:29:30] Local transaction time DE012 :092717
    [RF0120-1 2007-Jul-27 09:29:30] Local transaction date DE013 :0727
    [RF0120-1 2007-Jul-27 09:29:30] Expiration date D
    E014 :0712
    [RF0120-1 2007-Jul-27 09:29:30] Settlement date DE015 :0727
    [RF0120-1 2007-Jul-27 09:29:30] Merchant type DE018 :5311
    [RF0120-1 2007-Jul-27 09:29:30] Point-of-service(POS) entry code DE022 :051
    [RF0120-1 2007-Jul-27 09:29:30] Acquiring inst. ID code DE032 :001912
    [RF0120-1 2007-Jul-27 09:29:30] Forwarding Inst. ID code DE033 :001912
    [RF0120-1 2007-Jul-27 09:29:30] Retrieval ref. no.
    DE037 :754710356390
    [RF0120-1 2007-Jul-27 09:29:30] Autholization ID response DE038 :356390
    [RF0120-1 2007-Jul-27 09:29:30] Response code DE039 :00
    [RF0120-1 2007-Jul-27 09:29:30] Card acceptor terminal ID DE041 :19306002
    [RF0120-1 2007-Jul-27 09:29:30] Card acceptor ID code DE042 :000001106
    020132
    [RF0120-1 2007-Jul-27 09:29:30] Card acceptor Name/Location
    What could have caused the above mentioned errors i.e Ora-07445 ; ora-3113 / ora-3114? How to resolve the problem.
    Please help .
    Thanks.

    i am also facing the same some time in ora 9.2.0.6 on Sun OS 9 SPARC 64-bits
    Errors in file /oracle/oracle9i/admin/FINPROD/udump/finprod_ora_6076.trc:
    ORA-07445: exception encountered: core dump [0000000100FDE088] [SIGSEGV] [Address not mapped to object] [0x00000013A] [] []
    Thu Aug 30 08:52:39 2007
    Errors in file /oracle/oracle9i/admin/FINPROD/udump/finprod_ora_6078.trc:
    ORA-07445: exception encountered: core dump [0000000100FDE088] [SIGSEGV] [Address not mapped to object] [0x00000013A] [] []
    Thu Aug 30 09:41:49 2007

  • Will the informations  be recorded in the alert.log file? -----No.168

    will the informations about the loss of a temporary file be recorded in the alert.log file?

    Yes, because whe your database starts needs to "mount" a tablespace with temporary files (case of tablespace "TEMP"). But don't worry with a loss of this tablespace because doesn't contain nothing when database starts.

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

  • How to be notified for all ORA- Errors recorded in the alert.log file

    based on Note:405396.1, I Changed the Matches Warning from the default value ORA-0*(600?|7445|4[0-9][0-9][0-9])[^0-9] to ORA-* in order to receive an warning alert for all ORA- errors.
    but I just recieved the alert like the following:
    Metric=Generic Alert Log Error
    Time/Line Number=Mon Feb 25 23:52:21 2008/21234
    Timestamp=Feb 26, 2008 12:06:03 AM EST
    Severity=Warning
    Message=ORA-error stack (1654, 1654, 1654) logged in /opt/oracle/admin/PRD/bdump/alert_PRD.log.
    Notification Rule Name=Alert Log Error
    Notification Rule Owner=SYSMAN
    as you can see, the message only indicate the ORA-1654, nothing else.
    How to set in 10g grid control to get the details alert that in the alert log like:
    "ORA-1654: unable to extend index ADM.RC_BP_STATUS by 1024 in tablespace PSINDEX"
    I can't believe Oracle 10g Grid control only provide the ORA- number without details

    Go to your database target.
    On the home tab, on the left hand side under Diagnostic Summary, you'll see a clickable date link next to where it says 'Alert Log'. Click on that.
    next click on Generic Alert Log Error Monitoring Configuration (its at the bottom)
    In the alert thresholds put:
    ORA-0*(600?|7445|4[0-9][0-9][0-9])[^0-9]
    I believe that will pick anything up but experiment, its only perl.
    If you want to test this use the DBMS_System.ksdwrt package but I would advise you only do so on a test database. If you've never heard of it, google it. Its a way of writing to your alert log.
    Make sure you have your emails sent to long format as well.

  • Alert log file of the database is too big

    Dear Experts?
    Let me update you that we are in process of doing an R12.1 upgrade ? And Our Current Instance is running on the 11.5.10 with 9.2.0.6 ?
    We have the below challenges before going for an database upgrade ?
    We have observed that the customer database alert_SID.log (9.2.0.6) size is 2.5GB ? how to purge this file ? Please advise
    Please also note that our Instance is running on the Oracle Enterprise Linux 4 update 8
    Regards
    Mohammed.

    user977334 wrote:
    Dear Experts?
    Let me update you that we are in process of doing an R12.1 upgrade ? And Our Current Instance is running on the 11.5.10 with 9.2.0.6 ?
    We have the below challenges before going for an database upgrade ?
    We have observed that the customer database alert_SID.log (9.2.0.6) size is 2.5GB ? how to purge this file ? Please advise
    Please also note that our Instance is running on the Oracle Enterprise Linux 4 update 8
    Regards
    Mohammed.Rename the alert logfile. once you rename the logfile another alert log file will create and being populated with time, and later you can delete it old alert log file . it doesnot harm your database.
    --neeraj                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               

  • How to read trace files alerted in the alert.log file

    Hello,
    My alert.log file indicated multiple trace files to review. How to read these trace files to understand the cause of errors. Do I open the trace files with vi and do a search for 'ORA-' error. Are there tools to read and understand trace files. Thank you.

    It depends what kind of trace file it is.
    You can use vi or other text editing tool to open the trace file. The trace file usually provides more detailed information when you have ORA- errors in alert.log. It's also very helpful for Oracle support when troubleshooting.

  • Oracle 9i (SE) Solaris 9 (Alert.log file)

    Hi Guys,
    How do I clean up my alert.log file. Do I have to delete it completely or only delete the content of the file.
    Thank you.

    Laura Gaigala wrote:
    Why You want to clean up it? Too large or some other reasons?
    If You have some planned db restart, then during restart rename archive.log and upon startup it will be created automaticaly again.
    If no restart is planned, then delete it's content, but before that make a copy of alert.log. Just in order You will need to find something.Actually, I've found that it is quite safe to rename the alert.log right out from under a running database. It will simply start a new one with the next message to be written. However, I agree it is much nicer to do this housekeeping while the db is down, so that the first entry in an alert log is the startup.
    This renameing of the log against a running process does not work for the listener log. I've found that if I rename listener.log to listener.log.1, the listener will continue to log to the original file (now listener.log.1) until such time as it is restarted. THEN it will start a new listener.log.
    This was all on unix. Windows may behave differently.

  • SMON ABOUT TO RECOVER UNDO SEGMENT s messages in alert log

    Problem
    ======
    There are lots of messages appearing in alert log of the following form:
    SMON: about to recover undo segment %s
    SMON: mark undo segment %s as available
    Reason
    ======
    When the recovery is going on after a abnormal shutdown. Cause These errors do not indicate rollback segment corruption. In oracle8i, this may becoz of problem with the "rollback_segments" parameter in the init.ora. where as in oracle9i, When the instance is shutdown, during the next startup instance recovery needs to take place.
    In AUM we do not have any control over which undo segments will brought online after the instance startup.When SMON finds such offline undo segments with transactions needing recovery ,then it does what is intended to do recovery.
    Solution
    ======
    with oracle8i, we need to cross check rollback_segments" parameter in the init.ora
    with oracle9i,
    first note down segment from SMON: mark undo segment %s as available
    sqlplus "/ as sysdba"
    alter session set "_smu_debug_mode"=4;
    alter rollback segment <offline segment name> online;
    e.g. alter rollback segment "_SYSSMU11$" online;
    Where 11 is the number that is appearing in the messages in the alert log.

    What's the point duplicate metalink doc here,
    SMON: ABOUT TO RECOVER UNDO SEGMENT %s messages in alert log
    Doc ID: Note:266159.1
    besides it's violation of Oracle support service contract.

  • ORA-1142 in alert log file

    hello everybody,
    I am getting the following ORA error in my Alert Log file.........
    alter tablespace SYSTEM end backup
    Sun Apr 13 01:42:58 2008
    ORA-1142 signalled during: alter tablespace SYSTEM end backup..
    what is this error??

    The version of oracle i am running is
    Oracle9i Enterprise Edition Release 9.2.0.7.0 - 64bit Production
    PL/SQL Release 9.2.0.7.0 - Production
    CORE 9.2.0.7.0 Production
    TNS for Solaris: Version 9.2.0.7.0 - Production
    NLSRTL Version 9.2.0.7.0 - Production........
    Section of the Alert Log displaying the message................
    Sun Apr 13 05:40:57 2008
    Thread 1 advanced to log sequence 109947
    Current log# 3 seq# 109947 mem# 0: /u09/oradata/inora/redo/redo03.log
    Current log# 3 seq# 109947 mem# 1: /u10/oradata/inora/ctrl/redo03.log
    Sun Apr 13 05:40:57 2008
    ARCH: Evaluating archive log 2 thread 1 sequence 109946
    ARCH: Beginning to archive log 2 thread 1 sequence 109946
    Creating archive destination LOG_ARCHIVE_DEST_1: '/u08/oradata/inora/archive/inora_1_109946.dbf'
    Sun Apr 13 05:40:57 2008
    ARC1: Evaluating archive log 2 thread 1 sequence 109946
    ARC1: Unable to archive log 2 thread 1 sequence 109946
    Log actively being archived by another process
    Sun Apr 13 05:40:57 2008
    ARCH: Completed archiving log 2 thread 1 sequence 109946
    Sun Apr 13 05:40:59 2008
    Thread 1 advanced to log sequence 109948
    Current log# 1 seq# 109948 mem# 0: /u09/oradata/inora/redo/redo01.log
    Current log# 1 seq# 109948 mem# 1: /u10/oradata/inora/ctrl/redo01.log
    Sun Apr 13 05:40:59 2008
    ARCH: Evaluating archive log 3 thread 1 sequence 109947
    ARCH: Beginning to archive log 3 thread 1 sequence 109947
    Creating archive destination LOG_ARCHIVE_DEST_1: '/u08/oradata/inora/archive/inora_1_109947.dbf'
    Sun Apr 13 05:40:59 2008
    ARC0: Evaluating archive log 3 thread 1 sequence 109947
    ARC0: Unable to archive log 3 thread 1 sequence 109947
    Log actively being archived by another process
    Sun Apr 13 05:40:59 2008
    ARCH: Completed archiving log 3 thread 1 sequence 109947
    Sun Apr 13 05:42:10 2008
    alter tablespace SYSTEM end backup
    Sun Apr 13 05:42:10 2008
    ORA-1142 signalled during: alter tablespace SYSTEM end backup
    Sun Apr 13 05:42:11 2008
    Thread 1 advanced to log sequence 109949
    Current log# 2 seq# 109949 mem# 0: /u10/oradata/inora/ctrl/redo02.log
    Current log# 2 seq# 109949 mem# 1: /u09/oradata/inora/redo/redo02.log
    Sun Apr 13 05:42:11 2008
    ARCH: Evaluating archive log 1 thread 1 sequence 109948
    ARCH: Beginning to archive log 1 thread 1 sequence 109948
    Creating archive destination LOG_ARCHIVE_DEST_1: '/u08/oradata/inora/archive/inora_1_109948.dbf'
    Sun Apr 13 05:42:11 2008
    ARC1: Evaluating archive log 1 thread 1 sequence 109948
    ARC1: Unable to archive log 1 thread 1 sequence 109948
    Log actively being archived by another process

  • ORA-28 in alert.log file

    please help.. getting ORA-28 in alert.log file.
    Mon Feb 25 17:46:05 2013
    ORA-28 signalled during: ALTER TABLESPACE DATA_APP_199903 READ ONLY...
    Mon Feb 25 17:48:54 2013
    ALTER TABLESPACE DATA_APP_199903 READ ONLY
    please let me know if you need any other info to help me.

    Error: ORA 28
    Text: your session has been killed
    Cause: A privileged user killed the session and it is no longer logged in to the database.
    Action: Contact the database administrator.
    The administrator may be attempting to perform an operation that requires users to be logged out.
    When the database administrator announces that the database is available, log in and resume work.So, its a message only not exactly an error. It happens when you or other DBA said alter tablespace tbs read only; and at the same time privileged user killed your session. So, nothing to worry/to do, just relogin and resume work.
    Regards
    Girish Sharma

  • Errors in Alert log file

    Hi,
    I have encountered following errors in alrt log file, its strange to see FAST_START_MTTR_TARGET is out of valid and aksing to use another value and that value is changing every second, it should be in increasing order or it should be consistent. I think i have a serious problem, so anyone could help me out on this. I am getting this "FAST_START_MTTR_TARGET 121 is out of the valid MTTR range, use 24381 instead" error regurarly.
    FAST_START_MTTR_TARGET 121 is out of the valid MTTR range, use 24381 instead.
    Wed Jan 16 23:40:34 2008
    Completed checkpoint up to RBA [0x2aadb.2.10], SCN: 5473742880
    Wed Jan 16 23:45:51 2008
    FAST_START_MTTR_TARGET 121 is out of the valid MTTR range, use 24017 instead.
    Wed Jan 16 23:46:21 2008
    FAST_START_MTTR_TARGET 121 is out of the valid MTTR range, use 23647 instead.
    Wed Jan 16 23:46:52 2008
    FAST_START_MTTR_TARGET 121 is out of the valid MTTR range, use 23298 instead.
    Wed Jan 16 23:47:22 2008
    FAST_START_MTTR_TARGET 121 is out of the valid MTTR range, use 22906 instead.
    Wed Jan 16 23:47:52 2008
    FAST_START_MTTR_TARGET 121 is out of the valid MTTR range, use 22507 instead.
    Wed Jan 16 23:48:22 2008
    FAST_START_MTTR_TARGET 121 is out of the valid MTTR range, use 22133 instead.
    Wed Jan 16 23:48:52 2008
    FAST_START_MTTR_TARGET 121 is out of the valid MTTR range, use 21786 instead.
    Wed Jan 16 23:49:22 2008
    FAST_START_MTTR_TARGET 121 is out of the valid MTTR range, use 21443 instead.
    Wed Jan 16 23:49:52 2008
    FAST_START_MTTR_TARGET 121 is out of the valid MTTR range, use 21062 instead.
    Wed Jan 16 23:50:22 2008
    FAST_START_MTTR_TARGET 121 is out of the valid MTTR range, use 20698 instead.
    Wed Jan 16 23:53:53 2008
    Incremental checkpoint up to RBA [0x2aadb.31b4.0], current log tail at RBA [0x2aadb.3e38.0]
    Thu Jan 17 00:00:54 2008
    FAST_START_MTTR_TARGET 121 is out of the valid MTTR range, use 19582 instead.
    FAST_START_MTTR_TARGET 121 is out of the valid MTTR range, use 16287 instead.
    Thu Jan 17 00:34:01 2008
    FAST_START_MTTR_TARGET 121 is out of the valid MTTR range, use 15902 instead.
    Thu Jan 17 00:34:31 2008
    FAST_START_MTTR_TARGET 121 is out of the valid MTTR range, use 14638 instead.
    Thu Jan 17 00:35:01 2008
    FAST_START_MTTR_TARGET 121 is out of the valid MTTR range, use 13600 instead.
    Thu Jan 17 00:35:31 2008
    FAST_START_MTTR_TARGET 121 is out of the valid MTTR range, use 12773 instead.
    Thu Jan 17 00:36:02 2008
    FAST_START_MTTR_TARGET 121 is out of the valid MTTR range, use 12460 instead.
    Thu Jan 17 00:36:32 2008
    FAST_START_MTTR_TARGET 121 is out of the valid MTTR range, use 12338 instead.
    Thu Jan 17 00:37:01 2008
    Process P187 died, see its trace file
    Thu Jan 17 00:37:02 2008
    FAST_START_MTTR_TARGET 121 is out of the valid MTTR range, use 12248 instead.
    Thu Jan 17 00:37:02 2008
    Process P188 died, see its trace file
    Thu Jan 17 00:37:03 2008
    Process P189 died, see its trace file
    Thu Jan 17 00:37:04 2008
    Process P190 died, see its trace file
    Thu Jan 17 00:37:16 2008
    Process J000 died, see its trace file
    Thu Jan 17 00:37:16 2008
    kkjcre1p: unable to spawn jobq slave process
    Thu Jan 17 00:37:16 2008
    Errors in file /oracle/BP3/saptrace/background/bp3_cjq0_4788.trc:
    Process J000 died, see its trace file
    Thu Jan 17 00:37:22 2008
    kkjcre1p: unable to spawn jobq slave process
    Thu Jan 17 00:37:22 2008
    Errors in file /oracle/BP3/saptrace/background/bp3_cjq0_4788.trc:
    Thanks
    Jafar

    This parameter, FAST_START_MTTR_TARGET ranges from 0 to 3600 seconds. It is important to specify your oracle version, since a similar issue is reported for the 10gR1 release.
    The solution for it would be to increase the value to the suggested one in the alert.log file, but it could be completely out of range from the valid values, so set it to zero and let the oracle instance calculate the value. You can check the output at the V$INSTANCE_RECOVERY view at the columns TARGET_MTTR, and ESTIMATED_MTTR prior to proceeding with modificaiton.
    On the other hand, I suggest you to read this metalink note
    Kkjcre1p: Unable To Spawn Jobq Slave Process, Error 1089
         Doc ID:      Note:344275.1
    for the Kkjcre1p error message.
    ~ Madrid

Maybe you are looking for