- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: Allbase connect DBERR 14031
Operating System - HP-UX
1753259
Members
5649
Online
108792
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
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
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
тАО11-25-2003 07:18 AM
тАО11-25-2003 07:18 AM
Allbase connect DBERR 14031
When we try to connect to an Allbase database we get a DBERR 14031. Any ideas on how to overcome this problem?
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-25-2003 02:27 PM
тАО11-25-2003 02:27 PM
Re: Allbase connect DBERR 14031
Hi,
You may find this document helps:
http://itrc.hp.com/cki/bin/doc.pl/screen=ckiSearchResults?mode=id&searchString=KBRC00009784
Do keep me posted.
You may find this document helps:
http://itrc.hp.com/cki/bin/doc.pl/screen=ckiSearchResults?mode=id&searchString=KBRC00009784
Do keep me posted.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-25-2003 06:48 PM
тАО11-25-2003 06:48 PM
Re: Allbase connect DBERR 14031
having too many allbase processes running can cause shared memory problems. (Especially because daemons still run about 30 secs after job has been finished).
I had this problem as well. HP didn't find a solution, then.
What I do is to controll shared memory access myself in a shell programm.
I check number of SM accesses.
(ipcs -m ....)
only if number of these jobs is smaller than a predifined amount (depending on your hardware and kernel parameters) then the next allbase programm is being fired.
We run lots of allbase systems with lots of users and since then no problems anymore.
Werner
I had this problem as well. HP didn't find a solution, then.
What I do is to controll shared memory access myself in a shell programm.
I check number of SM accesses.
(ipcs -m ....)
only if number of these jobs is smaller than a predifined amount (depending on your hardware and kernel parameters) then the next allbase programm is being fired.
We run lots of allbase systems with lots of users and since then no problems anymore.
Werner
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-25-2003 08:43 PM
тАО11-25-2003 08:43 PM
Re: Allbase connect DBERR 14031
To explain more the problem arose when we had to reboot the machine due to a scsi problem. We were unable to take our processes down cleanly and hence we ended up with the allbase problem.
The problem was solved with the following answer from HP:
***DO NOT TRY THIS UNLESS IT IS YOUR LAST RESORT ****
this procedure reset's the address of where the shared memory segment should start.
Obviously it is not a first resort. the ipcs process should be followed before trying this.
Where /hertznet/allbase/htznet2/HTZNET1 is the path to your dbcon file.
# adb -w /hertznet/allbase/htznet2/HTZNET1
1a4?X <----- type this, no prompt in adb
1A4: 808 <----- adb returns this location and contents
1a4?W -1 <----- type this, offset, write and replace with -1
1A4: 808 = -1 <----- adb returns this >!]
The problem was solved with the following answer from HP:
***DO NOT TRY THIS UNLESS IT IS YOUR LAST RESORT ****
this procedure reset's the address of where the shared memory segment should start.
Obviously it is not a first resort. the ipcs process should be followed before trying this.
Where /hertznet/allbase/htznet2/HTZNET1 is the path to your dbcon file.
# adb -w /hertznet/allbase/htznet2/HTZNET1
1a4?X <----- type this, no prompt in adb
1A4: 808 <----- adb returns this location and contents
1a4?W -1 <----- type this, offset, write and replace with -1
1A4: 808 = -1 <----- adb returns this >!]
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