Oracle 26ai- Installing Oracle Grid Infrastructure for a Standalone Server Using the Command-Line Interface

By -

 Before Oracle AI Database 26ai, Oracle Grid Infrastructure could be installed using a response file.

For example(using a response file):

./gridSetup.sh -silent \
INVENTORY_LOCATION=/oraInventory \
SELECTED_LANGUAGES=en \
ORACLE_BASE=/grid/base \
oracle.install.option=HA_CONFIG \
oracle.install.asm.OSDBA=asmdba \
oracle.install.asm.OSOPER=asmoper \
oracle.install.asm.OSASM=asmadmin \
oracle.install.crs.config.autoConfigureClusterNodeVIP=false \
oracle.install.asm.diskGroup.name=ASM \
oracle.install.asm.diskGroup.redundancy=EXTERNAL \
oracle.install.asm.diskGroup.diskDiscoveryString='ORCL:*' \
oracle.install.asm.diskGroup.disks=ORCL\:ASM01 \
oracle.install.asm.SYSASMPassword=Your_Password \
oracle.install.asm.monitorPassword=Your_Password \
-ignorePrereqFailure

At the end of the installation, the installer displays a message similar to the following:

As install user, execute the following command to complete the configuration.
        /grid/19.25/gridSetup.sh -executeConfigTools -responseFile /grid/19.25/install/response/grid_2025-03-28_08-34-17AM.rsp [-silent]

Therefore, we should use a response file such as the following:

[grid@OL95 ~]$ cat /grid/19.25/install/response/gridsetup.rsp
oracle.install.responseFileVersion=/oracle/install/rspfmt_crsinstall_response_schema_v19.0.0
INVENTORY_LOCATION=/oraInventory
oracle.install.option=HA_CONFIG
ORACLE_BASE=/grid/base
oracle.install.asm.OSOPER=asmoper
oracle.install.asm.OSASM=asmadmin
oracle.install.asm.OSDBA=asmdba
oracle.install.asm.SYSASMPassword=Deraz_Kolah_122_Kebria
oracle.install.asm.diskGroup.name=ASM
oracle.install.asm.diskGroup.redundancy=EXTERNAL
oracle.install.asm.diskGroup.disks=ORCL:ASM01
oracle.install.asm.diskGroup.diskDiscoveryString=ORCL:*
oracle.install.asm.monitorPassword=Deraz_Kolah_122_Kebria

Starting with Oracle AI Database 26ai, Oracle Grid Infrastructure can be installed and configured using the command-line interface. Oracle provides the -configureCluster and -configureStandaloneServer options for the gridSetup.sh command. The -configureCluster option is used to configure Oracle Grid Infrastructure for a cluster, while the -configureStandaloneServer option is used to configure Oracle Grid Infrastructure for a standalone server.
In this article, I will show how to install and configure Oracle Grid Infrastructure on a standalone server using the -configureStandaloneServer option.
As the grid user, run the following command:

[grid@OL95 26ai]$ ./gridSetup.sh  -silent -configureStandaloneServer \
  -OSDBA asmdba \
  -OSASM asmadmin \
  -OSOPER asmoper \
  -ORACLE_BASE /grid/base \
  -dbDiskGroupName ASM \
  -diskList 'ORCL:ASM' \
  -redundancy EXTERNAL \
  -diskString 'ORCL:*'  \
  -executeRootScript \
  -configMethod root \
  -auSize 64 \
  -INVENTORY_LOCATION /oraInventory
Launching Oracle Grid Infrastructure Setup Wizard...

Enter password for SYS user:

Confirm password:

Enter password for ASMSNMP user:

Confirm password:


 Enter password for 'root' user:

 The response file for this session can be found at:
 /grid/26ai/install/response/grid_2026-08-16_08-52-51PM.rsp

You can find the log of this install session at:
 /tmp/GridSetupActions2026-08-16_08-52-51PM/gridSetupActions2026-08-16_08-52-51PM.log
[ Start ] NETCA - 2026-08-16 20:57:42.784
Command: /bin/sh -c /grid/26ai/bin/netca /orahome /grid/26ai /instype typical /inscomp client,oraclenet,javavm,server,ano /insprtcl tcp /cfg local /authadp NO_VALUE /responseFile /grid/26ai/network/install/netca_typ.rsp /silent  /orahnam OraGI23Home1  /ouiinternal

Parsing command line arguments:
    Parameter "orahome" = /grid/26ai
    Parameter "instype" = typical
    Parameter "inscomp" = client,oraclenet,javavm,server,ano
    Parameter "insprtcl" = tcp
    Parameter "cfg" = local
    Parameter "authadp" = NO_VALUE
    Parameter "responsefile" = /grid/26ai/network/install/netca_typ.rsp
    Parameter "silent" = true
    Parameter "orahnam" = OraGI23Home1
    Parameter "ouiinternal" = true
Done parsing command line arguments.
Oracle Net Services Configuration:
Profile configuration complete.
Oracle Net Listener Startup:
    Listener started successfully.
Listener configuration complete.
Oracle Net Services configuration successful. The exit code is 0
[ Exit Code ] 0
[ End ] NETCA - 2026-08-16 20:57:51.741

[ Start ] ASMCA - 2026-08-16 20:57:51.883
Command: /bin/sh -c /grid/26ai/bin/asmca -silent -oui_internal -configureASM -diskString 'ORCL:*' -diskGroupName ASM -diskList 'ORCL:ASM' -redundancy EXTERNAL -au_size 64
SYS_PASSWORD_PROMPT
ASMSNMP_PASSWORD_PROMPT

ASM has been created and started successfully.

[DBT-30001] Disk groups created successfully. Check /grid/base/cfgtoollogs/asmca/asmca-260816PM085752.log for details.

[ Exit Code ] 0
[ End ] ASMCA - 2026-08-16 20:59:03.73

[ Start ] CVU - 2026-08-16 20:59:03.83
Command: /bin/sh -c /grid/26ai/bin/cluvfy  stage -post hacfg

Performing following verification checks ...

  Oracle Restart Integrity ...PASSED
  OLR Integrity ...PASSED

Post-check for Oracle Restart configuration was successful.

CVU operation performed:      stage -post hacfg
Date:                         Aug 16, 2026, 8:59:04 PM
CVU version:                  23.26.2.0.0 (032926x8664)
CVU home:                     /grid/26ai
Grid home:                    /grid/26ai
User:                         grid
Operating system:             Linux5.15.0-302.167.6.el9uek.x86_64
Successfully Setup Software with warning(s).
[ Exit Code ] 0
[ End ] CVU - 2026-08-16 20:59:13.758

Moved the install session logs to:
 /oraInventory/logs/GridSetupActions2026-08-16_08-52-51PM

The command completes the Oracle Grid Infrastructure configuration and creates and starts the ASM instance. After the configuration completes successfully, we can verify the ASM instance by connecting to it using SQL*Plus as SYSASM:

[grid@OL95 ~]$ sqlplus "/as sysasm"
SQL*Plus: Release 23.26.2.0.0 - Production on Sun Aug 16 21:46:33 2026
Version 23.26.2.0.0
Copyright (c) 1982, 2026, Oracle.  All rights reserved.
Connected to:
Oracle AI Database 26ai Enterprise Edition Release 23.26.2.0.0 - Production
Version 23.26.2.0.0
SQL>

We can also use ASMCMD to verify that the ASM disk group was created and mounted successfully:

[grid@OL95 ~]$ asmcmd -p
ASMCMD [+] > lsdg
State    Type    Rebal  Sector  Logical_Sector  Block        AU  Total_MB  Free_MB  Req_mir_free_MB  Usable_file_MB  Offline_disks  Voting_files  Name
MOUNTED  EXTERN  N         512             512   4096  67108864     13248    12352                0           12352              0             N  ASM/

Comments

Post a Comment

Popular posts from this blog

Oracle 21c Enhancements for TTS Export/Import

By -
  In Oracle version 21c, new features have been introduced for transportable tablespace (TTS) export/import. This article explores these capabilities in detail. Improvement 1: Parallel Execution of TTS Export/Import In Oracle 19c, TTS export/import operations could not be executed in parallel, as demonstrated by the following: Connected to: Oracle Database 19c Enterprise Edition Release 19.0 .0 .0 .0 – Production ORA-39002: invalid operation ORA-39047: Jobs of type TRANSPORTABLE cannot use multiple execution streams. Oracle addressed this limitation in version 21c, enabling parallel execution for TTS export/import: [oracle@oLinux7 ~]$ expdp directory=drm dumpfile=TTS_DUMP%U.dmp transport_tablespaces=tbs1,tbs2 transport_full_check= y parallel= 2 Export: Release 21.0 . 0 . 0 . 0 – Production on Tue Oct 12 06 : 48 : 54 2021 Version 21.3 . 0 . 0 . 0 Processing object type TRANSPORTABLE_EXPORT/STATISTICS/TABLE_STATISTICS Processing object type TRANSPORTABLE_EXPOR...
Read more

Oracle 23ai — error_message_details Parameter for Displaying Error Details

By -
  error_message_details   is another new parameter introduced in Oracle version 23ai, which allows displaying detailed information about data value-related errors. By setting this parameter to   ON , we can see the exact value that caused errors such as   ORA-00001: unique constraint violated   within the error message itself. For example, in the following scenario, enabling the  error_message_details  parameter helps identify the value that triggered the error: SQL > create table tbl1(id number primary key); Table created. SQL > variable B number; SQL > exec :B: = 2547 ; PL / SQL procedure successfully completed. SQL > insert into tbl1 values (:B); 1 row created. SQL > insert into tbl1 values (:B); ERROR at line 1 : 'ORA-00001: unique constraint (USEF.SYS_C008328) violated on table USEF.TBL1 columns (ID)' 'ORA-03301: (ORA-00001 details) row with column values (ID:2547) already exists' Help: https: / / docs.oracle.com ...
Read more

Buffer Busy Wait and Read by Other Session in Oracle

By -
Image
Assume a block is accessed and pinned in the buffer cache by Session 1 (each buffer can be pinned by only one session at a time). While this block is pinned, if another session attempts to access the same block, it must wait. This type of wait is called  Buffer Busy Wait . What distinguishes Buffer Busy Wait from some other wait events is that the contention occurs at the  block level . Even if the two sessions intend to access different rows within the same block, they are still competing at the block level. As you know, Oracle blocks can contain different types of data. For example, one block may hold user data, while another may store control information. Therefore, contention for blocks can be divided into several categories: Data Block Data Segment Header Undo Header Undo Block Let’s briefly review the role of each block type in this wait event. 1) Data Block This refers to the blocks that store object data. Buffer Busy Waits at this level can have several causes: Poorly ...
Read more