As stated in the installation manual there are a few prerequisites in chapter CHAPTER 8B Configuring the Application Server on UNIX page 238
Before beginning this procedure, you should have completed the following tasks:
- Installed your application server.
See "Using the PeopleSoft Installer," Understanding PeopleSoft Servers
- Installed Tuxedo 11gR1
See "Installing Additional Components."
- Granted authorization to a PeopleSoft user ID to start the application server.
The database configuration procedure includes a step for setting up the user ID with authorization to start
the application server. See the application-specific installation instructions for information on the user IDs
for your PeopleSoft application. See the PeopleTools: Security Administration product documentation
for information on PeopleSoft PeopleTools delivered user profiles.
See "Creating a Database on UNIX," Running the Database Configuration Wizard.
See "Creating a Database Manually <on Windows or UNIX>," Creating Data Mover Import Scripts.
- Run the following SQL statements on your database server to review and if needed, update the PSCLASSDEFN table:
SELECT CLASSID, STARTAPPSERVER FROM PSCLASSDEFN
WHERE CLASSID IN (SELECT OPRCLASS FROM PSOPRCLS WHERE OPRID='<OPRID>');
UPDATE PSCLASSDEFN SET STARTAPPSERVER=1 WHERE CLASSID='<CLASSID>';
Note. Installers typically use VP1 or PS to test the application server. If these users are deleted or their
passwords are changed, the application server will no longer be available. To avoid this problem, you can set
up a new operator (called PSADMIN or PSASID, for instance) with privileges to start the application server.
If you do this, you can use the new operator for your servers and you won't need to change the
password each time VP1 or PS is changed.
Does you user have privileges to start the applications server.
Also pay attention to the connectid configuration in the application server. This should be the same connectid and password as you provided during the database creation script connect.sql
Hello. Thanks a lot for replying.
I solve the second error as below:
Grant select on PS.PSDBOWNER to PUBLIC;
After that I reboot psadmin and the second error is gone. Thanks.