Mfgsys.pf for SQL environment question

Yahoo Archive
1
There aren't any actual external processes that require them running on a
regular basis.

For Admin tools, you can put the schema holder locally on the admin box and
bypass the need to connect through the network for anything, in terms of
Extended UD Tables, you can run a schema updates on a temporary running
schema holder, then revert it back to -RO with no problem, and Insite does
not require a running schema holder either.

There are actually zero technical reasons to need a schema holder always
running and not set to -RO.

The below statement is mostly to make it less complicated for an end user
who may not be knowledgeable in the configuration, not for technical or
performance reasons.

-----Original Message-----
From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf Of
Brian Roberts
Sent: Thursday, July 26, 2012 1:20 PM
To: vantage@yahoogroups.com
Subject: RE: [Vantage] mfgsys.pf for SQL environment question

The -RO (read only) was Epicor's recommendation, but they are changing it.
Quote below from a help call I placed with Epicor about this:



"We are in the middle of changing the recommendations on setting the schema
holders to RO when you have a 64bit install of Epicor905. There are many
external processes that would require that the schema holders not be in read
only (for example, Insite or if you were planning on using Extended UD
tables) so it is recommended to remove the read-only on your schema holders
and take the RO out of the pf, then you should be able to connect from your
admin tools successfully."



Brian.



From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf Of
Tim Vonderhaar
Sent: Thursday, July 26, 2012 11:08 AM
To: vantage@yahoogroups.com
Subject: [Vantage] mfgsys.pf for SQL environment question





We had our test database lock up from a DMT that blew up. It left the main
app server such that it would not stop. Checking the log files, we saw this
error:

[12/07/20@10:23:56.843-0400] P-004504 T-005980 1 AS -- Warning: another user
is using this database in update mode.
[12/07/20@10:23:56.843-0400] P-004504 T-005980 1 AS -- Accessing the
database with -RO may give unexpected results. (1531)
[12/07/20@10:23:56.844-0400] P-004504 T-005980 1 AS -- WARNING:
Before-image file of database C:\Program Files\Epicor
Software\Epicor905\db\test\mfgsyssh is not truncated. (1552)

Talking with Epicor, they said that our .pf files were incorrect because the
database line had a -RO like this:

-db "C:\Program Files\Epicor Software\Epicor905\db\pilot\mfgsyssh" -RO

All the documentation I have read for all of the upgrades, including the
most current one on Epicor's website (Epicor905_SPGuide_905700_SQL.pdf page
27) still shows that SQL environments require the -RO which makes me very
curious as to what this is really doing. I'm guessing it stands for Read
Only, but that doesn't make any sense to me.

Anyone have any insights?

Tim





[Non-text portions of this message have been removed]



------------------------------------

Useful links for the Yahoo!Groups Vantage Board are: ( Note: You must have
already linked your email address to a yahoo id to enable access. )
(1) To access the Files Section of our Yahoo!Group for Report Builder and
Crystal Reports and other 'goodies', please goto:
http://groups.yahoo.com/group/vantage/files/.
(2) To search through old msg's goto:
http://groups.yahoo.com/group/vantage/messages
(3) To view links to Vendors that provide Vantage services goto:
http://groups.yahoo.com/group/vantage/linksYahoo! Groups Links
2
We had our test database lock up from a DMT that blew up. It left the main app server such that it would not stop. Checking the log files, we saw this error:

[12/07/20@10:23:56.843-0400] P-004504 T-005980 1 AS -- Warning: another user is using this database in update mode.
[12/07/20@10:23:56.843-0400] P-004504 T-005980 1 AS -- Accessing the database with -RO may give unexpected results. (1531)
[12/07/20@10:23:56.844-0400] P-004504 T-005980 1 AS -- WARNING: Before-image file of database C:\Program Files\Epicor Software\Epicor905\db\test\mfgsyssh is not truncated. (1552)

Talking with Epicor, they said that our .pf files were incorrect because the database line had a -RO like this:

-db "C:\Program Files\Epicor Software\Epicor905\db\pilot\mfgsyssh" -RO

All the documentation I have read for all of the upgrades, including the most current one on Epicor's website (Epicor905_SPGuide_905700_SQL.pdf page 27) still shows that SQL environments require the -RO which makes me very curious as to what this is really doing. I'm guessing it stands for Read Only, but that doesn't make any sense to me.

Anyone have any insights?

Tim
3
I went through the -RO debate with our last upgrade. -RO was supposed to be a performance enhancement for SQL environments originally. I talked to quite a few knowledgeable people on this and they said with or without doesn't impact performance and that it is better to leave off the -RO now because of some of the admin/maintenance programs if I remember correctly.


[Non-text portions of this message have been removed]
4
Thanks for the reply. I will go ahead and remove it.

--- In vantage@yahoogroups.com, "Lisser, Jennifer" <Jennifer.Lisser@...> wrote:
>
> I went through the -RO debate with our last upgrade. -RO was supposed to be a performance enhancement for SQL environments originally. I talked to quite a few knowledgeable people on this and they said with or without doesn't impact performance and that it is better to leave off the -RO now because of some of the admin/maintenance programs if I remember correctly.
>
>
> [Non-text portions of this message have been removed]
>
5
The -RO (read only) was Epicor's recommendation, but they are changing
it. Quote below from a help call I placed with Epicor about this:



"We are in the middle of changing the recommendations on setting the
schema holders to RO when you have a 64bit install of Epicor905. There
are many external processes that would require that the schema holders
not be in read only (for example, Insite or if you were planning on
using Extended UD tables) so it is recommended to remove the read-only
on your schema holders and take the RO out of the pf, then you should be
able to connect from your admin tools successfully."



Brian.



From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf
Of Tim Vonderhaar
Sent: Thursday, July 26, 2012 11:08 AM
To: vantage@yahoogroups.com
Subject: [Vantage] mfgsys.pf for SQL environment question





We had our test database lock up from a DMT that blew up. It left the
main app server such that it would not stop. Checking the log files, we
saw this error:

[12/07/20@10:23:56.843-0400] P-004504 T-005980 1 AS -- Warning: another
user is using this database in update mode.
[12/07/20@10:23:56.843-0400] P-004504 T-005980 1 AS -- Accessing the
database with -RO may give unexpected results. (1531)
[12/07/20@10:23:56.844-0400] P-004504 T-005980 1 AS -- WARNING:
Before-image file of database C:\Program Files\Epicor
Software\Epicor905\db\test\mfgsyssh is not truncated. (1552)

Talking with Epicor, they said that our .pf files were incorrect because
the database line had a -RO like this:

-db "C:\Program Files\Epicor Software\Epicor905\db\pilot\mfgsyssh" -RO

All the documentation I have read for all of the upgrades, including the
most current one on Epicor's website (Epicor905_SPGuide_905700_SQL.pdf
page 27) still shows that SQL environments require the -RO which makes
me very curious as to what this is really doing. I'm guessing it stands
for Read Only, but that doesn't make any sense to me.

Anyone have any insights?

Tim





[Non-text portions of this message have been removed]
6
Thanks Brian

--- In vantage@yahoogroups.com, "Brian Roberts" <broberts@...> wrote:
>
> The -RO (read only) was Epicor's recommendation, but they are changing
> it. Quote below from a help call I placed with Epicor about this:
>
>
>
> "We are in the middle of changing the recommendations on setting the
> schema holders to RO when you have a 64bit install of Epicor905. There
> are many external processes that would require that the schema holders
> not be in read only (for example, Insite or if you were planning on
> using Extended UD tables) so it is recommended to remove the read-only
> on your schema holders and take the RO out of the pf, then you should be
> able to connect from your admin tools successfully."
>
>
>
> Brian.
>
>
>
> From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf
> Of Tim Vonderhaar
> Sent: Thursday, July 26, 2012 11:08 AM
> To: vantage@yahoogroups.com
> Subject: [Vantage] mfgsys.pf for SQL environment question
>
>
>
>
>
> We had our test database lock up from a DMT that blew up. It left the
> main app server such that it would not stop. Checking the log files, we
> saw this error:
>
> [12/07/20@10:23:56.843-0400] P-004504 T-005980 1 AS -- Warning: another
> user is using this database in update mode.
> [12/07/20@10:23:56.843-0400] P-004504 T-005980 1 AS -- Accessing the
> database with -RO may give unexpected results. (1531)
> [12/07/20@10:23:56.844-0400] P-004504 T-005980 1 AS -- WARNING:
> Before-image file of database C:\Program Files\Epicor
> Software\Epicor905\db\test\mfgsyssh is not truncated. (1552)
>
> Talking with Epicor, they said that our .pf files were incorrect because
> the database line had a -RO like this:
>
> -db "C:\Program Files\Epicor Software\Epicor905\db\pilot\mfgsyssh" -RO
>
> All the documentation I have read for all of the upgrades, including the
> most current one on Epicor's website (Epicor905_SPGuide_905700_SQL.pdf
> page 27) still shows that SQL environments require the -RO which makes
> me very curious as to what this is really doing. I'm guessing it stands
> for Read Only, but that doesn't make any sense to me.
>
> Anyone have any insights?
>
> Tim
>
>
>
>
>
> [Non-text portions of this message have been removed]
>
7
In a SQL configuration, the mfgsyssh.db is the OpenEdge "Schema Holder" database. It contains the Epicor schema - tables, fields, indexes, etc. The actual DATA is in the SQL database which is read-write. The schema holder is READ when programs are compiled.

DMT's die for any one of a hundred reasons. But the -RO in that .pf file isn't one of them. Good detective work though!

Oh, using OE Management or Progress Explorer, you can kill a runaway appserver. Drill down and find the runaway in appserver client connections detail. it will typical be stuck "SENDING". note the Agent PID value. Then in Server Pool Control, select the server with that PID, and you have a Kill option at the top.

- Chris


--- In vantage@yahoogroups.com, "Tim Vonderhaar" <tvonderhaar@...> wrote:
>
> We had our test database lock up from a DMT that blew up. It left the main app server such that it would not stop. Checking the log files, we saw this error:
>
> [12/07/20@10:23:56.843-0400] P-004504 T-005980 1 AS -- Warning: another user is using this database in update mode.
> [12/07/20@10:23:56.843-0400] P-004504 T-005980 1 AS -- Accessing the database with -RO may give unexpected results. (1531)
> [12/07/20@10:23:56.844-0400] P-004504 T-005980 1 AS -- WARNING: Before-image file of database C:\Program Files\Epicor Software\Epicor905\db\test\mfgsyssh is not truncated. (1552)
>
> Talking with Epicor, they said that our .pf files were incorrect because the database line had a -RO like this:
>
> -db "C:\Program Files\Epicor Software\Epicor905\db\pilot\mfgsyssh" -RO
>
> All the documentation I have read for all of the upgrades, including the most current one on Epicor's website (Epicor905_SPGuide_905700_SQL.pdf page 27) still shows that SQL environments require the -RO which makes me very curious as to what this is really doing. I'm guessing it stands for Read Only, but that doesn't make any sense to me.
>
> Anyone have any insights?
>
> Tim
>
8
Ah, that makes good sense in that the OpenEdge is simply the schema and would make sense to have set to RO. I know that layer is present, just don't think about it and didn't connect the two.

Thanks for the tip about the PID.

--- In vantage@yahoogroups.com, "reptcon" <cheins@...> wrote:
>
> In a SQL configuration, the mfgsyssh.db is the OpenEdge "Schema Holder" database. It contains the Epicor schema - tables, fields, indexes, etc. The actual DATA is in the SQL database which is read-write. The schema holder is READ when programs are compiled.
>
> DMT's die for any one of a hundred reasons. But the -RO in that .pf file isn't one of them. Good detective work though!
>
> Oh, using OE Management or Progress Explorer, you can kill a runaway appserver. Drill down and find the runaway in appserver client connections detail. it will typical be stuck "SENDING". note the Agent PID value. Then in Server Pool Control, select the server with that PID, and you have a Kill option at the top.
>
> - Chris
>
>
> --- In vantage@yahoogroups.com, "Tim Vonderhaar" <tvonderhaar@> wrote:
> >
> > We had our test database lock up from a DMT that blew up. It left the main app server such that it would not stop. Checking the log files, we saw this error:
> >
> > [12/07/20@10:23:56.843-0400] P-004504 T-005980 1 AS -- Warning: another user is using this database in update mode.
> > [12/07/20@10:23:56.843-0400] P-004504 T-005980 1 AS -- Accessing the database with -RO may give unexpected results. (1531)
> > [12/07/20@10:23:56.844-0400] P-004504 T-005980 1 AS -- WARNING: Before-image file of database C:\Program Files\Epicor Software\Epicor905\db\test\mfgsyssh is not truncated. (1552)
> >
> > Talking with Epicor, they said that our .pf files were incorrect because the database line had a -RO like this:
> >
> > -db "C:\Program Files\Epicor Software\Epicor905\db\pilot\mfgsyssh" -RO
> >
> > All the documentation I have read for all of the upgrades, including the most current one on Epicor's website (Epicor905_SPGuide_905700_SQL.pdf page 27) still shows that SQL environments require the -RO which makes me very curious as to what this is really doing. I'm guessing it stands for Read Only, but that doesn't make any sense to me.
> >
> > Anyone have any insights?
> >
> > Tim
> >
>
9
Those are not errors that matter, basically it means you are connecting to a
running DB/SH with the -RO instead of a DB/SH that is not running at all.

And putting the schema at -RO is still the best option, the reason that they
say not to do it is due to confusion for people and running the Admin Tools
can be confusing and I think they just don't want to go through the process
of explaining it to everyone on how to get it setup and keep it up to date
once it is setup since it goes outside of places where their automated
installation and updates can "fix" the setup.

-----Original Message-----
From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf Of
Tim Vonderhaar
Sent: Thursday, July 26, 2012 11:08 AM
To: vantage@yahoogroups.com
Subject: [Vantage] mfgsys.pf for SQL environment question

We had our test database lock up from a DMT that blew up. It left the main
app server such that it would not stop. Checking the log files, we saw this
error:

[12/07/20@10:23:56.843-0400] P-004504 T-005980 1 AS -- Warning: another user
is using this database in update mode.
[12/07/20@10:23:56.843-0400] P-004504 T-005980 1 AS -- Accessing the
database with -RO may give unexpected results. (1531)
[12/07/20@10:23:56.844-0400] P-004504 T-005980 1 AS -- WARNING: Before-image
file of database C:\Program Files\Epicor Software\Epicor905\db\test\mfgsyssh
is not truncated. (1552)

Talking with Epicor, they said that our .pf files were incorrect because the
database line had a -RO like this:

-db "C:\Program Files\Epicor Software\Epicor905\db\pilot\mfgsyssh" -RO

All the documentation I have read for all of the upgrades, including the
most current one on Epicor's website (Epicor905_SPGuide_905700_SQL.pdf page
27) still shows that SQL environments require the -RO which makes me very
curious as to what this is really doing. I'm guessing it stands for Read
Only, but that doesn't make any sense to me.

Anyone have any insights?

Tim



------------------------------------

Useful links for the Yahoo!Groups Vantage Board are: ( Note: You must have
already linked your email address to a yahoo id to enable access. )
(1) To access the Files Section of our Yahoo!Group for Report Builder and
Crystal Reports and other 'goodies', please goto:
http://groups.yahoo.com/group/vantage/files/.
(2) To search through old msg's goto:
http://groups.yahoo.com/group/vantage/messages
(3) To view links to Vendors that provide Vantage services goto:
http://groups.yahoo.com/group/vantage/linksYahoo! Groups Links