Problem:
Under Process Monitor (PeopleTools > Process Scheduler > Process Monitor), reports are completing successfully, but hyperlinks to the posted reports are not appearing.
Solution:
The hyperlink appears under the Details column:
1. Select
2. Instance
3. Seq.
4. Process Type
5. Process Name
6. User
7. Run Date/Time
8. Run Status
9. Distribution Status
10. Details
Also, ensure that Publish/Subscribe (Pub/Sub) is enabled in the Application Server.
Problem:
When running the Build and Alter Task > Build and Alter Step, the follow appear in the log file:
SQL Build process began on 12/29/2008 at 3:43:44 PM for database FSDEV.
Warning: SAC_SRCNODE_VW - Record definition does not exist. Record not processed. (76,73)
Warning: The record SPL_PEGGING_INF has more than 16 keys. Table will be altered to support functional index.
Warning: The record WTHD_SENT_DTL has more than 16 keys. Table will be altered to support functional index.
Warning: The record WTHD_SNT_D_HST has more than 16 keys. Table will be altered to support functional index.
Warning: The record WTHD_TO_SND_DTL has more than 16 keys. Table will be altered to support functional index.
Warning: The record WTHD_TO_SND_TMP has more than 16 keys. Table will be altered to support functional index.
Warning: The record WTHD_TRXN_TMP3 has more than 16 keys. Table will be altered to support functional index.
Warning: GM_CONT_CERT_VW - Record definition does not exist. Record not processed. (76,73)
Warning: GM_CONT_JHDR_VW - Record definition does not exist. Record not processed. (76,73)
Warning: GM_CONT_PROF_VW - Record definition does not exist. Record not processed. (76,73)
Warning: PL_SOHOLD3_VW - Record definition does not exist. Record not processed. (76,73)
Warning: RE_OPEXADT_PADD - Record definition does not exist. Record not processed. (76,73)
Warning: RE_OPEXADT_RADD - Record definition does not exist. Record not processed. (76,73)
Warning: SAC_TGTNODE_VW - Record definition does not exist. Record not processed. (76,73)
Warning: SHIPTO_ADDR_VW1 - Record definition does not exist. Record not processed. (76,73)
Warning: SHIPTO_ADDR_VW2 - Record definition does not exist. Record not processed. (76,73)
Warning: SPA_SP_RC_PD_V2 - Record definition does not exist. Record not processed. (76,73)
Warning: VNDR_ORDER_TMP - Record definition does not exist. Record not processed. (76,73)
Warning: VNDR_REMIT_TMP - Record definition does not exist. Record not processed. (76,73)
**** Begin Build Settings for this Run
Create Tables = Yes
Create Indexes = Yes
Create Views = Yes
Create Triggers = Yes
Alter Tables = Yes
Log to File = Yes
Log to Window = No
Write comments to script = Yes
Always overwrite files = Yes
Execute SQL Now = No
Write SQL to script file = Yes
Logging level = Log fatal errors and warnings only
Table creation option = Skip table if it exists
View creation option = Drop and recreate view if it exists
IndexCreationOption = Recreate index only if modified
Alter Adds = Yes
Alter Changes = Yes
Alter Renames = Yes
Alter Deletes = Yes
Alter even if no changes = No
Alter Table Option = Alter in Place
Write script output to: Separate files
Log filename = E:/temp/softwareupdateFSCM900_MP5{823d7dbc-c7c8-11dd-9439-e147c04c274d}/BuildAndAlter.log
Table creation script filename = E:/temp/softwareupdateFSCM900_MP5{823d7dbc-c7c8-11dd-9439-e147c04c274d}/CreateTables.sql
Index creation script filename = E:/temp/softwareupdateFSCM900_MP5{823d7dbc-c7c8-11dd-9439-e147c04c274d}/CreateIndexes.sql
View creation script filename = E:/temp/softwareupdateFSCM900_MP5{823d7dbc-c7c8-11dd-9439-e147c04c274d}/CreateView.sql
Trigger creation script filename = E:/temp/softwareupdateFSCM900_MP5{823d7dbc-c7c8-11dd-9439-e147c04c274d}/CreateTriggers.sql
Alter table script filename = E:/temp/softwareupdateFSCM900_MP5{823d7dbc-c7c8-11dd-9439-e147c04c274d}/AlterTables.sql
Alter drop column option = drop column if data present
Alter truncate column option = truncate column if data present
Target database platform = MICROSFT
Target sizing set = 0
SQL Build process ended on 12/29/2008 at 3:45:28 PM.
1641 records processed, 0 errors, 19 warnings.
SQL Build script for Create Tables written to file E:/temp/softwareupdateFSCM900_MP5{823d7dbc-c7c8-11dd-9439-e147c04c274d}/CreateTables.sql.
SQL Build script for Create Indexes written to file E:/temp/softwareupdateFSCM900_MP5{823d7dbc-c7c8-11dd-9439-e147c04c274d}/CreateIndexes.sql.
SQL Build script for Create Views written to file E:/temp/softwareupdateFSCM900_MP5{823d7dbc-c7c8-11dd-9439-e147c04c274d}/CreateView.sql.
SQL Build script for Create Triggers written to file E:/temp/softwareupdateFSCM900_MP5{823d7dbc-c7c8-11dd-9439-e147c04c274d}/CreateTriggers.sql.
SQL Build script for Alter Tables written to file E:/temp/softwareupdateFSCM900_MP5{823d7dbc-c7c8-11dd-9439-e147c04c274d}/AlterTables.sql.
SQL Build log file written to E:/temp/softwareupdateFSCM900_MP5{823d7dbc-c7c8-11dd-9439-e147c04c274d}/BuildAndAlter.log.
Solution:
This is acceptable according to the documentation for the step:
Important!
If you receive the following warning message during the Build and Alter Step of the Build and Alter task, it is due to the Record being deleted by the Project. Please ignore the warning: Record definition does not exist. Record not processed. (76,73). If you receive the following warning message during the Build and Alter Step of the Build and Alter task, it is due to the field being deleted by the Project. Please ignore the warning: Field to be deleted has data present. Record processed. (76,23).DB2 Customers may need to recreate All Views manually by running createvw.dms using Datamover. This is because some views might become inoperable due to dependencies.If Run Create Triggers Script step fails because a trigger does not exist in the database then go to the CREATETRIGGERS.sql script in the Output directory, remove the offending statement and rerun the script.
Problem:
After deploying files from MP5, the COBOL programs must be compiled. However, some files do not compile:
E:tempcompile>set PS_HOME=E:PSOFTFS900
E:tempcompile>set COBROOT=E:cobolBase
E:tempcompile>cd /d E:PSOFTFS900setup
E:PSOFTFS900setup>cblbld E: tempcompile
ASCII Cobol Compilations Proceeding
Logging progress to file E:tempcompileCBLBLD.LOG
COBOL compiler found in E:cobolBase
Target directory (E:PSOFTFS900CBLBINA) exists and is writable
Copying source files …
Building the COBOL targets …
File(s) that failed to compile or link:
.
Compile error for CPPIPRDN.obj
Compile error for INPFVALD.obj
Compile error for INPGPROC.obj
Compile error for INPGREPL.obj
Compile error for INPJIURV.obj
Compile error for INPPPROC.obj
Compile error for INPTVALD.obj
Compile error for INPVPROC.obj
Compile error for INPVVALD.obj
Compile error for INPZPWFB.obj
Compile error for SFPBPCFG.obj
Compile error for SFPDCDRV.obj
Compile error for SFPDCOMP.obj
Compile error for SFPDCVAL.obj
Compile error for SFPDISUE.obj
Compile error for SFPSGBRC.obj
Compile error for SFPSUPDT.obj
Compile error for SFPSVALD.obj
The error list is in E:tempcompileERROR.LIS
.
Aborting this process !!! EXEs/GNTs/INTs are not going to be copied/replaced…
.
Please fix the errors and rerun this batch file !!!!!!!
.
Symptoms:
The problem is with COBOL compiles, where if the customer doesn’t have all the products licensed when we compile the COBOLs from recent Maintenance Packs we get errors. This is due to the fact that CA is not looking at the licensed products or dbcodes to validate licensed products. Therefore errors are displayed during the compilation as copybooks are not supplied for the non licensed products.
Here’s an example list of the COBOLs that don’t compile:
CEPCSQL2, CPPICSTI, CPPIPRDN, INPADYN3, INPADYN4, INPAPROC, INPIVALD, INPOTEST, INPSDRCT, INPVIADJ, INPVPROC, INPVVALD, INPXPROC, SFPDISUE, SFPEPROC, SFPFPROC, SFPREVAL
Here’s a copy of what’s in the dbcodes.ep:
EP PeopleSoft FIN/SCM Database
EP PeopleSoft FIN/SCM Demo Database
AM PeopleSoft Asset Management
CM PeopleSoft Cash Management
CO PeopleSoft Common Objects
TR = PeopleSoft Deal Management
EO = PeopleSoft Enterprise Components
EPO = PeopleSoft eProcurement
GL = PeopleSoft General Ledger
AP = PeopleSoft Payables
PO = PeopleSoft Purchasing
Cause:
Not Applicable
Solution:
Tools incident 714685000 was created. The incident is considered to be an enhancement for change assistant in a tools versions greater than 8.45.
If the customer does not have licenses for the modules related to the cobol files that are failing, they can ignore the compile errors. If they do not want to ignore the error messages, they can remove the erroring files from the src directory (move them to another directory) and run compile again.
Reference:
E-CA Change assistant not checking the license before compiling the cobols (Doc ID 623178.1)
Problem:
In Change Assistant (on glwebapp), navigated to Tools > Apply Change Packages. Went through wizard and reached Select apply directory. Chose directory E:staging, but the following error appeared:
Cannot locate any Change Packages in the apply directory
Solution:
Choose directory that contains the zip file of the downloaded patch (e.g. the directory that contains upd745700.zip, E:stagingCDImagescd849-FinMP5Cumulative).
set PS_HOME=E:PSOFTFS900
set COBROOT=”C:Program FilesMicro FocusNet Express 5.0Base”
E:PSOFTFS900srccblwin32cblmake FSP*
E:PSOFTFS900srccblwin32cblmake GLP*
Note that the above commands assume that the current working directory is the directory with the COBOL programs. It may be a good idea to run the cblmake, after running cblbld and the current working directory is that with the output of the cblbld programs (e.g. E:tempcompile_20081223b).
In Command Prompt, run the following commands:
set PS_HOME=E:PSOFTFS900
set COBROOT=E:cobolBase
cd /d E:PSOFTFS900setup
cblbld E: tempcompile_20081223a
set PS_HOME=E:PSOFTFS900
set COBROOT=”C:Program FilesMicro FocusNet Express 5.0Base”
cd /d E:PSOFTFS900setup
cblbld E: tempcompile_20081223b
Problem:
After compiling, the following is displayed:
File(s) that failed to compile or link:
.
Compile error for FSPCTADJ.obj
Compile error for FSPYCLOG.obj
Compile error for GLPCEARN.obj
Compile error for GLPCIPNL.obj
Compile error for GLPCPROC.obj
Compile error for GLPOELIM.obj
Compile error for GLPPBKCD.obj
Compile error for GLPPINWK.obj
Compile error for GLPPRVRS.obj
Compile error for GLPPUNPS.obj
Compile error for PTPSQLGS.obj
The error list is in E:tempcompileERROR.LIS
.
Aborting this process !!! EXEs/GNTs/INTs are not going to be copied/replaced…
.
Please fix the errors and rerun this batch file !!!!!!!
Solution:
Check the CBLBLD.LOG file for details:
The E:tempcompileERROR.LIS file showed:
Compile error for FSPCTADJ.obj
Compile error for FSPYCLOG.obj
Compile error for GLPCEARN.obj
Compile error for GLPCIPNL.obj
Compile error for GLPCPROC.obj
Compile error for GLPOELIM.obj
Compile error for GLPPBKCD.obj
Compile error for GLPPINWK.obj
Compile error for GLPPRVRS.obj
Compile error for GLPPUNPS.obj
Compile error for PTPSQLGS.obj
Check the list file for the above files:
FSPCTADJ.LIS
FSPYCLOG.LIS
GLPCEARN.LIS
GLPCIPNL.LIS
GLPCPROC.LIS
GLPOELIM.LIS
GLPPBKCD.LIS
GLPPINWK.LIS
GLPPRVRS.LIS
GLPPUNPS.LIS
PTPSQLGS.LIS
The above COBOL programs exceed the 2200-line limit for the free version of Micro Focus Cobol Net Express Edition, and so cannot be compiled.
Exception java.lang.NullPointerException caught in org.apache.xml.serialize.BaseMarkupSerializer.serializeNode()
Dec 22, 2008 4:44:58 PM com.peoplesoft.pt.changeassistant WARNING: Exception java.lang.NullPointerException caught in org.apache.xml.serialize.BaseMarkupSerializer.serializeNode() java.lang.NullPointerException at org.apache.xml.serialize.BaseMarkupSerializer.serializeNode(Unknown Source) at org.apache.xml.serialize.BaseMarkupSerializer.serialize(Unknown Source) at com.peoplesoft.pt.changeassistant.XMLEncoding.fromXML(XMLEncoding.java:54) at com.peoplesoft.pt.changeassistant.XMLEncoding.fromXML(XMLEncoding.java:40) at com.peoplesoft.pt.changeassistant.Job.fromXML(Job.java:1373) at com.peoplesoft.pt.changeassistant.step.steps.DeployFile.onExecuteDeployFiles(DeployFile.java:98) at com.peoplesoft.pt.changeassistant.Job$StepRunner.run(Job.java:2041) at java.lang.Thread.run(Unknown Source)
Checking the Environment Hub (http://glwebapp:8000/PSEMHUB/hub), it returns:
Registered Hosts Summary – 8.49.15.
Hostname OS Type OS Version IP Address State Peer ID Peer Type Peer Version
GLDBASE Windows 2003 5.2 10.18.14.31 Running 4 Agent 8.49.15.
GLWEBAPP Windows 2003 5.2 10.18.14.30 Running 1 Agent 8.49.15.
GLWEBAPP Windows 2003 5.2 10.18.14.30 Not Running 2 Change Assistant 8.49.15.
Note that from the above table, the Change Assistant is not running.
Solution:
In Change Assistant, under Tools > Options, the Change Assistant Mode is set to Perform PeopleSoft Upgrade. It should be set to Apply Application Update.
Problem:
When recreating database (on page 420-421 of Enterprise PeopleTools 8.49 Installation for Microsoft SQL Server), Application Designer crashes on record 2746/4009 while copying project PPLTL84CUR.
Solution:
1. Run Application Designer on glwebapp, not gldbase
2. Copy the PTPATCH project using Application Designer
Others suggestions:
FSCM MP5 partially applied to node. Inconsistent libraries for Application Designer. Reapply MP5.
Allocate more memory to the Java runtime.
The following errors appear when running rel849n in SQL Server:
Msg 1913, Level 16, State 1, Line 2
The operation failed because an index or statistics with name ‘PSAPSROLECLASS’ already exists on table ‘PSROLECLASS’.
Msg 1913, Level 16, State 1, Line 2
The operation failed because an index or statistics with name ‘PSCPSTREELEAF’ already exists on table ‘PSTREELEAF’.
Solution:
These objects already exist in the database, and the error can be ignored.
Starting Application Server
To start the application server, log on to the gl-web-app server (10.18.14.30) using Terminal Services Client. Open Command Prompt and enter the following commands (in bold red):
C:> E:
E:> cd PSOFTFS900appserv
E:PSOFTFS900appserv> psadmin.exe
Enter the following options:
1) Application Server
1) Administer a domain
1) FSDMO
1) Boot this domain
1) Boot (Serial Boot)
Starting Batch Server/Process Scheduler
To start the batch server, log on to the gl-web-app server (10.18.14.30) using Terminal Services Client. Open Command Prompt and enter the following commands:
E:
cd PSOFTFS900appserv
psadmin.exe
Enter the following options:
2) Process Scheduler
1) Start a Process Scheduler Server
1) FSDMO
Starting Web Server (BEA WebLogic)
To start the batch server, log on to the gl-web-app server (10.18.14.30) using Terminal Services Client. Open Command Prompt and enter the following commands:
E:
Cd PSOFTFS900webservfsdmobin
startWebLogicAdmin.cmd
The final line shows:
Open a second Command Prompt and enter the following commands:
E:
Cd PSOFTFS900webservfsdmobin
startManagedWebLogic.cmd PIA
The final line shows:
Starting Web Server (IBM WebSphere)
Single Node
cd /d E:PSOFTFS900webservfsdevbin
startserver.bat server1 -profileName fsdev
Multi Node
cd /d E:PSOFTFS900webservPIA_fsdmobin
startserver.bat server1 -profileName PIA_fsdmo
Recent Comments