prim11865:Changing User Ids and Passwords used in a Primavera Oracle Database

Changing User Ids and Passwords used in a Primavera Oracle Database

In The Database 

Focusing first on understanding how User Ids and passwords are created in a Primavera database using the manual scripted approach, the following excerpt is taken from the v5.0 manual database install script orpm_ins.sql. This piece of the script deals with creating the default User Ids and applying the necessary grants. The default User Ids are admuser, privuser and pubuser with matching default passwords. The script must be modified to use custom naming conventions for User Ids and/or passwords either matching or not matching.

                                prompt creating PMDB users

                                create user admuser
                                        identified by admuser
                                        temporary tablespace temp
                                       default   tablespace PMDB_dat1;

                               grant DBA to admuser;

                               create user privuser
                                       identified by privuser
                                       temporary tablespace temp
                                      default   tablespace PMDB_dat1;

                              grant connect               to privuser;

                              create user pubuser
                                      identified by pubuser
                                      temporary tablespace temp
                                     default   tablespace PMDB_dat1;

                             grant connect to pubuser;

                             prompt completed creating PMDB users

 ___________________________________________________________________

The Configasst.exe wizard takes the approach of creating User Ids with matching passwords while allowing you to utilize your own naming conventions. Instead of using admuser, privuser, and pubuser; you have the option to use for example red, white, and blue, or any naming convention you require. And by default the passwords that will be created will also be red, white and blue matching these or any User Ids you specify.

To customize the passwords to be different than the User Ids specified in the wizard, a DBA must alter the identified by statements after the database is created.

i.e.:alter user << username >> identified by << password >>;

In The Client Applications

By default the client applications install utilizes pubuser with pubuser as the password for the database alias and privuser with privuser as the password for the private user configuration. In order for the client applications to successfully connect to the databases the DBConfig for the applications must be reconfigured to match the User Ids and passwords specified in the databases.

For the Public Login the public group id remains unchanged, while the Username and Password are changed to match the database.

For the Private database login, first login with the proper Administrative User account.

And then the Private Database Users must be reconfigured to match the User Ids and passwords in the databases. Again leave the Public group Id unchanged.

In myPrimavera

By default the myPrimavera install utilizes the username privuser with privuser as the password for the database configuration. In order for myPrimavera  to successfully connect to the database the Administrator properties must be reconfigured to match the privuser password specified in the database.

In Timesheets Group Server

By default the Timesheets, Group Server install utilizes privuser with privuser as the password for the database connection. In order for the Group Server to successfully connect to the database the TPGS Administrator properties must be reconfigured to match the privuser password specified in the database.

In the SDK Software Development Kit 

By default the SDK install utilizes pubuser with pubuser as the password for the database configuration. In order for the SDK to successfully connect to the database the Username and Password are changed to match the database. The public group id remains unchanged.

In the Primavera Compression Server 

By default the Primavera Compression Server client configuration utilizes the username pubuser with pubuser as the password for the database configuration. In order for the Primavera Compression Server client to successfully connect to the database the Username and Password are changed to match the database.

 By default the Primavera Compression Server, server configuration utilizes the username pubuser with pubuser as the password for the database configuration. In order for the Primavera Compression Server, server to successfully connect to the database the Username and Password are changed to match the database.