Question

4
Replies
502
Views
MULSJ Member since 2012 2 posts
PEGA
Posted: 5 years ago
Last activity: 5 years 2 months ago
Closed
Solved

Error when running migrate script

Any suggestions how to resolve the following error:

Setup:
[pega:propertyparser] Reading Properties from : /dev/shm/Pega7DBpackages/scripts/migrateSystem1.properties
[mkdir] Created dir: /dev/shm/Pega7DBpackages/Temp/MigrateTemp-29-June-2015-17.47.20
[echo] Using temporary directory /dev/shm/Pega7DBpackages/Temp/MigrateTemp-29-June-2015-17.47.20
[unzip] Expanding: /dev/shm/Pega7DBpackages/archives/pegadbinstall-classes.zip into /dev/shm/Pega7DBpackages/Temp/MigrateTemp-29-June-2015-17.47.20/load
[echo] Using logging configuration from: ./config/deploylogging.properties

Generate Table Lists:
[java] Platform = oracledate
[java] Filename:/dev/shm/Pega7DBpackages/Temp/MigrateTemp-29-June-2015-17.47.20/tables.txt
[java]
[java] This system uses a non-standard configuration and requires special considerations during upgrade.
[java] Please contact Pega Global Customer Service before continuing.
[java]
[java] The following Data-Admin-DB-Table records are explictly mapped to a schema:
[java] PR4_FIELDVALUE

BUILD FAILED
/dev/shm/Pega7DBpackages/scripts/migrateSystem1.xml:799: Java returned: 1

When I went to tables.txt, it was empty.

Migrate.properties:
pega.source.jdbc.driver.jar=/dev/shm/Pega7DBpackages/scripts/oracle-11.1.0.6.jar
pega.source.jdbc.driver.class=oracle.jdbc.OracleDriver
pega.source.database.type=oracledate
pega.source.jdbc.url=jdbc:oracle:thin:@psin5p354-scan.jpmchase.net:6135/RRP_BAU_D.IM.AWM.JPMC.NET
pega.source.jdbc.username=xxxxxxxxxx
pega.source.jdbc.password=xxxxxxxxxxxxxx
#Custom connection properties
#pega.source.jdbc.custom.connection.properties=

pega.source.rules.schema=PEGADBO
#Set the following property if the source system already contains a split schema.
pega.source.data.schema=

#The system where the tables/rules will be migrated to
pega.target.jdbc.driver.jar=oracle-11.1.0.6.jar
pega.target.jdbc.driver.class=oracle.jdbc.OracleDriver
pega.target.database.type=oracledate
pega.target.jdbc.url=jdbc:oracle:thin:@psin5p354-scan.jpmchase.net:6135/RRP_BAU_D.IM.AWM.JPMC.NET
pega.target.jdbc.username=xxxxxxxxx
pega.target.jdbc.password=xxxxxxx
#Custom connection properties
#pega.target.jdbc.custom.connection.properties=

pega.target.rules.schema=PEGADBO_RULES
#Used to correctly schema qualify tables in stored procedures, views and triggers.
#This property is not required if migrating before performing an upgrade.
pega.target.data.schema=

#Set this property to bypass udf generation on the target system.
#pega.target.bypass.udf

#The location of the db2zos site specific properties file. Only used if the target system is a db2zos database.
#pega.target.zos.properties=config/db2zos/DB2SiteDependent.properties

#The commit count to use when loading database tables
db.load.commit.rate=1000

################### Migrate System Properties ###########################################
#The directory where output from the bulk mover will be stored. This directory will be cleared when pega.bulkmover.unload.db is run.
#This property must be set if either pega.bulkmover.unload.db or pega.bulkmover.load.db is set to true.
pega.bulkmover.directory=/dev/shm/Pega7DBpackages/BulkMover

#The location where a temporary directory will be created for use by the migrate system utilities.
pega.migrate.temp.directory=/dev/shm/Pega7DBpackages/Temp

######## The operations to be run by the utility, they will only be run if the property is set to true.
#Set to true if migrating before an upgrade. If true admin table(s) required
#for an upgrade will be migrated with the rules tables.
pega.move.admin.table=true
#Generate an xml document containing the definitions of tables in the source system. It will be found in the schema directory of the
#distribution image.
pega.clone.generate.xml=true
#Create ddl from the generated xml document. This ddl can be used to create copies of rule tables found on the source system.
pega.clone.create.ddl=true
#Apply the generated clone ddl to the target system.
pega.clone.apply.ddl=true
#Unload the rows from the rules tables on the source system into the pega.bulkmover.directory.
pega.bulkmover.unload.db=true
#Load the rows onto the target system from the pega.bulkmover.directory.
pega.bulkmover.load.db=true

### The following operations should only be run when migrating upgraded rules
#Generate the rules schema objects (views, triggers, procedures, functions). The objects will be created in the pega.target.rules.schema
#but will contain references to the pega.target.data.schema where appropriate.
pega.rules.objects.generate=false
#Apply the rules schema objects (views, triggers, procedures, functions) to pega.target.rules.schema.
pega.rules.objects.apply=false

***Updated by moderator: Lochan to close 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.

Low-Code App Development Upgrades
Moderation Team has archived post
Share this page LinkedIn