Veritas-bu

Re: [Veritas-bu] Anyway had NB_dbsrv just up and die on 6.5.1?

2008-04-16 16:28:59
Subject: Re: [Veritas-bu] Anyway had NB_dbsrv just up and die on 6.5.1?
From: "Rosenkoetter, Gabriel" <Gabriel.Rosenkoetter AT radian DOT biz>
To: mikemclain AT northwesternmutual DOT com, veritas-bu AT mailman.eng.auburn DOT edu
Date: Wed, 16 Apr 2008 16:06:53 -0400
That's good advice, and thanks for the pointer to the log file.

The error I've actually got, however, is:

[...]
I. 04/16 11:30:13. Starting checkpoint of "NBDB" (NBDB.db) at Wed Apr 16
2008 11
:30
I. 04/16 11:30:13. Finished checkpoint of "NBDB" (NBDB.db) at Wed Apr 16
2008 11
:30
E. 04/16 11:33:42. Fatal error: disk write failure
/usr/openv/db/data/NBDB.log
I. 04/16 14:40:57. Adaptive Server Anywhere Network Server Version
9.0.2.3567
I. 04/16 14:40:57.
I. 04/16 14:40:57. Copyright (c) 1989-2007 Sybase, Inc.
[...]

(The 14:40 and on being when I executed nbdbms_start_server.)

I knew I was going to be irritated by the fact that the NetBackup
"databases" were no longer under /usr/openv/netbackup/db, which I have
mounted as a separate (large) partition, but rather under /usr/openv/db,
which just falls through to /usr/openv, but I hadn't taken the time to
keep an eye on how large the non-images portion of the database was
getting.

You can figure out the rest, I'm sure.

--
gabriel rosenkoetter
Radian Group Inc, Unix/Linux/VMware Sysadmin / Backup & Recovery
gabriel.rosenkoetter AT radian DOT biz, 215 231 1556 


-----Original Message-----
From: mikemclain AT northwesternmutual DOT com
[mailto:mikemclain AT northwesternmutual DOT com] 
Sent: Wednesday, April 16, 2008 3:07 PM
To: Rosenkoetter, Gabriel; veritas-bu AT mailman.eng.auburn DOT edu
Subject: RE: [Veritas-bu] Anyway had NB_dbsrv just up and die on 6.5.1?

We have experienced it in 6.0 MP5, and it was usually caused by a need
for the Sybase ASA database (NBDB) to expand its cache more than the
default of 500M.

Check the /usr/openv/db/log/server.log for messages such as:

I. 03/08 17:11:53. Cache size adjusted to 509552K
I. 03/08 17:11:53. Cache size adjusted to 509816K
E. 03/08 17:11:53. Fatal error: memory exhausted
E. 03/08 17:11:53. Fatal error: memory exhausted
I. 03/08 17:11:53. Unable to synchronize due to external event - engine
shutting down


To stop the NB_dbsrv process run the following script:

     /usr/openv/db/bin/nbdbms_start_server -stop

To start the NB_dbsrv process run:

     /usr/openv/db/bin/nbdbms_start_server

The default max cache setting can be changed via the "-ch 500M"
parameter in the /usr/openv/var/global/server.conf file.   We upped ours
to 800M and haven't had the issue since.

HP-UX B.11.11 hostname (root /usr/openv/var/global) 265>cat server.conf
 -n VERITAS_NB_hostname
   -x tcpip(LocalOnly=YES;ServerPort=13785)  -gp 4096 -ct+ -gd DBA -gn
30 -gk DBA -gl DBA -ti 0 -c 25M -ch 800M -cl 25M -zl -os 1M  -o
/usr/openv/db//log/server.log
 -ud



-----Original Message-----
From: veritas-bu-bounces AT mailman.eng.auburn DOT edu
[mailto:veritas-bu-bounces AT mailman.eng.auburn DOT edu] On Behalf Of
Rosenkoetter, Gabriel
Sent: Wednesday, April 16, 2008 1:34 PM
To: veritas-bu AT mailman.eng.auburn DOT edu
Subject: [Veritas-bu] Anyway had NB_dbsrv just up and die on 6.5.1?

vmoprcmd -d yields "database server is down", similar responses for
anything else that would want to hit EMM. Google pointed up
http://seer.entsupport.symantec.com/docs/287092.htm, but I'm not having
exactly that same problem, because NB_dbsrv actualy is NOT running, and
today's vault-managed hot catalog backup failed when it tried to connect
too.

Is it theoretically safe just to start NB_dbsrv back up again, like I
would have before with bprd and bpsched? Looking at a system that still
has a running instance, it looks like there're supposed to be a whole
mess of command line arguments...

--
gabriel rosenkoetter
Radian Group Inc, Unix/Linux/VMware Sysadmin / Backup & Recovery
gabriel.rosenkoetter AT radian DOT biz, 215 231 1556 



_______________________________________________
Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu

This e-mail and any attachments may contain confidential information of
Northwestern Mutual. If you are not the intended recipient of this
message, be aware that any disclosure, copying, distribution or use of
this e-mail and any attachments is prohibited. If you have received this
e-mail in error, please notify Northwestern Mutual immediately by
returning it to the sender and delete all copies from your system.
Please be advised that communications received via the Northwestern
Mutual Secure Message Center are secure. Communications that are not
received via the Northwestern Mutual Secure Message Center may not be
secure and could be observed by a third party. Thank you for your
cooperation.



_______________________________________________
Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu

<Prev in Thread] Current Thread [Next in Thread>