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.
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.
Flag this post as spam/abuse.
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.
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.
Flag this post as spam/abuse.
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.
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.
Reply by James PalmerI 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 isC:\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.
I'll raise a bug report then [mention:b95db7be848d40f8a39db30310edfa01:e9ed411860ed4f2ba0265705b8793d05] and let support deal with it.
Case Number: 00298770
Case closed - apparently this has been addressed in 11.4 and 11.5, so OEM will now error gracefully if the parameters are incorrect.