Oe 10.1b03 (sun)
- Thread starter akash
- Start date
TomBascom
Curmudgeon
It would be useful to know what you are upgrading FROM...
There is an issue with 10.1B03 related to something called a "purge lock". Basically they don't get released like they are supposed to and they can sometimes fill up your lock table. Casper knows all about it
It should be somewhat rare and relies on pretty questionable programming to become a problem. Then again "questionable programming" is unfortunately far from rare :lol:
Anyhow, it's fixed in 10.1C which is probably a better release to be upgrading to anyway.
There is an issue with 10.1B03 related to something called a "purge lock". Basically they don't get released like they are supposed to and they can sometimes fill up your lock table. Casper knows all about it
It should be somewhat rare and relies on pretty questionable programming to become a problem. Then again "questionable programming" is unfortunately far from rare :lol:Anyhow, it's fixed in 10.1C which is probably a better release to be upgrading to anyway.
TomBascom
Curmudgeon
It would be useful to know what you are upgrading FROM...
There is an issue with 10.1B03 related to something called a "purge lock". Basically they don't get released like they are supposed to and they can sometimes fill up your lock table. Casper knows all about it It should be somewhat rare and relies on pretty questionable programming to become a problem. Then again "questionable programming" is unfortunately far from rare 
Anyhow, it's fixed in 10.1C which is probably a better release to be upgrading to anyway.
There is an issue with 10.1B03 related to something called a "purge lock". Basically they don't get released like they are supposed to and they can sometimes fill up your lock table. Casper knows all about it
It should be somewhat rare and relies on pretty questionable programming to become a problem. Then again "questionable programming" is unfortunately far from rare Anyhow, it's fixed in 10.1C which is probably a better release to be upgrading to anyway.
Hi Tom,
Thanks for your reply. Currently we are running 10.0B0542 (Sun) and 10.0B0533 (HP Superdome). Getting ready to upgrade to 10.1B0320 in both system. We heard that after upgrade in 10.1B (HP Superdome - I don't know the service pack and patch level) the database is frozen for 5+ minutes for another company. I am just wondering anyone hear or experiance any other issues. Below the db log while database was frozen.
[2008/05/01@10:02:25.581-0400] P-11514 T-1 I SRV 292: (4006) SYSTEM ERROR: Got message 20 for disconnected user 0
[2008/05/01@10:04:03.366-0400] P-11514 T-1 I SRV 292: (4006) SYSTEM ERROR: Got message 20 for disconnected user 0
[2008/05/01@10:05:20.525-0400] P-11655 T-1 I SRV 300: (13) SYSTEM ERROR: fmget: bad record or unknown value.
[2008/05/01@10:05:20.586-0400] P-11655 T-1 I SRV 300: (13) SYSTEM ERROR: fmget: bad record or unknown value.
[2008/05/01@10:05:25.293-0400] P-9160 T-1 I SRV 253: (13) SYSTEM ERROR: fmget: bad record or unknown value.
Thanks for your reply. Currently we are running 10.0B0542 (Sun) and 10.0B0533 (HP Superdome). Getting ready to upgrade to 10.1B0320 in both system. We heard that after upgrade in 10.1B (HP Superdome - I don't know the service pack and patch level) the database is frozen for 5+ minutes for another company. I am just wondering anyone hear or experiance any other issues. Below the db log while database was frozen.
[2008/05/01@10:02:25.581-0400] P-11514 T-1 I SRV 292: (4006) SYSTEM ERROR: Got message 20 for disconnected user 0
[2008/05/01@10:04:03.366-0400] P-11514 T-1 I SRV 292: (4006) SYSTEM ERROR: Got message 20 for disconnected user 0
[2008/05/01@10:05:20.525-0400] P-11655 T-1 I SRV 300: (13) SYSTEM ERROR: fmget: bad record or unknown value.
[2008/05/01@10:05:20.586-0400] P-11655 T-1 I SRV 300: (13) SYSTEM ERROR: fmget: bad record or unknown value.
[2008/05/01@10:05:25.293-0400] P-9160 T-1 I SRV 253: (13) SYSTEM ERROR: fmget: bad record or unknown value.
TomBascom
Curmudgeon
You seem to be running with "hot fixes" (a lot of extra digits in the Progress version number). Is there a reason for that?
Why not 10.1C?
5 minutes is how long the conversion should take. Is that what your other correspondent was referring to?
The fmget errors are something to discuss with tech support. But, if I read this right, they aren't from your database so I don't know what the relevance would be.
Why not 10.1C?
5 minutes is how long the conversion should take. Is that what your other correspondent was referring to?
The fmget errors are something to discuss with tech support. But, if I read this right, they aren't from your database so I don't know what the relevance would be.
There was lot of issues with revert functionality in 10.1B03, most of the hot fixes for revert. We started testing 10.1C now and it will take some time. Our Development team wants 10.1B features badly.
The database log is not from our database but from another company. And they are not collecting any perfmon data until this issue happened. According to progress, they can't debug this without more info. Any insight?
Thanks,
Akash.
The database log is not from our database but from another company. And they are not collecting any perfmon data until this issue happened. According to progress, they can't debug this without more info. Any insight?
Thanks,
Akash.