Sometimes DBAs have to change CDB/PDB names to meet the organization’s naming standards, and change the DBID of a cloned database to make sure database registered in RMAN recovery catalog.
This post illustrates how to rename CDB/PDB, change DBID, and move and rename datafiles/tempfiles/controlfiles of CDB/PDB.
Read more of this content when you subscribe today.
After database name has been changed, the controlfiles are still staying in the directory of old database, so we need relocate them into directory of new database name.
Read more of this content when you subscribe today.
In this post, I am going to install Oracle 18c RAC software, and create a 18c RAC database in silent mode.
This post will also apply to how to install Oracle 19c RAC software, and create a 19c RAC database in silent mode.
Read more of this content when you subscribe today.
There are repeating following errors in 19c CRS alert.log by ologgered trying to connect to GIMR.
Fatal NI connect error 12516, connecting to: (DESCRIPTION=(CONNECT_TIMEOUT=60)(ADDRESS=(PROTOCOL=tcp)(HOST=racnode-cluster-scan.virtuallab)(PORT=1521))(CONNECT_DATA=(SERVICE_NAME=GIMR_DSCREP_10)(CID=(PROGRAM=ologgerd)(HOST=racnode1.virtuallab)(USER=root)))(SECURITY=(ENCRYPTION_CLIENT=requested))) VERSION INFORMATION: TNS for Linux: Version 19.0.0.0.0 - Production TCP/IP NT Protocol Adapter for Linux: Version 19.0.0.0.0 - Production Version 19.8.0.0.0 Time: 08-AUG-2020 18:15:01 Tracing not turned on. Tns error struct: ns main err code: 12564 TNS-12564: TNS:connection refused ns secondary err code: 12560 nt main err code: 524 TNS-00524: Current operation is still in progress nt secondary err code: 115 nt OS err code: 0
Check mgmtlsnr or SCAN listeners, and found -MGMTDB PDB service ” gimr_dscrep_10″ is not registered properly.
[grid@racnode1 trace]$ lsnrctl services listener_scan2 ... .. . Service "gimr_dscrep_10" has 1 instance(s). Instance "-MGMTDB", status READY, has 1 handler(s) for this service… Handler(s): "DEDICATED" established:0 refused:0 state:blocked REMOTE SERVER (ADDRESS=(PROTOCOL=TCP)(HOST=172.16.100.62)(PORT=1526))
Read more of this content when you subscribe today.
Just after applied the latest 19c GI July 2020 RU, any operations on diskgroups will cause the following errors :
ORA-15032: not all alterations performed ORA-15137: The ASM cluster is in rolling patch state.
Read more of this content when you subscribe today.
-racnode1
[grid@racnode1 ~]$ kfod op=patches List of Patches 31281355 31304218 31305087 31335188 [grid@racnode1 ~]$
ASMCMD> showclusterstate Normal ASMCMD>
[grid@racnode1 ~]$ crsctl query crs softwarepatch Oracle Clusterware patch level on node racnode1 is [441346801]. [grid@racnode1 ~]$
[grid@racnode1 ~]$ crsctl query crs releasepatch Oracle Clusterware release patch level is [441346801] and the complete list of patches [31281355 31304218 31305087 31335188 ] have been applied on the local node. The release patch string is [19.8.0.0.0]. [grid@racnode1 ~]$
-racnode2
[grid@racnode2 ~]$ kfod op=patches List of Patches 31281355 31304218 31305087 31335188 [grid@racnode2 ~]$
ASMCMD> showclusterstate Normal ASMCMD>
[grid@racnode2 ~]$ crsctl query crs softwarepatch Oracle Clusterware patch level on node racnode2 is [441346801]. [grid@racnode2 ~]$
[grid@racnode2 ~]$ crsctl query crs releasepatch Oracle Clusterware release patch level is [441346801] and the complete list of patches [31281355 31304218 31305087 31335188 ] have been applied on the local node. The release patch string is [19.8.0.0.0]. [grid@racnode2 ~]$
Make DBA Life Easy 