- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Logical Volume used by Sybase
Operating System - HP-UX
1752567
Members
5161
Online
108788
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Discussions
back
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
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- 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
10-25-2004 01:40 PM
10-25-2004 01:40 PM
Logical Volume used by Sybase
Hi
I found that there are some files which was created by sybase are not displayed on the Volume Group screen of SAM.
1. In this case, can I know which logical volume or Physical Device it's actually using ?
2. Say, if I want to create another DB device for my sybase, what procedure I've to perform on the OS and what info I've to give sybase ?
Many Thanks
Daedalus
============================================
# pwd
/dev/vgtfxase
# ll
total 0
brw-r----- 1 root sys 64 0x01000e Mar 12 2003 et8data
brw-r----- 1 root sys 64 0x01000f Mar 12 2003 et8log
brw-r----- 1 sybase sybase 64 0x010004 Jan 17 2001 et8r1
brw------- 1 sybase sybase 64 0x01000d Sep 19 2001 et8r10
brw-r----- 1 sybase sybase 64 0x010005 Jan 17 2001 et8r2
brw-r----- 1 sybase sybase 64 0x010006 Jan 17 2001 et8r3
brw-r----- 1 sybase sybase 64 0x010007 Jan 17 2001 et8r4
brw-r----- 1 sybase sybase 64 0x010008 Jan 17 2001 et8r5
brw-r----- 1 sybase sybase 64 0x010009 Jan 17 2001 et8r6
brw-r----- 1 sybase sybase 64 0x01000a Jan 17 2001 et8r7
brw-r----- 1 sybase sybase 64 0x01000b Apr 2 2001 et8r8
brw-r----- 1 sybase sybase 64 0x01000c Apr 2 2001 et8r9
crw-rw-rw- 1 root sys 64 0x010000 Jan 12 2001 group
brw-r----- 1 root sys 64 0x010001 Sep 8 2001 lvol1
brw-r----- 1 root sys 64 0x010002 Jan 12 2001 lvol2
brw------- 1 root sys 64 0x010013 Apr 9 2001 lvol3
brw-r----- 1 sybase sybase 64 0x010003 Jan 17 2001 rawvol
crw-r----- 1 sybase sybase 64 0x01000e Mar 12 2003 ret8data
crw-r----- 1 sybase sybase 64 0x01000f Mar 12 2003 ret8log
crw-r----- 1 sybase sybase 64 0x010004 Jan 17 2001 ret8r1
crw------- 1 sybase sybase 64 0x01000d Sep 19 2001 ret8r10
crw-r----- 1 sybase sybase 64 0x010005 Jan 17 2001 ret8r2
crw-r----- 1 sybase sybase 64 0x010006 Jan 17 2001 ret8r3
crw-r----- 1 sybase sybase 64 0x010007 Jan 17 2001 ret8r4
crw-r----- 1 sybase sybase 64 0x010008 Jan 17 2001 ret8r5
crw-r----- 1 sybase sybase 64 0x010009 Jan 17 2001 ret8r6
crw-r----- 1 sybase sybase 64 0x01000a Jan 17 2001 ret8r7
crw-r----- 1 sybase sybase 64 0x01000b Apr 2 2001 ret8r8
crw-r----- 1 sybase sybase 64 0x01000c Apr 2 2001 ret8r9
crw-r----- 1 sybase sybase 64 0x010001 Jan 12 2001 rlvol1
crw-r----- 1 sybase sybase 64 0x010002 Jan 12 2001 rlvol2
crw------- 1 sybase sybase 64 0x010013 Apr 9 2001 rlvol3
crw-r----- 1 sybase sybase 64 0x010003 Jan 17 2001 rrawvol
============================================
I found that there are some files which was created by sybase are not displayed on the Volume Group screen of SAM.
1. In this case, can I know which logical volume or Physical Device it's actually using ?
2. Say, if I want to create another DB device for my sybase, what procedure I've to perform on the OS and what info I've to give sybase ?
Many Thanks
Daedalus
============================================
# pwd
/dev/vgtfxase
# ll
total 0
brw-r----- 1 root sys 64 0x01000e Mar 12 2003 et8data
brw-r----- 1 root sys 64 0x01000f Mar 12 2003 et8log
brw-r----- 1 sybase sybase 64 0x010004 Jan 17 2001 et8r1
brw------- 1 sybase sybase 64 0x01000d Sep 19 2001 et8r10
brw-r----- 1 sybase sybase 64 0x010005 Jan 17 2001 et8r2
brw-r----- 1 sybase sybase 64 0x010006 Jan 17 2001 et8r3
brw-r----- 1 sybase sybase 64 0x010007 Jan 17 2001 et8r4
brw-r----- 1 sybase sybase 64 0x010008 Jan 17 2001 et8r5
brw-r----- 1 sybase sybase 64 0x010009 Jan 17 2001 et8r6
brw-r----- 1 sybase sybase 64 0x01000a Jan 17 2001 et8r7
brw-r----- 1 sybase sybase 64 0x01000b Apr 2 2001 et8r8
brw-r----- 1 sybase sybase 64 0x01000c Apr 2 2001 et8r9
crw-rw-rw- 1 root sys 64 0x010000 Jan 12 2001 group
brw-r----- 1 root sys 64 0x010001 Sep 8 2001 lvol1
brw-r----- 1 root sys 64 0x010002 Jan 12 2001 lvol2
brw------- 1 root sys 64 0x010013 Apr 9 2001 lvol3
brw-r----- 1 sybase sybase 64 0x010003 Jan 17 2001 rawvol
crw-r----- 1 sybase sybase 64 0x01000e Mar 12 2003 ret8data
crw-r----- 1 sybase sybase 64 0x01000f Mar 12 2003 ret8log
crw-r----- 1 sybase sybase 64 0x010004 Jan 17 2001 ret8r1
crw------- 1 sybase sybase 64 0x01000d Sep 19 2001 ret8r10
crw-r----- 1 sybase sybase 64 0x010005 Jan 17 2001 ret8r2
crw-r----- 1 sybase sybase 64 0x010006 Jan 17 2001 ret8r3
crw-r----- 1 sybase sybase 64 0x010007 Jan 17 2001 ret8r4
crw-r----- 1 sybase sybase 64 0x010008 Jan 17 2001 ret8r5
crw-r----- 1 sybase sybase 64 0x010009 Jan 17 2001 ret8r6
crw-r----- 1 sybase sybase 64 0x01000a Jan 17 2001 ret8r7
crw-r----- 1 sybase sybase 64 0x01000b Apr 2 2001 ret8r8
crw-r----- 1 sybase sybase 64 0x01000c Apr 2 2001 ret8r9
crw-r----- 1 sybase sybase 64 0x010001 Jan 12 2001 rlvol1
crw-r----- 1 sybase sybase 64 0x010002 Jan 12 2001 rlvol2
crw------- 1 sybase sybase 64 0x010013 Apr 9 2001 rlvol3
crw-r----- 1 sybase sybase 64 0x010003 Jan 17 2001 rrawvol
============================================
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-25-2004 05:12 PM
10-25-2004 05:12 PM
Re: Logical Volume used by Sybase
determine which logical volume is being used by sybase. If its a filesystem you can see whats going on as far as which disks as follows:
lvdisplay -v /dev/vg01/et8r1
just put in a real logical volume name.
If however sybase is using raw disk, you need to use a sybase utilty to display contents.
Based on the fact that I admin Software AG Adabas, a database that uses raw or cooked filesystems, I would say that the entire volume group is devoted to sybase.
the lvdisplay command will tell you what disks its using. The database utility will tell you a little more.
SEP
lvdisplay -v /dev/vg01/et8r1
just put in a real logical volume name.
If however sybase is using raw disk, you need to use a sybase utilty to display contents.
Based on the fact that I admin Software AG Adabas, a database that uses raw or cooked filesystems, I would say that the entire volume group is devoted to sybase.
the lvdisplay command will tell you what disks its using. The database utility will tell you a little more.
SEP
Steven E Protter
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP