Siebel System Admin, Install and Upgrade (MOSC)

MOSC Banner

S_APP_KEY License key activation after upgrade

  1. We have upgraded from IP14 to 24.x version. I noticed the utility uses the following SQL query to update the database. Since we have nearly 300 records, I'd like to confirm whether we can use this SQL update query directly on the database to activate the license.

UPDATE dbo.S_APP_KEY
SET INACTIVE_FLG='N', LAST_UPD = 'YYYY-MM-DD HH:MM:SS'
WHERE MODULE_NAME IN ('Siebel Tools', 'Siebel eCustomer, SPE', 'Siebel eSales, SPE', 'Siebel eService, SPE');

Can we proceed with this method, or is there a preferred approach for activating the license in bulk for all the records?

  1. Additionally, I observed that when we perform a Full RR from DEV to UAT, the S_APP_KEY table is included in the DDLimport log. If we activate it in DEV and then move the Full RR, does this mean we do not need to activate it again in the RR environments like UAT and PROD? Or should we run this utility in both DR and RR environments as well?

Howdy, Stranger!

Log In

To view full details, sign in to My Oracle Support Community.

Register

Don't have a My Oracle Support Community account? Click here to get started.

Category Leaderboard

Top contributors this month

New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center