Skip to main content

Naming Conventions of Oracle Database

Naming Conventions of Oracle Database


About Assigning Global Database Names During Installation

The database name input field is used to set the DB_NAME, DB_UNIQUE_NAME, and DB_DOMAIN Oracle initialization parameter values.


The Oracle Database software identifies a database by its global database name. A global database name consists of the database name and database domain. Usually, the database domain is the same as the network domain, but it need not be. The global database name uniquely distinguishes a database from any other database in the same network. You specify the global database name when you create a database during the installation or using the Oracle Database Configuration Assistant.


For example:


sales.us.example.com


Here:


sales.us is the name of the database. The database name, DB_UNIQUE_NAME, portion is a string of no more than 30 characters that can contain alphanumeric characters, underscore (_), dollar sign ($), and pound sign (#) but must begin with an alphabetic character. No other special characters are permitted in a database name.


sales.us is also the DB_NAME. The DB_NAME initialization parameter specifies a database identifier of up to eight characters.


example.com is the database domain in which the database is located. In this example, the database domain equals the network domain. Together, the database name and the database domain make the global database name unique. The domain portion is a string of no more than 128 characters that can contain alphanumeric characters, underscore (_), and pound sign (#). The DB_DOMAIN initialization parameter specifies the database domain name.


However, the DB_NAME parameter need not necessarily be the first eight characters of DB_UNIQUE_NAME.


The DB_NAME parameter and the DB_DOMAIN parameter combine to create the global database name value.


The system identifier (SID) identifies a specific database instance. The SID uniquely distinguishes the instance from any other instance on the same computer. Each database instance requires a unique SID and database name. In most cases, the SID equals the database name portion of the global database name.


link : About Assigning Global Database Names During Installation

Labels:

Comments

Post a Comment

Popular posts from this blog

Upgrading Issue for RHEL 7 to 8 With Leapp

Overview The Leapp utility is a framework for updating and upgrading operating systems as well as applications. The operations of this utility consist of two phases 1. the preupgrade Phase – that chack the upgrade possibilities and 2. the actual upgrade phase – that map packages between previous and current versions of the software packages. Issue – 01: After running ‘ sudo leapp preupgrade ‘ sometimes you find the below issue in ‘ /var/log/leapp/leapp-report.txt ‘. Detail: Risk Factor: high (inhibitor) Title: Leapp detected loaded kernel drivers which have been removed in RHEL 8. Upgrade cannot proceed. Summary: Support for the following RHEL 7 device drivers has been removed in RHEL 8: – pata_acpi Key: f08a07da902958defa4f5c2699fae9ec2eb67c5b Remediation: 1. Disable detected kernel drivers in order to proceed with the upgrade process using the rmmod or modprobe -r . rmmod – Simple program to remove a module from the Linux Kernel modprobe – Add and remove modules from the Linux Ke...
Post a Comment
Read more

ORA-00800: soft external error arguments

The problem as stated: After upgrading the Oracle Database from 12c to 19c the following error generated in the alert log file. Actual Oracle Error Code: ORA-00800 After Upgrading from 12c to 19c ORA-00800: soft external error, arguments occured Oracle Database Enterprise 19c fails to start with error: ORA-00800: soft external error, arguments: [Set Priority Failed], [VKTM] Why does Insights prevent Oracle grid services from starting How to configure the User slice to allow Real-Time Scheduling for user processes In Alert Log: Errors in file /u01/app/oracle/diag/rdbms/orclproddbone/orclprod/trace/psbcdb_vktm_3529.trc (incident=1200048) (PDBNAME=CDB$ROOT): ORA-00800: soft external error, arguments: [Set Priority Failed], [VKTM], [Check traces and OS configuration], [Check Oracle document and MOS notes], [] Incident details in: /u01/app/oracle/diag/rdbms/orclproddbone/orclprod/incident/incdir_1200048/psbcdb_vktm_3529_i1200048.trc 2023-10-30T10:04:53.536165+06:00 Error attempting to elev...
Post a Comment
Read more

The Oracle Management Server (OMS) host and port specified via OMS_HOST and EM_UPLOAD_PORT is not available

The Oracle Management Server (OMS) host and port specified via OMS_HOST and EM_UPLOAD_PORT is not available. 1.0. error message: Error Message: The Oracle Management Server (OMS) host and port specified via OMS_HOST and EM_UPLOAD_PORT is not available. Pass in a valid hostname and port number for the OMS to successfully deploy the agent. 1.1. deploy log: Log: /opt/gc_inst/em/EMGC_OMS1/sysman/agentpush/2023-11-07_16-09-23-PM/applogs/dblivesrv_deploy.log Execution of command cd /opt/agent/ADATMP_2023-11-07_16-09-23-PM;/opt/agent/ADATMP_2023-11-07_16-09-23-PM/agentDeploy.sh -ignorePrereqs ORACLE_HOSTNAME=dblivesrv AGENT_BASE_DIR=/opt/agent OMS_HOST=oemsrv.localdomain EM_UPLOAD_PORT=4903 AGENT_INSTANCE_HOME=/opt/agent/agent_inst b_doDiscovery=false START_AGENT=false b_forceInstCheck=true -force AGENT_PORT=3872 on host dblivesrv Failed 1.2. oms details: [oracle@oemsrv ~]$ $OMS_HOME/bin/emctl status oms -details Oracle Enterprise Manager Cloud Control 13c Release 5 Copyright (c) 1996, 2...
Post a Comment
Read more