System Down, DB won't start

Posted by James Palmer on 17-Dec-2014 16:39

Evening all - some assistance would be gratefully received. We had a DB crash earlier, now whenever I try to restart the db (using OE Management) I get 

                Wed Dec 17 22:37:49 2014
[2014/12/17@22:37:49.939+0000] P-7336       T-7416  I          : (451)   Replication Status session begin for Inencoadmin on batch. 
[2014/12/17@22:37:49.939+0000] P-7336       T-7416  I          : (7129)  Usr 0 set name to NETWORKS\Inencoadmin. 
[2014/12/17@22:37:50.052+0000] P-7336       T-7416  I          : (334)   Replication Status session end. 


We're running 11.2.1 (32bit) on Windows 2003 Server. We have replication plus enabled, it's the source DB. 

All Replies

Posted by Libor Laubacher on 17-Dec-2014 16:49

This is not from start. This a check done by adminserver/oem for replication database.
 
Are you saying nothing happens when you click on start db ?
What happens when you trying starting it from command line ?
 
[collapse]
From: James Palmer [mailto:bounce-jdpjamesp@community.progress.com]
Sent: Wednesday, December 17, 2014 11:40 PM
To: TU.OE.RDBMS@community.progress.com
Subject: [Technical Users - OE RDBMS] System Down, DB won't start
 
Thread created by James Palmer

Evening all - some assistance would be gratefully received. We had a DB crash earlier, now whenever I try to restart the db (using OE Management) I get 

                Wed Dec 17 22:37:49 2014
[2014/12/17@22:37:49.939+0000] P-7336       T-7416  I          : (451)   Replication Status session begin for Inencoadmin on batch. 
[2014/12/17@22:37:49.939+0000] P-7336       T-7416  I          : (7129)  Usr 0 set name to NETWORKS\Inencoadmin. 
[2014/12/17@22:37:50.052+0000] P-7336       T-7416  I          : (334)   Replication Status session end. 


We're running 11.2.1 (32bit) on Windows 2003 Server. We have replication plus enabled, it's the source DB. 

Stop receiving emails on this subject.

Flag this post as spam/abuse.

[/collapse]

Posted by James Palmer on 17-Dec-2014 16:52

Exactly - that's what was confusing me. I've found the problem. Literally just worked it out. A mis-spellt parameter in Extra Parameters. As simple as that.

Posted by Libor Laubacher on 17-Dec-2014 17:01

Good man J
 
[collapse]
From: James Palmer [mailto:bounce-jdpjamesp@community.progress.com]
Sent: Wednesday, December 17, 2014 11:53 PM
To: TU.OE.RDBMS@community.progress.com
Subject: RE: [Technical Users - OE RDBMS] System Down, DB won't start
 
Reply by James Palmer

Exactly - that's what was confusing me. I've found the problem. Literally just worked it out. A mis-spellt parameter in Extra Parameters. As simple as that.

Stop receiving emails on this subject.

Flag this post as spam/abuse.

[/collapse]

Posted by James Palmer on 19-Dec-2014 03:40

I consider this a bug. What do others think?

If I take a copy of Sports2000 and proserve it from proenv with the PF below I get an error due to the case of -BPMax. 

-db C:\Database\s2k\s2k.db
-B 75000
-minport 3000
-maxport 5000
-lruskips 50
-B2 600
-BPmax 100
-Mxs 25
-L 8192
-hash 13063
-spin 24000
-shmsegsize 512
-bibufs 20
-aibufs 20
-Ma 5
-Mn 6
-Mi 1
-n 50
-Mm 4096
-Mpb 5
-omsize 2660


The error is

C:\Database\s2k>proserve -pf s2k.pf
OpenEdge Release 11.2.1 as of Mon Apr 29 19:26:32 EDT 2013
08:35:19 SERVER   : You have not supplied a parameter for argument -P. (1403)


If, on the other hand, I import the pf into OE Management and start the DB it looks like it's starting, but it doesn't and the log is blank. There is no report as to what has failed. I suspect the errors I was getting above on production re Replication are due to something OE Management does after it's tried starting the DB. I'm going to try and test that but that will be harder to replicate due to replication. 

Posted by Mike Fechner on 19-Dec-2014 03:44

I doubt Progress will change that.
 
Startup parameters have been case sensitive since ever I remember.

 

Posted by James Palmer on 19-Dec-2014 03:46

I don't mind that it fails, it's more that there is no report anywhere in OE Management if the params are wrong. I thought the DB was hosed when in fact all it was was someone mistyping a parameter.

Posted by Brian Bowman on 19-Dec-2014 06:14

I believe it is a bug.  Behavior should be the same in either case.  What I would question is whether the import into OEM threw any errors because of the invalid entry.

Brian

Sent from my iPad

Brian Bowman
Principal Product Manager
Progress Software Corporation
91 Souhegan Street
Amherst NH, 03031 USA
Office : +1 603 554 1001
Mobile: +1 603 801 8259

On Dec 19, 2014, at 4:42 AM, "James Palmer" <bounce-jdpjamesp@community.progress.com> wrote:

Reply by James Palmer

I consider this a bug. What do others think?

If I take a copy of Sports2000 and proserve it from proenv with the PF below I get an error due to the case of -BPMax. 

-db C:\Database\s2k\s2k.db
-B 75000
-minport 3000
-maxport 5000
-lruskips 50
-B2 600
-BPmax 100
-Mxs 25
-L 8192
-hash 13063
-spin 24000
-shmsegsize 512
-bibufs 20
-aibufs 20
-Ma 5
-Mn 6
-Mi 1
-n 50
-Mm 4096
-Mpb 5
-omsize 2660


The error is

C:\Database\s2k>proserve -pf s2k.pf
OpenEdge Release 11.2.1 as of Mon Apr 29 19:26:32 EDT 2013
08:35:19 SERVER   : You have not supplied a parameter for argument -P. (1403)


If, on the other hand, I import the pf into OE Management and start the DB it looks like it's starting, but it doesn't and the log is blank. There is no report as to what has failed. I suspect the errors I was getting above on production re Replication are due to something OE Management does after it's tried starting the DB. I'm going to try and test that but that will be harder to replicate due to replication. 

Stop receiving emails on this subject.

Flag this post as spam/abuse.

Posted by James Palmer on 19-Dec-2014 06:46

I'll raise a bug report then [mention:b95db7be848d40f8a39db30310edfa01:e9ed411860ed4f2ba0265705b8793d05] and let support deal with it.

Posted by James Palmer on 19-Dec-2014 06:51

Case Number: 00298770

Posted by James Palmer on 22-Dec-2014 06:49

Case closed - apparently this has been addressed in 11.4 and 11.5, so OEM will now error gracefully if the parameters are incorrect.

This thread is closed