CA Service Management

Expand all | Collapse all

14.1 CUM3 Patch Error

  • 1.  14.1 CUM3 Patch Error

    Posted Nov 02, 2016 08:44 AM

    Hi,

     

    Am applying CUM3 patch on 14.1 CUM2 and when i try to perfrom " Post installation steps" am getting below error

     

    am executing this command " pdm_load -f hampi_insert.dat"  and i got below error.

     

    11/02 12:20:12.79 Server       dbload                956 ERROR        dbintf.c               761 SELECT #config_key , #config_value , #delete_flag , #description , #id FROM l1admin_general_config
    11/02 12:20:12.79 Server       sql_agent            1384 ERROR        sqlclass.c            1010 SQL Execute  failed: [Microsoft OLE DB Provider for SQL Server] [ SQL Code=208 SQL State=42S02] Invalid object name 'l1admin_general_config'.
    11/02 12:20:12.79 Server       sql_agent            1384 ERROR        sqlclass.c            1011 Clause (INSERT INTO l1admin_general_config ( config_key, config_value, delete_flag, description, id ) VALUES ( ? , ? , ? , ? , ? )) Input (<config_key:string>esearch.nr.searchable.columns|<config_value:string>name, class.name, family.name, mac_address, dns_name, serial_number, location.name, system_name|<delete_flag:int>0|<description:string>Define the searchable fields for the Assets facet. You can define from the following fields: resource_name; class.name; family.name; mac_address; dns_name; serial_number; location.name; tenant.name|<id:int>1104)
    11/02 12:20:12.79 SINMQY32       sql_agent            1384 ERROR        sqlsrvr.c              651 Execution failed. MISC_DB_ERROR

     

    Am having 14.1 CUM2 with AA  and am doing this in test server.

     

    pdm_configure ran successfully and while performing this step, i got errors.



  • 2.  Re: 14.1 CUM3 Patch Error

    Posted Nov 02, 2016 10:41 AM

    Hi Sheik,

    Is there another message after those that say that the row conflicts with existing data?  Also can you see if the table "l1admin_general_config" exists?

     

    Jon I.



  • 3.  Re: 14.1 CUM3 Patch Error

    Posted Nov 02, 2016 10:46 AM

    Hi jon,

     

    thanks. is there any option that i can find object name and its equivalent physical table name. it will be easy for me to check.



  • 4.  Re: 14.1 CUM3 Patch Error

    Broadcom Employee
    Posted Nov 02, 2016 10:56 AM

    Sheik............

     

    'l1admin_general_config' is an actual table within the MDB database.

     

    Do you see this table present?

     

    If so, also check to see if 'l1admin_general_config' is defined within the NX_ROOT\SITE\DDICT.SCH file



  • 5.  Re: 14.1 CUM3 Patch Error

    Posted Nov 02, 2016 11:00 AM

    Hi Paul,

     

    Thanks.. there is no such table available in MDB. i believe this is new table , as i found other tables like (usp_menu_tree) with values updated present in hampi_insert. dat file.



  • 6.  Re: 14.1 CUM3 Patch Error

    Posted Nov 02, 2016 11:10 AM

    plus i have skipped X-flow installation, have not installed it.



  • 7.  Re: 14.1 CUM3 Patch Error

    Posted Nov 02, 2016 11:10 AM

    plus i have skipped X-flow installation, have not installed it



  • 8.  Re: 14.1 CUM3 Patch Error

    Broadcom Employee
    Posted Nov 02, 2016 12:33 PM

    I think if you don't have 1admin_general_config table, that means you cum3 mdb update is not done or not done properly. you may need to review the common installer log to see if some errors there.



  • 9.  Re: 14.1 CUM3 Patch Error

    Posted Nov 02, 2016 01:16 PM

    Hi,

     

    I saw below error lines in install.log.

     

    usage: Sqlcmd            [-U login id]          [-P password]
    2016/10/25 12.54.33.264 DEBUG [AWT-EventQueue-0] [CmdLineUtility]   [-S server]            [-H hostname]          [-E trusted connection]
    2016/10/25 12.54.33.264 DEBUG [AWT-EventQueue-0] [CmdLineUtility]   [-N Encrypt Connection][-C Trust Server Certificate]
    2016/10/25 12.54.33.264 DEBUG [AWT-EventQueue-0] [CmdLineUtility]   [-d use database name] [-l login timeout]     [-t query timeout]
    2016/10/25 12.54.33.264 DEBUG [AWT-EventQueue-0] [CmdLineUtility]   [-h headers]           [-s colseparator]      [-w screen width]
    2016/10/25 12.54.33.264 DEBUG [AWT-EventQueue-0] [CmdLineUtility]   [-a packetsize]        [-e echo input]        [-I Enable Quoted Identifiers]
    2016/10/25 12.54.33.264 DEBUG [AWT-EventQueue-0] [CmdLineUtility]   [-c cmdend]            [-L[c] list servers[clean output]]
    2016/10/25 12.54.33.264 DEBUG [AWT-EventQueue-0] [CmdLineUtility]   [-q "cmdline query"]   [-Q "cmdline query" and exit]
    2016/10/25 12.54.33.264 DEBUG [AWT-EventQueue-0] [CmdLineUtility]   [-m errorlevel]        [-V severitylevel]     [-W remove trailing spaces]
    2016/10/25 12.54.33.264 DEBUG [AWT-EventQueue-0] [CmdLineUtility]   [-u unicode output]    [-r[0|1] msgs to stderr]
    2016/10/25 12.54.33.264 DEBUG [AWT-EventQueue-0] [CmdLineUtility]   [-i inputfile]         [-o outputfile]        [-z new password]
    2016/10/25 12.54.33.264 DEBUG [AWT-EventQueue-0] [CmdLineUtility]   [-f <codepage> | i:<codepage>[,o:<codepage>]] [-Z new password and exit]
    2016/10/25 12.54.33.264 DEBUG [AWT-EventQueue-0] [CmdLineUtility]   [-k[1|2] remove[replace] control characters]
    2016/10/25 12.54.33.264 DEBUG [AWT-EventQueue-0] [CmdLineUtility]   [-y variable length type display width]
    2016/10/25 12.54.33.264 DEBUG [AWT-EventQueue-0] [CmdLineUtility]   [-Y fixed length type display width]
    2016/10/25 12.54.33.264 DEBUG [AWT-EventQueue-0] [CmdLineUtility]   [-p[1] print statistics[colon format]]
    2016/10/25 12.54.33.264 DEBUG [AWT-EventQueue-0] [CmdLineUtility]   [-R use client regional setting]
    2016/10/25 12.54.33.264 DEBUG [AWT-EventQueue-0] [CmdLineUtility]   [-b On error batch abort]
    2016/10/25 12.54.33.264 DEBUG [AWT-EventQueue-0] [CmdLineUtility]   [-v var = "value"...]  [-A dedicated admin connection]
    2016/10/25 12.54.33.264 DEBUG [AWT-EventQueue-0] [CmdLineUtility]   [-X[1] disable commands, startup script, enviroment variables [and exit]]
    2016/10/25 12.54.33.264 DEBUG [AWT-EventQueue-0] [CmdLineUtility]   [-x disable variable substitution]
    2016/10/25 12.54.33.264 DEBUG [AWT-EventQueue-0] [CmdLineUtility]   [-? show syntax summary]
    2016/10/25 12.54.33.264 INFO  [AWT-EventQueue-0] [CmdLineUtility] Command executed Sucessfully
    2016/10/25 12.54.33.264 INFO  [AWT-EventQueue-0] [DatabaseHelper] verifyDbClient is successful...
    2016/10/25 12.54.33.436 DEBUG [AWT-EventQueue-0] [ConfigureSQLServer] Successfully loaded SQL Server JDBC driver.
    2016/10/25 12.54.33.732 ERROR [AWT-EventQueue-0] [ConfigureSQLServer] Could not connect to the database.
    com.microsoft.sqlserver.jdbc.SQLServerException: Login failed for user 'sa'. ClientConnectionId:d37a85fc-4bcd-4509-83c4-b2c2c9892b40
        at com.microsoft.sqlserver.jdbc.SQLServerException.makeFromDatabaseError(SQLServerException.java:216)
        at com.microsoft.sqlserver.jdbc.TDSTokenHandler.onEOF(tdsparser.java:254)
        at com.microsoft.sqlserver.jdbc.TDSParser.parse(tdsparser.java:84)
        at com.microsoft.sqlserver.jdbc.SQLServerConnection.sendLogon(SQLServerConnection.java:2908)
        at com.microsoft.sqlserver.jdbc.SQLServerConnection.logon(SQLServerConnection.java:2234)
        at com.microsoft.sqlserver.jdbc.SQLServerConnection.access$000(SQLServerConnection.java:41)
        at com.microsoft.sqlserver.jdbc.SQLServerConnection$LogonCommand.doExecute(SQLServerConnection.java:2220)
        at com.microsoft.sqlserver.jdbc.TDSCommand.execute(IOBuffer.java:5696)
        at com.microsoft.sqlserver.jdbc.SQLServerConnection.executeCommand(SQLServerConnection.java:1715)
        at com.microsoft.sqlserver.jdbc.SQLServerConnection.connectHelper(SQLServerConnection.java:1326)
        at com.microsoft.sqlserver.jdbc.SQLServerConnection.login(SQLServerConnection.java:991)
        at com.microsoft.sqlserver.jdbc.SQLServerConnection.connect(SQLServerConnection.java:827)
        at com.microsoft.sqlserver.jdbc.SQLServerDriver.connect(SQLServerDriver.java:1012)
        at java.sql.DriverManager.getConnection(DriverManager.java:664)
        at java.sql.DriverManager.getConnection(DriverManager.java:247)
        at com.ca.smsi.installcore.Database.ConfigureSQLServer.connectMssql(ConfigureSQLServer.java:179)
        at com.ca.smsi.installcore.Database.ConfigureSQLServer.verifyMssqlConnect(ConfigureSQLServer.java:53)
        at com.ca.smsi.installcore.Database.DatabaseHelper.verifyDBAUser(DatabaseHelper.java:78)
        at com.ca.smsi.installcore.model.MDBValidator.validate(MDBValidator.java:56)
        at com.ca.smsi.installui.wizard.DatabasePage.validatePage(DatabasePage.java:1171)
        at com.ca.smsi.wizard.Wizard.next(Wizard.java:777)
        at com.ca.smsi.wizard.Wizard.actionPerformed(Wizard.java:460)
        at javax.swing.AbstractButton.fireActionPerformed(AbstractButton.java:2022)
        at javax.swing.AbstractButton$Handler.actionPerformed(AbstractButton.java:2348)
        at javax.swing.DefaultButtonModel.fireActionPerformed(DefaultButtonModel.java:402)
        at javax.swing.DefaultButtonModel.setPressed(DefaultButtonModel.java:259)
        at javax.swing.plaf.basic.BasicButtonListener.mouseReleased(BasicButtonListener.java:252)
        at java.awt.AWTEventMulticaster.mouseReleased(AWTEventMulticaster.java:289)
        at java.awt.Component.processMouseEvent(Component.java:6535)
        at javax.swing.JComponent.processMouseEvent(JComponent.java:3324)
        at java.awt.Component.processEvent(Component.java:6300)
        at java.awt.Container.processEvent(Container.java:2236)
        at java.awt.Component.dispatchEventImpl(Component.java:4891)
        at java.awt.Container.dispatchEventImpl(Container.java:2294)
        at java.awt.Component.dispatchEvent(Component.java:4713)
        at java.awt.LightweightDispatcher.retargetMouseEvent(Container.java:4888)
        at java.awt.LightweightDispatcher.processMouseEvent(Container.java:4525)
        at java.awt.LightweightDispatcher.dispatchEvent(Container.java:4466)
        at java.awt.Container.dispatchEventImpl(Container.java:2280)
        at java.awt.Window.dispatchEventImpl(Window.java:2750)
        at java.awt.Component.dispatchEvent(Component.java:4713)
        at java.awt.EventQueue.dispatchEventImpl(EventQueue.java:758)
        at java.awt.EventQueue.access$500(EventQueue.java:97)
        at java.awt.EventQueue$3.run(EventQueue.java:709)
        at java.awt.EventQueue$3.run(EventQueue.java:703)
        at java.security.AccessController.doPrivileged(Native Method)
        at java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:76)
        at java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:86)
        at java.awt.EventQueue$4.run(EventQueue.java:731)
        at java.awt.EventQueue$4.run(EventQueue.java:729)
        at java.security.AccessController.doPrivileged(Native Method)
        at java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:76)
        at java.awt.EventQueue.dispatchEvent(EventQueue.java:728)
        at java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:201)
        at java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:116)
        at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:105)
        at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:101)
        at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:93)
        at java.awt.EventDispatchThread.run(EventDispatchThread.java:82)
    2016/10/25 12.54.33.732 ERROR [AWT-EventQueue-0] [MDBValidator] SU2038
    java.lang.Exception: SU2038
        at com.ca.smsi.installcore.Database.ConfigureSQLServer.connectMssql(ConfigureSQLServer.java:192)
        at com.ca.smsi.installcore.Database.ConfigureSQLServer.verifyMssqlConnect(ConfigureSQLServer.java:53)
        at com.ca.smsi.installcore.Database.DatabaseHelper.verifyDBAUser(DatabaseHelper.java:78)
        at com.ca.smsi.installcore.model.MDBValidator.validate(MDBValidator.java:56)
        at com.ca.smsi.installui.wizard.DatabasePage.validatePage(DatabasePage.java:1171)
        at com.ca.smsi.wizard.Wizard.next(Wizard.java:777)
        at com.ca.smsi.wizard.Wizard.actionPerformed(Wizard.java:460)
        at javax.swing.AbstractButton.fireActionPerformed(AbstractButton.java:2022)
        at javax.swing.AbstractButton$Handler.actionPerformed(AbstractButton.java:2348)
        at javax.swing.DefaultButtonModel.fireActionPerformed(DefaultButtonModel.java:402)
        at javax.swing.DefaultButtonModel.setPressed(DefaultButtonModel.java:259)
        at javax.swing.plaf.basic.BasicButtonListener.mouseReleased(BasicButtonListener.java:252)
        at java.awt.AWTEventMulticaster.mouseReleased(AWTEventMulticaster.java:289)
        at java.awt.Component.processMouseEvent(Component.java:6535)
        at javax.swing.JComponent.processMouseEvent(JComponent.java:3324)
        at java.awt.Component.processEvent(Component.java:6300)
        at java.awt.Container.processEvent(Container.java:2236)
        at java.awt.Component.dispatchEventImpl(Component.java:4891)
        at java.awt.Container.dispatchEventImpl(Container.java:2294)
        at java.awt.Component.dispatchEvent(Component.java:4713)
        at java.awt.LightweightDispatcher.retargetMouseEvent(Container.java:4888)
        at java.awt.LightweightDispatcher.processMouseEvent(Container.java:4525)
        at java.awt.LightweightDispatcher.dispatchEvent(Container.java:4466)
        at java.awt.Container.dispatchEventImpl(Container.java:2280)
        at java.awt.Window.dispatchEventImpl(Window.java:2750)
        at java.awt.Component.dispatchEvent(Component.java:4713)
        at java.awt.EventQueue.dispatchEventImpl(EventQueue.java:758)
        at java.awt.EventQueue.access$500(EventQueue.java:97)
        at java.awt.EventQueue$3.run(EventQueue.java:709)
        at java.awt.EventQueue$3.run(EventQueue.java:703)
        at java.security.AccessController.doPrivileged(Native Method)
        at java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:76)
        at java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:86)
        at java.awt.EventQueue$4.run(EventQueue.java:731)
        at java.awt.EventQueue$4.run(EventQueue.java:729)
        at java.security.AccessController.doPrivileged(Native Method)
        at java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:76)
        at java.awt.EventQueue.dispatchEvent(EventQueue.java:728)
        at java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:201)
        at java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:116)
        at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:105)
        at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:101)
        at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:93)
        at java.awt.EventDispatchThread.run(EventDispatchThread.java:82)

     

    Do we have any other way to fix this. server is up and running, am able to login in background server.



  • 10.  Re: 14.1 CUM3 Patch Error

    Broadcom Employee
    Posted Nov 02, 2016 01:50 PM

    Sheik.......

     

    The 'sa' error message could strenghten Chi_Chen's statement regarding the MDB update not completing successfully.

    Using SQL Management Studio, can you connect to the MDB to confirm the credentials for the 'sa' SQL account?



  • 11.  Re: 14.1 CUM3 Patch Error

    Posted Nov 02, 2016 02:11 PM

    Hi Paul,

     

    Thanks.am unable to connect through sa account. Is there any option to fix

    mdb update alone? . Rest seems to be fine, as server is up and am able to

    login in background server. Pls help. I have alternate credentials other

    than sa. Moreover i have not given sa account while running setup file. Not

    sure how i got this error.

    On 02-Nov-2016 11:20 pm, "Paul_Coccimiglio" <



  • 12.  Re: 14.1 CUM3 Patch Error
    Best Answer

    Broadcom Employee
    Posted Nov 02, 2016 02:27 PM

    Sheik.........

    If the proper credentials are provided on the database screen using the CUM#3 Common Patch Installer, then the MDB update should proceed successfully.

     

    You can manually apply the MDB update:

     

    1.  Set the current directory to NX_ROOT\patches\cum3

    2.  Copy the file "MSSQL_MDB.CAZ" file to a temporary folder.
    3.  Extract the caz file, "MSSQL_MDB.CAZ", using Cazipxp.exe utility. For example, run:


    CAZIPXP -u MSSQL_MDB.CAZ


    4.  Run setupmdb.bat to apply the patch. For example, run:

     

    setupmdb -DBVENDOR=mssql -JRE_DIR=C:\PROGRA~2\CA\SC\JRE\1.7.0_10 -DBUSER=sa -DBPASSWORD=sa -DBDRIVER=Service_Desk -WORKSPACE=Service_Desk

     

    Notes: setupmdb.bat may need to be run by adding the "–DBPORT" option to provide the correct port number for some SQL server installations if the default port is changed or a named instance of SQL Server is used. Run 'setupmdb.bat -help' to list all options.



  • 13.  Re: 14.1 CUM3 Patch Error

    Posted Nov 02, 2016 02:37 PM

    Hi Paul,

     

    Yes, i followed the same as this is suggested by support team. Pls confirm

     

    1) whether this patch needs to be run in mdb server ( my database is in

    remote machine) or in sdm server.( background or standby)

     

    2) when i try this command in mdb server, i got below error.

     

    11-01,14:46:50 sqlcmd -S "localhost" -d master -U servicedesk -P *** -e -b

    -Q "exit(SELECT count(*)+100000 FROM master..sysdatabases WHERE name =

    'MDB')"

     

    HResult 0x2, Level 16, State 1

     

    Named Pipes Provider: Could not open a connection to SQL Server .

     

    Sqlcmd: Error: Microsoft SQL Server Native Client 10.0 : A network-related

    or instance-specific error has occurred while establishing a connection to

    SQL Server. Server is not found or not accessible. Check if instance name

    is correct and if SQL Server is configured to allow remote connections. For

    more information see SQL Server Books Online..

     

    Sqlcmd: Error: Microsoft SQL Server Native Client 10.0 : Login timeout

    expired.

     

    11-01,14:46:59 SQL command error, ERRORLEVEL=1, see logfile for

    details

     

    11-01,14:46:59 Setupmdb_pre exit /B return code=100

     

    11-01,14:46:59 Pre-process failed (errorlevel=100)

     

    11-01,14:46:59 Setupmdb exit /B return code=110

     

    Sqlcmd utility is working with hostname but throws error when tried with

    localhost.

     

    Pls help.

    CA Communities <https://communities.ca.com/?et=watches.email.thread>

    Re: 14.1 CUM3 Patch Error

     

    reply from PAUL COCCIMIGLIO

    <https://communities.ca.com/people/Paul_Coccimiglio?et=watches.email.thread>

    in CA Service Management - View the full discussion

    <https://communities.ca.com/message/241935793?commentID=241935793&et=watches.email.thread#comment-241935793>



  • 14.  Re: 14.1 CUM3 Patch Error

    Broadcom Employee
    Posted Nov 02, 2016 02:54 PM

    Is the MDB installed in the default SQL instance or a separate SQL instance?



  • 15.  Re: 14.1 CUM3 Patch Error

    Posted Nov 02, 2016 02:59 PM

    Hi,

     

    My sql server is in cluster.. 

     

    service name: MSSQL$I03

     

    MDB is running in this cluster.



  • 16.  Re: 14.1 CUM3 Patch Error

    Posted Nov 02, 2016 03:22 PM

     

    Hi paul,

     

    sorry for confusion. As per above instruction, i placed patches in NX_ROOT/Servciedesk/patches/cum3 in background sever.

     

    When i run command, i got above error. should i need to run this command in MDB server or in background server.

     

    should i need extract this file using CAZIP utility and then run this command... please help.



  • 17.  Re: 14.1 CUM3 Patch Error

    Broadcom Employee
    Posted Nov 02, 2016 01:11 PM

    Sheik........

     

    You indicated that this is a Test environment running in AA architecture.

     

    Do you have a snapshot/backup of the servers prior to installing CUM#3 that you can revert back to?

     

    If so, perhaps following the steps in TEC1777224 might help.