Friday, December 2, 2011

Could not reach message server to enable SDM process in JStartupFramework. (Could not create JStartupClusterController: Connection refused)

Solution : - Make the SDM standalone temporarily or permanent if its ok


 ./sdm.sh jstartup mode=standalone
Starting '/usr/java142/bin/java' '-Xmx256M' -jar '/usr/sap/SID/JCXX/SDM/program/bin/SDM.jar' jstartup 'sdmhome=/usr/sap/SID/JCXX/SDM/program' mode=standalone
Starting SDM - Software Deployment Manager...
tc/SL/SDM/SDM/sap.com/SAP AG/7.0016.20080423161536.0000
Initializing Network Manager (50517)
Checking if another SDM is running on port 50518

Operationmode for JStartupFramework set to "standalone".
Successfully executed. Return code: 0

Start the SDM

 ./StartServer.sh
Starting SDM - Software Deployment Manager...
tc/SL/SDM/SDM/sap.com/SAP AG/7.0016.20080423161536.0000
JStartupFramework is active
Operation mode of SDM in JStartupFramework is "Standalone". Simply start the ser
Initializing Network Manager (50517)
Starting SDM Server listening on port 50518
SDM started successfully.
Redirecting output to the two files "/usr/sap/SID/JCXX/SDM/program/log/sdm_serve




Error Info:------


: Dec 2, 2011 10:13:58 AM  Info: =========================================
Dec 2, 2011 10:13:58 AM  Info: =   Starting to execute command 'gui'   =
Dec 2, 2011 10:13:58 AM  Info: =========================================
Dec 2, 2011 10:13:58 AM  Info: Starting SDM - Software Deployment Manager...
Dec 2, 2011 10:13:58 AM  Info: tc/SL/SDM/SDM/sap.com/SAP AG/7.0016.20080423161536.0000
Dec 2, 2011 10:14:01 AM  Info: SDM operation mode successfully set to: Integrated
Dec 2, 2011 10:14:01 AM  Info: Initializing Network Manager (50517)
Dec 2, 2011 10:14:01 AM  Info: Checking if another SDM is running on port 50518
Dec 2, 2011 10:14:01 AM  Error: SDM is integrated in JStartupFramework. No repository changing commands are possible.
Dec 2, 2011 10:14:01 AM  Error: Could not start SDM. Processing error. Return code: 4
Dec 2, 2011 10:14:33 AM  Info:
Dec 2, 2011 10:14:33 AM  Info: ============================================
Dec 2, 2011 10:14:33 AM  Info: =   Starting to execute command 'server'   =
Dec 2, 2011 10:14:33 AM  Info: ============================================
Dec 2, 2011 10:14:33 AM  Info: Starting SDM - Software Deployment Manager...
Dec 2, 2011 10:14:34 AM  Info: tc/SL/SDM/SDM/sap.com/SAP AG/7.0016.20080423161536.0000
Dec 2, 2011 10:14:36 AM  Info: SDM operation mode successfully set to: Integrated
Dec 2, 2011 10:14:36 AM  Info: JStartupFramework is active
Dec 2, 2011 10:14:36 AM  Info: Operation mode of SDM in JStartupFramework is "Integrated".
Dec 2, 2011 10:14:36 AM  Info: Check if Server is running already.
Dec 2, 2011 10:14:36 AM  Info: OK server is not running. Enable SDM Process in JStartupFramework.
Dec 2, 2011 10:14:36 AM  Error: Could not create JStartupClusterController: Connection refused Throwable: java.net.ConnectException Throwable message: Connection refused
Dec 2, 2011 10:14:36 AM  Error: Cannot enable SDM Process with JStartupFramework: No Cluster Controller available.
Dec 2, 2011 10:14:36 AM  Error: Could not reach message server to enable SDM process in JStartupFramework. (Could not create JStartupClusterController: Connection refused)
Dec 2, 2011 10:14:36 AM  Error: Could not start SDM. Processing error. Return code: 104

Friday, October 7, 2011

SAP Technical Issues -Basis

Hey Basis folks, few most frequently faced issue from the Basis side which are kind of trivial and we encounter most of the time hopefully will help you too.

Activate SAP * user :

 delete from <schema>.usr02 where bname='sap*' and mandt='000'
As of Release 7.0 (NetWeaver 7.0/2004s):
The default value of the login/no_automatic_user_sapstar profile parameter has been changed (previously 0, now 1). To activate the emergency user, you must set the login/no_automatic_user_sapstar profile parameter to the value 0.(Checkout SAP Notes for more on this)

SIDadm unable to sqlplus (TNS lost connect)
Try "relink all"   $ORACLE_HOME/lib/relink all

Changing SAP Schema user password
brconnect -c -u / -f chpass -o <sap_schema_user> -p <password>


Speed up BDLS
1.Exclude tables that doesn't not contain LOGSYS info example COEP,GLPCA and etc
2. Create bitmap index for the large tables for the few columns and delete it later after BDLS is done, you'll see a significant improvement