Instructions and Clarification on Performing RMS 1603 Upgrade with 19c Database
(Doc ID 2687469.1)
Last updated on MARCH 16, 2022
Applies to:Oracle Retail Merchandising System - Version 15.0.3 to 16.0.3 [Release 15.0 to 16.0]
Information in this document applies to any platform.
This document contains questionnaire regarding Instructions and Clarification on Performing Oracle Retail Merchandising System (RMS) 1603 Upgrade with 19c Database.
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
|Questions and Answers|
|Per the RMS 1603 installation guide, the following jars is suggested to be dropped. Are these jars fully deprecated in 19c or is there any 19c equivalent versions that need to be loaded post 19c upgrade?|
|What are the instructions to perform the below for post 19c upgrade as its not mentioned in RMS 1603 IG ?|
|Are the below steps listed in the RMS 1603 install guide mandatory for RMS functionality?|
|From above implemetation guide, On item 7 under section "Grant permission to the user", what is the "basename" directory here ?|
|Under section "Load RBO Oracle Objects into the database" , can this step be skipped as the same rib type objects are already available under RMS schema as well?|
|The document links mentions about granting "DBA" role to the <WEB_SERVICE_CALLER_USER> i.e. "RMS" user in this case. Does DBA privileges needs to be assigned to RMS user ?|
|Is this upgrade approach certified, Current state (RMS 16.0.2 & 12c DB) => Upgrade to RMS 16.0.3(keeping DB 12c) => Later DB upgrade to 19c?|
|If a customer wants to upgrade from RMS 16.0.2 to 16.0.3, is it mandatory to upgrade the database to 19c ?|