CA Service Management

Expand all | Collapse all

error running command pdm_publish

Jump to Best Answer
  • 1.  error running command pdm_publish

    Posted 09-18-2016 02:46 AM
     Hi  I am working with CA SDM 12.7, and we need to create new custom fields "z", we have done the following steps:  start "WSP" go Schema Designer create table "z" add columanas of "sym" type and length string 2500 add column "del" SREL to boolean active save changes click save and publish CA SDM services down run CMD console as administrator run "pdm_status" command to validate stopped services execute command "pdm_publish"  but in the execution, it shows me the following error. +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
    C:\Windows\system32>pdm_status
    The Daemons are not running.

    C:\Windows\system32>pdm_publish
    Pdm_publish - Implement DBMS schema changes from Web Screen Painter
    Verifying files output from Web Screen Painter...
    Verifying CA Service Desk Manager server is not running...

    Merging schema files...
    Schema merge successful

    Building data dictionary...
    Data dictionary build successful

    Creating new tables...
    Creating table zPosSol...

    ERROR 15 [Microsoft OLE DB Provider for SQL Server] [ SQL Code=1919 SQL State=4
    2000] Column 'sym' in table 'dbo.zPosSol' is of a type that is invalid for use a
    s a key column in an index.

    ERROR 15 [Microsoft OLE DB Provider for SQL Server] [ SQL Code=1919 SQL State=4
    2000] Column 'sym' in table 'dbo.zPosSol' is of a type that is invalid for use a
    s a key column in an index.
    Can't spawn "cmd.exe": Bad file descriptor at .\pdm_publish.pl line 255, <ALTERT
    BL> line 9.
    AHD04748:sqlbuild failed for table zPosSol
    Creating table zTypeAffect...

    ERROR 15 [Microsoft OLE DB Provider for SQL Server] [ SQL Code=1919 SQL State=4
    2000] Column 'sym' in table 'dbo.zTypeAffect' is of a type that is invalid for u
    se as a key column in an index.

    ERROR 15 [Microsoft OLE DB Provider for SQL Server] [ SQL Code=1919 SQL State=4
    2000] Column 'sym' in table 'dbo.zTypeAffect' is of a type that is invalid for u
    se as a key column in an index.
    Can't spawn "cmd.exe": Bad file descriptor at .\pdm_publish.pl line 255, <ALTERT
    BL> line 16.
    AHD04748:sqlbuild failed for table zTypeAffect
    Creating table zTypeClient...

    ERROR 15 [Microsoft OLE DB Provider for SQL Server] [ SQL Code=1919 SQL State=4
    2000] Column 'sym' in table 'dbo.zTypeClient' is of a type that is invalid for u
    se as a key column in an index.

    ERROR 15 [Microsoft OLE DB Provider for SQL Server] [ SQL Code=1919 SQL State=4
    2000] Column 'sym' in table 'dbo.zTypeClient' is of a type that is invalid for u
    se as a key column in an index.
    Can't spawn "cmd.exe": Bad file descriptor at .\pdm_publish.pl line 255, <ALTERT
    BL> line 17.
    AHD04748:sqlbuild failed for table zTypeClient
    Creating table zTypeEn...

    ERROR 15 [Microsoft OLE DB Provider for SQL Server] [ SQL Code=1919 SQL State=4
    2000] Column 'sym' in table 'dbo.zTypeEn' is of a type that is invalid for use a
    s a key column in an index.

    ERROR 15 [Microsoft OLE DB Provider for SQL Server] [ SQL Code=1919 SQL State=4
    2000] Column 'sym' in table 'dbo.zTypeEn' is of a type that is invalid for use a
    s a key column in an index.
    Can't spawn "cmd.exe": Bad file descriptor at .\pdm_publish.pl line 255, <ALTERT
    BL> line 18.
    AHD04748:sqlbuild failed for table zTypeEn
    0 table(s) added successfully; 4 errors

    Rebuilding indexes for site-defined tables...
    Rebuilding indexes for table zApp...
    Rebuilding indexes for table zCausaRaiz...
    Rebuilding indexes for table zEncuesta...
    Rebuilding indexes for table zEncuesta1...
    Rebuilding indexes for table zEquipo...
    Rebuilding indexes for table zImputable...
    Rebuilding indexes for table zLienadeNegocio...
    Rebuilding indexes for table zNodos...
    Rebuilding indexes for table zPosSol...

    ERROR 15 [Microsoft OLE DB Provider for SQL Server] [ SQL Code=1919 SQL State=4
    2000] Column 'sym' in table 'dbo.zPosSol' is of a type that is invalid for use a
    s a key column in an index.

    ERROR 15 [Microsoft OLE DB Provider for SQL Server] [ SQL Code=1919 SQL State=4
    2000] Column 'sym' in table 'dbo.zPosSol' is of a type that is invalid for use a
    s a key column in an index.
    Can't spawn "cmd.exe": Bad file descriptor at .\pdm_publish.pl line 350, <INDEXS
    CH> line 41.
    AHD04748:sqlbuild failed for table zPosSol
    Rebuilding indexes for table zProblemRC...
    Rebuilding indexes for table zRegionU...
    Rebuilding indexes for table zResMethod...
    Rebuilding indexes for table zRptMthd...
    Rebuilding indexes for table zSubtenantNX...
    Rebuilding indexes for table zSupTur...
    Rebuilding indexes for table zTypeAffect...

    ERROR 15 [Microsoft OLE DB Provider for SQL Server] [ SQL Code=1919 SQL State=4
    2000] Column 'sym' in table 'dbo.zTypeAffect' is of a type that is invalid for u
    se as a key column in an index.

    ERROR 15 [Microsoft OLE DB Provider for SQL Server] [ SQL Code=1919 SQL State=4
    2000] Column 'sym' in table 'dbo.zTypeAffect' is of a type that is invalid for u
    se as a key column in an index.
    Can't spawn "cmd.exe": Bad file descriptor at .\pdm_publish.pl line 350, <INDEXS
    CH> line 71.
    AHD04748:sqlbuild failed for table zTypeAffect
    Rebuilding indexes for table zTypeClient...

    ERROR 15 [Microsoft OLE DB Provider for SQL Server] [ SQL Code=1919 SQL State=4
    2000] Column 'sym' in table 'dbo.zTypeClient' is of a type that is invalid for u
    se as a key column in an index.

    ERROR 15 [Microsoft OLE DB Provider for SQL Server] [ SQL Code=1919 SQL State=4
    2000] Column 'sym' in table 'dbo.zTypeClient' is of a type that is invalid for u
    se as a key column in an index.
    Can't spawn "cmd.exe": Bad file descriptor at .\pdm_publish.pl line 350, <INDEXS
    CH> line 76.
    AHD04748:sqlbuild failed for table zTypeClient
    Rebuilding indexes for table zTypeEn...

    ERROR 15 [Microsoft OLE DB Provider for SQL Server] [ SQL Code=1919 SQL State=4
    2000] Column 'sym' in table 'dbo.zTypeEn' is of a type that is invalid for use a
    s a key column in an index.

    ERROR 15 [Microsoft OLE DB Provider for SQL Server] [ SQL Code=1919 SQL State=4
    2000] Column 'sym' in table 'dbo.zTypeEn' is of a type that is invalid for use a
    s a key column in an index.
    Can't spawn "cmd.exe": Bad file descriptor at .\pdm_publish.pl line 350, <INDEXS
    CH> line 81.
    AHD04748:sqlbuild failed for table zTypeEn
    Rebuilding indexes for table zViaAtencion...
    Rebuilding indexes for table zWorkspaceRC...
    Rebuilding indexes for table zWorkspaceSolution...
    Rebuilding indexes for table zequiporep...
    Rebuilding indexes for table zfactura...
    Rebuilding indexes for table zimpacto...
    Rebuilding indexes for table zpcatCF...
    Rebuilding indexes for table zrootCF...
    Rebuilding indexes for table zrootNW...
    Rebuilding indexes for table zrootchg...
    Rebuilding indexes for table zsolutionCF...
    Rebuilding indexes for table ztiporep...
    Rebuilding indexes for table ztipotkt...
    Rebuilding indexes for table zvip...
    AHD04791:Succesfully rebuilt indexes for 28 tables; 4 errors

    Building data dictionary...
    Data dictionary build successful


    Building tblobj.cfg file...
    Build tblobj.cfg file successful

    Normal end of pdm_publish; 8 error(s) encountered

    C:\Windows\System32>


    +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
    I could help resolve the error, as this is a production environment and is very important to us.   Regards, Marco Velazquez.


  • 2.  Re: error running command pdm_publish

     
    Posted 09-18-2016 09:59 PM
      |   view attached

    Hi Marco,

     

    I think the problem lies in the length of your 'sym' field (2500 characters).  The sym field is normally used to provide a short label for a value in a reference table - one would usually specify string (20) or thereabouts.  If you specify a string length of greater than around 1000 characters, SDM enters it in SQL as a field type that is not searchable, and thus cannot be used as an index.   Make your sym field a lot shorter, and add a 'description' field for bulk text, and you will probably find it publishes OK.

     

    Hope that helps!

    Regards,

    James



  • 3.  Re: error running command pdm_publish

    Posted 09-21-2016 05:06 PM

    Hi Marcoaldama - Did camja06's response help answer your question? If so please Mark Correct. Thanks!



  • 4.  Re: error running command pdm_publish
    Best Answer

    Posted 09-21-2016 07:26 PM

    hello, I have solved my problem.

    attached below the document to use as a guide.

     

    http://www.ca.com/us/support/ca-support-online/product-content/knowledgebase-articles/tec605766.aspx 
    -------------------------------------------
    How To remove Custom Tables/Columns/Triggers without using PDM_WSPUPD
    Document ID: TEC605766
    Last Modified Date: 2/6/2014
    Show Technical Document Details
    Description:

    This document will guide you in how to remove customization such as tables, columns, or trigger without using the command PDM_WSPUPD. This is document is more for administrator to be hands on in removing items manually. Furthermore, this is also an alternative just in case there are issues with the tool PDM_WSPUPD or for troubleshooting purposes.

    Disclaimer: Please note the supported version is with PDM_WSPUPD. If wish to go this route, it will be at your own risk!

    Solution:

    First and foremost, please backup the following items before proceeding

    CA MDB

    nx_root\site directory(the whole directory)

    Use a Text Editor tool that has the features of editing and search/find the field in many instances in a particular file, multiple files, or folders. ex: Notepad ++

    Stop CA Service Desk Manager services.

    The common files that you will have to edit to remove the custom tables, columns or trigger:

    (Please note some of these individual file may have more than one reference of the custom table name or custom column name. Please do thorough search within the file for particular custom table or custom column you wish to remove. Furthermore, If it table you are planning to remove, please remember to remove the related columns, parameters, open/close brackets and etc)

    site\ddict.sch -> This file contains table names and column names.

    site\tblobj.cfg -> This file contains table names and the table object name.

    site\mods\wsp_schema.sch -> This file contains table names and column names. Schema modifications maintained by Web Screen Painter

    site\mods\wsp_schema.log -> This file contains the log entry of when the custom table or custom column was added. Please remove those entries

    site\mods\wsp_index.sch -> This file contains indexes of the custom table. Schema modifications maintained by Web Screen Painter

    site\mods\majic\wsp.mods -> This file contains table names and column names. Schema modifications maintained by Web Screen Painter

    Outside the common files above, please search for any particular spell files, mod file, scripts, or forms which may reference to the custom table, custom column or trigger you wish to remove. With an editor tool please do thorough search within site\mods\majic folder and site\mods\www folder. Depending the editor tool, it should tell you what files, what lines, and how many reference of the field you searched for.

    Once all the reference of the field(s) you wish to remove from Step 4 and Step 5; using the appropriate utility for your DBMS, alter the DBMS definition of the tables/columns you changed. You should delete from the database any table/columns you deleted from above files. Take care to ensure that the changes you make to the DBMS correspond exactly to the changes you made in the common files- Step 4.

    Run pdm_publish as described in Publish Schema Modifications above.

    Start CA Service Desk Manager services

    .---------------
    thanks for your help,

    Regards,
    Marco Velazquez.