Any word on 'Load Indicator Not Supported' error?

Has anyone figured this one out yet? According to the Admin
Guide, the MAX_DUMP_FILE_SIZE will only control the trace files,
not the alert file. It CAN be safely deleted, even with the
instance up.
What a pain :(
null

I also have this problem and it is sort of solved by disabling the Multi Threaded Server option.
Solution #1
Disable MTS by removing the parameter MTS_SERVERS from the init.ora file and any other MTS parameters
Note: You will still get the Load indicator error by it will not repeat in your alert log file. and it appears only at startup for the database
Solution #2
If you absolutely need MTS then set the init.ora parameter MAX_DUMP_FILE_SIZE very large so that your server will not crash by populating your alert.log file with the load indiator error and periodically clean the log out.

Similar Messages

  • Init.ora error: Load Indicator not supported by OS

    I am getting this error dumped into my init'instance'.ora file
    every 34 seconds. Has anyone seen this before?
    Tue Sep 14 16:02:26 1999
    Load Indicator not supported by OS !
    Tue Sep 14 16:03:00 1999
    Load Indicator not supported by OS !
    Tue Sep 14 16:03:34 1999
    Load Indicator not supported by OS !
    Tue Sep 14 16:04:07 1999
    Load Indicator not supported by OS !
    Tue Sep 14 16:04:41 1999
    Load Indicator not supported by OS !
    Tue Sep 14 16:05:15 1999
    Load Indicator not supported by OS !
    Tue Sep 14 16:05:49 1999
    Load Indicator not supported by OS !
    Tue Sep 14 16:06:23 1999
    Load Indicator not supported by OS !
    Any help, guesses and all, would be welcomed.
    Jeff
    null

    Jeff Wiegand (guest) wrote:
    : I am getting this error dumped into my init'instance'.ora file
    : every 34 seconds. Has anyone seen this before?
    : Tue Sep 14 16:02:26 1999
    : Load Indicator not supported by OS !
    : Tue Sep 14 16:06:23 1999
    : Load Indicator not supported by OS !
    Yes, them are here. Not in init'instance'.ora, but in
    alert_instance.log and pmon_pid.trc. Every 34 secs.
    And as I can see, many people have that "trouble", I'm
    also have. This thread was waked up about month ago without
    any clarification/solutions...
    null

  • Solution (sort of) to "Load Indicator not supported by OS" problem

    During database creation, even if you choose "Dedicated Server Mode" instead of "Shared Server Mode" (for MTS), you will actually be using dedicated server processes for Net8 BUT you will still use MTS for IIOP connections. That's why you have those MTS_ entries in your INIT.ORA file.
    The reason is IIOP connections to 8i can only be done with MTS.
    So, if you are not interested or will not use 8i to handle IIOP connections (in that case, maybe stick with 8.0.5 or use OAS ), comment out all MTS entries in your INIT.ORA file, restart the instance / database.
    You will then notice that the alert log has no more "Load Indicator not supported by OS" entries, while the pmon trace file will have only one entry for that message, just after startup, but never again.
    If you are interested on IIOP connections ( e.g.: the reason you chose 8i instead of 8.0.5 and OAS ), then I think Oracle is the only one who can answer this problem. Or maybe somebody with a support contract with Oracle can ask Oracle about this.
    So what does the error message mean? From what I have read, an 8i listener registered with multiple 8i dispatchers chooses the dispatcher that has the least load.
    However, even if I specify in my INIT.ORA that there is only one dispatcher (therefore assuming that it won't have to check the load of the dispatcher since there is only one to choose from), it still generates the error message.
    John Salvo

    If anyone knows any better about what I wrote, please let me and everyone else in this forum know.
    I will be adding this to my Linux 8i Installation Page:
    http://homepages.tig.com.au/~jmsalvo/linux/oracle8i.html
    John Salvo
    null

  • 8i: Load Indicator not supported by OS!

    I get a message in my PMON background dump file that
    reports 'Load Indicator not supported by OS!'. I am not sure
    what this is referring to, what the impact is on the stability
    of the instance, or what to do about it.
    I am running Oracle8i 8.1.5.0.1 (yes, the new patch) on RedHat
    6.0. I got the same message prior to installing the patch. I
    even built a new database to see if it was related to 8.1.5.0.0,
    but I still get the same thing. The problem occurs even with no
    one connected to the instance (there is only one instance on
    this machine). The error message keeps repeating and the dump
    file keeps growing.
    Is anyone else seeing this? Is there something I need to
    configure into my kernel? I am running kernel version 2.2.10
    configured for SMP on a dual processor Pentium III system.
    Here is the contents of my PMON dump file:
    ---- cut ----
    Dump file /u01/app/oracle/admin/test1/bdump/pmon_882.trc
    Oracle8i Enterprise Edition Release 8.1.5.0.0 - Production
    With the Partitioning and Java options
    PL/SQL Release 8.1.5.0.0 - Production
    ORACLE_HOME = /u01/app/oracle/product/8.1.5
    System name: Linux
    Node name: skinner.smiley.com
    Release: 2.2.10-smp-1
    Version: #6 SMP Fri Aug 6 01:02:58 MYT 1999
    Machine: i686
    Instance name: test1
    Redo thread mounted by this instance: 0 <none>
    Oracle process number: 2
    Unix process pid: 882, image: [email protected] (PMON)
    *** SESSION ID:(1.1) 1999.08.20.23.28.45.422
    OER 536879337 in Load Indicator : Error Code = 537937328 !
    *** 1999.08.20.23.29.26.111
    Load Indicator not supported by OS !
    *** 1999.08.20.23.29.59.881
    Load Indicator not supported by OS !
    *** 1999.08.20.23.30.33.651
    Load Indicator not supported by OS !
    <message repeats indefinitely>
    ---- cut ----
    null

    Robert Folmer (guest) wrote:
    : I am seeing the same error. Also got it before and after the
    : patch. Seems to create a dump file every time I start the
    : database. I have not changed any kernel memory params yet
    : (shmmax, etc) , so I will probably try that soon to see if it
    : helps.
    : John Smiley (guest) wrote:
    : : I get a message in my PMON background dump file that
    : : reports 'Load Indicator not supported by OS!'. I am not
    sure
    : : what this is referring to, what the impact is on the
    stability
    : : of the instance, or what to do about it.
    : : I am running Oracle8i 8.1.5.0.1 (yes, the new patch) on
    RedHat
    : : 6.0. I got the same message prior to installing the patch.
    I
    : : even built a new database to see if it was related to
    : 8.1.5.0.0,
    : : but I still get the same thing. The problem occurs even
    with
    : no
    : : one connected to the instance (there is only one instance on
    : : this machine). The error message keeps repeating and the
    dump
    : : file keeps growing.
    : : Is anyone else seeing this? Is there something I need to
    : : configure into my kernel? I am running kernel version
    2.2.10
    : : configured for SMP on a dual processor Pentium III system.
    : : Here is the contents of my PMON dump file:
    : : ---- cut ----
    : : Dump file /u01/app/oracle/admin/test1/bdump/pmon_882.trc
    : : Oracle8i Enterprise Edition Release 8.1.5.0.0 - Production
    : : With the Partitioning and Java options
    : : PL/SQL Release 8.1.5.0.0 - Production
    : : ORACLE_HOME = /u01/app/oracle/product/8.1.5
    : : System name: Linux
    : : Node name: skinner.smiley.com
    : : Release: 2.2.10-smp-1
    : : Version: #6 SMP Fri Aug 6 01:02:58 MYT 1999
    : : Machine: i686
    : : Instance name: test1
    : : Redo thread mounted by this instance: 0 <none>
    : : Oracle process number: 2
    : : Unix process pid: 882, image: [email protected]
    (PMON)
    : : *** SESSION ID:(1.1) 1999.08.20.23.28.45.422
    : : OER 536879337 in Load Indicator : Error Code = 537937328 !
    : : *** 1999.08.20.23.29.26.111
    : : Load Indicator not supported by OS !
    : : *** 1999.08.20.23.29.59.881
    : : Load Indicator not supported by OS !
    : : *** 1999.08.20.23.30.33.651
    : : Load Indicator not supported by OS !
    : : <message repeats indefinitely>
    : : ---- cut ----
    According to my information, which was obtained in a private
    conversation, the new Oracle8i feature that is supposed to
    help with load balancing, namely the resource allocation plans,
    uses a facility that doesn't exist on Linux. As those resource
    plans are checked frequently by PMON, the message is being
    constantly reiterated. You can limit the size of a trace file
    to 10k and the message will stop. It would be nice to have a
    parameter to disable this feature.
    null

  • What is the problem---"Load Indicator not supported by OS !"

    I found a lot of error messages in
    $ORACLE_HOME/admin/$ORACLE_SID/bdump/pmon_DDD.trc today.
    Where, DDD is a 3 or 4-digit number.
    All the messages are the same, "Load Indicator not supported by
    OS!":
    *** SESSION ID:(1.1) 1999.11.18.18.48.02.435
    OER 536879337 in Load Indicator : Error Code = 587494760 !
    *** 1999.11.18.18.48.43.590
    Load Indicator not supported by OS !
    *** 1999.11.18.18.49.18.690
    Load Indicator not supported by OS !
    *** 1999.11.18.18.49.52.460
    Load Indicator not supported by OS !
    *** 1999.11.18.18.50.26.230
    Load Indicator not supported by OS !
    *** 1999.11.18.18.51.00.000
    Load Indicator not supported by OS !
    *** 1999.11.18.18.51.33.770
    Load Indicator not supported by OS !
    *** 1999.11.18.18.52.07.540
    Load Indicator not supported by OS !
    I checked our another Oracle 8i server, the error occurs too.
    My systems are all Redhat 6.1, glibc 2.1.2.
    The Oracle Server is Oracle 8i 8.1.5 for Linux, Enterprise
    Edition, and with the latest patch.
    What's wrong?
    null

    I agree. Could it be the shm settings in the hernal itself? I
    recall some suggested mods in the release docs.
    Shane Quigley (guest) wrote:
    : I don't think that this change will make any significant
    : improvement with the problem at hand. It seems that there is a
    : background process that try to call the "Load Indicator"
    : periodically at intervals of about a second. I have this
    : problem as well and the problem goes beyond they process
    monitor
    : (pmon) it seems as though the server logs the problem as well
    : the error is as follows:
    : skgm warning: EINVAL creating segment of size 0000000000370000
    : fis the shm parameters in /etc/system or equivalent.
    : I don't know if this helps any but all I know is that changing
    : the specification of the location of the control files will not
    : change anything. If no path is set when specifying the
    location
    : ie. control_files=(control01.ctl,control02.ctl)
    : then the default path is chosen. By explicitly setting the
    path
    : ie. control_file=
    : (/database/db1/control01.ctl,/database/db1/control02.ctl)
    : just allows you to specify a location that does not exist in
    : your current path.
    : If you have any further information regarding the problem
    please
    : let me know. In my configuration the control files have their
    : entire path specified and I still get this problem.
    : PS. Do you know if this problem could cause the OS to crash?
    : Wiwih Gunadi (guest) wrote:
    : : The problem is with your
    : : initSID.ora file in $ORACLE_BASE/admin/$ORACLE_SID/pfile
    : : directory.
    : : edit this file and find the "control_file" parameter
    : : most likely what you have there doesn't match your
    : : actual control file names
    : : mine says:
    : : control_file=(ora_control1, ora_control2)
    : : i changed it to:
    : : control_file=(/your/oracle/base/oradata/control01.ctl,
    : : /your/oracle/base/oradata/control02.ctl)
    : : then the database will mount correctly, but I still can't
    : : open it because of error ora-01571 something about redo logs
    : : being incompatible.
    : : Hope this helps,
    : : G. Young (guest) wrote:
    : : : I found a lot of error messages in
    : : : $ORACLE_HOME/admin/$ORACLE_SID/bdump/pmon_DDD.trc today.
    : : : Where, DDD is a 3 or 4-digit number.
    : : : All the messages are the same, "Load Indicator not
    supported
    : by
    : : : OS!":
    : : : *** SESSION ID:(1.1) 1999.11.18.18.48.02.435
    : : : OER 536879337 in Load Indicator : Error Code = 587494760 !
    : : : *** 1999.11.18.18.48.43.590
    : : : Load Indicator not supported by OS !
    : : : *** 1999.11.18.18.49.18.690
    : : : Load Indicator not supported by OS !
    : : : *** 1999.11.18.18.49.52.460
    : : : Load Indicator not supported by OS !
    : : : *** 1999.11.18.18.50.26.230
    : : : Load Indicator not supported by OS !
    : : : *** 1999.11.18.18.51.00.000
    : : : Load Indicator not supported by OS !
    : : : *** 1999.11.18.18.51.33.770
    : : : Load Indicator not supported by OS !
    : : : *** 1999.11.18.18.52.07.540
    : : : Load Indicator not supported by OS !
    : : : I checked our another Oracle 8i server, the error occurs
    too.
    : : : My systems are all Redhat 6.1, glibc 2.1.2.
    : : : The Oracle Server is Oracle 8i 8.1.5 for Linux, Enterprise
    : : : Edition, and with the latest patch.
    : : : What's wrong?
    null

  • To get rid of "Load Indicator not Supported by OS!" - del MTS if u r not into IIOP.

    During database creation, even if you choose "Dedicated Server Mode" instead of "Shared Server Mode" (for MTS), you will actually be using dedicated server processes for Net8 BUT you will still use MTS for IIOP connections. That's why you have those MTS_ entries in your INIT.ORA file.
    The reason is IIOP connections to 8i can only be done with MTS.
    So, if you are not interested or will not use 8i to handle IIOP connections (in that case, maybe stick with 8.0.5 or use OAS ), comment out all MTS entries in your INIT.ORA file, restart the instance / database.
    You will then notice that the alert log has no more "Load Indicator not supported by OS" entries, while the pmon trace file will have only one entry for that message, just after startup, but never again.
    If you are interested on IIOP connections ( e.g.: the reason you chose 8i instead of 8.0.5 and OAS ), then I think Oracle is the only one who can answer this problem. Or maybe somebody with a support contract with Oracle can ask Oracle about this.
    So what does the error message mean? From what I have read, an 8i listener registered with multiple 8i dispatchers chooses the dispatcher that has the least load.
    However, even if I specify in my INIT.ORA that there is only one dispatcher (therefore assuming that it won't have to check the load of the dispatcher since there is only one to choose from), it still generates the error message.
    John Salvo

    Unfortunately, the RAM shortage on my PC mandates the use of MTS. I've modified the
    startup procedures to clean up the trace & log files, so my filesystem doesn't get filled up to the brim. I can live with the few messages in my trace & log files.

  • 8.1.5.0.2 patch does NOT fix "Load Indicator not supported by OS"

    Well, I was hoping it did. Anyone else who experienced otherwise, please post.
    However, it did fix the problem in the pmon trace file of:
    OER 536879337 in Load Indicator : Error Code = 570716328 !
    ... whenever starting an instance. This error does not happen anymore.
    null

    recieved the same error
    8.1.5.0.2
    Load Indicator not supported by OS !
    *** 1999.12.31.11.16.13.768
    Load Indicator not supported by OS !
    *** 1999.12.31.11.16.47.538
    Load Indicator not supported by OS !
    anyone have an idea

  • Alert log message : Load Indicator not supported by OS

    I am running Oracle 8.1.5 on Red Hat Linux 6.1 , I am getting an alert message
    "Load Indicator not supported by OS"
    Kindly help me urgently on the below email address
    [email protected]
    Thanks

    Try turning of the Multi-threaded server option (i.e. comment out "mts" references in the init[SID].ora file). This appears to be an MTS-related bug.
    HTH
    <BLOCKQUOTE><font size="1" face="Verdana, Arial">quote:</font><HR>Originally posted by (Viral Shah):
    I am running Oracle 8.1.5 on Red Hat Linux 6.1 , I am getting an alert message
    "Load Indicator not supported by OS"
    Kindly help me urgently on the below email address
    [email protected]
    Thanks<HR></BLOCKQUOTE>
    null

  • "Load Indicator not supported by OS !" messages

    Hello,
    I'm running a 8.1.5.0.2 Oracle8i database on a Mandrake 7, and i get loads of these messages : 'Load Indicator not supported by OS !' in the logs. ( "loads of" meaning about every 30 seconds...)
    How can I get rid of these ?

    I Have The same Problem,But i Already commented All The entries For "Mts" In My INITxxx.ORA
    <BLOCKQUOTE><font size="1" face="Verdana, Arial">quote:</font><HR>Originally posted by jmsalvo (John Salvo):
    Check my help page:
    http://homepages.tig.com.au/~jmsalvo/linux/oracle8i.html <HR></BLOCKQUOTE>
    null

  • Error "Load indicator not supported by OS"

    Hello all,
    im runnin 8i on Suse 6.2 (2.2.12).
    Always when i start the server as an mts he fills up the alert log with messages like menioned above.
    Just a time and this string and that nearly all 30 secs. The server is up and running but why does he do that. so i have to delete the alert log every morning cause there are about 200k log per day.
    When i stop the server and get it up as anon mts everything is fine.
    Any suggestions?
    Li

    I also have this problem and it is sort of solved by disabling the Multi Threaded Server option.
    Solution #1
    Disable MTS by removing the parameter MTS_SERVERS from the init.ora file and any other MTS parameters
    Note: You will still get the Load indicator error by it will not repeat in your alert log file. and it appears only at startup for the database
    Solution #2
    If you absolutely need MTS then set the init.ora parameter MAX_DUMP_FILE_SIZE very large so that your server will not crash by populating your alert.log file with the load indiator error and periodically clean the log out.

  • Load Indicator not supported by OS!

    I cannot get rid of above message in my
    alert_ORCL.log. What does it mean ???

    ORacle can forward this patch to you.
    However after I applied patch I still get
    OS not supported. I would suggest waiting for 8.1.7 which is due for release in a few weeks.
    <BLOCKQUOTE><font size="1" face="Verdana, Arial">quote:</font><HR>Originally posted by Adam Jablonski ([email protected]):
    I cannot get rid of above message in my
    alert_ORCL.log. What does it mean ???<HR></BLOCKQUOTE>
    null

  • URGENT : Load Indicator not supported by OS !

    i'm on suse 7.0
    kernelversion 2.2
    oracle 8.1.6
    i've this error message on startup
    any help please !!

    I have the same error msg. I opened a tar a while ago with oracle and was told to ingore it. You can look at my tar to find out all the details of how to make sure you set up a cron job to delete these pmon*.trc files from your os so the file system doesn't fill up. But basically it's nothing to worry about. I was told they would get rid of the message in future releases.
    TAR: 1874896.996

  • "Load Indicator not supported by OS!" alert

    The message in the subject is posted to the
    alert log by PMON every 30 seconds or so.
    How can I get rid of it? Trawling through
    the docs and this site is giving me no
    clues at all...

    I do have the same problem and am on the desk now, but, sorry, no solution right now !!
    (Linux Redhat 6.2 & Oracle 8.1.5.0.0 ).
    Did U look for any patches to apply on your linux environnement and stilll have the problem ?? (ftp.oracle.com/pub/www/otn/linux)
    null

  • Datatype : 25 not supported error while saving Logical Query in BIP Dataset

    Hi All,
    I have created a nested logical Query in OBIEE Publisher Datamodel using parameters.
    Here is the simple query :
    Select name, revenue, date from
    select "SubjectAreaName"."TableName"."Name" name,
    case when :Date > date '2012-01-01' then "SubjectAreaName"."TableName"."Revenue" else NULL end Revenue,
    date date
    from
    "SubjectAreaName"
    where
    date = :Date
    ) T1
    Note - :Date is the parameter. When I try saving this dataset as-is, it throws me Datatype : 25 not supported error. But, when i replace the parameter :Date with actual date, then the query works. Also, the inner query works with or without parameters. The issue arises when I use the outer query and the parameters.
    Please let me know if you have come across such a problem ?
    Any help on this regard would be highly appreciated.
    Thanks
    Swarna

    ya i can understand we wont do the sql logic at the data model part as some time performance issue may come when comparaed to sql run in package and sql running in data model . so i have mostly done using package and i will just do select * from table in the data set of data model so i didn't face any issue's like this .
    once check this tutorial may be you already
    i use to create parameters like this i didn't face any issue
    SELECT * from TEST where ID=:p_id
    http://st-curriculum.oracle.com/obe/fmw/bi/bip/bip11g/gettingstarted/gettingstarted.htm

  • CS4 install problem "you cannot run...architecture not supported" error

    Just received my copy of CS4 (Mac) from amazon.com. Installed it. But could not get it to run. Got a "You cannot run....architecture not supported" error message. Can't understand why? This is my first version of Photoshop CS. Didn't install CS3...etc. Nor did I previously install the "master" edition. And I am running a MBP 2.5GHz laptop. So it has to be software related. A corrupt file perhaps?
    I also cannot install Adobe AIR. Suddenly 3 windows pop up. Telling me I can't install AIR.
    Not happy. Expensive software not running. Not good. :P What gives???
    Please help me soon!

    Where were you yesterday Buko?? :) Where would one find the "CS4 Cleanscript" any how? Would have been nice if you provided a link. Heh...
    Any how. Last night. I did d/l the trial version of CS4 Extended. Installed it. Then read the READ.ME file. Stresses that you MUST use their uninstall program. That you can't simply drag the folder to the TRASH (or use AppDelete or AppZapper...as you would be doing the same thing pretty much). So, I used Adobe's CS4 uninstaller. Did a very thorough job of removing the right files.
    I managed to sucessfully install my copy of CS4. I even got the proper SETUP dialogue box this time (6 tabs). Previously only 3 tabs were visible. This one asks you to input your serial # and even register before you finish.
    Now I see the blue PS folder icon. Have copied a few PS program icons to my dock. Working now as it should.
    Moral of the story? Read the READ.ME file!! And use proprietary uninstall programs for huge complicated programs like PS CS4. :) Later guys.

Maybe you are looking for

  • HP Laserjet Pro 200 Printer Not Responding Wirelessly to Macbook Pro 13 Using Mavericks OS

    My printer has worked fine wirelessly since upgrading to Mavericks in Jan 2014.   Last week my printer stopped responding both wirelessly and with the cable.  I can print wirelessly from my I-Phone and I-Pad.  I have reset the printers (deleted them)

  • Java-style buttons in Oracle Forms 6i

    Hey there, Does anyone know how to create buttons with curved edges in Oracle Forms 6i? Something like those Swing components in Java? Thanks Al

  • Power shot s 100.

    i have black spaces on the sides of the viewing screen. how do i get rid of them? also, can i adjust the pictures i have already taken to delete them?

  • Help for a Dreamweaver beginner

    Hi everyone, I am a currently doing the Total Training DVD for Studio 8 bundle and have built my first index page. There is a section in the DVD (which I can't for the life of me find again) which covers browsers. My page displays correctly in Intern

  • Alert configuration not open in RWB

    Hi,      Whenever i try to open "Alert configuartion" and "Alert Inbox" in RWB, it shows page cannot be displayed error. So, i am not able to open that. But i checked in SICF, alert inbox is activated. And also i changed the exchange profile host nam