I found an interesting message while upgrading from ingres 2.6 to 9.2

Warning: UPGRADEDB 11 Procedures, 10 recreated.
Warning: UPGRADEDB Errors occurred upgrading trees for database live.
Upgrading Front End objects...
************************************************** **************
Processing of database 'live' completed
live will be promoted to II 9.2.0 status.
************************************************** **************
Warning: UPGRADEDB had errors upgrading trees.

After a bit of digging around on Ingres Support Channel I found a reference
to log files in a directory:
$II_SYSTEM/files/upgradedb. The error logs are here in detail for all
databases

ls -l /home/ingres/files/upgradedb/ingres
-rw-rw-rw- 1 ingres ingres 644216 Feb 25 09:13 upgrade.dbg
-rw-rw-rw- 1 ingres ingres 70030 Feb 25 09:13 upgrade.log
...
-rw-rw-r-- 1 ingres ingres 16036 Feb 25 08:07 live.i01
-rw-rw-r-- 1 ingres ingres 15732 Feb 25 08:07 live.o01
...

The error was a failure in re-creating a procedure which referenced a table
which had been dropped some time ago.

--
Paul White
Shift Seven Solutions

Paul,

In the Migration Guide, in the section titled "How You Upgrade Using the
Upgradedb Utility" step 4 says "[Each DB including the iidbdb] Clean the
database". Did you do this?

"Clean the database" has these instructions:

To ensure the integrity of the system catalogs, issue the following
commands:
sysmod dbname
verifydb -mreport -sdbname dbname -odbms_catalog
.....

John


________________________________

From: info-ingres-bounces (AT) kettleriver...ting (DOT) com
[mailto:info-ingres-bounces (AT) kettleriverconsulting (DOT) com] On Behalf Of Paul
White
Sent: Wednesday, 25 February 2009 10:14 AM
To: info-ingres (AT) kettleriverconsulting (DOT) com
Subject: [Info-Ingres] ingres is environmentally friendly


I found an interesting message while upgrading from ingres 2.6 to 9.2

Warning: UPGRADEDB 11 Procedures, 10 recreated.
Warning: UPGRADEDB Errors occurred upgrading trees for database live.
Upgrading Front End objects...
************************************************** **************
Processing of database 'live' completed
live will be promoted to II 9.2.0 status.
************************************************** **************
Warning: UPGRADEDB had errors upgrading trees.


After a bit of digging around on Ingres Support Channel I found a
reference to log files in a directory:
$II_SYSTEM/files/upgradedb. The error logs are here in detail for all
databases

ls -l /home/ingres/files/upgradedb/ingres
-rw-rw-rw- 1 ingres ingres 644216 Feb 25 09:13 upgrade.dbg
-rw-rw-rw- 1 ingres ingres 70030 Feb 25 09:13 upgrade.log
...
-rw-rw-r-- 1 ingres ingres 16036 Feb 25 08:07 live.i01
-rw-rw-r-- 1 ingres ingres 15732 Feb 25 08:07 live.o01
...

The error was a failure in re-creating a procedure which referenced a
table which had been dropped some time ago.

--
Paul White
Shift Seven Solutions

Hi there John.

I took a shortcut in this case since it is a test installation.
Sysmod/verifydb run every week and have been reporting this error for 2-3
years and I have been ignoring this error because it was not causing
problems:

S_DU16E9_UNEXPECTED_DBP_PERMS Database procedure
'ingres'.'stock_detail_aud' has permits defined on it even though it is
marked non-grantable.
S_DU0251_MARK_DBP_DORMANT Recommended action is to mark the database
procedure (and all database procedures dependent on it) dormant.
This will also result in destruction of permits on newly dormant database
procedures.
S_DU17FF_FIX_INTERACTIVELY VERIFYDB cannot perform the recommended
action u
nless the RUNINTERACTIVE mode is selected.
Paul



On Wed, Feb 25, 2009 at 9:30 AM, John Dennis <John.Dennis (AT) ingres (DOT) com> wrote:


--
Paul White
Shift Seven Solutions