CA Service Management

Hello,

I have added a new column to a custom table, i stopped the service and published that column successfully with pdm_publish. I started back the CA Service Desk Manager service and everything worked fine. However, the field is not added to related the database table. I have checked "CA\Service Desk Manager\site\didict.sch", "CA\Service Desk Manager\site\mods\wsp_schema.sch", "CA\Service Desk Manager\site\mods\majic\wsp_mods" and wspcol table. Every one of those have the column that i added but not the table itself. What can i do? Will another restart solve my problem?

P.S. I cannot restart the system constantly because it is a live environment.

Regards,

Barış

If the column name is already in NX_ROOT/site/mods/wsp_schema.log  file,  and you do a pdm_publish there after, that column is not added to the database.

So, I’d recommend checking the above file to see if there was an entry about that column already in it

_R

Hi Raghu,

Thanks for the reply. The log file shows that it is added by my pdm_publish. Should i delete this line and try another pdm_publish?

"2017.01.06 23:55:12 created column zusp_serv_bo.bowner"

Regards,

Barış

If the database is really missing this column in the table zusp_serv_bo then yes that method should help

The time stamp on the file is just last week, when did you publish ?

zusp_serv_bo.bowner

_R

I published at the timestamp time that i send at my previous reply. I can also see the custom colum at the bop_sinfo -d  as folows;

C:\Windows\system32>bop_sinfo -d zusp_serv_bo

Factory zusp_serv_bo
Attributes:
id INTEGER
producer_id LOCAL STRING(20)
persistent_id LOCAL STRING(60)
bo SREL -> nr.id
bowner SREL -> dept.id
serv SREL -> nr.id
last_mod_dt DATE
last_mod_by SREL -> cnt.id

But not in sql;

select * from zusp_serv_bo

id   last_mod_dt   last_mod_by   bo   serv

Will pdm_publish still work again? or should i just restart the CA SDM?

Thanks for the help.

Regards,

Barış

I would try removing that Column in the log file mentioned earlier and redo wsp - make a dummy schema change. Save. Stop SDM Pdm publish and start SDM.

_R

The following shoud help if column was not created in database:

backup %SDMROOT%\site\ddict.sch and %SDMROOT%\site\mods\wsp_schema.sch

backup wspcol table:

pdm_extract wspcol>swpcolbck.txt

Delete any information regarding bowner field in SDMROOT%\site\ddict.sch and %SDMROOT%\site\mods\wsp_schema.sch

Recycle SDM services

Extract bowner field information from wspcol

pdm_extract -f "select id, schema_name, status from wspcol where schema_name ='bowner'" >bowner.txt

edit created bowner.txt and change and change status value from 3 to 1 and save file

load changed information:

pdm_userload -a -m -f bowner.txt

Go to webscreen painter. Publish and save option in scema browser should be allready active so perform standart publishing procedure: 1. perform publish and save from wsp; 2. stop SDM services; 3. execute pdm_publish.