cancel
Showing results for 
Search instead for 
Did you mean: 

Business scenario generation error

manikunj_kausal
Explorer
0 Kudos

Hi ,

I have created Business scenario by importing BPM process into HANA OPInt. Business scenario is validated successfully but not able to generate it .getting following message :

  Failed to acquire scenario lock; either a background process is processing the scenario or another user is performing operations on the scenario:

        SAP DBTech JDBC: [258]: insufficient privilege: Not authorized for table         SYS_PROCESS_VISIBILITY.sap.opi.pv::SPVR_SCENARIO_DEFINITION_LOCK : SAP DBTech JDBC:

        [258]: insufficient privilege: Not authorized for table SYS_PROCESS_VISIBILITY.sap.opi.pv::SPVR_SCENARIO_DEFINITION_LOCK

        com.sap.pv.opm.hana.runtime.exception.ScenarioLockException: SAP DBTech JDBC:

        [258]: insufficient privilege: Not authorized for table SYS_PROCESS_VISIBILITY.sap.opi.pv::SPVR_SCENARIO_DEFINITION_LOCK

  at com.sap.pv.opm.hana.runtime.impl.PVScenarioLock.lock(PVScenarioLock.java:68)

  at com.sap.ndb.studio.pv.opm.resource.PVResourceController.generate(PVResourceController.java:1132)

  at com.sap.ndb.studio.pv.opm.jobs.GenerateJob.generate(GenerateJob.java:184)

  at com.sap.ndb.studio.pv.opm.jobs.GenerateJob.activateAndGenerate(GenerateJob.java:151)

  at com.sap.ndb.studio.pv.opm.jobs.GenerateJob.run(GenerateJob.java:94)

  at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)

Caused by: com.sap.db.jdbc.exceptions.JDBCDriverException: SAP DBTech JDBC: [258]: insufficient privilege: Not authorized

  at com.sap.db.jdbc.exceptions.SQLExceptionSapDB.createException(SQLExceptionSapDB.java:345)

  at com.sap.db.jdbc.exceptions.SQLExceptionSapDB.generateDatabaseException(SQLExceptionSapDB.java:185)

  at com.sap.db.jdbc.packet.ReplyPacket.buildExceptionChain(ReplyPacket.java:102)

  at com.sap.db.jdbc.ConnectionSapDB.execute(ConnectionSapDB.java:1033)

  at com.sap.db.jdbc.CallableStatementSapDB.sendCommand(CallableStatementSapDB.java:1790)

  at com.sap.db.jdbc.StatementSapDB.sendSQL(StatementSapDB.java:945)

  at com.sap.db.jdbc.CallableStatementSapDB.doParse(CallableStatementSapDB.java:185)

  at com.sap.db.jdbc.CallableStatementSapDB.constructor(CallableStatementSapDB.java:144)

  at com.sap.db.jdbc.CallableStatementSapDB.<init>(CallableStatementSapDB.java:89)

  at com.sap.db.jdbc.CallableStatementSapDBFinalize.<init>(CallableStatementSapDBFinalize.java:31)

  at com.sap.db.jdbc.ConnectionSapDB.prepareStatement(ConnectionSapDB.java:1268)

  at com.sap.db.jdbc.trace.Connection.prepareStatement(Connection.java:416)

  at com.sap.ndb.studio.jdbc.JDBCConnection.prepareStatement(JDBCConnection.java:553)

  at com.sap.pv.opm.hana.runtime.persistency.PersistenceProvider.prepareStatement(PersistenceProvider.java:107)

  at com.sap.pv.opm.hana.runtime.persistency.PersistenceProvider.executeWithPreparedStatement(PersistenceProvider.java:99)

  at com.sap.pv.opm.hana.runtime.persistency.PersistenceProvider.insert(PersistenceProvider.java:70)

  at com.sap.pv.opm.hana.runtime.impl.PVScenarioLock.lock(PVScenarioLock.java:60)

And for this attached the image for that error

To resolve this error I have tried to  execute following code as mention in the developer guide section( 6.Releasing the lock scenario) by replacing package name and scenario name,but not  executing this code showing error in this code.

deletefrom "SYS_PROCESS_VISIBILITY" . "sap.opi.pv::SPVR_SCENARIO_DEFINITION_LOCK" where

"SCENARIO_DEFINITION_ID" in

(select "SCENARIO_DEF_ID" from "SYS_PROCESS_VISIBILITY" . "sap.opi.pv::SPVD_SCENARIO_METADATA" t1 join "SYS_PROCESS_VISIBILITY" . "sap.opi.pv::SPVR_SCENARIO_DEFINITION_LOCK" t2 on t1.SCENARIO_DEF_ID = t2.SCENARIO_DEFINITION_ID where t1. "SCENARIO_NAME" = '<package name.scenario name>'groupby "SCENARIO_DEF_ID" )


Accepted Solutions (1)

Accepted Solutions (1)

Archana
Product and Topic Expert
Product and Topic Expert
0 Kudos

Hello Mani,

You need to have OPINT_DEVELOPER role to generate the business scenario. Please ensure you have this role assigned to your user. Also, ensure that _SYS_REPO user have SELECT privilege, with grantable option, for the source schema that is used in your business scenario. Please go through the Authorization section in the guides to ensure that you have all required roles needed to design, generate and view the Business Scenario.

regards,

Archana

Answers (0)