SREL actbool attributes are not visible after pdm_publish

[Anon Anon]

Dear Team

 

In CA SDM 14.1 after publishing the schema with pdm_publish also the SREL attribute delete_flag is not visible.

 

PFA screen shots for the same.

 

Please do help in this.

 

Thanks

Saswata

[Anon Anon]

Hi Saswata,

 

Did the pdm_publish processed successfully? Verify if the field is there in didct.sch file and also do you see the field in the SQL?

 

Thanks,

Naveen

[Anon Anon]

Dear Naveen

 

Yes pdm_publish completed successfully and the failover for AA also done and its also visible in the database. (PFA)

[Anon Anon]

Can anybody help me on this?

[Legacy User]

Hi,

have you tried to republish your attr?

You can use PDM_WSPUPD script:

https://wiki.ca.com/display/CASM1401/How%20to%20Modify%20Schema%20Using%20Web%20Screen%20Painter

 

Or try to add column manually.

Check the followed tech doc to find where your attribte should be defined:

http://www.ca.com/us/support/ca-support-online/product-content/knowledgebase-articles/tec605766.aspx

 

regards,

cdtj

[Giedrius Bekintis]

Do you use Advanced Availability setup? If yes did you performed all of the steps bellow?

 

If you are using the advanced availability configuration, complete the following steps:

1. Execute the following command on the background server to notify all active users using Support Automation to save their work: sa_server_notifier [-h] | [-q seconds] | [-c]

   -h

   Displays the help page.

   -q seconds

   This option notifies a local server (background) to quiesce in a specified time interval. This interval is the number of seconds before the server goes offline. This option cannot be used for a standby server or application server.

   -c

   This option cancels a previously sent quiesce request.

   A pop-up message is displayed to all the active users using Support Automation on the background server. This message notifies the users about the server shutdown and the scheduled time left for the shutdown. The users must save their work and logout within that scheduled time.

2. Shut down the CA Service Desk Manager services on the background server. Important! Do not restart the CA Service Desk Manager services on standby or application servers after "save and publish" is performed from WSP. This action corrupts the advanced availability configuration. If the CA Service Desk Manager services on standby or application servers are stopped and you want to start the services, run the pdm_server_control –v command on the servers to suppress the version control before starting the CA Service Desk Manager services.Important! If the background server fails during the publishing activity, ensure that you recover the WSP changes. For more information, see the Recover WSP Changes During Background Server Failure topic.
3. Execute the following command on the standby server that you wish to promote as the new background server: pdm_server_control -b

   -b

   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.

   The background server shuts down automatically and the standby server is promoted as the new background server. This change does not affect the end-user sessions. The in-progress updates (if any) are stored and delayed, until the new background server comes online.

4. Run the following command on the original background server (now the standby server) to update the DBMS with the schema changes: pdm_publish

   The pdm_publish command creates a control file that causes the next CA Service Desk Manager startup to suppress synchronizing the standby server with the background server. This action is necessary to preserve the schema file changes made by pdm_publish. This command optionally performs the second fail-over after successful publishing of the schema changes. The following message is prompted to the user at the end of successful publishing:

   Do you want pdm_publish to start CA Service Desk Manager in this standby server and perform fail-over(Y/N)? 

   • If you enter Y, pdm_publish starts the CA Service Desk Manager services on the standby server and performs fail-over automatically. Skip to step g to apply the schema changes on all the application servers.
   • If you enter N, go to Step e.
5. Start CA Service Desk Manager services on the standby server (original background server). The startup detects the control file that is created by pdm_publish, but does not synchronize the standby server with the background server. This lack of synchronization preserves the changes made by pdm_publish for this startup.Important! Ensure that you follow these directions exactly, as the failure to failover to the original background server after a pdm_publish results in corrupted services.
6. Run the following command on the standby server (original background server) to make it the background server again: pdm_server_control -b

   This command also deletes the control file, so that version control works normally when this server again becomes a standby server.

7. Execute the following command on the application servers: pdm_server_control -q interval -s server_name

   -q interval -s server_name

   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.

   A pop-up message is displayed to all the active users on the specified application server. This message notifies the users about the server shutdown and the scheduled time left for the shutdown. The users must save their work and logout within that scheduled time. The users log on to the updated application server to resume their work.

8. Restart all standby servers.

[Anon Anon]

Did the same but still its not coming

[Chi Chen]

Saswata, when you said not visible did you mean not seen in

bop_sinfo command or not seen in the web page? Using bop_sinfo

command you can check if the schema change/added attribute is there

and once this is confirmed, you can start use/troubleshoot it in the web

pages. Thanks _Chi