Microsoft Windows [Version 5.2.3790] (C) Copyright 1985-2003 Microsoft Corp. C:Documents and Settingsoracle>f: F:>cd oracleproddb9.2.0 F:oracleproddb9.2.0>PROD_hostname.cmd ECHO is off. ECHO is off. Tue 05/19/2009 09:49 AM PROD_hostname.cmd exiting with status 0 F:oracleproddb9.2.0>sqlplus apps/apps SQL*Plus: Release 9.2.0.7.0 - Production on Tue May 19 09:49:27 2009 Copyright (c) 1982, 2002, Oracle Corporation. All rights reserved. ERROR: ORA-01033: ORACLE initialization or shutdown in progress Enter user-name: / as sysdba Connected to: Oracle9i Enterprise Edition Release 9.2.0.7.0 - Production With the Partitioning, OLAP and Oracle Data Mining options JServer Release 9.2.0.7.0 - Production SQL> shutdown immediate ORA-01109: database not open Database dismounted. ORACLE instance shut down. SQL> startup ORACLE instance started. Total System Global Area 831725752 bytes Fixed Size 454840 bytes Variable Size 411041792 bytes Database Buffers 409600000 bytes Redo Buffers 10629120 bytes Database mounted. ORA-01113: file 1 needs media recovery ORA-01110: data file 1: 'E:ORACLEPRODDATASYSTEM01.DBF' SQL> recover automatic database Media recovery complete. SQL> alter database open; Database altered. SQL> select * from v$database; NAME --------- PROD SQL>
Database Media Recovery of 11i Instance
How to Start the Illuminat PeopleSoft Instance
This document details steps to start PeopleSoft on the Peoplesoft2 server.
Step 1: Boot up the PeopleSoft server and log on as the Administrator user.
Step 2: From the Start menu, load Microsoft Virtual PC.
Step 3: Select Windows 2000 Peoplesoft2, and click Start.
The virtual machine starts and Windows 2000 Professional boots.
Step 4: After booting, click OK to log on as the ILLUMINAT user.
Step 5: Start the Tuxedo application server. Open Command Prompt and change directory to C:PT849appserv.
Run psadmin and start the EPDMO Application Server.
Enter the items shown in bold below.
C:>cd pt849 C:PT849>cd appserv C:PT849appserv>psadmin PSADMIN -- Tools Release: 8.49 Copyright (c) 1988, 2003, Oracle. All rights reserved. -------------------------------- PeopleSoft Server Administration -------------------------------- 1) Application Server 2) Process Scheduler 3) Search Server 4) Service Setup q) Quit Command to execute (1-4, q): 1 -------------------------------------------- PeopleSoft Application Server Administration -------------------------------------------- 1) Administer a domain 2) Create a domain 3) Delete a domain 4) Import domain configuration q) Quit Command to execute (1-4, q) : 1 Tuxedo domain list: 1) EPDMO 2) VASU Select domain number to administer: 1 -------------------------------- PeopleSoft Domain Administration -------------------------------- Domain Name: EPDMO 1) Boot this domain 2) Domain shutdown menu 3) Domain status menu 4) Configure this domain 5) TUXEDO command line (tmadmin) 6) Edit configuration/log files menu 7) Messaging Server Administration menu 8) Purge Cache 9) Preload File Cache 10) Clean IPC resources of this domain q) Quit Command to execute (1-10, q) : 1 ------------------------------- PeopleSoft Domain Boot Menu ------------------------------- Domain Name: EPDMO 1) Boot (Serial Boot) 2) Parallel Boot q) Quit Command to execute (1-2, q) [q]: 1 Attempting to boot bulletin board... tmadmin - Copyright (c) 1996-1999 BEA Systems, Inc. Portions * Copyright 1986-1997 RSA Data Security, Inc. All Rights Reserved. Distributed under license by BEA Systems, Inc. Tuxedo is a registered trademark. No bulletin board exists. Entering boot mode. INFO: BEA Tuxedo, Version 9.1, 32-bit, Patch Level (none) INFO: Serial #: 650522264137-2065448083901, Expiration NONE, Maxusers 1000000 INFO: Licensed to: Oracle-Peoplesoft-ISV Booting admin processes ... exec BBL -A : process id=3004 ... Started. 1 process started. Attempting to boot ... INFO: BEA Tuxedo, Version 9.1, 32-bit, Patch Level (none) INFO: Serial #: 650522264137-2065448083901, Expiration NONE, Maxusers 1000000 INFO: Licensed to: Oracle-Peoplesoft-ISV Booting server processes ... exec PSWATCHSRV -A -- -ID 54448 -C psappsrv.cfg -D EPDMO -S PSWATCHSRV : process id=2500 ... Started. exec PSAPPSRV -s@..psappsrv.lst -s@..psqcksrv.lst -sICQuery -sSqlQuery:SqlRequ est -- -C psappsrv.cfg -D EPDMO -S PSAPPSRV : process id=1248 ... Started. exec PSAPPSRV -s@..psappsrv.lst -s@..psqcksrv.lst -sICQuery -sSqlQuery:SqlRequ est -- -C psappsrv.cfg -D EPDMO -S PSAPPSRV : process id=300 ... Started. exec PSAPPSRV -s@..psappsrv.lst -s@..psqcksrv.lst -sICQuery -sSqlQuery:SqlRequ est -- -C psappsrv.cfg -D EPDMO -S PSAPPSRV : process id=304 ... Started. exec PSSAMSRV -A -- -C psappsrv.cfg -D EPDMO -S PSSAMSRV : process id=3112 ... Started. exec PSMONITORSRV -A -- -ID 54448 -C psappsrv.cfg -D EPDMO -S PSMONITORSRV : process id=3092 ... Started. exec WSL -A -- -n //PEOPLESOFT2:7000 -z 0 -Z 0 -I 5 -T 60 -m 1 -M 3 -x 40 -c 500 0 -p 7001 -P 7003 : process id=3028 ... Started. exec JSL -A -- -n //PEOPLESOFT2:9000 -m 5 -M 7 -I 5 -j ANY -x 40 -S 10 -c 100000 0 -w JSH : process id=1184 ... Started. exec JREPSVR -A -- -W -P C:PT849appservEPDMOjrepository : process id=3208 ... Started. 9 processes started. -------------------------------- PeopleSoft Domain Administration -------------------------------- Domain Name: EPDMO 1) Boot this domain 2) Domain shutdown menu 3) Domain status menu 4) Configure this domain 5) TUXEDO command line (tmadmin) 6) Edit configuration/log files menu 7) Messaging Server Administration menu 8) Purge Cache 9) Preload File Cache 10) Clean IPC resources of this domain q) Quit Command to execute (1-10, q) : q -------------------------------------------- PeopleSoft Application Server Administration -------------------------------------------- 1) Administer a domain 2) Create a domain 3) Delete a domain 4) Import domain configuration q) Quit Command to execute (1-4, q) : q -------------------------------- PeopleSoft Server Administration -------------------------------- 1) Application Server 2) Process Scheduler 3) Search Server 4) Service Setup q) Quit Command to execute (1-4, q): q C:PT849appserv>
Step 6: To start the web server, click Start > Programs > Oracle – peoplesoftAS > Start SOA Suite.
Step 7: Oracle Application Server starts. Click Close.
Step 8: PeopleSoft is now accessible. On your laptop, point your web browser to http://peoplesoft2:8000/ps/signon.html and log on as user VP1.
Note: Do not log off the desktop of the PeopleSoft2 virtual machine as this will close the application server.
Checking for Prerequisite Patches and Patch Levels
In a patch’s README file, the prerequisite patches and patch levels that must be in place before that patch is applied are listed. Patches are indicated by a patch number (usually seven digits long), for example, 4712852. Patch levels are usually of the form 11i.<PRODUCT CODE>.<LETTER>, for example, 11i.GL.H.
To determine if a particular prerequisite patch has already been applied to the system, query the AD_BUGS table.
Step 1: Source the environment to load SQL*Plus. Either the applications tier environment or database tier environment can be sourced.
[applmgr@appslinux /]$ cd /u2/oracle/vis2appl/ [applmgr@appslinux vis2appl]$ . APPSORA.env
Step 2: Load SQL*Plus:
[applmgr@appslinux vis2appl]$ sqlplus apps/apps
Step 3: To determine whether a particular patch has been applied, query the BUG_NUMBER column of the AD_BUGS table for the patch number. For example, to determine if the patch 4712852 has been applied to the system, issue this SQL query:
SQL> select bug_number, creation_date from ad_bugs where bug_number = '4712852'; BUG_NUMBER CREATION_DATE ------------------------------ ------------- 4712852 16-MAR-07
If the query returns a row, the patch has been applied, whereas if the query does not return any rows, then the patch has not been applied.
Step 4: To determine the patch level of a product, query the PATCH_LEVEL columns of the FND_PRODUCT_INSTALLATIONS table. For example, to determine the patch level for the GL product, issue this SQL query:
SQL> select patch_level, status from fnd_product_installations where patch_level like '%GL%'; PATCH_LEVEL S ------------------------------ - 11i.GL.H I
Unable to access Application Express
In web browser, navigated to http://shrivastava.test.int:7777/pls/apex. Received message:
Forbidden You don't have permission to access /pls/apex/apex on this server. ---------------------------------------------------------- Oracle-Application-Server-10g/10.1.2.0.0 Oracle-HTTP-Server Server at SHRIVASTAVA.TEST.INT Port 7777
Solution:
Password in the dads.conf (C:oracleproduct10.2.0http_1Apachemodplsql confdads.conf ) file is incorrect. Confirm by logging on to SQL*Plus as user APEX_PUBLIC_USER. Correct password, then bounce Apache web server.
Running DDDAUDIT
To run DDDAUDIT manually:
1. Click Start > Run
2. Click Browse, navigate to binsqlMSSbinw, and select sqrw.exe. Append the necessary flags:
On glwebapp:
E:PSOFTFS900binsqrMSSBINWsqrw.exe -IE:PSOFTFS900sqr -ZIFE:PSOFTFS900sqrpssqr.ini -fC:Temp -KEEP
Note that the above is one line without breaks.
If PS_HOME is mapped to a drive, use the drive letter instead:
P:binsqrMSSBINWsqrw.exe -IP:sqr -ZIFP:sqrpssqr.ini -fC:Temp -KEEP
Parameters for DDDAUDIT reportSQ
3. The SQR for PeopleSoft V8.49.15 form appears. Enter the following parameters:
Report name: E:PSOFTFS900sqrdddaudit.sqr
Data Source: FSDMO
Username: sa
Password: train
The FSDMO ODBC connection must be created for it to appear in the Data Source drop down list.
Parameters for SYSAUDIT report
4. The SQR for PeopleSoft V8.49.15 form appears. Enter the following parameters:
Report name: E:PSOFTFS900sqrsysaudit.sqr
Data Source: FSDMO
Username: sa
Password: train
The FSDMO ODBC connection must be created for it to appear in the Data Source drop down list.
5. To view the report, enter the following at the Command Prompt:
E:PSOFTFS900binsqrMSSBINWsqrwv.exe
PDF reports not appearing in browser
Problem:
After running a report in PeopleSoft with PDF output, when the output file is clicked in Process Monitor, a dialog box appears prompting you to save the PDF file to the hard drive. The expected behaviour is that the PDF report will appear in the browser window.
Solution:
1. In Internet Explorer, click the Tools menu and then click Internet Options. Click the Advanced tab. Then click Restore Defaults.
Alternatively, uncheck ‘Do not save encrypted pages to disk.
2. The digital certificates are incorrectly configured. Regenerate and setup the correct certificates.
(TRIGGER-1) Trigger defined in the Application Designer and not found in the Database
Problem:
After cloning fsdev to fstst, DDDAUDIT was run. It showed the following error:
(TRIGGER-1) Trigger defined in the Application Designer and not found in the Database: Record Name Trigger Name --------------- --------------- CHARTFIELD1_TBL PSICHARTFIELD1_TBL CHARTFIELD1_TBL PSUCHARTFIELD1_TBL 2 Total Rows
Solution:
In GLWEBAPP, launch Application Designer. Log on to FSTST (ensure FSTST ODBC Connection created).
(QUERY-22) Following Queries Were Created Without PUBLIC Access Query Name
Problem:
After cloning fsdev to fstst, SYSAUDIT was run. It showed the following error:
(QUERY-22) Following Queries Were Created Without PUBLIC Access Query Name ------------------------------- Oper ID ------------------------------- FJBG_CALENDARS VP1 FJBG_NAVIGATION VP1 FJBG_SET_CONTROL_GROUP VP1 FJBG_TIMESPANS VP1 4 Total Rows
Solution:
Spoke to consultant (FB). He said that he created these queries and they were set to be private. Therefore, the error could be ignored.
(TREE-21) Tree Selector Control contains Tree name that is not defined in Tree Definition table
Problem:
After cloning fsdev to fstst, SYSAUDIT was run. It showed the following error:
(TREE-21) Tree Selector Control contains Tree name that is not defined in Tree Definition table: Tree Name -------------------- Set Id ------------ Effect DT ------------ Selector Number ---------- ACCT_BY_LOB_DETAIL SHARE 01/01/1900 101 1 Total Rows
Solution:
This tree was created by the consultant FB and he advised that it could be ignored.
Enterprise FSCM9.0 PeopleBooks Not Appearing
Problem:
After installing Enterprise FSCM 9.0 PeopleBooks and bouncing PeopleBooks web server, they do not appear in the list of PeopleBooks.
Solution:
Enterprise FSCM 9.0 PeopleBooks installed to wrong directory. It should be installed to the htmldoc directory:
E:PSOFTFS900webservPSOL_fsdmoinstalledAppsPSOL_fsdmoNodeCellPSOL.earPSOL.warhtmldoc
Recent Comments