My Oracle Support Banner

E-DB2: Need to Make Access Ids Different than Our Secondary Auth Ids Db2 (Doc ID 2953335.1)

Last updated on JUNE 05, 2023

Applies to:

PeopleSoft Enterprise PT PeopleTools - Version 8.59 and later
Information in this document applies to any platform.

Goal

There is one production database and multiple development databases; each has an Access ID being the same as one of the authorization IDs granted access to various tables.

Example list:

(1) HRINT database - Table owner HRINT / Secondary auth id HRINT1 with access to HRINT tables / Access ID HRINT1

(2) HRTST database - Table owner HRTST / Secondary auth id HRTST1 with access to HRTST tables / Access ID HRTST1

If a new Access ID is created, say HRINTA for the HRINT database, and give it secondary auth ids HRINT and HRINT1 (or just HRINT1), would this work?

There needs to be a SET CURRENT SQLID = HRINT1 performed, where would the code would get that HRINT1 value needed to access the right tables.

Documentation mentions that it may be better to use a single Access ID; if so, this Access ID would need to give to the secondary auth ids for all the databases.
 

Solution

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Goal
Solution


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.