8 Replies Latest reply: Apr 12, 2012 6:57 PM by user10122696 RSS

    I can't log in datamover with user ps

    918438
      Hi everyone,I am Jason
      I can't log in datamover with user ps

      Here is the log:
      PeopleTools 8.52 Client Trace - 2012-02-18

      PID-Line Time Elapsed Trace Data...
      -------- -------- ---------- -------------------->
      1-1 23.55.35 Tuxedo session opened {oprid='PS', appname='TwoTier', addr='//TwoTier:7000', open at 03CA4D90, pid=14236}
      1-2 23.55.35 0.098000 Cur#0.14236.HR91DEV RC=0 Dur=0.034000 Create Connection Info=Primary/HR91DEV/people/ Handle=03CCE7E8
      1-3 23.55.35 0.003000 Cur#1.14236.notSamTran RC=0 Dur=0.003000 Open Cursor Handle=03CCE7E8
      1-4 23.55.35 0.000000 Cur#1.14236.HR91DEV RC=0 Dur=0.000000 COM Stmt=SELECT OWNERID FROM PS.PSDBOWNER WHERE DBNAME=:1
      1-5 23.55.35 0.000000 Cur#1.14236.HR91DEV RC=0 Dur=0.000000 Bind-1 type=2 length=7 value=HR91DEV
      1-6 23.55.35 0.001000 Cur#1.14236.HR91DEV RC=0 Dur=0.000000 Fetch
      1-7 23.55.35 0.001000 Cur#1.14236.HR91DEV RC=0 Dur=0.001000 COM Stmt=SELECT OWNERID, TOOLSREL, TO_CHAR(LASTREFRESHDTTM,'YYYY-MM-DD HH24:MI:SS'), TO_CHAR(LASTCHANGEDTTM,'YYYY-MM-DD HH24:MI:SS') FROM SYSADM.PSSTATUS
      1-8 23.55.35 0.000000 Cur#1.14236.HR91DEV RC=0 Dur=0.000000 Fetch
      1-9 23.55.35 0.000000 Cur#1.14236.HR91DEV RC=0 Dur=0.000000 COM Stmt=SELECT DBID FROM SYSADM.PSSTATUS
      1-10 23.55.35 0.000000 Cur#1.14236.HR91DEV RC=0 Dur=0.000000 Fetch
      1-11 23.55.35 0.000000 Cur#1.14236.HR91DEV RC=0 Dur=0.000000 COM Stmt=SELECT VERSION, OPERPSWD, ENCRYPTED, SYMBOLICID, ACCTLOCK FROM SYSADM.PSOPRDEFN WHERE OPRID = :1
      1-12 23.55.35 0.000000 Cur#1.14236.HR91DEV RC=0 Dur=0.000000 Bind-1 type=2 length=2 value=PS
      1-13 23.55.35 0.001000 Cur#1.14236.HR91DEV RC=0 Dur=0.000000 Fetch
      1-14 23.55.35 0.000000 Cur#1.14236.HR91DEV RC=0 Dur=0.000000 COM Stmt=SELECT ACCESSID, ACCESSPSWD, ENCRYPTED FROM SYSADM.PSACCESSPRFL WHERE SYMBOLICID = :1
      1-15 23.55.35 0.000000 Cur#1.14236.HR91DEV RC=0 Dur=0.000000 Bind-1 type=2 length=7 value=SYSADM1
      1-16 23.55.35 0.000000 Cur#1.14236.HR91DEV RC=0 Dur=0.000000 Fetch
      1-17 23.55.35 0.000000 Cur#1.14236.HR91DEV RC=0 Dur=0.000000 Disconnect
      1-18 23.55.35 0.048000 Cur#0.14236.notSamTran RC=0 Dur=0.048000 Destroy Connection Handle=03CCE7E8
      1-19 23.55.35 0.046000 Cur#0.14236.HR91DEV RC=404 Dur=0.046000 Create Connection Info=Primary/HR91DEV/SYSADM/ Handle=00000000


      thx for ur help
        • 1. Re: I can't log in datamover with user ps
          918438
          I can log in datamover with sysadm and i am sure that password of PS is correct.
          • 2. Re: I can't log in datamover with user ps
            HakanBiroglu
            Hi,

            You can login in bootstrap mode, so at db level (user SYSADM, connectivity, correct cb client, which should be 32 bit) all is fine, usually the case.

            What is the error the Datamover returns?

            /* */
            Did you configure the Configuration Manager on the machine from where you are trying to start datamover.
            If not do so and pay attention to set the correct connectid and password for connectid.
            /* See in the trace file now that connection could be made with user people, so your Configuration Manager should be setup correctly*/

            Is the password for PS encrypted in PSOPRDEFN?
            To be sure you could also try to reset the password of user PS thought Datamover in bootstrap mode and again encryping it with following commands:

            update PSOPRDEFN
            set OPERPSWD = 'PS', ENCRYPTED = 0 , ACCTLOC = 0
            where oprid = 'PS';

            ENCRYPT_PASSWORD PS;

            Edited by: Hakan Biroglu on Feb 18, 2012 5:47 PM
            • 3. Re: I can't log in datamover with user ps
              918438
              update PSOPRDEFN
              set OPERPSWD = 'PS', ENCRYPTED = 0 , ACCTLOC = 0
              where oprid = 'PS';

              ENCRYPT_PASSWORD PS;

              I have done as what u said but it didn't work.

              I can log in datamover with sysadm successfully but when i tried to log in datamover with PS,it returned

              File: SQL Access ManagerSQL error. Stmt #: 2 Error Position: 0 Return: 404 - ORA-01017: invalid username/password; logon denied
              Invalid User ID and password for signon.
              • 4. Re: I can't log in datamover with user ps
                Nicolas.Gasparotto
                Are you working on Oracle 11g+ ? How is the SYSADM's password ? Upper case or lower case ? Try to make it in upper case.
                In addition, make sure you configured the Configuration Manager with people/peop1e (by default it is).

                Nicolas.
                • 5. Re: I can't log in datamover with user ps
                  HakanBiroglu
                  Hi,

                  I think Nicolas, as usua,l has got it correctly.

                  I think you might be hitten case sensitive password issue with Oracle 11G.

                  Funny is that I ran into the same error some while ago and written a post on this issue. See my blogpost for more details.
                  http://bloggingaboutoracleapplications.org/peopletools-and-oracle-11g-installation-issues/

                  To keep it short:

                  I was able to log in Datamover with user sysadm and password sysadm, but I was not able to log in Datamover with user SYSADM and password SYSADM. So, there must be a case-sensitive issue.

                  The issue is caused by Oracle 11g initialization parameter SEC_CASE_SENSITIVE_LOGON

                  SEC_CASE_SENSITIVE_LOGON enables or disables password case sensitivity in the database. During the installation scripts user sysadm was created with password sysadm. When Datamover seeds the database it populated table PSACCESPRFL with user SYSADM and password SYSADM
                  UPDATE PSACCESSPRFL SET ACCESSID = 'SYSADM', SYMBOLICID = 'SYSADM1', ACCESSPSWD = 'SYSADM', VERSION = 0, ENCRYPTED = 0;

                  Whenever you try to log in to Datamover or Application Designer using a PeopleSoft userid, PeopleTools uses the ACCESSID and ACCESSPWD to connect to the database. With the parameter SEC_CASE_SENSITIVE_LOGON set to TRUE you are not able to log in, because PeopleTools is trying to log in with a password in capitals.

                  Changing parameter SEC_CASE_SENSITIVE_LOGON to FALSEenables you to log in Application Designer and Datamover with PeopleSoft userids.

                  Have your DBA change this parameter to false
                  alter system set sec_case_sensitive_logon=false;
                  • 6. Re: I can't log in datamover with user ps
                    918438
                    Thank you,guys!

                    I was hitten case sensitive password issue with Oracle 11G.

                    It worked perfectly after I changeed my password in table PSACCESSPRFL
                    • 7. Re: I can't log in datamover with user ps
                      Nicolas.Gasparotto
                      Even though you solved your problem, in addition of what was saying above, here a little bit more information, hopefully it will help to understand the trace analyzes for further issues.
                      You provided the traces, so let's explain briefly what is happening and the conclusion will be easier to understand :
                      1-2 23.55.35 0.098000 Cur#0.14236.HR91DEV RC=0 Dur=0.034000 Create Connection Info=Primary/HR91DEV/people/ Handle=03CCE7E8
                      Here it connects to the database with the connectid given in the Configuration Manager, here it is people. Since there's more input later on, the connectid and connectid's password are correct.
                      1-4 23.55.35 0.000000 Cur#1.14236.HR91DEV RC=0 Dur=0.000000 COM Stmt=SELECT OWNERID FROM PS.PSDBOWNER WHERE DBNAME=:1
                      Here it's checking if the database name given in the DataMover login screen match the database name of the DBOWNER table (this table has been granted for read to the connectid account).
                      1-11 23.55.35 0.000000 Cur#1.14236.HR91DEV RC=0 Dur=0.000000 COM Stmt=SELECT VERSION, OPERPSWD, ENCRYPTED, SYMBOLICID, ACCTLOCK FROM SYSADM.PSOPRDEFN WHERE OPRID = :1
                      Here it's taking information about the user given in the DataMover login screen (if there's not this user, it will assume a bootstrap mode connection and will do coming step differently), including password (if it's matching with the one given in the DataMover login screen, otherwise you're logged out), acctlock (if it's locked then you're logged out). And most important, it's taking the SYMBOLICID used later to take the accessid (owner of Peolesoft objects).
                      1-14 23.55.35 0.000000 Cur#1.14236.HR91DEV RC=0 Dur=0.000000 COM Stmt=SELECT ACCESSID, ACCESSPSWD, ENCRYPTED FROM SYSADM.PSACCESSPRFL WHERE SYMBOLICID = :1
                      With the SYMBOLICID taken in previous step, it's taking the corresponding ACCESSID and ACCESSID's password from PSACCESSPRFL.
                      1-17 23.55.35 0.000000 Cur#1.14236.HR91DEV RC=0 Dur=0.000000 Disconnect
                      DataMover disconnects from the database from connectid (people) to reconnects to the database with the ACCESSID taken in previous step.
                      1-19 23.55.35 0.046000 Cur#0.14236.HR91DEV RC=404 Dur=0.046000 Create Connection Info=Primary/HR91DEV/SYSADM/ Handle=00000000
                      Here, it's trying to connect to the database with the ACCESSID taken earlier, here it's SYSADM. The user SYSADM must exist in the database with the exact password in PSACCESSPRFL (ACCESSPSWD).
                      There's no more input in your trace, it means the connection with SYSADM's user failed.
                      The conclusion is that more likely, the ACCESSPSWD does not match the SYSADM's database password. It can be totally different, but one should keep in mind that from 11g onwards, the case sensitivity makes Upper!=UPPER. You could then either change the SYSADM's database password or ACCESSPSWD in PSACCESSPRFL.

                      You can find out more in an blog entry I wrote sometime ago :
                      http://gasparotto.blogspot.com/2010/03/peoplesoft-database-connectivity-part.html

                      HTH,

                      Nicolas.
                      • 8. Re: I can't log in datamover with user ps
                        user10122696
                        Many thanks to Nicolas for this thread. It was invaluable in helping me resolve my issue. I had upgraded a Financials database from PT8.45 to PT8.51 with the database at ORACLE 9i. After the upgrade I could log in to AppDesigner and DataMover with my OPRID, built/started appservers and webservers, etc.. NO PROBLEMS.
                        But my DBA exported the data and imported into an 11g database and I found myself unable to login to AppDesigner or DataMover with the same OPRID (I didn't even bother to try to start appservers). After much digging I discovered this post. After reading the post I realized that my encrypted ACCESSID and ACCESSPSWD values in PSACCESSPRFL were probably uppercase values. In bootstrap mode I ran the resetpswd.dms script to update the PSACCESSPRFL table with my lowercase ACCESS ID and lowercase ACCESS PSWD and reencrypt these. I confirmed with a select statement that my encrypted values were now changed. AND as I expected at this point my OPRID can once again log into the database in AppDesigner and DataMover.