You are right that this should never (or very rarely) happen, But I had
something similar happen in my cloud trial trying to create a 12.2 RAC
database. It was created after 4 hours but when I looked at the logs it showed
the first attempt failed, timing out after 3 hours. Then it tried again and
succeeded after about an hour.
My advise would be to start again and it may work the next time.
Keith
On Jun 1, 2018, at 12:09 AM, Leyi Zhang <kamusis@xxxxxxxxx> wrote:
Hi Lists:
I’m trying to get some experience for Oracle 18c, so I decide to use Oracle
Cloud free USD300 credit to create a Oracle 18c RAC service.
But I failed.
I post the issue on the Oracle community forums, but get no answer yet, so
I’m thinking maybe gurus here can help me.
Here is the link of the post:
https://community.oracle.com/thread/4149124 ;
<https://community.oracle.com/thread/4149124>
For convince, I post the log here:
May 30, 2018 2:33:16 PM UTC Activity Submitted
May 30, 2018 2:33:16 PM UTC Activity Started
May 30, 2018 2:33:44 PM UTC Created Compute resources for Database Server...
May 30, 2018 2:43:28 PM UTC SSH access to VM [DB_1/vm-1] succeeded...
May 30, 2018 2:43:28 PM UTC SSH access to VM [DB_1/vm-2] succeeded...
May 30, 2018 3:39:54 PM UTC Failed to configure RAC Oracle Database
Server...[failed to create database orcl, got exceptionfailed to create
database orcl]
May 30, 2018 3:39:54 PM UTC Initiating Database Service Termination...
May 30, 2018 3:39:54 PM UTC Skipping delete backups for Database Service
instance [dbcloud18c] since the request parameter for delete backups is not
set.
May 30, 2018 3:45:32 PM UTC Stopped all Compute resources...
May 30, 2018 3:45:43 PM UTC Removed Compute resources...
May 30, 2018 3:45:49 PM UTC Database Service record removal complete...
May 30, 2018 3:45:53 PM UTC Activity Started
May 30, 2018 3:46:03 PM UTC Created Compute resources for Database Server...
May 30, 2018 5:49:21 PM UTC Timed out after waiting 120 minutes to start
the Compute resources... The orchestration
/Compute-602932719/kamusis@xxxxxxxxx/dbaas/dbcloud18c/1/db_1/vm-2
<http://kamusis@xxxxxxxxx/dbaas/dbcloud18c/1/db_1/vm-2> is in 'error' state
since Wed May 30 2018 15:48:42:000 OPlan [launchplan]: re-launching
instances: dbcloud18c db_1 2 Instance [dbcloud18c db_1 2]: Cannot satisfy the
placement, relationship and resource requirements.
May 30, 2018 5:49:22 PM UTC Initiating Database Service Termination...
May 30, 2018 5:49:22 PM UTC Skipping delete backups for Database Service
instance [dbcloud18c] since the request parameter for delete backups is not
set.
May 30, 2018 5:52:45 PM UTC Stopped all Compute resources...
May 30, 2018 5:52:56 PM UTC Removed Compute resources...
May 30, 2018 5:53:01 PM UTC Database Service record removal complete...
May 30, 2018 5:53:02 PM UTC Activity Ended
Actually I have 2 questions:
1. How can I do troubleshooting when a Oracle cloud service creation request
failed?
2. As a public cloud platform, in my opinion, this type of issue should never
happened, as I said in the post, “ If you let me submit a service creation
request successfully, then you should create it successfully. That is
cloud.”, how do you guys think?
Thanks.
--
Kamus <kamusis@xxxxxxxxx <mailto:kamusis@xxxxxxxxx>>
Visit my blog for more : http://www.dbform.com ;<http://www.dbform.com/>
Join ACOUG: http://www.acoug.org ;<http://www.acoug.org/>
