Discussion
Bank of New Zealand
IN
Last activity: 6 Apr 2018 19:26 EDT
Upgrade from PRPC 5.5 to PRPC 7.1.7 (Split schem) - while performing rule migration, encountered "insufficient privileges" error
upgrade scripts from single(5.5) to split schema (7.1.7).
we are upgrading pega platform from 5.5 to 7.1.7. while performing rules migration from existing schema to newly created schema,
i verified the Deployment user has all the access privileges also alter any table access. even though we are facing the following insufficient error message.
deployment user privilege details:
CREATE TRIGGER
ALTER ANY TABLE
GRANT ANY PRIVILEGE
DROP ANY TRIGGER
CREATE ANY TRIGGER
CREATE ANY PROCEDURE
CREATE ANY TABLE
CREATE TABLE
GRANT ANY OBJECT PRIVILEGE
DROP ANY PROCEDURE
CREATE PROCEDURE
DROP ANY VIEW
CREATE ANY VIEW
SELECT ANY TABLE
CREATE VIEW
Privilege access error:
[java] INFO: ALTER TABLE PEGA7_CRDB_OWNER.PC_INDEX_FLOWREF
[java] Sep 25, 2015 09:37:06 PM com.pega.pegarules.install.SQLLoader writeM
ge
[java] WARNING: Failed to execute SQL in file oracledate00020.sql
[java] Sep 25, 2015 09:37:06 PM com.pega.pegarules.install.SQLLoader writeM
ge
[java] WARNING: Statement: ALTER TABLE PEGA7_CRDB_OWNER.PC_INDEX_FLOWREF
[java] ADD CONSTRAINT PC_INDEX_FLOWREF_PK PRIMARY KEY
[java] (
[java] PZINSKEY
[java] )
[java] java.sql.SQLSyntaxErrorException: ORA-01031: insufficient privileges
Steps we followed.
1.we have one exsiting schema with all the Pega 5.5 related rules tables. and we created a new schame to migrate Rules from existing schema
2. created a deployment user whcih have access for both the schemas. and i verified that the deploymentuser has all the access.
3. modified the migratesystem.properties files as below. and execute the migrate.bat file.
#The system where the tables/rules will be migrated from
pega.source.jdbc.driver.jar=D:\Pega717\Ojdbc\ojdbc6.jar
pega.source.jdbc.driver.class=oracle.jdbc.OracleDriver
pega.source.database.type=oracledate
pega.source.jdbc.url=jdbc:oracle:thin:@//(HOSTNAME):1521/(SERVICE Name)
pega.source.jdbc.username=DEPLOYMENT_USER
pega.source.jdbc.password=DEPLOYMENT_USER123
pega.source.rules.schema=FP7_DEVDATA_OWNER (Data Schema)
#The system where the tables/rules will be migrated to
pega.target.jdbc.driver.jar=D:\Pega717\Ojdbc\ojdbc6.jar
pega.target.jdbc.driver.class=oracle.jdbc.OracleDriver
pega.target.database.type=oracledate
pega.target.jdbc.url=jdbc:oracle:thin:@//(HOSTNAME):1521/(SERVICE Name)
pega.target.jdbc.username=DEPLOYMENT_USER
pega.target.jdbc.password=DEPLOYMENT_USER123
pega.target.rules.schema=PEGA7_CRDB_OWNER (Rules Schema whcih is created newly)
pega.bulkmover.directory=D:\Pega717\Firstpiont\Migration\BulkMoverDir
pega.migrate.temp.directory=D:\Pega717\Firstpiont\Migration\Temp
pega.move.admin.table=true
pega.clone.generate.xml=true
pega.clone.create.ddl=true
pega.clone.apply.ddl=true
pega.bulkmover.unload.db=true
pega.bulkmover.load.db=true
Please suggest to identify the root cause?
**Moderation Team has archived post**
This post has been archived for educational purposes. Contents and links will no longer be updated. If you have the same/similar question, please write a new post.