CA Service Management

Expand all | Collapse all

sdm14.1 advance avalaibility

  • 1.  sdm14.1 advance avalaibility

    Posted Mar 28, 2017 04:25 PM

    Hello Team

     

    we have installed sdm 14.1 with Advance Avalaibility option. one sdm application server ,one is background server, one is stanby server and one is database server. Total 4 servers.

     

    Now we tested the ticket by creating from application server . so it also reflecting to the background server which is perfect. some more testing i was doing and found that

     

    1.if background sdm service is OFFand standby sdm service is ON then application sdm server not work. Like sdm application login page is opening but i cannot login as it is giving error "servicedesk contact not found. session timeout". 

     

    2.if Backgroud  SDM service is ON and standby sdm service is OFF then application sdm server still work and i can login to the application and do the activity.

     

     

    so basically sdm application server works with sdm background server so if bg sdm not running then it affect to sdm application server also. No matter standby sdm is ON or OFF.

     

    Moreover, How can i change standby sdm server to BG sdm server and BG sdm server to standby sdm server? is there any command of it ?

     

    thanks



  • 2.  Re: sdm14.1 advance avalaibility

    Broadcom Employee
    Posted Mar 28, 2017 04:38 PM

    Aamir......

     

    When you say that "if bg sdm not running", was a failover to the Standby server to promote it to the Background server done?



  • 3.  Re: sdm14.1 advance avalaibility

    Posted Mar 29, 2017 08:11 AM

    Hi Amir,

    I will try to explain a few things here to answer your questions and provide some insight on how this all works.

     

    I will answer your questions below each one here:

     

    1.if background sdm service is OFFand standby sdm service is ON then application sdm server not work. Like sdm application login page is opening but i cannot login as it is giving error "servicedesk contact not found. session timeout". 

    JON:  This is expected.  The background server runs the bop_auth process which is what checks service desk for the contact of the user attempting to log in, and pulls its appropriate access type and role.  Thus a background server is needed in order to log into the application from an app server.  The standby server is used for just that - to "stand-by" and if needed, you can failover from the background server TO the standby server, making the standby server a background server.  This is done via a command that you would run on the standby server which is "pdm_server_control -b"  - when you run that command on a running standby server, it will promote that server to be the background server, and then services will automatically stop on the original background server.  You can then start that original background server back up, and it will start up as a standby server.  You can then fail back over to the original background by running that same command on the original background server.

     

    2.if Backgroud  SDM service is ON and standby sdm service is OFF then application sdm server still work and i can login to the application and do the activity.

    JON:  Correct, this is expected.

     

    so basically sdm application server works with sdm background server so if bg sdm not running then it affect to sdm application server also. No matter standby sdm is ON or OFF.'

    JON:  Correct, the app servers do not depend on the standby server at all, they only depend on the background server.

     

    Moreover, How can i change standby sdm server to BG sdm server and BG sdm server to standby sdm server? is there any command of it ?

    JON:  As I mentioned in my answer to question #1 above, this is done via a command that you would run on the standby server which is "pdm_server_control -b"  - when you run that command on a running standby server, it will promote that server to be the background server, and then services will automatically stop on the original background server.  You can then start that original background server back up, and it will start up as a standby server.  You can then fail back over to the original background by running that same command on the original background server.

     

    Additionally, you can find a lot more information, including a video on how to use Advanced Availability features on the documentation site which you can find here:   Install CA SDM Using Advanced Availability Configuration - CA Service Management - 14.1 - CA Technologies Documentation 

     

    Hope this helps clear things up a bit for you.

     

    Thanks,

    Jon I.



  • 4.  Re: sdm14.1 advance avalaibility

    Posted Mar 29, 2017 08:18 AM

    The Advanced Availability alone only provide what they say. Mostly providing you to do maintenance with minimal impact to the business. that it and

    Then there is no automatic load balancing or failover. To promote a standby server to a be the background and/ or to do several actions around your different servers you will need to use the pdm_server_control command

     

    Usage: pdm_server_control -h | -b | -q interval [-s server_name] | -t | -c [-s server_name] | -v

    Where:
           -h
                displays the help page.

           -b
                This option notifies a local standby server to become the
                background server.  The standby server must already be running.
                If the server is not running, it is started but no failover is
                performed; to start a failover, run the command again.

           -q interval [-s server_name]
                This option notifies a local or remote application server to
                quiesce in a specified time interval.  This interval is the
                number of seconds before the server goes offline.  When using
                this option without a server_name, the local server is notified
                to quiesce.  This option cannot be used for a background or a
                standby server.

           -t
                Display server type of this SDM AA Server.

           -c [-s server_name]
                This option notifies a local or remote application server to
                cancel the previous quiesce request.

           -v
                Suppress version control on next startup of this server.
                This option prevents synchronizing this server with the background
                and should be used only when CA Service Desk files have been
                manually updated on this server.

     

    With all that say  putting a load balancer and few automated scripts for fail over you may come to something really close to High Availability with minimal invest.

     

    Hope this clarify.

    \J



  • 5.  Re: sdm14.1 advance avalaibility

    Posted Mar 29, 2017 08:19 AM

    look like Jon and myself  was responding simultaneously

    Active community. that great !



  • 6.  Re: sdm14.1 advance avalaibility

    Posted Apr 03, 2017 05:52 AM

    Thanks Mayer & Jon. 

     

    we have standalone sdm 12.6(conventional) which we migrated to 14.1 sdm by running the setup file. Migrated successfully. Now i took backup of migrated mdb and restored on our new architecture high avalability  sdm14.1  mdb. Restored successfully. Now when i m reconfiguring Background Server sdm its giving error. Cannot connect to database . Even the database server is pingable. What could be the issue??

     



  • 7.  Re: sdm14.1 advance avalaibility

    Posted Apr 03, 2017 06:16 AM

    I then suppose you have migrated  to a new database server.

    Did you verify that your nx.env refer to the correct MDB host?

    You will also need to recreate the ServiceDesk login on your new SQL instance and link it back to the ServiceDesk user schema of the mdb

    /J



  • 8.  Re: sdm14.1 advance avalaibility

    Posted Apr 03, 2017 06:43 AM

    Hello Mayer

     

     

    i have re created new login and also in nx.env file its correct mdb host but still giving this error cannot conenct db

     



  • 9.  Re: sdm14.1 advance avalaibility

    Posted Apr 03, 2017 07:29 AM

    Ok.

    Any in your configure.log and/ or  in checkdb.0

    can you share any errors from the logs here?

    The error code from SQL is normally evailable in the checkdb.0 log and most of the time self explanatory.

     

    note sure but you may want to look for typo too, SQL been case sensitive

     

    another way for a quick test is to use the  sql_check_db.exe from the bin folder in the command line

     

    ...\Service Desk Manager\bin> sql_check_db.exe -t  -n  MYSQLSERVERNAME -d mdb -o mdbadmin -U ServiceDesk -p MYPASSWORD

     

    below is the full usage but be careful and make sure to only use with the "-t" in your case as you can overwrite some settings like this:

    Usage:
    sql_check_db.exe {-c|-u|-t|-A} [-f] [-s <Primary_Server>] [-n <dbnode>] [ -d <dbname>] [ -U <dbuserid>] [ -p <p
    assword> ] [ -a <web url>]

    Where:
    c - Check Primary Server name
    u - Update Primary server name
    t - Test connection only
    T - Table to test against (default pri)
    f - Force update - do not ask
    s - Primary Server name
    n - Database node (NX_DB_NODE)
    d - Database name (NX_DB_STUFF)
    o - Table Owner name (NX_MDB_OWNER)
    U - Login userid (NX_DB_USERID)
    p - Password
    a - Register application web url
    A - De-register application
    r - Register application id

    must return like below if successful:

     

    SUCCESS - Test connection was successful.
    CONN_OK

    Regards,

    /J



  • 10.  Re: sdm14.1 advance avalaibility

    Posted Apr 03, 2017 09:36 AM

    Hi Mayer

     

    I have pasted logs of dbcheck and configure ..Please check

     

    db check log

     

     

    04/03 01:13:34.33 SDM14BG sql_ckeckdb 1256 ERROR sqlclass.c 473 Failed to logon to SQL Server (SDM14) Reason: [Microsoft OLE DB Provider for SQL Server] [ SQL Code=4060 SQL State=42000] Cannot open database "mdb" requested by the login. The login failed.
    04/03 02:13:31.60 SDM14BG sql_ckeckdb 1500 ERROR sqlclass.c 473 Failed to logon to SQL Server (SDM14) Reason: [Microsoft OLE DB Provider for SQL Server] [ SQL Code=4060 SQL State=42000] Cannot open database "mdb" requested by the login. The login failed.
    04/03 02:15:29.06 SDM14BG sql_ckeckdb 1816 ERROR sqlclass.c 473 Failed to logon to SQL Server (SDM14) Reason: [Microsoft OLE DB Provider for SQL Server] [ SQL Code=4060 SQL State=42000] Cannot open database "mdb" requested by the login. The login failed.
    04/03 02:36:08.30 SDM14BG sql_ckeckdb 2276 ERROR sqlclass.c 473 Failed to logon to SQL Server (SDM14) Reason: [Microsoft OLE DB Provider for SQL Server] [ SQL Code=4060 SQL State=42000] Cannot open database "mdb" requested by the login. The login failed.
    04/03 02:37:09.04 SDM14BG sql_ckeckdb 2380 ERROR sqlclass.c 473 Failed to logon to SQL Server (SDM14) Reason: [Microsoft OLE DB Provider for SQL Server] [ SQL Code=4060 SQL State=42000] Cannot open database "mdb" requested by the login. The login failed.
    04/03 03:29:00.70 SDM14BG sql_ckeckdb 3040 ERROR sqlclass.c 473 Failed to logon to SQL Server (SDM14) Reason: [Microsoft OLE DB Provider for SQL Server] [ SQL Code=4060 SQL State=42000] Cannot open database "mdb" requested by the login. The login failed.
    04/03 03:29:58.32 SDM14BG sql_ckeckdb 724 ERROR sqlclass.c 473 Failed to logon to SQL Server (SDM14) Reason: [Microsoft OLE DB Provider for SQL Server] [ SQL Code=4060 SQL State=42000] Cannot open database "mdb" requested by the login. The login failed.
    04/03 03:39:51.93 SDM14BG sql_ckeckdb 3000 ERROR sqlclass.c 473 Failed to logon to SQL Server (SDM14) Reason: [Microsoft OLE DB Provider for SQL Server] [ SQL Code=4060 SQL State=42000] Cannot open database "mdb" requested by the login. The login failed.
    04/03 03:41:11.28 SDM14BG sql_ckeckdb 2424 ERROR sqlclass.c 473 Failed to logon to SQL Server (SDM14) Reason: [Microsoft OLE DB Provider for SQL Server] [ SQL Code=4060 SQL State=42000] Cannot open database "mdb" requested by the login. The login failed.
    04/03 04:48:05.82 SDM14BG sql_ckeckdb 2396 ERROR sqlclass.c 473 Failed to logon to SQL Server (SDM14) Reason: [Microsoft OLE DB Provider for SQL Server] [ SQL Code=4060 SQL State=42000] Cannot open database "mdb" requested by the login. The login failed.
    04/03 04:48:43.35 SDM14BG sql_ckeckdb 1732 ERROR sqlclass.c 473 Failed to logon to SQL Server (SDM14) Reason: [Microsoft OLE DB Provider for SQL Server] [ SQL Code=4060 SQL State=42000] Cannot open database "mdb" requested by the login. The login failed.
    04/03 04:49:42.82 SDM14BG sql_ckeckdb 1312 ERROR sqlclass.c 473 Failed to logon to SQL Server (SDM14) Reason: [Microsoft OLE DB Provider for SQL Server] [ SQL Code=4060 SQL State=42000] Cannot open database "mdb" requested by the login. The login failed.
    04/03 04:54:21.04 SDM14BG sql_ckeckdb 2848 ERROR sqlclass.c 473 Failed to logon to SQL Server (SDM14) Reason: [Microsoft OLE DB Provider for SQL Server] [ SQL Code=4060 SQL State=42000] Cannot open database "mdb" requested by the login. The login failed.
    04/03 04:54:47.99 SDM14BG sql_ckeckdb 1312 ERROR sqlclass.c 473 Failed to logon to SQL Server (SDM14) Reason: [Microsoft OLE DB Provider for SQL Server] [ SQL Code=4060 SQL State=42000] Cannot open database "mdb" requested by the login. The login failed.
    04/03 05:00:13.60 SDM14BG sql_ckeckdb 132 ERROR sqlclass.c 473 Failed to logon to SQL Server (SDM14) Reason: [Microsoft OLE DB Provider for SQL Server] [ SQL Code=4060 SQL State=42000] Cannot open database "mdb" requested by the login. The login failed.
    04/03 05:01:39.09 SDM14BG sql_ckeckdb 796 ERROR sqlclass.c 473 Failed to logon to SQL Server (SDM14) Reason: [Microsoft OLE DB Provider for SQL Server] [ SQL Code=4060 SQL State=42000] Cannot open database "mdb" requested by the login. The login failed.
    04/03 05:02:36.28 SDM14BG sql_ckeckdb 2552 ERROR sqlclass.c 473 Failed to logon to SQL Server (SDM14) Reason: [Microsoft OLE DB Provider for SQL Server] [ SQL Code=4060 SQL State=42000] Cannot open database "mdb" requested by the login. The login failed.
    04/03 05:03:51.13 SDM14BG sql_ckeckdb 2816 ERROR sqlclass.c 473 Failed to logon to SQL Server (SDM14) Reason: [Microsoft OLE DB Provider for SQL Server] [ SQL Code=4060 SQL State=42000] Cannot open database "mdb" requested by the login. The login failed.
    04/03 05:05:02.32 SDM14BG sql_ckeckdb 2032 ERROR sqlclass.c 473 Failed to logon to SQL Server (SDM14) Reason: [Microsoft OLE DB Provider for SQL Server] [ SQL Code=4060 SQL State=42000] Cannot open database "mdb" requested by the login. The login failed.
    04/03 05:05:11.98 SDM14BG sql_ckeckdb 2560 ERROR sqlclass.c 473 Failed to logon to SQL Server (SDM14) Reason: [Microsoft OLE DB Provider for SQL Server] [ SQL Code=4060 SQL State=42000] Cannot open database "mdb" requested by the login. The login failed.
    04/03 05:05:28.81 SDM14BG sql_ckeckdb 1348 ERROR sqlclass.c 473 Failed to logon to SQL Server (SDM14) Reason: [Microsoft OLE DB Provider for SQL Server] [ SQL Code=4060 SQL State=42000] Cannot open database "mdb" requested by the login. The login failed.
    04/03 05:11:06.82 SDM14BG sql_ckeckdb 1420 ERROR sqlclass.c 473 Failed to logon to SQL Server (SDM14) Reason: [Microsoft OLE DB Provider for SQL Server] [ SQL Code=4060 SQL State=42000] Cannot open database "mdb" requested by the login. The login failed.
    04/03 05:12:04.45 SDM14BG sql_ckeckdb 2500 ERROR sqlclass.c 473 Failed to logon to SQL Server (SDM14) Reason: [Microsoft OLE DB Provider for SQL Server] [ SQL Code=4060 SQL State=42000] Cannot open database "mdb" requested by the login. The login failed.
    04/03 05:14:50.25 SDM14BG sql_ckeckdb 724 ERROR sqlclass.c 473 Failed to logon to SQL Server (SDM14) Reason: [Microsoft OLE DB Provider for SQL Server] [ SQL Code=4060 SQL State=42000] Cannot open database "mdb" requested by the login. The login failed.

     

     

     

     

    configure log

     

     

    04/03 06:32:24.926 INFO ConfigUI.java 599 Logger initialization complete. Log level set to INFO
    04/03 06:32:24.926 INFO ConfigUI.java 210 Cmdline: java -Djava.net.preferIPv4Stack=false -DNX_ROOT=$NX_ROOT class com.ca.ServicePlus.configui.ConfigUI C:\Program Files (x86)\CA\Service Desk Manager\bin\pdm_configure.exe
    04/03 06:32:24.973 INFO ConfigUIUtils.java 85 NX_ROOT => C:\PROGRA~2\CA\SERVIC~1
    04/03 06:32:24.973 INFO ConfigUIUtils.java 86 java.library.path => C:\Program Files (x86)\CA\SC\JRE\1.7.0_10\bin;C:\Windows\Sun\Java\bin;C:\Windows\system32;C:\Windows;C:\Program Files (x86)\CA\Service Desk Manager\bin;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Program Files (x86)\Microsoft SQL Server\110\Tools\Binn\ManagementStudio\;C:\Program Files (x86)\Microsoft SQL Server\110\Tools\Binn\;C:\Program Files\Microsoft SQL Server\110\Tools\Binn\;C:\Program Files (x86)\Microsoft Visual Studio 10.0\Common7\IDE\PrivateAssemblies\;C:\Program Files (x86)\Microsoft SQL Server\110\DTS\Binn\;C:\Program Files\Microsoft SQL Server\110\DTS\Binn\;.
    04/03 06:32:24.973 INFO ConfigUIUtils.java 88 os.name => Windows Server 2012
    04/03 06:32:24.973 INFO ConfigUIUtils.java 89 user.name => Administrator
    04/03 06:32:25.082 INFO ConfigUIUtils.java 427 osGetEnv(NX_DEBUG_CONFIG)=
    04/03 06:32:25.176 INFO ConfigUI.java 303 Running prerequisites installer.
    Prerequisite.class.isAssignableFrom(prereqClazz) = true
    Prerequisite.class.isAssignableFrom(prereqClazz) = true
    Prerequisite.class.isAssignableFrom(prereqClazz) = true
    04/03 06:32:26.379 INFO ServerConfigPage.java 121 ## config.server_config_type :advanced
    04/03 06:32:28.177 INFO PreDatabasePage.java 121 ## Setting Property accounts.privileged_user.name to (ServiceDesk)
    04/03 06:32:32.458 INFO ? ? ERROR: AHD50072:Unable to log in to SQL Server
    04/03 06:32:32.708 INFO ? ? Process sql_check_db completed with exit code 99
    04/03 06:32:32.708 INFO SQLDatabasePage.java 486 ## Value of UspServerInfo.hasDefaultData : false
    04/03 06:32:32.708 INFO SQLDatabasePage.java 519 ## Background Servername () ; Primary Servername () ; Local Servername (SDM14BG)
    04/03 06:32:32.723 INFO SQLDatabasePage.java 762 Running: sqlcmd -S SDM14 -U sa -P <password> -l 5 -i tmp_sql.sql
    04/03 06:32:32.801 INFO SQLDatabasePage.java 774 Changed database context to 'mdb'.

    04/03 06:32:32.801 INFO SQLDatabasePage.java 774

    04/03 06:32:32.801 INFO SQLDatabasePage.java 774 ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

    04/03 06:32:32.801 INFO SQLDatabasePage.java 774 Microsoft SQL Server 2012 - 11.0.2100.60 (X64)

    04/03 06:32:32.801 INFO SQLDatabasePage.java 774 Feb 10 2012 19:39:15

    04/03 06:32:32.801 INFO SQLDatabasePage.java 774 Copyright (c) Microsoft Corporation

    04/03 06:32:32.801 INFO SQLDatabasePage.java 774 Enterprise Edition (64-bit) on Windows NT 6.2 <X64> (Build 9200: ) (Hypervisor)

    04/03 06:32:32.801 INFO SQLDatabasePage.java 774

    04/03 06:32:32.801 INFO SQLDatabasePage.java 774 Current user is a member of the sysadmin role

    04/03 06:32:32.801 INFO SQLDatabasePage.java 774

    04/03 06:32:32.801 INFO SQLDatabasePage.java 774 -----------

    04/03 06:32:32.801 INFO SQLDatabasePage.java 774 0

    04/03 06:32:32.864 INFO SQLDatabasePage.java 1127 ## Load default data :
    04/03 06:32:36.645 INFO GeneralPage.java 230 ## BackgroundServerName: (SDM14BG)
    04/03 06:32:39.286 INFO GeneralPage.java 622 ## Current server configuration type is : background
    04/03 06:32:48.879 INFO WebPage.java 225 ## Deploying Webservices : false
    04/03 06:32:53.661 INFO OptionsPage.java 209 Primary server: false
    04/03 06:32:53.661 INFO OptionsPage.java 210 Advanced server: true
    04/03 06:32:53.661 INFO OptionsPage.java 211 Secondary server: false
    04/03 06:32:53.677 INFO UspServerInfo.java 179 ## No default data. Can't execute select query.
    04/03 06:32:55.192 INFO ConfigThread.java 223 ############ Property values ###############
    04/03 06:32:55.192 INFO ConfigThread.java 224 ## general.configuration_type :
    04/03 06:32:55.192 INFO ConfigThread.java 225 ## config.server_config_type :advanced
    04/03 06:32:55.208 INFO ConfigThread.java 226 ## advanced.configuration_type :background_or_standby
    04/03 06:32:55.208 INFO ConfigThread.java 227 ## advanced.server_type :2
    04/03 06:32:55.208 INFO ConfigThread.java 228 ## options.reinit_database :0
    04/03 06:32:55.208 INFO ConfigThread.java 229 ## database.server_conversion :
    04/03 06:32:55.208 INFO ConfigThread.java 230 ############################################
    04/03 06:32:55.208 INFO ConfigThread.java 232 ## Configuring AA Server type (2)
    04/03 06:32:55.208 INFO ConfigThread.java 259 ## isAdvanced (true)
    04/03 06:32:55.223 INFO ConfigThread.java 260 ## isPrimaryServer (false)
    04/03 06:32:55.223 INFO ConfigThread.java 261 ## reloadData (false)
    04/03 06:32:55.223 INFO ConfigThread.java 262 ## forceSetupMDB (false)
    04/03 06:32:55.223 INFO ConfigThread.java 263 ## isBackgroundStandby (true)
    04/03 06:32:55.223 INFO ConfigThread.java 264 ## isBackground (true)
    04/03 06:32:55.223 INFO ConfigThread.java 265 ## isStandBy (false)
    04/03 06:32:55.223 INFO ConfigThread.java 266 ## isAppServer (false)
    04/03 06:32:55.223 INFO ConfigThread.java 267 ## isMinimumConfig (false)
    04/03 06:32:55.223 INFO ConfigThread.java 268 ## hasWebInterface (true)
    04/03 06:32:55.223 INFO ConfigThread.java 269 ## deployWebServices (false)
    04/03 06:32:55.223 INFO ConfigThread.java 270 ## isClient (false)
    04/03 06:32:55.254 INFO ApplyConfigurationTask.java 519 ## No default data is present. Can't get BackgroundServerList.
    04/03 06:32:55.254 INFO ApplyConfigurationTask.java 330 List of Background Servers : (SDM14BG) and localHostName (SDM14BG)
    04/03 06:32:55.333 INFO ConfigThread.java 541 Total number of configuration tasks : 25
    04/03 06:32:55.333 INFO ConfigThread.java 549 Executing task# 1, task name : Create localized resources
    04/03 06:32:55.333 INFO Task.java 214 Running: Create localized resources
    04/03 06:32:55.333 INFO CreateLocalizedResources.java 93 ## Starting resource creation
    04/03 06:32:55.348 INFO CreateLocalizedResources.java 154 End of resource creation;see resource.log for details ##
    04/03 06:32:55.348 INFO ConfigThread.java 589 Configuration progress : 1 out of 25 tasks completed.
    04/03 06:32:55.348 INFO ConfigThread.java 549 Executing task# 2, task name : Apply initial configuration settings
    04/03 06:32:55.348 INFO Task.java 214 Running: Apply initial configuration settings
    04/03 06:32:55.348 INFO ApplyConfigurationTask.java 1922 In createL10Ndata Getting NX_KEY (0x4E580000)
    04/03 06:32:55.348 INFO ApplyConfigurationTask.java 1923 Setting NX_KEY is set to (0x4E580000)
    04/03 06:32:55.348 INFO ApplyConfigurationTask.java 1925 Getting NX_KEY (0x4E580000)
    04/03 06:32:55.348 INFO ApplyConfigurationTask.java 1932 running command: "C:\PROGRA~2\CA\SERVIC~1\bin\pdm_perl" CreateL10N_data.pl -i sa.dat -m C:\PROGRA~2\CA\SERVIC~1\data\merged -o C:\PROGRA~2\CA\SERVIC~1\data\sa_multi.dat -d ENU -l JPN,DEU,FRA,ESN,ITA,PTB,CHS,FRC,ENU
    04/03 06:32:55.567 INFO ? ? stderr > Name "main::LIST_LANGS" used only once: possible typo at CreateL10N_data.pl line 44.
    04/03 06:32:56.083 INFO ? ? stdout >
    04/03 06:32:56.083 INFO ? ? stdout > INPUT_FILE = sa.dat
    04/03 06:32:56.083 INFO ? ? stdout > MERGED_DIR = C:\PROGRA~2\CA\SERVIC~1\data\merged
    04/03 06:32:56.083 INFO ? ? stdout > OUTPUT_FILE = C:\PROGRA~2\CA\SERVIC~1\data\sa_multi.dat
    04/03 06:32:56.083 INFO ? ? stdout > DEFAULT_LANG = ENU
    04/03 06:32:56.083 INFO ? ? stdout > LIST_LANGS = JPN,DEU,FRA,ESN,ITA,PTB,CHS,FRC,ENU
    04/03 06:32:56.083 INFO ? ? stdout >
    04/03 06:32:56.083 INFO ? ? stdout >
    04/03 06:32:56.083 INFO ? ? stdout > merged_file = C:\PROGRA~2\CA\SERVIC~1\data\merged/JPN/sa.dat
    04/03 06:32:56.083 INFO ? ? stdout >
    04/03 06:32:56.083 INFO ? ? stdout > merged_file = C:\PROGRA~2\CA\SERVIC~1\data\merged/DEU/sa.dat
    04/03 06:32:56.083 INFO ? ? stdout >
    04/03 06:32:56.083 INFO ? ? stdout > merged_file = C:\PROGRA~2\CA\SERVIC~1\data\merged/FRA/sa.dat
    04/03 06:32:56.083 INFO ? ? stdout >
    04/03 06:32:56.083 INFO ? ? stdout > merged_file = C:\PROGRA~2\CA\SERVIC~1\data\merged/ESN/sa.dat
    04/03 06:32:56.083 INFO ? ? stdout >
    04/03 06:32:56.083 INFO ? ? stdout > merged_file = C:\PROGRA~2\CA\SERVIC~1\data\merged/ITA/sa.dat
    04/03 06:32:56.083 INFO ? ? stdout >
    04/03 06:32:56.083 INFO ? ? stdout > merged_file = C:\PROGRA~2\CA\SERVIC~1\data\merged/PTB/sa.dat
    04/03 06:32:56.083 INFO ? ? stdout >
    04/03 06:32:56.083 INFO ? ? stdout > merged_file = C:\PROGRA~2\CA\SERVIC~1\data\merged/CHS/sa.dat
    04/03 06:32:56.083 INFO ? ? stdout >
    04/03 06:32:56.083 INFO ? ? stdout > merged_file = C:\PROGRA~2\CA\SERVIC~1\data\merged/FRC/sa.dat
    04/03 06:32:56.083 INFO ? ? stdout >
    04/03 06:32:56.083 INFO ? ? stdout > merged_file = C:\PROGRA~2\CA\SERVIC~1\data\merged/ENU/sa.dat
    04/03 06:32:56.083 INFO ? ? stdout >
    04/03 06:32:56.083 INFO ? ? stdout > skip table = sa_security_group, lang = ENU, default_lang = ENU
    04/03 06:32:56.083 INFO ? ? stdout >
    04/03 06:32:56.083 INFO ? ? stdout >
    04/03 06:32:56.083 INFO ? ? stdout > skip table = sa_security_tool_function, lang = ENU, default_lang = ENU
    04/03 06:32:56.083 INFO ? ? stdout >
    04/03 06:32:56.083 INFO ? ? stdout >
    04/03 06:32:56.099 INFO ApplyConfigurationTask.java 1945 -i exit code = 0
    04/03 06:32:56.099 INFO ApplyConfigurationTask.java 1922 In createL10Ndata Getting NX_KEY (0x4E580000)
    04/03 06:32:56.099 INFO ApplyConfigurationTask.java 1923 Setting NX_KEY is set to (0x4E580000)
    04/03 06:32:56.099 INFO ApplyConfigurationTask.java 1925 Getting NX_KEY (0x4E580000)
    04/03 06:32:56.099 INFO ApplyConfigurationTask.java 1932 running command: "C:\PROGRA~2\CA\SERVIC~1\bin\pdm_perl" CreateL10N_data.pl -i sa_messages.dat -m C:\PROGRA~2\CA\SERVIC~1\data\merged -o C:\PROGRA~2\CA\SERVIC~1\data\sa_messages_multi.dat -d ENU -l JPN,DEU,FRA,ESN,ITA,PTB,CHS,FRC,ENU
    04/03 06:32:56.317 INFO ? ? stderr > Name "main::LIST_LANGS" used only once: possible typo at CreateL10N_data.pl line 44.
    04/03 06:32:56.505 INFO ? ? stdout >
    04/03 06:32:56.505 INFO ? ? stdout > INPUT_FILE = sa_messages.dat
    04/03 06:32:56.505 INFO ? ? stdout > MERGED_DIR = C:\PROGRA~2\CA\SERVIC~1\data\merged
    04/03 06:32:56.505 INFO ? ? stdout > OUTPUT_FILE = C:\PROGRA~2\CA\SERVIC~1\data\sa_messages_multi.dat
    04/03 06:32:56.505 INFO ? ? stdout > DEFAULT_LANG = ENU
    04/03 06:32:56.505 INFO ? ? stdout > LIST_LANGS = JPN,DEU,FRA,ESN,ITA,PTB,CHS,FRC,ENU
    04/03 06:32:56.505 INFO ? ? stdout >
    04/03 06:32:56.505 INFO ? ? stdout >
    04/03 06:32:56.505 INFO ? ? stdout > merged_file = C:\PROGRA~2\CA\SERVIC~1\data\merged/JPN/sa_messages.dat
    04/03 06:32:56.505 INFO ? ? stdout >
    04/03 06:32:56.505 INFO ? ? stdout > lang = JPN, default_lang = ENU
    04/03 06:32:56.505 INFO ? ? stdout >
    04/03 06:32:56.505 INFO ? ? stdout >
    04/03 06:32:56.505 INFO ? ? stdout > merged_file = C:\PROGRA~2\CA\SERVIC~1\data\merged/DEU/sa_messages.dat
    04/03 06:32:56.505 INFO ? ? stdout >
    04/03 06:32:56.505 INFO ? ? stdout > lang = DEU, default_lang = ENU
    04/03 06:32:56.505 INFO ? ? stdout >
    04/03 06:32:56.505 INFO ? ? stdout >
    04/03 06:32:56.505 INFO ? ? stdout > merged_file = C:\PROGRA~2\CA\SERVIC~1\data\merged/FRA/sa_messages.dat
    04/03 06:32:56.505 INFO ? ? stdout >
    04/03 06:32:56.505 INFO ? ? stdout > lang = FRA, default_lang = ENU
    04/03 06:32:56.505 INFO ? ? stdout >
    04/03 06:32:56.505 INFO ? ? stdout >
    04/03 06:32:56.505 INFO ? ? stdout > merged_file = C:\PROGRA~2\CA\SERVIC~1\data\merged/ESN/sa_messages.dat
    04/03 06:32:56.505 INFO ? ? stdout >
    04/03 06:32:56.505 INFO ? ? stdout > lang = ESN, default_lang = ENU
    04/03 06:32:56.505 INFO ? ? stdout >
    04/03 06:32:56.505 INFO ? ? stdout >
    04/03 06:32:56.505 INFO ? ? stdout > merged_file = C:\PROGRA~2\CA\SERVIC~1\data\merged/ITA/sa_messages.dat
    04/03 06:32:56.505 INFO ? ? stdout >
    04/03 06:32:56.505 INFO ? ? stdout > lang = ITA, default_lang = ENU
    04/03 06:32:56.505 INFO ? ? stdout >
    04/03 06:32:56.505 INFO ? ? stdout >
    04/03 06:32:56.505 INFO ? ? stdout > merged_file = C:\PROGRA~2\CA\SERVIC~1\data\merged/PTB/sa_messages.dat
    04/03 06:32:56.505 INFO ? ? stdout >
    04/03 06:32:56.505 INFO ? ? stdout > lang = PTB, default_lang = ENU
    04/03 06:32:56.505 INFO ? ? stdout >
    04/03 06:32:56.505 INFO ? ? stdout >
    04/03 06:32:56.505 INFO ? ? stdout > merged_file = C:\PROGRA~2\CA\SERVIC~1\data\merged/CHS/sa_messages.dat
    04/03 06:32:56.505 INFO ? ? stdout >
    04/03 06:32:56.505 INFO ? ? stdout > lang = CHS, default_lang = ENU
    04/03 06:32:56.505 INFO ? ? stdout >
    04/03 06:32:56.505 INFO ? ? stdout >
    04/03 06:32:56.505 INFO ? ? stdout > merged_file = C:\PROGRA~2\CA\SERVIC~1\data\merged/FRC/sa_messages.dat
    04/03 06:32:56.505 INFO ? ? stdout >
    04/03 06:32:56.505 INFO ? ? stdout > lang = FRC, default_lang = ENU
    04/03 06:32:56.505 INFO ? ? stdout >
    04/03 06:32:56.505 INFO ? ? stdout >
    04/03 06:32:56.505 INFO ? ? stdout > merged_file = C:\PROGRA~2\CA\SERVIC~1\data\merged/ENU/sa_messages.dat
    04/03 06:32:56.505 INFO ? ? stdout >
    04/03 06:32:56.505 INFO ? ? stdout > lang = ENU, default_lang = ENU
    04/03 06:32:56.505 INFO ? ? stdout >
    04/03 06:32:56.505 INFO ? ? stdout >
    04/03 06:32:56.505 INFO ApplyConfigurationTask.java 1945 -i exit code = 0
    04/03 06:32:56.505 INFO ApplyConfigurationTask.java 1922 In createL10Ndata Getting NX_KEY (0x4E580000)
    04/03 06:32:56.505 INFO ApplyConfigurationTask.java 1923 Setting NX_KEY is set to (0x4E580000)
    04/03 06:32:56.505 INFO ApplyConfigurationTask.java 1925 Getting NX_KEY (0x4E580000)
    04/03 06:32:56.505 INFO ApplyConfigurationTask.java 1932 running command: "C:\PROGRA~2\CA\SERVIC~1\bin\pdm_perl" CreateL10N_data.pl -i sa_locale.dat -m C:\PROGRA~2\CA\SERVIC~1\data\merged -o C:\PROGRA~2\CA\SERVIC~1\data\sa_locale_default.dat -d ENU -l ENU
    04/03 06:32:56.676 INFO ? ? stderr > Name "main::LIST_LANGS" used only once: possible typo at CreateL10N_data.pl line 44.
    04/03 06:32:56.676 INFO ? ? stdout >
    04/03 06:32:56.676 INFO ? ? stdout > INPUT_FILE = sa_locale.dat
    04/03 06:32:56.676 INFO ? ? stdout > MERGED_DIR = C:\PROGRA~2\CA\SERVIC~1\data\merged
    04/03 06:32:56.676 INFO ? ? stdout > OUTPUT_FILE = C:\PROGRA~2\CA\SERVIC~1\data\sa_locale_default.dat
    04/03 06:32:56.676 INFO ? ? stdout > DEFAULT_LANG = ENU
    04/03 06:32:56.676 INFO ? ? stdout > LIST_LANGS = ENU
    04/03 06:32:56.676 INFO ? ? stdout >
    04/03 06:32:56.676 INFO ? ? stdout >
    04/03 06:32:56.676 INFO ? ? stdout > merged_file = C:\PROGRA~2\CA\SERVIC~1\data\merged/ENU/sa_locale.dat
    04/03 06:32:56.676 INFO ? ? stdout >
    04/03 06:32:56.676 INFO ApplyConfigurationTask.java 1945 -i exit code = 0
    04/03 06:32:56.676 INFO ApplyConfigurationTask.java 892 selected config (DEFAULT)
    04/03 06:32:56.692 INFO ApplyConfigurationTask.java 896 Restoring the pdm_startup file
    04/03 06:32:56.692 INFO ApplypdmEditConfiguration.java 372 Restoring TPL Files...
    04/03 06:32:56.692 INFO ApplypdmEditConfiguration.java 375 Replacing pdm_startup.tpl with the one in samples/pdmconf
    04/03 06:32:56.692 INFO ApplypdmEditConfiguration.java 389 Replacing web.xml.tpl with the one in samples/pdmconf
    04/03 06:32:56.692 INFO ApplypdmEditConfiguration.java 396 Replacing web.cfg.tpl with the one in samples/pdmconf
    04/03 06:32:56.692 INFO ApplypdmEditConfiguration.java 2357 Entering the method deleteExistingCfgFiles
    04/03 06:32:56.692 INFO ApplypdmEditConfiguration.java 2375 Leaving the method deleteExistingCfgFiles
    04/03 06:32:56.692 INFO UspServerInfo.java 179 ## No default data. Can't execute select query.
    04/03 06:32:59.473 INFO ApplyConfigurationTask.java 1154 ## Setting NX_SERVER_TYPE to (1) and BACKGROUND_SERVERS (SDM14BG)
    04/03 06:33:00.427 INFO ApplyConfigurationTask.java 1172 ## Remove NX_RF from NX.env ...
    04/03 06:33:11.520 INFO IntegrateWorkflowTask.java 676 Either 'C:\PROGRA~2\CA\SERVIC~1\bopcfg\www\CATALINA_BASE\webapps\pm.xml' and/or 'C:\PROGRA~2\CA\SERVIC~1\bopcfg\www\CATALINA_BASE\webapps\wl.xml' do not exist, do not attempt file update.
    04/03 06:33:11.520 INFO ConfigThread.java 589 Configuration progress : 2 out of 25 tasks completed.
    04/03 06:33:11.520 INFO ConfigThread.java 549 Executing task# 3, task name : Configure Tomcat integration
    04/03 06:33:11.520 INFO Task.java 214 Running: Configure Tomcat integration
    04/03 06:33:11.974 INFO ConfigThread.java 589 Configuration progress : 3 out of 25 tasks completed.
    04/03 06:33:11.974 INFO ConfigThread.java 549 Executing task# 4, task name : Install axis
    04/03 06:33:11.974 INFO Task.java 214 Running: Install axis
    04/03 06:33:11.974 INFO InstallAxisTask.java 80 Axis appears to already be installed at:C:\PROGRA~2\CA\SERVIC~1\bopcfg\www\CATALINA_BASE\webapps\axis
    04/03 06:33:11.974 INFO ConfigThread.java 589 Configuration progress : 4 out of 25 tasks completed.
    04/03 06:33:11.974 INFO ConfigThread.java 549 Executing task# 5, task name : Configure Visualizer
    04/03 06:33:11.974 INFO Task.java 214 Running: Configure Visualizer
    04/03 06:33:11.974 INFO ConfigThread.java 589 Configuration progress : 5 out of 25 tasks completed.
    04/03 06:33:11.974 INFO ConfigThread.java 549 Executing task# 6, task name : Configure Support Automation
    04/03 06:33:11.974 INFO Task.java 214 Running: Configure Support Automation
    04/03 06:33:12.442 INFO ConfigThread.java 589 Configuration progress : 6 out of 25 tasks completed.
    04/03 06:33:12.442 INFO ConfigThread.java 549 Executing task# 7, task name : Configure REST Tomcat
    04/03 06:33:12.442 INFO Task.java 214 Running: Configure REST Tomcat
    04/03 06:33:12.880 INFO ConfigThread.java 589 Configuration progress : 7 out of 25 tasks completed.
    04/03 06:33:12.880 INFO ConfigThread.java 549 Executing task# 8, task name : Configure Federated Search Tomcat
    04/03 06:33:12.880 INFO Task.java 214 Running: Configure Federated Search Tomcat
    04/03 06:33:13.770 INFO ConfigThread.java 589 Configuration progress : 8 out of 25 tasks completed.
    04/03 06:33:13.770 INFO ConfigThread.java 549 Executing task# 9, task name : Build schema
    04/03 06:33:13.770 INFO Task.java 214 Running: Build schema
    04/03 06:33:21.255 INFO ConfigThread.java 589 Configuration progress : 9 out of 25 tasks completed.
    04/03 06:33:21.255 INFO ConfigThread.java 549 Executing task# 10, task name : Build data dictionary
    04/03 06:33:21.255 INFO Task.java 214 Running: Build data dictionary
    04/03 06:33:25.239 INFO ConfigThread.java 589 Configuration progress : 10 out of 25 tasks completed.
    04/03 06:33:25.239 INFO ConfigThread.java 549 Executing task# 11, task name : Applying patches
    04/03 06:33:25.239 INFO Task.java 214 Running: Applying patches
    04/03 06:33:25.239 INFO PatchDatabaseTask.java 353 Executing altArgs >sql_check_db -c -s SDM14BG -o mdbadmin -d mdb -U mdbadmin -p <DB password> -n SDM14<
    04/03 06:33:26.020 INFO ? ? Process C:\PROGRA~2\CA\SERVIC~1\bin\sql_check_db.exe completed with exit code 99
    04/03 06:33:26.020 ERROR PatchDatabaseTask.java 470 Can't contact the database or (the database is empty and you are not loading data) or (this database is configured for another server).
    04/03 06:33:26.020 ERROR PatchDatabaseTask.java 473 Correct the database or vnode if it is not working.
    04/03 06:33:26.020 ERROR PatchDatabaseTask.java 474 Reconfigure and acknowledge that you want to reconfigure the database to this Primary Server or reload data if the server name in the dlgtsrv table names another server.



  • 11.  Re: sdm14.1 advance avalaibility

    Posted Apr 06, 2017 03:28 AM

    Sorry for delay Just back. Have you fix your problem?

    let us know

    /J



  • 12.  Re: sdm14.1 advance avalaibility

    Posted Apr 06, 2017 03:36 AM

    Hello MAyer 

     

    The issue is now at the last stage of reconfigure. Stucked here 

     

     



  • 13.  Re: sdm14.1 advance avalaibility

    Broadcom Employee
    Posted Apr 06, 2017 04:12 AM

    Hi Aamir,

     

    Do you see any error message in configure.log when you encounter the error?  

     

    Thank you,

    Kaori



  • 14.  Re: sdm14.1 advance avalaibility

    Posted Apr 06, 2017 04:26 AM

    Hi Kishi

     

    i checked the configure logs, But seems ok other than the following..pls see.. 

     

    for ur information , i deleted the record  from usp_servers table as it contain the previous sdm record in it.

     

     

    DB_OK
    04/05 09:49:58.760 INFO ? ? WARNING - usp_servers table exists, but has no rows
    04/05 09:49:59.010 INFO ? ? Process sql_check_db completed with exit code 11
    04/05 09:49:59.916 INFO SQLDatabasePage.java 1222 #### No information for background server is found in usp_servers table. ####
    04/05 09:50:00.260 INFO SQLDatabasePage.java 1197 #### No information for Primary server is found in usp_servers table. ####
    04/05 09:50:00.260 INFO SQLDatabasePage.java 519 ## Background Servername () ; Primary Servername () ; Local Servername (SDM14BG2)
    04/05 09:50:00.276 INFO SQLDatabasePage.java 762 Running: sqlcmd -S SDM14 -U sa -P <password> -l 5 -i tmp_sql.sql
    04/05 09:50:00.353 INFO SQLDatabasePage.java 774 Changed database context to 'mdb'.

    04/05 09:50:00.385 INFO SQLDatabasePage.java 774

    04/05 09:50:00.385 INFO SQLDatabasePage.java 774 ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

    04/05 09:50:00.385 INFO SQLDatabasePage.java 774 Microsoft SQL Server 2012 - 11.0.2100.60 (X64)

    04/05 09:50:00.385 INFO SQLDatabasePage.java 774 Feb 10 2012 19:39:15

    04/05 09:50:00.385 INFO SQLDatabasePage.java 774 Copyright (c) Microsoft Corporation

    04/05 09:50:00.385 INFO SQLDatabasePage.java 774 Enterprise Edition (64-bit) on Windows NT 6.2 <X64> (Build 9200: ) (Hypervisor)

    04/05 09:50:00.385 INFO SQLDatabasePage.java 774

    04/05 09:50:00.385 INFO SQLDatabasePage.java 774 Current user is a member of the sysadmin role

    04/05 09:50:00.385 INFO SQLDatabasePage.java 774

    04/05 09:50:00.385 INFO SQLDatabasePage.java 774 -----------

    04/05 09:50:00.385 INFO SQLDatabasePage.java 774 0

    04/05 09:50:00.963 INFO SQLDatabasePage.java 1171 #### No information for Active servers is found in usp_servers table. ####
    04/05 09:50:00.963 INFO SQLDatabasePage.java 1092 ## active Non-Background List : ()
    04/05 09:50:00.963 INFO SQLDatabasePage.java 1095 The Value of swing_box_migrate is : null
    04/05 09:50:00.963 INFO SQLDatabasePage.java 1127 ## Load default data :
    04/05 09:50:10.119 INFO GeneralPage.java 230 ## BackgroundServerName: (SDM14BG2)
    04/05 09:51:01.666 INFO GeneralPage.java 622 ## Current server configuration type is : background
    04/05 09:51:13.182 INFO WebPage.java 225 ## Deploying Webservices : false
    04/05 09:51:16.433 INFO OptionsPage.java 209 Primary server: false
    04/05 09:51:16.433 INFO OptionsPage.java 210 Advanced server: true
    04/05 09:51:16.433 INFO OptionsPage.java 211 Secondary server: false
    04/05 09:51:18.619 INFO ConfigThread.java 223 ############ Property values ###############
    04/05 09:51:18.619 INFO ConfigThread.java 224 ## general.configuration_type :
    04/05 09:51:18.619 INFO ConfigThread.java 225 ## config.server_config_type :advanced



  • 15.  Re: sdm14.1 advance avalaibility

    Broadcom Employee
    Posted Apr 06, 2017 08:07 AM

    Hi Aamir,

     

    It does not look complete configure.log... You should open a Support Case so that a support engineer can look into logs and others. It is very difficult to troubleshoot this type of question through the community. Also we can assist you via Webex which may help to solve the probelm. So please reach CA support for this problem.

     

    Thank you,

    Kaori