This is a continuation of my PeopleTools 8.51 posts. Now, we will use Change Assistant.
Please see my Step by Step page for more articles like this, or you can start at the beginning of this series with Part 1.
This is a continuation of my PeopleTools 8.51 posts. Now, we will use Change Assistant.
Please see my Step by Step page for more articles like this, or you can start at the beginning of this series with Part 1.
This is a continuation of my PeopleTools 8.51 posts. In this part, we are looking at installing WebLogic and the PIA.
Sorry it has taken a while to get this post proofread — I was sick this weekend and had family visiting as well. I will try to keep the others coming soon.
This step by step continues from the previous part 1. In that part, we simply prepared the system. Now, we are ready to install software.
Again, I am following the “Enterprise PeopleTools 8.51 Update” document from Oracle.
I just watched the presentation on Feature Packs:
PeopleSoft Apps Strategy Blog: More About PeopleSoft Feature Packs
This article is a follow up from a first article that lists some of the new features provided via feature packs.
The one thing that I learned is that Feature Packs are more for people installing new versions of PeopleSoft whether a new customer converting to PeopleSoft or an existing customer upgrading to the latest version. If you are keeping current on bundles you also get the new features.
So, the important thing in my opinion is to create a business process that can quickly install and test the bundles so that you keep your system updated. This allows you to both avoid problems by getting fixes in and allows you to take full advantage of system with the new features.
I wanted to test drive the new PeopleTools 8.51, and I decided to try it in a copy of my personal HCM 9.0 Environment. In addition, I thought this would make a great Step-By-Step article. Please comment on anything you see that I missed.
To do this, I am following the “Enterprise PeopleTools 8.51 Update” document from Oracle.
Just to give you an idea of what I have running — this is an image with PeopleTools 8.49.12. It already has WebLogic, PIA, the app server, and batch server running fine.
This first part is just preparing for the upgrade.
I have been working on trying to upgrade an instance of PeopleSoft that I have to PeopleTools 8.51. In doing so, I had some issues with installing WebLogic. This post describes the errors and fixes.
Today, I ran into an error importing a PeopleTools tree into an instance of PeopleSoft. Probably, the problem was that I was using an old version of PeopleTools (8.46).
If this were a production system, the fix would be to upgrade PeopleTools to 8.51. But, this is for testing purposes, and I kind of want to keep the old version so that I can make sure things run with it.
Here is the error message that I received from Data Mover:
SQL error. Stmt #: 0 Error Position: 0 Return: 1400 - ORA-01400: cannot insert NULL into ("SYSADM"."PSTREEDEFN"."PT_ALLVALUEAUDOPT")
With all that said, you probably don’t want to follow these directions. (This is a don’t try at home moment.) I don’t even know why I am posting this. Maybe it will help some one with SQL syntax or something. Most likely, I will need it again for a later update into this same instance.
This is a continuation of the following posts:
This time, we are trying some of the suggestions from Dan on this comment:
So, let’s see what happens
Trace files can give a lot of nice troubleshooting information, sometimes too much. Sometimes, you may have a situation where a problem occurs in one system but not in another. You could run a trace in both systems, but comparing those trace files is difficult. Each line has a timestamp, which will be different in each file.
Here is a trick for getting rid of those timestamps. Here is the source:
sed : Remove first 4 letters in each line
Of course, you need Linux, Unix, or Cygwin for this — something with the sed program. Here is the command:
sed 's/^.\{51\}//g' "mytrace.tracesql" > modtrace.tracesql
For example, here are the first few lines of a trace file:
PSAPPSRV.248 (181) 1-1 10.24.26 Cur#1.248.FSDEV90 RC=0 Dur=0.001000 COM Stmt=SELECT VERSION FROM PSVERSION WHERE OBJECTTYPENAME = 'SYS' PSAPPSRV.248 (181) 1-2 10.24.26 0.003000 Cur#1.248.FSDEV90 RC=0 Dur=0.001000 COM Stmt=SELECT PORTAL_NAME, PORTAL_REFTYPE, PORTAL_OBJNAME FROM PSPRSMDEFN WHERE VERSION > :1 UNION SELECT PORTAL_NAME, PORTAL_REFTYPE, PORTAL_OBJNAME FROM PSPRSMDEL WHERE VERSION > :2 PSAPPSRV.248 (181) 1-3 10.24.26 0.000000 Cur#1.248.FSDEV90 RC=0 Dur=0.000000 Bind-1 type=8 length=4 value=214748355
After running the command, here is what it looks like:
Cur#1.248.FSDEV90 RC=0 Dur=0.001000 COM Stmt=SELECT VERSION FROM PSVERSION WHERE OBJECTTYPENAME = 'SYS' Cur#1.248.FSDEV90 RC=0 Dur=0.001000 COM Stmt=SELECT PORTAL_NAME, PORTAL_REFTYPE, PORTAL_OBJNAME FROM PSPRSMDEFN WHERE VERSION > :1 UNION SELECT PORTAL_NAME, PORTAL_REFTYPE, PORTAL_OBJNAME FROM PSPRSMDEL WHERE VERSION > :2 Cur#1.248.FSDEV90 RC=0 Dur=0.000000 Bind-1 type=8 length=4 value=214748355
Now, you can use a tool like Beyond Compare or Meld to compare the trace files without the timestamp. If you don’t have a compare tool, look here.