concurrency in perl (deployment)

Hi all,
I am looking for concurrency in the perl.
I want to deploy the content for two diffrent branches to database depending on their edition. For this I have designed deployment configurations for each one. THis configs will call a perl script in its script tag.
and then the perl script will execute each ones data deployment script.

Bothe the deployment works fine when they ran indivisually. But when I tried to run it sumulttenously from command line. only the first deployment happens. or some time both deploym,ent happens but partially.

If the tables are not exists in DB then the tables are created but the data does not deployed to DB. Is this could be issues of concurrencyt of Perl?

Does anyone had this problem?

Looking for the soluutions.

Thanks
-Parag

Find more posts tagged with

Comments

Ambuj

Hi all,
I am looking for concurrency in the perl.
I want to deploy the content for two diffrent branches to database depending on their edition. For this I have designed deployment configurations for each one. THis configs will call a perl script in its script tag.
and then the perl script will execute each ones data deployment script.

Bothe the deployment works fine when they ran indivisually. But when I tried to run it sumulttenously from command line. only the first deployment happens. or some time both deploym,ent happens but partially.

If the tables are not exists in DB then the tables are created but the data does not deployed to DB. Is this could be issues of concurrencyt of Perl?

Does anyone had this problem?

Looking for the soluutions.

Thanks
-Parag

I don't think this issue is related to PERL code. I assume that this has to do with the permissions on your DB Schema or the deployment procedure.

Try deploying some simple fixed values to database and check if it works well. Remove create access on this schema for TS/OD user and then check whether it deploys data to existing tables or not?

For me, issue needs to be debugged step-by-step. Meanwhile you can provide your perl code + dbschema.cfg for reference..

tejul

Did you try to use an instance name for each deployment ? (the -inst option in the command line)

ISCBorisB

Did you try to use an instance name for each deployment ? (the -inst option in the command line)

Parag has mentioned two individual Deployment configurations. Therefore run-time Deployment instances are unique and -inst usage would be redundant.
As pointed out by Ambuj the problem is in a database, both Deployments shared resource.

Adam Stoller

Hi all,
I am looking for concurrency in the perl.
I want to deploy the content for two diffrent branches to database depending on their edition. For this I have designed deployment configurations for each one. THis configs will call a perl script in its script tag.
and then the perl script will execute each ones data deployment script.

Bothe the deployment works fine when they ran indivisually. But when I tried to run it sumulttenously from command line. only the first deployment happens. or some time both deploym,ent happens but partially.

If the tables are not exists in DB then the tables are created but the data does not deployed to DB. Is this could be issues of concurrencyt of Perl?

Does anyone had this problem?

Looking for the soluutions.

Thanks
-Parag

Let's try to clarify a few things first:

and the first one that manages to execute does the INSERT, and the other one is stuck, confused, because it can no longer do an INSERT, it needs to do an UPDATE - but that wasn't what it was told to do ... (this is a common issue when invoking DD from OD in a fan-out deployment model - you have to create a distinct definition and execDeploymentTask for the part of the fan-out that will be responsible for running DD, and for the part that will just be deploying assets via OD.

Parag

[QUOTE=ghoti]Let's try to clarify a few things first:

Thanks alot for replies.The perl script is called from the deployment descriptor. some parameters are passed along with this like the name of data deployment descriptor.(****_dd.cfg)the Perl script gets the latest edition depending on the branch name. and executes the data deployment config.Here the scenario is such that:Two parent deployment configs associated with diffrent branch.These are calling a single perl script only the parameters passed are diffrent(name of _dd file)The two deployments are completely independent i.e. the data deployed to two diffrent tables. Both have no relation.Thanks.-Parag