Database as a Service (DBaaS) - Create Database Using OCI Console

-

Oracle Cloud Infrastructure

Database as a Service (DBaaS) - Create Database Service

In today’s session i will cover how to create database using DBaaS service on OCI.
 
  • Create SSH Key
  • Create Database Service using console
  • Connecting to the VM using SSH

Create SSH Key :
 
How to generate private public keys using putty.
Generate SSH keys:
 
Step 1: Go to Putty Key Generator.
 
 
 
 
 
Step2 : Move your cursor around the blank area to generate random data in key.
Step 3: Generated key appears under Public Key for pasting into OPENSSH authorized key file.
 
 
 
 
Step 4: Save Private keys
 
 
 
 
Step 5: Select all of the generated key that appears under Public key for pasting into OPENSSH authorized_key file, copy it , paste it into text file and then save the file on same location as the private key.
 
 
 
 
 
 
Create Database Service OCI console:
Log into your Oracle Cloud console using your credentials . if you don't have any account yet then you can create your personal trial account for 30 days on oracle cloud site.
 
 
Click here to create one for you.
Log into the Oracle Cloud and navigate to the Oracle Cloud Infrastructure (OCI) console.
Use the top-left menu to select the "Bare Metal, VM and Exadata" option.
 
 
Select the compartment and click on the "Launch DB System" tab.
It will ask you few information about database and network.
 
 
 
 
Chose Oracle Edition type in my case it it Enterprise Edition.
Paste ssh public keys which we had generated in step 1.
 
 
Chose VCN, Sunbet and mention any prefix which you want to add with host and domain URL.
Provide DB name, chose DB version you would like install, mention PDB if you want to create.
 
 
Check Automatic Backup if you like to create backup along with instance. I will do later so i am ignoring for now.
 
 
 
 
Click on Launch DB System.
Right after Launch DB system and it will be in provisioning state:
 
 
 
It will take some time so let's get coffee break . It took around 45 minute for me to provision DB instance.
 
 
 
 
DB is available now.
 
 
Let's explore little bit here .
Click in OCIDB Instance name:
 
 
Verify DB Details:
 
 
 
 
Click on Patches and see how many patch is available to apply on new instance.
 
 
Patching and Backup we will cover in later session.
 
 
Connecting to the VM using SSH:
 
Connect to the "opc" operating system user by specifying your private key and the public IP address from your DB Systems page.
 
Let's use putty in case of windows system:
Get Public IP from console and then open putty:
 
 
 
 
 
 
 
 
 
 
 
Click on SSH and auth and add your private keys file .
 
 
 
 
Click Open
 
 
 
 
Accept Yes
 
 
 
 
If you would like to connect to root, you must connect to the "opc" user and run them using "sudo".
 
 
We all set to connect to DB Instance.
 
Happy Learning .
In Next session we will see how to connect DB from SQL Developer.


Comments

Post a Comment

Popular posts from this blog

Workflow Agent Listener Service WF_DEFERRED + Business Event not processing

-
Workflow Agent Listener Service WF_DEFERRED Will Not Start, Mailer May Be Down To implement the solution, please execute the following steps: 1.  Use this query to identify any remaining items in wf_deferred queue: SQL> select corrid, decode(state, 0, '0 = Ready', 1, '1 = Delayed', 2, '2 = Retained', 3, '3 = Exception', to_char(state)) State, count(*) COUNT from wf_deferred group by corrid, state; 2. Items with the APPS corrid will not dequeue from agent listener via service container.  This runs the deferred listener from the command lin e . Make sure that the listener and workflow service components - including the mailer - are down before you run this . This is not intended to be a substitute for the normal operation of this service container from the OAM console. Use this only during this cleanup operation. One will have to run this script manually: begin wf_log_pkg.wf_debug_flag := TRUE; wf_event...
Read more

Output Post Processor - EBS 12.2.4 Troubleshoot

-
Output Post Processor TroubleShooting Issue 1 Output Post Processor is Down with Actual Process is 0 And Target Process is 1 1. Shutdown Concurrent Managers 2. To ensure concurrent manager down; check there is no FNDLIBR process running. ps -ef | grep FNDLIBR 3. Run adadmin to relink FNDSVC executable. a. Invoke adadmin from command prompt b. Choose option 2 (2. Maintain Applications Files menu) c. Choose option 1 (1. Relink Applications programs ) d. Then type FND When prompted; ( Enter list of products to link (all for all products) [all] : FND ) e. Ensure adrelink is exiting with status 0 4. Start Concurrent Managers 5. Check the Output Post Processor Issue 2 Concurrent Processing  R12 Output Post Processor Service Not Coming Up Reason : If Service Manager for the node is not running.  Possible cause might be service manager definition is missing under Concurrent ->Manager ->Define form. If the Service Manager is not pr...
Read more

How to Diagnose Workflow Notification Mailer Issue

-
Outbound Notification Emails : 1. Check if the notification is present in the recipient/user's Worklist/Notifications page.If it does not exist     then it means that notification itself is not created and need to check the corresponding workflow     status.You may also query the notification from the wf_notifications table SQL> select recipient_role,notification_id,status,mail_status from wf_notifications where recipient_role like '&user_name';    The e-mail notification is sent only if all of following are true.                --Notification status is OPEN or CANCELED                --Notification mail_status is MAIL or INVALID 2. Check Recipient role has a valid e-mail address and notification preference MAIL% SELECT email_address, nvl(WF_PREF.get_pref(name, 'MAILT...
Read more