Skip to main content

This content is closed to future replies and is no longer being maintained or updated.
Links may no longer function. If you have a similar request, please write a new post.

Question

 Sumanto Chatterjee (Sumanto) Capgemini Developer
Capgemini
ES
Sumanto Member since 2015 4 posts
Capgemini
Posted: Jun 1, 2017
Last activity: Jun 1, 2017
Posted: 1 Jun 2017 2:25 EDT
Last activity: 1 Jun 2017 8:00 EDT
Closed

Getting error while upgrading from 6.2 to 7.2.2

As a first part of upgrade process while migrating rules from source schema to temp directory getting error.

Can anyone help me out?

Please find the attached error screen shot.

To see attachments, please log in.
Updates

Posted: 7 years ago
Posted: 1 Jun 2017 3:02 EDT
Laurence Brannigan (LaurenceB_GCS) PEGA Senior Software Solutions Engineer
PEG
GB

The attached screen shot only shows the end of the SQL that failed. Do you still have this? If so could you post the top of the SQL so that we can see the table name?

Also, it would probably help to correlate this if you could let us know the following settings from your migrateSystem.properties file: -

pega.source.rules.schema

pega.source.data.schema

pega.target.rules.schema

pega.target.data.schema

 

As well as the last section of migrateSystem.properties, beginning from "######## The operations to be run by the utility"

To see attachments, please log in.
Posted: 7 years ago
Posted: 1 Jun 2017 4:16 EDT
Basavaraj Kadakol (BASAVARAJ) PEGA Senior Manager of Technical Support Engineering
Pegasystems Inc.
AU

Hi Sumant,

Can you verify the user has required grants on the source schema and permissions on the temp folder?

Regards,

Basavaraj

To see attachments, please log in.
Posted: 7 years ago
Posted: 1 Jun 2017 4:49 EDT
Sumanto Chatterjee (Sumanto) Capgemini Developer
Capgemini
ES

@ LaurenceB_GCS :- Every time i'm getting the same error for PR4_BASE,it says table or view does not exist.

And  also please find the below details that had updated in the migrate.properties file

Source Schema details(Driver class,jar,type,url,username,password)

Target Schema details(Driver class,jar,type,url,username,password)

pega.source.rules.schema is set to blank

pega.source.data.schema is set to blank

pega.target.rules.schema is set to blank

pega.target.data.schema is set to blank

pega.bulkmover.directory=C:\PEGA_POC_722_Setup\PRPC_Temp\Migrate

pega.migrate.temp.directory=C:\PEGA_POC_722_Setup\PRPC_Temp\Migrate

pega.bulkmover.unload.db=true

pega.clone.apply.ddl=true

pega.clone.create.ddl=true

pega.clone.generate.xml=true

Show More

@ LaurenceB_GCS :- Every time i'm getting the same error for PR4_BASE,it says table or view does not exist.

And  also please find the below details that had updated in the migrate.properties file

Source Schema details(Driver class,jar,type,url,username,password)

Target Schema details(Driver class,jar,type,url,username,password)

pega.source.rules.schema is set to blank

pega.source.data.schema is set to blank

pega.target.rules.schema is set to blank

pega.target.data.schema is set to blank

pega.bulkmover.directory=C:\PEGA_POC_722_Setup\PRPC_Temp\Migrate

pega.migrate.temp.directory=C:\PEGA_POC_722_Setup\PRPC_Temp\Migrate

pega.bulkmover.unload.db=true

pega.clone.apply.ddl=true

pega.clone.create.ddl=true

pega.clone.generate.xml=true

pega.move.admin.table=true

pega.bulkmover.load.db=true

pega.rules.objects.generate=false

pega.rules.objects.apply=false

i have also attached the error details screen shot.Could you please help me out regarding this.


Show Less
To see attachments, please log in.
Posted: 7 years ago
Posted: 1 Jun 2017 6:04 EDT
Gowrishankar Ramasamy (GowrishankarR29) Citicorp Services India Private Limited
Citicorp Services India Private Limited
IN

Hi Suman,

             I could see that the following properties are blank in the migrate system.properties    

pega.source.rules.schema is set to blank

pega.source.data.schema is set to blank

pega.target.rules.schema is set to blank

pega.target.data.schema is set to blank

           I hope you are performing single to split schema upgrade, If that is the case, first we need to migrate the rules related tables and objects to a new schema (This schema would be called the rules schema). You need to fill out the above mentioned four properties.

Source Schema details(Driver class,jar,type,url,username,password)

Target Schema details(Driver class,jar,type,url,username,password)

Show More

Hi Suman,

             I could see that the following properties are blank in the migrate system.properties    

pega.source.rules.schema is set to blank

pega.source.data.schema is set to blank

pega.target.rules.schema is set to blank

pega.target.data.schema is set to blank

           I hope you are performing single to split schema upgrade, If that is the case, first we need to migrate the rules related tables and objects to a new schema (This schema would be called the rules schema). You need to fill out the above mentioned four properties.

Source Schema details(Driver class,jar,type,url,username,password)

Target Schema details(Driver class,jar,type,url,username,password)

Here Source schema and target schema details should be the same. The username configured here should have access to the 62(Single schema) Schema and newly created Rules schema, to which the rules related tables and objects would be migrated to.

pega.source.rules.schema should be set to 62(Single schema) schema.

pega.source.data.schema should be set to 62(Single schema) schema.

pega.target.rules.schema should be set to newly created Rules schema.

pega.target.data.schema is set to blank

Could you please do the necessary modifications to migrate.properties file and do the migration and let us know the results.

 

Thanks,

Gowrishankar.


Show Less
To see attachments, please log in.
Posted: 7 years ago
Posted: 1 Jun 2017 7:01 EDT
Sumanto Chatterjee (Sumanto) Capgemini Developer
Capgemini
ES

From the above comment i'm bit confused with this part

Here Source schema and target schema details should be the same. 

As from the pdn tutorial i have understand that in the source schema the details will be for 6.2(Considering Old as 6.2) and in the target schema the details will be for the temporary empty schema.Please find the attached screenshot where i had taken the reference.

Kindly help.

 

To see attachments, please log in.
Posted: 7 years ago
Posted: 1 Jun 2017 7:26 EDT
Gowrishankar Ramasamy (GowrishankarR29) Citicorp Services India Private Limited
Citicorp Services India Private Limited
IN

Hi Suman,

            Sorry I have confused you a bit. It is Source DB details and Target DB details should be same. and also pega.source.data.schema should be blank. Since we are going to seperate out only the rules from unified schema. Hope it is clear, please let me know if you are not clear.

Thanks,

Gowrishankar.

To see attachments, please log in.
Posted: 7 years ago
Posted: 1 Jun 2017 8:00 EDT
Sumanto Chatterjee (Sumanto) Capgemini Developer
Capgemini
ES

Hi Gowrishankar,

Please correct me if i'm wrong.So you mean to say whatever details i had given for source DB details and Destination DB details that is correct.i.e.

Source Schema details(Driver class,jar,type,url,username,password) :- 6.2 details (considering my old one as 6.2)

Target Schema details(Driver class,jar,type,url,username,password)  :- Temporary empty schema details

pega.source.rules.schema :- 6.2(Single schema)

pega.source.data.schema  :- 6.2(Single schema)

pega.target.rules.schema  :- Newly created rule schema(What should be the value here as i had created only temporary empty schema).

pega.target.data.schema   :- It will be blank.

 

Show More

Hi Gowrishankar,

Please correct me if i'm wrong.So you mean to say whatever details i had given for source DB details and Destination DB details that is correct.i.e.

Source Schema details(Driver class,jar,type,url,username,password) :- 6.2 details (considering my old one as 6.2)

Target Schema details(Driver class,jar,type,url,username,password)  :- Temporary empty schema details

pega.source.rules.schema :- 6.2(Single schema)

pega.source.data.schema  :- 6.2(Single schema)

pega.target.rules.schema  :- Newly created rule schema(What should be the value here as i had created only temporary empty schema).

pega.target.data.schema   :- It will be blank.

 

Your help is much appreciated.

 

Thanks

 

 

 


Show Less
To see attachments, please log in.
Posted: 7 years ago
Posted: 1 Jun 2017 4:51 EDT
Sumanto Chatterjee (Sumanto) Capgemini Developer
Capgemini
ES

@BASAVARAJ_GCS- yes Basavaraj as i'm having the administrator access of the machine where it is getting installed,so i have the required access for  temp folder.

I'm not sure with the grant of the source schema.Could you explain.

To see attachments, please log in.

We'd prefer it if you saw us at our best.

Pega Collaboration Center has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice