Tag Archives: DBA

[Solved] Error 4 opening dom ASM/Self in 0x8283c00

Installing Oracle RAC 19.3.0.0 on RHEL 7.9, in the run root.sh script step of the installation GI, it runs normally on the first node, but Error 4 opening dom ASM/Self in 0x8283c00 occurs when running the root.sh script on the second node

Root.sh script executed successfully in node 1

Problem running root.sh script on node 2

Creating /etc/oratab file...
Entries will be added to the /etc/oratab file as needed by
Database Configuration Assistant when a database is created
Finished running generic part of root script.
Now product-specific root actions will be performed.
Relinking oracle with rac_on option
Using configuration parameter file: /u01/app/19.0.0/grid/crs/install/crsconfig_params
The log of current session can be found at:
  /u01/app/grid/crsdata/momdb2/crsconfig/rootcrs_momdb2_2022-06-19_11-05-10AM.log
2022/06/19 11:05:13 CLSRSC-594: Executing installation step 1 of 19: 'SetupTFA'.
2022/06/19 11:05:14 CLSRSC-594: Executing installation step 2 of 19: 'ValidateEnv'.
2022/06/19 11:05:14 CLSRSC-363: User ignored prerequisites during installation
2022/06/19 11:05:14 CLSRSC-594: Executing installation step 3 of 19: 'CheckFirstNode'.
2022/06/19 11:05:14 CLSRSC-594: Executing installation step 4 of 19: 'GenSiteGUIDs'.
2022/06/19 11:05:14 CLSRSC-594: Executing installation step 5 of 19: 'SetupOSD'.
2022/06/19 11:05:14 CLSRSC-594: Executing installation step 6 of 19: 'CheckCRSConfig'.
2022/06/19 11:05:15 CLSRSC-594: Executing installation step 7 of 19: 'SetupLocalGPNP'.
2022/06/19 11:05:16 CLSRSC-594: Executing installation step 8 of 19: 'CreateRootCert'.
2022/06/19 11:05:16 CLSRSC-594: Executing installation step 9 of 19: 'ConfigOLR'.
2022/06/19 11:05:23 CLSRSC-594: Executing installation step 10 of 19: 'ConfigCHMOS'.
2022/06/19 11:05:23 CLSRSC-594: Executing installation step 11 of 19: 'CreateOHASD'.
2022/06/19 11:05:24 CLSRSC-594: Executing installation step 12 of 19: 'ConfigOHASD'.
2022/06/19 11:05:24 CLSRSC-330: Adding Clusterware entries to file 'oracle-ohasd.service'
2022/06/19 11:05:35 CLSRSC-4002: Successfully installed Oracle Trace File Analyzer (TFA) Collector.
2022/06/19 11:06:01 CLSRSC-594: Executing installation step 13 of 19: 'InstallAFD'.
2022/06/19 11:06:27 CLSRSC-594: Executing installation step 14 of 19: 'InstallACFS'.
2022/06/19 11:07:02 CLSRSC-594: Executing installation step 15 of 19: 'InstallKA'.
2022/06/19 11:07:03 CLSRSC-594: Executing installation step 16 of 19: 'InitConfig'.
2022/06/19 11:07:10 CLSRSC-594: Executing installation step 17 of 19: 'StartCluster'.
2022/06/19 11:11:03 CLSRSC-343: Successfully started Oracle Clusterware stack
2022/06/19 11:11:03 CLSRSC-594: Executing installation step 18 of 19: 'ConfigNode'.
2022/06/19 11:11:11 CLSRSC-594: Executing installation step 19 of 19: 'PostConfig'.
2022/06/19 11:11:26 CLSRSC-325: Configure Oracle Grid Infrastructure for a Cluster ... succeeded
***Error 4 opening dom ASM/Self in 0x8283c00
Domain name to open is ASM/Self 
Error 4 opening dom ASM/Self in 0x8283c00***

According to MOS: 19C: While Executing Root.sh on Remote Nodes HIT UNEXPECTED “ERROR 4 OPENING DOM ASM/SELF IN 0x57f7d60” (Doc ID 2571719.1) description, this issue has no effect on the installation and can be ignored

How to Solve gtid master-slave replication connecting Issue

Project scenario:

Master slave connection method

Problem Description:

Last_IO_Errno: 2003 Last_IO_Error: error connecting to master '[email protected]:3306' - retry-time: 60 retries: 7

Cause analysis:

    1. when trying to log in to the master database to copy users from the server, an error of 113 is found

[ root@localhost mysql]# mysql -urepl -p123 -h 192.168.8.131 -P 3306 mysql: [Warning] Using a password on the command line interface can be insecure. Error 2003 (HY000): can't connect to MySQL server on '192.168.8.131' (113)

    1. check whether the main server firewall is closed. It is found that it is closed. It is speculated that the port is not open

systemctl status firewalld service

    1. 3. Check whether the 3306 port of the main database is open to the public. It is found that it is no

firewall CMD -- zone = public -- Query port = 3306/TCP

    1. 4 Open 3306 port

firewall CMD -- zone = public -- add port = 3306/TCP -- permanent

    1. 5 Update firewall

firewall CMD -- reload

 

Solution:

The master-slave replication connecting problem is mainly caused by the master and slave libraries can not be connected, after this problem found that although the firewall has been closed, but the port is not necessarily open to the public state, you need to set their own.

Oracle Database Cannot Open mount Mode Error: ORA-01102

Error in opening mount mode of database: ora-01102: cannot mount database in exclusive mode

SQL> startup nomount;
 
ORACLE instance started.

Total System Global Area 1073741824 bytes
Fixed Size		    2932632 bytes
Variable Size		  427819112 bytes
Database Buffers	  629145600 bytes
Redo Buffers		   13844480 bytes
SQL> SQL> alter database mount;
 
alter database mount
*
ERROR at line 1:
ORA-01102: cannot mount database in EXCLUSIVE mode

Reason: There is a “sgadef.dbf” file in the “ORACLE_HOME/dbs” directory and Oracle processes (pmon, smon, lgwr, and dbwr) still exist – even if the database is closed, the shared memory segments and semaphores still exist – there is an “ORACLE_HOME/dbs/lk” file “lk” and “sgadef. There is an “ORACLE_HOME/dbs/lk” file “lk” and “sgadef. dbf ” files for locking shared memory. It seems that even if no memory is allocated, Oracle thinks the memory is still locked.
To view the startup log:


Solution.
1. Go to /d01/oracle/PROD/db/tech_st/12.1.0/dbs/ directory
2. Delete the lkPOD file

rm -rf  lkPROD

3. Make sure Oracle has no background processes: ps -ef |grep ora_ |grep PROD|grep ora_dbw0_PROD

if there is a background process, please use the command “kill” to delete it.

[oracle@ebs ~]$  kill -9 1912

Log in again using mount mode

[oracle@ebs ~]$ sqlplus/as sysdba

SQL*Plus: Release 12.1.0.2.0 Production on Wed Mar 2 12:52:42 2022

Copyright (c) 1982, 2014, Oracle.  All rights reserved.

Connected to an idle instance.

SQL> startup mount
ORACLE instance started.

Total System Global Area 1073741824 bytes
Fixed Size		    2932632 bytes
Variable Size		  427819112 bytes
Database Buffers	  629145600 bytes
Redo Buffers		   13844480 bytes
Database mounted.

Successfully resolved.

Oracle Start as DBA Error [How to Solve]

Problem Description:

In the morning, I created Oracle11g on the new machine and reported an error when starting with the startup command:

This error message means:
ora-00119: the initialization parameters of the system are invalid

Ora-00132: unresolved network listener name

My understanding: there is a problem with the listening configuration in the initialization file. It cannot be initialized and listening cannot be started.

Troubleshooting direction:

View the initialization file. Everyone has different installation paths.

The initialization file must exist in the Oracle installation directory orcl. My path:

Open the initialization file in Notepad and find the local listening configuration: local_Listener: the original local listening configuration parameter is listener_ORCL

Now, change it to:

local_listener=(ADDRESS = (PROTOCOL = TCP)(HOST = localhost)(PORT = 1521)

verification:

Load initialization file synchronously at startup:

The database started successfully.

[Solved] MYSQL Command Execute Error: Can ‘t connect to local MySQL server through socket ‘/tmp/mysql.sock ‘(2) “

Description

Today, when adding a MySQL slave node to the online production environment, the following error was reported when executing the command to back up MySQL data:

Can 't connect to local MySQL server through socket '/tmp/mysql.sock '(2) "

The general meaning of error reporting is that MySQL under TMP cannot be found Sock file

Solution:

1. First find mysql Directory where the sock is located

find/-name mysql.sock

2. Create/TMP/MySQL Sock soft connect to the file
establish a soft connection (write an absolute path):

ln -s /var/lib/mysql/mysql.sock /tmp/mysql.sock

If the manual residual soft connection is wrong, you can delete it with the following command:

rm -rf /tmp/mysql.sock

Re-execute MySQL command, perfect solution!!