Alert file entry: Load Information not supported by OS!

I get the following alert file entry every 30-60 seconds with any database I create with Oracle8.1.5i on RedHat6.2:
Load Information not supported by OS!
The entry appears to relate to PMON and (eventually) causes the creation of PMON derived trace files.
Can anybody help?

Thanks Kristian, your solution is totally correct.
About a day after you posted your advice, I finally managed to get our Oracle support info from our Oracle reseller, and they have advised the same thing. Apparently, this is a known bug.

Similar Messages

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>quote:<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

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.

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

Re: Load Inidicator Not Supported by OS

Hi Guys,
I am running Oracle on RedHat6.2. I note in alert log I find entery - "Load Inidicator Not Supported by OS! " . I am confused ,I have configured Kernel as per requirement from Oracle .
I plan to run MTS ., Now my concern is during load conditions will PMON is going to shutdown instance due this problem .
Thanks in advance .
Manoj

I Have The same Problem,But i Already commented All The entries For "Mts" In My INITxxx.ORA
<BLOCKQUOTE>quote:<HR>Originally posted by jmsalvo (John Salvo):
Check my help page:
http://homepages.tig.com.au/~jmsalvo/linux/oracle8i.html <HR></BLOCKQUOTE>
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

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

Was given an alert that my device did not support PayPal, I changed my payment method and I am still getting the alert

I tried to purchase an app and was given an alert that my device was not supported by Paypal and I needed to change my payment information. So I logged into my Apple account and updated it, but I'm still getting the alert when I try to buy something

iTunes Store Support
http://www.apple.com/emea/support/itunes/contact.html

"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>quote:<HR>Originally posted by jmsalvo (John Salvo):
Check my help page:
http://homepages.tig.com.au/~jmsalvo/linux/oracle8i.html <HR></BLOCKQUOTE>
null

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

Error message "Live file system repair is not supported."

System won't boot. Directed to Disk Utility to repair but get error message "Live file system repair is not supported." Appreciate all help.
Thanks.
John

I recently ran into a similar issue with my Time Machine backup disk. After about 6 days of no backups - I had swapped the disk for my photo library for a media project; I reattached the Time Machine disk and attempted a backup.
Time Machine could not backup to the disk. Running Disk Utility and attempting to Repair the disk ended up returning the "Live file system repair is not supported" message.
After much experimentaion with disk analysis softwares, I came to the realization that the issue might be that the USB disk dock wasn't connected directly to the MacBook Pro - it was daisy-chained through a USB Hub.
Connecting the USB disk dock directly to the MBP and running Disk Utility appears to have resolved the issue. DU ran for about 6 hours and succesfully repaired the disk. Consequently, I have been able to use that Time Machine disk for subsequent backups.

Print to PDF - using Snow Leopard (Saving a PDF file when printing is not supported. Instead, choose

i have a PDF form that i created that is used as a custom proposal that my company sends out to potential clients. the form in its editable state is only used internally. we recently upgraded to snow leopard, but prior to the upgrade, we were able to fill the custom proposal form out using adobe reader, and, as you well know, we weren't able to save that edited document as a PDF with the custom form fields filled out. our work around using adobe reader was to print to a pdf using the adobe pdf printer in the printer dialog. with the addition of snow leopard, however, instead of choosing the adobe pdf printer, we were to choose PDF from the bottom left corner, then Save As PDF, and it would spit out an uneditable pdf that then allowed us to email it to the potential client without them being able to edit it as well as have an internal, digital copy for our records instead of having lots of paper floating around (i know this is also doable using security that disallows the client certain editing privileges, but printing to a pdf is much quicker and more efficient, and the pdf security isn't really that secure at its best).
in any case, i came across this gem of a post here on the support forums that installs another option from the PDF drop down on the bottom left of the print dialog menu that reads Save As Adobe PDF and is supposed to do exactly what i am trying to get it to do...print to a pdf file from adobe reader.
http://kb2.adobe.com/cps/509/cpsid_50981.html
once i updated to acrobat 9.2 (as the link above suggests 9.1), however, the Save As Adobe PDF does appear in the print dialog menu, but it still gives me the same error that acrobat 8 - 9 gave me while using Snow Leopard — Saving a PDF file when printing is not supported. Instead, choose File > Save — and as i've already explained, you can't save an edited pdf form in reader (as i am the only one in the office with acrobat) and still keep the fields as you've entered them in. the only work around is to print to a pdf but is apparently having some recent problems.
using acrobat, however, i know that i can save the editable pdf as a new file with the fields customized as i have left them, but it still saves it as an editable pdf and the print to a pdf option still remains the best option...that way we have digital copies internally that are uneditable that can be printed at any time or emailed to the client.
how can i do print to a pdf, based on what i've written above, using snow leopard and acrobat and reader?

A simple way is to flatten the form fields, which converts the field appearances to regular page contents. You can do this with JavaScript or PDF Optimizer (Advanced > PDF Optimizer > Discard Objects > Flatten form fields). A very nice script that adds a custom menu item can be found here: http://www.uvsar.com/projects/acrobat/flattener/

Saving a PDF file when printing is not supported. Instead, choose File Save.

I am using Mountain Lion (10.8.2) and I was using Adobe Reader version 9. In the past, I've always been able to print to file using the File -> Print dialogue but all of a sudden it stopped working. I read somewhere that installing the latest version of Adobe Reader (version 11) would remove the old printer, so I did so. It took me about an hour on version 11 to even find the pdf print to file option, but I am getting the same message. For what it's worth, when I try print to file from Microsoft Word, I have no problem. I have no idea why things changed all of a sudden, but does anyone have any idea how I can get this working again?

I checked with Adobe. No luck.
Allow me to clarify my problem:
I have Adobe Reader XI. I also use a Mac--imac and a MacBook Pro. My adobe was updated on 12/24. Prior to that point, I could open my print dialogue box and there was a PDF tab on the bottom left. In the drop down menu there were many choices, including but not limited to Open in PDF Preview, Print PDF, Save PDF, email PDF. If I selected one page of 30 pages from a document saved in Adobe, I could extract just that one page and save it or email it, without having to send the entire document. After the update, when I open a PDF file using ADOBE READER XI, and then open the print dialogue box, and follow those same steps, I get the message "Saving a PDF file when printing is not supported. Instead, choose File > Save." My question is why is this feature now unavailable and is there a way to fix it?
The answer I got from Adobe was that Adobe never had this function, so it must have been via my print or preview programs..which are apple. Does anyone have any thoughts?
Thank you.
https://forums.adobe.com/message/7124567

Saving a PDF file when printing is not supported.

Hi Guys,
I upgrade from leopard to snow and now I don't have the possibility anymore to to print PDF as a PDF.
Before I was going to print and then choose save as a pdf and everything ok.
Now after the upgrade to snow every time that I am going to print a pdf from a pdf (acrobat 9 and X) I received this msg "Saving a PDF file when printing is not supported. Instead, choose File > Save "
Why that happened ? how can I fix it?
The thing is that I have a pdf form (contract) that I have to fill up and print it as a pdf.
Now I can't do that I can save only the form with the fields unlock.
thanks you in advance for your help.
Xoxo
Fotis

Ah.. this is so annoying filled in a long form.. which doesn't allow saving.. I assumed as normal with this type of form I could print to PDF and at least get a electronic copy.. but no, I made the mistake of installing Adobe Reader.. and it has screwed up the print options.. when I try to save as PDF from the print menu I get the helpful suggestion
"Saving a PDF file when printing is not supported. Instead, choose File > Save."
When I do as suggested.. it helpfully tells me that it will only save a "blank form"..
Adobe has badly messed up their reader.. I now need to print out and then scan this document to get the electronic copy I need.. I will be uninstalling promptly after this fiasco..

Alert file entry: Load Information not supported by OS!

Similar Messages

Maybe you are looking for