-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 30.04.2013 13:22, Muhammad Sharfuddin wrote: > Hello Fabian, > > On 04/30/2013 02:19 PM, Fabian Herschel wrote: >> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 >> >> Hi Muhammad, >> >> please find my answer below... >> >> >> The new setup preferred by _SAP_ is, that you use the >> saphostagent. This new menthod gives you the following benefits >> (you might not need today) >> >> 1. Support for DB only on a server and Java (only) Instance on >> an other server (this is currently not working, because in that >> case the bootstrap files are missing at the DB server) >> >> 2. Support for Sybase (you can only control the "old" set of >> databases like DB2 (older version than 10), MaxDB and Oracle >> >> 3. You use the more generic DB Interface written by SAP and the >> DB-Vendors, so the resource agent does not need to take care >> about specialities of database but could concentrate on the SAP >> specific control of the database >> >> > thanks a lot for sharing and explaining. > > >>> correct, cluster never shows any error when it runs/start the >>> SAPInstance, though we found that whenever we run the >>> SAPInstance from cluster SAP gives us errors while login via >>> SAP Client(SAPGui). as a workarround, we stopped the >>> SAPInstance from the cluster, let the cluster runs/start the >>> other resources(IP, File Systems, and SAPDBInstance) and then >>> manually started the SAPInstance(via sap way): >>> >>> startsap -i DVEBMGS00 -v pgtprd >> >> This should not be needed - there must a something wrong - which >> error message did you get when SAPInstance was controlled by >> cluster and you login via SAPGui? >> >> If you get a SICK message about 3.0 kernel please update to a >> current SAP Kernel (I could provide the SAP Note number if >> needed). > > as said cluster always successfully starts the SAPInstance without > any error, but when we login into SAP via SAPGui there we got the > following error: "Run time Errors.START_CALL_SICK.short text > database inconsistency .start trasaction SICK".
OK, this looks for me like the Linux Kernel is detected as 3.0 instead of 2.6. Could you (if needed with your SAP consultant) login and check, if there is something about the "unknown 3.0 kernel"? In this case the SAP Kernel should be updated. > > as a workaround I **only** stopped the SAPInstance from cluster(let > the IP, File Systems, SAPDBInstance remain running via cluster) > and start SAPInstance via command line "startsap -i DVEBMGS00 -v > pgtprd". > > SAP kernel version is 701, and we are running SAP on SLES 11 SP2 > via "Kernel 2.6 compatibility mode for SAP" (SAP note 1310037) Yes the 2.6 compatibility environment was only inteded to be used as a bridge between the avaialblibity of Linux 3.0 kernel and the customer to be able to update to newest SAP Kernels like 720 PL 402 or so. Sorry, that I couldn't solve that problem via this list, it now gets very SAP and support specific - if you have already opened a ticket at SUSE, please reference to that thread (my colleague already has read it :) and than we could help you with professional support. In sum its that SAP also wants you to update to the newer SAP kernels and my guess is that this is exactly your problem. While starting/stopping the instance with login-user/shell will lead into the 2.6 compat environment, the RA still runs in 3.0. ==> solution is either to change one line in RA (NOT preferred) or to update SAP kernel to current version (very appreciated and preferred :) > > > Regards, > > Muhammad Sharfuddin > _______________________________________________ Linux-HA mailing > list [email protected] > http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: > http://linux-ha.org/ReportingProblems > -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEcBAEBAgAGBQJRf8Y0AAoJEJ1uHhrzMvZR9/QIAIKZs1RyGLfZZ9aUlJZR7EGM V7thYcSldUGn0HivtW9N+kufxJHfapJ70L1o9wAw0kTbq5CaVgt42B177zB4Kq3q 5q6db1ouDh7ZufV+6Dprhff8mplEMrTCJKDPjYnna7COYzkWYPun2FBNPmAV1pGs rBmxDBH9enZ5Piacj357Rqqs2mFhmnBeSDOIDDqMX8BBG+MIuslYOoBfyzwUTilv ECJnkAHQZcT9CsRJ6wLkQCfFSD+HzpGp3tLZhYxi9ub7SPlthCI8vJOgp5HZhbLp SvR9SCp3RG71+HLWKuCBd+u/JWDuymFnZ8jIoyUDWFVJRdkT59jsha2T2qIqbRI= =nIwo -----END PGP SIGNATURE----- _______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
