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

 Bin Xu (GAVINHSU)
Mediatek Inc. China

Mediatek Inc. China
CN
GAVINHSU Member since 2011 37 posts
Mediatek Inc. China
Posted: Aug 13, 2015
Last activity: Nov 18, 2015
Posted: 13 Aug 2015 21:16 EDT
Last activity: 18 Nov 2015 10:25 EST
Closed
Solved

ClassNotFoundException: PRAppLoader when upgrading from 6.1 SP2 to 7.1.8

When I tried to upgrade our PEGA platform from version 6.1 SP2 to 7.1.8, this error came to us after running the upgrade.bat for 133 minutes 51 seconds.

I've checked the database, there is no table names PR_ASSEMBLEDCLASSES at all.

I'm wondering whether this table should be migrated from old database or not? I'm pretty sure that here's no error when I migrated tables from old database.

Does anyone know what is the root cause, and how to resolve it? Appreciate a lot.

[java] 2015-8-13 18:11:45 com.pega.pegarules.internal.bootstrap.PRMiniLoader

     [java] 19830421: Will load phase 2 bootstrap from Pega-EngineCode:07-10-17

     [java] Warn - NonVersionedJdbcJarReader - unable to load classes from the database: DB2 SQL Error: SQLCODE=-204, SQLSTATE=42704, SQLERRMC=BPMRULED.PR_ASSEMBLEDCLASSES, DRIVER=4.11.77

     [java] 2015-8-13 18:12:33 com.pega.pegarules.internal.bootstrap.phase2.PRBootstrapImpl

     [java] 19830421: PegaRULES classes will be loaded from jar files (and NOT the database)

     [java] 2015-8-13 18:12:35 com.pega.pegarules.internal.bootstrap.phase2.PRBootstrapImpl

     [java] 严重: Error initializing PRAppLoader

     [java] java.lang.ClassNotFoundException: com.pega.pegarules.bootstrap.loader.PRAppLoader

     [java] at com.pega.pegarules.internal.bootstrap.phase2.PRBaseLoader.findClass(PRBaseLoader.java:312)

     [java] at java.lang.ClassLoader.loadClass(Unknown Source)

Show More

When I tried to upgrade our PEGA platform from version 6.1 SP2 to 7.1.8, this error came to us after running the upgrade.bat for 133 minutes 51 seconds.

I've checked the database, there is no table names PR_ASSEMBLEDCLASSES at all.

I'm wondering whether this table should be migrated from old database or not? I'm pretty sure that here's no error when I migrated tables from old database.

Does anyone know what is the root cause, and how to resolve it? Appreciate a lot.

[java] 2015-8-13 18:11:45 com.pega.pegarules.internal.bootstrap.PRMiniLoader

     [java] 19830421: Will load phase 2 bootstrap from Pega-EngineCode:07-10-17

     [java] Warn - NonVersionedJdbcJarReader - unable to load classes from the database: DB2 SQL Error: SQLCODE=-204, SQLSTATE=42704, SQLERRMC=BPMRULED.PR_ASSEMBLEDCLASSES, DRIVER=4.11.77

     [java] 2015-8-13 18:12:33 com.pega.pegarules.internal.bootstrap.phase2.PRBootstrapImpl

     [java] 19830421: PegaRULES classes will be loaded from jar files (and NOT the database)

     [java] 2015-8-13 18:12:35 com.pega.pegarules.internal.bootstrap.phase2.PRBootstrapImpl

     [java] 严重: Error initializing PRAppLoader

     [java] java.lang.ClassNotFoundException: com.pega.pegarules.bootstrap.loader.PRAppLoader

     [java] at com.pega.pegarules.internal.bootstrap.phase2.PRBaseLoader.findClass(PRBaseLoader.java:312)

     [java] at java.lang.ClassLoader.loadClass(Unknown Source)

     [java] at com.pega.pegarules.internal.bootstrap.phase2.PRBaseLoader.loadClass(PRBaseLoader.java:237)

     [java] at java.lang.ClassLoader.loadClass(Unknown Source)

     [java] at java.lang.Class.forName0(Native Method)

     [java] at java.lang.Class.forName(Unknown Source)

     [java] at com.pega.pegarules.internal.bootstrap.phase2.PRBootstrapImpl.initializeAppLoader(PRBootstrapImpl.java:1134)

     [java] at com.pega.pegarules.internal.bootstrap.phase2.PRBootstrapImpl._finishInitialization_privact(PRBootstrapImpl.java:250)

     [java] at com.pega.pegarules.internal.bootstrap.phase2.PRBootstrapImpl.finishInitialization(PRBootstrapImpl.java:122)

     [java] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

     [java] at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)

     [java] at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)

     [java] at java.lang.reflect.Method.invoke(Unknown Source)

     [java] at com.pega.pegarules.internal.bootstrap.PRBootstrap.checkForStartup(PRBootstrap.java:682)

     [java] at com.pega.pegarules.internal.bootstrap.PRBootstrap.invokeMethodPropagatingThrowable(PRBootstrap.java:405)

     [java] at com.pega.pegarules.boot.internal.extbridge.AppServerBridgeToPega.invokeMethodPropagatingThrowable(AppServerBridgeToPega.java:223)

     [java] at com.pega.pegarules.boot.internal.extbridge.AppServerBridgeToPega.invokeMethod(AppServerBridgeToPega.java:272)

     [java] at com.pega.pegarules.pub.PegaRULES.main(PegaRULES.java:85)

     [java] 2015-8-13 18:12:35 com.pega.pegarules.internal.bootstrap.PRBootstrap

     [java] 19830421:

     [java] ============ PegaRULES Bootstrap Configuration ============

     [java]            Date: Thu Aug 13 18:12:35 CST 2015

     [java]    Java Version: Sun Microsystems Inc. 1.6.0_30

     [java]   Configuration: file:/C:/Users/mtk40659/AppData/Local/Temp//PegaInstallTemp-13-August-2015-15.58.45/prbootstrap.properties

     [java] Pega-EngineCode: 07-10-17

     [java]     JDBC Driver: com.ibm.db2.jcc.DB2Driver

     [java]        JDBC URL: jdbc:db2:// Proprietary information hidden:50000/bpmd2:fullyMaterializeLobData=true;fullyMaterializeInputStreams=true;progressiveStreaming=2;useJDBC4ColumnNameAndLabelSemantics=2;

     [java]       JDBC User: bpmruled

     [java]        Database: DB2/LINUXX8664 SQL09073

     [java]          Driver: IBM Data Server Driver for JDBC and SQLJ 4.11.77

     [java] Active CodeSets: pega-enginecode:07-10-17 at (latest patch)

     [java]

     [java] =============== End Bootstrap Configuration ===============

     [java]

     [java] 2015-8-13 18:12:35 com.pega.pegarules.boot.internal.extbridge.AppServerBridgeToPega

     [java] 严重: Problem during method invocation (main)

     [java] java.lang.RuntimeException: PRAppLoader was not properly initialized, unable to load class com.pega.pegarules.deploy.internal.util.ImportImpl

     [java] at com.pega.pegarules.internal.bootstrap.PRBootstrap.getImplementationOf(PRBootstrap.java:205)

     [java] at com.pega.pegarules.internal.bootstrap.PRBootstrap.getEntry(PRBootstrap.java:321)

     [java] at com.pega.pegarules.internal.bootstrap.PRBootstrap.getMethod(PRBootstrap.java:301)

     [java] at com.pega.pegarules.internal.bootstrap.PRBootstrap.invokeMethodPropagatingThrowable(PRBootstrap.java:406)

     [java] at com.pega.pegarules.boot.internal.extbridge.AppServerBridgeToPega.invokeMethodPropagatingThrowable(AppServerBridgeToPega.java:223)

     [java] at com.pega.pegarules.boot.internal.extbridge.AppServerBridgeToPega.invokeMethod(AppServerBridgeToPega.java:272)

     [java] at com.pega.pegarules.pub.PegaRULES.main(PegaRULES.java:85)

     [java] Exception in thread "main" java.lang.RuntimeException: Problem during method invocation (main)

     [java] at com.pega.pegarules.boot.internal.extbridge.AppServerBridgeToPega.invokeMethod(AppServerBridgeToPega.java:278)

     [java] at com.pega.pegarules.pub.PegaRULES.main(PegaRULES.java:85)

     [java] Caused by: java.lang.RuntimeException: PRAppLoader was not properly initialized, unable to load class com.pega.pegarules.deploy.internal.util.ImportImpl

     [java] at com.pega.pegarules.internal.bootstrap.PRBootstrap.getImplementationOf(PRBootstrap.java:205)

     [java] at com.pega.pegarules.internal.bootstrap.PRBootstrap.getEntry(PRBootstrap.java:321)

     [java] at com.pega.pegarules.internal.bootstrap.PRBootstrap.getMethod(PRBootstrap.java:301)

     [java] at com.pega.pegarules.internal.bootstrap.PRBootstrap.invokeMethodPropagatingThrowable(PRBootstrap.java:406)

     [java] at com.pega.pegarules.boot.internal.extbridge.AppServerBridgeToPega.invokeMethodPropagatingThrowable(AppServerBridgeToPega.java:223)

     [java] at com.pega.pegarules.boot.internal.extbridge.AppServerBridgeToPega.invokeMethod(AppServerBridgeToPega.java:272)

     [java] ... 1 more


Show Less
To see attachments, please log in.
Updates

Posted: 9 years ago
Posted: 13 Aug 2015 22:22 EDT
Celeste Dufresne (CelesteDufresne_GCS)
PEGA
Fellow, Technical Support, Cloud Service
Pegasystems Inc.
US

The pr_assembledclasses table existed in 6.1sp2 and should certainly exist in 7.1.8.  Is this an upgrade to a single or split schema? Assuming this is a split schema upgrade did you successfully migrate the rules tables from your existing 6.1sp2 single schema to the new rules schema BPMRULED and now you are running the rules schema upgrade?  Please post the complete upgrade log.

To see attachments, please log in.
Posted: 9 years ago
Posted: 13 Aug 2015 23:44 EDT
Bin Xu (GAVINHSU)
Mediatek Inc. China

Mediatek Inc. China
CN

Hi Celeste,

Thanks for your reply.

Yeah, we're upgrading our PRPC to split-schema database - it use to be single schema in version 6.1.

There're total 40 tables were migrated to new rules schema from old database, and no PR_ASSEMBLEDCLASSES was migrated.

Meanwhile, the migration was succeeded.

To see attachments, please log in.
Posted: 9 years ago
Posted: 13 Aug 2015 23:46 EDT
Bin Xu (GAVINHSU)
Mediatek Inc. China

Mediatek Inc. China
CN

Complete upgrade log as below.

Targets:Upgrade

Unable to locate tools.jar. Expected to find it in C:\Program Files\Java\jre6\lib\tools.jar

Buildfile: D:\Software\Install\Work\PRPC_V7.1.8\114819_Pega718\.\pegaGuiInstallerTemp\build.xml

SetupProperties:

Upgrade:

     [echo] calling upgrade ....

upgrade:

Initialization:

     [echo] Performing Upgrade Finalization

     [echo] Using logging configuration from: ./config/deploylogging.properties

   [delete] Deleting: D:\Software\Install\Work\PRPC_V7.1.8\114819_Pega718\scripts\resume.properties

   [delete] Deleting directory D:\Software\Install\Work\PRPC_V7.1.8\114819_Pega718\scripts\taskRuntimes

    [mkdir] Created dir: D:\Software\Install\Work\PRPC_V7.1.8\114819_Pega718\scripts\taskRuntimes

   [delete] Deleting: D:\Software\Install\Work\PRPC_V7.1.8\114819_Pega718\scripts\logs\Warnings.log

Reading Properties from : D:\Software\Install\Work\PRPC_V7.1.8\114819_Pega718\scripts/setupDatabase.properties

pega.jdbc.driver.jar=D:\Software\Install\Work\PRPC_V7.1.8\114819_Pega718\scripts\lib\db2jcc4.jar

pega.jdbc.driver.class=com.ibm.db2.jcc.DB2Driver

pega.database.type=udb

pega.jdbc.url=jdbc:db2:// Proprietary information hidden:50000/bpmd2:fullyMaterializeLobData=true;fullyMaterializeInputStreams=true;progressiveStreaming=2;useJDBC4ColumnNameAndLabelSemantics=2;

pega.jdbc.username=bpmruled

pega.jdbc.password=******

rules.schema.name=bpmruled

Show More

Complete upgrade log as below.

Targets:Upgrade

Unable to locate tools.jar. Expected to find it in C:\Program Files\Java\jre6\lib\tools.jar

Buildfile: D:\Software\Install\Work\PRPC_V7.1.8\114819_Pega718\.\pegaGuiInstallerTemp\build.xml

SetupProperties:

Upgrade:

     [echo] calling upgrade ....

upgrade:

Initialization:

     [echo] Performing Upgrade Finalization

     [echo] Using logging configuration from: ./config/deploylogging.properties

   [delete] Deleting: D:\Software\Install\Work\PRPC_V7.1.8\114819_Pega718\scripts\resume.properties

   [delete] Deleting directory D:\Software\Install\Work\PRPC_V7.1.8\114819_Pega718\scripts\taskRuntimes

    [mkdir] Created dir: D:\Software\Install\Work\PRPC_V7.1.8\114819_Pega718\scripts\taskRuntimes

   [delete] Deleting: D:\Software\Install\Work\PRPC_V7.1.8\114819_Pega718\scripts\logs\Warnings.log

Reading Properties from : D:\Software\Install\Work\PRPC_V7.1.8\114819_Pega718\scripts/setupDatabase.properties

pega.jdbc.driver.jar=D:\Software\Install\Work\PRPC_V7.1.8\114819_Pega718\scripts\lib\db2jcc4.jar

pega.jdbc.driver.class=com.ibm.db2.jcc.DB2Driver

pega.database.type=udb

pega.jdbc.url=jdbc:db2:// Proprietary information hidden:50000/bpmd2:fullyMaterializeLobData=true;fullyMaterializeInputStreams=true;progressiveStreaming=2;useJDBC4ColumnNameAndLabelSemantics=2;

pega.jdbc.username=bpmruled

pega.jdbc.password=******

rules.schema.name=bpmruled

data.schema.name=bpmruled

user.temp.dir=D:\PEGA718_Upgrade_Temp

pega.zos.properties=

bypass.pega.schema=true

run.assembler=

import.assembled.classes=true

system.name=pega

production.level=2

multitenant.system=false

update.existing.applications=false

import.codeset.name=Customer

import.codeset.version=06-01-01

build.conclusions=

[propertyfile] Creating new property file: D:\Software\Install\Work\PRPC_V7.1.8\114819_Pega718\scripts\resume.properties

[propertyfile] Updating property file: D:\Software\Install\Work\PRPC_V7.1.8\114819_Pega718\scripts\resume.properties

Found 7373888KB of free space on 'C:\Users\mtk40659\AppData\Local\Temp\'

     [echo] setting to generated ddl

     [echo] Driver Path: D:\Software\Install\Work\PRPC_V7.1.8\114819_Pega718\scripts\lib\db2jcc4.jar

    [mkdir] Created dir: C:\Users\mtk40659\AppData\Local\Temp\PegaInstallTemp-13-August-2015-15.58.45\load

    [mkdir] Created dir: C:\Users\mtk40659\AppData\Local\Temp\PegaInstallTemp-13-August-2015-15.58.45\pr_temp

    [touch] Creating D:\Software\Install\Work\PRPC_V7.1.8\114819_Pega718\scripts\logs\Warnings.log

     [echo] Using C:\Users\mtk40659\AppData\Local\Temp\/PegaInstallTemp-13-August-2015-15.58.45 for install scratch space...

    [unzip] Expanding: D:\Software\Install\Work\PRPC_V7.1.8\114819_Pega718\archives\prweb.war into C:\Users\mtk40659\AppData\Local\Temp\PegaInstallTemp-13-August-2015-15.58.45\load

    [unzip] Expanding: D:\Software\Install\Work\PRPC_V7.1.8\114819_Pega718\archives\pegadbinstall-classes.zip into C:\Users\mtk40659\AppData\Local\Temp\PegaInstallTemp-13-August-2015-15.58.45\load

     [copy] Copying 1 file to C:\Users\mtk40659\AppData\Local\Temp\PegaInstallTemp-13-August-2015-15.58.45\load\WEB-INF\classes

     [copy] Copying 1 file to C:\Users\mtk40659\AppData\Local\Temp\PegaInstallTemp-13-August-2015-15.58.45

Checking Configuration Files:

     [echo] Rules schema has been set to 'bpmruled'

     [echo] ***writing resume property upgrade.from.version=06-01-25 to file***

[propertyfile] Updating property file: D:\Software\Install\Work\PRPC_V7.1.8\114819_Pega718\scripts\resume.properties

     [echo] Upgrading from Pega-RULES product version 06-01-25

Processing Configuration Files:

[propertyfile] Creating new property file: C:\Users\mtk40659\AppData\Local\Temp\PegaInstallTemp-13-August-2015-15.58.45\prbootstrap.properties

[propertyfile] Updating property file: C:\Users\mtk40659\AppData\Local\Temp\PegaInstallTemp-13-August-2015-15.58.45\udb.conf

Configuration:

     [echo] Database Type: udb

     [echo] JDBC Driver JAR: D:\Software\Install\Work\PRPC_V7.1.8\114819_Pega718\scripts\lib\db2jcc4.jar

     [echo] Bootstrap Config: C:\Users\mtk40659\AppData\Local\Temp\/PegaInstallTemp-13-August-2015-15.58.45/prbootstrap.properties

     [echo] PegaRULES Config: C:\Users\mtk40659\AppData\Local\Temp\/PegaInstallTemp-13-August-2015-15.58.45/prconfig.xml

     [echo] PegaRULES Logging Config: C:\Users\mtk40659\AppData\Local\Temp\/PegaInstallTemp-13-August-2015-15.58.45/prlogging.xml

     [echo] Deployment Logging Config: ./config/deploylogging.properties

Cleanup RuleSets:

Generate RuleSet Cleanup Script:

     [echo] Generating Cleanup Script: D:\PEGA718_Upgrade_Temp/PRPC-RulesetCleanup.sql

     [java] Version size : 1

     [java] Error : The file could not be created due to an IO Error:

     [java] D:\PEGA718_Upgrade_Temp\PRPC-RulesetCleanup.sql (The system cannot find the path specified)

     [java] The script 'PRPC-RulesetCleanup.sql' has been created in the specified directory

Execute RuleSet Cleanup Script:

     [echo] File not found: D:\PEGA718_Upgrade_Temp/PRPC-RulesetCleanup.sql

     [echo] Skipping RuleSet Cleanup...

Generate Upgrade DDL:

     [echo] Bypassing DDL generation...

Schema Upgrade:

     [echo] Skipping automatic schema upgrade because bypass.pega.schema is set to true

Apply UDFs:

Apply UDFs Inner:

     [echo] ***setting resume checkpoint***

[propertyfile] Updating property file: D:\Software\Install\Work\PRPC_V7.1.8\114819_Pega718\scripts\resume.properties

Engine Load:

Engine Load Inner:

     [java] 2015-8-13 15:59:34 com.pega.pegarules.internal.bootstrap.PRBootstrapDataSource

     [java] 19830421: Loading bootstrap properties from file:///C:\Users\mtk40659\AppData\Local\Temp\/PegaInstallTemp-13-August-2015-15.58.45/prbootstrap.properties

     [java] 2015-8-13 15:59:34 com.pega.pegarules.internal.bootstrap.SettingReaderJNDI

     [java] 19830421: Could not find java:comp/env/prbootstrap/ in the local JNDI context, skipping prconfig setting lookup

     [java] 2015-8-13 15:59:34 com.pega.pegarules.internal.bootstrap.SettingReaderJNDI

     [java] 19830421: Could not find prbootstrap in the local JNDI context, skipping prconfig setting lookup

     [java] 2015-8-13 15:59:34 com.pega.pegarules.internal.bootstrap.PRBootstrap

     [java] 19830421: Engine schema defined in allclasses: null

     [java] 2015-8-13 15:59:34 com.pega.pegarules.internal.bootstrap.SettingReaderJNDI

     [java] 19830421: Could not find java:comp/env/prconfig/ in the local JNDI context, skipping prconfig setting lookup

     [java] 2015-8-13 15:59:34 com.pega.pegarules.internal.bootstrap.SettingReaderJNDI

     [java] 19830421: Could not find prconfig in the local JNDI context, skipping prconfig setting lookup

     [java] 2015-8-13 15:59:34 com.pega.pegarules.internal.bootstrap.PRBootstrap

     [java] 19830421: Engine classes schema: null

     [java] 2015-8-13 15:59:34 com.pega.pegarules.internal.bootstrap.PRBootstrap

     [java] 19830421: Assembled classes schema: null

     [java] 2015-8-13 17:48:26 com.pega.pegarules.internal.bootstrap.phase2.util.JarLoaderTool$ContentElement addUnique

     [java] 警告: Duplicate entry for prlogging.xml in jar prresources.jar (DIFFERENT)

     [java] 2015-8-13 15:59:36 com.pega.pegarules.internal.bootstrap.phase2.util.JarLoaderTool processOneJar

     [java] 信息:  Storing: base\activation-1.1.1.jar (because it is signed)

     [java] 2015-8-13 15:59:53 com.pega.pegarules.internal.bootstrap.phase2.util.JarLoaderTool processOneJar

     [java] 信息:  Storing: base\java6\bcmail-jdk15on-149.jar (because it is signed)

     [java] 2015-8-13 15:59:54 com.pega.pegarules.internal.bootstrap.phase2.util.JarLoaderTool processOneJar

     [java] 信息:  Storing: base\java6\bcpkix-jdk15on-149.jar (because it is signed)

     [java] 2015-8-13 15:59:56 com.pega.pegarules.internal.bootstrap.phase2.util.JarLoaderTool processOneJar

     [java] 信息:  Storing: base\java6\bcprov-jdk15on-149.jar (because it is signed)

     [java] 2015-8-13 16:02:28 com.pega.pegarules.internal.bootstrap.phase2.util.JarLoaderTool processOneJar

     [java] 信息:  Storing: avalon-framework-4.0-dsm.jar (because it must be extracted)

     [java] 2015-8-13 16:02:55 com.pega.pegarules.internal.bootstrap.phase2.util.JarLoaderTool processOneJar

     [java] 信息:  Storing: batik-1.5-fop-0.20-5-dsm.jar (because it must be extracted)

     [java] 2015-8-13 16:06:32 com.pega.pegarules.internal.bootstrap.phase2.util.JarLoaderTool processOneJar

     [java] 信息:  Storing: chemistry-opencmis-commons-impl-0.12.0.jar (because it must be extracted)

     [java] 2015-8-13 16:20:52 com.pega.pegarules.internal.bootstrap.phase2.util.JarLoaderTool processOneJar

     [java] 信息:  Storing: fop-0.20.5-dsm.jar (because it must be extracted)

     [java] 2015-8-13 16:42:27 com.pega.pegarules.internal.bootstrap.phase2.util.JarLoaderTool processOneJar

     [java] 信息:  Storing: pad-reporting-7.1.8.jar (because it must be extracted)

     [java] 2015-8-13 16:47:16 com.pega.pegarules.internal.bootstrap.phase2.util.JarLoaderTool processOneJar

     [java] 信息:  Storing: praddressing-1.5.4.jar (because it must be extracted)

     [java] 2015-8-13 16:48:33 com.pega.pegarules.internal.bootstrap.phase2.util.JarLoaderTool processOneJar

     [java] 信息:  Storing: praxiom-1.2.13.jar (because it must be extracted)

     [java] 2015-8-13 16:49:25 com.pega.pegarules.internal.bootstrap.phase2.util.JarLoaderTool processOneJar

     [java] 信息:  Storing: praxis2-1.6.2.jar (because it must be extracted)

     [java] 2015-8-13 17:02:27 com.pega.pegarules.internal.bootstrap.phase2.util.JarLoaderTool processOneJar

     [java] 信息:  Storing: prhazelcast-3.4.1.jar (because it must be extracted)

     [java] 2015-8-13 17:02:39 com.pega.pegarules.internal.bootstrap.phase2.util.JarLoaderTool processOneJar

     [java] 信息:  Storing: prhttpcomponents-client-4.1.2.jar (because it must be extracted)

     [java] 2015-8-13 17:02:40 com.pega.pegarules.internal.bootstrap.phase2.util.JarLoaderTool processOneJar

     [java] 信息:  Storing: prhttpcomponents-core-4.1.3.jar (because it must be extracted)

     [java] 2015-8-13 17:09:36 com.pega.pegarules.internal.bootstrap.phase2.util.JarLoaderTool processOneJar

     [java] 信息:  Storing: prneethi-3.0.2.jar (because it must be extracted)

     [java] 2015-8-13 17:48:24 com.pega.pegarules.internal.bootstrap.phase2.util.JarLoaderTool processOneJar

     [java] 信息:  Storing: prrahas-module-1.6.2.jar (because it must be extracted)

     [java] 2015-8-13 17:48:24 com.pega.pegarules.internal.bootstrap.phase2.util.JarLoaderTool processOneJar

     [java] 信息:  Storing: prrampart-core-1.6.2.jar (because it must be extracted)

     [java] 2015-8-13 17:48:25 com.pega.pegarules.internal.bootstrap.phase2.util.JarLoaderTool processOneJar

     [java] 信息:  Storing: prrampart-module-1.6.2.jar (because it must be extracted)

     [java] 2015-8-13 17:48:26 com.pega.pegarules.internal.bootstrap.phase2.util.JarLoaderTool processOneJar

     [java] 信息:  Loading: prresources.jar (no signature data exists in database)

     [java] 2015-8-13 17:48:26 com.pega.pegarules.internal.bootstrap.phase2.util.JarLoaderTool processOneJar

     [java] 信息: Omitting file: prresources.jar /prlogging.xml

     [java] 2015-8-13 17:52:10 com.pega.pegarules.internal.bootstrap.phase2.util.JarLoaderTool processOneJar

     [java] 信息:  Storing: saxon9he.jar (because it is signed)

     [java] 2015-8-13 18:11:43 com.pega.pegarules.internal.bootstrap.phase2.util.JarLoaderTool reportOutput

     [java] 信息:              Count of jar files: 270

     [java] 2015-8-13 18:11:43 com.pega.pegarules.internal.bootstrap.phase2.util.JarLoaderTool reportOutput

     [java] 信息:       Count of jar files loaded: 270

     [java] 2015-8-13 18:11:43 com.pega.pegarules.internal.bootstrap.phase2.util.JarLoaderTool reportOutput

     [java] 信息:      Count of jar files skipped: 0

     [java] 2015-8-13 18:11:43 com.pega.pegarules.internal.bootstrap.phase2.util.JarLoaderTool reportOutput

     [java] 信息:               Count of packages: 5732

     [java] 2015-8-13 18:11:43 com.pega.pegarules.internal.bootstrap.phase2.util.JarLoaderTool reportOutput

     [java] 信息:                Count of classes: 91915

     [java] 2015-8-13 18:11:43 com.pega.pegarules.internal.bootstrap.phase2.util.JarLoaderTool reportOutput

     [java] 信息:        Count of other resources: 18835

     [java] 2015-8-13 18:11:43 com.pega.pegarules.internal.bootstrap.phase2.util.JarLoaderTool reportOutput

     [java] 信息:                 = Total entries: 110750

     [java] 2015-8-13 18:11:43 com.pega.pegarules.internal.bootstrap.phase2.util.JarLoaderTool reportOutput

     [java] 信息:          Count resources loaded: 110729

     [java] 2015-8-13 18:11:43 com.pega.pegarules.internal.bootstrap.phase2.util.JarLoaderTool reportOutput

     [java] 信息:      Count resources not loaded: 1

     [java] 2015-8-13 18:11:43 com.pega.pegarules.internal.bootstrap.phase2.util.JarLoaderTool reportOutput

     [java] 信息:               Count jars stored: 20

     [java] 2015-8-13 18:11:43 com.pega.pegarules.internal.bootstrap.phase2.util.JarLoaderTool reportOutput

     [java] 信息:               Uncompressed size: 391605190

     [java] 2015-8-13 18:11:43 com.pega.pegarules.internal.bootstrap.phase2.util.JarLoaderTool reportOutput

     [java] 信息:             Jar compressed size: 150492055 -> 38.4295353695389% of uncompressed size

     [java] 2015-8-13 18:11:43 com.pega.pegarules.internal.bootstrap.phase2.util.JarLoaderTool reportOutput

     [java] 信息:           Total processing time: 7926.571 seconds

     [java] 2015-8-13 18:11:43 com.pega.pegarules.internal.bootstrap.phase2.util.JarLoaderTool reportOutput

     [java] 信息:            Read entry data time: 10.743 seconds

     [java] 2015-8-13 18:11:43 com.pega.pegarules.internal.bootstrap.phase2.util.JarLoaderTool reportOutput

     [java] 信息:            Longest package name: com/pega/elasticsearch/common/jackson/dataformat/yaml/snakeyaml/external/com/google/gdata/util/common/base (106)

     [java] 2015-8-13 18:11:43 com.pega.pegarules.internal.bootstrap.phase2.util.JarLoaderTool reportOutput

     [java] 信息:              Longest class name: OldRuleResolver$RuleResolutionSecondLevelCandidatesForCircumstancesMap$CandidateListForCircumstance.class (105)

     [echo] ***setting resume checkpoint***

[propertyfile] Updating property file: D:\Software\Install\Work\PRPC_V7.1.8\114819_Pega718\scripts\resume.properties

Reorganize Database Indexes Preupgrade:

_getSystemName:

_findSystemName:

     [echo] select max(s.pySystemName) from BPMRULED.pr_data_admin s inner join BPMRULED.pr_data_admin r    on s.pySystemName = r.pySystemName    where s.pxobjclass = 'Data-Admin-System' and r.pxObjClass = 'Data-Admin-Requestor'

     [echo] System Name: prpc

  [replace] Replaced 1 occurrences in 1 files.

     [echo] ***setting resume checkpoint***

[propertyfile] Updating property file: D:\Software\Install\Work\PRPC_V7.1.8\114819_Pega718\scripts\resume.properties

_importPreupgrade:

  [replace] Replaced 1 occurrences in 1 files.

     [echo] about to Import Rules from : D:\Software\Install\Work\PRPC_V7.1.8\114819_Pega718\scripts/../rules//preupgrade.jar ...

     [java] 2015-8-13 18:11:45 com.pega.pegarules.internal.bootstrap.PRBootstrapDataSource

     [java] 19830421: Loading bootstrap properties from file:///C:\Users\mtk40659\AppData\Local\Temp\/PegaInstallTemp-13-August-2015-15.58.45/prbootstrap.properties

     [java] 2015-8-13 18:11:45 com.pega.pegarules.internal.bootstrap.SettingReaderJNDI

     [java] 19830421: Could not find java:comp/env/prbootstrap/ in the local JNDI context, skipping prconfig setting lookup

     [java] 2015-8-13 18:11:45 com.pega.pegarules.internal.bootstrap.SettingReaderJNDI

     [java] 19830421: Could not find prbootstrap in the local JNDI context, skipping prconfig setting lookup

     [java] 2015-8-13 18:11:45 com.pega.pegarules.internal.bootstrap.PRBootstrap

     [java] 19830421: Engine schema defined in allclasses: null

     [java] 2015-8-13 18:11:45 com.pega.pegarules.internal.bootstrap.SettingReaderJNDI

     [java] 19830421: Could not find java:comp/env/prconfig/ in the local JNDI context, skipping prconfig setting lookup

     [java] 2015-8-13 18:11:45 com.pega.pegarules.internal.bootstrap.SettingReaderJNDI

     [java] 19830421: Could not find prconfig in the local JNDI context, skipping prconfig setting lookup

     [java] 2015-8-13 18:11:45 com.pega.pegarules.internal.bootstrap.PRBootstrap

     [java] 19830421: Engine classes schema: null

     [java] 2015-8-13 18:11:45 com.pega.pegarules.internal.bootstrap.PRBootstrap

     [java] 19830421: Assembled classes schema: null

     [java] 2015-8-13 18:11:45 com.pega.pegarules.internal.bootstrap.PRBootstrap

     [java] 19830421:

     [java] 2015-8-13 18:11:45 com.pega.pegarules.internal.bootstrap.PRBootstrap

     [java] 19830421: *=================================================================*

     [java] 2015-8-13 18:11:45 com.pega.pegarules.internal.bootstrap.PRBootstrap

     [java] 19830421: prbootstrap.properties entry "initialization.settingsource=file"; note that

     [java] 2015-8-13 18:11:45 com.pega.pegarules.internal.bootstrap.PRBootstrap

     [java] 19830421: this excludes use of entries in Data-Admin-System-Settings as prbootstrap settings

     [java] 2015-8-13 18:11:45 com.pega.pegarules.internal.bootstrap.PRBootstrap

     [java] 19830421: *=================================================================*

     [java]

     [java] 2015-8-13 18:11:45 com.pega.pegarules.internal.bootstrap.PRMiniLoader

     [java] 19830421: Will load phase 2 bootstrap from Pega-EngineCode:07-10-17

     [java] Warn - NonVersionedJdbcJarReader - unable to load classes from the database: DB2 SQL Error: SQLCODE=-204, SQLSTATE=42704, SQLERRMC=BPMRULED.PR_ASSEMBLEDCLASSES, DRIVER=4.11.77

     [java] 2015-8-13 18:12:33 com.pega.pegarules.internal.bootstrap.phase2.PRBootstrapImpl

     [java] 19830421: PegaRULES classes will be loaded from jar files (and NOT the database)

     [java] 2015-8-13 18:12:35 com.pega.pegarules.internal.bootstrap.phase2.PRBootstrapImpl

     [java] 严重: Error initializing PRAppLoader

     [java] java.lang.ClassNotFoundException: com.pega.pegarules.bootstrap.loader.PRAppLoader

     [java] at com.pega.pegarules.internal.bootstrap.phase2.PRBaseLoader.findClass(PRBaseLoader.java:312)

     [java] at java.lang.ClassLoader.loadClass(Unknown Source)

     [java] at com.pega.pegarules.internal.bootstrap.phase2.PRBaseLoader.loadClass(PRBaseLoader.java:237)

     [java] at java.lang.ClassLoader.loadClass(Unknown Source)

     [java] at java.lang.Class.forName0(Native Method)

     [java] at java.lang.Class.forName(Unknown Source)

     [java] at com.pega.pegarules.internal.bootstrap.phase2.PRBootstrapImpl.initializeAppLoader(PRBootstrapImpl.java:1134)

     [java] at com.pega.pegarules.internal.bootstrap.phase2.PRBootstrapImpl._finishInitialization_privact(PRBootstrapImpl.java:250)

     [java] at com.pega.pegarules.internal.bootstrap.phase2.PRBootstrapImpl.finishInitialization(PRBootstrapImpl.java:122)

     [java] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

     [java] at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)

     [java] at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)

     [java] at java.lang.reflect.Method.invoke(Unknown Source)

     [java] at com.pega.pegarules.internal.bootstrap.PRBootstrap.checkForStartup(PRBootstrap.java:682)

     [java] at com.pega.pegarules.internal.bootstrap.PRBootstrap.invokeMethodPropagatingThrowable(PRBootstrap.java:405)

     [java] at com.pega.pegarules.boot.internal.extbridge.AppServerBridgeToPega.invokeMethodPropagatingThrowable(AppServerBridgeToPega.java:223)

     [java] at com.pega.pegarules.boot.internal.extbridge.AppServerBridgeToPega.invokeMethod(AppServerBridgeToPega.java:272)

     [java] at com.pega.pegarules.pub.PegaRULES.main(PegaRULES.java:85)

     [java] 2015-8-13 18:12:35 com.pega.pegarules.internal.bootstrap.PRBootstrap

     [java] 19830421:

     [java] ============ PegaRULES Bootstrap Configuration ============

     [java]            Date: Thu Aug 13 18:12:35 CST 2015

     [java]    Java Version: Sun Microsystems Inc. 1.6.0_30

     [java]   Configuration: file:/C:/Users/mtk40659/AppData/Local/Temp//PegaInstallTemp-13-August-2015-15.58.45/prbootstrap.properties

     [java] Pega-EngineCode: 07-10-17

     [java]     JDBC Driver: com.ibm.db2.jcc.DB2Driver

     [java]        JDBC URL: jdbc:db2:// Proprietary information hidden:50000/bpmd2:fullyMaterializeLobData=true;fullyMaterializeInputStreams=true;progressiveStreaming=2;useJDBC4ColumnNameAndLabelSemantics=2;

     [java]       JDBC User: bpmruled

     [java]        Database: DB2/LINUXX8664 SQL09073

     [java]          Driver: IBM Data Server Driver for JDBC and SQLJ 4.11.77

     [java] Active CodeSets: pega-enginecode:07-10-17 at (latest patch)

     [java]

     [java] =============== End Bootstrap Configuration ===============

     [java]

     [java] 2015-8-13 18:12:35 com.pega.pegarules.boot.internal.extbridge.AppServerBridgeToPega

     [java] 严重: Problem during method invocation (main)

     [java] java.lang.RuntimeException: PRAppLoader was not properly initialized, unable to load class com.pega.pegarules.deploy.internal.util.ImportImpl

     [java] at com.pega.pegarules.internal.bootstrap.PRBootstrap.getImplementationOf(PRBootstrap.java:205)

     [java] at com.pega.pegarules.internal.bootstrap.PRBootstrap.getEntry(PRBootstrap.java:321)

     [java] at com.pega.pegarules.internal.bootstrap.PRBootstrap.getMethod(PRBootstrap.java:301)

     [java] at com.pega.pegarules.internal.bootstrap.PRBootstrap.invokeMethodPropagatingThrowable(PRBootstrap.java:406)

     [java] at com.pega.pegarules.boot.internal.extbridge.AppServerBridgeToPega.invokeMethodPropagatingThrowable(AppServerBridgeToPega.java:223)

     [java] at com.pega.pegarules.boot.internal.extbridge.AppServerBridgeToPega.invokeMethod(AppServerBridgeToPega.java:272)

     [java] at com.pega.pegarules.pub.PegaRULES.main(PegaRULES.java:85)

     [java] Exception in thread "main" java.lang.RuntimeException: Problem during method invocation (main)

     [java] at com.pega.pegarules.boot.internal.extbridge.AppServerBridgeToPega.invokeMethod(AppServerBridgeToPega.java:278)

     [java] at com.pega.pegarules.pub.PegaRULES.main(PegaRULES.java:85)

     [java] Caused by: java.lang.RuntimeException: PRAppLoader was not properly initialized, unable to load class com.pega.pegarules.deploy.internal.util.ImportImpl

     [java] at com.pega.pegarules.internal.bootstrap.PRBootstrap.getImplementationOf(PRBootstrap.java:205)

     [java] at com.pega.pegarules.internal.bootstrap.PRBootstrap.getEntry(PRBootstrap.java:321)

     [java] at com.pega.pegarules.internal.bootstrap.PRBootstrap.getMethod(PRBootstrap.java:301)

     [java] at com.pega.pegarules.internal.bootstrap.PRBootstrap.invokeMethodPropagatingThrowable(PRBootstrap.java:406)

     [java] at com.pega.pegarules.boot.internal.extbridge.AppServerBridgeToPega.invokeMethodPropagatingThrowable(AppServerBridgeToPega.java:223)

     [java] at com.pega.pegarules.boot.internal.extbridge.AppServerBridgeToPega.invokeMethod(AppServerBridgeToPega.java:272)

     [java] ... 1 more

BUILD FAILED

D:\Software\Install\Work\PRPC_V7.1.8\114819_Pega718\pegaGuiInstallerTemp\build.xml:83: The following error occurred while executing this line:

D:\Software\Install\Work\PRPC_V7.1.8\114819_Pega718\scripts\setupDatabase.xml:317: The following error occurred while executing this line:

D:\Software\Install\Work\PRPC_V7.1.8\114819_Pega718\scripts\setupDatabase.xml:2570: Java returned: 1

Total time: 133 minutes 51 seconds


Show Less
To see attachments, please log in.
Posted: 9 years ago
Posted: 14 Aug 2015 0:08 EDT
Bin Xu (GAVINHSU)
Mediatek Inc. China

Mediatek Inc. China
CN

Migration tables list (from migration log):

Wed Aug 12 20:38:58 CST 2015 (INFO): 

Wed Aug 12 20:38:58 CST 2015 (INFO): PegaBulkMover: Table + PR_SYS_HOTFIX_EVENTS Load completed 0 Rows loaded

Wed Aug 12 20:38:58 CST 2015 (INFO): 

Wed Aug 12 20:38:58 CST 2015 (INFO): Processed 40 of 40 table(s)

Wed Aug 12 20:38:58 CST 2015 (INFO): 

Wed Aug 12 20:38:58 CST 2015 (INFO): Ending Time: Wed Aug 12 20:38:58 CST 2015

Wed Aug 12 20:38:58 CST 2015 (INFO): 

Wed Aug 12 20:38:58 CST 2015 (INFO): Elapsed Time: 33 hour(s), 25 minute(s), 21 second(s).

Tables:

PR_SYS_DECCHG

PR4_RULE_LIBRARY

PR_INDEX_REFERENCE

PR4_RULE_RULESET

PR_APP_BRANCH_IDX

PR4_FIELDVALUE

PR4_RULE_FLOW

PR_CHANGELOG

PR_ENGINECLASSES

PR4_RULE_USECASE

PR_DATA_ADMIN_PRODUCT

PR4_RULE_REQUIREMENT

PR_DATA_RULE_APPMETADATA

PR_SYS_HOTFIX_EVENTS

PR4_RULE

PR_DATA_SCANNER

PR_INDEX_CSS

PR4_RULE_VW

PR_INDEX_PRIVILEGE

PR_SYS_CONTEXT

PR4_RULE_TESTCASE

PR4_RULE_DECLAREPAGES

PR4_RULE_PROPERTY

PC_INDEX_FLOWREF

PR4_RULE_AUTOTEST

PR_INDEX_DATASOURCES

PR_LINK_USECASE

PR4_RULE_FILE_BINARY

PR4_BASE

PR4_RULE_SHORTCUT

PR_INDEX_RULE_AGENTS

PR_INDEX_CUSTOMFIELDS

PR4_RULE_FILE

PR_INDEX_WARNINGS

PR4_RULE_SYSGEN

PR4_RULE_MESSAGE

PR_REFERENCE_PAGE

PR_INDEX_CIRCUMSTANCE_DEF

Show More

Migration tables list (from migration log):

Wed Aug 12 20:38:58 CST 2015 (INFO): 

Wed Aug 12 20:38:58 CST 2015 (INFO): PegaBulkMover: Table + PR_SYS_HOTFIX_EVENTS Load completed 0 Rows loaded

Wed Aug 12 20:38:58 CST 2015 (INFO): 

Wed Aug 12 20:38:58 CST 2015 (INFO): Processed 40 of 40 table(s)

Wed Aug 12 20:38:58 CST 2015 (INFO): 

Wed Aug 12 20:38:58 CST 2015 (INFO): Ending Time: Wed Aug 12 20:38:58 CST 2015

Wed Aug 12 20:38:58 CST 2015 (INFO): 

Wed Aug 12 20:38:58 CST 2015 (INFO): Elapsed Time: 33 hour(s), 25 minute(s), 21 second(s).

Tables:

PR_SYS_DECCHG

PR4_RULE_LIBRARY

PR_INDEX_REFERENCE

PR4_RULE_RULESET

PR_APP_BRANCH_IDX

PR4_FIELDVALUE

PR4_RULE_FLOW

PR_CHANGELOG

PR_ENGINECLASSES

PR4_RULE_USECASE

PR_DATA_ADMIN_PRODUCT

PR4_RULE_REQUIREMENT

PR_DATA_RULE_APPMETADATA

PR_SYS_HOTFIX_EVENTS

PR4_RULE

PR_DATA_SCANNER

PR_INDEX_CSS

PR4_RULE_VW

PR_INDEX_PRIVILEGE

PR_SYS_CONTEXT

PR4_RULE_TESTCASE

PR4_RULE_DECLAREPAGES

PR4_RULE_PROPERTY

PC_INDEX_FLOWREF

PR4_RULE_AUTOTEST

PR_INDEX_DATASOURCES

PR_LINK_USECASE

PR4_RULE_FILE_BINARY

PR4_BASE

PR4_RULE_SHORTCUT

PR_INDEX_RULE_AGENTS

PR_INDEX_CUSTOMFIELDS

PR4_RULE_FILE

PR_INDEX_WARNINGS

PR4_RULE_SYSGEN

PR4_RULE_MESSAGE

PR_REFERENCE_PAGE

PR_INDEX_CIRCUMSTANCE_DEF

PR4_RULE_DELEGATIONCONFIG


Show Less
To see attachments, please log in.
Posted: 9 years ago
Posted: 14 Aug 2015 7:52 EDT
Celeste Dufresne (CelesteDufresne_GCS)
PEGA
Fellow, Technical Support, Cloud Service
Pegasystems Inc.
US

In looking at your upgrade log you have bypass.pega.schema=true.  Did you genereate and apply the upgrade ddl after the migration and before starting to run this upgrade?  The migrate script just copies the pr_data_admin table and the needed rules tables to the new schema.  The rules upgrade is going to make the schema changes needed to upgrade to 7.1.8 and then upgrade the rules schema.  Set bypass.pega.schema=false if you have not run the generateddl script and applied it and then restart this upgrade.

To see attachments, please log in.
Posted: 9 years ago
Updated: 9 years ago
Posted: 19 Aug 2015 7:51 EDT
Updated: 19 Aug 2015 7:52 EDT
Tarun Sipani (sipat) Senior Technical Support Engineer
Pegasystems Inc.
JP

Hi Celeste,

Both with and without bypass.pega.schema=true has been tried with no  benefits.

Now we are trying the command line :upgrade.bat: --rulesShecma, which qives  a tablespace error and we’re trying to fix it now.

After making few changes to the setupDatabase.properties [PFA ], when I ran upgrade.bat –rulesSchema,

I’ve got an error as below; and unfortunately, this is the only message I can find from the log file.

Buildfile: build.xml does not exist!

Build failed––––

Exiting with Error

Requesting for further steps to make the upgrad.bat, work as expected, which is presently existing without being able to locate build.xml

Also , any suggestion for trying a Split schema at this stage are welcome.

Note: Customer does not have a Applicaiton Server, only trying to upgrade the DB.

Kindly share any insights/best-practices/experiences so upgrades to ML 8.

Regards,

Tarun Sipani

To see attachments, please log in.
Posted: 9 years ago
Posted: 19 Aug 2015 8:12 EDT
Celeste Dufresne (CelesteDufresne_GCS)
PEGA
Fellow, Technical Support, Cloud Service
Pegasystems Inc.
US

In your setupDatabase.properties file change this property so that it is not set.

From:

# Generate schema will be skipped if this property is set to true

# Note: Leave this property blank if you need to generate the schema

bypass.pega.schema=false

To:

bypass.pega.schema=

Please post the logs from when the upgrade script with bypass.pega.schema not set to true.  You do not need to pass any parameters on the command line for the rules schema upgrade if you have populated the setupDatabase.properties file.

You would just run the command like this:

upgrade.bat

To see attachments, please log in.
Posted: 9 years ago
Posted: 19 Aug 2015 23:07 EDT
Bin Xu (GAVINHSU)
Mediatek Inc. China

Mediatek Inc. China
CN

Hi Celeste,

Thanks for your answer.

We'll try again with "bypass.pega.schema=", and will post the logs here.

However, we have ran the upgrade.sh successfully with "bypass.pega.schema=true", although there're 149 extra tables was created - originally, there're only 40 tables was migrated from old database to new rules schema.

We're wondering that what is the correct number of tables should be existed in the RULES schema?

How can we upgrade successfully without creating those extra tables?

We also found that some of those created extra tables have data stored in; so, can those tables be dropped after the upgrade?

To see attachments, please log in.
Posted: 9 years ago
Updated: 9 years ago
Posted: 20 Aug 2015 21:19 EDT
Updated: 20 Aug 2015 22:38 EDT
Tarun Sipani (sipat) Senior Technical Support Engineer
Pegasystems Inc.
JP

Dear SME,

Customer is able to used the "upgrade" commands.

Now the only question, is the missing clarity around :

1) Right no of tables, list of them, to compare and determine whether a success/failure situation has been achieved.

The Customer end is pressing to quickly determine, any such information from the SME would be hugely appreciated.

Thanks and Regards,

Tarun Sipani

---------------------------

Adding the upgrade logs tried, with “bypass.pega.schema=” , kindly advise , how to validate this as success and expected nos of tables

To see attachments, please log in.
Posted: 9 years ago
Posted: 20 Aug 2015 22:16 EDT
Celeste Dufresne (CelesteDufresne_GCS)
PEGA
Fellow, Technical Support, Cloud Service
Pegasystems Inc.
US

So the migrate to the new rules schema and the upgrade of the rules schema is completed.  Has the rest of the upgrade been completed (second pass of migrate script, upgrade of data schema, running of additional scripts since upgrading from pre 62, etc) or are you just looking to verify where things stand at the end of the upgrade of the rules schema step?  If you are just trying to verify that the upgrade of the rules schema has completed successfully before moving on to the rest of the upgrade comparing a list of tables is not what you should be doing.  You should be looking at the upgrade log to make sure that all of the tasks completed without issue.  If you post the log here I can look at it if you want. 

To see attachments, please log in.
Posted: 9 years ago
Updated: 9 years ago
Posted: 20 Aug 2015 22:43 EDT
Updated: 20 Aug 2015 22:46 EDT
Tarun Sipani (sipat) Senior Technical Support Engineer
Pegasystems Inc.
JP

Hi Celeste,

Very sorry for the trouble, pfa the upgrade logs.

Do let me know if any other detail is required.

Thanks and Kind Regards,

Tarun Sipani

To see attachments, please log in.
Posted: 9 years ago
Updated: 9 years ago
Posted: 20 Aug 2015 23:20 EDT
Updated: 21 Aug 2015 1:37 EDT
Tarun Sipani (sipat) Senior Technical Support Engineer
Pegasystems Inc.
JP

Hi Celeste,

1) Yes we request you to please have a look in the upgrade logs attached.

Thank you very much for reminding about the other steps for this 6.1 SP2 to ML8 upgrade [I am referring Pega718_UpgradeGuide]

Request you to please let us know the part in the log indicator-of-sucess, if possible.

(second pass of migrate script, upgrade of data schema, running of additional scripts since upgrading from pre 62, etc)

  I could find :

~cleanup.sh

~ResourceKit\AdditionalUpgradeScripts [upgrade query on specific DB]

2) Is there any additional action to be taken apart from the above.

P.S.

Presently, this is single schema [Rules and Data].

To see attachments, please log in.
Posted: 9 years ago
Posted: 21 Aug 2015 7:51 EDT
Celeste Dufresne (CelesteDufresne_GCS)
PEGA
Fellow, Technical Support, Cloud Service
Pegasystems Inc.
US

I am a little confused by these log files as to what you have run and why.   These are in general the steps that you need to run to upgrade from 6.1sp2 to 7.1.8 split schema.  In the end you will have a new rules schema and what was your combined 6.1sp2 schema will be the 7.1 data schema.  I'm assuming that you are following the upgrade to split schema with 1 database process from the upgrade guide.

1.  Run migrate script to clone rules tables from combined 61sp2 schema (Combined61sp2) in new rules schema (NewRules)

2.  Run upgrade script to upgrade new rules schema (NewRules).  As part of this step dummy data tables will be added to rules schema.

3.  Run migrate script (with target dataschema=Combined61sp2, target rulesschema=NewRules) to generate rules schema objects, grants between schemas

4.  Run upgrade script with dataOnly option to upgrade dataSchema.  RulesSchema=NewRules, DataSchema=Combined61sp2

5.  Post upgrade steps include running additional scripts since you upgraded from pre-62, setting up app server, running optimize schema tool to clean up dummy data tables from NewRules schema and old rules tables from Combined61sp2 schema which is your new data schema, etc.

Show More

I am a little confused by these log files as to what you have run and why.   These are in general the steps that you need to run to upgrade from 6.1sp2 to 7.1.8 split schema.  In the end you will have a new rules schema and what was your combined 6.1sp2 schema will be the 7.1 data schema.  I'm assuming that you are following the upgrade to split schema with 1 database process from the upgrade guide.

1.  Run migrate script to clone rules tables from combined 61sp2 schema (Combined61sp2) in new rules schema (NewRules)

2.  Run upgrade script to upgrade new rules schema (NewRules).  As part of this step dummy data tables will be added to rules schema.

3.  Run migrate script (with target dataschema=Combined61sp2, target rulesschema=NewRules) to generate rules schema objects, grants between schemas

4.  Run upgrade script with dataOnly option to upgrade dataSchema.  RulesSchema=NewRules, DataSchema=Combined61sp2

5.  Post upgrade steps include running additional scripts since you upgraded from pre-62, setting up app server, running optimize schema tool to clean up dummy data tables from NewRules schema and old rules tables from Combined61sp2 schema which is your new data schema, etc.

From the log labeled rule_upgrade0819.log it looks like that covers step #2.  There seems to be an issue with badtablemapping with the pr_sys_statusnodes table but for the most part this upgrade completed successfully.  However then this data_upgrade_0821.log I am not at all sure what you were attempting to do.  It seems like you ran the upgrade script again but only set the data.schema.name=your new rules schema and then you ran the upgrade script a third time with both data and rules schema set.   Did you ever run the second pass of the migrate script (step #3)? We can probably fix this upgrade from the point where you are at now without too much difficultly instead of restarting from the beginning but I want to be sure that you understand what steps you should be following and if something is not clear in the Upgrade guide that will get that corrected.


Show Less
To see attachments, please log in.
Posted: 9 years ago
Updated: 9 years ago
Posted: 21 Aug 2015 9:27 EDT
Updated: 21 Aug 2015 9:29 EDT
Tarun Sipani (sipat) Senior Technical Support Engineer
Pegasystems Inc.
JP

Hi Celeste,

We will work with customer to confirm the intend/actions-done.

Then list down the next plan for restoration / complete upgrade , for your review.

Your help on this is highly helpful.

Thanks and regards

Tarun

To see attachments, please log in.
Posted: 9 years ago
Updated: 9 years ago
Posted: 24 Aug 2015 2:24 EDT
Updated: 24 Aug 2015 2:30 EDT
Bin Xu (GAVINHSU)
Mediatek Inc. China

Mediatek Inc. China
CN

Hi Celeste,


What we're planning to do the upgrade is:

1.  Run migrate script to clone rules tables from combined 61sp2 schema (db2bpmd) in new rules schema (bpmruled)

2.  Run upgrade script to upgrade new rules schema (bpmruled).

O3.  Run migrate script (with target dataschema=Combined61sp2, target rulesschema=NewRules) to generate rules schema objects, grants between schemas

3.  Run upgrade script with dataOnly option to upgrade dataSchema.  RulesSchema=bpmruled, DataSchema=db2bpmd

...

The reason that original step O3 wasn't ran is we thought we can use upgraded rules schema (bpmruled) directly, there seems no need to migrate upgraded rules schema back.

Anyway, we have all the database backup, so that the upgrade can be rollback anytime without re-run the previous steps.

We're gonna to run the upgrade again exactly follow your instruction, if the step O3 is required.

But, we still don't see what is the necessary of running step O3 - why cannot use the upgraded schema directly?

To see attachments, please log in.
Posted: 9 years ago
Posted: 24 Aug 2015 15:12 EDT
Tarun Sipani (sipat) Senior Technical Support Engineer
Pegasystems Inc.
JP

Hi Celeste,

Would you kindly comment on the need of 2+2 times upgrades/migrates using the upgrade.sh and migrate.sh .

IMHO we are delliting the previous older rules post completing.

The customer is been given quotes from the upgrade guide, but still not satisfied.

Also, what is final proof of completion of activity.

Sorry for the too many questions , but please if you could explain the behind the sceens needs for it.

Would be much appreciated.

Thanking again,

Tarun Sipani

To see attachments, please log in.
Posted: 9 years ago
Posted: 30 Aug 2015 22:16 EDT
Celeste Dufresne (CelesteDufresne_GCS)
PEGA
Fellow, Technical Support, Cloud Service
Pegasystems Inc.
US

Sorry I was away last week.   Yes, you do need to run the migrate script a second time as I said previously, regardless of whether you are using the upgraded schema directly or migrating the upgrade back to a new schema.  In your case you are want to use the upgraded rules schema directly so you don't need to migrate that schema back but you need to create the rules schema objects and grants between this new rules schema and what will become your data schema.

Run migrate script (with target RulesSchema=bpmruled, DataSchema=db2bpmd) to generate rules schema objects, grants between schemas.  The first six flags in the migrateSystem.properties file will be set to false and just these last 2 flags will be set to true for this pass.

### 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=true
#Apply the rules schema objects (views, triggers, procedures, functions) to pega.target.rules.schema.
pega.rules.objects.apply=true

To see attachments, please log in.
Posted: 9 years ago
Updated: 9 years ago
Posted: 31 Aug 2015 6:50 EDT
Updated: 31 Aug 2015 6:51 EDT
Tarun Sipani (sipat) Senior Technical Support Engineer
Pegasystems Inc.
JP

Hi Celeste,

Thank you for your help on this.

As advised we are trying to migrate.sh with the attached property file. [Attachment-1]

When I execute migrate.sh to migrate upgraded rules schema to new rules schema (from UPGRADE to NEW RULES schema), I’ve got error message as below. [Attach -2]

2015-08-27 17:00:33,754 ( SQLLoader)    INFO - CREATE TABLE BPMRULED.PR_DATA_PRODUCTS

2015-08-27 17:00:33,761 ( SQLLoader) WARNING - Failed to execute SQL in file udb03150.sql

com.ibm.db2.jcc.am.SqlSyntaxErrorException: DB2 SQL Error: SQLCODE=-601, SQLSTATE=42710, SQLERRMC=BPMRULED.PR_DATA_PRODUCTS;TABLE, DRIVER=4.11.77

From the attached log file, you can find that the PR_DATA_PRODUCTS table was trying to be created twice.

Once at 2015-08-27 17:00:27,863, and the other was in 2015-08-27 17:00:33,754.

Request you to please have a look, why we getting this error, which looks like related to duplicates, creation.

Regards,

Tarun

To see attachments, please log in.
Posted: 9 years ago
Posted: 31 Aug 2015 8:33 EDT
Celeste Dufresne (CelesteDufresne_GCS)
PEGA
Fellow, Technical Support, Cloud Service
Pegasystems Inc.
US

When are you running this step?  Have you reverted the database, wiped out the BPMRULED schema and restarted this from the beginning and are now seeing this issue on the second pass of the migrate script after you have successfully migrated the rules to bpmruled schema and upgraded the rules schema?  From the properties file at the very least your target username cannot be the rules schema user for this step.  It needs to be a deployment user who can access both the rules and data schemas as part of this step will be to generate the grants needed between the schemas.  But even with that issue it does not look like the bpmruled schema actually doesn't contain the tables that it should at this point.

pega.target.jdbc.username=bpmruled

pega.target.rules.schema=bpmruled
pega.target.data.schema=db2bpmd

To see attachments, please log in.
Posted: 9 years ago
Posted: 1 Sep 2015 1:34 EDT
Bin Xu (GAVINHSU)
Mediatek Inc. China

Mediatek Inc. China
CN

Hi Celeste,


Thanks a lot for you patience.


Actually, follow the instruction you provided last time, we have reverted all the database schema and restarted the upgrade from the very beginning.

What we have done includes:

  • Restore the original rules & data schema  - db2bpmd.
  • Clear the new rules schema - bpmruled.
  • Create a new upgrade schema - bpmupgrd.
  • Start the upgrade from the very beginning.
  • We've got the error at step 3 as per your provided steps:

1.  Run migrate script to clone rules tables from combined 61sp2 schema (Combined61sp2) in new rules schema (NewRules)

2.  Run upgrade script to upgrade new rules schema (NewRules).  As part of this step dummy data tables will be added to rules schema.

3.  Run migrate script (with target dataschema=Combined61sp2, target rulesschema=NewRules) to generate rules schema objects, grants between schemas

4.  Run upgrade script with dataOnly option to upgrade dataSchema.  RulesSchema=NewRules, DataSchema=Combined61sp2

Show More

Hi Celeste,


Thanks a lot for you patience.


Actually, follow the instruction you provided last time, we have reverted all the database schema and restarted the upgrade from the very beginning.

What we have done includes:

  • Restore the original rules & data schema  - db2bpmd.
  • Clear the new rules schema - bpmruled.
  • Create a new upgrade schema - bpmupgrd.
  • Start the upgrade from the very beginning.
  • We've got the error at step 3 as per your provided steps:

1.  Run migrate script to clone rules tables from combined 61sp2 schema (Combined61sp2) in new rules schema (NewRules)

2.  Run upgrade script to upgrade new rules schema (NewRules).  As part of this step dummy data tables will be added to rules schema.

3.  Run migrate script (with target dataschema=Combined61sp2, target rulesschema=NewRules) to generate rules schema objects, grants between schemas

4.  Run upgrade script with dataOnly option to upgrade dataSchema.  RulesSchema=NewRules, DataSchema=Combined61sp2

5.  Post upgrade steps include running additional scripts since you upgraded from pre-62, setting up app server, running optimize schema tool to clean up dummy data tables from NewRules schema and old rules tables from Combined61sp2 schema which is your new data schema, etc.

Regarding the user name, we're pretty sure that the privilege to do everything; so user name may not be the root cause.




Show Less
To see attachments, please log in.
Posted: 9 years ago
Posted: 1 Sep 2015 8:38 EDT
Celeste Dufresne (CelesteDufresne_GCS)
PEGA
Fellow, Technical Support, Cloud Service
Pegasystems Inc.
US

The general instructions I gave you previously where assuming you were following the upgrade with 1 database process.  If you are switching to upgrading with 2 databases then this will change the property settings for step #3.

Let's use your actual schema names to make this clear what you have done.

So the Combined61sp2=db2bpmd.  If you are upgrading with 1 database then you only need one new rules schema so you would either have NewRules=bpmruled or NewRules=bpmupgrd.  You would only need 2 new schemas if you are following the upgrade with 2 database process where you would have a temporary upgrade schema which you would migrate back to the actual new rules schema in step #3.  

When you did steps #1 and #2 did you use the same NewRules schema for both steps and if so was it bpmruled or bpmupgrd?  If you are not sure then attach the logs from when you ran these steps

Upgrade with 1 database process in general (one new schema=NewRules):

1.  Run migrate script to clone rules tables from combined 61sp2 schema (Combined61sp2=db2bpmd) in new rules schema (NewRules=?)

2.  Run upgrade script to upgrade new rules schema (NewRules=?).  As part of this step dummy data tables will be added to rules schema.

3.  Run migrate script (with target dataschema=Combined61sp2, target rulesschema=NewRules) to generate rules schema objects, grants between schemas

Show More

The general instructions I gave you previously where assuming you were following the upgrade with 1 database process.  If you are switching to upgrading with 2 databases then this will change the property settings for step #3.

Let's use your actual schema names to make this clear what you have done.

So the Combined61sp2=db2bpmd.  If you are upgrading with 1 database then you only need one new rules schema so you would either have NewRules=bpmruled or NewRules=bpmupgrd.  You would only need 2 new schemas if you are following the upgrade with 2 database process where you would have a temporary upgrade schema which you would migrate back to the actual new rules schema in step #3.  

When you did steps #1 and #2 did you use the same NewRules schema for both steps and if so was it bpmruled or bpmupgrd?  If you are not sure then attach the logs from when you ran these steps

Upgrade with 1 database process in general (one new schema=NewRules):

1.  Run migrate script to clone rules tables from combined 61sp2 schema (Combined61sp2=db2bpmd) in new rules schema (NewRules=?)

2.  Run upgrade script to upgrade new rules schema (NewRules=?).  As part of this step dummy data tables will be added to rules schema.

3.  Run migrate script (with target dataschema=Combined61sp2, target rulesschema=NewRules) to generate rules schema objects, grants between schemas

4.  Run upgrade script with dataOnly option to upgrade dataSchema.  RulesSchema=NewRules, DataSchema=Combined61sp2

5.  Post upgrade steps include running additional scripts since you upgraded from pre-62, setting up app server, running optimize schema tool to clean up dummy data tables from NewRules schema and old rules tables from Combined61sp2 schema which is your new data schema, etc.

Upgrade with 2 database process in general (2 new schemas temporary Upgrade and NewRules):

1.  Run migrate script to clone rules tables from combined 61sp2 schema (Combined61sp2=db2bpmd) in new temporary rules schema (UpGrade)

2.  Run upgrade script to upgrade new rules schema (Upgrade) As part of this step dummy data tables will be added to rules schema.

3.  Run migrate script (with source rulesschema=Upgrade target dataschema=Combined61sp2, target rulesschema=NewRules) to migrate the Upgrade schema to NewRules schema and generate rules schema objects, grants between schemas

4.  Run upgrade script with dataOnly option to upgrade dataSchema.  RulesSchema=NewRules, DataSchema=Combined61sp2

5.  Post upgrade steps include running additional scripts since you upgraded from pre-62, setting up app server, running optimize schema tool to clean up old rules tables from Combined61sp2 schema which is your new data schema, etc.


Show Less
To see attachments, please log in.
Posted: 9 years ago
Updated: 9 years ago
Posted: 2 Sep 2015 4:09 EDT
Updated: 2 Sep 2015 5:32 EDT
Tarun Sipani (sipat) Senior Technical Support Engineer
Pegasystems Inc.
JP

Hi Celeste,

Thank you very much for the detailed steps, I just confirmed below with the customer end.

1) We are using a third temporary-upgrade schema and then trying to migrate (Step #3) to the final Schema.

2) Steps 1 and 2 [from Upgrade with 2 database process in general (2 new schemas temporary Upgrade and NewRules):] have been completed.

Can we request you to please confirm the migrate properties to achieve this.

[Does any of the first 6 properties be changed to true, to migrate from upgrade to final schema]

Regards and Thanks,

Tarun

To see attachments, please log in.
Posted: 9 years ago
Posted: 2 Sep 2015 8:05 EDT
Celeste Dufresne (CelesteDufresne_GCS)
PEGA
Fellow, Technical Support, Cloud Service
Pegasystems Inc.
US

OK, so from what I am reading you are following this process:

Upgrade with 2 database process in general (2 new schemas temporary Upgrade=bpmupgrd and NewRules=bpmruled, Combined61sp2=db2bpmd that will become the new data schema)

1.  Run migrate script to clone rules tables from combined 61sp2 schema (Combined61sp2=db2bpmd) in new temporary rules schema (UpGrade=bpmupgrd)

2.  Run upgrade script to upgrade new rules schema (Upgrade=bpmupgrd) As part of this step dummy data tables will be added to rules schema.

3.  Run migrate script (with source rulesschema=bpmupgrd source dataschema=bpmupgrd target dataschema=Combined61sp2, target rulesschema=bpmruled) to migrate the Upgrade schema to bpmruled schema and generate rules schema objects, grants between schemas

4.  Run upgrade script with dataOnly option to upgrade dataSchema.  RulesSchema=bpmruled, DataSchema=db2bpmd

5.  Post upgrade steps include running additional scripts since you upgraded from pre-62, setting up app server, running optimize schema tool to clean up old rules tables from Combined61sp2 schema which is your new data schema, etc.

Show More

OK, so from what I am reading you are following this process:

Upgrade with 2 database process in general (2 new schemas temporary Upgrade=bpmupgrd and NewRules=bpmruled, Combined61sp2=db2bpmd that will become the new data schema)

1.  Run migrate script to clone rules tables from combined 61sp2 schema (Combined61sp2=db2bpmd) in new temporary rules schema (UpGrade=bpmupgrd)

2.  Run upgrade script to upgrade new rules schema (Upgrade=bpmupgrd) As part of this step dummy data tables will be added to rules schema.

3.  Run migrate script (with source rulesschema=bpmupgrd source dataschema=bpmupgrd target dataschema=Combined61sp2, target rulesschema=bpmruled) to migrate the Upgrade schema to bpmruled schema and generate rules schema objects, grants between schemas

4.  Run upgrade script with dataOnly option to upgrade dataSchema.  RulesSchema=bpmruled, DataSchema=db2bpmd

5.  Post upgrade steps include running additional scripts since you upgraded from pre-62, setting up app server, running optimize schema tool to clean up old rules tables from Combined61sp2 schema which is your new data schema, etc.

For step #3 with this process you actually need to migrate the upgraded rules back to the new rules schema and then also generate the rules schema objects/grants between schemas.  This is assuming that bpmupgrd has the upgraded rules tables and that the bpmruled schema is empty completely.   In your migrateSystem.properties file you need to set the flags like this to do this step which will generate and apply the ddl changes needed to the bpmruled schema and then copy the content of the bpmupgrd schema into bpmruled.  After it has done that it will create any triggers, stored procedures, etc. that are needed in the bpmruled schema and also issue the grants needed for the db2bpmd and bpmruled schemas to interact with each other.

pega.move.admin.table=false

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

pega.rules.objects.generate=true
pega.rules.objects.apply=true


Show Less
To see attachments, please log in.
Posted: 9 years ago
Posted: 4 Sep 2015 15:32 EDT
Celeste Dufresne (CelesteDufresne_GCS)
PEGA
Fellow, Technical Support, Cloud Service
Pegasystems Inc.
US

FYI, I will be away the next couple of weeks but I asked a colleague to keep an eye on this post in case you have any further questions.

To see attachments, please log in.
Posted: 9 years ago
Posted: 24 Sep 2015 1:26 EDT
Bin Xu (GAVINHSU)
Mediatek Inc. China

Mediatek Inc. China
CN

We have finished all the database upgrade steps, and deployed the prweb in Weblogic with deployment plan.

But, when we tried to startup the application server form Weblogic console, we keep getting error message as below.

2015-09-23 14:45:11,183 [   PegaRULES-Batch-1] [  STANDARD] [ ] [   MTKRDApp:01.01.01] (l.access.ConnectionManagerImpl) ERROR   - Not returning connection 3 for database "pegadata" to the pool as it previously encountered the following error

User ID: System

Last SQL: SELECT distinct ASS.PXREFOBJECTKEY as ".pzInsKey" FROM    PC_ASSIGN_WORKLIST ASS WHERE PXREFOBJECTCLASS LIKE '%-RD-Work-STA' AND PXTASKLABEL='AdminWorkList'

  1. com.ibm.db2.jcc.am.SqlSyntaxErrorException: DB2 SQL Error: SQLCODE=-204, SQLSTATE=42704, SQLERRMC=BPMRULED.PC_ASSIGN_WORKLIST, DRIVER=3.61.75

The problem is that schema BPMRULED was desined as RULES schema, so it shouldn’t contain table PC_ASSIGN_WORKLIST.

From the pr4_base table of RULES schema - BPMRULED, we can find that the class Assign-Worklist was mapped to PegaDATA. PC_ASSIGN_WORKLIST.

From the pr4_base table of Data schema – DB2BPMD, the class Assign-Worklist was still mapped to PegaRULES. PC_ASSIGN_WORKLIST.

Show More

We have finished all the database upgrade steps, and deployed the prweb in Weblogic with deployment plan.

But, when we tried to startup the application server form Weblogic console, we keep getting error message as below.

2015-09-23 14:45:11,183 [   PegaRULES-Batch-1] [  STANDARD] [ ] [   MTKRDApp:01.01.01] (l.access.ConnectionManagerImpl) ERROR   - Not returning connection 3 for database "pegadata" to the pool as it previously encountered the following error

User ID: System

Last SQL: SELECT distinct ASS.PXREFOBJECTKEY as ".pzInsKey" FROM    PC_ASSIGN_WORKLIST ASS WHERE PXREFOBJECTCLASS LIKE '%-RD-Work-STA' AND PXTASKLABEL='AdminWorkList'

  1. com.ibm.db2.jcc.am.SqlSyntaxErrorException: DB2 SQL Error: SQLCODE=-204, SQLSTATE=42704, SQLERRMC=BPMRULED.PC_ASSIGN_WORKLIST, DRIVER=3.61.75

The problem is that schema BPMRULED was desined as RULES schema, so it shouldn’t contain table PC_ASSIGN_WORKLIST.

From the pr4_base table of RULES schema - BPMRULED, we can find that the class Assign-Worklist was mapped to PegaDATA. PC_ASSIGN_WORKLIST.

From the pr4_base table of Data schema – DB2BPMD, the class Assign-Worklist was still mapped to PegaRULES. PC_ASSIGN_WORKLIST.

From the log, we can find that seems the bootstrap was using DB2BPMD as the database schema.

We’re not sure whether this could be the root cause or not, and how to correct it.

 

19830421: Could not find java:comp/env/prbootstrap/ in the local JNDI context, skipping prconfig setting lookup

<Sep 24, 2015 10:49:35 AM CST> <Emergency> <com.pega.pegarules.internal.bootstrap.SettingReaderJNDI> <BEA-000000> <Could not find java:comp/env/prbootstrap/ in the local JNDI context, skipping prconfig setting lookup>

<Sep 24, 2015 10:49:35 AM CST> <Emergency> <com.pega.pegarules.internal.bootstrap.SettingReaderJNDI> <BEA-000000> <Could not find java:comp/env/prbootstrap/ in the local JNDI context, skipping prconfig setting lookup>

Sep 24, 2015 10:49:35 AM com.pega.pegarules.internal.bootstrap.SettingReaderJNDI

19830421: Could not find prbootstrap in the local JNDI context, skipping prconfig setting lookup

<Sep 24, 2015 10:49:35 AM CST> <Emergency> <com.pega.pegarules.internal.bootstrap.SettingReaderJNDI> <BEA-000000> <Could not find prbootstrap in the local JNDI context, skipping prconfig setting lookup>

<Sep 24, 2015 10:49:35 AM CST> <Emergency> <com.pega.pegarules.internal.bootstrap.SettingReaderJNDI> <BEA-000000> <Could not find prbootstrap in the local JNDI context, skipping prconfig setting lookup>

Sep 24, 2015 10:49:35 AM com.pega.pegarules.internal.bootstrap.PRBootstrapDataSource

19830421: Bootstrap datatables schema: "DB2BPMD"

The default schemas set in deployment plan was:

- <variable>

<name>defaultDataSchema</name>

<value>db2bpmd</value>

</variable>

- <variable>

<name>defaultRulesSchema</name>

<value>bpmruled</value>

</variable>


Show Less
To see attachments, please log in.
Posted: 9 years ago
Posted: 24 Sep 2015 9:51 EDT
Celeste Dufresne (CelesteDufresne_GCS)
PEGA
Fellow, Technical Support, Cloud Service
Pegasystems Inc.
US

What database user have you defined in your PegaRULES datasource?  For the base datasource user you can use the data schema.  If this is what you have then I expect the problem is that you did not deployed correctly so that both the app and plan are being picked up.  You need to deploy at the directory structure level.

For example: the directory structure for ear deployments is:

<someDirectory>\app\prpc_wls_jee4.ear
<someDirectory>\plan\Plan.xml

You need to select <someDirectory> when you deploy from the WebLogic console so that both the ear and Plan.xml are used.

 








To see attachments, please log in.
Posted: 9 years ago
Posted: 18 Nov 2015 3:18 EST
Bin Xu (GAVINHSU)
Mediatek Inc. China

Mediatek Inc. China
CN

The final solution is using the original prweb.war, and with single Datasource of weblogic.

After that the server started, with errors, but it seems the functions work fine.

To see attachments, please log in.
Posted: 9 years ago
Posted: 18 Nov 2015 10:25 EST
Arvind Malav (malaa) Technical Manager
Pegasystems Inc.
IN

Hi Gavin,

While deploying PRPC ear in weblogic in Split-schema , choose following folder:

\Pega718\archives\prpc\weblogic\ear

and NOT \Pega718\archives\prpc\weblogic\ear\app

I believe, you were deploying PRPC ear by going ear from Pega719\archives\prpc\weblogic\ear\app.

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