cloning a database server (without closing asm and database)

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

cloning a database server (without closing asm and database)

claudiu
Hello Erman,

I hope you are good in these days, I neep help about that I mentioned about subject..
We cloned the linux sever without closing asm and database and now while trying to open asm  we are facing an error like below;

sqlplus / as sysasm
startup
ORA-01078: failure in processing system parameters
ORA-29701: unable to connect to Cluster Synchronization Service

And decided to remove olf conf;

After roothat.pl deconfig i am trying to new roothas.pl ;

[root@xxx install]# ./roothas.pl
Using configuration parameter file: ./crsconfig_params
The log of current session can be found at:
  /u01/app/oracle/crsdata/xxxclone/crsconfig/roothas_2020-05-06_09-12-53AM.log
LOCAL ADD MODE
Creating OCR keys for user 'oracle', privgrp 'oinstall'..
Operation successful.
LOCAL ONLY MODE
Successfully accumulated necessary OCR keys.
Creating OCR keys for user 'root', privgrp 'root'..
Operation successful.
CRS-4664: Node xxxclone successfully pinned.
2020/05/06 09:13:07 CLSRSC-330: Adding Clusterware entries to file 'oracle-ohasd.service'
2020/05/06 09:15:13 CLSRSC-214: Failed to start the resource 'ohasd'
Failed to start the Clusterware. Last 20 lines of the alert log follow:
2020/05/06 09:15:13 CLSRSC-318: Failed to start Oracle OHASD service
Died at crsinstall.pm line 2775.


When i checke the roothas.pl log file;


Executing cmd: /usr/bin/systemctl start oracle-ohasd.service
Executing cmd: /u01/app/oracle/product/12.2.0/grid/bin/crsctl start has
Command output:
>  CRS-4124: Oracle High Availability Services startup failed.
>  CRS-4000: Command Start failed, or completed with errors.
>End Command output
Executing /etc/init.d/ohasd install
Executing cmd: /etc/init.d/ohasd install
Executing cmd: /u01/app/oracle/product/12.2.0/grid/bin/clsecho -p has -f clsrsc -m 214 "ohasd"
Command output:
>  CLSRSC-214: Failed to start the resource 'ohasd'
>End Command output
CLSRSC-214: Failed to start the resource 'ohasd'
ohasd failed to start
Alert log is /u01/app/oracle/product/12.2.0/grid/log/xxxclone/alertxxxclone.log
Failed to start  service 'ohasd'
Executing cmd: /u01/app/oracle/product/12.2.0/grid/bin/clsecho -p has -f clsrsc -m 318
Command output:
>  CLSRSC-318: Failed to start Oracle OHASD service
>End Command output
CLSRSC-318: Failed to start Oracle OHASD service
###### Begin DIE Stack Trace ######
    Package         File                 Line Calling  
    --------------- -------------------- ---- ----------
 1: main            roothas.pl            151 crsutils::dietrap
 2: crsinstall      crsinstall.pm        2775 main::__ANON__
 3: crsinstall      crsinstall.pm        1164 crsinstall::start_siha_ohasd
 4: crsinstall      crsinstall.pm         936 crsinstall::config_ohasd_siha
 5: crsinstall      crsinstall.pm         360 crsinstall::HAInstall
 6: main            roothas.pl            260 crsinstall::new
####### End DIE Stack Trace #######
Reply | Threaded
Open this post in threaded view
|

Re: cloning a database server (without closing asm and database)

ErmanArslansOracleBlog
Administrator
Thanks claudiu. I m fine:) I hope you are fine too..

The information you provided is insufficient for dealing with this issue.
Still, I will try to help. Probably, /etc/init.d/ohasd fails during its execution.

1)
This might me related with the hostname of your node. (as this is a clone server, this is a very possible cause) - addressed here -> root.sh fails while starting ohasd in Oracle Restart 12.1.0.2 Grid Installation (Doc ID 2548031.1)

Ensure your hostname is correct.
-Change the hostname to the correct name.
-update hostname in /etc/hosts file accordingly and retry.

2) This problem might be due to the insufficient storage on temp filesystem or a bug

Check the issue addressed here ->
root.sh fails with CLSRSC-214: Failed To Start 'ohasd' and rootupgrade.sh due to Existing Checkpoint File (Doc ID 1910022.1)

If the actions above is not useful for you, then I need to see related errors in /var/log/messages, ohasd log and rootcrs log files. 
Please mask your logs so that no real hostname or ip can be seen .