4.1.2.4.1.2 SaaS Deployment of the Custom PLSQL Extensions

The prerequisite for SaaS Deployment of the Custom PLSQL Extensions would be a Successful Resolution of SR #1 and readiness of the deployment pipeline. These details will be published as part of the SR #1 status update.

Deployment of Archive

Customers are required to use My Oracle Support (MOS) portal and create a Service Request (SR) # 2 for requesting to deploy the Custom PLSQL extensions on their preferred SaaS instance.

Service Request #2 – for deploying the Custom PLSQL extension archive.

The following details must be used while raising an SR:

Project Name / ID	The Project Name / ID used while generating the Archive using Starter Kit Archive scripts
SaaS Instance Details	SaaS Instance tenancy details
Reference SR#	Reference to the SR# containing the successfully verified archives

Archive Deployment Service Request Status

SR status to be monitored by the Customers using MOS portal for the archive deployment updates.

Note:

** Separate SRs are required for deployment of archives into different SaaS Instances. For example: SR#1 = Test, SR#2 = Pre-Prod, SR#3 = Prod etc.