Drop Down MenusCSS Drop Down MenuPure CSS Dropdown Menu

ORA-27300: OS system dependent operation

-
When I tried to create a  new database for RAC environment using DBCA, It shows the error about invalid grid and diskgroup not mounted.
Error Details are
ORA-27300: OS system dependent operation:invalid_egid failed with status: 1
ORA-27301: OS failure message: Operation not permitted
ORA-27302: failure occurred at: skgpwinit6
ORA-27303: additional information: startup egid = 501 (oinstall), current egid = 502 (dba)
There was a permission problem.
[oracle@node1 ~]$ ls -l /u01/app/11.2.0/grid/bin/oracle
-rwxrwxr-x oracle dba 210824714 July 30 09:00 /u01/app/11.2.0/grid/bin/oracle

Solution :
Stop the ASM instance and then execute following command
[oracle@node1 ~]$ chmod 6751 /u01/app/11.2.0/grid/bin/oracle
[oracle@node1 ~]$ ls -l /u01/app/11.2.0/grid/bin/oracle
-rwsr-s–x 1 oracle dba 210824714 July 30 09:02 /u01/app/11.2.0/grid/bin/oracle

 Change the permission on second node grid home oracle binary file .
Start the ASM instance and then tried to create database using DBCA. It was successful.

Comments

Post a Comment

Popular posts from this blog

PostgreSQL DOMAIN Data Type -2

-
PRACTICAL 2 .CREATION OF DOMAIN WITHOUT CONSTRAINT: Consider the following scenario on PostgreSQL 9.3: Step 1 .Create a domain with no constraints: postgres=# CREATE DOMAIN zipcode AS text; CREATE DOMAIN Step 2 .Add a named constraint: postgres=# ALTER DOMAIN zipcode ADD CONSTRAINT zipcheck CHECK (char_length(VALUE) = 3); ALTER DOMAIN Step 3 .Check the Domain whether created or not: postgres=# \dD List of domains Schema | Name | Type | Modifier | Check --------+-------------+------+----------+------------------------------------------------------------------ public | postal_code | text | | CHECK (VALUE ~ '^\d{5}$'::text OR VALUE ~ '^\d{5}-\d{4}$'::text) public | zipcode | text | | CHECK (char_length(VALUE) = 3) (2 rows) Step 4 .Ctreate a table using "zipcode" Data type postgres=# create table details (name...
Read more

VMWARE WORKSTATION 3,4,5,6,7,8,9,10,11,12,14,15...etc LICENSE KEYS COLLECTION

-
Image
Below tutorialdba.com collected and sorted out hundreds of universal License Keys for all major versions of VMware Workstation Pro (not for VMware Workstation Player) 4.x, 5.x, 6.x, 7.x, 8.x, 9.x, 10.x, 11.x, 12.x and v14.x on Windows and Linux platforms (support both 32-bit and 64-bit operating system) in this single post. Besides, we also provide some license keys for VMware other projects. Just enjoy and share them. // 4~14 Universal License Keys // Version License Keys VMware Workstation VMware Workstation 4.x.x ZHDH1-UR90N-W844G-4PTN6 G1NP0-T88AL-M016F-4P8N2 ZC14J-4U16A-0A04G-4MEZP J1WF8-58LDE-881DG-4M8Q3 VMware Workstation 5.x.x LUXRM-WP0DN-A256U-4M9Q3 DJXDR-NDT27-Y2NDU-4YTZK DA925-HP80U-Z8HDC-4WXXP 3KW2W-AYR2C-88M6F-4MDQ2 VMware Workstation 6.x.x A0E8R-YUDFV-6AK2F-4GAN2 CRX0D-VWL0V-7CJ6C-46C7A NA8RX-QPNDU-D2LA9-4WAZL 1H4WM-N21FZ-7GK2A-44U5U 6AJ6N-THY2P-42KEF-4WTFG FK8R9-LPCDT-88H4Y-4WRN3 KAR8R-T8MAL-K8J6A-4WDXQ YJEKW-JMFF4-YA1DC-4WTQ...
Read more

Postgres Database Patch

-
If you are used to patch Oracle databases you probably know how to use opatch to apply PSUs. How does PostgreSQL handle this? Do we need to patch the existing binaries to apply security fixes? The answer is: No.Lets say you want to patch PostgreSQL from version 10.5/11.3 to version 10.10/11.5. This is called minor version postgres upgrade or postgres patching Why need to patch postgresql server  ? Multiple SQL injection vulnerabilities have been discovered in PostgreSQL that could allow for arbitrary code execution. The vulnerabilities are the result of the application’s failure to sufficiently sanitize user-supplied input before using it in an SQL query. These vulnerabilities allow attackers with the CREATE permission (or Trigger permission in some tables) to exploit input sanitation vulnerabilities in the pg_upgrade and pg_dump functions. The CREATE permission is automatically given to new users on the public schema, and the public schema is the default schema used on the...
Read more

How to find the server is whether standby (slave) or primary(master) in Postgresql replication ?

-
Method 1 You can check the mode of the server using "pg_controldata". [pgsql@test~]$ pg_controldata /usr/local/pgsql/data84/ Database cluster state: in archive recovery --> This is Standby Database Database cluster state: in production --> This is Production Database [Master] Method 2 You can use pg_is_in_recovery() which returns True if recovery is still in progress(so the server is running in standby mode or slave) postgres=# select pg_is_in_recovery(); pg_is_in_recovery ------------------- t (1 row) If Return    false   so the server is running in primary mode or master postgres=# select pg_is_in_recovery(); pg_is_in_recovery ------------------- f (1 row)
Read more

PostgreSQL Database startup / shutdown /restart

-
Pg_ctl Utility & Postgresql Service to do the same thing: Start the postgres server in the background. Without PGDATA set, “pg_ctl start” needs needs the additional  -D /datadir   argument in order to start. you can start/stop the postgresql server as root user as well as postgres user root user: “ service postgresql start “ “ /etc/init.d/postgresql  start “, or “ systemctl start postgresql-10 ” – this is for redhat linux above version 6 postgres or edb user: Pg_ctl is only applicable for postgres user or edb user if you are a Enterprisedb su – postgres ./ pg_ctl start  -D /opt/PostgreSQL/9.3/data By using following anyone methods you can start,stop,reload else restart the postgresql server By using Pg_ctl Utility Postgresl -9.3 Script By using Postgresql Service 1. pg_ctl utility – as postgres user: using pg_ctl you can start/stop/reload/restart the postgresql server this utility can only permitted to access as postgres...
Read more