Monthly Archives: December 2008 - Page 2

Error running rel849n.sql

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 PeopleSoft Services

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

Distribution Status stays at Posting

Problem:

When processes submitted, status remains at “Posting”.

Solution:

Navigate to PeopleTools > Process Scheduler > Report Nodes

Create a new Node Name e.g. FSDMO1.
Under Distribution Node Details, set the URL: http://GLWebApp:8000/psreports/fsdmo
Set Description: FSDMO Reporting Node
Set Operating System: NT/Win2000
Under Connection Information, set Network Path: \glwebappe$psreports

Navigate to PeopleTools > Process Scheduler > Servers

Click Search, and then click PSNT.
Click the Distribution tab.
Under Server Distribution Details, in Distribution Node Name, enter FSDMO1.

Running PSAE Programs

Task B-8-8: Running PeopleTools Conversions

In Task B-8-8: Running PeopleTools Conversions, on page 432 of the “Enterprise PeopleTools 8.49 Installation for Microsoft SQL Server”:

On glwebapp:

E:PSOFTFS900binclientwinx86psae -CD FSDMO -CT MICROSFT -CO VP1 -CP VP1 -R INSTALL -AI UPG844PORTAL

E:PSOFTFS900binclientwinx86psae -CD FSDMO -CT MICROSFT -CO VP1 -CP VP1 -R INSTALL -AI UPGQRYDUPHED

E:PSOFTFS900binclientwinx86psae -CD FSDMO -CT MICROSFT -CO VP1 -CP VP1 -R INSTALL -AI UPGPTSMDAT

E:PSOFTFS900binclientwinx86psae -CD FSDMO -CT MICROSFT -CO VP1 -CP VP1 -R INSTALL -AI UPGPT846PP

E:PSOFTFS900binclientwinx86psae -CD FSDMO -CT MICROSFT -CO VP1 -CP VP1 -R INSTALL -AI UPGPT848PP

Note: You may need to copy and paste the above lines into NotePad, and then copy these lines and paste into Command Line.

Task B-11: Running VERSION Application Engine Program

E:PSOFTFS900binclientwinx86psae -CD FSDMO -CT MICROSFT -CO VP1 -CP VP1 -R INSTALL -AI VERSION

Errors while running createvw.dms

Errors while running createvw.dms:

Related language record RE_LANDLORD_LG used by record RE_LANDLORD not found. (20,52)
Related Language Record VCHR_SRCHLG1_VW used by VCHR_SRCHCRT_VW not found (20,52)
Related language record BI_SHP_LANG_VW used by record BI_SHP_ADDR_VW2 not found. (20,52)

Data Mover crashes out.

Solution:

Did not perform step 10 of the PT 8.49.15 Product Patch User Documentation (https://psft-updates.oracle.com/ice/Resolutions/768890/PT84915UserDoc_rev2.htm). Using Application Designer, log on as user VP1 and copy project PATCH849. Then, in Data Mover, log on as VP1 and rerun CREATEVW.DMS.

10. Copy Patch Project – ONLY if PATCH849 exists –

Note: If no database changes have been made in PT 8.49 by the time this patch is released, the PATCH849 project will not exist in the projects folder and this step can be ignored.

a. Using PeopleTools 8.49.15, launch Application Designer, and sign on to the database as a PeopleSoft User. [VP1]
b. Select Tools > Copy Project > From File
c. Enter projects and select PATCH849 from the list of projects
d. Select Options and highlight the languages Common and English ONLY.
e. Select Copy to begin copying updated PeopleTools objects to your database.

After rerunning CREATEVW.DMS, the last four lines of the CREATEVW.LOG file shows:

SQL Views: 27267
Ended: Wed Dec 17 18:23:25 2008
Successful completion
Script Completed.

Other steps to try:

Stop SQL Server services and restart.
Log on as user VP1 when running createvw.dms

Reference:

http://www.pinpointps.com/?q=node/59

Restarting data mover after a crash
A data mover script can be restarted by coding in the DMS ‘set start after record name’ before the Import * command. If the record is name ps_tablename, then do not code the ‘ps_’, just code tablename.

Attempted to create views using Application Designer: In Application Designer, click Ctrl+F7 (Insert > Definitions from Project…), and search for all Records. Select All records and insert them into the current project (takes about 10 minutes to complete). Then click Build > Project and check only Create Views (modify other settings as necessary). Build the SQL script, and after creating,

Unable to connect from client machine to new 11.5.10.2 instance

Problem:

After configuring TNS names on the client, tried to connect to new 11.5.10.2 instance but failed.

Solution:

Managed SQL Access enabled. To disable, follow these steps:

Step 1:        Login to E-Business Suite with the ‘System Administrator’ Responsibility.

Step 2:        Go to : Profile –> System

Step 3:        Query the Profile “SQLNet Access’ at Site Level.

Step 4:        Set the Profile with the Value : ALLOW_ALL

Step 5:        Save and Exit Oracle Applications

Step 6:        Run Autoconfig on the 9i ORACLE_HOME

cd <9i ORACLE_HOME>/appsutil/scripts/$CONTEXT_NAME

adautocfg.sh

Step 7:        Bounce the 9i SQLNet Listener :

cd <9i ORACLE_HOME>/appsutil/scripts/$CONTEXT_NAME

addlnctl.sh stop <SID>

addlnctl.sh start <SID>

Metalink Reference:

Subject:  11.5.10 New Features : Managed SQL*Net Access from Hosts

Doc ID:  Note:291897.1

ERR ‘REP-3002: Error initializing printer’

Problem:

After installing Oracle Applications 11.5.10.2, submitted Active Users report. Concurrent request fails with message

‘REP-3002: Error initializing printer’

Solution:

To implement the solution, please execute the following steps:

1. Define a dummy printer on the server to be defined as local printer.

2. Set this dummy printer to be the default.

3. Make the following updates in the registry, before making any changes to the registry you should always make a backup copy:

Complete path Regedit:

HKEY_USERSS-1-5-...............SoftwareMicrosoftWindows NTCurrentVersionDevices

You will find String value with name as the newly defined printer

Same goes to:

HKEY_USERSS-1-5-...............SoftwareMicrosoftWindows NTCurrentVersionPrinterPorts

You will find String value with name as the newly defined printer

HKEY_USERSS-1-5-...............SoftwareMicrosoftWindows NTCurrentVersionWindows

You will find String value with name “Device” and has value including the printer name as defined

All the above string values should also be set under the following paths for the valid printer to be seen by all users

HKEY_USERS.DEFAULTSoftwareMicrosoftWindows NTCurrentVersionDevices
HKEY_USERS.DEFAULTSoftwareMicrosoftWindows NTCurrentVersionPrinterPorts
HKEY_USERS.DEFAULTSoftwareMicrosoftWindows NTCurrentVersionWindows

COBOL batch programs not running

Problem:

After installing PeopleSoft Financials, the COBOL batch programs not running.

Solution:

1. Download Micro Focus Cobol Net Express Edition from:

http://www.download.com/Net-Express-with-NET/3000-2069_4-10866201.html
http://microfocus.com/products/netexpress/
http://microfocus.com/products/netexpresswithnet/index.asp

2. Install Micro Focus Cobol Net Express With .Net on the batch server. Disable the option to install .Net, as it will require Microsoft Visual Studio 2008.

Post-install checks fail after installing

Problem:

After installing Oracle Applications E-Business Suite 11.5.10.2 on Windows, the post installation checks (HTTP Check, JSP Check, PHP Check) fail.

Solution:

Install Microsoft XML (msxml3.msi) located in downloadsXML.

Could not start Service Manager

Problem:

Concurrent manager not starting on ebusinesstest. Checked Metalink Doc ID:  Note:104452.1 (Subject:  Troubleshooting Concurrent Manager (Unix specific). Changed to /u0/oracle/testcomn/admin/log/TEST_ebusinesstest ($APPLCSF/$APPLLOG) and check last .mgr file (TEST_0424.mgr). It showed the following error message:

Starting PASMGR Concurrent Manager                 : 24-APR-2009 12:29:17
Spawned Process 18408
Could not start Service Manager FNDSM_EBUSINESSTEST_TEST. The TNS alias could not be located, the listener process on EBUSINESSTEST could not be contacted, or the listener failed to spawn the Service Manager process.
Routine AFPEIM encountered an error while starting concurrent manager PASMGR with library /u0/oracle/testappl/pa/11.5.0/bin/PALIBR.
Check that your system has enough resources to start a concurrent manager process. Contact your system admi : 24-APR-2009 12:29:17
                     Process monitor session ended : 24-APR-2009 12:29:17

Solution:

Checked Metalink for message ‘Could not start Service Manager’. Checked Metalink Doc ID:  423170.1 (Subject:  Concurrent Manager Fails to Start Because of a ‘Could not start Service Manager FNDSM__’ Error)

To implement the solution, please execute the following steps:

1. Download and apply patch 3830807: ” PATCH 3293983 NEEDS TO INCLUDE ALL THE MAKEFILES UNDER THE 8.0.6 ORACLE_HOME”.

2. Launch adadmin and choose the task to relink all product executables.

3. Startup the Concurrent Manager.

The Concurrent Manager should start without any errors. There should be no errors in the 8.0.6 listener log file.