CA Service Management

Hi friends,

we are upgrading ca sdm 14.1 to 17.0 background server. It installed perfectly.But while installing in application server there is some error is coming. please give me related solution to solve.and another thing is it required pdm_configure

after up gradation. the error message is in attachment

Thanks & Regards,

vijaybabu

Hi,

Could you look at the install.log file? What error   Message write? Also you can look to stdlog file or configuration log file.

Installation is configuring SDM so don’t need  pdm_configure after installation.

Türker,

Best Regards

Hi Birolutuker.kara

i am getting status in stdlog file

02/10 18:17:01.00 BLR_SDM_APP options_mgr 908 SIGNIFICANT options_mgr.c 1757 NX_INSTALL sym: CMDB val: NOTSTANDALONE
02/10 18:17:01.42 BLR_SDM_APP options_mgr 1852 SIGNIFICANT options_mgr.c 1760 NX_DEINSTALL sym: VIZ_INSTALLED val: NoVaLue
02/10 18:17:01.84 BLR_SDM_APP options_mgr 2696 SIGNIFICANT options_mgr.c 1760 NX_DEINSTALL sym: CMDB_VISUALIZER val: NoVaLue
02/10 18:17:02.27 BLR_SDM_APP options_mgr 3824 SIGNIFICANT options_mgr.c 1757 NX_INSTALL sym: SA_SERVER_ON_PRIMARY val: YES
02/10 18:17:02.69 BLR_SDM_APP options_mgr 2404 SIGNIFICANT options_mgr.c 1757 NX_INSTALL sym: LDAP_MAX_FETCH val: 100
02/10 18:17:03.19 BLR_SDM_APP options_mgr 2500 SIGNIFICANT options_mgr.c 1757 NX_INSTALL sym: SERVER_TYPE val: 2
02/10 18:17:03.61 BLR_SDM_APP options_mgr 3396 SIGNIFICANT options_mgr.c 1757 NX_INSTALL sym: BACKGROUND_SERVERS val: BLR_SDM_BCKGRND,BLR_SDM_STANDBY
02/10 18:17:04.03 BLR_SDM_APP options_mgr 3988 SIGNIFICANT options_mgr.c 1757 NX_INSTALL sym: RF val: 1
02/10 18:17:04.53 BLR_SDM_APP options_mgr 3604 SIGNIFICANT options_mgr.c 1757 NX_INSTALL sym: RF_OVERRIDE_LINKED val: 1
02/10 18:17:04.95 BLR_SDM_APP options_mgr 3904 SIGNIFICANT options_mgr.c 1757 NX_INSTALL sym: DB_TYPE val: SQL
02/10 18:17:05.41 BLR_SDM_APP options_mgr 3280 SIGNIFICANT options_mgr.c 1757 NX_INSTALL sym: DB_NODE val: BLR_SDM_BCKGRND
02/10 18:17:05.91 BLR_SDM_APP options_mgr 3128 SIGNIFICANT options_mgr.c 1757 NX_INSTALL sym: DB_STUFF val: mdb
02/10 18:17:06.34 BLR_SDM_APP options_mgr 3352 SIGNIFICANT options_mgr.c 1757 NX_INSTALL sym: DB_USERID val: mdbadmin
02/10 18:17:06.78 BLR_SDM_APP options_mgr 3656 SIGNIFICANT options_mgr.c 1757 NX_INSTALL sym: DB_PORT val: 1433
02/10 18:17:07.33 BLR_SDM_APP options_mgr 2112 SIGNIFICANT options_mgr.c 1757 NX_INSTALL sym: JDBC_DRIVER val: com.microsoft.sqlserver.jdbc.SQLServerDriver
02/10 18:17:07.77 BLR_SDM_APP options_mgr 1132 SIGNIFICANT options_mgr.c 1757 NX_INSTALL sym: CAWF_CATALINA_BASE val: $NX_ROOT/bopcfg/www/CATALINA_BASE_WF
02/10 18:17:08.20 BLR_SDM_APP options_mgr 3880 SIGNIFICANT options_mgr.c 1757 NX_INSTALL sym: SLUMP_ID val: 7538
02/10 18:17:17.72 BLR_SDM_APP options_mgr 3788 SIGNIFICANT options_mgr.c 1760 NX_DEINSTALL sym: REST_INSTALLED val: NoVaLue
02/10 18:17:18.28 BLR_SDM_APP options_mgr 2952 SIGNIFICANT options_mgr.c 1757 NX_INSTALL sym: FS_INSTALLED val: Yes
02/10 18:17:18.69 BLR_SDM_APP options_mgr 1844 SIGNIFICANT options_mgr.c 1757 NX_INSTALL sym: FS_SERVLET_URL val: http://BLR_SDM_APP:8040/cafedsearch/sdm/search
02/10 18:17:25.95 BLR_SDM_APP pdm_d_mgr 3608 SIGNIFICANT ServerStatusMonitor. 1569 Waited 12286 seconds for the RF Broker to respond to server list request
02/10 18:17:37.97 BLR_SDM_APP web-engine 2976 SIGNIFICANT webengine.c 2201 Enabling Low Fragmentation Heap succeeded.
02/10 18:17:38.64 BLR_SDM_APP pdm_tomcat 3772 SIGNIFICANT pdm_tomcat.c 1420 Stopping SERVICEDESK Tomcat javaw process (pid=-1): "C:\Program Files (x86)\CA\SC\JRE\1.8.0_112\bin\javaw" -Xrs -Djava.net.preferIPv4Stack=false -Xms64M -Xmx1024M -Djaas.config=C:\PROGRA~2\CA\SERVIC~1\add-ons\caflow\jaas.config -Djava.security.auth.login.config=C:\PROGRA~2\CA\SERVIC~1\add-ons\caflow\jaas.config -Djdbc.baseDriver=com.microsoft.sqlserver.jdbc.SQLServerDriver -Djavax.xml.transform.TransformerFactory=com.sun.org.apache.xalan.internal.xsltc.trax.TransformerFactoryImpl -Dsun.io.useCanonCaches=false -Djava.awt.headless=true -Djava.endorsed.dirs="C:\Program Files (x86)\CA\SC\tomcat\8.5.6"\common\endorsed -classpath "C:\Program Files (x86)\CA\SC\tomcat\8.5.6"\common\lib\tools.jar;"C:\Program Files (x86)\CA\SC\JRE\1.8.0_112"\lib\tools.jar;"C:\Program Files (x86)\CA\SC\tomcat\8.5.6"\bin\bootstrap.jar;"C:\Program Files (x86)\CA\SC\tomcat\8.5.6"\bin\tomcat-juli.jar;C:\PROGRA~2\CA\SERVIC~1\java\lib\sqljdbc.jar;C:\PROGRA~2\CA\SERVIC~1\java\lib\ojdbc14.jar -Dcatalina.base=C:\PROGRA~2\CA\SERVIC~1\bopcfg\www\CATALINA_BASE -Dcatalina.home="C:\Program Files (x86)\CA\SC\tomcat\8.5.6" -Djava.io.tmpdir=C:\PROGRA~2\CA\SERVIC~1\bopcfg\www\CATALINA_BASE\temp org.apache.catalina.startup.Bootstrap stop
02/10 18:17:40.71 BLR_SDM_APP pdm_tomcat 2180 SIGNIFICANT pdm_tomcat.c 1373 Starting SERVICEDESK Tomcat: "C:\Program Files (x86)\CA\SC\JRE\1.8.0_112\bin\javaw" -Xrs -Djava.net.preferIPv4Stack=false -Xms64M -Xmx1024M -Djaas.config=C:\PROGRA~2\CA\SERVIC~1\add-ons\caflow\jaas.config -Djava.security.auth.login.config=C:\PROGRA~2\CA\SERVIC~1\add-ons\caflow\jaas.config -Djdbc.baseDriver=com.microsoft.sqlserver.jdbc.SQLServerDriver -Djavax.xml.transform.TransformerFactory=com.sun.org.apache.xalan.internal.xsltc.trax.TransformerFactoryImpl -Dsun.io.useCanonCaches=false -Djava.awt.headless=true -Djava.endorsed.dirs="C:\Program Files (x86)\CA\SC\tomcat\8.5.6"\common\endorsed -classpath "C:\Program Files (x86)\CA\SC\tomcat\8.5.6"\common\lib\tools.jar;"C:\Program Files (x86)\CA\SC\JRE\1.8.0_112"\lib\tools.jar;"C:\Program Files (x86)\CA\SC\tomcat\8.5.6"\bin\bootstrap.jar;"C:\Program Files (x86)\CA\SC\tomcat\8.5.6"\bin\tomcat-juli.jar;C:\PROGRA~2\CA\SERVIC~1\java\lib\sqljdbc.jar;C:\PROGRA~2\CA\SERVIC~1\java\lib\ojdbc14.jar -Dcatalina.base=C:\PROGRA~2\CA\SERVIC~1\bopcfg\www\CATALINA_BASE -Dcatalina.home="C:\Program Files (x86)\CA\SC\tomcat\8.5.6" -Djava.io.tmpdir=C:\PROGRA~2\CA\SERVIC~1\bopcfg\www\CATALINA_BASE\temp org.apache.catalina.startup.Bootstrap start
02/10 18:17:40.73 BLR_SDM_APP pdm_tomcat 2180 SIGNIFICANT pdm_tomcat.c 1384 SERVICEDESK Tomcat javaw process started (pid=3732)
02/10 18:17:55.97 BLR_SDM_APP pdm_d_mgr 3608 SIGNIFICANT ServerStatusMonitor. 1569 Waited 12316 seconds for the RF Broker to respond to server list request
02/10 18:17:56.92 BLR_SDM_APP pdm_tomcat 2592 SIGNIFICANT pdm_tomcat.c 1420 Stopping SERVICEDESK Tomcat javaw process (pid=-1): "C:\Program Files (x86)\CA\SC\JRE\1.8.0_112\bin\javaw" -Xrs -Djava.net.preferIPv4Stack=false -Xms64M -Xmx1024M -Djaas.config=C:\PROGRA~2\CA\SERVIC~1\add-ons\caflow\jaas.config -Djava.security.auth.login.config=C:\PROGRA~2\CA\SERVIC~1\add-ons\caflow\jaas.config -Djdbc.baseDriver=com.microsoft.sqlserver.jdbc.SQLServerDriver -Djavax.xml.transform.TransformerFactory=com.sun.org.apache.xalan.internal.xsltc.trax.TransformerFactoryImpl -Dsun.io.useCanonCaches=false -Djava.awt.headless=true -Djava.endorsed.dirs="C:\Program Files (x86)\CA\SC\tomcat\8.5.6"\common\endorsed -classpath "C:\Program Files (x86)\CA\SC\tomcat\8.5.6"\common\lib\tools.jar;"C:\Program Files (x86)\CA\SC\JRE\1.8.0_112"\lib\tools.jar;"C:\Program Files (x86)\CA\SC\tomcat\8.5.6"\bin\bootstrap.jar;"C:\Program Files (x86)\CA\SC\tomcat\8.5.6"\bin\tomcat-juli.jar;C:\PROGRA~2\CA\SERVIC~1\java\lib\sqljdbc.jar;C:\PROGRA~2\CA\SERVIC~1\java\lib\ojdbc14.jar -Dcatalina.base=C:\PROGRA~2\CA\SERVIC~1\bopcfg\www\CATALINA_BASE -Dcatalina.home="C:\Program Files (x86)\CA\SC\tomcat\8.5.6" -Djava.io.tmpdir=C:\PROGRA~2\CA\SERVIC~1\bopcfg\www\CATALINA_BASE\temp org.apache.catalina.startup.Bootstrap stop
02/10 18:18:03.46 BLR_SDM_APP dbload 2380 SIGNIFICANT dbload.c 647 Dbload Started - Parms: -u "C:\PROGRA~2\CA\SERVIC~1\data\upd_usp_servers_load.dat"
02/10 18:18:03.62 BLR_SDM_APP sql_agent 3144 SIGNIFICANT sql_agent.c 245 STARTUP of sql_agent:mdb:dbload-#2380:
02/10 18:18:04.90 BLR_SDM_APP dbload 2380 SIGNIFICANT dbload.c 766 Dbload Completed
02/10 18:18:04.90 BLR_SDM_APP sql_agent 3144 SIGNIFICANT sql_agent.c 282 SHUTDOWN of sql_agent:mdb:dbload-#2380:
02/10 18:18:07.23 BLR_SDM_APP options_mgr 3940 SIGNIFICANT options_mgr.c 1757 NX_INSTALL sym: RF val: 1
02/10 18:18:07.65 BLR_SDM_APP options_mgr 3688 SIGNIFICANT options_mgr.c 1760 NX_DEINSTALL sym: RF_OVERRIDE_LINKED val: NoVaLue
02/10 18:18:09.37 BLR_SDM_APP pdm_tomcat 2176 SIGNIFICANT pdm_tomcat.c 1420 Stopping SERVICEDESK Tomcat javaw process (pid=-1): "C:\Program Files (x86)\CA\SC\JRE\1.8.0_112\bin\javaw" -Xrs -Djava.net.preferIPv4Stack=false -Xms64M -Xmx1024M -Djaas.config=C:\PROGRA~2\CA\SERVIC~1\add-ons\caflow\jaas.config -Djava.security.auth.login.config=C:\PROGRA~2\CA\SERVIC~1\add-ons\caflow\jaas.config -Djdbc.baseDriver=com.microsoft.sqlserver.jdbc.SQLServerDriver -Djavax.xml.transform.TransformerFactory=com.sun.org.apache.xalan.internal.xsltc.trax.TransformerFactoryImpl -Dsun.io.useCanonCaches=false -Djava.awt.headless=true -Djava.endorsed.dirs="C:\Program Files (x86)\CA\SC\tomcat\8.5.6"\common\endorsed -classpath "C:\Program Files (x86)\CA\SC\tomcat\8.5.6"\common\lib\tools.jar;"C:\Program Files (x86)\CA\SC\JRE\1.8.0_112"\lib\tools.jar;"C:\Program Files (x86)\CA\SC\tomcat\8.5.6"\bin\bootstrap.jar;"C:\Program Files (x86)\CA\SC\tomcat\8.5.6"\bin\tomcat-juli.jar;C:\PROGRA~2\CA\SERVIC~1\java\lib\sqljdbc.jar;C:\PROGRA~2\CA\SERVIC~1\java\lib\ojdbc14.jar -Dcatalina.base=C:\PROGRA~2\CA\SERVIC~1\bopcfg\www\CATALINA_BASE -Dcatalina.home="C:\Program Files (x86)\CA\SC\tomcat\8.5.6" -Djava.io.tmpdir=C:\PROGRA~2\CA\SERVIC~1\bopcfg\www\CATALINA_BASE\temp org.apache.catalina.startup.Bootstrap stop
02/10 18:18:34.91 BLR_SDM_APP pdm_d_mgr 3608 SIGNIFICANT ServerStatusMonitor. 1569 Waited 12355 seconds for the RF Broker to respond to server list request
02/10 18:19:04.91 BLR_SDM_APP pdm_d_mgr 3608 SIGNIFICANT ServerStatusMonitor. 1569 Waited 12385 seconds for the RF Broker to respond to server list request
02/10 18:19:34.93 BLR_SDM_APP pdm_d_mgr 3608 SIGNIFICANT ServerStatusMonitor. 1569 Waited 12415 seconds for the RF Broker to respond to server list request
02/10 18:20:04.93 BLR_SDM_APP pdm_d_mgr 3608 SIGNIFICANT ServerStatusMonitor. 1569 Waited 12445 seconds for the RF Broker to respond to server list request
02/10 18:20:34.93 BLR_SDM_APP pdm_d_mgr 3608 SIGNIFICANT ServerStatusMonitor. 1569 Waited 12475 seconds for the RF Broker to respond to server list request
02/10 18:21:04.94 BLR_SDM_APP pdm_d_mgr 3608 SIGNIFICANT ServerStatusMonitor. 1569 Waited 12505 seconds for the RF Broker to respond to server list request
02/10 18:21:34.94 BLR_SDM_APP pdm_d_mgr 3608 SIGNIFICANT ServerStatusMonitor. 1569 Waited 12535 seconds for the RF Broker to respond to server list request
02/10 18:22:04.94 BLR_SDM_APP pdm_d_mgr 3608 SIGNIFICANT ServerStatusMonitor. 1569 Waited 12565 seconds for the RF Broker to respond to server list request
02/10 18:22:34.94 BLR_SDM_APP pdm_d_mgr 3608 SIGNIFICANT ServerStatusMonitor. 1569 Waited 12595 seconds for the RF Broker to respond to server list request
02/10 18:23:04.94 BLR_SDM_APP pdm_d_mgr 3608 SIGNIFICANT ServerStatusMonitor. 1569 Waited 12625 seconds for the RF Broker to respond to server list request
02/10 18:23:24.94 BLR_SDM_APP slump_nxd 2520 SIGNIFICANT server.c 4307 SLUMP Build(alb-205): Up Time(3 hr 30 min 45 sec) Sent (1475) Received (1575) Ports in Use (9) Processes (6) Fast Channel (2)
02/10 18:23:34.94 BLR_SDM_APP pdm_d_mgr 3608 SIGNIFICANT ServerStatusMonitor. 1569 Waited 12655 seconds for the RF Broker to respond to server list request
02/10 18:24:04.94 BLR_SDM_APP pdm_d_mgr 3608 SIGNIFICANT ServerStatusMonitor. 1569 Waited 12685 seconds for the RF Broker to respond to server list request
02/10 18:24:35.34 BLR_SDM_APP pdm_d_mgr 3608 SIGNIFICANT ServerStatusMonitor. 1569 Waited 12716 seconds for the RF Broker to respond to server list request
02/10 18:25:05.35 BLR_SDM_APP pdm_d_mgr 3608 SIGNIFICANT ServerStatusMonitor. 1569 Waited 12746 seconds for the RF Broker to respond to server list request
02/10 18:25:35.37 BLR_SDM_APP pdm_d_mgr 3608 SIGNIFICANT ServerStatusMonitor. 1569 Waited 12776 seconds for the RF Broker to respond to server list request
02/10 18:26:05.37 BLR_SDM_APP pdm_d_mgr 3608 SIGNIFICANT ServerStatusMonitor. 1569 Waited 12806 seconds for the RF Broker to respond to server list request

Hi Vijay_Babu,

If server is linked = 1 (configured is yes) in usp_servers table before this step you can get this error. You can check it before installation or this step. If linked = 1 then you can set linked value "0" on database level then retry install

Türker

Vijay Babu,

Do these servers have SDM up and running?

BLR_SDM_BCKGRND

BLR_SDM_STANDBY

Was SDM upgraded successfully on both the above?

Are you able to login to the SDM UI on the current BG server successfully?

The reason behind the above questions is this error on your APP.  It's not starting because its not getting response from BG.

02/10 18:18:34.91 BLR_SDM_APP pdm_d_mgr 3608 SIGNIFICANT ServerStatusMonitor. 1569 Waited 12355 seconds for the RF Broker to respond to server list request

Thx

_R

Hi 

Finally I installed ca sdm 14.1 to 17.0 successfully in our test server.

but some thing went wrong in installation.contacts and incidents are not showing.

i am planning  revert using virtual machine snap shot.and i will start from scratch. 

There are 3 servers registered and all have the same schema checksum

Thankyou for your support.

Regards,

vijaybabu

Thank you for the update Vijay Babu.

Do you happen to have followed some specific steps to overcome the error your app server was originally showing? If so, would you mind sharing it with the community so others can benefit too?

02/10 18:18:34.91 BLR_SDM_APP pdm_d_mgr 3608 SIGNIFICANT ServerStatusMonitor. 1569 Waited 12355 seconds for the RF Broker to respond to server list request

Contacts/Incidents not showing - maybe you have some custom forms and you need to recustomize them to the 17.0 standard. Check this out: Customization Upgrade Utility - CA Service Management - 17.0 - CA Technologies Documentation 

_R

Hi Raghu rudraraju,

I tried customization up gradation based on you shared document link.

But the customized forms are appearing. but i am unable to see incident page, and contact page.

Or if i make original www rather than customized www folder .i can see contacts, incidents.

Is there any other way to resolve this issue.

Thanks & Regards,

Vijaybabu

Hey Vijaybabu,

I think we could use a new thread on this to keep the topic separate and not cause confusion with the original question you had.

Based on what you stated though, the customization migration tool should (most cases) be able to upgrade your existing old release custom forms to new release format.  Other option is for you to do the same manually.

_R