dbTalk Databases Forums  

[Info-Ingres] upgradedb on distributed databases...locked up.

comp.databases.ingres comp.databases.ingres


Discuss [Info-Ingres] upgradedb on distributed databases...locked up. in the comp.databases.ingres forum.



Reply
 
Thread Tools Display Modes
  #1  
Old   
Martin Bowes
 
Posts: n/a

Default [Info-Ingres] upgradedb on distributed databases...locked up. - 12-16-2010 , 07:02 AM






Hi All,

I'm upgrading to Ingres10 on an installation with lots of distributed databases.

First gotcha was that upgradedb -all really bitched at the distributed databases. It was pretty convinced only the database owner should do upgradedb on those.

Second Gotcha was the database owner needed to be an ingres super user to get the necessary permission level to run upgradedb....
E_SC034F_NO_FLAG_PRIV User 'lust' attempted to specify invalid flag/option 'Createdb IIDBDB application code' while connecting to Ingres.

Gotcha number three was when finally I got the upgradedb to start...it promptly locks itself up on iistatistics when processing front end objects.

I decided to simply drop all the distributed databases and recreate them.....

Gotcha number 4...can't drop the database as its not the right version! At which point the air around me turned blue.

So I have to upgrade the database in order to drop it, only I cant do that upgrade completely as it locks up.

In the end I was forced to run upgradedb on the distributed databases, waitfor it to lock up and delete the upgrade out of the server. The database version was however upgraded by that point. Ergo I was able to then destroy the distributed database and recreate it using my maintenance scripts.

Not Happy.

Martin Bowes

Reply With Quote
  #2  
Old   
michaelnewport@yahoo.com
 
Posts: n/a

Default Re: upgradedb on distributed databases...locked up. - 12-16-2010 , 10:51 AM






On Dec 16, 2:02*pm, Martin Bowes <martin.bo... (AT) ctsu (DOT) ox.ac.uk> wrote:
Quote:
Hi All,

I'm upgrading to Ingres10 on an installation with lots of distributed databases.

First gotcha was that upgradedb -all really bitched at the distributed databases. It was pretty convinced only the database owner should do upgradedb on those.

Second Gotcha was the database owner needed to be an ingres super user toget the necessary permission level to run upgradedb....
E_SC034F_NO_FLAG_PRIV User 'lust' attempted to specify invalid flag/option 'Createdb IIDBDB application code' while connecting to Ingres.

Gotcha number three was when finally I got the upgradedb to start...it promptly locks itself up on iistatistics when processing front end objects.

I decided to simply drop all the distributed databases and recreate them.....

Gotcha number 4...can't drop the database as its not the right version! At which point the air around me turned blue.

So I have to upgrade the database in order to drop it, only I cant do that upgrade completely as it locks up.

In the end I was forced to run upgradedb on the distributed databases, wait for it to lock up and delete the upgrade out of the server. The databaseversion was however upgraded by that point. Ergo I was able to then destroy the distributed database and recreate it using my maintenance scripts.

Not Happy.

Martin Bowes
....well, if you ever get tired of db's, there are some vacancies in
the Oz cricket team....;-))

Reply With Quote
  #3  
Old   
Ingres Forums
 
Posts: n/a

Default Re: [Info-Ingres] upgradedb on distributed databases...locked up. - 12-17-2010 , 01:30 AM



Hi Martin,

As per Ingres10 distributed databases need to be upgraded by the
database owner.
The reason being that the Ingres super user does not necessarily have
access to the vnodes the local databases reside on.
So during the upgrade the distributed database can loose the tables
linked to tables on local databases.

The main upgrade process stayed the same, i.e. needs super user
privileges to upgrade iidbdb.
With no distributed databases present the upgrade can be run as usual
by the Ingres super user.
If distributed databases are detected during this upgrade all but these
databases get updated and the user is requested to upgrade the
distributed databases as the database owner.
This additional upgradedb run is meant to ensure you’re not loosing
tables.
With various distributed databases owned by various users I admit this
can be quite an overhead.

As to the iistatistics problem I'll be notifying Karl, but perhaps more
information might be needed on this one.

Regards
Manu


--
frima01

Reply With Quote
  #4  
Old   
Martin Bowes
 
Posts: n/a

Default Re: [Info-Ingres] upgradedb on distributed databases...locked up. - 12-17-2010 , 02:42 AM



Would that be the Australian Cricket Team which just dismissed England for 187?

Marty

-----Original Message-----
From: michaelnewport (AT) yahoo (DOT) com [mailto:michaelnewport (AT) yahoo (DOT) com]
Sent: 16 December 2010 16:51
To: info-ingres (AT) kettleriverconsulting (DOT) com
Subject: Re: [Info-Ingres] upgradedb on distributed databases...locked up.

On Dec 16, 2:02*pm, Martin Bowes <martin.bo... (AT) ctsu (DOT) ox.ac.uk> wrote:
Quote:
Hi All,

I'm upgrading to Ingres10 on an installation with lots of distributed databases.

First gotcha was that upgradedb -all really bitched at the distributed databases. It was pretty convinced only the database owner should do upgradedb on those.

Second Gotcha was the database owner needed to be an ingres super user to get the necessary permission level to run upgradedb....
E_SC034F_NO_FLAG_PRIV User 'lust' attempted to specify invalid flag/option 'Createdb IIDBDB application code' while connecting to Ingres.

Gotcha number three was when finally I got the upgradedb to start...it promptly locks itself up on iistatistics when processing front end objects.

I decided to simply drop all the distributed databases and recreate them....

Gotcha number 4...can't drop the database as its not the right version! At which point the air around me turned blue.

So I have to upgrade the database in order to drop it, only I cant do that upgrade completely as it locks up.

In the end I was forced to run upgradedb on the distributed databases, wait for it to lock up and delete the upgrade out of the server. The database version was however upgraded by that point. Ergo I was able to then destroy the distributed database and recreate it using my maintenance scripts.

Not Happy.

Martin Bowes
....well, if you ever get tired of db's, there are some vacancies in
the Oz cricket team....;-))
_______________________________________________
Info-Ingres mailing list
Info-Ingres (AT) kettleriverconsulting (DOT) com
http://ext-cando.kettleriverconsulti...fo/info-ingres

Reply With Quote
  #5  
Old   
michaelnewport@yahoo.com
 
Posts: n/a

Default Re: upgradedb on distributed databases...locked up. - 12-18-2010 , 06:30 AM



On Dec 17, 9:42*am, Martin Bowes <martin.bo... (AT) ctsu (DOT) ox.ac.uk> wrote:
Quote:
Would that be the Australian Cricket Team which just dismissed England for 187?

Marty







-----Original Message-----
From: michaelnewp... (AT) yahoo (DOT) com [mailto:michaelnewp... (AT) yahoo (DOT) com]
Sent: 16 December 2010 16:51
To: info-ing... (AT) kettleriverconsulting (DOT) com
Subject: Re: [Info-Ingres] upgradedb on distributed databases...locked up..

On Dec 16, 2:02�pm, Martin Bowes <martin.bo... (AT) ctsu (DOT) ox.ac.uk> wrote:
Hi All,

I'm upgrading to Ingres10 on an installation with lots of distributed databases.

First gotcha was that upgradedb -all really bitched at the distributed databases. It was pretty convinced only the database owner should do upgradedb on those.

Second Gotcha was the database owner needed to be an ingres super user to get the necessary permission level to run upgradedb....
E_SC034F_NO_FLAG_PRIV User 'lust' attempted to specify invalid flag/option 'Createdb IIDBDB application code' while connecting to Ingres.

Gotcha number three was when finally I got the upgradedb to start...it promptly locks itself up on iistatistics when processing front end objects.

I decided to simply drop all the distributed databases and recreate them....

Gotcha number 4...can't drop the database as its not the right version!At which point the air around me turned blue.

So I have to upgrade the database in order to drop it, only I cant do that upgrade completely as it locks up.

In the end I was forced to run upgradedb on the distributed databases, wait for it to lock up and delete the upgrade out of the server. The database version was however upgraded by that point. Ergo I was able to then destroy the distributed database and recreate it using my maintenance scripts.

Not Happy.

Martin Bowes

...well, if you ever get tired of db's, there are some vacancies in
the Oz cricket team....;-))
....thats the spirit....dont let the bastards grind you down...

Reply With Quote
  #6  
Old   
Martin Bowes
 
Posts: n/a

Default Re: [Info-Ingres] upgradedb on distributed databases...locked up. - 12-20-2010 , 04:45 AM



Gee they've gone pretty quiet now....

-----Original Message-----
From: michaelnewport (AT) yahoo (DOT) com [mailto:michaelnewport (AT) yahoo (DOT) com]
Sent: 18 December 2010 12:30
To: info-ingres (AT) kettleriverconsulting (DOT) com
Subject: Re: [Info-Ingres] upgradedb on distributed databases...locked up.

On Dec 17, 9:42*am, Martin Bowes <martin.bo... (AT) ctsu (DOT) ox.ac.uk> wrote:
Quote:
Would that be the Australian Cricket Team which just dismissed England for 187?

Marty







-----Original Message-----
From: michaelnewp... (AT) yahoo (DOT) com [mailto:michaelnewp... (AT) yahoo (DOT) com]
Sent: 16 December 2010 16:51
To: info-ing... (AT) kettleriverconsulting (DOT) com
Subject: Re: [Info-Ingres] upgradedb on distributed databases...locked up.

On Dec 16, 2:02�pm, Martin Bowes <martin.bo... (AT) ctsu (DOT) ox.ac.uk> wrote:
Hi All,

I'm upgrading to Ingres10 on an installation with lots of distributed databases.

First gotcha was that upgradedb -all really bitched at the distributed databases. It was pretty convinced only the database owner should do upgradedb on those.

Second Gotcha was the database owner needed to be an ingres super user to get the necessary permission level to run upgradedb....
E_SC034F_NO_FLAG_PRIV User 'lust' attempted to specify invalid flag/option 'Createdb IIDBDB application code' while connecting to Ingres.

Gotcha number three was when finally I got the upgradedb to start...it promptly locks itself up on iistatistics when processing front end objects.

I decided to simply drop all the distributed databases and recreate them....

Gotcha number 4...can't drop the database as its not the right version! At which point the air around me turned blue.

So I have to upgrade the database in order to drop it, only I cant do that upgrade completely as it locks up.

In the end I was forced to run upgradedb on the distributed databases, wait for it to lock up and delete the upgrade out of the server. The database version was however upgraded by that point. Ergo I was able to then destroy the distributed database and recreate it using my maintenance scripts.

Not Happy.

Martin Bowes

...well, if you ever get tired of db's, there are some vacancies in
the Oz cricket team....;-))
....thats the spirit....dont let the bastards grind you down...

_______________________________________________
Info-Ingres mailing list
Info-Ingres (AT) kettleriverconsulting (DOT) com
http://ext-cando.kettleriverconsulti...fo/info-ingres

Reply With Quote
  #7  
Old   
michaelnewport@yahoo.com
 
Posts: n/a

Default Re: upgradedb on distributed databases...locked up. - 12-29-2010 , 11:42 AM



On Dec 20, 11:45*am, Martin Bowes <martin.bo... (AT) ctsu (DOT) ox.ac.uk> wrote:
Quote:
Gee they've gone pretty quiet now....


.....about that career change....;-))

Reply With Quote
  #8  
Old   
Martin Bowes
 
Posts: n/a

Default Re: [Info-Ingres] upgradedb on distributed databases...locked up. - 12-30-2010 , 03:45 AM



One day a rooster, next day a feather duster!

Marty

-----Original Message-----
From: michaelnewport (AT) yahoo (DOT) com [mailto:michaelnewport (AT) yahoo (DOT) com]
Sent: 29 December 2010 17:43
To: info-ingres (AT) kettleriverconsulting (DOT) com
Subject: Re: [Info-Ingres] upgradedb on distributed databases...locked up.

On Dec 20, 11:45*am, Martin Bowes <martin.bo... (AT) ctsu (DOT) ox.ac.uk> wrote:
Quote:
Gee they've gone pretty quiet now....


.....about that career change....;-))
_______________________________________________
Info-Ingres mailing list
Info-Ingres (AT) kettleriverconsulting (DOT) com
http://ext-cando.kettleriverconsulti...fo/info-ingres

Reply With Quote
  #9  
Old   
Roy Hann
 
Posts: n/a

Default Re: [Info-Ingres] upgradedb on distributed databases...locked up. - 12-30-2010 , 04:38 AM



Martin Bowes wrote:

Quote:
One day a rooster, next day a feather duster!
So that chicken you served on Tuesday evening...?!

Still, tasty little fellas.

--
Roy

UK Ingres User Association Conference 2011 will be on Tuesday June 7 2011.
Put the date in your diary today.

Reply With Quote
Reply




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off



Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.