Warren,
I was just searching through era net on the prostrct command myself, and didn't get very far. Like Wayne said, backup what you have right now.
Here is one article that may give you some help: Click here
http://www.progress.com/services/support/cgi-bin/techweb-kbase.cgi/webkb.html?kbid=2077&keywords=database%20is%20damaged or see below.
Kbase Id:
2077
Title:
How to run dbscan with database repair utility: dbrpr
How to run dbscan with database repair utility: dbrpr
910730-sal03
INTRODUCTION:
=============
This Progress Software Technical Support Knowledgebase entry describes
how to run the database utility (dbrpr) to scan your database for bad
records and blocks.
WHY YOU NEED TO DO THIS:
========================
If you receive errors that indicate the there has been database
corruption or damage. (Errors include 1124, 355, 18, 49, etc.) Or if
you have had disk or hardware problems that may have damaged the
database and structures in any way.
PROCEDURAL APPROACH:
====================
The database repair utility is a function of proutil and the _proutil
executable and you execute it like any other proutil function.
However,
there are a number of prerequisites to using the utility:
1. ALWAYS HAVE A CURRENT BACKUP OF THE DATABASE.
2. The server must be down and the database not in use.
3. If possible, bring the database into sync by having a normal
shutdown where there are no incomplete transactions that are to be
backed out.
4. The next step is to truncate the bi file. This step should not
be skipped. You need to attempt to truncate the bi file. If there
is bi corruption, you will receive an error during the truncation,
At this time, you can decide to skip recovery and use the -F
(Force Access) option to start dbrpr. The -F option bypasses the
transaction recovery, which can compromise database integrity.
To execute the Database repair utility, use the following command:
prior to 6.3F: proutil <database name> -C dbrpr | tee dbrpr.out
6.3F or higher: proutil <database name> -C dbrpr > <filename>
On BTOS/CTOS platforms, use the command:
PROGRESS Utilities
Database Name <database name>
Utilitiy Name -C dbrpr
[Options] >file.out -F
On VMS, use the command:
DEFINE SYS$OUTPUT filename
PROGRESS/UTIL=DBRPR <database name>
DEASSIGN SYS$OUTPUT
On DOS,NLM and WINDOWS: Create a text file and in this file you need
to enter a list of responses to menu prompts from the scan program.
For Verssion 6, use:1(return) 1(return) 4(return) G(return) Q(return
For Version 7 or 8, use:
1(return) 1(return) 4(return) G(return) N(return) Q(return)
If this is Multi-vol you need to add ALL after G
Then at a DOS prompt type:
_proutil dbname -C dbrpr < text-file-you-created > file.out
where "file.out" represents the file where the output of the scan will
be written.
The syntax to use for the text-file-you-created would be:
Version 6 Version 7 Version 8
1^M 1^M 1^M
1^M 1^M 1^M
4^M 4^M 4^M
G^M G^M G^M
Q^M ^M ^M
Q^M ^M
Q^M
These formats are examples if you wished to do options 1,1,4.
The Version of your PROGRESS Software will display followed by
the main menu:
DATABASE REPAIR MENU
--------------------
1. Database Scan Menu
2.
3.
4. Dump Block
5.
6.
7.
8.
Q. Quit
Choice: _
In regards to this discussion, the only options of interest
are 1, 4, and Q.
Option 1. Database Scan Menu
This option allows you to test the format of database blocks
and records. To continue, type 1 and press enter to select
option 1. The following menu appears:
DATABASE SCAN MENU
------------------
1. Report Bad Blocks
2.
3.
4. Report Bad Records
5.
6.
7.
8.
G. GO
Of the eight choices only 1 and 4 are of interest to database
scans. The menu allows you to select as many choices as you
want then runs all the choices together. When you select a
number (1 or 4 in this case) it is highlighted and you can
select more choices. Select another choice, or deselect
your choice by reselecting it. When all the choices you want
to run are marked, enter G (Go) to execute the selected items.
The items process in the same order as the Menu lists them, 1
thru 8 (in this case 1 then 4 will execute).
Your selections depend on what you want to scan, the type
of error received, and time. The first option is the fastest,
but only scans the Recid of the Block from the last block to
the first which is the master block. An example of an error
determining what to run is the 1124 error, which indicates
that one of the block recids is incorrect, therefore option
1 would be sufficient. The longer but more comprehensive scan
is to run both 1 (Block Recid) and 4 record scan. The record
scan checks all records and reports any inconsistencies.
Following is the sample output from two separate scans from
Version 5 and Version 6. The first is a Version 6 scan for
blocks only and the second is for Version 5 with options 1
and 4 selected. The Version 5.2I and higher and Version 6
database repair are very similiar and there is no need to
distinquish the difference when running them. The sample
output is what you would see in the output file after the
scan runs. If you run the scan without the redirection
(> filename), the output displays on the screen.
A sample output from the Version 6 demo database with a
bad block address:
PROGRESS Version 6.2F03 as of Sun Sep 23 20:00:10 EDT 1990
Scanning /users/demo.db
From dbkey 6144 to dbkey 32
Can't find Blk 128 (4096)
Comments: The scan is from last 6144 to first recid 32 (Master
block). This report shows that the scan could not find a block
128, at this point you should contact Progress Technical Support
for information on how to approach the problem.
A sample output from the Version 5 demo database running both
database block and record scan, labeled 1 and 2 respectively.
There are very few changes between Version 5.2I and higher and
Version 6 database repair.
PROGRESS Version 5.2I as of Thu Feb 15 17:03:14 EST 1990
1 Scanning /users/demo.db
From dbkey 4096 to dbkey 32
2 Scanning /users/demo.db
From dbkey 4096 to dbkey 32
Bad File Number:-6 Len:255 dbkey:995
Total Records: 1202
Continues: 22
# Dumped: 0
COMMENTS: This scan is again on a demo database with both record
and block scans. The first entry (1) is the block scan that was
clean, all block recids were correct. The second scan (2) was a
record scan that showed a bad file number in a record. This is a
case where the actual record with recid (995) has been damaged.
While at the main menu there may be another piece of data that the
Technical rep may request and that is that you give them hex dumps
HOW TO DUMP A DATABASE BLOCK USING DBRPR
You may be requested to dump a block for analysis by Progress
Technical Support. If this is the case, here are the steps to
follow.
You will again see this main menu when you enter the appropriate
dbrpr startup command for your system.
DATABASE REPAIR MENU
--------------------
1. Database Scan Menu
2. Test One or More Indicies
3. Remove Bad Record Fragment
4. Dump Block
5. Load Block
6. Copy Bytes Between Files
7. Load RM Dump File
8. Reformat Block to a Free Block
Q. Quit
Choice:
Select Option 4, Dump Block. This will prompt you to enter a dbkey,
as shown below. After you enter the dbkey, the block will be dumped
to a file called <dbkey>.dmp.
DATABASE REPAIR MENU
--------------------
1. Database Scan Menu
2. Test One or More Indicies
3. Remove Bad Record Fragment
4. Dump Block
5. Load Block
6. Copy Bytes Between Files
7. Load RM Dump File
8. Reformat Block to a Free Block
Q. Quit
Choice: 4
Enter dbkey: 3200
After all requested scans and dumps are complete you should then
call Progress Technical Support to help you with further database
repair utilities and how to proceed depending on the error
messages.
NOTE: It is important to get feedback from Progress Technical
Support before attempting to repair a database. The dbrpr utility
is an unsupported tool because of the damage that can be caused by
using the tool incorrectly. Every precaution should be taken
before using this tool. It also needs to be known that restoring
a good backup is recommended before dbrpr.
To exit after the scan is complete, select Quit from the main menu
(The Database Repair Menu).
ONLINE PROCEDURES OR UTILITIES:
===============================
PROUTIL
REFERENCES TO WRITTEN DOCUMENTATION:
====================================
There is no written documentation at the current time.
REFERENCES TO OTHER RELATED KBASES:
===================================
Progress Knowledge Base entry # 19439
Title: Database corruption in memory which cause (1124)(1152) errs.
Progress Software Technical Support Note # 2077
DISCLAIMER
The origins of this information may be internal or external to Progress Software Corporation. Progress Software Corporation makes all reasonable efforts to verify this information. However, the information provided in this document is for your information only. Progress Software Corporation makes no explicit or implied claims to the validity of this information.
Any trademarks referenced in this document are the property of their respective owners. Consult your product manuals for complete trademark information.
top home | business solutions | products | tech support | services | partner info
Copyright © 2000 Progress Software Corporation.
All Rights Reserved.
----- Original Message -----
From: Eddy, Warren
To: 'vantage@yahoogroups.com'
Sent: Sunday, April 29, 2001 2:49 PM
Subject: RE: [Vantage] Vantage error
Wayne;
I already tried prostrct -repair, it didn't help. Thanks for the clue on
checking for disk errors thru NT; I'm trying that now. Other than that not
sure what can be done.
Thanks
Warren R. Eddy
Information Services Manager
National Tube Form, LLC
Phone: (219) 478-2363 ext 217
Fax: (219) 478-1043
Warren.Eddy@...
-----Original Message-----
From: Wayne Cox [mailto:wmc@...]
Sent: Sunday, April 29, 2001 1:00 PM
To: vantage@yahoogroups.com
Subject: Re: [Vantage] Vantage error
At 11:54 AM 4/29/2001 -0500, you wrote:
>I just installed patch 44 for progress, we're on Progress 9.0B, and it
>requires a server re-boot. When I tried to bring up pro-control my
>production DB wouldn't start. The event viewer says the DB is damaged.
I'd run a regular NT "check for errors" on your disks. Then make a backup
of all the DB files as they are now. Beyond that... never had to try any
recovery. But I think prostrct -repair is able to correct some of the
common problems. Have you checked around on eranet?
-Wayne
To access the Files Section of our Yahoo!Group for Report Builder and
Crystal Reports and other 'goodies', please go to:
http://groups.yahoo.com/group/vantage/files/. Note: You must have already
linked your email address to a yahoo id to enable access.
Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
Yahoo! Groups Sponsor
To access the Files Section of our Yahoo!Group for Report Builder and Crystal Reports and other 'goodies', please go to: http://groups.yahoo.com/group/vantage/files/. Note: You must have already linked your email address to a yahoo id to enable access.
Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.
[Non-text portions of this message have been removed]