- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- STRMS stop reason - GlancePlus
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
тАО01-28-2007 06:02 PM
тАО01-28-2007 06:02 PM
STRMS stop reason - GlancePlus
configuration:
HP-UX B.11.11 not patched
application server rp5470 (4 CPU)
database server rp2470 (2 CPU)- Oracle 9.2.0.4
connection betwenn servers - network 1GB
Database server - all database process oracleagro are in STRMS stop reasn
Application server - all user proces are in STRMS stop reason, some in PRI.
Is this problem? How determine where is problem? How increase server performance with data on Oracle?
Thank You Ludek
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-29-2007 07:15 AM
тАО01-29-2007 07:15 AM
Re: STRMS stop reason - GlancePlus
So it is normal.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-29-2007 11:54 AM
тАО01-29-2007 11:54 AM
Re: STRMS stop reason - GlancePlus
Bill Hassell, sysadmin
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-29-2007 04:50 PM
тАО01-29-2007 04:50 PM
Re: STRMS stop reason - GlancePlus
I watch in GlancePlus network:
NET2: between application - database server for example Packet in rate = 3000 a Packet out rate = 2100. How determine rate in MB?
NET1: application server - user network for example Packet in rate = 120 a Packet out rate = 70.
Is it normal?
Thank You Ludek
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-30-2007 01:57 AM
тАО01-30-2007 01:57 AM
Re: STRMS stop reason - GlancePlus
>NET2: between application - database server for example Packet in rate = 3000 a Packet out rate = 2100. How determine rate in MB?
> NET1: application server - user network for example Packet in rate = 120 a Packet out rate = 70. Is it normal?
The rate in MB cannot be determined because tyhe packet size is variable (1 byte to 1500 bytes apx). 3000 packets per sec is fairly normal but networking is extremely tricky as a metric because it depends on both ends. A very fast server will look very slow if the other side of the connection is very slow. A 1Gb network connection will not perform at full speed when talking to a 10 Mb PC LAN card. Since it appears that the bulk of the traffic is between the app and database servers, that appears to be optimal.
> How increase server performance with data on Oracle?
There is no simple answer at all. The first step is PATCH!!! You cannot expect good performance (or reliability for that matter) without applying the current patch set. The next step is to analyze your Oracle stats (you do have StatsPak, correct?). The numbers may tell you that you have crippled your Oracle engine with far too little memory and may have to add 4-8Gb more RAM and increasing SGA significantly. Or the stats for your slowest SQL task show that there are missing or unbalanced indexes.
The vmstat command will tell you if RAM is too small: look at the po column. 2 digits (ie, 10-99) and especially 3 digits or more indicate a serious memory shortage. This will slow all processes to a crawl.
Bill Hassell, sysadmin