- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Async. I/O problems.
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-27-2001 01:13 PM
тАО03-27-2001 01:13 PM
Async. I/O problems.
And sybase is configuerd to use async. i/o device and configures with 224 MB of memory.
When I try to increase memory of sybase, system brings up the devices in standard i/o rather than async. i/o.
If I set the memory back to 224 again..and bounce the system...sybase comes up with async. i/o.
I think there's something on HP side which is stopping me from using both.
Could someone help me on this.
shmmax is set to 1GB.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-27-2001 05:22 PM
тАО03-27-2001 05:22 PM
Re: Async. I/O problems.
Another governing factor is the "shmmax" kernel parameter. You must set it high enough for increasing the amount of physical memory Sybase could grab. The shmmax value should set to a value that is larger than the amount of memory your server have got.
Another chance for not being able to start async I/O is that there weren't enough lockable memory because other processes were holding up the memory. In such cases, reboot your server and make sure Sybase is the first application to start.
Rgds,
Philip
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-28-2001 08:24 AM
тАО03-28-2001 08:24 AM
Re: Async. I/O problems.
To my knowledge shmmax should be equal to physical memory and it is set to 1GB in the system.
I have 63 devices in sybase for async i/o mode.
Is more number of devices configures causing the problem..or any other way of increasing memory for sybase as well as making use of async i/o for all 63 devices.
Thanks,
Vijay
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-28-2001 03:45 PM
тАО03-28-2001 03:45 PM
Re: Async. I/O problems.
In any case, in general when Sybase is unable to get as much memory as it would like to get, starting devices with standard I/O instead of async I/O is a pretty common sympton that happens as a result.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-28-2001 06:58 PM
тАО03-28-2001 06:58 PM
Re: Async. I/O problems.
Have you granted the sybase user the MLOCK right? see "man 1m setprivgrp" for details.
You can try creating the file /etc/privgroup which contain one single line text as
sybase RTPRIO MLOCK CHOWN
reboot server for that to take effect then try starting dataserver again and see.
Rgds,
Philip