Errors when running db_stat from command line

Question

Hi,
I'm trying to use db_stat at the command line to generate statistics.
However, I keep getting errors. I cannot use the db->stat call
because this is to be done at a customer site using their existing binary.
Note that the call to db_stat -m fails, while the call to db_stat -d <dbname>
prints an error/warning then appears to succeed.
Most likely, there is some usage subtlety that I have missed.
Any suggestions about what I have done wrong?
I am using BDB 4.6.21 on Windows. Databases are created inside a
db environment.
Here is a transcript:
C:\Program Files\SonicWallES\PluginDefault\collab\data>dir __*
Volume in drive C has no label.
Volume Serial Number is 7084-88E3
Directory of C:\Program Files\SonicWallES\PluginDefault\collab\data
08/07/2008 07:11 PM 24,576 __db.001
08/07/2008 07:11 PM 65,536 __db.002
08/07/2008 07:11 PM 270,336 __db.003
08/07/2008 07:11 PM 499,712 __db.004
4 File(s) 860,160 bytes
0 Dir(s) 2,177,224,704 bytes free
C:\Program Files\SonicWallES\PluginDefault\collab\data>"C:\Program Files\SonicWallES\utilities\bdb\db_stat.exe" -m
db_stat.exe: __db.001: unable to find environment
db_stat.exe: DB_ENV->open: No such file or directory
C:\Program Files\SonicWallES\PluginDefault\collab\data>dir ..
Volume in drive C has no label.
Volume Serial Number is 7084-88E3
Directory of C:\Program Files\SonicWallES\PluginDefault\collab
08/18/2008 12:44 PM <DIR> .
08/18/2008 12:44 PM <DIR> ..
08/07/2008 10:09 PM 2,646,016 c_thumbprint.db
09/05/2008 03:08 PM <DIR> data
07/16/2008 06:43 PM <DIR> dbs
08/07/2008 10:09 PM 42,131,456 e_thumbprint.db
08/07/2008 10:09 PM 10,485,760 f_thumbprint.db
08/07/2008 10:09 PM 5,226,496 g_thumbprint.db
08/07/2008 10:09 PM 41,869,312 h_thumbprint.db
08/07/2008 10:09 PM 41,926,656 i_thumbprint.db
08/09/2008 02:47 AM <DIR> old_data
08/07/2008 10:09 PM 10,633,216 p_thumbprint.db
08/14/2008 05:26 PM 1,749 redirect.xml
09/08/2008 04:12 PM <DIR> sn_data
08/07/2008 10:09 PM 78,725,120 t_thumbprint.db
08/07/2008 10:10 PM 42,074,112 v_thumbprint.db
08/07/2008 10:50 PM 335,790,080 x_thumbprint.db
11 File(s) 611,509,973 bytes
6 Dir(s) 2,177,224,704 bytes free
C:\Program Files\SonicWallES\PluginDefault\collab\data>"C:\Program Files\SonicWallES\utilities\bdb\db_stat.exe" -d ..\x_thumbprint.db
db_stat.exe: __db.001: unable to find environment
Mon Sep 08 16:17:01 2008 Local time
61561 Hash magic number
9 Hash version number
Little-endian Byte order
Flags
8192 Underlying database page size
0 Specified fill factor
4882732 Number of keys in the database
4882732 Number of data items in the database
24548 Number of hash buckets
35M Number of bytes free on bucket pages (82% ff)
0 Number of overflow pages
0 Number of bytes free in overflow pages (0% ff)
8220 Number of bucket overflow pages
32M Number of bytes free in bucket overflow pages (51% ff)
0 Number of duplicate pages
0 Number of bytes free in duplicate pages (0% ff)
1 Number of pages on the free list

Answer 1

If I'm reading your code correctly, you're starting a Korn shell session, then executing your C shell script as if you were at at the session window's prompt. If that is correct, you haven't caused your standard out (stdout) to hit ENTER yet. I'm not an expert, but I hope this works for you.
Your code:
Process Child = runtime.exec("/usr/bin/ksh"); // execute command
                        BufferedWriter outCommand = new BufferedWriter(new OutputStreamWriter(Child.getOutputStream()));
                        outCommand.write("/home/mypath/tesh.csh");
                        outCommand.flush();I think you need to enter one extra line before the flush():
Process Child = runtime.exec("/usr/bin/ksh"); // execute command
                        BufferedWriter outCommand = new BufferedWriter(new OutputStreamWriter(Child.getOutputStream()));
                        outCommand.write("/home/mypath/tesh.csh");
                        outCommand.newLine();  // hit ENTER
                        outCommand.flush();P.S. If you're running this script and your Java program from the same UNIX machine, you could just execute the shell script inside the runtime.exec() call.