Epicor 9 Using MS SQL, Read Only Schema Holders Problem

Yahoo Archive
1
Geezer.

And you had to partition it 'cuz FAT only saw 33M in a single chunk...

Ernie Lowell
Diba Industries

--- In vantage@yahoogroups.com, "Vic Drecchio" <vic.drecchio@...> wrote:
>
> I had mine set to RO for a while. As others stated, the performance gain is
> insignificant. It adds extra unnecessary steps (room for error) for
> patches/upgrades requiring schema changes. But Joshua brings up a great
> point; if you're at the point where you're wanting to tweak out an
> additional 1% performance gain by doing this, then I'd second his advice and
> encourage you to purchase some new hardware. We're all lucky right now;
> hardware is cheap. I'm old enough to remember a 40MB "MFM" hard drive
> costing $300.. A little different now! :-)
>
>
>
> From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf Of
> Clive
> Sent: Wednesday, June 12, 2013 7:18 AM
> To: vantage@yahoogroups.com
> Subject: [Vantage] Epicor 9 Using MS SQL, Read Only Schema Holders Problem
>
>
>
>
>
> We're quite happily running Epicor 9.05.700C using MS SQL 2008 as the DB and
> everyting works correctly, however, I'm looking into changing the Progress
> schema holder db to be read only for the modest performance improvement it
> gives you but the main AppServer will not start. I've logged a support call
> with Epicor and unfortunately they can help no further without it becoming
> consulting / chargeable (as usual).
>
> I've followed the correct SQL performance tuning guide and some additional
> advice from Epicor buthe main AppServer will not and there are soem specific
> errors in the log files. I'm posting here in the hope that maybe someone
> else has had a similar problem and been able tp resolve it.
>
> An example of the error I get in the Broker log file is...
>
> IOException reading message from server : java.io.EOFException: pipe to
> server broken (8117)
> Message from server : Startup Procedure Failed (8113)
>
> ... and an example from ther Server log file is...
>
> P-010292 T-013988 1 AS -- ** Could not connect to server for database
> mfgsyssh, errno 0. (1432)
> P-010292 T-013988 1 AS -- Error initializing the application server. (5479)
>
> ... hopefully someone here has had the same errors, if not I'll have to bite
> the bullet and pay for some consulting (either with Epicor or our prefered
> Epicor partner).
>
> Thanks.
>
>
>
>
>
> [Non-text portions of this message have been removed]
>
2
We're quite happily running Epicor 9.05.700C using MS SQL 2008 as the DB and everyting works correctly, however, I'm looking into changing the Progress schema holder db to be read only for the modest performance improvement it gives you but the main AppServer will not start. I've logged a support call with Epicor and unfortunately they can help no further without it becoming consulting / chargeable (as usual).

I've followed the correct SQL performance tuning guide and some additional advice from Epicor buthe main AppServer will not and there are soem specific errors in the log files. I'm posting here in the hope that maybe someone else has had a similar problem and been able tp resolve it.

An example of the error I get in the Broker log file is...

IOException reading message from server : java.io.EOFException: pipe to server broken (8117)
Message from server : Startup Procedure Failed (8113)

... and an example from ther Server log file is...

P-010292 T-013988 1 AS -- ** Could not connect to server for database mfgsyssh, errno 0. (1432)
P-010292 T-013988 1 AS -- Error initializing the application server. (5479)

... hopefully someone here has had the same errors, if not I'll have to bite the bullet and pay for some consulting (either with Epicor or our prefered Epicor partner).

Thanks.
3
I would advise against setting it to read only. The performance gain is minimal, and honestly if you're reaching for that you might need new equip. But anyways when I had mine read only it was a huge pain. If there was a financial glitch and Epicor sent us a progress program I would have to bring everything down, undo the read-only settings, run the progress program, set everything back, then bring it all back up. Just wasn't worth it because of that for us. Food for thought.


Sent from my U.S. Cellular® Smartphone

-------- Original message --------
From: Clive <clive.1972@...>
Date: 06/12/2013 6:08 AM (GMT-06:00)
To: vantage@yahoogroups.com
Subject: [Vantage] Epicor 9 Using MS SQL, Read Only Schema Holders Problem

We're quite happily running Epicor 9.05.700C using MS SQL 2008 as the DB and everyting works correctly, however, I'm looking into changing the Progress schema holder db to be read only for the modest performance improvement it gives you but the main AppServer will not start. I've logged a support call with Epicor and unfortunately they can help no further without it becoming consulting / chargeable (as usual).

I've followed the correct SQL performance tuning guide and some additional advice from Epicor buthe main AppServer will not and there are soem specific errors in the log files. I'm posting here in the hope that maybe someone else has had a similar problem and been able tp resolve it.

An example of the error I get in the Broker log file is...

IOException reading message from server : java.io.EOFException: pipe to server broken (8117)
Message from server : Startup Procedure Failed (8113)

... and an example from ther Server log file is...

P-010292 T-013988 1 AS -- ** Could not connect to server for database mfgsyssh, errno 0. (1432)
P-010292 T-013988 1 AS -- Error initializing the application server. (5479)

... hopefully someone here has had the same errors, if not I'll have to bite the bullet and pay for some consulting (either with Epicor or our prefered Epicor partner).

Thanks.



[Non-text portions of this message have been removed]
4
I had a conversation with Epicor support recently and they said pretty much the same thing. Even though it is still listed in the performance tuning guide, they said they no longer recommend setting the schema holder to read only.

--- In vantage@yahoogroups.com, Joshua Giese <jgiese@...> wrote:
>
> I would advise against setting it to read only. The performance gain is minimal, and honestly if you're reaching for that you might need new equip. But anyways when I had mine read only it was a huge pain. If there was a financial glitch and Epicor sent us a progress program I would have to bring everything down, undo the read-only settings, run the progress program, set everything back, then bring it all back up. Just wasn't worth it because of that for us. Food for thought.
>
>
> Sent from my U.S. Cellular® Smartphone
>
> -------- Original message --------
> From: Clive <clive.1972@...>
> Date: 06/12/2013 6:08 AM (GMT-06:00)
> To: vantage@yahoogroups.com
> Subject: [Vantage] Epicor 9 Using MS SQL, Read Only Schema Holders Problem
>
> We're quite happily running Epicor 9.05.700C using MS SQL 2008 as the DB and everyting works correctly, however, I'm looking into changing the Progress schema holder db to be read only for the modest performance improvement it gives you but the main AppServer will not start. I've logged a support call with Epicor and unfortunately they can help no further without it becoming consulting / chargeable (as usual).
>
> I've followed the correct SQL performance tuning guide and some additional advice from Epicor buthe main AppServer will not and there are soem specific errors in the log files. I'm posting here in the hope that maybe someone else has had a similar problem and been able tp resolve it.
>
> An example of the error I get in the Broker log file is...
>
> IOException reading message from server : java.io.EOFException: pipe to server broken (8117)
> Message from server : Startup Procedure Failed (8113)
>
> ... and an example from ther Server log file is...
>
> P-010292 T-013988 1 AS -- ** Could not connect to server for database mfgsyssh, errno 0. (1432)
> P-010292 T-013988 1 AS -- Error initializing the application server. (5479)
>
> ... hopefully someone here has had the same errors, if not I'll have to bite the bullet and pay for some consulting (either with Epicor or our prefered Epicor partner).
>
> Thanks.
>
>
>
> [Non-text portions of this message have been removed]
>
5
The errors mean that you probably missed the -RO in whatever .pf file the
appserver is using to connect. That error tells us that it's trying to
connect to a running appserver.

Check the Appserver settings and see which .pf file it's set to use and make
sure that is the one that has the .pf with the correct -db line with the -RO
on it.

-----Original Message-----
From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf Of
Clive
Sent: Wednesday, June 12, 2013 7:18 AM
To: vantage@yahoogroups.com
Subject: [Vantage] Epicor 9 Using MS SQL, Read Only Schema Holders Problem

We're quite happily running Epicor 9.05.700C using MS SQL 2008 as the DB and
everyting works correctly, however, I'm looking into changing the Progress
schema holder db to be read only for the modest performance improvement it
gives you but the main AppServer will not start. I've logged a support call
with Epicor and unfortunately they can help no further without it becoming
consulting / chargeable (as usual).

I've followed the correct SQL performance tuning guide and some additional
advice from Epicor buthe main AppServer will not and there are soem specific
errors in the log files. I'm posting here in the hope that maybe someone
else has had a similar problem and been able tp resolve it.

An example of the error I get in the Broker log file is...

IOException reading message from server : java.io.EOFException: pipe to
server broken (8117) Message from server : Startup Procedure Failed (8113)

... and an example from ther Server log file is...

P-010292 T-013988 1 AS -- ** Could not connect to server for database
mfgsyssh, errno 0. (1432)
P-010292 T-013988 1 AS -- Error initializing the application server. (5479)

... hopefully someone here has had the same errors, if not I'll have to bite
the bullet and pay for some consulting (either with Epicor or our prefered
Epicor partner).

Thanks.



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

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
6
I had mine set to RO for a while. As others stated, the performance gain is
insignificant. It adds extra unnecessary steps (room for error) for
patches/upgrades requiring schema changes. But Joshua brings up a great
point; if you're at the point where you're wanting to tweak out an
additional 1% performance gain by doing this, then I'd second his advice and
encourage you to purchase some new hardware. We're all lucky right now;
hardware is cheap. I'm old enough to remember a 40MB "MFM" hard drive
costing $300.. A little different now! :-)



From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf Of
Clive
Sent: Wednesday, June 12, 2013 7:18 AM
To: vantage@yahoogroups.com
Subject: [Vantage] Epicor 9 Using MS SQL, Read Only Schema Holders Problem





We're quite happily running Epicor 9.05.700C using MS SQL 2008 as the DB and
everyting works correctly, however, I'm looking into changing the Progress
schema holder db to be read only for the modest performance improvement it
gives you but the main AppServer will not start. I've logged a support call
with Epicor and unfortunately they can help no further without it becoming
consulting / chargeable (as usual).

I've followed the correct SQL performance tuning guide and some additional
advice from Epicor buthe main AppServer will not and there are soem specific
errors in the log files. I'm posting here in the hope that maybe someone
else has had a similar problem and been able tp resolve it.

An example of the error I get in the Broker log file is...

IOException reading message from server : java.io.EOFException: pipe to
server broken (8117)
Message from server : Startup Procedure Failed (8113)

... and an example from ther Server log file is...

P-010292 T-013988 1 AS -- ** Could not connect to server for database
mfgsyssh, errno 0. (1432)
P-010292 T-013988 1 AS -- Error initializing the application server. (5479)

... hopefully someone here has had the same errors, if not I'll have to bite
the bullet and pay for some consulting (either with Epicor or our prefered
Epicor partner).

Thanks.





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