- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: MC/SG and SAP R/3 integration using SGeSAP - p...
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-29-2002 04:52 AM
тАО11-29-2002 04:52 AM
MC/SG and SAP R/3 integration using SGeSAP - problems - please help - long
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-30-2002 08:26 PM
тАО11-30-2002 08:26 PM
Re: MC/SG and SAP R/3 integration using SGeSAP - problems - please help - long
I don't have an answer for you, but I'll float it back to the top, maybe someone can help.
live free or die
harry
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-03-2002 02:57 AM
тАО12-03-2002 02:57 AM
Re: MC/SG and SAP R/3 integration using SGeSAP - problems - please help - long
I made a mistake a the beginning of problem desciption - of course I was going to say that packages start in sequence upon cluster startup (not that they do not !!!).
I quickly managed with the problem with cluster halting - I deleted packages from the cluster and added them back again in opposite order. Now, during cluster halt, apprd01 halts first, then goes ciPRD and finally dbPRD so NFS is not an issue anymore. It has no impact on cluster startup because dbPRD is the only one that starts automatically - the two other are started by its preceding package.
Problem with a deadlock during concurrent package startup at failover is still an issue however :-(
Regards,
Zbigniew Klos
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-03-2002 10:15 AM
тАО12-03-2002 10:15 AM
Re: MC/SG and SAP R/3 integration using SGeSAP - problems - please help - long
Perhaps the ASTREAT and DELAY_INTERVALS parameters in the /opt/cmcluster/sap/SID/sap.conf file may be of some help to you.
Also, "Managing MC/ServiceGuard Extension for SAP R/3" may help you configure the SGeSAP toolkit. The document is located here:
http://docs.hp.com/hpux/ha/index.html#ServiceGuard%20Extension%20for%20SAP
-s.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-05-2002 02:44 AM
тАО12-05-2002 02:44 AM
Re: MC/SG and SAP R/3 integration using SGeSAP - problems - please help - long
in my opinion it's not a quite good idea to start one package from the other (if i understood you start application server from central instance package). We have a configuration here, where we start db and ci in one package and have up to three application servers always trying to start up in parallel. We simply check if the dbci-package is running in the customer_defined_run_commands of the app-packages in a while loop (10 tries, 20 seconds sleep), and if this succeeds the package can go on to start it's sap-application-server. So it's YOU who checks for db and ci and not the sap-script, which should not end up in a deadlock situation.
The second question is not quite clear to me. The only situation where the db-package is going down before the others should be a failure. If you are bringing the cluster down manually, it's only a question of discipline. Ok, it's possible that you have a failure of the db-package alone and then you are in a mess, i see (should be very rare condition). A possible solution is, that you are using a seperat NFS-package for this. The only problem now is, that mostly the NFS-package is the first to fail if there are any problems, but it should also be the first one that come up on the other node.
As i said, we only have dbci and app seperated and each one has all necessary binaries in the package, giving you much overhead but good stability in cluster operations.
Hope i really understood your problem and giving some hints here.
Heinz