nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

xCP 2.0 - BAM - Deploy from xCPDesigner error

dchavez@uade.edu.ar

Hi Everyone!

I've developed an application at xCP Designer 2.0. I have created some history queries, so some events are triggered. First time, I could install it without any problems. But I tried install it again after some modifications and I've had this error:

HTTP Status 500 - Request processing failed; nested exception is org.springframework.jdbc.UncategorizedSQLException: SqlMapClient operation; uncategorized SQLException for SQL []; SQL state [72000]; error code [1418]; --- The error occurred in config/ibatis/bam-deploy-sql-map-daos.xml. --- The error occurred while applying a parameter map. --- Check the oracle-dropIndex-InlineParameterMap. --- Check the statement (update failed). --- Cause: java.sql.SQLException: ORA-01418: specified index does not exist ; nested exception is com.ibatis.common.jdbc.exception.NestedSQLException: --- The error occurred in config/ibatis/bam-deploy-sql-map-daos.xml. --- The error occurred while applying a parameter map. --- Check the oracle-dropIndex-InlineParameterMap. --- Check the statement (update failed). --- Cause: java.sql.SQLException: ORA-01418: specified index does not exist

Could somebody help me?

Find more posts tagged with

Note:

If there are Accepted Answers, those will be shown by default. You can switch to 'All Replies' by selecting the tab below.

Button

Accepted answers

gildation

Per Support Team, this is a known issue (related to BAM running with Oracle). I think there is a P11 that fixes it.

As workaround, remove the BAM service from my XMS configuration.

All comments

dchavez@uade.edu.ar

This error happen when I've tried to install the application with parameter:

Minimal and Maintain.

This is the install URL: http://sdbuetmsgd13:8080/bam-server/admin?datapolicy=MAINTAIN&deploymentmethod=INCREMENTAL&deploymentenvironment=DEV&namespace=sgdi

I don't have any problems with the Clean parameter

StijnQ

I'm having the exact same problem. Yesterday I made some changes to a historical query, and now I can't deploy my application anymore. I get the same "ORA-01418: specified index does not exist".

I've encountered this problem 2-3 times last week as well, but then I was able to 'fix' it by undoing the changes to the historical query, deploying, and trying again. However, this time that doesn't work either.

Any help would be appreciated.

dchavez@uade.edu.ar

Hi Stijn

I can install the application with deployment-method full and data-policy clean in developer environment of xMS-Agent.

However we can install the modifications without problems in production environment xMS-Agent.

Rigth now, the deploy way on the development environment is

deployment-mehtod: full

datapolicy: clean

In production

Deployment-method: Incremental

datapolicy: maintain.

I hope that your problem be in development environment.

We're going to analize the problem with administrator. I'm writting you if we have some new news.

I'm sorry, but my English is not the best.

StijnQ

Hey Damian

Thank you for the response. I tried to deploy using the 'clean' datapolicy, but even that didn't work.

After trying just about everything I got it working again. I'm not sure what it was exactly that fixed it, but I'll describe the things I did. First I undeployed the application from the BAM server (on a dev server). This can be done by using this URL in a browser: http://<ip address>:<port>/bam-server/admin?action=undeploy&namespace=<namespace>. More info about this in the Documentum-xCelerated-Composition-Platform-2.2-Deployment-Guide.

After this I was able to deploy again. However, the deploy didn't really succeed (data on the server wasn't actually being changed). After trying a lot of things I reset the server to an earlier snapshot (this is on a dev server) and tried a clean deploy. This kept saying that it couldn't deploy (because of some metadata issues on the existing types). I kept trying to deploy (clean) and every time I got an error about metadata issues on a different type than before. After trying a few times i received no more errors and the deployment succeeded.

Hope this is of any help to you.

dchavez@uade.edu.ar

Hi Stijn

Thanks u for all information ...This way is too complicated to work. We're working with only this method: deploy-method: full and data-policy: clean.

I'd like to do one comments: I know that the undeploy method does not eliminate the tables on the database. You should undeploy the application and drop the tables BAM database. It is necessary to delete register of dm_jobs, too and another tables.

The idea is implement the deploy-method: Incremental and data-policy: minimal, without have to delete the application or restore the environment development.

We're going to analyze it next week this problem..... I hope have a new news ....

One questions: Are you working with xCP 2.2? Because We'd like to migrate and if u have the same problems, it's complicated to do it.

Tanks you again!

Damian

StijnQ

Hey Damian

I was not aware of that, but everything is working for now, so I won't be dropping any tables.

I am using the latest patch of xCP Designer 2.2, yes.

Hope you are able to find a solution for your problem as well!

Stijn

gildation

Per Support Team, this is a known issue (related to BAM running with Oracle). I think there is a P11 that fixes it.

As workaround, remove the BAM service from my XMS configuration.

dchavez@uade.edu.ar

Hi Gildation! Thank you for your answer.

I'm going to try to remove the BAM configuration on the xMS Server. I'm going to check the BAM version for the oracle database, too.

Thank you!

Damian

dchavez@uade.edu.ar

I've changed the deploy method and I could deploy the application with incremental method.

Thanks you GIldation, again.